You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Stephen Connolly <st...@gmail.com> on 2008/09/05 01:18:38 UTC
[ANN] Versions Maven Plugin 1.0-alpha-1 released
The Mojo team is pleased to announce the release of the Versions Maven
Plugin, version 1.0-alpha-1.
This plugin allows:
* the querying for newer versions of plugins used in a project.
* the querying for newer versions of dependencies used in a project.
* updating a project's parent to the latest available version
(e.g. useful for syncing with corporate poms to ensure the latest is
used prior to rolling a release)
* updating properties defined in a project to the latest version of a
specific
artifact (e.g. for ensuring that a suite of dependencies are all the same
version)
http://mojo.codehaus.org/versions-maven-plugin/
You can run mvn -up to get the latest version of the plugin, or specify
the version in your project's plugin configuration:
<plugin>
<groupId>org.codehaus.mojo</groupId>
<artifactId>versions-maven-plugin</artifactId>
<version>1.0-alpha-1</version>
</plugin>
Release Notes - Maven 2.x Versions Plugin - Version 1.0-alpha-1
** Bug
* [MVERSIONS-1] - javadoc plugin doesn't have its version specified but
it has
* [MVERSIONS-2] - display-plugin-updates does not include lifecycle
plugins that are not defined in the pom.
** Known Issues - Maven 2.x Versions Plugin - Version 1.0-alpha-1
* [MVERSIONS-3] - display-plugin-updates does not identify the plugin
version as not being provided when derived from the super-pom
Enjoy,
-The Mojo team
Re: [ANN] Versions Maven Plugin 1.0-alpha-1 released
Posted by Stephen Connolly <st...@gmail.com>.
Yep, basically 4 digit version numbers are not in the maven format!
On Fri, Sep 5, 2008 at 2:37 PM, Stephen Duncan Jr
<st...@gmail.com>wrote:
> On Fri, Sep 5, 2008 at 9:24 AM, Stephen Duncan Jr
> <st...@gmail.com>wrote:
>
> > My first attempt to run it gave this output that seems...incorrect:
> >
> > [INFO] The following dependency updates are available:
> > [INFO] c3p0:c3p0 .......................................... 0.9.1.2 ->
> > 0.9.0
> >
> >
> Sorry about the noise; I see from the FAQ that a fourth digit in a version
> number isn't handled numerically by default...
>
> --
> Stephen Duncan Jr
> www.stephenduncanjr.com
>
Re: [ANN] Versions Maven Plugin 1.0-alpha-1 released
Posted by Stephen Duncan Jr <st...@gmail.com>.
On Fri, Sep 5, 2008 at 9:24 AM, Stephen Duncan Jr
<st...@gmail.com>wrote:
> My first attempt to run it gave this output that seems...incorrect:
>
> [INFO] The following dependency updates are available:
> [INFO] c3p0:c3p0 .......................................... 0.9.1.2 ->
> 0.9.0
>
>
Sorry about the noise; I see from the FAQ that a fourth digit in a version
number isn't handled numerically by default...
--
Stephen Duncan Jr
www.stephenduncanjr.com
Re: [ANN] Versions Maven Plugin 1.0-alpha-1 released
Posted by Stephen Duncan Jr <st...@gmail.com>.
On Thu, Sep 4, 2008 at 7:18 PM, Stephen Connolly <
stephen.alan.connolly@gmail.com> wrote:
> The Mojo team is pleased to announce the release of the Versions Maven
> Plugin, version 1.0-alpha-1.
>
> This plugin allows:
> * the querying for newer versions of plugins used in a project.
> * the querying for newer versions of dependencies used in a project.
> * updating a project's parent to the latest available version
> (e.g. useful for syncing with corporate poms to ensure the latest is
> used prior to rolling a release)
> * updating properties defined in a project to the latest version of a
> specific
> artifact (e.g. for ensuring that a suite of dependencies are all the same
> version)
>
> http://mojo.codehaus.org/versions-maven-plugin/
>
> You can run mvn -up to get the latest version of the plugin, or specify
> the version in your project's plugin configuration:
>
> <plugin>
> <groupId>org.codehaus.mojo</groupId>
> <artifactId>versions-maven-plugin</artifactId>
> <version>1.0-alpha-1</version>
> </plugin>
>
> Release Notes - Maven 2.x Versions Plugin - Version 1.0-alpha-1
>
> ** Bug
> * [MVERSIONS-1] - javadoc plugin doesn't have its version specified but
> it has
> * [MVERSIONS-2] - display-plugin-updates does not include lifecycle
> plugins that are not defined in the pom.
>
> ** Known Issues - Maven 2.x Versions Plugin - Version 1.0-alpha-1
> * [MVERSIONS-3] - display-plugin-updates does not identify the plugin
> version as not being provided when derived from the super-pom
>
> Enjoy,
>
> -The Mojo team
>
My first attempt to run it gave this output that seems...incorrect:
[INFO] The following dependency updates are available:
[INFO] c3p0:c3p0 .......................................... 0.9.1.2 ->
0.9.0
--
Stephen Duncan Jr
www.stephenduncanjr.com
Re: [ANN] Versions Maven Plugin 1.0-alpha-1 released
Posted by Brett Porter <br...@gmail.com>.
Yes, Archiva will proxy and merge the metadata as well if configured to do
so.
- Brett
2008/9/5 Stephen Connolly <st...@gmail.com>
> That is a good question...
>
> I would think that when you ask for the latest maven-metatdata.xml archivia
> will check if it's cache is out of date and then query central...
>
> if you do mvn -U do you get the latest version of a plugin automatically
> (if
> yes, then the answer is yes, if no then the answer is no)
>
> FYI, we're using nexus and have no issues in this regard
>
> -Stephen
>
> On Fri, Sep 5, 2008 at 7:46 AM, Wim Deblauwe <wi...@gmail.com>
> wrote:
>
> > Does it work if you are not using the central repo directly but a
> > repository
> > manager (archiva in my case) in between. Will this plugin "see" the newer
> > versions, even if they are not in archiva yet?
> >
> > regards,
> >
> > Wim
> >
> > 2008/9/5 Stephen Connolly <st...@gmail.com>
> >
> > > The Mojo team is pleased to announce the release of the Versions Maven
> > > Plugin, version 1.0-alpha-1.
> > >
> > > This plugin allows:
> > > * the querying for newer versions of plugins used in a project.
> > > * the querying for newer versions of dependencies used in a project.
> > > * updating a project's parent to the latest available version
> > > (e.g. useful for syncing with corporate poms to ensure the latest is
> > > used prior to rolling a release)
> > > * updating properties defined in a project to the latest version of a
> > > specific
> > > artifact (e.g. for ensuring that a suite of dependencies are all the
> > same
> > > version)
> > >
> > > http://mojo.codehaus.org/versions-maven-plugin/
> > >
> > > You can run mvn -up to get the latest version of the plugin, or specify
> > > the version in your project's plugin configuration:
> > >
> > > <plugin>
> > > <groupId>org.codehaus.mojo</groupId>
> > > <artifactId>versions-maven-plugin</artifactId>
> > > <version>1.0-alpha-1</version>
> > > </plugin>
> > >
> > > Release Notes - Maven 2.x Versions Plugin - Version 1.0-alpha-1
> > >
> > > ** Bug
> > > * [MVERSIONS-1] - javadoc plugin doesn't have its version specified
> > but
> > > it has
> > > * [MVERSIONS-2] - display-plugin-updates does not include lifecycle
> > > plugins that are not defined in the pom.
> > >
> > > ** Known Issues - Maven 2.x Versions Plugin - Version 1.0-alpha-1
> > > * [MVERSIONS-3] - display-plugin-updates does not identify the
> plugin
> > > version as not being provided when derived from the super-pom
> > >
> > > Enjoy,
> > >
> > > -The Mojo team
> > >
> >
>
--
Brett Porter
Blog: http://blogs.exist.com/bporter/
Re: [ANN] Versions Maven Plugin 1.0-alpha-1 released
Posted by Stephen Connolly <st...@gmail.com>.
That is a good question...
I would think that when you ask for the latest maven-metatdata.xml archivia
will check if it's cache is out of date and then query central...
if you do mvn -U do you get the latest version of a plugin automatically (if
yes, then the answer is yes, if no then the answer is no)
FYI, we're using nexus and have no issues in this regard
-Stephen
On Fri, Sep 5, 2008 at 7:46 AM, Wim Deblauwe <wi...@gmail.com> wrote:
> Does it work if you are not using the central repo directly but a
> repository
> manager (archiva in my case) in between. Will this plugin "see" the newer
> versions, even if they are not in archiva yet?
>
> regards,
>
> Wim
>
> 2008/9/5 Stephen Connolly <st...@gmail.com>
>
> > The Mojo team is pleased to announce the release of the Versions Maven
> > Plugin, version 1.0-alpha-1.
> >
> > This plugin allows:
> > * the querying for newer versions of plugins used in a project.
> > * the querying for newer versions of dependencies used in a project.
> > * updating a project's parent to the latest available version
> > (e.g. useful for syncing with corporate poms to ensure the latest is
> > used prior to rolling a release)
> > * updating properties defined in a project to the latest version of a
> > specific
> > artifact (e.g. for ensuring that a suite of dependencies are all the
> same
> > version)
> >
> > http://mojo.codehaus.org/versions-maven-plugin/
> >
> > You can run mvn -up to get the latest version of the plugin, or specify
> > the version in your project's plugin configuration:
> >
> > <plugin>
> > <groupId>org.codehaus.mojo</groupId>
> > <artifactId>versions-maven-plugin</artifactId>
> > <version>1.0-alpha-1</version>
> > </plugin>
> >
> > Release Notes - Maven 2.x Versions Plugin - Version 1.0-alpha-1
> >
> > ** Bug
> > * [MVERSIONS-1] - javadoc plugin doesn't have its version specified
> but
> > it has
> > * [MVERSIONS-2] - display-plugin-updates does not include lifecycle
> > plugins that are not defined in the pom.
> >
> > ** Known Issues - Maven 2.x Versions Plugin - Version 1.0-alpha-1
> > * [MVERSIONS-3] - display-plugin-updates does not identify the plugin
> > version as not being provided when derived from the super-pom
> >
> > Enjoy,
> >
> > -The Mojo team
> >
>
Re: [ANN] Versions Maven Plugin 1.0-alpha-1 released
Posted by Wim Deblauwe <wi...@gmail.com>.
Does it work if you are not using the central repo directly but a repository
manager (archiva in my case) in between. Will this plugin "see" the newer
versions, even if they are not in archiva yet?
regards,
Wim
2008/9/5 Stephen Connolly <st...@gmail.com>
> The Mojo team is pleased to announce the release of the Versions Maven
> Plugin, version 1.0-alpha-1.
>
> This plugin allows:
> * the querying for newer versions of plugins used in a project.
> * the querying for newer versions of dependencies used in a project.
> * updating a project's parent to the latest available version
> (e.g. useful for syncing with corporate poms to ensure the latest is
> used prior to rolling a release)
> * updating properties defined in a project to the latest version of a
> specific
> artifact (e.g. for ensuring that a suite of dependencies are all the same
> version)
>
> http://mojo.codehaus.org/versions-maven-plugin/
>
> You can run mvn -up to get the latest version of the plugin, or specify
> the version in your project's plugin configuration:
>
> <plugin>
> <groupId>org.codehaus.mojo</groupId>
> <artifactId>versions-maven-plugin</artifactId>
> <version>1.0-alpha-1</version>
> </plugin>
>
> Release Notes - Maven 2.x Versions Plugin - Version 1.0-alpha-1
>
> ** Bug
> * [MVERSIONS-1] - javadoc plugin doesn't have its version specified but
> it has
> * [MVERSIONS-2] - display-plugin-updates does not include lifecycle
> plugins that are not defined in the pom.
>
> ** Known Issues - Maven 2.x Versions Plugin - Version 1.0-alpha-1
> * [MVERSIONS-3] - display-plugin-updates does not identify the plugin
> version as not being provided when derived from the super-pom
>
> Enjoy,
>
> -The Mojo team
>