maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Erik Husby (JIRA)" <j...@codehaus.org>
Subject [jira] Commented: (MSITE-228) Try and unable to resolve org.apache.maven.skins:maven-default-skin:jar:RELEASE when another skin is specified
Date Thu, 01 Oct 2009 17:47:56 GMT

    [ http://jira.codehaus.org/browse/MSITE-228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=193097#action_193097
] 

Erik Husby commented on MSITE-228:
----------------------------------

I am still struggling with this problem even in Maven 2.2.0. What is worse is that it always
updates the metadata for the default skin even though the metadata already exists in the user's
repository. And the problem is that sometimes the metadata from maven central is correct and
sometime it is wrong.

And this problem of getting the wrong metadata breaks my builds.

I tried protecting the ~/.m2/repository/org/apache/maven/skins directory once it had correct
metadata but that causes the build to fail because Maven site plugin wants to update the metadata
and it can't.

It seems that the fact is skin is sometimes a plugin and sometimes it isn't indicates a design
failure. And I would call this instance on updating the metadata every time a bug, not a feature.

My next attempt to work around this problem will be to update all the site.xml to use something
else than the default skin.

> Try and unable to resolve org.apache.maven.skins:maven-default-skin:jar:RELEASE when
another skin is specified
> --------------------------------------------------------------------------------------------------------------
>
>                 Key: MSITE-228
>                 URL: http://jira.codehaus.org/browse/MSITE-228
>             Project: Maven 2.x Site Plugin
>          Issue Type: Bug
>    Affects Versions: 2.0-beta-5
>            Reporter: Stefano Bagnara
>
> 1) My project does not use external repositories for dependencies but only for plugins.
> 2) For dependencies I have a "stage" folder that is a "legacy structured" local repository
I reference this way:
> {code}<repository>
>       <id>local-james-stage-m1</id>
>       <name>Local James stage repository</name>
>       <url>file://c:/lab/void/projects/server-trunk-modular/stage</url>
>       <layout>legacy</layout>
>       <releases>
>         <enabled>true</enabled>
>         <checksumPolicy>ignore</checksumPolicy>
>       </releases>
>       <snapshots>
>         <enabled>true</enabled>
>         <checksumPolicy>ignore</checksumPolicy>
>       </snapshots>
>     </repository>{code}
> 3) in my site.xml I have this:
> {code}<skin>
>     <groupId>org.apache.james</groupId>
>     <artifactId>maven-skin</artifactId>
>     <version>1.1-SNAPSHOT</version>
>   </skin>{code}
> 4) and in my local stage repository I have the org.apache.james/poms/maven-skin-1.1-SNAPSHOT.pom
and org.apache.james/jars/maven-skin-1.1-SNAPSHOT.jar files.
> If I try to build the project, package it, run tests and everything else it works, but
when I try to build "mvn site" if fails with this error:
> {code}
> [DEBUG] maven-default-skin: using locally installed snapshot
> [INFO] ------------------------------------------------------------------------
> [ERROR] BUILD FAILURE
> [INFO] ------------------------------------------------------------------------
> [INFO] The skin does not exist: Unable to determine the release version
> Try downloading the file manually from the project website.
> Then, install it using the command:
>     mvn install:install-file -DgroupId=org.apache.maven.skins -DartifactId=maven-default-skin
\
>         -Dversion=RELEASE -Dpackaging=jar -Dfile=/path/to/file
>   org.apache.maven.skins:maven-default-skin:jar:RELEASE
> [INFO] ------------------------------------------------------------------------
> [DEBUG] Trace
> org.apache.maven.BuildFailureException: The skin does not exist: Unable to determine
the release version
> Try downloading the file manually from the project website.
> Then, install it using the command:
>     mvn install:install-file -DgroupId=org.apache.maven.skins -DartifactId=maven-default-skin
\
>         -Dversion=RELEASE -Dpackaging=jar -Dfile=/path/to/file
>   org.apache.maven.skins:maven-default-skin:jar:RELEASE
>         at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:560)
>         at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:480)
>         at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:459)
>         at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311)
>         at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:278)
>         at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143)
>         at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334)
>         at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125)
>         at org.apache.maven.cli.MavenCli.main(MavenCli.java:272)
>         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>         at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>         at java.lang.reflect.Method.invoke(Method.java:585)
>         at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
>         at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
>         at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
>         at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
> Caused by: org.apache.maven.plugin.MojoFailureException: The skin does not exist: Unable
to determine the release version
> Try downloading the file manually from the project website.
> Then, install it using the command:
>     mvn install:install-file -DgroupId=org.apache.maven.skins -DartifactId=maven-default-skin
\
>         -Dversion=RELEASE -Dpackaging=jar -Dfile=/path/to/file
>   org.apache.maven.skins:maven-default-skin:jar:RELEASE
>         at org.apache.maven.plugins.site.AbstractSiteRenderingMojo.getSkinArtifactFile(AbstractSiteRenderingMojo.java:372)
>         at org.apache.maven.plugins.site.AbstractSiteRenderingMojo.createSiteRenderingContext(AbstractSiteRenderingMojo.java:442)
>         at org.apache.maven.plugins.site.SiteMojo.renderLocale(SiteMojo.java:108)
>         at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:92)
>         at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:443)
>         at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539)
>         ... 16 more
> {code}
> I also tried adding to my stage folder the file org.apache.maven.skins/jars/maven-default-skin-1.0.jar
and org.apache.maven.skins/poms/maven-default-skin-1.0.pom but it doesn't find the artifact
anyway.
> Why does it need the default skin when I specified a custome skin? How can I tell maven
the version of the default skin (1.0) so it doesn't lookup for "RELEASE"?
> Otherwise, how can I solve this issue without using remote repositories or changing my
local stage folder to another structure (m2 repository with release number properties, I guess)?

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message