Are you saying we should do this?
rm -f pom.xml
mv pom-core.xml pom.xml
The only reason why this should be it is that you want to be able to check out that
build/pom.xml on its own.
What I want to avoid is we have 3 pom.xml files that is 80-90% same content. That is mess
to maintain/understand/use.
/max
These are used by
http://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_trunk.tests/
http://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_trunk.continuous/
http://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_trunk.soa-tooling.te...
http://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_trunk.soa-tooling.co...
(and matching 4 other jobs in 3.3x branch, s/trunk/stable_branch/ in the
above URLs)
On 03/22/2012 10:17 AM, Max Rydahl Andersen wrote:
> They seem to have 80% the same content.
>
> Why are there three ?
>
> Why not just one and then soa moves somewhere else with just their needed setup ?
>
> /max
>
>
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/jbosstools-dev
--
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio
http://nick.divbyzero.com
_______________________________________________
jbosstools-dev mailing list
jbosstools-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbosstools-dev