Re: [jbosstools-dev] Parent pom updated! Minimum/default target platform used in master branch (4.1/7.0) now points at Kepler M4 bits, with M5 coming next week; Juno&Kepler TPs will remove unneeded IUs next week

Mickael, how about we add a profile that does this: $ mvn verify -Phelp [info] Max, if you're trying to override the target platform version [info] use -DTARGET_PLATFORM_VERSION=x.yz.a.quality-SNAPSHOT, eg., [info] mvn verify -DTARGET_PLATFORM_VERSION=4.21.3.Final-SNAPSHOT or $ mvn verify -Phelp [info] Fetching a copy of the parent pom from master branch... [info] Opening parent pom in your default text editor so you can [info] `egrep -i "target|platform" and figure out the property [info] you need to override. :P -- Seriously, though, Max, if you can't remember that the maven/tycho variable for the target platform version is TARGET_PLATFORM_VERSION then making you memorize a new profile might not be the best solution. In fact, you only need to provide an override if the following two usecases don't work for you: a) you want the default minimum: mvn verify b) you want the default maximum mvn verify -Pmaximum Because, while the idea of having profiles for each and every TP stream is *somewhat* reasonable, it doesn't solve the usecase where there are multiple Juno SR0 based target platforms (eg., we have 4.20.5 now and will have 4.20.6 soon - do we have to update the parent pom every time there's a newer SR0 version created? And what if a user wants to use the previous one? -PJunoSR0.previous and -PJunoSR0 ? -PJunoSR0d and -PJunoSR0e ? Besides, the whole point of refactoring the GAVs for the TPs was to get AWAY from using names like JunoSR0 in favour of 4.20.x. --- component with a stable parent pom This is true, but we have some time here since M4/M5 are still under development. It's not until M7 that the bits are stable enough to be called .CR or .Final, or to remove the -SNAPSHOT suffix. So... all components, even if they're "done" this week, should be rebuilding w/ updated TPs all the way through M7 to verify they still work against the newer Kepler stuff. I've bumped https://issues.jboss.org/browse/JBIDE-13408 to Blocker, but I'm leaving it on Alpha2 for now. Cheers, Nick On 01/31/2013 08:43 AM, Max Rydahl Andersen wrote: -- Nick Boldt :: JBoss by Red Hat Productization Lead :: JBoss Tools & Dev Studio http://nick.divbyzero.com