On 11 April 2014 14:40, Chris Graham wrote:
>
>
> Sent from my iPhone
>
> On 11/04/2014, at 9:23 AM, Barrie Treloar wrote:
>
> > On 10 April 2014 23:37, Lennart Jörelid
> wrote:
> >
> >> So ... the consequence of your approach would be that POMs throughout a
> >> maven reactor would have to rep
Sent from my iPhone
On 11/04/2014, at 9:23 AM, Barrie Treloar wrote:
> On 10 April 2014 23:37, Lennart Jörelid wrote:
>
>> So ... the consequence of your approach would be that POMs throughout a
>> maven reactor would have to repeat a dependency declaration if the classes
>> in your maven pr
On Apr 10, 2014, at 10:07 AM, Lennart Jörelid wrote:
> So ... the consequence of your approach would be that POMs throughout a
> maven reactor would have to repeat a dependency declaration if the classes
> in your maven project "directly" import a type. This - to me - seems not
> only complex to
On 10 April 2014 23:37, Lennart Jörelid wrote:
> So ... the consequence of your approach would be that POMs throughout a
> maven reactor would have to repeat a dependency declaration if the classes
> in your maven project "directly" import a type. This - to me - seems not
> only complex to resolv
Hi,
We solved 12 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11212&version=19130&styleName=Html
The most important one being that the plugin can now (again) be used
to generate announcements from JIRA for our own projects :-)
There are still a couple of issues left in JIRA
We've introduced AbstractMavenLifecycleParticipant#afterSessionEnd for
this very purpose in 3.2.1, it is called after all projects are built
and gives build extensions the chance to do any necessary cleanup. You
will have to require your plugin to have true
in pom.xml, because regular plugins are
Hi Devs
Actual question is at the end. Some introduction first.
I'm developing two Maven plugins, where actual functionality is not
implemented in the plugin, but delegated to "providers".
This idea is taken from maven-compiler-plugin, where the plugin
delegates compilation to plexus compilers.
So ... the consequence of your approach would be that POMs throughout a
maven reactor would have to repeat a dependency declaration if the classes
in your maven project "directly" import a type. This - to me - seems not
only complex to resolve in a big reactor, but quite user-unfriendly as
well. An
I realize folks are busy, I'll just run with this given I think we all agree
immutable classpaths are better and fiddly magic in the core is bad. I'm going
to remove the capability to dynamically fiddle with the project classpath and
the IT for MNG-4363 will be omitted from the run for Maven 4.0
