You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Mark Hobson <ma...@gmail.com> on 2005/09/12 13:51:39 UTC
[m2] using deployed plugin snapshots with new metadata
I've just svn up'd to the latest m2 and seem to be having issues with
using deployed snapshots of custom plugins that was working
previously.
I deploy the custom plugin with "m2 -DupdateReleaseInfo=true deploy".
All seems to deploy okay, complete with the new XML metadata files.
I then delete any local-repo versions of the plugin and delete
plugin-registry.xml to force auto-discovery of my plugin. My
settings.xml is setup with the correct pluginGroup.
I then run the plugin goal against another project which fails. It
seems to be looking for pom urls of the form xxx-SNAPSHOT.pom, rather
than those that are there of the form xxx-20050912.112423-1.pom, even
though the metadata XML file indicates the snapshot version is indeed
20050912.112423, build 1.
Am I doing anything wrong here?
Cheers,
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: [m2] using deployed plugin snapshots with new metadata
Posted by Brett Porter <br...@gmail.com>.
Thanks Mark, I'll take a look.
- Brett
On 9/14/05, Mark Hobson <ma...@gmail.com> wrote:
>
> Raised http://jira.codehaus.org/browse/MNG-874
>
> Would like to set fix for beta-1 (being quite a blocker) but don't
> wanna get shouted at ;)
>
> On 13/09/05, Mark Hobson <ma...@gmail.com> wrote:
> > On 12/09/05, Mark Hobson <ma...@gmail.com> wrote:
> > > On 12/09/05, Brett Porter <br...@gmail.com> wrote:
> > > > ugh. My last fix was a bit short sighted - sorry about that.
> > > >
> > > > I'll keep looking into it.
> > >
> > > That's working now thanks.
> >
> > Think I spoke too soon - I'm trying this again with the proposed
> > 2.0-beta-1 version and I'm getting:
> >
> > [WARNING]
> > ***** Using defaults for missing POM
> > org.codehaus.mojo:maven-tomcat-plugin:pom:1.0-SNAPSHOT *****
> >
> > Even though it then proceeds to successfully download the jar. It
> > then ultimately fails due to the missing pom and insufficient
> > dependencies in the classpath.
> >
> > Any ideas why it's not using the timestamp-named pom? Be great to get
> > this fixed before beta-1 release.
> >
> > Cheers,
> >
> > Mark
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
Re: [m2] using deployed plugin snapshots with new metadata
Posted by Mark Hobson <ma...@gmail.com>.
Raised http://jira.codehaus.org/browse/MNG-874
Would like to set fix for beta-1 (being quite a blocker) but don't
wanna get shouted at ;)
On 13/09/05, Mark Hobson <ma...@gmail.com> wrote:
> On 12/09/05, Mark Hobson <ma...@gmail.com> wrote:
> > On 12/09/05, Brett Porter <br...@gmail.com> wrote:
> > > ugh. My last fix was a bit short sighted - sorry about that.
> > >
> > > I'll keep looking into it.
> >
> > That's working now thanks.
>
> Think I spoke too soon - I'm trying this again with the proposed
> 2.0-beta-1 version and I'm getting:
>
> [WARNING]
> ***** Using defaults for missing POM
> org.codehaus.mojo:maven-tomcat-plugin:pom:1.0-SNAPSHOT *****
>
> Even though it then proceeds to successfully download the jar. It
> then ultimately fails due to the missing pom and insufficient
> dependencies in the classpath.
>
> Any ideas why it's not using the timestamp-named pom? Be great to get
> this fixed before beta-1 release.
>
> Cheers,
>
> Mark
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: [m2] using deployed plugin snapshots with new metadata
Posted by Mark Hobson <ma...@gmail.com>.
On 12/09/05, Mark Hobson <ma...@gmail.com> wrote:
> On 12/09/05, Brett Porter <br...@gmail.com> wrote:
> > ugh. My last fix was a bit short sighted - sorry about that.
> >
> > I'll keep looking into it.
>
> That's working now thanks.
Think I spoke too soon - I'm trying this again with the proposed
2.0-beta-1 version and I'm getting:
[WARNING]
***** Using defaults for missing POM
org.codehaus.mojo:maven-tomcat-plugin:pom:1.0-SNAPSHOT *****
Even though it then proceeds to successfully download the jar. It
then ultimately fails due to the missing pom and insufficient
dependencies in the classpath.
Any ideas why it's not using the timestamp-named pom? Be great to get
this fixed before beta-1 release.
Cheers,
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: [m2] using deployed plugin snapshots with new metadata
Posted by Mark Hobson <ma...@gmail.com>.
On 12/09/05, Brett Porter <br...@gmail.com> wrote:
> ugh. My last fix was a bit short sighted - sorry about that.
>
> I'll keep looking into it.
That's working now thanks.
Cheers,
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: [m2] using deployed plugin snapshots with new metadata
Posted by Brett Porter <br...@gmail.com>.
ugh. My last fix was a bit short sighted - sorry about that.
I'll keep looking into it.
- Brett
On 9/13/05, Mark Hobson <ma...@gmail.com> wrote:
>
> Hmm, still having probs with this, albeit slightly different. The
> remote artifact metadata now reads:
>
> <metadata>
> <groupId>org.codehaus.mojo</groupId>
> <artifactId>maven-tomcat-plugin</artifactId>
> <versioning>
> <release>1.0-SNAPSHOT</release>
> <versions>
> <version>1.0-SNAPSHOT</version>
> </versions>
> </versioning>
> </metadata>
>
> Which compared to the previous one is missing the latest version tag.
> Now it's looking for
> "org.apache.maven.plugins:maven-tomcat-plugin:pom:RELEASE" and failing
> when it can't find it.
>
> Any ideas?
>
> Mark
>
Re: [m2] using deployed plugin snapshots with new metadata
Posted by Mark Hobson <ma...@gmail.com>.
Hmm, still having probs with this, albeit slightly different. The
remote artifact metadata now reads:
<metadata>
<groupId>org.codehaus.mojo</groupId>
<artifactId>maven-tomcat-plugin</artifactId>
<versioning>
<release>1.0-SNAPSHOT</release>
<versions>
<version>1.0-SNAPSHOT</version>
</versions>
</versioning>
</metadata>
Which compared to the previous one is missing the latest version tag.
Now it's looking for
"org.apache.maven.plugins:maven-tomcat-plugin:pom:RELEASE" and failing
when it can't find it.
Any ideas?
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: [m2] using deployed plugin snapshots with new metadata
Posted by Mark Hobson <ma...@gmail.com>.
On 12/09/05, Brett Porter <br...@gmail.com> wrote:
> fixed - will commit when svn cleanup gives me back my console :)
Heh, thanks Brett, muchly appreciated.
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: [m2] using deployed plugin snapshots with new metadata
Posted by Brett Porter <br...@gmail.com>.
fixed - will commit when svn cleanup gives me back my console :)
- Brett
On 9/12/05, Mark Hobson <ma...@gmail.com> wrote:
>
> On 12/09/05, Brett Porter <br...@gmail.com> wrote:
> > That's the problem. Will fix.
>
> Thanks Brett - I did think that was a bit strange but couldn't find
> any docs on the new metadata format so didn't look into it further.
>
> Mark
>
Re: [m2] using deployed plugin snapshots with new metadata
Posted by Mark Hobson <ma...@gmail.com>.
On 12/09/05, Brett Porter <br...@gmail.com> wrote:
> That's the problem. Will fix.
Thanks Brett - I did think that was a bit strange but couldn't find
any docs on the new metadata format so didn't look into it further.
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: [m2] using deployed plugin snapshots with new metadata
Posted by Brett Porter <br...@gmail.com>.
On 9/12/05, Mark Hobson <ma...@gmail.com> wrote:
>
> The remote version metadata is:
>
> ...
<localCopy>true</localCopy>
>
That's the problem. Will fix.
- Brett
Re: [m2] using deployed plugin snapshots with new metadata
Posted by Mark Hobson <ma...@gmail.com>.
On 12/09/05, Brett Porter <br...@gmail.com> wrote:
> It sounds like you've got it right. It should simply work.
>
> what is the contents of maven-metadata.xml for the artifact and version on
> the remote server? what about the various copies in the local repository?
The remote artfiact metadata is:
<metadata>
<groupId>org.codehaus.mojo</groupId>
<artifactId>maven-tomcat-plugin</artifactId>
<versioning>
<latest>1.0-SNAPSHOT</latest>
<release>1.0-SNAPSHOT</release>
<versions>
<version>1.0-SNAPSHOT</version>
</versions>
</versioning>
</metadata>
The remote version metadata is:
<metadata>
<groupId>org.codehaus.mojo</groupId>
<artifactId>maven-tomcat-plugin</artifactId>
<version>1.0-SNAPSHOT</version>
<versioning>
<snapshot>
<timestamp>20050912.112423</timestamp>
<buildNumber>1</buildNumber>
<localCopy>true</localCopy>
</snapshot>
</versioning>
</metadata>
My local group metadata for both central and my remote repo is:
<metadata>
<groupId>org.codehaus.mojo</groupId>
<plugins>
<plugin>
<prefix>tomcat</prefix>
<artifactId>maven-tomcat-plugin</artifactId>
</plugin>
</plugins>
</metadata>
My local artifact metadata for both central and my remote repo is:
<metadata>
<groupId>org.codehaus.mojo</groupId>
<artifactId>maven-tomcat-plugin</artifactId>
<versioning>
<latest>1.0-SNAPSHOT</latest>
<release>1.0-SNAPSHOT</release>
<versions>
<version>1.0-SNAPSHOT</version>
</versions>
</versioning>
</metadata>
My local version metadata for my remote repo only is:
<metadata>
<groupId>org.codehaus.mojo</groupId>
<artifactId>maven-tomcat-plugin</artifactId>
<version>1.0-SNAPSHOT</version>
<versioning>
<snapshot>
<timestamp>20050912.112423</timestamp>
<buildNumber>1</buildNumber>
<localCopy>true</localCopy>
</snapshot>
</versioning>
</metadata>
No other local files were downloaded.
> I will do a quick test as we don't have integration tests for deployment.
Cheers,
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: [m2] using deployed plugin snapshots with new metadata
Posted by Brett Porter <br...@gmail.com>.
It sounds like you've got it right. It should simply work.
what is the contents of maven-metadata.xml for the artifact and version on
the remote server? what about the various copies in the local repository?
I will do a quick test as we don't have integration tests for deployment.
- Brett
On 9/12/05, Mark Hobson <ma...@gmail.com> wrote:
>
> I've just svn up'd to the latest m2 and seem to be having issues with
> using deployed snapshots of custom plugins that was working
> previously.
>
> I deploy the custom plugin with "m2 -DupdateReleaseInfo=true deploy".
> All seems to deploy okay, complete with the new XML metadata files.
>
> I then delete any local-repo versions of the plugin and delete
> plugin-registry.xml to force auto-discovery of my plugin. My
> settings.xml is setup with the correct pluginGroup.
>
> I then run the plugin goal against another project which fails. It
> seems to be looking for pom urls of the form xxx-SNAPSHOT.pom, rather
> than those that are there of the form xxx-20050912.112423-1.pom, even
> though the metadata XML file indicates the snapshot version is indeed
> 20050912.112423, build 1.
>
> Am I doing anything wrong here?
>
> Cheers,
>
> Mark
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>