[jira] Created: (MEV-650) svnkit:1.3.2 depends on jna:3.2.3 which is not in the Maven Central

svnkit:1.3.2 depends on jna:3.2.3 which is not in the Maven Central --- Key: MEV-650 URL: http://jira.codehaus.org/browse/MEV-650 Project: Maven Evangelism Issue Type: Bug

[jira] Commented: (SUREFIRE-569) There should be a way to run unit tests from a dependency jar.

[ http://jira.codehaus.org/browse/SUREFIRE-569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=200249#action_200249 ] Thomas Strecker commented on SUREFIRE-569: -- Basically the description at

[jira] Commented: (MRESOURCES-104) while filtering resources the token replacement stops at the character @

[ http://jira.codehaus.org/browse/MRESOURCES-104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=200250#action_200250 ] Gareth Williams commented on MRESOURCES-104: One of the developers I work with was

[jira] Commented: (MEV-647) Missing POM for JFreeChart 1.0.13

[ http://jira.codehaus.org/browse/MEV-647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=200252#action_200252 ] Ingo Weinzierl commented on MEV-647: There is a valid JBoss-respository existing (see [1]) for

[jira] Created: (MCHANGES-188) Announcement collides with ${changes.version} property

Announcement collides with ${changes.version} property -- Key: MCHANGES-188 URL: http://jira.codehaus.org/browse/MCHANGES-188 Project: Maven 2.x Changes Plugin Issue Type: Bug

[jira] Commented: (MASSEMBLY-355) I get duplicate files in my -jar-with-dependencies.jar

[ http://jira.codehaus.org/browse/MASSEMBLY-355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=200260#action_200260 ] Andreas Münstermann commented on MASSEMBLY-355: --- Hi, I had the same problem and

[jira] Commented: (MECLIPSE-130) extra empty lines are preserved when writing Manifest.mf file

[ http://jira.codehaus.org/browse/MECLIPSE-130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=200262#action_200262 ] Erik Schepers commented on MECLIPSE-130: Does anyone know what the status of this bug is?

[jira] Commented: (MPH-71) call help:evaluate in batch mode

[ http://jira.codehaus.org/browse/MPH-71?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=200267#action_200267 ] Costin Caraivan commented on MPH-71: This would definitely be useful when integrating Maven with

[jira] Commented: (MPH-71) call help:evaluate in batch mode

[ http://jira.codehaus.org/browse/MPH-71?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=200269#action_200269 ] Galak commented on MPH-71: -- Moreover: when I want to evaluate a property which is inherited from a parent pom,

[jira] Commented: (SUREFIRE-569) There should be a way to run unit tests from a dependency jar.

[ http://jira.codehaus.org/browse/SUREFIRE-569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=200290#action_200290 ] Joerg Schaible commented on SUREFIRE-569: - As workaround simply unpack the jar with the

[jira] Commented: (MAVENUPLOAD-2164) Upload request for groupId's de.huxhorn.sulky and de.huxhorn.lilith

[ http://jira.codehaus.org/browse/MAVENUPLOAD-2164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=200307#action_200307 ] Joern Huxhorn commented on MAVENUPLOAD-2164: Didn't help at all, my artifacts are

[jira] Issue Comment Edited: (MAVENUPLOAD-2164) Upload request for groupId's de.huxhorn.sulky and de.huxhorn.lilith

[ http://jira.codehaus.org/browse/MAVENUPLOAD-2164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=200307#action_200307 ] Joern Huxhorn edited comment on MAVENUPLOAD-2164 at 12/2/09 9:20 AM:

[jira] Closed: (MAVENUPLOAD-2164) Upload request for groupId's de.huxhorn.sulky and de.huxhorn.lilith

[ http://jira.codehaus.org/browse/MAVENUPLOAD-2164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joern Huxhorn closed MAVENUPLOAD-2164. -- Resolution: Not A Bug Argh, sorry... The artifacts have obviously arrived at

[jira] Created: (MNG-4478) deploy plugin altDeploymentRepository does not use authorization credentials

deploy plugin altDeploymentRepository does not use authorization credentials Key: MNG-4478 URL: http://jira.codehaus.org/browse/MNG-4478 Project: Maven 2 Issue

[jira] Created: (DOXIA-371) Confluence macros conflict with -

Confluence macros conflict with - --- Key: DOXIA-371 URL: http://jira.codehaus.org/browse/DOXIA-371 Project: Maven Doxia Issue Type: Bug Components: Module - Confluence Reporter: Michael

[jira] Closed: (MNG-4478) deploy plugin altDeploymentRepository does not use authorization credentials

[ http://jira.codehaus.org/browse/MNG-4478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bentmann closed MNG-4478. -- Resolution: Duplicate Assignee: Benjamin Bentmann deploy plugin altDeploymentRepository does

[jira] Commented: (MNG-2258) Wrong execution order of plugins in same phase

[ http://jira.codehaus.org/browse/MNG-2258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=200327#action_200327 ] Julien HENRY commented on MNG-2258: --- In my corporate parent pom I have the following in reporting

[jira] Issue Comment Edited: (MNG-2258) Wrong execution order of plugins in same phase

[ http://jira.codehaus.org/browse/MNG-2258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=200327#action_200327 ] Julien HENRY edited comment on MNG-2258 at 12/2/09 10:39 AM: - In my

[jira] Created: (MASSEMBLY-452) Shared Assembly Descriptor does not work in Maven3-alpha4

Shared Assembly Descriptor does not work in Maven3-alpha4 - Key: MASSEMBLY-452 URL: http://jira.codehaus.org/browse/MASSEMBLY-452 Project: Maven 2.x Assembly Plugin Issue Type: Bug

[jira] Commented: (MASSEMBLY-452) Shared Assembly Descriptor does not work in Maven3-alpha4

[ http://jira.codehaus.org/browse/MASSEMBLY-452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=200335#action_200335 ] Ben Tatham commented on MASSEMBLY-452: -- Perhaps this issue should be added to:

[jira] Commented: (MNG-2258) Wrong execution order of plugins in same phase

[ http://jira.codehaus.org/browse/MNG-2258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=200336#action_200336 ] Martin Zeltner commented on MNG-2258: - Hi Julien Are you sure that you're using Maven 2.2.1, the

[jira] Created: (DOXIA-372) Please add snapshot build for 1.1.3 to repository

Please add snapshot build for 1.1.3 to repository - Key: DOXIA-372 URL: http://jira.codehaus.org/browse/DOXIA-372 Project: Maven Doxia Issue Type: Bug Components: Core Affects

[jira] Commented: (DOXIA-372) Please add snapshot build for 1.1.3 to repository

[ http://jira.codehaus.org/browse/DOXIA-372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=200338#action_200338 ] Olivier Lamy commented on DOXIA-372: snapshots are now here :

[jira] Commented: (DOXIA-372) Please add snapshot build for 1.1.3 to repository

[ http://jira.codehaus.org/browse/DOXIA-372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=200340#action_200340 ] Dave Syer commented on DOXIA-372: - I think I just pasted the wrong URL in the description. Thanks for

[jira] Commented: (DOXIA-372) Please add snapshot build for 1.1.3 to repository

[ http://jira.codehaus.org/browse/DOXIA-372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=200342#action_200342 ] Olivier Lamy commented on DOXIA-372: 1.1.2 is in vote status. I'm deploying 1.1.3-SNAPSHOT

[jira] Closed: (DOXIA-372) Please add snapshot build for 1.1.3 to repository

[ http://jira.codehaus.org/browse/DOXIA-372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy closed DOXIA-372. -- Resolution: Not A Bug Assignee: Olivier Lamy Please add snapshot build for 1.1.3 to repository

[jira] Created: (MASSEMBLY-453) Maven assembly plugin doesn't throws error when dependency version contains the brackets for tight tolerance

Maven assembly plugin doesn't throws error when dependency version contains the brackets for tight tolerance Key: MASSEMBLY-453 URL:

[jira] Commented: (MASSEMBLY-453) Maven assembly plugin doesn't throws error when dependency version contains the brackets for tight tolerance

[ http://jira.codehaus.org/browse/MASSEMBLY-453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=200348#action_200348 ] BJ Allmon commented on MASSEMBLY-453: - Title is goofed up.. Meant to say.. Maven assembly

[jira] Commented: (MAVENUPLOAD-2350) JCaptcha 1.0

[ http://jira.codehaus.org/browse/MAVENUPLOAD-2350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=200352#action_200352 ] Antoine Véret commented on MAVENUPLOAD-2350: Response from Jerry Huxtable,

[jira] Updated: (MECLIPSE-130) extra empty lines are preserved when writing Manifest.mf file

[ http://jira.codehaus.org/browse/MECLIPSE-130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Erik Schepers updated MECLIPSE-130: --- Attachment: EclipseOSGiManifestWriter.java.patch Ok, I did some looking into the code. The

[jira] Commented: (MECLIPSE-477) Extra empty lines are preserved when writing Manifest.mf file

[ http://jira.codehaus.org/browse/MECLIPSE-477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=200360#action_200360 ] Erik Schepers commented on MECLIPSE-477: I've attached a simple patch to MECLIPSE-130 that

[jira] Commented: (MCHANGES-188) Announcement collides with ${changes.version} property

[ http://jira.codehaus.org/browse/MCHANGES-188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=200368#action_200368 ] Dennis Lundberg commented on MCHANGES-188: -- You have misunderstood the purpose of this

[jira] Created: (MASSEMBLY-454) Read descriptor file is the same when plugin is ran twice

Read descriptor file is the same when plugin is ran twice - Key: MASSEMBLY-454 URL: http://jira.codehaus.org/browse/MASSEMBLY-454 Project: Maven 2.x Assembly Plugin Issue Type: Bug

[jira] Closed: (MASSEMBLY-454) Read descriptor file is the same when plugin is ran twice

[ http://jira.codehaus.org/browse/MASSEMBLY-454?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bentmann closed MASSEMBLY-454. --- Resolution: Not A Bug Assignee: Benjamin Bentmann You must not declare the same

[jira] Commented: (MASSEMBLY-454) Read descriptor file is the same when plugin is ran twice

[ http://jira.codehaus.org/browse/MASSEMBLY-454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=200374#action_200374 ] Johnathan Gifford commented on MASSEMBLY-454: - That worked. However, I need to control

[jira] Commented: (MASSEMBLY-454) Read descriptor file is the same when plugin is ran twice

[ http://jira.codehaus.org/browse/MASSEMBLY-454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=200380#action_200380 ] Benjamin Bentmann commented on MASSEMBLY-454: - For questions about plugin usage and

[jira] Commented: (MASSEMBLY-42) Document Maven2 Assembly Plugin - Assembly Descriptor

[ http://jira.codehaus.org/browse/MASSEMBLY-42?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=200386#action_200386 ] John Cheng commented on MASSEMBLY-42: - I believe it is documented now, albeit there are some

[jira] Created: (MASSEMBLY-455) Incorrect documentation for Pre-defined Descriptor Files

Incorrect documentation for Pre-defined Descriptor Files Key: MASSEMBLY-455 URL: http://jira.codehaus.org/browse/MASSEMBLY-455 Project: Maven 2.x Assembly Plugin Issue Type: Bug

[jira] Reopened: (DOXIA-372) Please add snapshot build for 1.1.3 to repository

[ http://jira.codehaus.org/browse/DOXIA-372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Syer reopened DOXIA-372: - How about closing the issue when it is fixed? Unless I'm missing something there still isn't a snapshot