We've just had this problem pop up with a number of the plugins in the
CI system - though they are using the latest 2.4-SNAPSHOT.
I haven't had a chance to investigate yet, just thought I'd point it
out.
- Brett
On 21/12/2007, at 2:43 PM, Dan Fabulich wrote:
Jerome Lacoste wrote:
java.
Hey,
After your commit the assembly plugin started to fail for me again. when and
how is the aspect activated? I'm rather clueless regarding aspects so sorry
if that's obvious from code.
Milos
On Dec 17, 2007 9:04 PM, <[EMAIL PROTECTED]> wrote:
> Author: jdcasey
> Date: Mon Dec 17 12:04:45 2007
Hi,
Agree to start processing this.
If I can help I will.
--
Olivier
2007/12/20, Brett Porter <[EMAIL PROTECTED]>:
> So, what's next?
>
> This seems generally in favour - now might be a good time to get
> started on it?
>
> From past experience the steps would be:
> - poll the current maven com
2007/12/21, Stephen Connolly <[EMAIL PROTECTED]>:
>
> It's a hack when 95% of people have need for these changes
On those 95% many use the allready available maven.test.skip.exec, that is
ONLY a convenience way to skip tests, but this is NOT recommended. So what
is discussed here is only a shortc
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 wor
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
Yeah, except when they move onto a different project and are wondering
why it does not work any more... (so it's a hack and a hack is a hack.
now we are just left arguing over how many angels can dance on the
head of a pin)
At least SUREFIRE-417 will cure that problem.
If it walks like a duck, qu
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/20
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:
maven-surefi
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:
>
> maven-surefire-configuration
>
>${cheat}
>
>
> ...
>
>
>false
>
>
> ...
>
> then:
> mvn -Dcheat=true test
>
>
> On 21/12/2007, at 5:46
The Maven team is pleased to announce the release of the Maven Invoker Plugin,
version 1.1
http://maven.apache.org/plugins/maven-invoker-plugin/
You can run mvn -up to get the latest version of the plugin, or specify
the version in your project's plugin configuration:
org.apache.maven.plugins
11 matches
Mail list logo
