Not sure why parent pom have this change committed yet. Cleanup is still ongoing ;(
Anyways, SOA tools would be an *additional* site to add, right? not an Either-or in the
current nor future setup afaics from a build perspective.
/max
On 15 Nov 2012, at 08:57, Andrej Podhradsky <apodhrad(a)redhat.com> wrote:
Hi Nick,
I noticed your change in parent pom
<profile>
<id>jbosstools-nightly-staging-composite-soa-tooling</id>
<properties>
<!-- TODO: This SOA profile should be based on usage of a SOA-specific TP made of
unified + JBT -->
- <jbosstools-site>${jbosstools-nightly-staging-composite}</jbosstools-site>
- <jbosstools-tests-site>${jbosstools-nightly-staging-composite-soa-tooling}</jbosstools-tests-site>
+ <jbosstools-site>${jbosstools-nightly-staging-composite-soa-tooling}</jbosstools-site>
+ <jbosstools-tests-site>${jbosstools-nightly-soa-tooling-tests}</jbosstools-tests-site>
</properties>
</profile>
Yesterday me and Mickael discussed about this ;-) the impossibility of setting two
repositories (core + soa) using nightly profiles.
As I got to know, there will be a soa specific target platform (when?) so it was a
temporary solution. For me it is no problem to specify
the repo from command line but having this resolved in pom is always better.
Just wondering from where is build
http://download.jboss.org/jbosstools/updates/nightly/soatests/trunk?
Have a nice day!
--
Andrej Podhradsky
Quality Assurance Associate
JBoss SOA Platform
IRC: apodhrad at #jbossqa #jbosssoa #jbosssoaqa #devstudio-qa #brno
_______________________________________________
jbosstools-dev mailing list
jbosstools-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbosstools-dev