[JBoss JIRA] (TOOLSDOC-274) Document how to install SOA Tooling plugins for SOA-P, BRMS, etc. from JBoss Central
by Nick Boldt (JIRA)
Nick Boldt created TOOLSDOC-274:
-----------------------------------
Summary: Document how to install SOA Tooling plugins for SOA-P, BRMS, etc. from JBoss Central
Key: TOOLSDOC-274
URL: https://issues.jboss.org/browse/TOOLSDOC-274
Project: Documentation for JBoss Tools and Developer Studio
Issue Type: Task
Security Level: Public (Everyone can see)
Components: Beginners Guide, Getting Started Guide, Update Guide
Affects Versions: 3.3.0.Beta2
Reporter: Nick Boldt
Assignee: Isaac Rooskov
Fix For: 3.3.0.Beta2
We need a README for installing the SOA-related plugins via JBoss Central - so
that we explicitly tell the SOA, BRMS, etc. users how to get their plugins
installed.
See also JBDS-2046, which tracks the UI in Central that users will see. Note too that there will be an update site on devstudio.jboss.com from which users will get their bits (via Central) and from which bits can be installed the old way too.
--
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
[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
13 years, 11 months
[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
13 years, 11 months
[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