You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Graham Leggett <mi...@sharp.fm> on 2007/10/05 13:12:23 UTC
The skin does not exist: Unable to determine the release version
Hi all,
Out of the blue this morning, our maven docs build is suddenly failing
like below.
Doing a search in our project for maven-default-skin comes up with
nothing, and doing help:effective-pom also shows up no references to
help:effective-pom.
A Google search shows up this problem as having something to do with
SNAPSHOTs, but no clear answer has been found. We have encountered this
error in the past, and a clean rebuild usually makes it go away, but not
this time for no clear reason.
Can someone describe how to make this error go away permanently once and
for all?
[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
Alternatively, if you host your own repository you can deploy the file
there: mvn deploy:deploy-file -DgroupId=org.apache.maven.skins
-DartifactId=maven-default-skin \
-Dversion=RELEASE -Dpackaging=jar -Dfile=/path/to/file \
-Durl=[url] -DrepositoryId=[id]
org.apache.maven.skins:maven-default-skin:jar:RELEASE
The site plugin is configured like so:
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-site-plugin</artifactId>
<version>2.0-beta-5</version>
<configuration>
<siteDirectory>${basedir}</siteDirectory>
</configuration>
</plugin>
Regards,
Graham
--
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: The skin does not exist: Unable to determine the release
version
Posted by Graham Leggett <mi...@sharp.fm>.
On Fri, October 5, 2007 7:12 pm, Dennis Lundberg wrote:
> Judging by the error message, you have not specified a version for the
> skin you are using. If you specify the version I think you will get
> around this problem.
I have already found this workaround, but this is not a solution.
The default behaviour of the site plugin is broken, as it does not produce
a repeatable or reliable build.
A new person taking over the project who creates a new artifact without
the kludge workaround is then forced to run into the same problem, which
is why when you search on Google for this problem you find mystified posts
from people trying to figure out why maven just "doesn't work".
Leaving this bug unfixed is not doing maven any favours.
Regards,
Graham
--
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: The skin does not exist: Unable to determine the release version
Posted by Barrie Treloar <ba...@gmail.com>.
Apologies for dragging up an old post, but I have been using the
maven-invoker-plugin with Maven 2.2.1 and I get the same error.
So other people can find a google response, I followed the same
instructions here to create a src/site/site.xml which specifies the
skin for each of my IT projects.
I'm not sure how http://jira.codehaus.org/browse/MNG-3139 relates to
the invoker plugin.
On Tue, Oct 9, 2007 at 6:55 AM, Dennis Lundberg <de...@apache.org> wrote:
> Graham, we need more details to be able to say anything.
>
> Graham Leggett wrote:
>>
>> On Fri, October 5, 2007 7:12 pm, Dennis Lundberg wrote:
>>
>>> Judging by the error message, you have not specified a version for the
>>> skin you are using. If you specify the version I think you will get
>>> around this problem. Here's how, just put this in your site.xml
>>>
>>> <project>
>>> ...
>>> <skin>
>>> <groupId>org.apache.maven.skins</groupId>
>>> <artifactId>maven-classic-skin</artifactId>
>>> <version>1.0</version>
>>> </skin>
>>> ...
>>> </project>
>>
>> Having just tried this out, I am still getting random failures even when a
>> site.xml file is specified for the root pom of a multi-module project.
>>
>> It would seem that whatever changed in the repository on friday, it has
>> broken the site plugin, and we have been forced to disable all generation
>> of documentation as it kept breaking our build.
>>
>> Does anyone have any insight on what may be causing this issue?
>>
>> Regards,
>> Graham
>> --
>
>
> --
> Dennis Lundberg
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: The skin does not exist: Unable to determine the release
version
Posted by Dennis Lundberg <de...@apache.org>.
Graham, we need more details to be able to say anything.
Graham Leggett wrote:
> On Fri, October 5, 2007 7:12 pm, Dennis Lundberg wrote:
>
>> Judging by the error message, you have not specified a version for the
>> skin you are using. If you specify the version I think you will get
>> around this problem. Here's how, just put this in your site.xml
>>
>> <project>
>> ...
>> <skin>
>> <groupId>org.apache.maven.skins</groupId>
>> <artifactId>maven-classic-skin</artifactId>
>> <version>1.0</version>
>> </skin>
>> ...
>> </project>
>
> Having just tried this out, I am still getting random failures even when a
> site.xml file is specified for the root pom of a multi-module project.
>
> It would seem that whatever changed in the repository on friday, it has
> broken the site plugin, and we have been forced to disable all generation
> of documentation as it kept breaking our build.
>
> Does anyone have any insight on what may be causing this issue?
>
> Regards,
> Graham
> --
--
Dennis Lundberg
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: The skin does not exist: Unable to determine the release
version
Posted by Graham Leggett <mi...@sharp.fm>.
On Fri, October 5, 2007 7:12 pm, Dennis Lundberg wrote:
> Judging by the error message, you have not specified a version for the
> skin you are using. If you specify the version I think you will get
> around this problem. Here's how, just put this in your site.xml
>
> <project>
> ...
> <skin>
> <groupId>org.apache.maven.skins</groupId>
> <artifactId>maven-classic-skin</artifactId>
> <version>1.0</version>
> </skin>
> ...
> </project>
Having just tried this out, I am still getting random failures even when a
site.xml file is specified for the root pom of a multi-module project.
It would seem that whatever changed in the repository on friday, it has
broken the site plugin, and we have been forced to disable all generation
of documentation as it kept breaking our build.
Does anyone have any insight on what may be causing this issue?
Regards,
Graham
--
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: The skin does not exist: Unable to determine the release version
Posted by Dennis Lundberg <de...@apache.org>.
Judging by the error message, you have not specified a version for the
skin you are using. If you specify the version I think you will get
around this problem. Here's how, just put this in your site.xml
<project>
...
<skin>
<groupId>org.apache.maven.skins</groupId>
<artifactId>maven-classic-skin</artifactId>
<version>1.0</version>
</skin>
...
</project>
You can read more on this page:
http://maven.apache.org/plugins/maven-site-plugin/examples/sitedescriptor.html
Graham Leggett wrote:
> Hi all,
>
> Out of the blue this morning, our maven docs build is suddenly failing
> like below.
>
> Doing a search in our project for maven-default-skin comes up with
> nothing, and doing help:effective-pom also shows up no references to
> help:effective-pom.
>
> A Google search shows up this problem as having something to do with
> SNAPSHOTs, but no clear answer has been found. We have encountered this
> error in the past, and a clean rebuild usually makes it go away, but not
> this time for no clear reason.
>
> Can someone describe how to make this error go away permanently once and
> for all?
>
> [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
> Alternatively, if you host your own repository you can deploy the file
> there: mvn deploy:deploy-file -DgroupId=org.apache.maven.skins
> -DartifactId=maven-default-skin \
> -Dversion=RELEASE -Dpackaging=jar -Dfile=/path/to/file \
> -Durl=[url] -DrepositoryId=[id]
>
>
> org.apache.maven.skins:maven-default-skin:jar:RELEASE
>
> The site plugin is configured like so:
>
> <plugin>
> <groupId>org.apache.maven.plugins</groupId>
> <artifactId>maven-site-plugin</artifactId>
> <version>2.0-beta-5</version>
> <configuration>
> <siteDirectory>${basedir}</siteDirectory>
> </configuration>
> </plugin>
>
> Regards,
> Graham
> --
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
--
Dennis Lundberg
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: The skin does not exist: Unable to determine the release
version
Posted by Matthew McCullough <ma...@ambientideas.com>.
Believe it or not, I trolled some forums and found a solution that works for
me. I have to create a dummy site.xml in the src/main/site directory that
defines the skin version. Amazing.
In my case, it is triggered by moving the site plugin to an internal
repository. When I use the external repository (central), it somehow
resolves this on its own. Move it inside the company to our private repo,
and bam, I have to create these annoying site.xml files to "force" the
version of the skin.
Let me know if you are able to refine my findings further. Hopefully, a
quick site.xml creation will solve the issue for you as a workaround.
-Matthew McCullough
Ambient Ideas,
www.ambientideas.com
Graham Leggett wrote:
>
> Hi all,
>
> Out of the blue this morning, our maven docs build is suddenly failing
> like below.
>
> Doing a search in our project for maven-default-skin comes up with
> nothing, and doing help:effective-pom also shows up no references to
> help:effective-pom.
>
> A Google search shows up this problem as having something to do with
> SNAPSHOTs, but no clear answer has been found. We have encountered this
> error in the past, and a clean rebuild usually makes it go away, but not
> this time for no clear reason.
>
> Can someone describe how to make this error go away permanently once and
> for all?
>
> [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
> Alternatively, if you host your own repository you can deploy the file
> there: mvn deploy:deploy-file -DgroupId=org.apache.maven.skins
> -DartifactId=maven-default-skin \
> -Dversion=RELEASE -Dpackaging=jar -Dfile=/path/to/file \
> -Durl=[url] -DrepositoryId=[id]
>
>
> org.apache.maven.skins:maven-default-skin:jar:RELEASE
>
> The site plugin is configured like so:
>
> <plugin>
> <groupId>org.apache.maven.plugins</groupId>
> <artifactId>maven-site-plugin</artifactId>
> <version>2.0-beta-5</version>
> <configuration>
> <siteDirectory>${basedir}</siteDirectory>
> </configuration>
> </plugin>
>
> Regards,
> Graham
> --
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
>
--
View this message in context: http://www.nabble.com/The-skin-does-not-exist%3A-Unable-to-determine-the-release-version-tf4574534s177.html#a13065938
Sent from the Maven - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org