On 05/02/2009, at 7:28 PM, Brett Porter wrote:
Is there anything the clover2 plugin should be doing to ensure that
these modifications are made on the transitively resolved projects?
I'd have to dig a bit - it has been a while. I thought that the
project in a forked lifecycle was discarde
On 04/02/2009, at 11:51 AM, Nick Pellow wrote:
Hi Brett,
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.
I'm not 100% certain, however it looks like the resources call is
Hi Brett,
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.
I'm not 100% certain, however it looks like the resources call is
happening as part of the forked lifecycle[1].
The
There's a further resolution step. The resources:resources in question
is for the app, and has both:
[DEBUG] com.fidelity.shares:shares-app:jar:1.0-SNAPSHOT (selected for
null)
[DEBUG] com.fidelity.shares:shares-domain:jar:clover:1.0-
SNAPSHOT:compile (selected for compile)
and
[DEBUG]
You're right. the dependency artifacts are already transitive.
e.g. the -X output shows:
[DEBUG] [Clover] List of dependency artifacts after changes:
[DEBUG] [Clover] Artifact [com.fidelity.shares:shares-
domain:jar:clover:1.0-SNAPSHOT], scope = [compile]
[DEBUG] [Clover] List of artifac
The dependency artifacts should already be transitive. I'm not quite
sure how 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 Pe
Will the filtering be applied to the artifacts resolved by the maven-
compiler-plugin, and the maven-surefire-plugin?
My understanding is that:
1) the maven-clover2-plugin creates a classified artifact with the -
clover classifier. it also looks for -clover classified artifacts of
project dep
You can't modify the resolution, but you can filter the artifacts it
gets from the project. There are a few utility classes for that
(you'll see them used in the dependency plugin, assembly plugin for
example).
- Brett
On 03/02/2009, at 12:14 PM, Nick Pellow wrote:
Thanks for the clarifi
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 with a particular classifier are
considered different to ar
Yes, that's expected - artifacts with a particular classifier are
considered different 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 build
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 being put on the classpath under certain
circumstances.
e..g
[INFO] Compiling 3 source file
11 matches
Mail list logo
