On 11/15/2012 11:39 AM, Max Rydahl Andersen wrote:
Not sure why parent pom have this change committed yet. Cleanup is
still ongoing ;(
Max, we are doing this cleanup incrementally.
We cannot afford to change everything in one shot, push it to master and
expect everything will work. This cleanup is made of several sub-tasks,
we are trying to fix them one by one, and let time for developers and CI
to give feedback before we apply the next change.
So this is committed, and https://issues.jboss.org/browse/JBIDE-13014
was marked as DONE
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.
I'll negociate with Nick whether this commit should be reverted. IMHO,
it should be.
As a workaround, you can add
to your "mvn verify -P jbosstools-nightly-staging-composite-soa-tooling"
This issue is the consequence of a missing dedicated TP for SOA Tools
that would contain JBT as dependencies:
Eclipse developer at JBoss, by Red Hat <http://www.jboss.org/tools>
My blog <http://mickaelistria.wordpress.com>
- My Tweets