[jira] Commented: (MRELEASE-695) tagNameFormat with @{project.version} tags the SNAPSHOT version
[
https://jira.codehaus.org/browse/MRELEASE-695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=273811#comment-273811
]
Aristedes Maniatis commented on MRELEASE-695:
-
I can confirm. And I just wasted the last 3 hours of my life on this very
simple bug. This makes the release plugin 2.2 very broken and almost useless
for any regular user, since the tag created when you don't override
tagNameFormat is incorrect. If you are re-using the same snapshot version (eg.
2.0b1 -> 2.0-SNAPSHOT -> 2.0b2 -> 2.0-SNAPSHOT) then everything breaks when the
release cannot create the incorrect tag.
Downgrading to 2.1 solves the problem.
> tagNameFormat with @{project.version} tags the SNAPSHOT version
> ---
>
> Key: MRELEASE-695
> URL: https://jira.codehaus.org/browse/MRELEASE-695
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
>Affects Versions: 2.2
>Reporter: Fabrizio Giudici
>
> The much awaited (by me) MRELEASE-159 seems not to work. I tried a release
> with the following pom:
>
> org.apache.maven.plugins
> maven-release-plugin
>
> true
> clean install verify
> clean install javadoc:javadoc assembly:assembly
> deploy
> -P${release.profiles}
> -DaltDeploymentRepository="${altDeploymentRepository}"
> @{project.version}
>
>
> but I got the tag 1.0-ALPHA-2-SNAPSHOT in place of 1.0-ALPHA-2.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MSITE-577) generateReports still copies css and images folders
generateReports still copies css and images folders --- Key: MSITE-577 URL: http://jira.codehaus.org/browse/MSITE-577 Project: Maven 2.x and 3.x Site Plugin Issue Type: Bug Affects Versions: 3.0-beta-3 Reporter: Aristedes Maniatis With this config: false all the reports are stopped, but the css and images folders are still copied. These should not be copied over since there is no html for which they are relevant. Not having these folders in place is very useful if we are using the site phase for documentation generated by other means (and we still want to take advantage of things like the site-deploy). -- 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
[jira] Commented: (MSITE-577) generateReports still copies css and images folders
[ http://jira.codehaus.org/browse/MSITE-577?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=262308#action_262308 ] Aristedes Maniatis commented on MSITE-577: -- Do the customised files in src/site/apt require the default report images and style sheets? > generateReports still copies css and images folders > --- > > Key: MSITE-577 > URL: http://jira.codehaus.org/browse/MSITE-577 > Project: Maven 2.x and 3.x Site Plugin > Issue Type: Bug >Affects Versions: 3.0-beta-3 >Reporter: Aristedes Maniatis > > With this config: > > false > > all the reports are stopped, but the css and images folders are still copied. > These should not be copied over since there is no html for which they are > relevant. Not having these folders in place is very useful if we are using > the site phase for documentation generated by other means (and we still want > to take advantage of things like the site-deploy). -- 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
[jira] Commented: (MSITE-577) generateReports still copies css and images folders
[ http://jira.codehaus.org/browse/MSITE-577?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=262340#action_262340 ] Aristedes Maniatis commented on MSITE-577: -- Like so much of maven, the documentation is very sparse. I can't see anywhere on that page how the css/images for the reporting functionality relates to files inside src/site/apt. The best docs about skins (which I understand at a basic level) I found are http://www.coderoshi.com/2007/02/generating-site-and-documentation-in.html That still doesn't give us a list of the basic images/css files, although it suggests how you can override them one at a time. It doesn't tell us how to make them go away. Anyhow, this task is a simple one: if you suppress all report generation and you have nothing in /site/apt then all you get generated is a couple of useless folders images and css. Since I'm trying to subvert the whole maven site generation concept (I've got everything in docbook) I just want maven to get out of the way. But I still want to take advantage of the site:deploy functionality which is useful. > generateReports still copies css and images folders > --- > > Key: MSITE-577 > URL: http://jira.codehaus.org/browse/MSITE-577 > Project: Maven 2.x and 3.x Site Plugin > Issue Type: Bug >Affects Versions: 3.0-beta-3 >Reporter: Aristedes Maniatis > > With this config: > > false > > all the reports are stopped, but the css and images folders are still copied. > These should not be copied over since there is no html for which they are > relevant. Not having these folders in place is very useful if we are using > the site phase for documentation generated by other means (and we still want > to take advantage of things like the site-deploy). -- 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
[jira] Commented: (MSITE-577) generateReports still copies css and images folders
[ http://jira.codehaus.org/browse/MSITE-577?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=262347#action_262347 ] Aristedes Maniatis commented on MSITE-577: -- Sure (and I don't want to turn this bug tracker into a maven support forum). But I'm using site:site as the convenient goal for hooking in the docbook generation plugin (and other resource generation stuff I have). Ideally I'd extend the maven goals by adding in site:docbook, but I don't believe it is possible to add goals in this way without hacking at the core of maven. I guess there are other ways to solve this problem, and for now I've added in an ant plugin to delete the images/css files added by maven-site. But this isn't very robust since those files are liable to change with an upgrade of maven-site. Let me phrase this bug report in a different way. If you don't want to use the default skin. Can you make the default images/css go away? I can see ways to override the files one by one. But that's not what I had in mind. > generateReports still copies css and images folders > --- > > Key: MSITE-577 > URL: http://jira.codehaus.org/browse/MSITE-577 > Project: Maven 2.x and 3.x Site Plugin > Issue Type: Bug >Affects Versions: 3.0-beta-3 >Reporter: Aristedes Maniatis > > With this config: > > false > > all the reports are stopped, but the css and images folders are still copied. > These should not be copied over since there is no html for which they are > relevant. Not having these folders in place is very useful if we are using > the site phase for documentation generated by other means (and we still want > to take advantage of things like the site-deploy). -- 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
