May 2012 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-10576) Provide linking capability for all field editors in forms of JBoss Tools XML Editor

by Viacheslav Kabanovich (Created) (JIRA)

Provide linking capability for all field editors in forms of JBoss Tools XML Editor ----------------------------------------------------------------------------------- Key: JBIDE-10576 URL: https://issues.jboss.org/browse/JBIDE-10576 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: common/jst/core Affects Versions: 3.3.0.M5 Reporter: Viacheslav Kabanovich Assignee: Viacheslav Kabanovich Fix For: 3.3.0.Beta1 Now the linking capability is implemented only in text+button field editors. In some cases a drop-down field editor is used for attributes referencing other objects that may be linked. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

6
9
0 / 0

[JBoss JIRA] (JBDS-1983) JBDS Welcome screen should accept contributions from 3rd party extras like JRebel, Spring, FindBugs, PMD

by Nick Boldt (Created) (JIRA)

JBDS Welcome screen should accept contributions from 3rd party extras like JRebel, Spring, FindBugs, PMD -------------------------------------------------------------------------------------------------------- Key: JBDS-1983 URL: https://issues.jboss.org/browse/JBDS-1983 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Security Level: Public (Everyone can see) Components: 3rdPartyCertification, 3rdPartyDependencies, Welcome Affects Versions: 5.0.0.M5 Reporter: Nick Boldt Assignee: Nick Boldt Fix For: 5.0.0.Beta2 We're currently patching SpringIDE's broken plugin (JBDS-1838) which contributes a new Welcome screen, leading to this issue: !https://issues.jboss.org/secure/attachment/12349923/2011-12-15_0052.png! However, it's been revealed that in addition to Spring, PMD, FindBugs, and now JRebel also have this failing. Therefore we ought to find a new way to suppress the effect across all of JBT/JBDS instead of per-plugin, or get it fixed upstream. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

9
39
0 / 0

[JBoss JIRA] Created: (JBDS-1620) CLONE - Enable dropin folder reconciling by default for JBDS product

by Denis Golovin (JIRA)

CLONE - Enable dropin folder reconciling by default for JBDS product -------------------------------------------------------------------- Key: JBDS-1620 URL: https://issues.jboss.org/browse/JBDS-1620 Project: Developer Studio (JBoss Developer Studio) Issue Type: Feature Request Components: Build Affects Versions: 4.0.0.GA Reporter: Denis Golovin Assignee: Denis Golovin Fix For: 4.1.0.GA Now to get that supported several additions steps should be done: To activate dropins reconciling you need to do the following: - open studio/configuration/org.eclipse.equinox.simpleconfigurator/bundles.info - find the line org.eclipse.equinox.p2.reconciler.dropins,1.1.0.v20100525,plugins/org.eclipse.equinox.p2.reconciler.dropins_1.1.0.v20100525.jar,4,false and change it to org.eclipse.equinox.p2.reconciler.dropins,1.1.0.v20100525,plugins/org.eclipse.equinox.p2.reconciler.dropins_1.1.0.v20100525.jar,4,true - create the studio/dropins directory and add plugins as is usual - start JBDS with the -clean option at least once To eliminate this steps plugin org.eclipse.equinox.p2.reconciler.dropins should be marked as auto started in jbds-all.product definition which is used to build JBDS product -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

3
11
0 / 0

[JBoss JIRA] (JBDS-2058) Add Equinox Transforms to JBDS

by Snjezana Peco (JIRA)

Snjezana Peco created JBDS-2058: ----------------------------------- Summary: Add Equinox Transforms to JBDS Key: JBDS-2058 URL: https://issues.jboss.org/browse/JBDS-2058 Project: Developer Studio (JBoss Developer Studio) Issue Type: Feature Request Security Level: Public (Everyone can see) Components: 3rdPartyDependencies, Build, installer Affects Versions: 5.0.0.M5 Reporter: Snjezana Peco Assignee: Snjezana Peco Fix For: 5.0.0.Beta2 There are several issues with the 3rd party plugins that can be solved using Equinox Transforms - http://wiki.eclipse.org/Equinox_Transforms We can do the following: - remove/change unnecessary/invalid extension points - remove/change keybinding conflicts ... See JBDS-1983, JBDS-2030 Equinox Transforms has to be tested with Eclipse 3.7. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

4
3
0 / 0

[JBoss JIRA] (JBIDE-11176) Exception is thrown when seam dependency is added

by Rastislav Wagner (JIRA)

Rastislav Wagner created JBIDE-11176: ---------------------------------------- Summary: Exception is thrown when seam dependency is added Key: JBIDE-11176 URL: https://issues.jboss.org/browse/JBIDE-11176 Project: Tools (JBoss Tools) Issue Type: Bug Components: maven Affects Versions: 3.3.0.Beta1 Reporter: Rastislav Wagner Assignee: Fred Bricon java.lang.NullPointerException at org.jboss.tools.maven.seam.MavenSeamActivator.configureParentProject(MavenSeamActivator.java:839) at org.jboss.tools.maven.seam.MavenSeamActivator.configureSeamProject(MavenSeamActivator.java:161) at org.jboss.tools.maven.seam.internal.project.facet.MavenPostInstallListener.handleEvent(MavenPostInstallListener.java:58) at org.eclipse.wst.common.project.facet.core.events.internal.DelayedClassLoadingListener.handleEvent(DelayedClassLoadingListener.java:62) at org.eclipse.wst.common.project.facet.core.events.internal.ProjectListenerRegistry.notifyListeners(ProjectListenerRegistry.java:76) at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.notifyListeners(FacetedProject.java:1327) at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.modifyInternal(FacetedProject.java:454) at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.mergeChangesInternal(FacetedProject.java:1181) at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.access$2(FacetedProject.java:1117) at org.eclipse.wst.common.project.facet.core.internal.FacetedProject$1.run(FacetedProject.java:324) at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2344) at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.modify(FacetedProject.java:339) at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.installProjectFacet(FacetedProject.java:255) at org.jboss.tools.maven.seam.configurators.SeamProjectConfigurator.installWarFacets(SeamProjectConfigurator.java:315) at org.jboss.tools.maven.seam.configurators.SeamProjectConfigurator.configureInternal(SeamProjectConfigurator.java:173) at org.jboss.tools.maven.seam.configurators.SeamProjectConfigurator.mavenProjectChanged(SeamProjectConfigurator.java:257) at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.mavenProjectChanged(ProjectConfigurationManager.java:752) at org.eclipse.m2e.core.internal.project.registry.ProjectRegistryManager.notifyProjectChangeListeners(ProjectRegistryManager.java:724) at org.eclipse.m2e.core.internal.project.registry.ProjectRegistryManager.applyMutableProjectRegistry(ProjectRegistryManager.java:847) at org.eclipse.m2e.core.internal.project.registry.ProjectRegistryManager.refresh(ProjectRegistryManager.java:280) at org.eclipse.m2e.core.internal.project.registry.MavenProjectManager.refresh(MavenProjectManager.java:58) at org.eclipse.m2e.core.internal.builder.MavenBuilder.build(MavenBuilder.java:120) at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:728) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:199) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:239) at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:292) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:295) at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:351) at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:374) at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:143) at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:241) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) and java.lang.IllegalArgumentException: Path for project must have only one segment. at org.eclipse.core.runtime.Assert.isLegal(Assert.java:63) at org.eclipse.core.internal.resources.WorkspaceRoot.getProject(WorkspaceRoot.java:184) at org.jboss.tools.maven.seam.MavenSeamActivator.configureTestProject(MavenSeamActivator.java:172) at org.jboss.tools.maven.seam.MavenSeamActivator.configureSeamProject(MavenSeamActivator.java:163) at org.jboss.tools.maven.seam.internal.project.facet.MavenPostInstallListener.handleEvent(MavenPostInstallListener.java:58) at org.eclipse.wst.common.project.facet.core.events.internal.DelayedClassLoadingListener.handleEvent(DelayedClassLoadingListener.java:62) at org.eclipse.wst.common.project.facet.core.events.internal.ProjectListenerRegistry.notifyListeners(ProjectListenerRegistry.java:76) at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.notifyListeners(FacetedProject.java:1327) at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.modifyInternal(FacetedProject.java:454) at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.mergeChangesInternal(FacetedProject.java:1181) at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.access$2(FacetedProject.java:1117) at org.eclipse.wst.common.project.facet.core.internal.FacetedProject$1.run(FacetedProject.java:324) at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2344) at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.modify(FacetedProject.java:339) at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.installProjectFacet(FacetedProject.java:255) at org.jboss.tools.maven.seam.configurators.SeamProjectConfigurator.installWarFacets(SeamProjectConfigurator.java:315) at org.jboss.tools.maven.seam.configurators.SeamProjectConfigurator.configureInternal(SeamProjectConfigurator.java:173) at org.jboss.tools.maven.seam.configurators.SeamProjectConfigurator.mavenProjectChanged(SeamProjectConfigurator.java:257) at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.mavenProjectChanged(ProjectConfigurationManager.java:752) at org.eclipse.m2e.core.internal.project.registry.ProjectRegistryManager.notifyProjectChangeListeners(ProjectRegistryManager.java:724) at org.eclipse.m2e.core.internal.project.registry.ProjectRegistryManager.applyMutableProjectRegistry(ProjectRegistryManager.java:847) at org.eclipse.m2e.core.internal.project.registry.ProjectRegistryManager.refresh(ProjectRegistryManager.java:280) at org.eclipse.m2e.core.internal.project.registry.MavenProjectManager.refresh(MavenProjectManager.java:58) at org.eclipse.m2e.core.internal.builder.MavenBuilder.build(MavenBuilder.java:120) at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:728) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:199) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:239) at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:292) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:295) at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:351) at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:374) at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:143) at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:241) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

3
7
0 / 0

[JBoss JIRA] (JBIDE-10696) "error" for "non-error" conditions in openshift

by Max Rydahl Andersen (JIRA)

Max Rydahl Andersen created JBIDE-10696: ------------------------------------------- Summary: "error" for "non-error" conditions in openshift Key: JBIDE-10696 URL: https://issues.jboss.org/browse/JBIDE-10696 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Reporter: Max Rydahl Andersen Assignee: Andre Dietisheim Fix For: 3.3.0.Beta1 not sure if this is databinding limitations or our usage of databinding but i.e. when unselecting "Create new project" in openshift wizard I instantly get an "error icon/message" saying "select an existing project to use with OpenShift" - this feels rather "abrupt" since the user haven't actually done anything out of the ordinary, he is just filling in the form. i.e. in eclipse JDT it will just state "Enter a location for the project" with no error icon and finish disabled. I believe Eclipse UI guidelines says the same "5.5 Validate the wizard data in tab order. Display a prompt when information is absent, and an error when information is invalid." http://www.eclipse.org/articles/Article-UI-Guidelines/Contents.html#Wizards -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

4
9
0 / 0

[JBoss JIRA] (JBIDE-11590) OpenShift: Exception while importing application

by Stefan Bunciak (JIRA)

Stefan Bunciak created JBIDE-11590: -------------------------------------- Summary: OpenShift: Exception while importing application Key: JBIDE-11590 URL: https://issues.jboss.org/browse/JBIDE-11590 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 3.3.0.Beta3 Environment: Eclipse 4.2 Juno Fedora 15 Reporter: Stefan Bunciak Assignee: Andre Dietisheim Fix For: 3.3.0.Beta3 Tried to create new OpenShift server adapter, then import the application via this wizard and while loading cartridges this exception popped out: http://pastebin.com/n4BYMCtj Despite this I was able to import application successfully. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

2
5
0 / 0

[JBoss JIRA] (JBIDE-11194) new openshift server wizard is missing the "save password" checkbox

by Max Rydahl Andersen (JIRA)

Max Rydahl Andersen created JBIDE-11194: ------------------------------------------- Summary: new openshift server wizard is missing the "save password" checkbox Key: JBIDE-11194 URL: https://issues.jboss.org/browse/JBIDE-11194 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift, JBossAS/Servers Reporter: Max Rydahl Andersen Assignee: Andre Dietisheim Fix For: 3.3.0.Beta2 $subject should have same behavior/layout as the other username/passwords used for openshift -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

5
7
0 / 0

[JBoss JIRA] (JBIDE-11656) Content assist not working for EL ui:param variable

by Cody Lerum (JIRA)

Cody Lerum created JBIDE-11656: ---------------------------------- Summary: Content assist not working for EL ui:param variable Key: JBIDE-11656 URL: https://issues.jboss.org/browse/JBIDE-11656 Project: Tools (JBoss Tools) Issue Type: Bug Affects Versions: 3.3.0.Beta2 Environment: JBoss Tools nightly as of 4/25/12 -> JBoss Tools JSF 3.3.0.v20120423-2340-H897-Beta3 Reporter: Cody Lerum For the following code assist (content assist?) does not work for for the #{organization.name} in the h:outputText Also doesn't work if the ui:param is defined in the ui:define <ui:composition> <f:metadata> <ui:param name="organization" value="#{organizationManager.organization}" /> </f:metadata> <ui:define> <h:outputText value="#{organization.name} /> </ui:define> </ui:composition> -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

3
5
0 / 0

[JBoss JIRA] (JBIDE-10657) default java version problem for web projects is back

by Max Rydahl Andersen (JIRA)

Max Rydahl Andersen created JBIDE-10657: ------------------------------------------- Summary: default java version problem for web projects is back Key: JBIDE-10657 URL: https://issues.jboss.org/browse/JBIDE-10657 Project: Tools (JBoss Tools) Issue Type: Bug Components: common/jst/core, JBossAS/Servers Affects Versions: 3.3.0.M5 Reporter: Max Rydahl Andersen Assignee: Alexey Kazakov Priority: Critical Fix For: 3.3.0.Beta1 i'm not sure where the culprit is but https://community.jboss.org/message/647045#647045 shows that we are back at having problems with Java versions being set to "latest" (i.e. 7.0) on projects even though default java for workspace is 6.0 and the runtime is targeting 6.0. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

3
7
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues May 2012