-
Bug
-
Resolution: Done
-
Major
-
4.3.0.Beta1
-
None
-
Sprint #3 May 2015, Sprint #4 May 2015, Sprint #5 Jun 2015, Sprint #6 July 2015
-
https://github.com/jbosstools/jbosstools-build-sites/pull/189, https://github.com/jbosstools/jbosstools-maven-plugins/pull/43, https://github.com/jbosstools/jbosstools-maven-plugins/pull/48, https://github.com/jbosstools/jbosstools-build-sites/pull/198, https://github.com/jbdevstudio/jbdevstudio-product/pull/321, https://github.com/jbdevstudio/jbdevstudio-product/pull/322
If we change the way the jbosstools-src.zip is produced, such that in addition to upstream projects it ALSO includes the contents of jbosstools-build-sites too, then we can reuse that mojo for the jbdevstudio-product src.zip too, as it will ALSO include the 17 upstream JBT zips (from Github) and also the local JBDS sources.
This would mean a large chunk of ant code in jbdevstudio-product/sources/build.xml (if not all of it) could go away. Hooray for 1 solution spanning both projects and product!
Max also suggested that we use a clean copy of the sources just in case the build process makes them dirty:
git clone --depth=1 . clean-sources-dir && rm -rf clean-sources-dir/.git
- relates to
-
JBIDE-19756 jbosstools-src.zip has incomplete/misleading version info in folder names/structure
- Closed
-
JBIDE-20416 Include JBDS source zip on tools.jboss.org download page
- Closed
-
JBDS-3598 Error while building Jboss developer studio 9.1.0 Beta 2 from source
- Closed