[jira] Commented: (MSITE-366) multimodule site stage doesn't work

[ http://jira.codehaus.org/browse/MSITE-366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=151633#action_151633 ] Wendy Smoak commented on MSITE-366: --- What makes it not browseable? If it's incorrect links, is this

[jira] Created: (MSITE-366) multimodule site stage doesn't work

multimodule site stage doesn't work --- Key: MSITE-366 URL: http://jira.codehaus.org/browse/MSITE-366 Project: Maven 2.x Site Plugin Issue Type: Bug Components: multi module Affects Versions: 2.0

[jira] Created: (MAVENUPLOAD-2248) Upload CGLIB 2.2

Upload CGLIB 2.2 Key: MAVENUPLOAD-2248 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2248 Project: Maven Upload Requests Issue Type: Task Reporter: Joerg Schaible http://www.people.apache.org/~joehni/cglib-n

[jira] Issue Comment Edited: (MNG-2695) -o makes build fail for snapshot plugins

[ http://jira.codehaus.org/browse/MNG-2695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=151532#action_151532 ] bentmann edited comment on MNG-2695 at 10/22/08 12:30 PM: --- The existi

[jira] Commented: (MNG-3704) NPE in DefaultLIfecycleExecutor when run from within Hudson builds

[ http://jira.codehaus.org/browse/MNG-3704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=151608#action_151608 ] David J. M. Karlsen commented on MNG-3704: -- This is still the case, even with 2.1.0-M1: http:

[jira] Commented: (MCOMPILER-83) add separate configuration for test compiler

[ http://jira.codehaus.org/browse/MCOMPILER-83?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=151604#action_151604 ] Oleg Gusakov commented on MCOMPILER-83: --- {quote} Wendy Smoak - 20/Oct/08 09:24 PM If you bind

[jira] Created: (MCHANGELOG-87) Wrong svn path if artifactid != directory

Wrong svn path if artifactid != directory - Key: MCHANGELOG-87 URL: http://jira.codehaus.org/browse/MCHANGELOG-87 Project: Maven 2.x Changelog Plugin Issue Type: Bug Affects Versions: 2.1

[jira] Commented: (MRELEASE-382) Specifying workingDirectory as system property on CL is not picked up by release:perform

[ http://jira.codehaus.org/browse/MRELEASE-382?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=151583#action_151583 ] Anders Hammar commented on MRELEASE-382: If I have a pom in the current directory in which

[jira] Created: (MRELEASE-382) Specifying workingDirectory as system property on CL is not picked up by release:perform

Specifying workingDirectory as system property on CL is not picked up by release:perform Key: MRELEASE-382 URL: http://jira.codehaus.org/browse/MRELEASE-382 Proj

[jira] Created: (MNG-3801) Plugin dependencies for module ignored when building from aggregated project

Plugin dependencies for module ignored when building from aggregated project Key: MNG-3801 URL: http://jira.codehaus.org/browse/MNG-3801 Project: Maven 2 Issue Type

[jira] Created: (SCM-423) when I try to checkout file from perforce with maven, I get an exception "Perforce password (P4PASSWD) invalid or unset."

when I try to checkout file from perforce with maven, I get an exception "Perforce password (P4PASSWD) invalid or unset." - Key: SCM-423 URL: h