12:38 a.m.
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
3:04 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-6493) pi4soa build issues
[
https://jira.jboss.org/browse/JBIDE-6493?page=com.atlassian.jira.plugin.s...
]
Gary Brown commented on JBIDE-6493:
-----------------------------------
1) It probably would be a good idea to add a pi4soa component and enable those issues to
be assigned to me.
2) My fault - I did not bump up the version after 3.0.x was branched - will do this
today.
I assume the 3.1.x maintenance stream is built from the 3.0.x branch? If so, I need to
apply the fixes for Jeff there - when does the next maintenance build get published?
3) Sounds good to me - is this something you can do Nick? as I am still
learning/experimenting with Tycho on Savara.
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
3:23 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-6493) pi4soa build issues
[
https://jira.jboss.org/browse/JBIDE-6493?page=com.atlassian.jira.plugin.s...
]
Max Rydahl Andersen commented on JBIDE-6493:
--------------------------------------------
1) I added pi4soa component with you as lead
2) why should 3.1.x be from 3.0.x branch ? JBoss Tools 3.1.x is in 3.1.x branch :) or are
you mixing JBDS versions with JBT ? And what fixes for Jeff are we talking about ? New
features should be in trunk, right ?
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
3:30 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-6493) pi4soa build issues
[
https://jira.jboss.org/browse/JBIDE-6493?page=com.atlassian.jira.plugin.s...
]
Gary Brown commented on JBIDE-6493:
-----------------------------------
Thanks for adding the component.
Sorry I was not clear - from the pi4soa-3.0.x branch, and yes we are only talking about
bug fixes.
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
5:18 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-6493) pi4soa build issues
[
https://jira.jboss.org/browse/JBIDE-6493?page=com.atlassian.jira.plugin.s...
]
Gary Brown commented on JBIDE-6493:
-----------------------------------
(2) - trunk updated to 3.1.0 now - apart from the plugin/feature manifests, I also updated
the version property in the releng/build.properties* files.
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
10:24 a.m.
New subject: [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:
-----------------------------------
re: 3 - Athena build now publishing to here
http://download.jboss.org/jbosstools/builds/nightly/3.2.helios/
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
10:32 a.m.
New subject: [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:
-----------------------------------
re: version confusion
JBT 3.1.x contains pi4soa 3.0.0.x (maintenance) --
http://hudson.qa.jboss.com/hudson/view/DevStudio/job/jbosstools-cbi-pi4so... (update
site/zip are not published, only aggregated into JBT)
JBT 3.2 contains pi4soa 3.1 (trunk) --
http://hudson.qa.jboss.com/hudson/view/DevStudio/job/jbosstools-cbi-pi4soa/ (update
site/zip ARE published)
Regarding when pi4soa 3.0.x maintenance fixes get into JBT 3.1.x maintenance... depends on
*if we do another maintenance build* (JBDS 3.0.2 / JBT 3.1.2). If we don't then they
won't, and you'll have to publish your bits another way (eg., I could manually add
your update site zip to https://www.jboss.org/tools/download/stable/3_1_GA.html -- if this
is the case then *please be sure to nag me* about this if you don't see your bits
published!)
---
re: switching from Athena to Tycho
Yes, I can do that; however, with the update site now being published there's less
urgency there IMHO. If having a working Tycho build for pi4soa would help you with Savara
development, then perhaps this is still important.
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
11:06 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-6493) pi4soa build issues
[
https://jira.jboss.org/browse/JBIDE-6493?page=com.atlassian.jira.plugin.s...
]
Gary Brown commented on JBIDE-6493:
-----------------------------------
Hi Nick
In terms of manually adding the update site zip, I think this may cause confusion, as the
page implies that the contents of the individual zips are in the main 3.1.1.GA release.
Are the nightly builds for JBT 3.1.x still running? If so, maybe having access to the
fixes via the nightly builds may be good enough. Jeff what do you think?
I assume the benefit of having the Tycho build for pi4soa would be that the plugins would
be published to a maven repo, that can then be used by the Savara Tycho build to more
easily obtain the dependencies. In which case, it would be very useful :) It might be a
good time to restructure trunk along the lines outlined by Max, i.e.
plugins/features/tests/site.
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
1:23 p.m.
New subject: [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:
-----------------------------------
My point w/ the download page listing the pi4soa update site is that the only way to get
pi4soa is via the JBT update site or zip; there's no smaller download option than the
whole all-in-one site. So if you wanted a separate zip for pi4soa, that could be added.
And yes, 3.1.x is still running but there's no scheduled 3.1.2 release yet.
Tycho builds give you a better offline / local build experience and does dependency
resolution better than Athena/PDE. Yes, there's the option to publish to a maven/nexus
repo; however, we are currently not allowed (license restriction) to publish anything into
a Nexus repo which will be aggregated into a product. Therefore if you want pi4soa as a
maven repo, it cannot be included in JBoss Developer Studio, only in Tools.
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
2:32 p.m.
New subject: [JBoss JIRA] Commented: (JBIDE-6493) pi4soa build issues
[
https://jira.jboss.org/browse/JBIDE-6493?page=com.atlassian.jira.plugin.s...
]
Gary Brown commented on JBIDE-6493:
-----------------------------------
Any thoughts on how the hudson jobs would resolve those dependencies? Would we need to
colocate the Savara builds with the pi4soa builds?
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
11:04 a.m.
New subject: [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:
-----------------------------------
Simple - you define p2 dependencies as either <repository>s in your parent pom.xml,
<repository>
<id>helios</id>
<url>http://download.eclipse.org/releases/helios/</url>
<layout>p2</layout>
<releases>
<enabled>true</enabled>
</releases>
</repository>
or as <repository>s in your .target platform definition file.
<location includeAllPlatforms="false" includeMode="planner"
type="InstallableUnit">
<repository location="http://download.eclipse.org/releases/helios/"/>
</location>
So, if each component builds separately and publishes its own update site, downstream
builds can then build against those URLs.
That said, yes, if you can build a few components together it'll be more efficient
(same shared maven/p2 deps won't have to be dl'd more than once).
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
9:29 a.m.
New subject: [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
9:34 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-6493) pi4soa build issues
[
https://jira.jboss.org/browse/JBIDE-6493?page=com.atlassian.jira.plugin.s...
]
Gary Brown commented on JBIDE-6493:
-----------------------------------
Yes I'm happy with the new job. Thanks.
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
4:42 p.m.
New subject: [JBoss JIRA] Updated: (JBIDE-6493) pi4soa build issues
[
https://jira.jboss.org/browse/JBIDE-6493?page=com.atlassian.jira.plugin.s...
]
Nick Boldt updated JBIDE-6493:
------------------------------
Component/s: pi4soa
(was: Build/Releng)
pi4soa build issues
-------------------
Key: JBIDE-6493
URL: https://jira.jboss.org/browse/JBIDE-6493
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: pi4soa
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
6:30 p.m.
New subject: [JBoss JIRA] Resolved: (JBIDE-6493) pi4soa build issues
[
https://jira.jboss.org/browse/JBIDE-6493?page=com.atlassian.jira.plugin.s...
]
Nick Boldt resolved JBIDE-6493.
-------------------------------
Fix Version/s: 3.2.0.M1
Resolution: Done
Moved into pi4soa component; still can't assign to Gary though. *shrug*
Job linked to JBT build aggregator. If you're curious about all the respins, it's
cuz pi4soa is a fast build which lets me quickly test hudson integration/publishing.
pi4soa build issues
-------------------
Key: JBIDE-6493
URL: https://jira.jboss.org/browse/JBIDE-6493
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: pi4soa
Affects Versions: 3.2.0.M2
Reporter: Nick Boldt
Assignee: Nick Boldt
Priority: Minor
Fix For: 3.2.0.M1
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
12:59 a.m.
New subject: [JBoss JIRA] Updated: (JBIDE-6493) pi4soa build issues
[
https://jira.jboss.org/browse/JBIDE-6493?page=com.atlassian.jira.plugin.s...
]
Max Rydahl Andersen updated JBIDE-6493:
---------------------------------------
Assignee: (was: Nick Boldt)
pi4soa build issues
-------------------
Key: JBIDE-6493
URL: https://jira.jboss.org/browse/JBIDE-6493
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: pi4soa
Affects Versions: 3.2.0.M2
Reporter: Nick Boldt
Priority: Minor
Fix For: 3.2.0.M1
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
1:03 a.m.
New subject: [JBoss JIRA] Assigned: (JBIDE-6493) pi4soa build issues
[
https://jira.jboss.org/browse/JBIDE-6493?page=com.atlassian.jira.plugin.s...
]
Max Rydahl Andersen reassigned JBIDE-6493:
------------------------------------------
Assignee: Gary Brown
pi4soa build issues
-------------------
Key: JBIDE-6493
URL: https://jira.jboss.org/browse/JBIDE-6493
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: pi4soa
Affects Versions: 3.2.0.M2
Reporter: Nick Boldt
Assignee: Gary Brown
Priority: Minor
Fix For: 3.2.0.M1
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
5744
days inactive
5772
days old
jbosstools-issues@lists.jboss.org
16 comments
3 participants
participants (3)
-
Gary Brown (JIRA) -
Max Rydahl Andersen (JIRA)
-
Nick Boldt (JIRA)