Re: Problem with updating non-unique snapshot versions of a plugin

2009-08-20 Thread Sven Preßler
hmm, no response for a week, I guess that answers my question with 'no, no,
yes'...



2009/8/12 Sven Preßler sven.press...@gmail.com

 Hello,

 I'm currently using maven 2.0.9.
 I've got a project X which uses a Plugin my-plugin with version
 1.0-SNAPSHOT.
 How do I force maven to update this plugin from the repository, no matter
 what?
 I tried the following: make some changes to the plugin, build it with
 mvn package
 and upload the newly created .jar to the repository.
 I do that, because I want to simulate the situation on the build server, on
 which I cant just compile the latest version of my plugin.
 Now when I try to build project X with
 mvn package -U, I get something like
 [INFO] snapshot group:my-plugin:1.0-SNAPSHOT: checking for updates from
 m2repo-plugins
 but nothing is downloaded, I checked the .jar in my local repository, but
 it's unchanged.

 I found that it's possible to recreate (or something like that) the local
 repository with
 mvn dependency:purge-local-repository
 However, this only seems to work if I create a dependency/-entry for my
 plugin and even if I do that, it's not really a good solution, since I
 cannot run a command like that on our build server.

 Then I found this issue: http://jira.codehaus.org/browse/MNG-2839
 It's a bit different than my problem, so I'm not sure if I'm actually
 facing the same problem.
 So my question is: Is there any quick solution to this problem, did I miss
 something
 or do I just have to wait for the Fix Version 2.2.x as described in the
 issue?

 Thanks,
 Sven



Re: Problem with updating non-unique snapshot versions of a plugin

2009-08-20 Thread Stephen Connolly
2009/8/12 Sven Preßler sven.press...@gmail.com:
 Hello,

 I'm currently using maven 2.0.9.
 I've got a project X which uses a Plugin my-plugin with version
 1.0-SNAPSHOT.
 How do I force maven to update this plugin from the repository, no matter
 what?
 I tried the following: make some changes to the plugin, build it with
mvn package
 and upload the newly created .jar to the repository.

how exactly are you doing the upload?

There is maven metadata that needs to be updated, if you are not using
a repository manager that knows how to do this, and are instead
uploading by hand, then this would completely explain your problems

-Stephen

 I do that, because I want to simulate the situation on the build server, on
 which I cant just compile the latest version of my plugin.
 Now when I try to build project X with
mvn package -U, I get something like
 [INFO] snapshot group:my-plugin:1.0-SNAPSHOT: checking for updates from
 m2repo-plugins
 but nothing is downloaded, I checked the .jar in my local repository, but
 it's unchanged.

 I found that it's possible to recreate (or something like that) the local
 repository with
mvn dependency:purge-local-repository
 However, this only seems to work if I create a dependency/-entry for my
 plugin and even if I do that, it's not really a good solution, since I
 cannot run a command like that on our build server.

 Then I found this issue: http://jira.codehaus.org/browse/MNG-2839
 It's a bit different than my problem, so I'm not sure if I'm actually facing
 the same problem.
 So my question is: Is there any quick solution to this problem, did I miss
 something
 or do I just have to wait for the Fix Version 2.2.x as described in the
 issue?

 Thanks,
 Sven


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org



Re: Problem with updating non-unique snapshot versions of a plugin

2009-08-20 Thread Sven Preßler
2009/8/20 Stephen Connolly stephen.alan.conno...@gmail.com

 2009/8/12 Sven Preßler sven.press...@gmail.com:
  Hello,
 
  I'm currently using maven 2.0.9.
  I've got a project X which uses a Plugin my-plugin with version
  1.0-SNAPSHOT.
  How do I force maven to update this plugin from the repository, no matter
  what?
  I tried the following: make some changes to the plugin, build it with
 mvn package
  and upload the newly created .jar to the repository.

 how exactly are you doing the upload?

 There is maven metadata that needs to be updated, if you are not using
 a repository manager that knows how to do this, and are instead
 uploading by hand, then this would completely explain your problems

 -Stephen



I'm uploading via a svn commit.
I commit the .jar and I also commit updated versions of the two
maven-metadata-local.xml files (I edit the timestamp lastUpdated/ by hand)
Are there other files involved that need to be changed?

Sven


Re: Problem with updating non-unique snapshot versions of a plugin

2009-08-20 Thread Stephen Connolly
2009/8/20 Sven Preßler sven.press...@gmail.com:
 2009/8/20 Stephen Connolly stephen.alan.conno...@gmail.com

 2009/8/12 Sven Preßler sven.press...@gmail.com:
  Hello,
 
  I'm currently using maven 2.0.9.
  I've got a project X which uses a Plugin my-plugin with version
  1.0-SNAPSHOT.
  How do I force maven to update this plugin from the repository, no matter
  what?
  I tried the following: make some changes to the plugin, build it with
 mvn package
  and upload the newly created .jar to the repository.

 how exactly are you doing the upload?

 There is maven metadata that needs to be updated, if you are not using
 a repository manager that knows how to do this, and are instead
 uploading by hand, then this would completely explain your problems

 -Stephen



 I'm uploading via a svn commit.
 I commit the .jar and I also commit updated versions of the two
 maven-metadata-local.xml files (I edit the timestamp lastUpdated/ by hand)
 Are there other files involved that need to be changed?


Aha!

You are doing it all wrong!

Remote repositories and local repositories are not the same thing.

You cannot use a local repository as a remote repository.

The short answer is get yourself a good repository manager (e.g. nexus
or artifactory)

The long answer is get yourself a good repository manager or else use
a webdav based repository and deploy to it only using the maven deploy
plugin (i.e. deploy:deploy-file or deploy:deploy)

If you insist on doing what you are doing then you will end up with
the issues you are seeing

-Stephen

 Sven


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org



Re: Problem with updating non-unique snapshot versions of a plugin

2009-08-20 Thread Sven Preßler
hmm, interesting, thanks!
I actually just deleted the metadata-local files in the remote repository,
since your answer made me check for the file structure of other plugins in
the remote repo...
and now it's working, great!

Thanks,
Sven


2009/8/20 Stephen Connolly stephen.alan.conno...@gmail.com

 2009/8/20 Sven Preßler sven.press...@gmail.com:
  2009/8/20 Stephen Connolly stephen.alan.conno...@gmail.com
 
  2009/8/12 Sven Preßler sven.press...@gmail.com:
   Hello,
  
   I'm currently using maven 2.0.9.
   I've got a project X which uses a Plugin my-plugin with version
   1.0-SNAPSHOT.
   How do I force maven to update this plugin from the repository, no
 matter
   what?
   I tried the following: make some changes to the plugin, build it with
  mvn package
   and upload the newly created .jar to the repository.
 
  how exactly are you doing the upload?
 
  There is maven metadata that needs to be updated, if you are not using
  a repository manager that knows how to do this, and are instead
  uploading by hand, then this would completely explain your problems
 
  -Stephen
 
 
 
  I'm uploading via a svn commit.
  I commit the .jar and I also commit updated versions of the two
  maven-metadata-local.xml files (I edit the timestamp lastUpdated/ by
 hand)
  Are there other files involved that need to be changed?
 

 Aha!

 You are doing it all wrong!

 Remote repositories and local repositories are not the same thing.

 You cannot use a local repository as a remote repository.

 The short answer is get yourself a good repository manager (e.g. nexus
 or artifactory)

 The long answer is get yourself a good repository manager or else use
 a webdav based repository and deploy to it only using the maven deploy
 plugin (i.e. deploy:deploy-file or deploy:deploy)

 If you insist on doing what you are doing then you will end up with
 the issues you are seeing

 -Stephen

  Sven
 

 -
 To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
 For additional commands, e-mail: users-h...@maven.apache.org




Problem with updating non-unique snapshot versions of a plugin

2009-08-12 Thread Sven Preßler
Hello,

I'm currently using maven 2.0.9.
I've got a project X which uses a Plugin my-plugin with version
1.0-SNAPSHOT.
How do I force maven to update this plugin from the repository, no matter
what?
I tried the following: make some changes to the plugin, build it with
mvn package
and upload the newly created .jar to the repository.
I do that, because I want to simulate the situation on the build server, on
which I cant just compile the latest version of my plugin.
Now when I try to build project X with
mvn package -U, I get something like
[INFO] snapshot group:my-plugin:1.0-SNAPSHOT: checking for updates from
m2repo-plugins
but nothing is downloaded, I checked the .jar in my local repository, but
it's unchanged.

I found that it's possible to recreate (or something like that) the local
repository with
mvn dependency:purge-local-repository
However, this only seems to work if I create a dependency/-entry for my
plugin and even if I do that, it's not really a good solution, since I
cannot run a command like that on our build server.

Then I found this issue: http://jira.codehaus.org/browse/MNG-2839
It's a bit different than my problem, so I'm not sure if I'm actually facing
the same problem.
So my question is: Is there any quick solution to this problem, did I miss
something
or do I just have to wait for the Fix Version 2.2.x as described in the
issue?

Thanks,
Sven