January 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-12137) openshift server adapter should show progress of git push while running not in the end

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12137?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-12137: ------------------------------------- I filed a bugzilla to Eclipse bugzilla > openshift server adapter should show progress of git push while running not in the end > -------------------------------------------------------------------------------------- > > Key: JBIDE-12137 > URL: https://issues.jboss.org/browse/JBIDE-12137 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 3.3.0.Final > Reporter: Max Rydahl Andersen > Assignee: Andre Dietisheim > Fix For: 4.1.0.Alpha1 > > Attachments: openshift-6.ogv > > > Please bring back that the progress monitor shows the git progress instead of just showing console output in the end -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-12137) openshift server adapter should show progress of git push while running not in the end

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12137?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-12137: ------------------------------------- Attachment: openshift-6.ogv I did a patch. Added some screencast showing the patched egit/jgit in action > openshift server adapter should show progress of git push while running not in the end > -------------------------------------------------------------------------------------- > > Key: JBIDE-12137 > URL: https://issues.jboss.org/browse/JBIDE-12137 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 3.3.0.Final > Reporter: Max Rydahl Andersen > Assignee: Andre Dietisheim > Fix For: 4.1.0.Alpha1 > > Attachments: openshift-6.ogv > > > Please bring back that the progress monitor shows the git progress instead of just showing console output in the end -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13333) Fixing Eclipse/Kepler

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13333?page=com.atlassian.jira.plugi... ] Snjezana Peco commented on JBIDE-13333: --------------------------------------- https://bugs.eclipse.org/bugs/show_bug.cgi?id=398399 > Fixing Eclipse/Kepler > --------------------- > > Key: JBIDE-13333 > URL: https://issues.jboss.org/browse/JBIDE-13333 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: UpStream > Reporter: Max Rydahl Andersen > Assignee: Max Rydahl Andersen > Priority: Blocker > Fix For: 4.1.0.Alpha1 > > > "container" issue for issues related to fixes important to get into Kepler. > Please link your Eclipse/Kepler issue to this one instead of using subtasks. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13346) DirectoryScanner fails on non-existing folders

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13346?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-13346: --------------------------------------------- https://github.com/jbosstools/jbosstools-server/pull/38/ seems like a fair fix for this. The log message was not there in the past and just added assuming there wouldn't be any logging except a serious error; the PR fixes it by not logging for this specific case. +1 > DirectoryScanner fails on non-existing folders > ---------------------------------------------- > > Key: JBIDE-13346 > URL: https://issues.jboss.org/browse/JBIDE-13346 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: Archives, JBossAS/Servers > Affects Versions: 4.0.0.Final > Environment: Windows XP/Windows 7 > Eclipse 4.3M4 > Reporter: Jesper Skov > Assignee: Rob Stryker > Priority: Minor > Fix For: 4.0.1.Final, 4.1.0.Alpha1 > > Attachments: org.eclipse.wst.common.component > > > DirectoryScanner can be made to fail on non-existing folders. > In our setup, these folders are possibly picked up from the Deployment Assembly settings. > The folders are created by our custom Builder with highest priority, so appears to work properly with everything else in Eclipse. > But it seems the Archive DirectoryScanner runs before our builder. > The stack trace looks like this: > > {code} > java.lang.IllegalStateException: basedir C:\udvikler\ws\plugins\jb.it.reuters\build\gen-lib-deployable is not a directory > at org.jboss.ide.eclipse.archives.core.asf.DirectoryScanner.scanPrepare(DirectoryScanner.java:552) > at org.jboss.ide.eclipse.archives.core.asf.DirectoryScanner.scan(DirectoryScanner.java:588) > at org.jboss.ide.eclipse.archives.core.model.DirectoryScannerFactory.createDirectoryScanner(DirectoryScannerFactory.java:66) > at org.jboss.ide.eclipse.archives.webtools.filesets.vcf.WorkspaceFilesetVirtualComponent$WorkspaceFilter.<init>(WorkspaceFilesetVirtualComponent.java:100) > at org.jboss.ide.eclipse.archives.webtools.filesets.vcf.WorkspaceFilesetVirtualComponent.getRootFolder(WorkspaceFilesetVirtualComponent.java:53) > at org.eclipse.wst.common.componentcore.internal.flat.FlatVirtualComponent.consumeComponent(FlatVirtualComponent.java:203) > at org.eclipse.wst.common.componentcore.internal.flat.FlatVirtualComponent.addConsumedReferences(FlatVirtualComponent.java:196) > at org.eclipse.jst.j2ee.internal.common.ClasspathLibraryExpander.optimize(ClasspathLibraryExpander.java:47) > at org.eclipse.wst.common.componentcore.internal.flat.FlatVirtualComponent.cacheResources(FlatVirtualComponent.java:119) > at org.eclipse.wst.common.componentcore.internal.flat.FlatVirtualComponent.fetchResources(FlatVirtualComponent.java:101) > at org.eclipse.jst.j2ee.internal.common.ClasspathLibraryExpander.fetchResource(ClasspathLibraryExpander.java:74) > at org.eclipse.jst.j2ee.internal.common.classpath.J2EEComponentClasspathContainer.getBaseEARLibRefs(J2EEComponentClasspathContainer.java:463) > at org.eclipse.jst.j2ee.internal.common.classpath.J2EEComponentClasspathContainer.requiresUpdate(J2EEComponentClasspathContainer.java:208) > at org.eclipse.jst.j2ee.internal.common.classpath.J2EEComponentClasspathContainer.refresh(J2EEComponentClasspathContainer.java:540) > at org.eclipse.jst.j2ee.internal.common.classpath.J2EEComponentClasspathUpdater$ModuleUpdateJob.processModules(J2EEComponentClasspathUpdater.java:311) > at org.eclipse.jst.j2ee.internal.common.classpath.J2EEComponentClasspathUpdater$ModuleUpdateJob.access$4(J2EEComponentClasspathUpdater.java:295) > at org.eclipse.jst.j2ee.internal.common.classpath.J2EEComponentClasspathUpdater$ModuleUpdateJob$1.run(J2EEComponentClasspathUpdater.java:336) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.jst.j2ee.internal.common.classpath.J2EEComponentClasspathUpdater$ModuleUpdateJob.run(J2EEComponentClasspathUpdater.java:321) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53) > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13373) Allow to specify modeshape repository from commad line

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13373?page=com.atlassian.jira.plugi... ] Andrej Podhradsky closed JBIDE-13373. ------------------------------------- Committed to jbosstools-4.0.x branch > Allow to specify modeshape repository from commad line > ------------------------------------------------------ > > Key: JBIDE-13373 > URL: https://issues.jboss.org/browse/JBIDE-13373 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: QA > Reporter: Andrej Podhradsky > Assignee: Andrej Podhradsky > Fix For: 4.0.0.Final > > > So far, the modeshape repository is hardcoded. Since different modeshape distributions contain different repositories it would be great to have possibility to specify the repository from command line. > For example: > as-5.1 + modeshape 2.8.3 uses 'repository' > but > as-7.1 + modeshape 3.0.1 uses 'sample' > or > soa-5.3 + eds-5.3 uses 'eds -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13333) Fixing Eclipse/Kepler

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13333?page=com.atlassian.jira.plugi... ] Snjezana Peco commented on JBIDE-13333: --------------------------------------- https://bugs.eclipse.org/bugs/show_bug.cgi?id=398383 > Fixing Eclipse/Kepler > --------------------- > > Key: JBIDE-13333 > URL: https://issues.jboss.org/browse/JBIDE-13333 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: UpStream > Reporter: Max Rydahl Andersen > Assignee: Max Rydahl Andersen > Priority: Blocker > Fix For: 4.1.0.Alpha1 > > > "container" issue for issues related to fixes important to get into Kepler. > Please link your Eclipse/Kepler issue to this one instead of using subtasks. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13333) Fixing Eclipse/Kepler

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13333?page=com.atlassian.jira.plugi... ] Snjezana Peco commented on JBIDE-13333: --------------------------------------- https://bugs.eclipse.org/bugs/show_bug.cgi?id=398381 > Fixing Eclipse/Kepler > --------------------- > > Key: JBIDE-13333 > URL: https://issues.jboss.org/browse/JBIDE-13333 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: UpStream > Reporter: Max Rydahl Andersen > Assignee: Max Rydahl Andersen > Priority: Blocker > Fix For: 4.1.0.Alpha1 > > > "container" issue for issues related to fixes important to get into Kepler. > Please link your Eclipse/Kepler issue to this one instead of using subtasks. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-8246) Class cast exception when serializing extensionActivity with Text nodes

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBIDE-8246?page=com.atlassian.jira.plugin... ] Andrej Podhradsky commented on JBIDE-8246: ------------------------------------------ Hi Bob, can we close this issue? I don't know how to verify this :( > Class cast exception when serializing extensionActivity with Text nodes > ----------------------------------------------------------------------- > > Key: JBIDE-8246 > URL: https://issues.jboss.org/browse/JBIDE-8246 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: BPEL > Affects Versions: 3.2.0.CR1 > Reporter: Robert (Bob) Brodt > Assignee: Robert (Bob) Brodt > Fix For: 3.3.0.M1 > > > This was reported here: https://bugs.eclipse.org/bugs/show_bug.cgi?id=335458 > The BPELWriter throws a class cast exception when a Text node containing, e.g. whitespace, is serialized. See BPELWriter#extensionActivity2XML: > Element child = (Element) fragment.getFirstChild(); -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-12280) Build project slow/hangs for the first time a change is made

by Jiri Peterka (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12280?page=com.atlassian.jira.plugi... ] Jiri Peterka closed JBIDE-12280. -------------------------------- I've tried to generate 10000 classes according to Rob's steps however no issue seen in JBDS 5.0.2.CR3, closing. Shanu, if it doesn't still work for you please reopen. > Build project slow/hangs for the first time a change is made > ------------------------------------------------------------ > > Key: JBIDE-12280 > URL: https://issues.jboss.org/browse/JBIDE-12280 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: Archives > Affects Versions: 3.1.1 > Environment: jdk 1.6.0, windows vista > Reporter: Shanu N > Assignee: Rob Stryker > Fix For: 3.3.2 > > Attachments: dumpTest1.log > > > I am using JBOSS Developer studio 3.0.1 GA and I find that the build sometimes just hangs in 78% or 98% or is extremely slow. I have unchecked the 'build automatic' option and also unchecked many of the validators in the Validation menu. This usually happens if I am opening the workspace after a 2 days gap, do a change and build or if I close one workspace, open another or switch to another workspace, do a change and build. If I am continuously working only on one workspace, then anytime I do a build, it is fast. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-10297) Workspace set to default even if set differently

by Rastislav Wagner (JIRA)

[ https://issues.jboss.org/browse/JBIDE-10297?page=com.atlassian.jira.plugi... ] Rastislav Wagner closed JBIDE-10297. ------------------------------------ verified in JBT 3.3.2 2013-01-12_01-27-10-H228 > Workspace set to default even if set differently > ------------------------------------------------ > > Key: JBIDE-10297 > URL: https://issues.jboss.org/browse/JBIDE-10297 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: JBossAS/Servers > Environment: JBoss Tools 3.3.0 Nightly (2011-11-30_14-04-32-H4078) > Mac + Ubuntu > Reporter: Martin Malina > Assignee: Rob Stryker > Priority: Blocker > Fix For: 3.3.0.M5 > > Attachments: jbide-10297.patch > > > Before I installed JBoss Tools into Eclipse workspaces worked fine - Eclipse asks which workspace to use at start time. > Once I installed JBoss Tools, Eclipse stopped asking me for workspace location on startup. Even if I change the workspace it falls back to default on the next start of Eclipse. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues January 2013