jira.codehaus.org

  • Log In Access more options
    • Online Help
    • Keyboard Shortcuts
    • About JIRA
    • JIRA Credits
    • What?s New
  • Dashboards Access more options (Alt+d)
  • Projects Access more options (Alt+p)
  • Issues Access more options (Alt+i)
  • Maven 2.x and 3.x Site Plugin
  • MSITE-48

add reusable skin functionality and create skins default, stylus and classic

  • Log In
  • Views
    • XML
    • Word
    • Printable

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: None
  • Fix Version/s: 2.0-beta-5
  • Component/s: None
  • Labels:
    None

Description

add the classic theme from m1, and perhaps a derivative of the new theme for other sites

Issue Links

is depended upon by

Task - A task that needs to be done. MNG-1212 apply new style to plugins sites

  • Major - Major loss of function.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.

Activity

Ascending order - Click to sort in descending order
  • All
  • Comments
  • Work Log
  • History
  • Activity
Hide
Permalink
Jason van Zyl added a comment - 30/Oct/05 1:07 PM

The themes needs to be packaged up in a jar/zip so that it can easily be retrieved and applied to a site. Applying the new look and feel to all the Maven sites was tedious.

Show
Jason van Zyl added a comment - 30/Oct/05 1:07 PM The themes needs to be packaged up in a jar/zip so that it can easily be retrieved and applied to a site. Applying the new look and feel to all the Maven sites was tedious.
Hide
Permalink
Jason van Zyl added a comment - 30/Oct/05 1:08 PM

Before applying simply pack up the theme in a JAR so it can be easily applied.

Show
Jason van Zyl added a comment - 30/Oct/05 1:08 PM Before applying simply pack up the theme in a JAR so it can be easily applied.
Hide
Permalink
John Casey added a comment - 11/Nov/05 12:02 PM

so, themes that are like archetypes in terms of packaging, distribution, and reference?

Show
John Casey added a comment - 11/Nov/05 12:02 PM so, themes that are like archetypes in terms of packaging, distribution, and reference?
Hide
Permalink
Brett Porter added a comment - 12/Nov/05 2:48 AM

currently the theming is just an alternate stylesheet, but I think want Jason wants to do is zip up a set of images related to the css, the css and perhaps the velocity template if it is different?

Show
Brett Porter added a comment - 12/Nov/05 2:48 AM currently the theming is just an alternate stylesheet, but I think want Jason wants to do is zip up a set of images related to the css, the css and perhaps the velocity template if it is different?
Hide
Permalink
Brett Porter added a comment - 21/Dec/05 11:44 PM

http://docs.codehaus.org/display/MAVEN/Sites+and+Inheritence

Show
Brett Porter added a comment - 21/Dec/05 11:44 PM http://docs.codehaus.org/display/MAVEN/Sites+and+Inheritence
Hide
Permalink
Matthew Beermann added a comment - 17/Jan/06 2:28 PM

Might be a stupid question, but... if this bug is fixed, where do the skins reside, exactly? If I enable the snapshots.maven.codehaus.org pluginRepository and attempt to run the site:site goal, it dies with the error:

[INFO] artifact org.apache.maven.skins:maven-default-skin: checking for updates from central
[INFO] ----------------------------------------------------------------------------
[ERROR] BUILD FAILURE
[INFO] ----------------------------------------------------------------------------
[INFO] The skin does not exist: Unable to determine the release version

org.apache.maven.skins:maven-default-skin:jar:RELEASE

Show
Matthew Beermann added a comment - 17/Jan/06 2:28 PM Might be a stupid question, but... if this bug is fixed, where do the skins reside, exactly? If I enable the snapshots.maven.codehaus.org pluginRepository and attempt to run the site:site goal, it dies with the error: [INFO] artifact org.apache.maven.skins:maven-default-skin: checking for updates from central [INFO] ---------------------------------------------------------------------------- [ERROR] BUILD FAILURE [INFO] ---------------------------------------------------------------------------- [INFO] The skin does not exist: Unable to determine the release version org.apache.maven.skins:maven-default-skin:jar:RELEASE
Hide
Permalink
Dennis Lundberg added a comment - 17/Jan/06 3:04 PM

The skin functionality in maven-site-plugin is done, but not yet released. The same goes for the skins. Until they are released you need to add a SNAPSHOT-version to them, like this:

<skin>
<groupId>org.apache.maven.skins</groupId>
<artifactId>maven-site-skin</artifactId>
<version>1.0-SNAPSHOT</version>
</skin>

Show
Dennis Lundberg added a comment - 17/Jan/06 3:04 PM The skin functionality in maven-site-plugin is done, but not yet released. The same goes for the skins. Until they are released you need to add a SNAPSHOT-version to them, like this: <skin> <groupId>org.apache.maven.skins</groupId> <artifactId>maven-site-skin</artifactId> <version>1.0-SNAPSHOT</version> </skin>
Hide
Permalink
Michael Phillimore-Brown added a comment - 11/Mar/08 5:37 AM

I also had this error, so to help anyone else looking for this my issue was that the maven-metadata-central.xml file in the repo under org/apache/maven/skins/maven-default-skin did not have the versioning element. This may have been as a result of some old cached file somewhere.

The complete file (as per http://repo1.maven.org/maven2/org/apache/maven/skins/maven-default-skin/maven-metadata.xml) is below.

<?xml version="1.0" encoding="UTF-8"?><metadata>
<groupId>org.apache.maven.skins</groupId>
<artifactId>maven-default-skin</artifactId>
<version>1.0</version>
<versioning>
<release>1.0</release>
<versions>
<version>1.0</version>
</versions>
<lastUpdated>20060507032433</lastUpdated>
</versioning>
</metadata>

See also MNG-3139

Show
Michael Phillimore-Brown added a comment - 11/Mar/08 5:37 AM I also had this error, so to help anyone else looking for this my issue was that the maven-metadata-central.xml file in the repo under org/apache/maven/skins/maven-default-skin did not have the versioning element. This may have been as a result of some old cached file somewhere. The complete file (as per http://repo1.maven.org/maven2/org/apache/maven/skins/maven-default-skin/maven-metadata.xml) is below. <?xml version="1.0" encoding="UTF-8"?><metadata> <groupId>org.apache.maven.skins</groupId> <artifactId>maven-default-skin</artifactId> <version>1.0</version> <versioning> <release>1.0</release> <versions> <version>1.0</version> </versions> <lastUpdated>20060507032433</lastUpdated> </versioning> </metadata> See also MNG-3139

People

  • Assignee:
    Brett Porter
    Reporter:
    Brett Porter
Vote (0)
Watch (1)

Dates

  • Created:
    22/Sep/05 11:43 PM
    Updated:
    11/Mar/08 5:37 AM
    Resolved:
    29/Dec/05 1:26 AM

Time Tracking

Estimated:
4h
Original Estimate - 4 hours
Remaining:
0m
Remaining Estimate - 0 minutes
Logged:
4h
Time Spent - 4 hours
  • Atlassian JIRA (v5.0.4#731-sha1:3aa7374)
  • Report a problem
  • Powered by a free Atlassian JIRA open source license for Codehaus. Try JIRA - bug tracking software for your team.