March 2012 - jbosstools-issues - Jboss List Archives

[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

13 years, 11 months

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

13 years, 11 months

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

13 years, 11 months

4
9
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

13 years, 11 months

5
7
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

13 years, 11 months

3
7
0 / 0

[JBoss JIRA] (JBIDE-10063) Forge creates invalid web.xml

by Burr Sutter (Created) (JIRA)

Forge creates invalid web.xml ----------------------------- Key: JBIDE-10063 URL: https://issues.jboss.org/browse/JBIDE-10063 Project: Tools (JBoss Tools) Issue Type: Bug Components: forge Environment: Tools 3.3.M4 Reporter: Burr Sutter Forge console (plug-in) - new-project --named forgeProject2 --topLevelPackage com.burrsutter.forgeProject2 - scaffold setup creates a web.xml with the following errors (according to Eclipse) - error: Attribute location references to /404.jsp that does not exist in web content - error: Attribute location references to /500.jsp that does not exist in web content -- 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

13 years, 11 months

7
8
0 / 0

[JBoss JIRA] (JBIDE-11340) Run as.. loads wrong URL for portlet project and EPP 4

by Lucia Jelinkova (JIRA)

Lucia Jelinkova created JBIDE-11340: --------------------------------------- Summary: Run as.. loads wrong URL for portlet project and EPP 4 Key: JBIDE-11340 URL: https://issues.jboss.org/browse/JBIDE-11340 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS/Servers Affects Versions: 3.3.0.Beta1 Reporter: Lucia Jelinkova Assignee: Rob Stryker Fix For: 3.3.0.Beta3 -- 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

13 years, 11 months

3
12
0 / 0

[JBoss JIRA] Created: (JBIDE-8700) Add Configure>Detect Project Configuration menu to runtime plugin

by Snjezana Peco (JIRA)

Add Configure>Detect Project Configuration menu to runtime plugin ----------------------------------------------------------------- Key: JBIDE-8700 URL: https://issues.jboss.org/browse/JBIDE-8700 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: runtimes Affects Versions: 3.2.0.Final Reporter: Snjezana Peco Assignee: Snjezana Peco Fix For: 3.3.0.M1 The action would detect different project configurations. For the first time, it would detect CDI based on the existence of cdi-api in the project's classpath. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

3
8
0 / 0

[JBoss JIRA] (JBIDE-10177) web.xml validator should be aware of JSF mappings

by Alexey Kazakov (Created) (JIRA)

web.xml validator should be aware of JSF mappings ------------------------------------------------- Key: JBIDE-10177 URL: https://issues.jboss.org/browse/JBIDE-10177 Project: Tools (JBoss Tools) Issue Type: Bug Components: JSF Affects Versions: 3.3.0.M4 Reporter: Alexey Kazakov Assignee: Viacheslav Kabanovich Fix For: 3.3.0.Beta1 1. Create JSF2 KickStart project. 2. Create 404.xhtml page in WebContent folder 3. Add the following code to the end of web.xml file: {code} <error-page> <error-code>404</error-code> <location>/404.jsf</location> </error-page> {code} There should not be any error/warning markers on /404.jsf. This location should be mapped to the 404.xhtml file. But right now I get: "error: Attribute location references to /404.jsp that does not exist in web content" error message. -- 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

13 years, 11 months

10
14
0 / 0

[JBoss JIRA] (JBIDE-9998) Make new Forge Runtime Layout Work with JBT

by Koen Aers (Created) (JIRA)

Make new Forge Runtime Layout Work with JBT ------------------------------------------- Key: JBIDE-9998 URL: https://issues.jboss.org/browse/JBIDE-9998 Project: Tools (JBoss Tools) Issue Type: Bug Components: forge Reporter: Koen Aers Assignee: Koen Aers Fix For: 3.3.0.M4 Forge Runtime changed module layout yesterday, resulting in the current Forge Runtime SNAPSHOT builds not working with the tools. -- 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

13 years, 11 months

6
5
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 March 2012