[JBoss JIRA] (JBIDE-10671) [performance tuning] create separate jbosstools-nightly-staging-composite site for SOA Tooling
8:51 a.m.
Nick Boldt created JBIDE-10671:
----------------------------------
Summary: [performance tuning] create separate
jbosstools-nightly-staging-composite site for SOA Tooling
Key: JBIDE-10671
URL: https://issues.jboss.org/browse/JBIDE-10671
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Build/Releng, updatesite
Affects Versions: 3.3.0.Beta1
Reporter: Nick Boldt
Assignee: Douglas Palmer
Fix For: 3.3.0.Beta1
To speed up SOA Tooling aggregate build, source from a new URL instead of
http://download.jboss.org/jbosstools/builds/staging/_composite_/trunk/. This would mean no
metadata for content that will ultimately not be included in the site will be downloaded
-- only metadata for staged SOA nightlies will be read/used.
--
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
8:53 a.m.
[
https://issues.jboss.org/browse/JBIDE-10671?page=com.atlassian.jira.plugi...
]
Nick Boldt updated JBIDE-10671:
-------------------------------
Description:
To speed up SOA Tooling aggregate build, source from a new URL instead of
http://download.jboss.org/jbosstools/builds/staging/_composite_/trunk/. This would mean no
metadata for content that will ultimately not be included in the site will be downloaded
-- only metadata for staged SOA nightlies will be read/used.
1. create new site
http://download.jboss.org/jbosstools/builds/staging/_composite_/soa/trunk/ or similar
(need two sites for use with trunk and stable_branch)
2. Add new propert(ies) to parent pom.xml (to complement
jbosstools-nightly-staging-composite)
3. Replace reference to jbosstools-nightly-staging-composite in
build/aggregate/soa-site/pom.xml with new URL
4. respin to verify
was:To speed up SOA Tooling aggregate build, source from a new URL instead of
http://download.jboss.org/jbosstools/builds/staging/_composite_/trunk/. This would mean no
metadata for content that will ultimately not be included in the site will be downloaded
-- only metadata for staged SOA nightlies will be read/used.
[performance tuning] create separate
jbosstools-nightly-staging-composite site for SOA Tooling
-----------------------------------------------------------------------------------------------
Key: JBIDE-10671
URL: https://issues.jboss.org/browse/JBIDE-10671
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Build/Releng, updatesite
Affects Versions: 3.3.0.Beta1
Reporter: Nick Boldt
Assignee: Douglas Palmer
Fix For: 3.3.0.Beta1
To speed up SOA Tooling aggregate build, source from a new URL instead of
http://download.jboss.org/jbosstools/builds/staging/_composite_/trunk/. This would mean no
metadata for content that will ultimately not be included in the site will be downloaded
-- only metadata for staged SOA nightlies will be read/used.
1. create new site
http://download.jboss.org/jbosstools/builds/staging/_composite_/soa/trunk/ or similar
(need two sites for use with trunk and stable_branch)
2. Add new propert(ies) to parent pom.xml (to complement
jbosstools-nightly-staging-composite)
3. Replace reference to jbosstools-nightly-staging-composite in
build/aggregate/soa-site/pom.xml with new URL
4. respin to verify
--
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
9:03 a.m.
[
https://issues.jboss.org/browse/JBIDE-10671?page=com.atlassian.jira.plugi...
]
Nick Boldt updated JBIDE-10671:
-------------------------------
Description:
To speed up SOA Tooling aggregate build, source from a new URL instead of
http://download.jboss.org/jbosstools/builds/staging/_composite_/trunk/. This would mean no
metadata for content that will ultimately not be included in the site will be downloaded
-- only metadata for staged SOA nightlies will be read/used.
1. create new site
http://download.jboss.org/jbosstools/builds/staging/_composite_/soa/trunk/ or similar
(need two sites for use with trunk and stable_branch)
2. Add new propert(ies) to parent pom.xml (to complement
jbosstools-nightly-staging-composite)
3. Replace reference to jbosstools-nightly-staging-composite in
build/aggregate/soa-site/pom.xml with new URL
4. Ensure that build/aggregate/soa-site/pom.xml can find published URL of correct nightly
JBT Core site (for trunk or stable_branch), eg.,
http://download.jboss.org/jbosstools/updates/nightly/core/trunk/ or
http://download.jboss.org/jbosstools/updates/nightly/core/3.3.indigo/ -- needed to resolve
dependencies to common components in JBT Core or the SOA site won't be able to
build/resolve/get installed.
5. respin to verify
was:
To speed up SOA Tooling aggregate build, source from a new URL instead of
http://download.jboss.org/jbosstools/builds/staging/_composite_/trunk/. This would mean no
metadata for content that will ultimately not be included in the site will be downloaded
-- only metadata for staged SOA nightlies will be read/used.
1. create new site
http://download.jboss.org/jbosstools/builds/staging/_composite_/soa/trunk/ or similar
(need two sites for use with trunk and stable_branch)
2. Add new propert(ies) to parent pom.xml (to complement
jbosstools-nightly-staging-composite)
3. Replace reference to jbosstools-nightly-staging-composite in
build/aggregate/soa-site/pom.xml with new URL
4. respin to verify
[performance tuning] create separate
jbosstools-nightly-staging-composite site for SOA Tooling
-----------------------------------------------------------------------------------------------
Key: JBIDE-10671
URL: https://issues.jboss.org/browse/JBIDE-10671
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Build/Releng, updatesite
Affects Versions: 3.3.0.Beta1
Reporter: Nick Boldt
Assignee: Douglas Palmer
Fix For: 3.3.0.Beta1
To speed up SOA Tooling aggregate build, source from a new URL instead of
http://download.jboss.org/jbosstools/builds/staging/_composite_/trunk/. This would mean no
metadata for content that will ultimately not be included in the site will be downloaded
-- only metadata for staged SOA nightlies will be read/used.
1. create new site
http://download.jboss.org/jbosstools/builds/staging/_composite_/soa/trunk/ or similar
(need two sites for use with trunk and stable_branch)
2. Add new propert(ies) to parent pom.xml (to complement
jbosstools-nightly-staging-composite)
3. Replace reference to jbosstools-nightly-staging-composite in
build/aggregate/soa-site/pom.xml with new URL
4. Ensure that build/aggregate/soa-site/pom.xml can find published URL of correct nightly
JBT Core site (for trunk or stable_branch), eg.,
http://download.jboss.org/jbosstools/updates/nightly/core/trunk/ or
http://download.jboss.org/jbosstools/updates/nightly/core/3.3.indigo/ -- needed to resolve
dependencies to common components in JBT Core or the SOA site won't be able to
build/resolve/get installed.
5. respin to verify
--
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
9:13 a.m.
[
https://issues.jboss.org/browse/JBIDE-10671?page=com.atlassian.jira.plugi...
]
Nick Boldt updated JBIDE-10671:
-------------------------------
Attachment: soa-site.build.txt
Log of build of soa-site (without SwitchYard). Shows what's downloaded (metadata,
plugins, features) and from where.
[performance tuning] create separate
jbosstools-nightly-staging-composite site for SOA Tooling
-----------------------------------------------------------------------------------------------
Key: JBIDE-10671
URL: https://issues.jboss.org/browse/JBIDE-10671
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Build/Releng, updatesite
Affects Versions: 3.3.0.Beta1
Reporter: Nick Boldt
Assignee: Douglas Palmer
Fix For: 3.3.0.Beta1
Attachments: soa-site.build.txt
To speed up SOA Tooling aggregate build, source from a new URL instead of
http://download.jboss.org/jbosstools/builds/staging/_composite_/trunk/. This would mean no
metadata for content that will ultimately not be included in the site will be downloaded
-- only metadata for staged SOA nightlies will be read/used.
1. create new site
http://download.jboss.org/jbosstools/builds/staging/_composite_/soa/trunk/ or similar
(need two sites for use with trunk and stable_branch)
2. Add new propert(ies) to parent pom.xml (to complement
jbosstools-nightly-staging-composite)
3. Replace reference to jbosstools-nightly-staging-composite in
build/aggregate/soa-site/pom.xml with new URL
4. Ensure that build/aggregate/soa-site/pom.xml can find published URL of correct nightly
JBT Core site (for trunk or stable_branch), eg.,
http://download.jboss.org/jbosstools/updates/nightly/core/trunk/ or
http://download.jboss.org/jbosstools/updates/nightly/core/3.3.indigo/ -- needed to resolve
dependencies to common components in JBT Core or the SOA site won't be able to
build/resolve/get installed.
5. respin to verify
--
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
9:15 a.m.
[
https://issues.jboss.org/browse/JBIDE-10671?page=com.atlassian.jira.plugi...
]
Nick Boldt edited comment on JBIDE-10671 at 1/19/12 10:14 AM:
--------------------------------------------------------------
Log of build of soa-site (without SwitchYard). Shows what's downloaded (metadata,
plugins, features) and from where.
Can also read logs from Jenkins builds here:
http://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_trunk.soa-tooling.ag... (and
here: http://hudson.qa.jboss.com/hudson/job/devstudio-5.0_trunk.soa-tooling.upd...)
was (Author: nickboldt):
Log of build of soa-site (without SwitchYard). Shows what's downloaded (metadata,
plugins, features) and from where.
[performance tuning] create separate
jbosstools-nightly-staging-composite site for SOA Tooling
-----------------------------------------------------------------------------------------------
Key: JBIDE-10671
URL: https://issues.jboss.org/browse/JBIDE-10671
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Build/Releng, updatesite
Affects Versions: 3.3.0.Beta1
Reporter: Nick Boldt
Assignee: Douglas Palmer
Fix For: 3.3.0.Beta1
Attachments: soa-site.build.txt
To speed up SOA Tooling aggregate build, source from a new URL instead of
http://download.jboss.org/jbosstools/builds/staging/_composite_/trunk/. This would mean no
metadata for content that will ultimately not be included in the site will be downloaded
-- only metadata for staged SOA nightlies will be read/used.
1. create new site
http://download.jboss.org/jbosstools/builds/staging/_composite_/soa/trunk/ or similar
(need two sites for use with trunk and stable_branch)
2. Add new propert(ies) to parent pom.xml (to complement
jbosstools-nightly-staging-composite)
3. Replace reference to jbosstools-nightly-staging-composite in
build/aggregate/soa-site/pom.xml with new URL
4. Ensure that build/aggregate/soa-site/pom.xml can find published URL of correct nightly
JBT Core site (for trunk or stable_branch), eg.,
http://download.jboss.org/jbosstools/updates/nightly/core/trunk/ or
http://download.jboss.org/jbosstools/updates/nightly/core/3.3.indigo/ -- needed to resolve
dependencies to common components in JBT Core or the SOA site won't be able to
build/resolve/get installed.
5. respin to verify
--
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
3:01 p.m.
[
https://issues.jboss.org/browse/JBIDE-10671?page=com.atlassian.jira.plugi...
]
Nick Boldt updated JBIDE-10671:
-------------------------------
Attachment: soa-site.build2.txt
second build log -- you'll notice that while the metadata is fetched again, very few
actual plugins/features are this time. Because they're all in the ~/.m2 cache so
there's no need. Working as designed. :)
[performance tuning] create separate
jbosstools-nightly-staging-composite site for SOA Tooling
-----------------------------------------------------------------------------------------------
Key: JBIDE-10671
URL: https://issues.jboss.org/browse/JBIDE-10671
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Build/Releng, updatesite
Affects Versions: 3.3.0.Beta1
Reporter: Nick Boldt
Assignee: Douglas Palmer
Fix For: 3.3.0.Beta1
Attachments: soa-site.build.txt, soa-site.build2.txt
To speed up SOA Tooling aggregate build, source from a new URL instead of
http://download.jboss.org/jbosstools/builds/staging/_composite_/trunk/. This would mean no
metadata for content that will ultimately not be included in the site will be downloaded
-- only metadata for staged SOA nightlies will be read/used.
1. create new site
http://download.jboss.org/jbosstools/builds/staging/_composite_/soa/trunk/ or similar
(need two sites for use with trunk and stable_branch)
2. Add new propert(ies) to parent pom.xml (to complement
jbosstools-nightly-staging-composite)
3. Replace reference to jbosstools-nightly-staging-composite in
build/aggregate/soa-site/pom.xml with new URL
4. Ensure that build/aggregate/soa-site/pom.xml can find published URL of correct nightly
JBT Core site (for trunk or stable_branch), eg.,
http://download.jboss.org/jbosstools/updates/nightly/core/trunk/ or
http://download.jboss.org/jbosstools/updates/nightly/core/3.3.indigo/ -- needed to resolve
dependencies to common components in JBT Core or the SOA site won't be able to
build/resolve/get installed.
5. respin to verify
--
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
8:12 a.m.
[
https://issues.jboss.org/browse/JBIDE-10671?page=com.atlassian.jira.plugi...
]
Nick Boldt commented on JBIDE-10671:
------------------------------------
BTW, you can also force maven to run in offline mode, resolving exclusively from the local
~/.m2 cache:
mvn clean install -o
[performance tuning] create separate
jbosstools-nightly-staging-composite site for SOA Tooling
-----------------------------------------------------------------------------------------------
Key: JBIDE-10671
URL: https://issues.jboss.org/browse/JBIDE-10671
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Build/Releng, updatesite
Affects Versions: 3.3.0.Beta1
Reporter: Nick Boldt
Assignee: Douglas Palmer
Fix For: 3.3.0.Beta1
Attachments: soa-site.build.txt, soa-site.build2.txt
To speed up SOA Tooling aggregate build, source from a new URL instead of
http://download.jboss.org/jbosstools/builds/staging/_composite_/trunk/. This would mean no
metadata for content that will ultimately not be included in the site will be downloaded
-- only metadata for staged SOA nightlies will be read/used.
1. create new site
http://download.jboss.org/jbosstools/builds/staging/_composite_/soa/trunk/ or similar
(need two sites for use with trunk and stable_branch)
2. Add new propert(ies) to parent pom.xml (to complement
jbosstools-nightly-staging-composite)
3. Replace reference to jbosstools-nightly-staging-composite in
build/aggregate/soa-site/pom.xml with new URL
4. Ensure that build/aggregate/soa-site/pom.xml can find published URL of correct nightly
JBT Core site (for trunk or stable_branch), eg.,
http://download.jboss.org/jbosstools/updates/nightly/core/trunk/ or
http://download.jboss.org/jbosstools/updates/nightly/core/3.3.indigo/ -- needed to resolve
dependencies to common components in JBT Core or the SOA site won't be able to
build/resolve/get installed.
5. respin to verify
--
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
11:18 p.m.
[
https://issues.jboss.org/browse/JBIDE-10671?page=com.atlassian.jira.plugi...
]
Nick Boldt commented on JBIDE-10671:
------------------------------------
In addition to the various component sites (bpel, drools, esb, jbpm, modeshape, teiid), I
think the new soa nightly staging site
[http://download.jboss.org/jbosstools/builds/staging/_composite_/soa-tooli...]
should composite in the latest stable'ish nightly trunk/branch core site
[http://download.jboss.org/jbosstools/updates/core/trunk/] too. That way you'll get
the bits in the JBT Core upstream rather than the more-churny stuff in
http://download.jboss.org/jbosstools/builds/staging/_composite_/trunk/.
Make sense?
[performance tuning] create separate
jbosstools-nightly-staging-composite site for SOA Tooling
-----------------------------------------------------------------------------------------------
Key: JBIDE-10671
URL: https://issues.jboss.org/browse/JBIDE-10671
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Build/Releng, updatesite
Affects Versions: 3.3.0.Beta1
Reporter: Nick Boldt
Assignee: Douglas Palmer
Fix For: 3.3.0.Beta1
Attachments: soa-site.build.txt, soa-site.build2.txt
To speed up SOA Tooling aggregate build, source from a new URL instead of
http://download.jboss.org/jbosstools/builds/staging/_composite_/trunk/. This would mean no
metadata for content that will ultimately not be included in the site will be downloaded
-- only metadata for staged SOA nightlies will be read/used.
1. create new site
http://download.jboss.org/jbosstools/builds/staging/_composite_/soa/trunk/ or similar
(need two sites for use with trunk and stable_branch)
2. Add new propert(ies) to parent pom.xml (to complement
jbosstools-nightly-staging-composite)
3. Replace reference to jbosstools-nightly-staging-composite in
build/aggregate/soa-site/pom.xml with new URL
4. Ensure that build/aggregate/soa-site/pom.xml can find published URL of correct nightly
JBT Core site (for trunk or stable_branch), eg.,
http://download.jboss.org/jbosstools/updates/nightly/core/trunk/ or
http://download.jboss.org/jbosstools/updates/nightly/core/3.3.indigo/ -- needed to resolve
dependencies to common components in JBT Core or the SOA site won't be able to
build/resolve/get installed.
5. respin to verify
--
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
1:37 p.m.
[
https://issues.jboss.org/browse/JBIDE-10671?page=com.atlassian.jira.plugi...
]
Nick Boldt resolved JBIDE-10671.
--------------------------------
Assignee: Nick Boldt (was: Douglas Palmer)
Resolution: Done
New sites:
http://download.jboss.org/jbosstools/builds/staging/_composite_/core/trunk/
http://download.jboss.org/jbosstools/builds/staging/_composite_/core/3.3....
http://download.jboss.org/jbosstools/builds/staging/_composite_/soa-tooli...
http://download.jboss.org/jbosstools/builds/staging/_composite_/soa-tooli...
Closing.
[performance tuning] create separate
jbosstools-nightly-staging-composite site for SOA Tooling
-----------------------------------------------------------------------------------------------
Key: JBIDE-10671
URL: https://issues.jboss.org/browse/JBIDE-10671
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Build/Releng, updatesite
Affects Versions: 3.3.0.Beta1
Reporter: Nick Boldt
Assignee: Nick Boldt
Fix For: 3.3.0.Beta1
Attachments: soa-site.build.txt, soa-site.build2.txt
To speed up SOA Tooling aggregate build, source from a new URL instead of
http://download.jboss.org/jbosstools/builds/staging/_composite_/trunk/. This would mean no
metadata for content that will ultimately not be included in the site will be downloaded
-- only metadata for staged SOA nightlies will be read/used.
1. create new site
http://download.jboss.org/jbosstools/builds/staging/_composite_/soa/trunk/ or similar
(need two sites for use with trunk and stable_branch)
2. Add new propert(ies) to parent pom.xml (to complement
jbosstools-nightly-staging-composite)
3. Replace reference to jbosstools-nightly-staging-composite in
build/aggregate/soa-site/pom.xml with new URL
4. Ensure that build/aggregate/soa-site/pom.xml can find published URL of correct nightly
JBT Core site (for trunk or stable_branch), eg.,
http://download.jboss.org/jbosstools/updates/nightly/core/trunk/ or
http://download.jboss.org/jbosstools/updates/nightly/core/3.3.indigo/ -- needed to resolve
dependencies to common components in JBT Core or the SOA site won't be able to
build/resolve/get installed.
5. respin to verify
--
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
9:59 a.m.
[
https://issues.jboss.org/browse/JBIDE-10671?page=com.atlassian.jira.plugi...
]
Vlado Pakan commented on JBIDE-10671:
-------------------------------------
Nick could you please verify and close this Jira? I'm not able to do it.
[performance tuning] create separate
jbosstools-nightly-staging-composite site for SOA Tooling
-----------------------------------------------------------------------------------------------
Key: JBIDE-10671
URL: https://issues.jboss.org/browse/JBIDE-10671
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Build/Releng, updatesite
Affects Versions: 3.3.0.Beta1
Reporter: Nick Boldt
Assignee: Nick Boldt
Fix For: 3.3.0.Beta1
Attachments: soa-site.build.txt, soa-site.build2.txt
To speed up SOA Tooling aggregate build, source from a new URL instead of
http://download.jboss.org/jbosstools/builds/staging/_composite_/trunk/. This would mean no
metadata for content that will ultimately not be included in the site will be downloaded
-- only metadata for staged SOA nightlies will be read/used.
1. create new site
http://download.jboss.org/jbosstools/builds/staging/_composite_/soa/trunk/ or similar
(need two sites for use with trunk and stable_branch)
2. Add new propert(ies) to parent pom.xml (to complement
jbosstools-nightly-staging-composite)
3. Replace reference to jbosstools-nightly-staging-composite in
build/aggregate/soa-site/pom.xml with new URL
4. Ensure that build/aggregate/soa-site/pom.xml can find published URL of correct nightly
JBT Core site (for trunk or stable_branch), eg.,
http://download.jboss.org/jbosstools/updates/nightly/core/trunk/ or
http://download.jboss.org/jbosstools/updates/nightly/core/3.3.indigo/ -- needed to resolve
dependencies to common components in JBT Core or the SOA site won't be able to
build/resolve/get installed.
5. respin to verify
--
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
10:05 a.m.
[
https://issues.jboss.org/browse/JBIDE-10671?page=com.atlassian.jira.plugi...
]
Nick Boldt closed JBIDE-10671.
------------------------------
Sorry, I must have clicked Resolve instead of Close. Closing.
[performance tuning] create separate
jbosstools-nightly-staging-composite site for SOA Tooling
-----------------------------------------------------------------------------------------------
Key: JBIDE-10671
URL: https://issues.jboss.org/browse/JBIDE-10671
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Build/Releng, updatesite
Affects Versions: 3.3.0.Beta1
Reporter: Nick Boldt
Assignee: Nick Boldt
Fix For: 3.3.0.Beta1
Attachments: soa-site.build.txt, soa-site.build2.txt
To speed up SOA Tooling aggregate build, source from a new URL instead of
http://download.jboss.org/jbosstools/builds/staging/_composite_/trunk/. This would mean no
metadata for content that will ultimately not be included in the site will be downloaded
-- only metadata for staged SOA nightlies will be read/used.
1. create new site
http://download.jboss.org/jbosstools/builds/staging/_composite_/soa/trunk/ or similar
(need two sites for use with trunk and stable_branch)
2. Add new propert(ies) to parent pom.xml (to complement
jbosstools-nightly-staging-composite)
3. Replace reference to jbosstools-nightly-staging-composite in
build/aggregate/soa-site/pom.xml with new URL
4. Ensure that build/aggregate/soa-site/pom.xml can find published URL of correct nightly
JBT Core site (for trunk or stable_branch), eg.,
http://download.jboss.org/jbosstools/updates/nightly/core/trunk/ or
http://download.jboss.org/jbosstools/updates/nightly/core/3.3.indigo/ -- needed to resolve
dependencies to common components in JBT Core or the SOA site won't be able to
build/resolve/get installed.
5. respin to verify
--
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
5133
days inactive
5188
days old
jbosstools-issues@lists.jboss.org
10 comments
2 participants
participants (2)
-
Nick Boldt (JIRA) -
Vlado Pakan (JIRA)