[jira] (MSKINS-30) Validate generated site as XHTML 1.0 Transitional
Bruno P. Kinoshita created MSKINS-30: Summary: Validate generated site as XHTML 1.0 Transitional Key: MSKINS-30 URL: https://jira.codehaus.org/browse/MSKINS-30 Project: Maven Skins Issue Type: Improvement Components: Fluido Skin Affects Versions: fluido-1.1 Reporter: Bruno P. Kinoshita Priority: Trivial Attachments: patch1 The W3C validator for HTML complains about few issues in the site generated by Maven Fluido Skin. Attached you can find a patch that: - includes alt element in the banner image - includes type attribute in style element - replaces footer element (HTML5 only) by a class with class footer - required CSS changes to maintain the same UI -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MSKINS-30) Validate generated site as XHTML 1.0 Transitional
[ https://jira.codehaus.org/browse/MSKINS-30?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bruno P. Kinoshita updated MSKINS-30: - Attachment: MSKINS-30.patch > Validate generated site as XHTML 1.0 Transitional > - > > Key: MSKINS-30 > URL: https://jira.codehaus.org/browse/MSKINS-30 > Project: Maven Skins > Issue Type: Improvement > Components: Fluido Skin >Affects Versions: fluido-1.1 >Reporter: Bruno P. Kinoshita >Priority: Trivial > Attachments: MSKINS-30.patch, patch1 > > > The W3C validator for HTML complains about few issues in the site generated > by Maven Fluido Skin. Attached you can find a patch that: > - includes alt element in the banner image > - includes type attribute in style element > - replaces footer element (HTML5 only) by a class with class footer > - required CSS changes to maintain the same UI -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MSKINS-30) Validate generated site as XHTML 1.0 Transitional
[ https://jira.codehaus.org/browse/MSKINS-30?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=293821#comment-293821 ] Bruno P. Kinoshita commented on MSKINS-30: -- Ignore patch1, please. Sorry for the noise. > Validate generated site as XHTML 1.0 Transitional > - > > Key: MSKINS-30 > URL: https://jira.codehaus.org/browse/MSKINS-30 > Project: Maven Skins > Issue Type: Improvement > Components: Fluido Skin >Affects Versions: fluido-1.1 >Reporter: Bruno P. Kinoshita >Priority: Trivial > Attachments: MSKINS-30.patch, patch1 > > > The W3C validator for HTML complains about few issues in the site generated > by Maven Fluido Skin. Attached you can find a patch that: > - includes alt element in the banner image > - includes type attribute in style element > - replaces footer element (HTML5 only) by a class with class footer > - required CSS changes to maintain the same UI -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MSKINS-26) hard coded style with padding-top for body
[
https://jira.codehaus.org/browse/MSKINS-26?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bruno P. Kinoshita updated MSKINS-26:
-
Attachment: MSKINS-26.patch
This patch includes a CSS class with the padding required for the body. It also
adds a class to the body tag.
Not sure if the changes in the CSS are in the right file (maven-theme,
maven-base?). Feel free to change the patch :-)
Cheers
> hard coded style with padding-top for body
> --
>
> Key: MSKINS-26
> URL: https://jira.codehaus.org/browse/MSKINS-26
> Project: Maven Skins
> Issue Type: Bug
> Components: Fluido Skin
>Affects Versions: fluido-1.0
>Reporter: Olivier Lamy
> Attachments: MSKINS-26.patch
>
>
> there is an hardcoded
> {code:xml}
> body{padding-top: 20px;}
> {code}
> It's impossible to not have it generated
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MSKINS-28) Make it possible to center "powered by" logos in sidebar
[
https://jira.codehaus.org/browse/MSKINS-28?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=293827#comment-293827
]
Bruno P. Kinoshita commented on MSKINS-28:
--
Hello, in order to center align the powered-by logos, you can create a custom
site.css in src/resources/css/site.css. Inside this file, put the following CSS:
#poweredBy {
text-align: center;
}
It will align the powered-by logos, without the need to change the skin's code
:-)
Hope that helps.
> Make it possible to center "powered by" logos in sidebar
>
>
> Key: MSKINS-28
> URL: https://jira.codehaus.org/browse/MSKINS-28
> Project: Maven Skins
> Issue Type: Wish
> Components: Fluido Skin
>Affects Versions: fluido-1.1
>Reporter: Andreas Sewe
>Priority: Minor
>
> Left alignment may look OK for badge-like logos like
> ,
> but is quite ugly for other types of logo.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MDEPLOY-177) Maven release:perform hangs when downloading maven-metadata.xml
[
https://jira.codehaus.org/browse/MDEPLOY-177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=343897#comment-343897
]
Bruno P. Kinoshita commented on MDEPLOY-177:
Maybe you could try to reproduce this line:
scp://cloudportal.open-bio.org/home/websites/biojava.org/html/static/download/maven/org/biojava/biojava-legacy/1.8.6-SNAPSHOT/maven-metadata.xml
It is a shot in the dark, but *I think* what it doing is downloading via scp
the
`scp -vvv
mhe...@cloudportal.open-bio.org:/home/websites/biojava.org/html/static/download/maven/org/biojava/biojava-legacy/1.8.6-SNAPSHOT/maven-metadata.xml
.`
The -vvv is the highest debug level for scp if I recall correctly.
Just my 0.02 cents or BRL :)
> Maven release:perform hangs when downloading maven-metadata.xml
> ---
>
> Key: MDEPLOY-177
> URL: https://jira.codehaus.org/browse/MDEPLOY-177
> Project: Maven Deploy Plugin
> Issue Type: Bug
> Components: deploy:deploy
>Affects Versions: 2.8.1
> Environment: $ mvn -v
> Apache Maven 3.2.1 (ea8b2b07643dbb1b84b6d16e1f08391b666bc1e9;
> 2014-02-14T11:37:52-06:00)
> Maven home: /usr/local/Cellar/maven/3.2.1/libexec
> Java version: 1.7.0_51, vendor: Oracle Corporation
> Java home: /Library/Java/JavaVirtualMachines/jdk1.7.0_51.jdk/Contents/Home/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "mac os x", version: "10.9.2", arch: "x86_64", family: "mac"
>Reporter: Michael Heuer
>Priority: Critical
> Attachments: deploy-debug.txt, release-perform-debug.txt
>
>
> When attempting to mvn release:perform
> {code:none}
> $ mvn release:perform
> ...
> [INFO] [INFO]
>
> [INFO] [INFO] Building biojava-legacy 1.8.5
> [INFO] [INFO]
>
> [INFO] [INFO]
> [INFO] [INFO] >>> maven-source-plugin:2.2.1:jar (attach-sources) @
> biojava-legacy >>>
> [INFO] [INFO]
> [INFO] [INFO] <<< maven-source-plugin:2.2.1:jar (attach-sources) @
> biojava-legacy <<<
> [INFO] [INFO]
> [INFO] [INFO] --- maven-source-plugin:2.2.1:jar (attach-sources) @
> biojava-legacy ---
> [INFO] [INFO]
> [INFO] [INFO] --- maven-javadoc-plugin:2.9.1:jar (attach-javadocs) @
> biojava-legacy ---
> [INFO] [INFO] Not executing Javadoc as the project is not a Java
> classpath-capable package
> [INFO] [INFO]
> [INFO] [INFO] --- maven-install-plugin:2.4:install (default-install) @
> biojava-legacy ---
> [INFO] [INFO] Installing
> /Users/xxx/working/biojava-legacy/target/checkout/pom.xml to
> /Users/xxx/.m2/repository/org/biojava/biojava-legacy/1.8.5/biojava-legacy-1.8.5.pom
> [INFO] [INFO]
> [INFO] [INFO] --- maven-deploy-plugin:2.8.1:deploy (default-deploy) @
> biojava-legacy ---
> [INFO] Uploading:
> scp://cloudportal.open-bio.org/home/websites/biojava.org/html/static/download/maven/org/biojava/biojava-legacy/1.8.5/biojava-legacy-1.8.5.pom
> [INFO] 4/9 KB
> [INFO] 8/9 KB
> [INFO] 9/9 KB
> [INFO]
> [INFO] Uploaded:
> scp://cloudportal.open-bio.org/home/websites/biojava.org/html/static/download/maven/org/biojava/biojava-legacy/1.8.5/biojava-legacy-1.8.5.pom
> (9 KB at 3.0 KB/sec)
> [INFO] Downloading:
> scp://cloudportal.open-bio.org/home/websites/biojava.org/html/static/download/maven/org/biojava/biojava-legacy/maven-metadata.xml
> [INFO] 750/750 B
> [INFO] 751/750 B
> {code}
> the build hangs at this point. It appears there might be a difference
> between the expected file size and the downloaded file size, but no
> warning/error messages appear, the build just hangs.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MDEPLOY-177) Maven release:perform hangs when downloading maven-metadata.xml
[
https://jira.codehaus.org/browse/MDEPLOY-177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=343918#comment-343918
]
Bruno P. Kinoshita commented on MDEPLOY-177:
Hi Michael, that's exactly what I meant (though coffee-less-me didn't phrase
that very well :-) Thanks
> Maven release:perform hangs when downloading maven-metadata.xml
> ---
>
> Key: MDEPLOY-177
> URL: https://jira.codehaus.org/browse/MDEPLOY-177
> Project: Maven Deploy Plugin
> Issue Type: Bug
> Components: deploy:deploy
>Affects Versions: 2.8.1
> Environment: $ mvn -v
> Apache Maven 3.2.1 (ea8b2b07643dbb1b84b6d16e1f08391b666bc1e9;
> 2014-02-14T11:37:52-06:00)
> Maven home: /usr/local/Cellar/maven/3.2.1/libexec
> Java version: 1.7.0_51, vendor: Oracle Corporation
> Java home: /Library/Java/JavaVirtualMachines/jdk1.7.0_51.jdk/Contents/Home/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "mac os x", version: "10.9.2", arch: "x86_64", family: "mac"
>Reporter: Michael Heuer
>Priority: Critical
> Attachments: deploy-debug.txt, release-perform-debug.txt
>
>
> When attempting to mvn release:perform
> {code:none}
> $ mvn release:perform
> ...
> [INFO] [INFO]
>
> [INFO] [INFO] Building biojava-legacy 1.8.5
> [INFO] [INFO]
>
> [INFO] [INFO]
> [INFO] [INFO] >>> maven-source-plugin:2.2.1:jar (attach-sources) @
> biojava-legacy >>>
> [INFO] [INFO]
> [INFO] [INFO] <<< maven-source-plugin:2.2.1:jar (attach-sources) @
> biojava-legacy <<<
> [INFO] [INFO]
> [INFO] [INFO] --- maven-source-plugin:2.2.1:jar (attach-sources) @
> biojava-legacy ---
> [INFO] [INFO]
> [INFO] [INFO] --- maven-javadoc-plugin:2.9.1:jar (attach-javadocs) @
> biojava-legacy ---
> [INFO] [INFO] Not executing Javadoc as the project is not a Java
> classpath-capable package
> [INFO] [INFO]
> [INFO] [INFO] --- maven-install-plugin:2.4:install (default-install) @
> biojava-legacy ---
> [INFO] [INFO] Installing
> /Users/xxx/working/biojava-legacy/target/checkout/pom.xml to
> /Users/xxx/.m2/repository/org/biojava/biojava-legacy/1.8.5/biojava-legacy-1.8.5.pom
> [INFO] [INFO]
> [INFO] [INFO] --- maven-deploy-plugin:2.8.1:deploy (default-deploy) @
> biojava-legacy ---
> [INFO] Uploading:
> scp://cloudportal.open-bio.org/home/websites/biojava.org/html/static/download/maven/org/biojava/biojava-legacy/1.8.5/biojava-legacy-1.8.5.pom
> [INFO] 4/9 KB
> [INFO] 8/9 KB
> [INFO] 9/9 KB
> [INFO]
> [INFO] Uploaded:
> scp://cloudportal.open-bio.org/home/websites/biojava.org/html/static/download/maven/org/biojava/biojava-legacy/1.8.5/biojava-legacy-1.8.5.pom
> (9 KB at 3.0 KB/sec)
> [INFO] Downloading:
> scp://cloudportal.open-bio.org/home/websites/biojava.org/html/static/download/maven/org/biojava/biojava-legacy/maven-metadata.xml
> [INFO] 750/750 B
> [INFO] 751/750 B
> {code}
> the build hangs at this point. It appears there might be a difference
> between the expected file size and the downloaded file size, but no
> warning/error messages appear, the build just hangs.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
