[jira] (DOXIA-298) Confluence: Problem with relative links

[ https://jira.codehaus.org/browse/DOXIA-298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=300128#comment-300128 ] Valters Vingolds commented on DOXIA-298: It seems this patch breaks possibility to link to a

[jira] (DOXIA-466) confluence: can't create links to non-html resources (like .pdf of .xls files) because .html is always appended

Valters Vingolds created DOXIA-466: -- Summary: confluence: can't create links to non-html resources (like .pdf of .xls files) because .html is always appended Key: DOXIA-466 URL:

[jira] (DOXIA-298) Confluence: Problem with relative links

[ https://jira.codehaus.org/browse/DOXIA-298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=300140#comment-300140 ] Lukas Theussl commented on DOXIA-298: - Please open a new ticket, link back to this one and

[jira] (MRELEASE-766) release:prepare stores settings.xml in a public directory

[ https://jira.codehaus.org/browse/MRELEASE-766?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=300141#comment-300141 ] Robert Scholte commented on MRELEASE-766: - Have you seen this happening or is it just a

[jira] (MRELEASE-763) release:prepare ignores invalid dependencies in inactive profiles

[ https://jira.codehaus.org/browse/MRELEASE-763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte updated MRELEASE-763: Issue Type: Improvement (was: Bug) I see your point, but this means we have to do all the

[jira] (MRELEASE-761) [regression] release:rollback no longer works

[ https://jira.codehaus.org/browse/MRELEASE-761?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte reassigned MRELEASE-761: --- Assignee: Robert Scholte [regression] release:rollback no longer works

[jira] (MRELEASE-761) [regression] release:rollback no longer works

[ https://jira.codehaus.org/browse/MRELEASE-761?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte closed MRELEASE-761. --- Resolution: Fixed Fix Version/s: 2.4 Fixed in

[jira] (MRELEASE-635) perform does not honor updateWorkingCopiesVersion setting

[ https://jira.codehaus.org/browse/MRELEASE-635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=300145#comment-300145 ] Robert Scholte commented on MRELEASE-635: - I guess you meant {{release:prepare}}, right?

[jira] (MRELEASE-760) updateWorkingCopyVersions=false still bumps up pom versions to next development version

[ https://jira.codehaus.org/browse/MRELEASE-760?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte closed MRELEASE-760. --- Resolution: Fixed Fix Version/s: 2.4 Assignee: Robert Scholte Fixed in

[jira] (MRELEASE-674) release plugin converts explicit version to snapshot

[ https://jira.codehaus.org/browse/MRELEASE-674?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte reopened MRELEASE-674: - release plugin converts explicit version to snapshot

[jira] (MRELEASE-674) release plugin converts explicit version to snapshot

[ https://jira.codehaus.org/browse/MRELEASE-674?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte closed MRELEASE-674. --- Resolution: Fixed Sounds to me you should use {{updateWorkingCopyVersions=false}}. MRELEASE-760

[jira] (MRELEASE-674) release plugin converts explicit version to snapshot

[ https://jira.codehaus.org/browse/MRELEASE-674?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte closed MRELEASE-674. --- Resolution: Won't Fix Fix Version/s: (was: 2.4) Marking this as {{won't fix}}, since

[jira] (MRELEASE-525) Update-versions does not work in batch mode

[ https://jira.codehaus.org/browse/MRELEASE-525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=300149#comment-300149 ] Robert Scholte commented on MRELEASE-525: - Could this be a duplicate of MRELEASE-760?

[jira] (MRELEASE-766) release:prepare stores settings.xml in a public directory

[ https://jira.codehaus.org/browse/MRELEASE-766?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=300153#comment-300153 ] Joseph Walton commented on MRELEASE-766: I've seen it happening. It's possible that the

[jira] (MPLUGIN-109) Misleading warning when creating a Maven plugin defining a custom packaging

[ https://jira.codehaus.org/browse/MPLUGIN-109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=300156#comment-300156 ] Brett Porter commented on MPLUGIN-109: -- This is no longer the case - you can configure

[jira] (MSHADE-103) maven-shade-plugin does not resolve from user-defined repositories

[ https://jira.codehaus.org/browse/MSHADE-103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=39#comment-39 ] Joseph Walton edited comment on MSHADE-103 at 6/1/12 12:23 AM: --- -This

[jira] (MSHADE-103) maven-shade-plugin does not resolve from user-defined repositories

[ https://jira.codehaus.org/browse/MSHADE-103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joseph Walton updated MSHADE-103: - Attachment: MSHADE-103.tar.gz I have a case where the remote repository is a local directory and the

[jira] (MSHADE-103) maven-shade-plugin does not resolve from user-defined repositories

[ https://jira.codehaus.org/browse/MSHADE-103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=300161#comment-300161 ] Joseph Walton edited comment on MSHADE-103 at 6/1/12 12:34 AM: --- I