You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by Vincent Massol <vm...@pivolis.com> on 2003/04/14 23:57:19 UTC
maven-plugins and maven versions
Hi,
Following the idea of moving the maven plugins in maven-plugins, I
believe a new issue will arise: the compatibility between the plugin and
the maven core.
One solution (is there any other?) would be to add a <compatibility> tag
in the plugin project POMs.
Comments?
Thanks
-Vincent
From: "Vincent Massol" <vm...@pivolis.com>
To: "'Maven Developers List'" <de...@maven.apache.org>
Subject: maven-plugins and maven versions
Date: Mon, 14 Apr 2003 23:57:19 +0200
Message-ID: <00...@octovma>
MIME-Version: 1.0
Content-Type: text/plain;
charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.4024
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Importance: Normal
Hi,
Following the idea of moving the maven plugins in maven-plugins, I
believe a new issue will arise: the compatibility between the plugin and
the maven core.
One solution (is there any other?) would be to add a <compatibility> tag
in the plugin project POMs.
Comments?
Thanks
-Vincent
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: maven-plugins and maven versions
Posted by Brett Porter <bp...@f2network.com.au>.
I don't know a lot about the internals, especially the plugin cache. Are
the plugins or the POM loaded first? If it is the plugins, that
obviously makes this difficult, but I thought the POM came first, which
means you can preregister dependant plugins.
It also depends on what happens with the "core" plugins. Which plugins
are registered by default? If we continue with the $MAVEN_HOME/plugins
directory, then these can all be used, unless a different versioned
plugin (same artifactID, different version) has already been loaded.
But I don't see any reason why the plugins can't be part of the local
repository (they already are copied there under /maven/), and loaded
from there. I'm not sure what the best way is to then define default
plugins and how to turn those off on a project to project basis however
- but that ability only exists now through "delete" anyway.
Maybe the core maven template just specifies these plugins as
dependencies, and you use Jelly in maven.xml to deregister them as a
preGoal to some plugin-loading-completed goal?
How is that sounding?
Cheers,
Brett
michal.maczka wrote:
>
>>-----Original Message-----
>>From: Brett Porter [mailto:bporter@f2network.com.au]
>>Sent: Tuesday, April 15, 2003 9:52 AM
>>To: Maven Developers List
>>Subject: Re: maven-plugins and maven versions
>>
>>
>>I agree - I would have raised the point of plugin versioning except that
>>I had already seen it go by. I think depending on and downloading a
>>plugin should be handled like any other artifact.
>>
>
> Yeah,
> ...But I believe that there is no way to make it that simple.
> How will Maven then search for a given goal?
> This certaily requires more complex processing.
>
> [..]
>
>
> Michal
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
--
Web Developer
f2 network ~ everything essential
02 8596 4437
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
RE: maven-plugins and maven versions
Posted by "michal.maczka" <mi...@cqs.ch>.
> -----Original Message-----
> From: Brett Porter [mailto:bporter@f2network.com.au]
> Sent: Tuesday, April 15, 2003 9:52 AM
> To: Maven Developers List
> Subject: Re: maven-plugins and maven versions
>
>
> I agree - I would have raised the point of plugin versioning except that
> I had already seen it go by. I think depending on and downloading a
> plugin should be handled like any other artifact.
>
Yeah,
...But I believe that there is no way to make it that simple.
How will Maven then search for a given goal?
This certaily requires more complex processing.
[..]
Michal
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: maven-plugins and maven versions
Posted by Brett Porter <bp...@f2network.com.au>.
I agree - I would have raised the point of plugin versioning except that
I had already seen it go by. I think depending on and downloading a
plugin should be handled like any other artifact.
I know I maintain my own build plugin with custom goals, and would like
some to stay on a previous version when I make some changes (even if
just for a testing phase without having a separate maven install).
Cheers,
Brett
michal.maczka wrote:
> I was first to mention it I asked about last week ;)
> Just kidding.
>
> I think that once Maven matures the core will be
> changed relativly rarly
> (e.g Maven 1.4 will be in use for a year before 1.5 is out)
>
> But Plugins will change much more frequently.
> And certainly once there will be no more centralized
> maintaince of plugins (which is not working even now
> as there is a couple of broken plugins in Maven Core)
> some mechanism for versioning Maven core is need.
>
> But I think that to make it correct not only the plugin should
> contain some information specifing which version of
> core they are using but also an information about other plugins
> it depends on (maybe except plugis distributed with core)
>
> In my last post I mentioned that maybe there are things
> which can be learnt from RPM or DEB file format as I
> think this is conceptualy close.
>
> I am much afraid that this is rather complex subject...
>
>
> what you think?
>
>
>
>>Amazing coincidence - that adds a point #3 to the proposal (maven
>>version dependencies) I just sent and is probably the most relevant of
>>them all :)
>>
>>What things to you think a project and/or plugin need to know?
>>I'd say:
>>1) known to work with maven version X through Y
>>2) known not to work with maven version Z
>>3) may work with versions Y and above - not tested
>>
>
>
> Well, I don't see a chance that "dead" or temporary unmaintainn plugin
> will provide such information.
>
>
> Michal
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
--
Web Developer
f2 network ~ everything essential
02 8596 4437
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
RE: maven-plugins and maven versions
Posted by "michal.maczka" <mi...@cqs.ch>.
I was first to mention it I asked about last week ;)
Just kidding.
I think that once Maven matures the core will be
changed relativly rarly
(e.g Maven 1.4 will be in use for a year before 1.5 is out)
But Plugins will change much more frequently.
And certainly once there will be no more centralized
maintaince of plugins (which is not working even now
as there is a couple of broken plugins in Maven Core)
some mechanism for versioning Maven core is need.
But I think that to make it correct not only the plugin should
contain some information specifing which version of
core they are using but also an information about other plugins
it depends on (maybe except plugis distributed with core)
In my last post I mentioned that maybe there are things
which can be learnt from RPM or DEB file format as I
think this is conceptualy close.
I am much afraid that this is rather complex subject...
what you think?
>
> Amazing coincidence - that adds a point #3 to the proposal (maven
> version dependencies) I just sent and is probably the most relevant of
> them all :)
>
> What things to you think a project and/or plugin need to know?
> I'd say:
> 1) known to work with maven version X through Y
> 2) known not to work with maven version Z
> 3) may work with versions Y and above - not tested
>
Well, I don't see a chance that "dead" or temporary unmaintainn plugin
will provide such information.
Michal
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: maven-plugins and maven versions
Posted by Brett Porter <bp...@f2network.com.au>.
Amazing coincidence - that adds a point #3 to the proposal (maven
version dependencies) I just sent and is probably the most relevant of
them all :)
What things to you think a project and/or plugin need to know?
I'd say:
1) known to work with maven version X through Y
2) known not to work with maven version Z
3) may work with versions Y and above - not tested
Cheers,
Brett
Vincent Massol wrote:
> Hi,
>
> Following the idea of moving the maven plugins in maven-plugins, I
> believe a new issue will arise: the compatibility between the plugin and
> the maven core.
>
> One solution (is there any other?) would be to add a <compatibility> tag
> in the plugin project POMs.
>
> Comments?
>
> Thanks
> -Vincent
> From: "Vincent Massol" <vm...@pivolis.com>
> To: "'Maven Developers List'" <de...@maven.apache.org>
> Subject: maven-plugins and maven versions
> Date: Mon, 14 Apr 2003 23:57:19 +0200
> Message-ID: <00...@octovma>
> MIME-Version: 1.0
> Content-Type: text/plain;
> charset="us-ascii"
> Content-Transfer-Encoding: 7bit
> X-Priority: 3 (Normal)
> X-MSMail-Priority: Normal
> X-Mailer: Microsoft Outlook, Build 10.0.4024
> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
> Importance: Normal
>
> Hi,
>
> Following the idea of moving the maven plugins in maven-plugins, I
> believe a new issue will arise: the compatibility between the plugin and
> the maven core.
>
> One solution (is there any other?) would be to add a <compatibility> tag
> in the plugin project POMs.
>
> Comments?
>
> Thanks
> -Vincent
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
--
Web Developer
f2 network ~ everything essential
02 8596 4437
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org