Lars,
Could you give it an other try as I think it should be fixed now.
Thanks
Olivier
On Tue, Nov 3, 2009 at 3:45 PM, Olivier Gaudin
<gaudol@...> wrote:
No pb at all Lars. This whole thing is a bit annoying as it gives a bad impression and fixing it is not in our hands...
Anyway, the answer to your question is : absolutely, you should use 1.0-beta-1 as a version.
Olivier
On Tue, Nov 3, 2009 at 3:28 PM, Lars Fischer
<lfischer@...> wrote:
Hello Olivier,
I hope you have recognised the smiley. My post wasn't intended as offence.
Olivier Gaudin schrieb:
I would to bring some clarifications as several assumptions have been madehere.
1. http://repository.sonatype.org <http://repository.sonatype.org/> is a repository managed by Sonatype, that aggregates many repository. Those repository can contain anything
2. We only publish releases, not snapshots
3. The latest version of the mojo is 1.0-beta-1 :
http://repository.sonatype.org/content/groups/public/org/codehaus/mojo/sonar-maven-plugin/1.0-beta-1/
Having said that, we did publish by mistake a 1.0-snapshot on the 6th of June and this was apparently captured by some repositories. As this snapshot version is more recent than the 1.0-beta-1, if you do not explicitly mention the version it is going to try to download the 1.0-snapshot version and then fails as it does not exist (was removed).
Thank you for the clarification.
I am going to see if I can get it fixed in Sonatype repo. For the time being, I would recommend you set the version of the mojo.
I execute sonar within a hudson ci-build. Can I change the mojo version by using plugin-management / dependency-management in the parent pom of my projects?
