Hi,
ok so I'm working on a new goal for the versions plugin, analyze (and an
associated report analysis-report)
I would like this goal to highlight potential issues with respect to
versions
first problem I see is:
1. Referencing a reactor project as a plugin or plugin dependency consumed
l
On 4-Apr-09, at 10:13 AM, David Jencks wrote:
I'd like to write something I'll call it an archetype for
now that generates a maven project but needs to run a _lot_ of
java code in order to figure out what to put in the new pom.xml.
The basis of it is there given we have velocity
I'd like to write something I'll call it an archetype for now
that generates a maven project but needs to run a _lot_ of java code
in order to figure out what to put in the new pom.xml.
What's my best strategy here? From a quick glance at the archetype
plugin stuff it looks like th
On Sat, Apr 4, 2009 at 9:53 AM, James Carpenter wrote:
> I am building a maven plugin whose output is a directory structure with
> various files. As part of an integration test (driven by the shitty
> plugin), I would like to compare the output structure/files to those of an
> expected structure.
