Type: Bug
Versions: 1.9
Environment: N/A
Reporter: Kristopher Brown
Priority: Minor
Inside goal clover:test-single
line 284 is:
and this goal is no longer present.
Seems to work for me if I just change this to:
--
This message is automatically generated by
> >4) Would it be worth while adding properties to the
> reactor/maven tag
> >to pass through the current context or some properties.
> >
> >
> I think so. I'm pretty sure that there is already an open
> JIRA issue for it to. If you'd like to comment there, we can
> bring that forward to 1.1-
Hi,
I'm trying to pass properties into subprojects using the reactor, and
I've provided an example of the script used at the end.
I'm not 100% certain, but I've had a good look through the reactor tag
code, and followed that through to PluginManager#attainGoals(Project,
List) which sets up the n
AIL PROTECTED]
> Sent: 13 May 2004 16:47
> To: 'Maven Developers List'
> Subject: RE: Inter-plugin dependancy best practices
>
> Hi Kristopher,
>
> > -Original Message-
> > From: Kristopher Brown
> [mailto:[EMAIL PROTECTED]
> > Sent:
Hi,
How should plugin developers indicate that a plugin is inter-dependant
on anther plugin? Some have suggested a registering mechanism like that
used by the site report. Another way is by modifying a shared variable.
For example, maven.compile.src.set can be used by plugins to make other
plug
