On 22/10/2006, at 3:06 AM, [EMAIL PROTECTED] wrote:
+it0073
+it0073
typo?
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Hi there,
I've written a mojo that analyses the current project's dependencies
against those that are declared in the pom. It uses ASM to determine
the actual class dependencies from the project's compiled classes and
test classes, and then compares these against the classes held within
the
Hey,
Sounds good, but I think the most useful form of reuse is a Plexus
component. This means it can easily be used in Mojos and any other
Maven application that uses Plexus.
We can then put it in maven-shared. Definitely sounds useful and
allows you to do the Optimize Dependencies in
Hi Jason,
That should be fine, I wrote it with that kind of separation in mind.
The class file analyser is totally independent of Maven, so not sure
whether that would move it out of maven-shared and into
plexus-components? It's only the mojo that brings in the Maven
dependencies - any
On 23/10/06, Mark Hobson [EMAIL PROTECTED] wrote:
Shall we say a maven-dependency-analyser project in maven-shared?
Itchy trigger finger.. ignore that bit!
Mark
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional
Hi all,
I wanted to start talking about a new feature for Maven 2.1 that I think
will prove to be very powerful. I'd like Maven 2.1 to allow customization of
the components used in any particular role of the build. it would allow
developers to specify which ArtifactResolver implementation(s)
John,
I've not looked at the Plexus code, but it reminds me a bit of Avalon.
It seems like what you are trying to achieve should be easily doable
except that I am noticing that all the components.xml files are bound to
their components inside their respective jars. I'm not sure why that is,
