[jira] Updated: (MJAVADOC-304) failOnError is ignored if javadoc:javadoc is called via Site Plugin 3.0-beta

[ http://jira.codehaus.org/browse/MJAVADOC-304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebastian Annies updated MJAVADOC-304: -- Attachment: MJAVADOC-304_Patch.patch MJAVADOC-304_IT_Test.patch

[jira] Created: (MJAVADOC-304) failOnError is ignored if javadoc:javadoc is called via Site Plugin 3.0-beta

failOnError is ignored if javadoc:javadoc is called via Site Plugin 3.0-beta Key: MJAVADOC-304 URL: http://jira.codehaus.org/browse/MJAVADOC-304 Project: Maven 2.x Javadoc

[jira] Updated: (SCM-584) Checkout branch with Git uses unfamiliar command sequence which leads to errors during checkout

[ http://jira.codehaus.org/browse/SCM-584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebastian Annies updated SCM-584: - Attachment: SCM-584-test-prj.zip A little project showing the error. I would have written a regular test

[jira] Updated: (SCM-584) Checkout branch with Git uses unfamiliar command sequence which leads to errors during checkout

[ http://jira.codehaus.org/browse/SCM-584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebastian Annies updated SCM-584: - Attachment: SCM-584.patch Patches the problem by appending the --branch parameter to the git command in

[jira] Created: (MNG-4918) MavenProject#clone() doubles active profiles

MavenProject#clone() doubles active profiles Key: MNG-4918 URL: http://jira.codehaus.org/browse/MNG-4918 Project: Maven 2 3 Issue Type: Bug Affects Versions: 3.0, 3.0.1 Environment:

[jira] Updated: (MNG-4918) MavenProject#clone() doubles active profiles

[ http://jira.codehaus.org/browse/MNG-4918?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebastian Annies updated MNG-4918: -- Attachment: fix.patch A fix for the clone problem MavenProject#clone() doubles active profiles

[jira] Updated: (MJAVADOC-299) excludePackageNames has no effect if subpackages is specified

[ http://jira.codehaus.org/browse/MJAVADOC-299?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebastian Annies updated MJAVADOC-299: -- Attachment: MJAVADOC-299.zip MJAVADOC-299_IT_Test.patch An integrationtest

[jira] Created: (MSITE-489) Make Maven 3.x trunk compile against Maven 3.0-beta-1

Make Maven 3.x trunk compile against Maven 3.0-beta-1 - Key: MSITE-489 URL: http://jira.codehaus.org/browse/MSITE-489 Project: Maven 2.x Site Plugin Issue Type: Task Affects Versions:

[jira] Commented: (MRELEASE-526) release:prepare 2.0 goal tags at the wrong level, tagging project/ instead of project/trunk

[ http://jira.codehaus.org/browse/MRELEASE-526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=219055#action_219055 ] Sebastian Annies commented on MRELEASE-526: --- Same for git. It's a blocker since. 2.0 is

[jira] Issue Comment Edited: (MRELEASE-526) release:prepare 2.0 goal tags at the wrong level, tagging project/ instead of project/trunk

[ http://jira.codehaus.org/browse/MRELEASE-526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=219055#action_219055 ] Sebastian Annies edited comment on MRELEASE-526 at 4/27/10 2:27 AM:

[jira] Created: (DOXIA-382) Sink cannot be reused after parsing with ConfluenceParser

Sink cannot be reused after parsing with ConfluenceParser -- Key: DOXIA-382 URL: http://jira.codehaus.org/browse/DOXIA-382 Project: Maven Doxia Issue Type: Bug Components:

[jira] Closed: (DOXIA-381) Using the render-books goal with confluence sources leads to incomplete output

[ http://jira.codehaus.org/browse/DOXIA-381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebastian Annies closed DOXIA-381. -- Resolution: Duplicate Using the render-books goal with confluence sources leads to incomplete output

[jira] Created: (DOXIA-381) Using the render-books goal with confluence sources leads to incomplete output

Using the render-books goal with confluence sources leads to incomplete output -- Key: DOXIA-381 URL: http://jira.codehaus.org/browse/DOXIA-381 Project: Maven Doxia

[jira] Updated: (DOXIA-381) Using the render-books goal with confluence sources leads to incomplete output

[ http://jira.codehaus.org/browse/DOXIA-381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebastian Annies updated DOXIA-381: --- Attachment: TestCase_for_DOXIA-381.patch Added a TestCase Using the render-books goal with

[jira] Commented: (MRELEASE-230) release:prepare cannot update the version of a module in a multi-module build if you have both normal artifact and attached artifact in dependencies

[ http://jira.codehaus.org/browse/MRELEASE-230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=136765#action_136765 ] Sebastian Annies commented on MRELEASE-230: --- Is there any workaround? release:prepare

[jira] Created: (SCM-370) generated client spec contains backslashes leading die problems on unix os

generated client spec contains backslashes leading die problems on unix os -- Key: SCM-370 URL: http://jira.codehaus.org/browse/SCM-370 Project: Maven SCM Issue Type:

[jira] Updated: (SCM-370) generated client spec contains backslashes leading die problems on unix os

[ http://jira.codehaus.org/browse/SCM-370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebastian Annies updated SCM-370: - Attachment: SCM-351__SCM-370.patch Modified generateDefaultClientspecName in PerforceScmProvider to

[jira] Commented: (SCM-351) generated client spec name fails if there is a space or tilde in directory name

[ http://jira.codehaus.org/browse/SCM-351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_127450 ] Sebastian Annies commented on SCM-351: -- [SCM-370] is a very similar issue. I attached a patch there that will also fix

[jira] Issue Comment Edited: (SCM-370) generated client spec contains backslashes leading die problems on unix os

[ http://jira.codehaus.org/browse/SCM-370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_127449 ] sannies edited comment on SCM-370 at 3/17/08 6:35 AM: --- Patch: Modified

[jira] Created: (MJAVADOC-178) Transitive Dependencies to Taglet Artifacts are not resolved nor added to the classpath

Transitive Dependencies to Taglet Artifacts are not resolved nor added to the classpath --- Key: MJAVADOC-178 URL: http://jira.codehaus.org/browse/MJAVADOC-178

[jira] Commented: (CONTINUUM-1402) Syncing with Perforce on Linux/Unix/Bash fails

[ http://jira.codehaus.org/browse/CONTINUUM-1402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_115890 ] Sebastian Annies commented on CONTINUUM-1402: - No Workaround for me: I got 45 modules. Syncing with

[jira] Commented: (CONTINUUM-1402) Syncing with Perforce on Linux/Unix/Bash fails

[ http://jira.codehaus.org/browse/CONTINUUM-1402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_109968 ] Sebastian Annies commented on CONTINUUM-1402: - this would require a fix in the Maven Perforce SCM Provider

[jira] Issue Comment Edited: (CONTINUUM-1402) Syncing with Perforce on Linux/Unix/Bash fails

[ http://jira.codehaus.org/browse/CONTINUUM-1402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_106601 ] Sebastian Annies edited comment on CONTINUUM-1402 at 9/5/07 4:40 PM: - Can someone

[jira] Commented: (CONTINUUM-1402) Syncing with Perforce on Linux/Unix/Bash fails

[ http://jira.codehaus.org/browse/CONTINUUM-1402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_106601 ] Sebastian Annies commented on CONTINUUM-1402: - Can someone concerned please have a look into PLXUTILS-44 and

[jira] Commented: (CONTINUUM-1402) Syncing with Perforce on Linux/Unix/Bash fails

[ http://jira.codehaus.org/browse/CONTINUUM-1402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_106309 ] Sebastian Annies commented on CONTINUUM-1402: - I will provide a plexus-utils fix in the next days (perhaps I

[jira] Commented: (CONTINUUM-1351) Acnnot checkout sources - perforce.

[ http://jira.codehaus.org/browse/CONTINUUM-1351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_106036 ] Sebastian Annies commented on CONTINUUM-1351: - This issue is not very specific. Could you please give us

[jira] Created: (CONTINUUM-1402) Syncing with Perforce on Linux/Unix/Bash fails

Syncing with Perforce on Linux/Unix/Bash fails -- Key: CONTINUUM-1402 URL: http://jira.codehaus.org/browse/CONTINUUM-1402 Project: Continuum Issue Type: Bug Components: Integration -

[jira] Issue Comment Edited: (CONTINUUM-1402) Syncing with Perforce on Linux/Unix/Bash fails

[ http://jira.codehaus.org/browse/CONTINUUM-1402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_105305 ] Sebastian Annies edited comment on CONTINUUM-1402 at 8/21/07 7:41 AM: -- MORE

[jira] Issue Comment Edited: (CONTINUUM-1402) Syncing with Perforce on Linux/Unix/Bash fails

[ http://jira.codehaus.org/browse/CONTINUUM-1402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_105305 ] Sebastian Annies edited comment on CONTINUUM-1402 at 8/21/07 7:40 AM: -- MORE

[jira] Issue Comment Edited: (CONTINUUM-1402) Syncing with Perforce on Linux/Unix/Bash fails

[ http://jira.codehaus.org/browse/CONTINUUM-1402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_105305 ] Sebastian Annies edited comment on CONTINUUM-1402 at 8/21/07 7:39 AM: -- MORE

[jira] Issue Comment Edited: (CONTINUUM-1402) Syncing with Perforce on Linux/Unix/Bash fails

[ http://jira.codehaus.org/browse/CONTINUUM-1402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_105305 ] Sebastian Annies edited comment on CONTINUUM-1402 at 8/21/07 10:15 AM: --- MORE

[jira] Issue Comment Edited: (CONTINUUM-1402) Syncing with Perforce on Linux/Unix/Bash fails

[ http://jira.codehaus.org/browse/CONTINUUM-1402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_105305 ] Sebastian Annies edited comment on CONTINUUM-1402 at 8/21/07 10:16 AM: --- MORE

[jira] Closed: (CONTINUUM-1274) Release Project fails due to pom.xml not writable with perforce as SCM

[ http://jira.codehaus.org/browse/CONTINUUM-1274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sebastian Annies closed CONTINUUM-1274. --- Resolution: Fixed Fix Version/s: (was: Future)

[jira] Created: (CONTINUUM-1352) Introduce a mail size limit

Introduce a mail size limit --- Key: CONTINUUM-1352 URL: http://jira.codehaus.org/browse/CONTINUUM-1352 Project: Continuum Issue Type: New Feature Components: Integration - Maven 2, Notification Subsystem,

[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] Issue Comment Edited: (CONTINUUM-1274) Release Project fails due to pom.xml not writable with perforce as SCM

[ http://jira.codehaus.org/browse/CONTINUUM-1274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_96294 ] Sebastian Annies edited comment on CONTINUUM-1274 at 5/19/07 5:08 AM: -- - was:

[jira] Issue Comment Edited: (CONTINUUM-1274) Release Project fails due to pom.xml not writable with perforce as SCM

[ http://jira.codehaus.org/browse/CONTINUUM-1274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_96294 ] Sebastian Annies edited comment on CONTINUUM-1274 at 5/19/07 5:43 AM: -- is this

[jira] Issue Comment Edited: (CONTINUUM-1274) Release Project fails due to pom.xml not writable with perforce as SCM

[ http://jira.codehaus.org/browse/CONTINUUM-1274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_96293 ] Sebastian Annies edited comment on CONTINUUM-1274 at 5/19/07 9:25 AM: -- the perforce

[jira] Commented: (SCM-281) Perforce problem: incorrect client spec is used

[ http://jira.codehaus.org/browse/SCM-281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_96364 ] Sebastian Annies commented on SCM-281: -- The client spec seems to be a major problem with the perforce integration. I

[jira] Commented: (CONTINUUM-1274) Release Project fails due to pom.xml not writable with perforce as SCM

[ http://jira.codehaus.org/browse/CONTINUUM-1274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_96369 ] Sebastian Annies commented on CONTINUUM-1274: - I fixed this issue for myself (works for me and I don't what

[jira] Commented: (CONTINUUM-1274) Release Project fails due to pom.xml not writable with perforce as SCM

[ http://jira.codehaus.org/browse/CONTINUUM-1274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_96281 ] Sebastian Annies commented on CONTINUUM-1274: - I added some log to the AbstractRewritePomsPhase.java source:

[jira] Commented: (CONTINUUM-1274) Release Project fails due to pom.xml not writable with perforce as SCM

[ http://jira.codehaus.org/browse/CONTINUUM-1274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_96294 ] Sebastian Annies commented on CONTINUUM-1274: - Logging should be improved. I have to debug everything, cause

[jira] Issue Comment Edited: (CONTINUUM-1274) Release Project fails due to pom.xml not writable with perforce as SCM

[ http://jira.codehaus.org/browse/CONTINUUM-1274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_96294 ] Sebastian Annies edited comment on CONTINUUM-1274 at 5/18/07 7:01 PM: -- Logging

[jira] Created: (CONTINUUM-1274) Release Project fails due to pom.xml not writable with perforce as SCM

Release Project fails due to pom.xml not writable with perforce as SCM -- Key: CONTINUUM-1274 URL: http://jira.codehaus.org/browse/CONTINUUM-1274 Project: Continuum Issue