To elaborate, here's an example:
https://github.com/jbosstools/jbosstools-bpel/blob/master/pom.xml
If you had these projects checked out:
~/jbt41/jbosstools-bpel
~/jbt41/jbosstools-server
~/jbt41/jbosstools-base
you could run a build of bpel + server + base like this:
mvn install -Pbootstrap
However, if you run the tycho-versions plugin to bump your
plugins/features to a newer version, it will (currently) try to also
upversion everything in server and base, even if you only meant bpel.
mvn -Dtycho.mode=maven
org.sonatype.tycho:tycho-versions-plugin:set-version
-DnewVersion=4.5.6-SNAPSHOT
---
So, since they're in conflict, we're wondering which usecase is more
important -- using the tycho-versions plugin, or using the bootstrap
profile.
Cheers,
Nick
On 01/30/2013 11:55 AM, Mickael Istria wrote:
Hi all,
We've wondered whether these bootstrap profiles have been used/useful.
As we are not convinced of their added-value, we've been thinking about
removing them. But we won't do it without your permission ;)
Who uses bootstrap profiles during build? Can you please describe your
use-cases?
Thanks!
--
Mickael Istria
Eclipse developer at JBoss, by Red Hat <
http://www.jboss.org/tools>
My blog <
http://mickaelistria.wordpress.com> - My Tweets
<
http://twitter.com/mickaelistria>
_______________________________________________
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