[jira] Closed: (MASSEMBLY-105) need better support for unpack

[ http://jira.codehaus.org/browse/MASSEMBLY-105?page=all ] John Casey closed MASSEMBLY-105. Assignee: John Casey Resolution: Fixed > need better support for unpack > -- > > Key: MASSEMBLY-105 >

[jira] Closed: (MASSEMBLY-90) add a DependencySet filter based on type

[ http://jira.codehaus.org/browse/MASSEMBLY-90?page=all ] John Casey closed MASSEMBLY-90. --- Assignee: John Casey Resolution: Fixed should be possible using wildcards now: *:jar:* > add a DependencySet filter based on type > -

[jira] Closed: (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 ] John Casey closed MASSEMBLY-119. Resolution: Fixed it should avoid attaching/installing/deploying when the assembly file isDirectory(), now. > dir format will fail with an error because it can

[jira] Closed: (MASSEMBLY-107) DependencySet does not support classifier

[ http://jira.codehaus.org/browse/MASSEMBLY-107?page=all ] John Casey closed MASSEMBLY-107. Assignee: John Casey Resolution: Fixed Should work now, since Artifact.getId() includes classifier... Also, you can do: *:javadocs now...so this should b

[jira] Closed: (MASSEMBLY-41) Enable wilcards in dependency set includes/excludes

[ http://jira.codehaus.org/browse/MASSEMBLY-41?page=all ] John Casey closed MASSEMBLY-41. --- Assignee: John Casey Resolution: Fixed Fix Version/s: 2.2 MASSEMBLY-103 does contain a comment detailing the fix for this...I've implemented: org.a

[jira] Closed: (MASSEMBLY-103) More powerful includes/excludes stuff in DependencySets in descriptors

[ http://jira.codehaus.org/browse/MASSEMBLY-103?page=all ] John Casey closed MASSEMBLY-103. Assignee: John Casey Resolution: Fixed Fix Version/s: 2.2 try: org.apache.maven:*:jar org.apache.maven:maven-artifact:* > M

[jira] Commented: (SCM-230) mercurial plugin

[ http://jira.codehaus.org/browse/SCM-230?page=comments#action_78582 ] THURNER rupert commented on SCM-230: btw, thanks a lot for the fixes! we also have this problem. > mercurial plugin > > > Key: SCM-230 >

[jira] Commented: (SCM-230) mercurial plugin

[ http://jira.codehaus.org/browse/SCM-230?page=comments#action_78581 ] THURNER rupert commented on SCM-230: upload a patch and mailbomb scm-dev@maven.apache.org mailing list :) i wonder also if there is a place to document the testcases so th

[jira] Updated: (MASSEMBLY-97) multiproject with assembly fails in mysterious ways

[ http://jira.codehaus.org/browse/MASSEMBLY-97?page=all ] John Casey updated MASSEMBLY-97: Fix Version/s: 2.2 > multiproject with assembly fails in mysterious ways > --- > > Key: MASSEMBLY-9

[jira] Closed: (MASSEMBLY-97) multiproject with assembly fails in mysterious ways

[ http://jira.codehaus.org/browse/MASSEMBLY-97?page=all ] John Casey closed MASSEMBLY-97. --- Assignee: John Casey Resolution: Won't Fix Use assembly:single or assembly:directory-single for this type of application. directory-single is added in 2.2-SNA

[jira] Closed: (MDEP-40) use Lowercase "alpha"

[ http://jira.codehaus.org/browse/MDEP-40?page=all ] Brian Fox closed MDEP-40. - Resolution: Fixed since the repo is trashed anyway, I updated the version correctly. Now when the permissions are un"screwed" it will be deployed correctly. > use Lowercase "alpha"

[jira] Moved: (MNG-2635) DefaultArtifactCollector.recurse can lose versionRange

[ http://jira.codehaus.org/browse/MNG-2635?page=all ] Arnaud Heritier moved MPARTIFACT-73 to MNG-2635: Complexity: Intermediate Workflow: Maven New (was: jira) Key: MNG-2635 (was: MPARTIFACT-73) Project: Maven 2

[jira] Created: (MPARTIFACT-73) DefaultArtifactCollector.recurse can lose versionRange

DefaultArtifactCollector.recurse can lose versionRange -- Key: MPARTIFACT-73 URL: http://jira.codehaus.org/browse/MPARTIFACT-73 Project: maven-artifact-plugin Issue Type: Bug Envir

[jira] Updated: (MAVEN-1810) Upgrade maven-nsis-plugin to v 2.1

[ http://jira.codehaus.org/browse/MAVEN-1810?page=all ] Arnaud Heritier updated MAVEN-1810: --- Description: http://jira.codehaus.org/browse/MPNSIS?report=com.atlassian.jira.plugin.system.project:roadmap-panel I'm not yet sure to include it in maven

[jira] Updated: (MAVEN-1809) Upgrade maven-pdf-plugin to v 2.5.1

[ http://jira.codehaus.org/browse/MAVEN-1809?page=all ] Arnaud Heritier updated MAVEN-1809: --- Description: http://jira.codehaus.org/browse/MPPDF?report=com.atlassian.jira.plugin.system.project:roadmap-panel Affects Version/s: 1.1-beta-3

[jira] Created: (MAVEN-1810) Upgrade maven-nsis-plugin to v 2.1

Upgrade maven-nsis-plugin to v 2.1 -- Key: MAVEN-1810 URL: http://jira.codehaus.org/browse/MAVEN-1810 Project: Maven 1.x Issue Type: Sub-task Reporter: Arnaud Heritier Assigned To: Arnaud

[jira] Created: (MAVEN-1809) Upgrade maven-pdf-plugin to v 2.5.1

Upgrade maven-pdf-plugin to v 2.5.1 --- Key: MAVEN-1809 URL: http://jira.codehaus.org/browse/MAVEN-1809 Project: Maven 1.x Issue Type: Sub-task Reporter: Arnaud Heritier Assigned To: Arnau

[jira] Closed: (MPPDF-57) Unable to remove cover type and version

[ http://jira.codehaus.org/browse/MPPDF-57?page=all ] Arnaud Heritier closed MPPDF-57. Resolution: Fixed - To avoid problems, be sure to not use a -PARAM without arg - Remove default hardcoded settings to allow users to remove them using an empty proper

[jira] Commented: (MPPDF-57) Unable to remove cover type and version

[ http://jira.codehaus.org/browse/MPPDF-57?page=comments#action_78556 ] Arnaud Heritier commented on MPPDF-57: -- Lukas, I reproduced (and fixed) it with wendy's testcase In fact it's logical because there's no test arround the cover type attri

[jira] Created: (CONTINUUM-973) Maven 1.x mail notifier not working, being removed after build.

Maven 1.x mail notifier not working, being removed after build. --- Key: CONTINUUM-973 URL: http://jira.codehaus.org/browse/CONTINUUM-973 Project: Continuum Issue Type: Bug

[jira] Updated: (MPPDF-57) Unable to remove cover type and version

[ http://jira.codehaus.org/browse/MPPDF-57?page=all ] Wendy Smoak updated MPPDF-57: - Attachment: svn-intro.pdf Yes, I meant 'maven site'. :) $ echo $MAVEN_HOME c:\java\maven-1.1-RC1-SNAPSHOT $PATH contains $MAVEN_HOME/bin. $ ll $MAVEN_HOME/plugins/ | gre

[jira] Created: (MNG-2634) Archiver should be adding "Created-By: Apache Maven _2.0.4_" to the manifest

Archiver should be adding "Created-By: Apache Maven _2.0.4_" to the manifest Key: MNG-2634 URL: http://jira.codehaus.org/browse/MNG-2634 Project: Maven 2 Issue Type

[jira] Closed: (MDEP-45) Documentation is wrong on maven.apache.org

[ http://jira.codehaus.org/browse/MDEP-45?page=all ] Dennis Lundberg closed MDEP-45. --- Resolution: Won't Fix No, the docs are correct. This is explained in the FAQ: http://maven.apache.org/plugins/maven-dependency-plugin/faq.html > Documentation is wrong

[jira] Commented: (MPPDF-57) Unable to remove cover type and version

[ http://jira.codehaus.org/browse/MPPDF-57?page=comments#action_78549 ] Lukas Theussl commented on MPPDF-57: I cannot reproduce any of the above, I see no problems in your test project with neither cover.type nor cover.date. Are you sure you

[jira] Created: (MNG-2633) Unexpected behaviour settings in POM.xml.

Unexpected behaviour settings in POM.xml. -- Key: MNG-2633 URL: http://jira.codehaus.org/browse/MNG-2633 Project: Maven 2 Issue Type: Bug Components: Dependencies Affects Ver

[jira] Updated: (MPPDF-57) Unable to remove cover type and version

[ http://jira.codehaus.org/browse/MPPDF-57?page=all ] Wendy Smoak updated MPPDF-57: - Attachment: pdf-test.tar.gz Example project with pdf plugin configured. 'mvn site' will build the pdf. > Unable to remove cover type and version >

[jira] Commented: (MPPDF-57) Unable to remove cover type and version

[ http://jira.codehaus.org/browse/MPPDF-57?page=comments#action_78535 ] Wendy Smoak commented on MPPDF-57: -- Thanks. That fixed the cover version, but not the cover type. If I specify maven.pdf.cover.type= Then I get the text '-PARAM' where

[jira] Created: (SUREFIRE-56) Test is broken and marked as Fail but works with plain execution with JUnit

Test is broken and marked as Fail but works with plain execution with JUnit --- Key: SUREFIRE-56 URL: http://jira.codehaus.org/browse/SUREFIRE-56 Project: surefire Issue

[jira] Closed: (MPA-82) Invalid jar in the central repository : sitemesh 2.2.1

[ http://jira.codehaus.org/browse/MPA-82?page=all ] Arnaud Heritier closed MPA-82. -- Assignee: Arnaud Heritier (was: Jason van Zyl) Resolution: Cannot Reproduce Fix Version/s: 2006-q4 Seems to be fixed now. There was certainly a problem (tem

[jira] Created: (CONTINUUM-972) Unable to delete projects

Unable to delete projects - Key: CONTINUUM-972 URL: http://jira.codehaus.org/browse/CONTINUUM-972 Project: Continuum Issue Type: Bug Affects Versions: 1.0.3 Environment: Redhat Enterprise 3 Re

[jira] Commented: (MAVENUPLOAD-1197) Upload jsch.0.1.29 to the maven central repository

[ http://jira.codehaus.org/browse/MAVENUPLOAD-1197?page=comments#action_78522 ] Antoine Levy-Lambert commented on MAVENUPLOAD-1197: --- Hello Carlos, thanks for your help. Actually groupId is com.jcraft artifactId is jsch. Regard

[jira] Commented: (MEJB-7) Transitive Classpath not written to the manifest

[ http://jira.codehaus.org/browse/MEJB-7?page=comments#action_78519 ] Sam Wilson commented on MEJB-7: --- That seems to solve the issue. However, given that this is part of the spec, shouldn't this be the default behavior and not require this sort of

[jira] Commented: (MAVENUPLOAD-1197) Upload jsch.0.1.29 to the maven central repository

[ http://jira.codehaus.org/browse/MAVENUPLOAD-1197?page=comments#action_78517 ] Carlos Sanchez commented on MAVENUPLOAD-1197: - Next time upload to groupId com.jcraft.jsch > Upload jsch.0.1.29 to the maven central repository > ---

[jira] Updated: (MPPDF-57) Unable to remove cover type and version

[ http://jira.codehaus.org/browse/MPPDF-57?page=all ] Lukas Theussl updated MPPDF-57: --- Assignee: Lukas Theussl Fix Version/s: 2.5.1 It's fixed in SVN but I can't deploy snapshots for the moment. If you could test it from SVN then we can close thi

[jira] Closed: (CONTINUUM-970) Remove release-plugin dependency from continuum-release and instead use maven-release-manager from maven-shared

[ http://jira.codehaus.org/browse/CONTINUUM-970?page=all ] Jesse McConnell closed CONTINUUM-970. - Resolution: Fixed ah yes, so I did. committed now r467991 > Remove release-plugin dependency from continuum-release and instead use > maven-release-m

[jira] Created: (MNG-2632) Setting property in profiles is not evaluated for POM validation

Setting property in profiles is not evaluated for POM validation Key: MNG-2632 URL: http://jira.codehaus.org/browse/MNG-2632 Project: Maven 2 Issue Type: Bug Componen

[jira] Commented: (MPPDF-57) Unable to remove cover type and version

[ http://jira.codehaus.org/browse/MPPDF-57?page=comments#action_78510 ] Arnaud Heritier commented on MPPDF-57: -- Wendy, which release of maven are you using ? m1.0 or a beta/snapshot of m1.1 ? > Unable to remove cover type and version > -

[jira] Commented: (MNG-2631) M2 searches artefacts in wrong repo when using ranges

[ http://jira.codehaus.org/browse/MNG-2631?page=comments#action_78508 ] Carlos Sanchez commented on MNG-2631: - You haven't set releases to false in the snapshot repo so for maven it's also a releases repo > M2 searches artefacts in wrong rep

[jira] Commented: (MNG-2631) M2 searches artefacts in wrong repo when using ranges

[ http://jira.codehaus.org/browse/MNG-2631?page=comments#action_78507 ] Sebastian Krebs commented on MNG-2631: -- Sorry, my fault, I've forgotten to write the following. I've specified those two repositories in my settings.xml as well.

[jira] Created: (MIDEA-75) mvn idea:idea fails with StringIndexOutOfBoundsException (toRelative method) when adding resource to base project

mvn idea:idea fails with StringIndexOutOfBoundsException (toRelative method) when adding resource to base project - Key: MIDEA-75 URL: http://jira.code

[jira] Commented: (MNG-2631) M2 searches artefacts in wrong repo when using ranges

[ http://jira.codehaus.org/browse/MNG-2631?page=comments#action_78506 ] Carlos Sanchez commented on MNG-2631: - distributionManagement is only used for uploads, not for downloads so that's not the problem. You need to provide more info > M2 s

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

[ http://jira.codehaus.org/browse/MNG-1577?page=comments#action_78502 ] Bugittaa Pahasti commented on MNG-1577: --- My opinion is that the scope should be also possible to override, because there are so many poms with invalid dependencies. Per

[jira] Created: (MNG-2631) M2 searches artefacts in wrong repo when using ranges

M2 searches artefacts in wrong repo when using ranges - Key: MNG-2631 URL: http://jira.codehaus.org/browse/MNG-2631 Project: Maven 2 Issue Type: Bug Components: Artifacts and Repo

[jira] Created: (MDEP-45) Documentation is wrong on maven.apache.org

Documentation is wrong on maven.apache.org -- Key: MDEP-45 URL: http://jira.codehaus.org/browse/MDEP-45 Project: Maven 2.x Dependency Plugin Issue Type: Bug Affects Versions: 2.0 Report