On 9 February 2011 14:28, Brian Fox <bri...@infinity.nu> wrote: > Here's a workaround in the meantime: > http://svn.apache.org/viewvc/maven/pom/trunk/asf/pom.xml?p2=%2Fmaven%2Fpom%2Ftrunk%2Fasf%2Fpom.xml&p1=%2Fmaven%2Fpom%2Ftrunk%2Fasf%2Fpom.xml&r1=1065778&r2=1065777&view=diff&pathrev=1065778 > > On Wed, Feb 9, 2011 at 9:12 AM, John Patrick <nhoj.patr...@gmail.com> wrote: >> Hi, >> >> I believe this is the right mailing list, but please send me else where if >> not. >> >> I would like to request that a new profile activation type be added, >> which is based upon the maven version that is executing. What are >> people version upon this change? >> >> Base Ground >> ---- >> I've just done an upgrade from maven 2 to maven 3, it was a staggered >> upgrade so not all developers where done at the same time, as well as >> upgrading to maven 3 did not break anything. I had to create two >> profiles which contained version properties to use respectively. One >> issues was developer where using the wrong profile, or missing >> profile. >> >> >> >> e.g. >> >> <project xmlns="http://maven.apache.org/POM/4.0.0" >> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" >> xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 >> http://maven.apache.org/xsd/maven-4.0.0.xsd"> >> ... >> <profiles> >> ... >> <profile> >> <id>maven2-profile</id> >> <activation> >> <maven>2+</maven> >> ... >> <profile> >> <id>maven3-profile</id> >> <activation> >> <maven>3+</maven> >> ... >> >> So you can define which maven version to activate on, using a regex >> type pattern. >> e.g. >> --- 3+ maven version 3 or newer >> --- 3.0.1 specifically maven version 3.0.1 >> >> What are peoples views on this change, I realize that maven >> prerequisites exists but that is a hard limit, where as maven 2 to 3 >> you needed different plugin version and everything still worked okay. >> >> Cheers, >> John >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org >> For additional commands, e-mail: dev-h...@maven.apache.org >> >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > >
Cheers, Voted, I thought there would be an issue raised already. Just couldn't find the jira project it might be in. John --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org