[JBoss JIRA] Created: (JBDS-1308) replace b3 aggregator w/ tycho update site build
by Nick Boldt (JIRA)
replace b3 aggregator w/ tycho update site build
------------------------------------------------
Key: JBDS-1308
URL: https://jira.jboss.org/browse/JBDS-1308
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Components: Build
Affects Versions: 4.0.0.M2, 4.0.0.Beta1
Reporter: Nick Boldt
Assignee: Nick Boldt
Current implementation of the aggregator in JBDS uberbuilder uses b3, which I've wrapped w/ a bit of Ant to prefetch the update site zips and deduce which features to expose.
However, it doesn't work w/ remote update site URLs as input so I'd either have to rewrite the ant wrapper, or trash it in place of the code already working for the JBT aggregator (with a different site.xml if we want to include/exclude different stuff in JBDS vs. JBT).
Since that's easier and ultimately moves us forward, not backward, that's the plan.
This should ensure that all the stuff currently agg'd into JBDS from external builds (Drools, Teiid, jBPM 3) and the newly inserted ModeShape can all be agg'd in from the same source sites as JBT.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 5 months
[JBoss JIRA] Created: (JBDS-857) Installer build should not depend on bundle.eclipse step or on creation of *-ALL-*.zip files
by Nick Boldt (JIRA)
Installer build should not depend on bundle.eclipse step or on creation of *-ALL-*.zip files
--------------------------------------------------------------------------------------------
Key: JBDS-857
URL: https://jira.jboss.org/jira/browse/JBDS-857
Project: JBoss Developer Studio
Issue Type: Bug
Affects Versions: 3.0.0.M4
Reporter: Nick Boldt
Assignee: Nick Boldt
Fix For: 3.0.0.M4
bundle.eclipse is basically and empty method call, but there's a lot of leftover properties being set related to it which should be removed.
Also, the ALL zips are still created and used to produce the installer jars, then deleted while the build results page is being created.
We should switch the installer from "unpack a zip" to "use p2 to install a from the update zip" . If done correctly, we may even end up with ONE installer instead of 4, saving a ton of bandwidth and simplifying deployment to diverse hardware.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 5 months
[JBoss JIRA] Created: (JBIDE-7419) Project Examples: Seam Booking22 fails to deploy - jboss-seam.jar module listed in application.xml does not exist within .ear
by Burr Sutter (JIRA)
Project Examples: Seam Booking22 fails to deploy - jboss-seam.jar module listed in application.xml does not exist within .ear
-----------------------------------------------------------------------------------------------------------------------------
Key: JBIDE-7419
URL: https://jira.jboss.org/browse/JBIDE-7419
Project: Tools (JBoss Tools)
Issue Type: Bug
Environment: Win7 64-bit (32-bit JVM)
Reporter: Burr Sutter
Project Examples: Seam Booking22 fails to deploy - jboss-seam.jar module listed in application.xml does not exist within .ear
Caused by: java.lang.RuntimeException: Error determining structure: booking22-ear.ear
at org.jboss.deployment.EARStructure.doDetermineStructure(EARStructure.java:300) [:6.0.0.20100911-M5]
at org.jboss.deployers.vfs.plugins.structure.AbstractVFSArchiveStructureDeployer.determineStructure(AbstractVFSArchiveStructureDeployer.java:60) [:2.2.0.Alpha7]
at org.jboss.deployers.vfs.plugins.structure.StructureDeployerWrapper.determineStructure(StructureDeployerWrapper.java:73) [:2.2.0.Alpha7]
at org.jboss.deployers.vfs.plugins.structure.VFSStructuralDeployersImpl.doDetermineStructure(VFSStructuralDeployersImpl.java:197) [:2.2.0.Alpha7]
at org.jboss.deployers.vfs.plugins.structure.VFSStructuralDeployersImpl.determineStructure(VFSStructuralDeployersImpl.java:222) [:2.2.0.Alpha7]
at org.jboss.deployers.structure.spi.helpers.AbstractStructuralDeployers.determineStructure(AbstractStructuralDeployers.java:77) [:2.2.0.Alpha7]
... 31 more
Caused by: java.lang.RuntimeException: jboss-seam.jar module listed in application.xml does not exist within .ear vfs:///C:/servers/jboss-6.0.0.20100911-M5v2/jboss-6.0.0.20100911-M5/server/default/deploy/booking22-ear.ear/
at org.jboss.deployment.EARStructure.doDetermineStructure(EARStructure.java:271) [:6.0.0.20100911-M5]
... 36 more
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 5 months