[jira] Commented: (MAVENUPLOAD-1636) Upload JIDE Common Layer 2.1.1 to maven repository

[ http://jira.codehaus.org/browse/MAVENUPLOAD-1636?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_102657 ] Wim Deblauwe commented on MAVENUPLOAD-1636: --- And did you update the central repo? I tried again today (and

[jira] Closed: (MNG-916) RELEASE gets selected as a version

[ http://jira.codehaus.org/browse/MNG-916?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter closed MNG-916. Resolution: Fixed re-closing the historic issue - please create a new one if it is reoccurring (and link to here)

[jira] Commented: (MRELEASE-261) release:prepare shouls support flat directory multimodule projects

[ http://jira.codehaus.org/browse/MRELEASE-261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_102667 ] John Allen commented on MRELEASE-261: - Well in that case the common directory is '/' which is probably not what you

[jira] Commented: (MSITE-117) 'org.apache.maven.plugins:maven-site-plugin' does not exist or no valid version when building off line

[ http://jira.codehaus.org/browse/MSITE-117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_102670 ] paul browne commented on MSITE-117: --- Offtopic, but the way I resolved this is to remove the directory

[jira] Commented: (MSITE-136) when inheriting site.xml the menu ref='parent' expands to a menu with links for *all* ancestors and not just the immediate parent

[ http://jira.codehaus.org/browse/MSITE-136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_102676 ] John Allen commented on MSITE-136: -- Okay this is definitely due to the above, i.e. for every parent in the hierarchy of the

[jira] Closed: (DOXIA-115) APT module requires descritptor merge

[ http://jira.codehaus.org/browse/DOXIA-115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lukas Theussl closed DOXIA-115. --- Assignee: Lukas Theussl Resolution: Fixed Applied also to the xdoc module. Thanks! APT module

[jira] Commented: (MCHANGELOG-66) changelog for perforce fails because of default clientspec

[ http://jira.codehaus.org/browse/MCHANGELOG-66?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_102683 ] Sebastian Annies commented on MCHANGELOG-66: I don't think that this is a issue with the changelog plugin.

[jira] Issue Comment Edited: (MCHANGELOG-66) changelog for perforce fails because of default clientspec

[ http://jira.codehaus.org/browse/MCHANGELOG-66?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_102683 ] Sebastian Annies edited comment on MCHANGELOG-66 at 7/19/07 7:10 AM: - I don't think

[jira] Commented: (MCHANGELOG-66) changelog for perforce fails because of default clientspec

[ http://jira.codehaus.org/browse/MCHANGELOG-66?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_102684 ] Dennis Lundberg commented on MCHANGELOG-66: --- I agree that it seems that the support for Perforce in Maven SCM

[jira] Commented: (MANTRUN-40) Properties defined in pom properties do not propagate to the antrun environment

[ http://jira.codehaus.org/browse/MANTRUN-40?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_102685 ] Stephane Nicoll commented on MANTRUN-40: I second Jason D. on that. It took me a while to figure out what was

[jira] Commented: (MCHANGELOG-66) changelog for perforce fails because of default clientspec

[ http://jira.codehaus.org/browse/MCHANGELOG-66?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_102686 ] Dennis Lundberg commented on MCHANGELOG-66: --- I've deployed a new 2.1-SNAPSHOT that allows you to configure

[jira] Created: (MINSTALL-39) Maven Install Plugin always copy the artifact in the repository, even if there was no changes

Maven Install Plugin always copy the artifact in the repository, even if there was no changes - Key: MINSTALL-39 URL: http://jira.codehaus.org/browse/MINSTALL-39

[jira] Created: (MNG-3115) DependencyManagement does not work for dependencies of type zip

DependencyManagement does not work for dependencies of type zip - Key: MNG-3115 URL: http://jira.codehaus.org/browse/MNG-3115 Project: Maven 2 Issue Type: Bug

[jira] Commented: (SCM-258) The perforce provider should be able to accept complex filespecs using a clientspec rather than the path in the SCM url

[ http://jira.codehaus.org/browse/SCM-258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_102717 ] Brian Jackson commented on SCM-258: --- I'm now also running into the problem that the plugin overwrites the existing

[jira] Commented: (MCHANGELOG-66) changelog for perforce fails because of default clientspec

[ http://jira.codehaus.org/browse/MCHANGELOG-66?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_102718 ] Dennis Lundberg commented on MCHANGELOG-66: --- Thanks for testing this. I'll write up some documentation on this

[jira] Closed: (MCHANGELOG-66) changelog for perforce fails because of default clientspec

[ http://jira.codehaus.org/browse/MCHANGELOG-66?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg closed MCHANGELOG-66. - Resolution: Fixed Fix Version/s: 2.1 Added documentation as well. changelog for

[jira] Closed: (MDEP-47) Ability to have an includes/excludes feature on the dependency:unpack goal.

[ http://jira.codehaus.org/browse/MDEP-47?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Fox closed MDEP-47. - Resolution: Fixed Thanks for the patches, Damian. It looks and works great. I deployed a snapshot and the site. Could

[jira] Updated: (MDEP-98) The source must not be a directory

[ http://jira.codehaus.org/browse/MDEP-98?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Fox updated MDEP-98: -- Fix Version/s: 2.0-alpha-5 The source must not be a directory --