I did this with Maven 1 and I'm sure it would work with Maven 2, but it
may not be what your want. The way I handled it was to dynamically
construct the pom in a target directory along with the project files and
then invoke the goal (plugin) calls Maven again just for that project.
Richard van Nieuwenhoven wrote:
Hi,
That is why i ask for an "official" solution, a plugin will probably not
work. But is there an other? like a custom "dependence resolution
component" for this project. Or a global custom "dependence resolution
component". Or a way to dynamically create a global or local profile.
Or ...... any ideas?
thanks for the help,
Ritchie
Gilles Scokart wrote:
On 24/04/2008, Richard van Nieuwenhoven <[EMAIL PROTECTED]> wrote:
Hi,
the reason i need it is that a plugin generates code that depends on a
framework in a specific configuration. And the knowledge witch
combination of frameworks is needed, is provided by the generator (the
plugin). I do not like to duplicate this knowledge in evey module that
uses the plugin, this is why i would like the plugin (or some other
mean) to include the dependencies in the ProjectModel.
The IDE integration should be no problem because the included
dependencies would (and must) be included in the ProjectModel and
therefore are propagated to all running plugins as if they were in the
pom directly.
mfg
Ritchie
Only if the plugin is executed. IDE (or other tools like Ivy for
instance) don't run the plugins to use the dependency informations.
Also think to what you will publish to a repository. The projects
that depends on the project using the plugin will not execute your
plugin neither.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
