[jira] (MSITE-699) Allow inclusion of files outside of src/site into the built site
[
https://jira.codehaus.org/browse/MSITE-699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Herve Boutemy updated MSITE-699:
Description:
I would like to have the capability of using README.md on the root of the
project as the index.html that gets generated.
This means it should also allow specifying which doxia to use.
I was thinking of
{code}{code}
was:
I would like to have the capability of using README.md on the root of the
project as the index.html that gets generated.
This means it should also allow specifying which doxia to use.
I was thinking of
> Allow inclusion of files outside of src/site into the built site
>
>
> Key: MSITE-699
> URL: https://jira.codehaus.org/browse/MSITE-699
> Project: Maven Site Plugin
> Issue Type: Improvement
>Affects Versions: 3.3
>Reporter: Archimedes Trajano
>
> I would like to have the capability of using README.md on the root of the
> project as the index.html that gets generated.
> This means it should also allow specifying which doxia to use.
> I was thinking of
> {code} />{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MSITE-699) Allow inclusion of files outside of src/site into the built site
[
https://jira.codehaus.org/browse/MSITE-699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=334445#comment-334445
]
Herve Boutemy commented on MSITE-699:
-
did you try including content using Velocity?
> Allow inclusion of files outside of src/site into the built site
>
>
> Key: MSITE-699
> URL: https://jira.codehaus.org/browse/MSITE-699
> Project: Maven Site Plugin
> Issue Type: Improvement
>Affects Versions: 3.3
>Reporter: Archimedes Trajano
>
> I would like to have the capability of using README.md on the root of the
> project as the index.html that gets generated.
> This means it should also allow specifying which doxia to use.
> I was thinking of
> {code} />{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MRELEASE-812) "prepare" does not commit before tagging and therefore deploys snapshot instead of release
[ https://jira.codehaus.org/browse/MRELEASE-812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=334448#comment-334448 ] Stefan Fleiter commented on MRELEASE-812: - Stumbled upon this and wasted several hours on it. Wanting to report the bug I see this one, known for far too long. What a shame! > "prepare" does not commit before tagging and therefore deploys snapshot > instead of release > -- > > Key: MRELEASE-812 > URL: https://jira.codehaus.org/browse/MRELEASE-812 > Project: Maven Release Plugin > Issue Type: Bug > Components: Git >Affects Versions: 2.4 >Reporter: Andrei Pozolotin >Priority: Critical > Attachments: mvn-2.3.2.txt, mvn-2.4.0.txt > > > thank you very much for new release! > http://mail-archives.apache.org/mod_mbox/maven-announce/201212.mbox/%3Cop.wpjbptp1kdkhrr@columbia%3E > it seems we need an emergency fix: > attached are 2 logs: > 1) mvn-2.3.2.txt invocation that works fine with 2.3.2 > 2) mvn-2.4.0.txt invocation that fails with 2.4 > problem: > "perform" does not commit tags, deploys snapshot instead of release > here is project parent: > http://search.maven.org/remotecontent?filepath=com/barchart/base/barchart-archon/2.3.6/barchart-archon-2.3.6.pom > build is invoked both times with this: > mvn --define resume=false release:prepare > mvn --define resume=false release:perform -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MJARSIGNER-13) signing in multi-module project fails on windows
[
https://jira.codehaus.org/browse/MJARSIGNER-13?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=334449#comment-334449
]
Kurt T Stam commented on MJARSIGNER-13:
---
Super Dennis, this fixed it for us! Cheers --Kurt
> signing in multi-module project fails on windows
>
>
> Key: MJARSIGNER-13
> URL: https://jira.codehaus.org/browse/MJARSIGNER-13
> Project: Maven Jar Signer Plugin
> Issue Type: Bug
>Affects Versions: 1.2
> Environment: Windows XP, android sdk
>Reporter: Anna Gadomska
> Attachments: pom.xml
>
>
> I got multi-module (6 modules) android project with .pom file and "sign"
> profile defined. When I execute with 'sign' profile:
> - in Maven 3.0.1 - it signs 3 modules and fails. when I resume the execution
> (mv -rf) it signs another 3 modules and fails again. The reason for
> failing is: [INFO] jarsigner: attempt to rename xxx.jar to xxx.jar.orig
> failed.
> - in Maven 2.2.1 - it doesn't work at all, even for first module; it returns
> "error code 1"
> However, I tried the same .pom - everything works perfectly in Linux
> (Ubuntu).
> I was afraid that it might be the issue with spaces, so I hardcoded the paths
> - the error I got from maven than was:
> {noformat}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-jarsigner-plugin:1.2:sign (signing) on project
> MyProject: Failed executing 'cmd.exe /X /C
> "C:\tools\JavaTMSEDevelopementKit\jre\..\bin\jarsigner.exe -verbose -keystore
> "C:\tmp\debug.keystore" -storepass '*' -keypass '*' xxx.jar
> '*'debugkey"' - exitcode 1 -> [Help 1]
> {noformat}
> Attaching pom file which I am using.
> Please help?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MINSTALL-100) Update description for installAtEnd param
Anders Hammar created MINSTALL-100: -- Summary: Update description for installAtEnd param Key: MINSTALL-100 URL: https://jira.codehaus.org/browse/MINSTALL-100 Project: Maven Install Plugin Issue Type: Bug Components: install:install Affects Versions: 2.5.1 Environment: online docs Reporter: Anders Hammar Reported on users list by Grzegorz Slowikowski: Whether every project should be deployed during its own deploy-phase or at the end of the multimodule build. If set to true and the build fails, none of the reactor projects is deployed Should be "installed", not "deployed". -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MINSTALL-100) Update description for installAtEnd param
[ https://jira.codehaus.org/browse/MINSTALL-100?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=334455#comment-334455 ] Anders Hammar commented on MINSTALL-100: It should also be "install phase" instead of "deploy-phase". > Update description for installAtEnd param > - > > Key: MINSTALL-100 > URL: https://jira.codehaus.org/browse/MINSTALL-100 > Project: Maven Install Plugin > Issue Type: Bug > Components: install:install >Affects Versions: 2.5.1 > Environment: online docs >Reporter: Anders Hammar > > Reported on users list by Grzegorz Slowikowski: > Whether every project should be deployed during its own deploy-phase or at > the end of the multimodule build. If set to true and the build fails, none > of the reactor projects is deployed > Should be "installed", not "deployed". -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
