.
Clover is free for open source projects and may be trialled for 30
days for free.
Thanks again,
Nick Pellow
Atlassian Clover.
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h
Hi Ringo,
You will need to set the properties on the project object.
To get a project injected into your MOJO:
/**
* The Maven project instance for the executing project.
*
* pNote: This is passed by Maven and must not be configured by
the user./p
*
* @parameter
to the main project, but not the
transitively resolved projects.
It's always hard to tell from the output - is the resources call
in the forked lifecycle or the main one afterwards? The latter
would not retain all the settings.
- Brett
On 03/02/2009, at 4:08 PM, Nick Pellow wrote
to tell from the output - is the resources call in
the forked lifecycle or the main one afterwards? The latter would
not retain all the settings.
- Brett
On 03/02/2009, at 4:08 PM, Nick Pellow wrote:
You're right. the dependency artifacts are already transitive.
e.g. the -X output shows:
[DEBUG
to artifacts with a different or no classifier.
On 02/02/2009, at 5:44 PM, Nick Pellow wrote:
Hi,
The maven-clover2-plugin creates both a classified and a normal jar
artifact for each sub-module it builds.
I have a problem, where I am seeing both a classified _and_ a non-
classified artifact
).
- Brett
On 03/02/2009, at 12:14 PM, Nick Pellow wrote:
Thanks for the clarification, Brett.
What can the maven-clover2-plugin do to ensure that only classified
artifacts are resolved if they are available?
On 03/02/2009, at 9:17 AM, Brett Porter wrote:
Yes, that's expected - artifacts
you are seeing the results you are. Have you tracked the
output of the swizzling process? Does -X show what is then fed into
the compiler plugin in the forked lifecycle?
- Brett
On 03/02/2009, at 3:26 PM, Nick Pellow wrote:
Will the filtering be applied to the artifacts resolved
that will cause this?
Cheers,
Nick Pellow
Atlassian Clover.
being able to bind to the front and back of a lifecycle would be
absolutely
splendid
+1. A simple event system which fired build events to registered
listeners (plugins could register these) would go a long way. Example
events could be:
* Build Started
* Phase Started
* Goal Started
*
Hi Brett,
Hi,
I noticed that the 'aggregator' parameter for a MOJO is slated for
deprecation in a future release of Maven.
http://books.sonatype.com/maven-book/reference/writing-plugins.html#d0e22494
Seems presumptive on the part of the author. It has both its
usefulness and its
Hi,
I noticed that the 'aggregator' parameter for a MOJO is slated for
deprecation in a future release of Maven.
http://books.sonatype.com/maven-book/reference/writing-plugins.html#d0e22494
What should be used instead, to fulfill the following use-case:
- a multi-module project, which would
can't unset something like that because it appears null and the
merge will overwrite it. You could change it to something else though
--Brian (mobile)
On Oct 29, 2008, at 1:49 AM, Nick Pellow [EMAIL PROTECTED]
wrote:
Hi,
If a plugin is defined in the normal build section of a pom and has
definition, merge/ ?
What are your thoughts on adding another option for this? I am
guessing other plugins will also not want to merge executions from
profiles.
Cheers,
Nick
On 11/11/2008, at 11:39 AM, Nick Pellow wrote:
Hi Brian,
Even changing the executions to something else doesn't
/profiles
Cheers,
Nick Pellow
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Message-
From: Nick Pellow [mailto:[EMAIL PROTECTED]
Sent: Wednesday, October 22, 2008 10:38 PM
To: dev@maven.apache.org
Subject: preserving order of dependencies
Hi,
I am developing a maven plugin which needs to add a dependency to the
javac and surefire classpaths.
Using:
final
Hi,
I am developing a maven plugin which needs to add a dependency to the
javac and surefire classpaths.
Using:
final Set set = getProject().getDependencyArtifacts();
set.add( myArtifact );
getProject().setDependencyArtifacts( set );
seems to work most of the time.
In certain situations
().setDependencyArtifacts( set );
This is a work around for http://jira.codehaus.org/browse/MNG-2197 ,
trying to ensure that clover is on the compile time classpath.
Is there a better way to implement this? Is it possible to filter the
exclusions from the set of dependencyArtifacts?
Cheers,
Nick
Hi,
I am writing a custom maven2 MOJO. I need to access the runtime
configuration of another plugin, from this MOJO.
What is the best way to do this?
A concrete example: I would like to access any user defined excludes
and includes patterns of the maven-surefire-plugin from my MOJO.
Hi,
I have 3 MOJOs in a single maven plugin. Each MOJO needs to be
executed during specific build phases.
What is the best way to make this possible, without forcing users of
the plugin to insert explicit executions into their pom.xml ?
i.e. is it possible to make the following
without specifying its execution.
Hth,
Nick Stolwijk
~Java Developer~
Iprofs BV.
Claus Sluterweg 125
2012 WS Haarlem
www.iprofs.nl
On Tue, Sep 16, 2008 at 11:03 AM, Nick Pellow
[EMAIL PROTECTED] wrote:
Hi,
I have 3 MOJOs in a single maven plugin. Each MOJO needs to be
executed
during specific
20 matches
Mail list logo
