If you have a super pom that all your projects inherit from then this solution is workable. You probably want one so that your organization can configure things like the enforcer plugin to make sure all your projects follow the same rules. But if you can't do that then this solution doesn't work very well.

Ralph

Stephen Connolly wrote:
It's a hack when 95% of people have need for these changes and
everyone does it differently and then we're back to the bad parts of
ANT...
(IMHO what is wrong with ant is that everyone has a completely
different build.xml and you need to figure it out every time.)

On Dec 21, 2007 8:40 AM, nicolas de loof <[EMAIL PROTECTED]> wrote:
I agree with brett.
POM properties can be used as shortcut for plugins configuration, to enable
profiles or for such use cases. They are not hacks.


2007/12/21, Brett Porter <[EMAIL PROTECTED]>:

If you document it for the users of the build, I wouldn't consider
that a hack :)

On 21/12/2007, at 7:34 PM, Stephen Connolly wrote:

That's hacking your pom.xml, and hacks are bad ;-)

On Dec 21, 2007 6:51 AM, Brett Porter <[EMAIL PROTECTED]> wrote:
There's always the one shot:

<artifactId>maven-surefire-configuration</artifactId>
<configuration>
  <skipExec>${cheat}</skipExec>
</configuration>

...

<properties>
  <cheat>false</cheat>
</properties>

...

then:
mvn -Dcheat=true test


On 21/12/2007, at 5:46 PM, Stephen Connolly wrote:

cool.

It's not just me, but hoards of developers who's hands will now be
saved from RSI due to excessive typing

;-)

On Dec 21, 2007 3:35 AM, Dan Fabulich <[EMAIL PROTECTED]> wrote:
Stephen Connolly wrote:

Can we make the property shorter and easier to remember...

that's what I liked about the -Dtest=0 hack
Just for you, I've filed SUREFIRE-417 (Make new "skipTests"
parameter to
replace skipExec). ;-)

I've got to fix SUREFIRE-416 anyway, and I'd forgotten that this
has
always bothered me. :-)

"mvn -DskipTests" is short enough, right?  I thought about making
it
"skipTest" but I thought it might sound like we were skipping the
entire
"test" lifecycle phase...?


-Dan

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to