What maven version are you using? In fact, since maven 2.0.9, maven super-pom explicitly locks plugins versions to be used. But it's a very recommended practice to lock down the plugins you use.
Do you use a prior version to 2.0.9, or recently upgraded your maven version? Cheers 2009/5/29 Peter Kahn <[email protected]> > Can someone review this and let me know if I'm on the right track or if I'm > missing a maven nuance related to the site plugin and the default skin > problem? Thanks > > *Problem: > *Simple maven2 project build install & site without having a site.xml > flawlessly. At some point (last night) it stops working failing to find an > vm file and the skin. > > [ERROR] ResourceManager : unable to find resource > 'VM_global_library.vm' in any resource loader. > ... > SiteToolException: ArtifactNotFoundException: The skin does not exist: > Unable to determine the release version > > > *Workaround*: > I can provide a site.xml that specifies the the skin, but I'm ok with the > default site and don't want to go through the setup work for all the report > links. Also, this doesn't explain the spontaneous break and I don't like > it > when I don't know how something broke. > > *Additional Factors: > *I am also running a nexus maven proxy and forcing all users through it. > Nexus acts as prox for the following with repo1 and jboss being the only > offering the site plugin. > > https://repository.apache.org/content/groups/snapshots > https://maven.atlassian.com/maven1 > https://maven.atlassian.com/repository/public > <http://snapshots.repository.codehaus.org/> > http://snapshots.repository.codehaus.org/ > http://google-caja.googlecode.com/svn/maven > http://mirrors.ibiblio.org/pub/mirrors/maven2/ > http://download.java.net/maven/ * > http://repository.jboss.com/maven2* > http://maven.glassfish.org/content/groups/public/ * > http://repo1.maven.org/maven2/* > http://oauth.googlecode.com/svn/code/maven > > *Conclusion and Solution: > *I removed my proxy of jboss cleared & reindexed nexus and cleared my local > repository. When I rebuilt site without a site.xml doc my project built > properly. > > I believe that there is a problem with the site plugin at the jboss site. > Since I don't believe that I need jboss I think I can exclude it from my > proxy. If I did need it, i'm not sure how I'd ensure that my projects used > maven plugins from repo1 instead of jboss. > > If I should submit a bug on this somewhere please let me know and I'll do > it. Thanks for the help > -- > Peter Kahn > [email protected] > pkahnp...@aim > http://www.google.com/profiles/citizenkahn > Awareness - Intention - Action > -- Baptiste <Batmat> MATHUS - http://batmat.net Sauvez un arbre, Mangez un castor !
