maven-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nils Fredrik Gjerull (JIRA)" <>
Subject [jira] Commented: (MNG-1916) Making it possible for plug-in to add modules to the reactor programatically
Date Wed, 04 Jan 2006 12:49:12 GMT
    [ ] 

Nils Fredrik Gjerull commented on MNG-1916:

Wildcarded {{<modules>}} would certainly help. As commented in issue MNG-1915 I am working
on making a maven2 plug-in for JPF. This is the reason I would like to specify a number of
directories and have all subdirectories containing jpf plug-ins included in the reactor.

I would like to have more fine grained control of which of this subdirectories should be included.
One example would be to only include directories containing pom.xml, plugin.xml and plugin-fragment.xml
files. This is however not essential, so wildcarded {{<modules>}} would probably do
the trick.

> Making it possible for plug-in to add modules to the reactor programatically
> ----------------------------------------------------------------------------
>          Key: MNG-1916
>          URL:
>      Project: Maven 2
>         Type: Improvement

>     Reporter: Nils Fredrik Gjerull

> I would like to be able to specify a number of directories as plug-in directories, automatically
discover every plug-in in those directories and include them in the reactor. As I understands
it the reactor with it's modules ({{org.apache.maven.execution.ReactorManager}}) is created
in {{org.apache.maven.DefaultMaven}}. If I understands this correctly maven plug-ins can't
add projects to the reactor programatically.
> My proposition to solve this is to add a phase which will be executed after the pom.xml
is parsed, but before the information stored in Model/MavenProject is used, and most importantly
before the {{ReactorManager is created}}. Then you can add information to the MavenProject
programatically, increasing the flexibility for plug-ins.
> I am not fluent in the maven2 code base, but it seems to me that this require quite a
lot of changes to the code. As I understands it the life cycle starts after the {{ReactorManager}}
is made, and therefore after the information in Model have started to be used.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message