[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-6493) pi4soa build issues
[
https://jira.jboss.org/browse/JBIDE-6493?page=com.atlassian.jira.plugin.s...
]
Nick Boldt commented on JBIDE-6493:
-----------------------------------
OK, we now have a pi4soa build using Tycho.
* It does NOT include sources in the build.
* Instead of producing an update site that's 13M, it's only 4.2M.
* It is faster.
New Hudson Job:
http://hudson.qa.jboss.com/hudson/view/DevStudio_Tycho/job/jbosstools-pi4... (currently
disabled until JBT 3.2.0.M1 is released)
Old Hudson Job:
http://hudson.qa.jboss.com/hudson/view/DevStudio/job/jbosstools-cbi-pi4soa/ (currently
disabled but still works as backup)
New Output:
http://download.jboss.org/jbosstools/builds/nightly/3.2.helios/jbosstools...
Old Output:
http://download.jboss.org/jbosstools/builds/nightly/3.2.helios/jbosstools...
If you're happy with the new job + smaller update site, then I will hook up this new
site into the JBT aggregator build, and we'll be done w/ this JIRA.
Let me know, thx.
pi4soa build issues
-------------------
Key: JBIDE-6493
URL: https://jira.jboss.org/browse/JBIDE-6493
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Build/Releng
Affects Versions: 3.2.0.M2
Reporter: Nick Boldt
Assignee: Nick Boldt
Priority: Minor
1. Max, there is no component for pi4soa in JBIDE JIRA. Should one be added?
2. Gary, I cannot assign this to you. Max, should Gary be added to the viable options for
assignment?
2. Current version of pi4soa features/plugins is numbered greater than the version that
was released in JBT 3.1.1, yet the code in trunk is still 3.0.0. Should this be moved up
to 3.1.0 to distinguish new work for JBT 3.2 (Eclipse 3.6 Helios) it from the JBT 3.1.x
maintenance stream (Eclipse 3.5 Galileo)?
3. pi4soa build currently uses Athena and does not publish an update site outside of
Hudson. We should switch to Tycho and begin publishing bits to
http://download.jboss.org/jbosstools/builds/nightly/3.2.helios/
--
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