[jira] Commented: (MJAR-66) Maven fails to include generated resources

[ http://jira.codehaus.org/browse/MJAR-66?page=comments#action_84698 ] Baerrach bonDierne commented on MJAR-66: I haven't spent any time looking into it but I would suspect that because on a clean the resource directory {noformat}

[jira] Commented: (MRELEASE-128) SCM properties being replaced during release:perform

[ http://jira.codehaus.org/browse/MRELEASE-128?page=comments#action_83880 ] Baerrach bonDierne commented on MRELEASE-128: - I'm experiencing the same problem but with ${user.name} {noformat} scm:cvs:pserver:[EMAIL PROTECTED]:

[jira] Closed: (MRELEASE-187) error message "cvs server: pom.xml is locally modified" when using windows

[ http://jira.codehaus.org/browse/MRELEASE-187?page=all ] Baerrach bonDierne closed MRELEASE-187. --- Resolution: Duplicate MRELEASE-94 > error message "cvs server: pom.xml is locally modified" when using windows > ---

[jira] Commented: (MRELEASE-188) release:perform is not updating some modules to the next version identifier correctly.

[ http://jira.codehaus.org/browse/MRELEASE-188?page=comments#action_83779 ] Baerrach bonDierne commented on MRELEASE-188: - After modifying my pom to look like: {noformat} abc abc-abcdefgh-abcdefghijklm-ancdefg

[jira] Commented: (MRELEASE-3) release:prepare should not require multimodule artifacts to be in the local repository

[ http://jira.codehaus.org/browse/MRELEASE-3?page=comments#action_83778 ] Baerrach bonDierne commented on MRELEASE-3: --- MRELEASE-182 (release:prepare preparationGoals should be "clean verify") may be related to this issue. I disagree wi

[jira] Commented: (MRELEASE-182) release:prepare preparationGoals should be "clean verify"

[ http://jira.codehaus.org/browse/MRELEASE-182?page=comments#action_83776 ] Baerrach bonDierne commented on MRELEASE-182: - MRELEASE-3 (release:prepare should not require multimodule artifacts to be in the local repository) may include

[jira] Commented: (MRELEASE-145) release:prepare requires all modules to be SNAPSHOTS

[ http://jira.codehaus.org/browse/MRELEASE-145?page=comments#action_83775 ] Baerrach bonDierne commented on MRELEASE-145: - modules are a convenience so that you can issue the one maven command and have it applied to all module project

[jira] Commented: (MRELEASE-188) release:perform is not updating some modules to the next version identifier correctly.

[ http://jira.codehaus.org/browse/MRELEASE-188?page=comments#action_83774 ] Baerrach bonDierne commented on MRELEASE-188: - I think it may be because of the formatting of the pom... Here is a copy of my pom with names changed to prote

[jira] Created: (MRELEASE-188) release:perform is not updating some modules to the next version identifier correctly.

release:perform is not updating some modules to the next version identifier correctly. -- Key: MRELEASE-188 URL: http://jira.codehaus.org/browse/MRELEASE-188 Project:

[jira] Created: (MRELEASE-187) error message "cvs server: pom.xml is locally modified" when using windows

error message "cvs server: pom.xml is locally modified" when using windows -- Key: MRELEASE-187 URL: http://jira.codehaus.org/browse/MRELEASE-187 Project: Maven 2.x Release Plugin

[jira] Commented: (MASSEMBLY-170) ManifestCreationFinalizer does not close File handles causing tests to fail

[ http://jira.codehaus.org/browse/MASSEMBLY-170?page=comments#action_83413 ] Baerrach bonDierne commented on MASSEMBLY-170: -- I normally honour the formatting, if I am not it probably means the eclipse formatting rules are out of dat

[jira] Commented: (MNG-2697) maven-plugin-testing-tools: ProjectToolTest.testPackageProjectArtifact_ShouldPopulateArtifactFileWithJarLocation fails on Windows

[ http://jira.codehaus.org/browse/MNG-2697?page=comments#action_83412 ] Baerrach bonDierne commented on MNG-2697: - Unit tests based on Files would be better than string based ones, especially since the raw type being tested is a File. If

[jira] Commented: (MJAVADOC-108) proxy support for plugin not complete enough

[ http://jira.codehaus.org/browse/MJAVADOC-108?page=comments#action_83207 ] Baerrach bonDierne commented on MJAVADOC-108: - I would have thought this was easy, but since this plugin forks off the javadoc command and there appears to be

[jira] Created: (MJAVADOC-108) proxy support for plugin not complete enough

proxy support for plugin not complete enough Key: MJAVADOC-108 URL: http://jira.codehaus.org/browse/MJAVADOC-108 Project: Maven 2.x Javadoc Plugin Issue Type: Bug Affects Versions: 2.1

[jira] Commented: (MECLIPSE-192) no way to get eclipse:eclipse working since the last SNAPSHOT of the plugin

[ http://jira.codehaus.org/browse/MECLIPSE-192?page=comments#action_83084 ] Baerrach bonDierne commented on MECLIPSE-192: - Mangling occurs in ProjecTool.packageProjectArtifact(). This mangles the pom info to include the test version

[jira] Commented: (MECLIPSE-192) no way to get eclipse:eclipse working since the last SNAPSHOT of the plugin

[ http://jira.codehaus.org/browse/MECLIPSE-192?page=comments#action_83077 ] Baerrach bonDierne commented on MECLIPSE-192: - Ok. In AbstractJarMojo.java line 152: {code:language=java} archiver.getArchiver().addDirectory( contentDir

[jira] Commented: (MNG-2105) Enable remote debugging command line option (+ docs)

[ http://jira.codehaus.org/browse/MNG-2105?page=comments#action_83017 ] Baerrach bonDierne commented on MNG-2105: - For now http://docs.codehaus.org/display/MAVENUSER/Dealing+with+Eclipse-based+IDE contains notes. > Enable remote debuggi

[jira] Commented: (MECLIPSE-192) no way to get eclipse:eclipse working since the last SNAPSHOT of the plugin

[ http://jira.codehaus.org/browse/MECLIPSE-192?page=comments#action_82929 ] Baerrach bonDierne commented on MECLIPSE-192: - I am still getting this issue for the latest version on trunk, revision 488511 The culprit unit tests are these

[jira] Updated: (MASSEMBLY-170) ManifestCreationFinalizer does not close File handles causing tests to fail

[ http://jira.codehaus.org/browse/MASSEMBLY-170?page=all ] Baerrach bonDierne updated MASSEMBLY-170: - Attachment: MASSEMBLY-170-patch.txt > ManifestCreationFinalizer does not close File handles causing tests to fail >

[jira] Created: (MASSEMBLY-170) ManifestCreationFinalizer does not close File handles causing tests to fail

ManifestCreationFinalizer does not close File handles causing tests to fail --- Key: MASSEMBLY-170 URL: http://jira.codehaus.org/browse/MASSEMBLY-170 Project: Maven 2.x Assembly P

[jira] Commented: (MNG-2705) add jar sources in repository for snapshot builds

[ http://jira.codehaus.org/browse/MNG-2705?page=comments#action_82839 ] Baerrach bonDierne commented on MNG-2705: - As per the discussion http://www.nabble.com/forum/ViewPost.jtp?post=7776225&framed=y&skin=177 this should be enabled for s

[jira] Created: (MNG-2705) add jar sources in repository for snapshot builds

add jar sources in repository for snapshot builds - Key: MNG-2705 URL: http://jira.codehaus.org/browse/MNG-2705 Project: Maven 2 Issue Type: Task Reporter: Baerrach bonDierne

[jira] Updated: (MASSEMBLY-166) ManifestCreationFinalizerTest fails on Windows

[ http://jira.codehaus.org/browse/MASSEMBLY-166?page=all ] Baerrach bonDierne updated MASSEMBLY-166: - Attachment: MASSEMBLY-166-patch.txt > ManifestCreationFinalizerTest fails on Windows > -- > >

[jira] Created: (MASSEMBLY-166) ManifestCreationFinalizerTest fails on Windows

ManifestCreationFinalizerTest fails on Windows -- Key: MASSEMBLY-166 URL: http://jira.codehaus.org/browse/MASSEMBLY-166 Project: Maven 2.x Assembly Plugin Issue Type: Bug Affects Versions: 2.2

[jira] Updated: (MNG-2701) FileSetUtilsTest.operatingSystemAllowsLinking fails on windows

[ http://jira.codehaus.org/browse/MNG-2701?page=all ] Baerrach bonDierne updated MNG-2701: Attachment: MNG-2701.txt > FileSetUtilsTest.operatingSystemAllowsLinking fails on windows > -- > >

[jira] Created: (MNG-2701) FileSetUtilsTest.operatingSystemAllowsLinking fails on windows

FileSetUtilsTest.operatingSystemAllowsLinking fails on windows -- Key: MNG-2701 URL: http://jira.codehaus.org/browse/MNG-2701 Project: Maven 2 Issue Type: Bug Environment:

[jira] Updated: (MSUREFIREREP-6) surefire-report reruns tests

[ http://jira.codehaus.org/browse/MSUREFIREREP-6?page=all ] Baerrach bonDierne updated MSUREFIREREP-6: -- Attachment: MSUREFIREREP-6-patch.txt Patch as requested by someone to create a "report-only" goal. Includes update to index.apt to reference

[jira] Updated: (MNG-2697) maven-plugin-testing-tools: ProjectToolTest.testPackageProjectArtifact_ShouldPopulateArtifactFileWithJarLocation fails on Windows

[ http://jira.codehaus.org/browse/MNG-2697?page=all ] Baerrach bonDierne updated MNG-2697: Attachment: MNG-2697-patch.txt Can this issue be assigned to jdcasey please, his name appears as the author in the svn history. Thanks > maven-plugin-testin

[jira] Created: (MNG-2697) maven-plugin-testing-tools: ProjectToolTest.testPackageProjectArtifact_ShouldPopulateArtifactFileWithJarLocation fails on Windows

maven-plugin-testing-tools: ProjectToolTest.testPackageProjectArtifact_ShouldPopulateArtifactFileWithJarLocation fails on Windows - Key: MNG-2697

[jira] Commented: (MNG-1577) dependencyManagement does not work for transitive dependencies

[ http://jira.codehaus.org/browse/MNG-1577?page=comments#action_82415 ] Baerrach bonDierne commented on MNG-1577: - Given the long list of comments and the potential hurdles raised in them, is there any direction on the proposed solutions

[jira] Updated: (MASSEMBLY-118) assembly uses maven parent relative path and not the modules relative path

[ http://jira.codehaus.org/browse/MASSEMBLY-118?page=all ] Baerrach bonDierne updated MASSEMBLY-118: - Attachment: MASSEMBLY-118-patch.txt New patch based on r471978 which does not exhibit the defect. So the patch only includes test cases for regr

[jira] Commented: (MASSEMBLY-119) dir format will fail with an error because it can not install the directory into the repository

[ http://jira.codehaus.org/browse/MASSEMBLY-119?page=comments#action_79464 ] Baerrach bonDierne commented on MASSEMBLY-119: -- Against r471978 I had some minor issues: * pom.xml needed explicit version of 2.1 for maven-jar, for some re

[jira] Commented: (CONTINUUM-968) Tests for continuum-release fail randomly

[ http://jira.codehaus.org/browse/CONTINUUM-968?page=comments#action_79068 ] Baerrach bonDierne commented on CONTINUUM-968: -- I'm working off HEAD (revision 470234) with a local snapshot build of maven-release-manager. Windows XP (no

[jira] Commented: (CONTINUUM-968) Tests for continuum-release fail randomly

[ http://jira.codehaus.org/browse/CONTINUUM-968?page=comments#action_78993 ] Baerrach bonDierne commented on CONTINUUM-968: -- The error may be in maven-release-manager but there is no source attached when the snapshot was deployed.

[jira] Commented: (MNG-670) warn when local dependency scope is vetoed

[ http://jira.codehaus.org/browse/MNG-670?page=comments#action_78982 ] Baerrach bonDierne commented on MNG-670: Linked to MNG-2645 which requests better error message reporting so that warning display the cuplrit for bad scoping. > warn

[jira] Created: (MNG-2645) warning message for local scope test should indicate whether the problem is

warning message for local scope test should indicate whether the problem is --- Key: MNG-2645 URL: http://jira.codehaus.org/browse/MNG-2645 Project: Maven 2 Issue Type:

[jira] Commented: (MASSEMBLY-119) dir format will fail with an error because it can not install the directory into the repository

[ http://jira.codehaus.org/browse/MASSEMBLY-119?page=comments#action_75728 ] Baerrach bonDierne commented on MASSEMBLY-119: -- Sure, I have 7 days left before I go on leave for 3 weeks so I can't guarantee when I get a chance to check

[jira] Commented: (MJAR-28) Using the jar plugin with addClasspath and snapshots can create manifest classpath with incorrect jar versions

[ http://jira.codehaus.org/browse/MJAR-28?page=comments#action_74100 ] Baerrach bonDierne commented on MJAR-28: Sorry you are right. The changes I needed to make for this are in maven-archiver in the linked issue MNG-2456 as the archiver

[jira] Commented: (MNG-2546) Allow plugin executions in the "super-init" phase before reactor sorting of modules build order

[ http://jira.codehaus.org/browse/MNG-2546?page=comments#action_74070 ] Baerrach bonDierne commented on MNG-2546: - Can you also link to your eclipse pde plugin. Some work like this is being done in the eclipse:eclipse plugin and given the

[jira] Commented: (MJAR-28) Using the jar plugin with addClasspath and snapshots can create manifest classpath with incorrect jar versions

[ http://jira.codehaus.org/browse/MJAR-28?page=comments#action_74025 ] Baerrach bonDierne commented on MJAR-28: The patch I provided does just that, for SNAPSHOTS it uses the timestamped version instead of -SNAPSHOT. > Using the jar plug

[jira] Created: (CONTINUUM-840) jdbc2_0-stdext.jar download instructions not in README.txt

jdbc2_0-stdext.jar download instructions not in README.txt --- Key: CONTINUUM-840 URL: http://jira.codehaus.org/browse/CONTINUUM-840 Project: Continuum Issue Type: Bug Affects Vers

[jira] Commented: (MASSEMBLY-67) assembling dependent jars or snapshots uses timestamp formatted version instead of ${version}

[ http://jira.codehaus.org/browse/MASSEMBLY-67?page=comments#action_72435 ] Baerrach bonDierne commented on MASSEMBLY-67: - I wrote up the steps I did to roll my own: http://docs.codehaus.org/display/MAVENUSER/Patching+Maven+Plugins

[jira] Commented: (MNG-2493) Snapshot plugin repositories should be included for reference at the Maven site

[ http://jira.codehaus.org/browse/MNG-2493?page=comments#action_72360 ] Baerrach bonDierne commented on MNG-2493: - When you patch it can you change the id's to codehaus.org I'm not sure what the id value should be, but maven-assembly-p

[jira] Updated: (MASSEMBLY-119) dir format will fail with an error because it can not install the directory into the repository

[ http://jira.codehaus.org/browse/MASSEMBLY-119?page=all ] Baerrach bonDierne updated MASSEMBLY-119: - Attachment: MASSEMBLY-119-patch.txt New patch that works with new unit test layout by John Casey. > dir format will fail with an error because

[jira] Updated: (MASSEMBLY-118) assembly uses maven parent relative path and not the modules relative path

[ http://jira.codehaus.org/browse/MASSEMBLY-118?page=all ] Baerrach bonDierne updated MASSEMBLY-118: - Attachment: MASSEMBLY-118-patch.txt (patch included another patch which is now removed) > assembly uses maven parent relative path and not the

[jira] Updated: (MASSEMBLY-118) assembly uses maven parent relative path and not the modules relative path

[ http://jira.codehaus.org/browse/MASSEMBLY-118?page=all ] Baerrach bonDierne updated MASSEMBLY-118: - Attachment: MASSEMBLY-118-patch.txt New patch file working with the latest trunk code base that has created unit tests and integration tests do

[jira] Updated: (MNG-2493) Snapshot plugin repositories should be included for reference at the Maven site

[ http://jira.codehaus.org/browse/MNG-2493?page=all ] Baerrach bonDierne updated MNG-2493: Attachment: MNG-2493-patch-2.txt Patch contains corrected codehaus location and also includes a repository definition (not just a plugin repo) > Snapshot plu

[jira] Reopened: (MNG-2493) Snapshot plugin repositories should be included for reference at the Maven site

[ http://jira.codehaus.org/browse/MNG-2493?page=all ] Baerrach bonDierne reopened MNG-2493: - Unfortunately the codehaus repository is at http://snapshots.repository.codehaus.org. (this is the new location for the codehaus repo after the cr

[jira] Commented: (MJAR-28) Using the jar plugin with addClasspath and snapshots can create manifest classpath with incorrect jar versions

[ http://jira.codehaus.org/browse/MJAR-28?page=comments#action_72186 ] Baerrach bonDierne commented on MJAR-28: In MASSEMBLY-67 John Casey says The solution here is to use an outputFileNameMapping such as this: ${artifactId}-${baseVersio

[jira] Closed: (MNG-2456) Maven Archiver creates incorrect Class-Path entry in Manifest for deployed snapshots

[ http://jira.codehaus.org/browse/MNG-2456?page=all ] Baerrach bonDierne closed MNG-2456. --- Resolution: Fixed In MASSEMBLY-67 John Casey says The solution here is to use an outputFileNameMapping such as this: ${artifactId}-${baseVersion}.${extension}

[jira] Updated: (MNG-2493) Snapshot plugin repositories should be included for reference at the Maven site

[ http://jira.codehaus.org/browse/MNG-2493?page=all ] Baerrach bonDierne updated MNG-2493: Attachment: MNG-2493-patch.txt Updated guides index to include a new file. Added a new development guide for snapshot repositories. Includes both the Maven s

[jira] Created: (MNG-2493) Snapshot plugin repositories should be included for reference at the Maven site

Snapshot plugin repositories should be included for reference at the Maven site --- Key: MNG-2493 URL: http://jira.codehaus.org/browse/MNG-2493 Project: Maven 2 Issu

[jira] Updated: (MNG-2456) Maven Archiver creates incorrect Class-Path entry in Manifest for deployed snapshots

[ http://jira.codehaus.org/browse/MNG-2456?page=all ] Baerrach bonDierne updated MNG-2456: Attachment: MNG-2456-patch.txt Patch adds the type of the artifact to the classpath which was incorrectly left off. > Maven Archiver creates incorrect Class

[jira] Commented: (MNG-2456) Maven Archiver creates incorrect Class-Path entry in Manifest for deployed snapshots

[ http://jira.codehaus.org/browse/MNG-2456?page=comments#action_71722 ] Baerrach bonDierne commented on MNG-2456: - Oops. Classpath is missing file extension... Need to update tests and repatch. > Maven Archiver creates incorrect Class-Pat

[jira] Updated: (MASSEMBLY-130) Documentation: supported formats needs updating.

[ http://jira.codehaus.org/browse/MASSEMBLY-130?page=all ] Baerrach bonDierne updated MASSEMBLY-130: - Attachment: MASSEMBLY-130-patch.txt Attaching again. Noticed that when I synced there was a newer index.apt. > Documentation: supported formats

[jira] Updated: (MASSEMBLY-130) Documentation: supported formats needs updating.

[ http://jira.codehaus.org/browse/MASSEMBLY-130?page=all ] Baerrach bonDierne updated MASSEMBLY-130: - Attachment: MASSEMBLLY-130-patch.txt Patch attaced as MASSEMBLLY-130-patch.txt (hopefully it will overwrite...) I worked out the How To's went

[jira] Commented: (MASSEMBLY-130) Documentation: supported formats needs updating.

[ http://jira.codehaus.org/browse/MASSEMBLY-130?page=comments#action_71126 ] Baerrach bonDierne commented on MASSEMBLY-130: -- Sure, Some files have gone missing on me like: src\site\apt\introduction.apt src\site\apt\howto.apt I'm ad

[jira] Commented: (MASSEMBLY-130) Documentation: supported formats needs updating.

[ http://jira.codehaus.org/browse/MASSEMBLY-130?page=comments#action_71115 ] Baerrach bonDierne commented on MASSEMBLY-130: -- You need to use the patch -p2 to apply the patches. With the latest doc changes happening on trunk applying

[jira] Commented: (MASSEMBLY-118) assembly uses maven parent relative path and not the modules relative path

[ http://jira.codehaus.org/browse/MASSEMBLY-118?page=comments#action_71114 ] Baerrach bonDierne commented on MASSEMBLY-118: -- You need to use patch -p3 to apply the patches. > assembly uses maven parent relative path and not the mod

[jira] Commented: (MASSEMBLY-119) dir format will fail with an error because it can not install the directory into the repository

[ http://jira.codehaus.org/browse/MASSEMBLY-119?page=comments#action_71113 ] Baerrach bonDierne commented on MASSEMBLY-119: -- You need to use -p3 to use the patches supplied. > dir format will fail with an error because it can not in

[jira] Commented: (MASSEMBLY-130) Documentation: supported formats needs updating.

[ http://jira.codehaus.org/browse/MASSEMBLY-130?page=comments#action_70706 ] Baerrach bonDierne commented on MASSEMBLY-130: -- It appears that using the Eclipse Team -> Create Patch command sucks. It doesn't create unified diffs very w

[jira] Commented: (MASSEMBLY-118) assembly uses maven parent relative path and not the modules relative path

[ http://jira.codehaus.org/browse/MASSEMBLY-118?page=comments#action_70705 ] Baerrach bonDierne commented on MASSEMBLY-118: -- It appears that using the Eclipse Team -> Create Patch command sucks. It doesn't create unified diffs very w

[jira] Commented: (MASSEMBLY-119) dir format will fail with an error because it can not install the directory into the repository

[ http://jira.codehaus.org/browse/MASSEMBLY-119?page=comments#action_70704 ] Baerrach bonDierne commented on MASSEMBLY-119: -- It appears that using the Eclipse Team -> Create Patch command sucks. It doesn't create unified diffs very w

[jira] Commented: (MASSEMBLY-119) dir format will fail with an error because it can not install the directory into the repository

[ http://jira.codehaus.org/browse/MASSEMBLY-119?page=comments#action_70686 ] Baerrach bonDierne commented on MASSEMBLY-119: -- When I was applying the patches for MASSEMBLY-119, MASSEMBLY-118, MASSEMBLY-130 locally for some reason the

[jira] Updated: (MASSEMBLY-130) Documentation: supported formats needs updating.

[ http://jira.codehaus.org/browse/MASSEMBLY-130?page=all ] Baerrach bonDierne updated MASSEMBLY-130: - Attachment: MASSEMBLY-130-patch-2.txt Includes the first patch details as well as additional documentation in the how to section on using the i

[jira] Commented: (MASSEMBLY-130) Documentation: supported formats needs updating.

[ http://jira.codehaus.org/browse/MASSEMBLY-130?page=comments#action_70680 ] Baerrach bonDierne commented on MASSEMBLY-130: -- When I tried to apply this patch I got errors because index.apt was renamed to overview.apt. I'm not sure w

[jira] Closed: (MCHANGELOG-38) NPE when developer section does not include an id

[ http://jira.codehaus.org/browse/MCHANGELOG-38?page=all ] Baerrach bonDierne closed MCHANGELOG-38. Resolution: Fixed Fix Version/s: 2.0 Download the latest code for this plugin. Modified the pom to include an scm section (as org.apache.

[jira] Updated: (MASSEMBLY-130) Documentation: supported formats needs updating.

[ http://jira.codehaus.org/browse/MASSEMBLY-130?page=all ] Baerrach bonDierne updated MASSEMBLY-130: - Attachment: MASSEMBLY-130-patch.txt Provides documentation updates to fix some broken links and updating the supported formats. > Documentatio

[jira] Created: (MASSEMBLY-130) Documentation: supported formats needs updating.

Documentation: supported formats needs updating. Key: MASSEMBLY-130 URL: http://jira.codehaus.org/browse/MASSEMBLY-130 Project: Maven 2.x Assembly Plugin Issue Type: Bug Affects Versions:

[jira] Updated: (MASSEMBLY-119) dir format will fail with an error because it can not install the directory into the repository

[ http://jira.codehaus.org/browse/MASSEMBLY-119?page=all ] Baerrach bonDierne updated MASSEMBLY-119: - Attachment: MASSEMBLY-119-patch.txt This patch adds unit tests for removing the directory archiver from the attached artifacts list. > dir fo

[jira] Updated: (MASSEMBLY-118) assembly uses maven parent relative path and not the modules relative path

[ http://jira.codehaus.org/browse/MASSEMBLY-118?page=all ] Baerrach bonDierne updated MASSEMBLY-118: - Attachment: MASSEMBLY-118-patch.txt Unit test with patch to fix the issue that an assembly with includeBaseDirectory set to false fails if the

[jira] Commented: (MNG-140) refactor maven-artifact

[ http://jira.codehaus.org/browse/MNG-140?page=comments#action_70331 ] Baerrach bonDierne commented on MNG-140: This might also include common artifact naming conventions. The artifact itself should know how to generate a file name, at the

[jira] Commented: (MASSEMBLY-118) assembly uses maven parent relative path and not the modules relative path

[ http://jira.codehaus.org/browse/MASSEMBLY-118?page=comments#action_70237 ] Baerrach bonDierne commented on MASSEMBLY-118: -- Interestingly, it works correctly for dir format. And I notice for both a slash and an empty outputDirector

[jira] Commented: (MASSEMBLY-118) assembly uses maven parent relative path and not the modules relative path

[ http://jira.codehaus.org/browse/MASSEMBLY-118?page=comments#action_70236 ] Baerrach bonDierne commented on MASSEMBLY-118: -- Yes, except that outputDirectory directory of - empty - / causes the file to not be added to the archive, b

[jira] Updated: (MJAR-28) Using the jar plugin with addClasspath and snapshots can create manifest classpath with incorrect jar versions

[ http://jira.codehaus.org/browse/MJAR-28?page=all ] Baerrach bonDierne updated MJAR-28: --- Attachment: MJAR-28-patch.txt This patch includes the changes needed to support MNG-2456 and an update of the documentation to include reference to user specifie

[jira] Commented: (MASSEMBLY-67) assembling dependent jars or snapshots uses timestamp formatted version instead of ${version}

[ http://jira.codehaus.org/browse/MASSEMBLY-67?page=comments#action_70228 ] Baerrach bonDierne commented on MASSEMBLY-67: - I have provided refactoring, test cases and a patch to fix this bug on MNG-2456, as it is not really a problem

[jira] Updated: (MNG-2456) Maven Archiver creates incorrect Class-Path entry in Manifest for deployed snapshots

[ http://jira.codehaus.org/browse/MNG-2456?page=all ] Baerrach bonDierne updated MNG-2456: Attachment: MNG-2456-step3-fix-bug-patch.txt Patch to fix the bug and get working unit test (Unfortunately the patch also includes previous steps) > Maven Arc

[jira] Updated: (MNG-2456) Maven Archiver creates incorrect Class-Path entry in Manifest for deployed snapshots

[ http://jira.codehaus.org/browse/MNG-2456?page=all ] Baerrach bonDierne updated MNG-2456: Attachment: MNG-2456-step2-add-test-cases-patch.txt Test Cases that exercise the problems. (Unfortunately the patch also includes previous steps) > Maven Arch

[jira] Updated: (MNG-2456) Maven Archiver creates incorrect Class-Path entry in Manifest for deployed snapshots

[ http://jira.codehaus.org/browse/MNG-2456?page=all ] Baerrach bonDierne updated MNG-2456: Attachment: MNG-2456-step1-refactoring-patch.txt Attached refactoring patch, with appropriate test cases, that changes Maven Archiver to use Project.getRuntim

[jira] Created: (MNG-2456) Maven Archiver creates incorrect Class-Path entry in Manifest for deployed snapshots

Maven Archiver creates incorrect Class-Path entry in Manifest for deployed snapshots Key: MNG-2456 URL: http://jira.codehaus.org/browse/MNG-2456 Project: Maven 2

[jira] Commented: (MECLIPSE-92) Allow .classpath generation for plugin-development support

[ http://jira.codehaus.org/browse/MECLIPSE-92?page=comments#action_70215 ] Baerrach bonDierne commented on MECLIPSE-92: This probably isn't the place for the discussion, I can see Stephane is close to getting maven and eclipse RCP stu

[jira] Commented: (MJAR-28) Using the jar plugin with addClasspath and snapshots can create manifest classpath with incorrect jar versions

[ http://jira.codehaus.org/browse/MJAR-28?page=comments#action_70120 ] Baerrach bonDierne commented on MJAR-28: Most of the comments I have made have been against MASSEMBLY-67 but the bug I believe is definitely in Maven Archiver (no bug

[jira] Commented: (MASSEMBLY-67) assembling dependent jars or snapshots uses timestamp formatted version instead of ${version}

[ http://jira.codehaus.org/browse/MASSEMBLY-67?page=comments#action_69654 ] Baerrach bonDierne commented on MASSEMBLY-67: - (Well it's not quite a week... but) Anyway I've found a web enabled IRC client and asked on the maven irc channel. #maven

[jira] Commented: (MASSEMBLY-67) assembling dependent jars or snapshots uses timestamp formatted version instead of ${version}

[ http://jira.codehaus.org/browse/MASSEMBLY-67?page=comments#action_69650 ] Baerrach bonDierne commented on MASSEMBLY-67: - I've reposted my request for help as it has been a week and no response from the dev list. > assembling dependent jars or

[jira] Commented: (MJAR-28) Using the jar plugin with addClasspath and snapshots can create manifest classpath with incorrect jar versions

[ http://jira.codehaus.org/browse/MJAR-28?page=comments#action_69271 ] Baerrach bonDierne commented on MJAR-28: Woops, I've attached the comments to bug MASSEMBLY-67. Never mind, they are related. Request for advice sent to dev list, see http://www.n

[jira] Commented: (MASSEMBLY-67) assembling dependent jars or snapshots uses timestamp formatted version instead of ${version}

[ http://jira.codehaus.org/browse/MASSEMBLY-67?page=comments#action_69270 ] Baerrach bonDierne commented on MASSEMBLY-67: - Woops, I've attached the comments to this bug rather than MJAR-28. Never mind, they are related. Request for advice sent to

[jira] Updated: (MASSEMBLY-67) assembling dependent jars or snapshots uses timestamp formatted version instead of ${version}

[ http://jira.codehaus.org/browse/MASSEMBLY-67?page=all ] Baerrach bonDierne updated MASSEMBLY-67: Attachment: MJAR-28-TestCases-Patch.txt MJAR-28-Notes.txt > assembling dependent jars or snapshots uses timestamp formatted version

[jira] Commented: (MJAR-47) maven-jar-plugin documentation should point to additional documentation, such as manifest guide

[ http://jira.codehaus.org/browse/MJAR-47?page=comments#action_68946 ] Baerrach bonDierne commented on MJAR-47: How To guides for things underneath the "archive" section would be great. Or links to archiver documentation so that we can work out how to

[jira] Commented: (MASSEMBLY-67) assembling dependent jars or snapshots uses timestamp formatted version instead of ${version}

[ http://jira.codehaus.org/browse/MASSEMBLY-67?page=comments#action_68549 ] Baerrach bonDierne commented on MASSEMBLY-67: - Ok, I think the problem is that we are not using the archiver to assemble a jar. We are using the archiver to assemble a bi

[jira] Commented: (MASSEMBLY-67) assembling dependent jars or snapshots uses timestamp formatted version instead of ${version}

[ http://jira.codehaus.org/browse/MASSEMBLY-67?page=comments#action_68545 ] Baerrach bonDierne commented on MASSEMBLY-67: - Brett, could you elaborate please? I'm not familiar with the archive section of the assembly plugin, but I am not sure how

[jira] Commented: (MECLIPSE-32) Allow for forcing the creation of direct project references for dependencies

[ http://jira.codehaus.org/browse/MECLIPSE-32?page=comments#action_68206 ] Baerrach bonDierne commented on MECLIPSE-32: Barry, See http://maven.apache.org/ref/2.0.3-SNAPSHOT/maven-model/maven.html Brett means that the configuration you require wo

[jira] Commented: (MCHANGELOG-38) NPE when developer section does not include an id

[ http://jira.codehaus.org/browse/MCHANGELOG-38?page=comments#action_68041 ] Baerrach bonDierne commented on MCHANGELOG-38: -- id may be required, but the problem is that it does not indicate this gracefully. I used the definition from the JIRA h

[jira] Commented: (MCHANGELOG-38) NPE when developer section does not include an id

[ http://jira.codehaus.org/browse/MCHANGELOG-38?page=comments#action_67904 ] Baerrach bonDierne commented on MCHANGELOG-38: -- org.codehaus.mojo changelog-maven-plugin Is the plugin I am u

[jira] Created: (MCHANGELOG-38) NPE when developer section does not include an id

NPE when developer section does not include an id - Key: MCHANGELOG-38 URL: http://jira.codehaus.org/browse/MCHANGELOG-38 Project: Maven 2.x Changelog Plugin Type: Bug Reporter: Baerrach bonDierne Priority: Cri

[jira] Updated: (MASSEMBLY-119) dir format will fail with an error because it can not install the directory into the repository

[ http://jira.codehaus.org/browse/MASSEMBLY-119?page=all ] Baerrach bonDierne updated MASSEMBLY-119: - Attachment: MASSEMBLY-119 Format dir fails on install.zip > dir format will fail with an error because it can not install the directory > into

[jira] Commented: (MASSEMBLY-118) assembly uses maven parent relative path and not the modules relative path

[ http://jira.codehaus.org/browse/MASSEMBLY-118?page=comments#action_67781 ] Baerrach bonDierne commented on MASSEMBLY-118: -- Spaces in the path? The issue is that in a reactor build the section is resolving path names to be parent project rel

[jira] Created: (MASSEMBLY-119) dir format will fail with an error because it can not install the directory into the repository

dir format will fail with an error because it can not install the directory into the repository --- Key: MASSEMBLY-119 URL: http://jira.codehaus.org/browse/MASSEMBLY-119 Project: Mav

[jira] Commented: (MASSEMBLY-87) In a multi-module build, assembly descriptor paths are not project-relative, but erraneously relative to the parent project directory

[ http://jira.codehaus.org/browse/MASSEMBLY-87?page=comments#action_6 ] Baerrach bonDierne commented on MASSEMBLY-87: - This may be a duplicate of MASSEMBLY-100. If you run mvn assembly:assembly in the parent pom, you are asking to run a plug

[jira] Commented: (MASSEMBLY-118) assembly uses maven parent relative path and not the modules relative path

[ http://jira.codehaus.org/browse/MASSEMBLY-118?page=comments#action_67775 ] Baerrach bonDierne commented on MASSEMBLY-118: -- This may be a duplicate of MASSEMBLY-100 which is listed as fixed in 2.2 (at this time 2.2 us unreleased.) > assembly

[jira] Created: (MASSEMBLY-118) assembly uses maven parent relative path and not the modules relative path

assembly uses maven parent relative path and not the modules relative path -- Key: MASSEMBLY-118 URL: http://jira.codehaus.org/browse/MASSEMBLY-118 Project: Maven 2.x Assembly Plugin Ty

  1   2   >