[jira] Updated: (MNG-2919) Scope defined in dependencyManagement section of parent pom overwrites scope of current artifact

[ http://jira.codehaus.org/browse/MNG-2919?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joerg Schaible updated MNG-2919: Attachment: MNG-2919.zip Simple setup to demonstrate the problem. > Scope defined in dependencyManagement

[jira] Commented: (MNG-2931) DefaultArtifactCollector changes the version of the originatingArtifact if it's in the dependencyManagement with another version

[ http://jira.codehaus.org/browse/MNG-2931?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_92126 ] Joerg Schaible commented on MNG-2931: - The version of the current artifact has to win! See, we manage all our versions in a

[jira] Commented: (MPARTIFACT-61) scpexe is a noop

[ http://jira.codehaus.org/browse/MPARTIFACT-61?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_92984 ] Joerg Schaible commented on MPARTIFACT-61: -- Not a problem anymore, at least for me ... using M2 since 1 year ;-)

[jira] Commented: (MAVENUPLOAD-1500) Upload jMock 2.0.0

[ http://jira.codehaus.org/browse/MAVENUPLOAD-1500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_94054 ] Joerg Schaible commented on MAVENUPLOAD-1500: - @Carlos Please close this. This bundle contains not jMock 2.

[jira] Commented: (MNG-2968) Forbid dots in artifactId

[ http://jira.codehaus.org/browse/MNG-2968?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_94832 ] Joerg Schaible commented on MNG-2968: - Isn't it possible to use a colon as separator? This is also used in several notation

[jira] Commented: (SUREFIRE-115) Surefire-JUnit does not recognize "suite"-methods

[ http://jira.codehaus.org/browse/SUREFIRE-115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_94928 ] Joerg Schaible commented on SUREFIRE-115: - I don't know, why this is still open. The suite method is called since ve

[jira] Commented: (MJAR-72) Option to include source within the jar artifact

[ http://jira.codehaus.org/browse/MJAR-72?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_95807 ] Joerg Schaible commented on MJAR-72: You can simply declare the sources as resources. > Option to include source within the

[jira] Commented: (MSITE-232) Deploy multi module site to windows share

[ http://jira.codehaus.org/browse/MSITE-232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_96808 ] Joerg Schaible commented on MSITE-232: -- Did you try to use a correct URL? That one starts with 3 slashes, so in your case

[jira] Created: (MEV-539) XStream 1.2.x relocation POMs wrong on central repo

XStream 1.2.x relocation POMs wrong on central repo --- Key: MEV-539 URL: http://jira.codehaus.org/browse/MEV-539 Project: Maven Evangelism Issue Type: Task Components: Invalid POM

[jira] Commented: (MAVENUPLOAD-1619) Please upload XMLUnit for Java 1.1

[ http://jira.codehaus.org/browse/MAVENUPLOAD-1619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_101299 ] Joerg Schaible commented on MAVENUPLOAD-1619: - Such a dependency should then be marked as optional. -- Jörg

[jira] Commented: (MNG-3090) Nearest dependency, which is not included by a filter, wins, although a farthest dependency, which is included by the same filter, does not win.

[ http://jira.codehaus.org/browse/MNG-3090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_101446 ] Joerg Schaible commented on MNG-3090: - This might also be correlated to an issue I reported on the list just before M207 w

[jira] Commented: (MAVENUPLOAD-1619) Please upload XMLUnit for Java 1.1

[ http://jira.codehaus.org/browse/MAVENUPLOAD-1619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_101675 ] Joerg Schaible commented on MAVENUPLOAD-1619: - And to make the long story short: Simply add true to the d

[jira] Commented: (MEV-535) xmlbeans 2.3.0 is located in the wrong directory (even though the pom file is correct

[ http://jira.codehaus.org/browse/MEV-535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_102017 ] Joerg Schaible commented on MEV-535: Carlos, can you reopen this issue? The xmlbeans-plugin is referring the artifacts at t

[jira] Created: (MEV-561) Maven reports invalid POM for xpp3:xpp3:1.1.4c and xpp3:xpp3_min:1.1.4c

Maven reports invalid POM for xpp3:xpp3:1.1.4c and xpp3:xpp3_min:1.1.4c --- Key: MEV-561 URL: http://jira.codehaus.org/browse/MEV-561 Project: Maven Evangelism Issue Type: B

[jira] Commented: (MJAR-53) In pom with packaging "war" the generated jar will be installed in repo instead of the war

[ http://jira.codehaus.org/browse/MJAR-53?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_116348 ] Joerg Schaible commented on MJAR-53: This is more or less the functionality of MWAR-33. > In pom with packaging "war" the g

[jira] Commented: (MJAR-53) In pom with packaging "war" the generated jar will be installed in repo instead of the war

[ http://jira.codehaus.org/browse/MJAR-53?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_116353 ] Joerg Schaible commented on MJAR-53: You should have read all comments to that issue ;-) > In pom with packaging "war" the

[jira] Commented: (MJAR-53) In pom with packaging "war" the generated jar will be installed in repo instead of the war

[ http://jira.codehaus.org/browse/MJAR-53?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_116356 ] Joerg Schaible commented on MJAR-53: The proposed solution at the end is that "mvn install" creates a war that does not inc

[jira] Commented: (MNG-2290) Generated URLs in POMs of child modules

[ http://jira.codehaus.org/browse/MNG-2290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_116727 ] Joerg Schaible commented on MNG-2290: - As previously stated, the original request was created due to a lock of Maven knowl

[jira] Closed: (MJAR-13) configure test-jar to include only special classes of the test source

[ http://jira.codehaus.org/browse/MJAR-13?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joerg Schaible closed MJAR-13. -- Resolution: Duplicate Duplicated by XSTR-30 > configure test-jar to include only special classes of the test so

[jira] Commented: (MJAR-13) configure test-jar to include only special classes of the test source

[ http://jira.codehaus.org/browse/MJAR-13?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_118224 ] Joerg Schaible commented on MJAR-13: Sorry, no, MJAR-30 :-) > configure test-jar to include only special classes of the tes

[jira] Commented: (MRELEASE-300) Regression: release:prepare fails for svn

[ http://jira.codehaus.org/browse/MRELEASE-300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_120154 ] Joerg Schaible commented on MRELEASE-300: - Interesting. Yes, we use the Cobertura also, but it works with 2.0-beta-

[jira] Commented: (MRELEASE-303) Resolved SNAPSHOT versions are overwritten

[ http://jira.codehaus.org/browse/MRELEASE-303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_121732 ] Joerg Schaible commented on MRELEASE-303: - This problem is not only major, it is a blocker. I just released an arti

[jira] Commented: (MJAR-98) The JAR-plugin cannot bundle binary (pdf) file

[ http://jira.codehaus.org/browse/MJAR-98?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_121993 ] Joerg Schaible commented on MJAR-98: You can configure th resource plugin to run twice with different configuration, so sim

[jira] Commented: (MCOMPILER-65) Intelligent fork or bootclasspath based on desired target JDK

[ http://jira.codehaus.org/browse/MCOMPILER-65?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_122023 ] Joerg Schaible commented on MCOMPILER-65: - It's too short sighted to think only of JDK 1.4 vs. JDK 5. For some libr

[jira] Commented: (MECLIPSE-120) Force inter-project dependencies

[ http://jira.codehaus.org/browse/MECLIPSE-120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_122017 ] Joerg Schaible commented on MECLIPSE-120: - I think we'll have to try out how this is suitable in daily work. As I a

[jira] Commented: (MECLIPSE-344) connecting existing workspace artifact-projects

[ http://jira.codehaus.org/browse/MECLIPSE-344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_122018 ] Joerg Schaible commented on MECLIPSE-344: - Will it link always all projects or is it possible to link only the SNAP

[jira] Commented: (MECLIPSE-120) Force inter-project dependencies

[ http://jira.codehaus.org/browse/MECLIPSE-120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_122364 ] Joerg Schaible commented on MECLIPSE-120: - IMHO no, I can reopen it, if the current functionality meets my use case

[jira] Commented: (MECLIPSE-387) download source should accept exclusion of artifact

[ http://jira.codehaus.org/browse/MECLIPSE-387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_122384 ] Joerg Schaible commented on MECLIPSE-387: - Well, the Eclipse plugin already cached that, but unfortunately in the t

[jira] Commented: (MNG-3259) Regression: Maven drops dependencies in multi-module build

[ http://jira.codehaus.org/browse/MNG-3259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_124262 ] Joerg Schaible commented on MNG-3259: - Is there anywhere a M209-SNAPSHOT available? I am happy to test it myself. I am rea

[jira] Commented: (MNG-3259) Regression: Maven drops dependencies in multi-module build

[ http://jira.codehaus.org/browse/MNG-3259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_124926 ] Joerg Schaible commented on MNG-3259: - Although I feel a bit uncomfortable, if such a problem suddenly vanished without id

[jira] Created: (MJAR-105) Regression: Build fails for an empty main jar with 2.2

Regression: Build fails for an empty main jar with 2.2 -- Key: MJAR-105 URL: http://jira.codehaus.org/browse/MJAR-105 Project: Maven 2.x Jar Plugin Issue Type: Bug Affects Versions: 2.2

[jira] Commented: (MJAR-105) Regression: Build fails for an empty main jar with 2.2

[ http://jira.codehaus.org/browse/MJAR-105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=131099#action_131099 ] Joerg Schaible commented on MJAR-105: - In your example, the resulting jar is not empty. Looking for

[jira] Commented: (MSITE-318) site:deploy unable to utilize UNC paths

[ http://jira.codehaus.org/browse/MSITE-318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=132833#action_132833 ] Joerg Schaible commented on MSITE-318: -- Just as a side note, we deploy our site docs since years

[jira] Commented: (MNG-3556) XML entity not supported in Maven 2

[ http://jira.codehaus.org/browse/MNG-3556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=132937#action_132937 ] Joerg Schaible commented on MNG-3556: - AFAICS entity support was dropped for M2 intentionally, sinc

[jira] Created: (MNG-3566) Phase prepare-package not available

Phase prepare-package not available --- Key: MNG-3566 URL: http://jira.codehaus.org/browse/MNG-3566 Project: Maven 2 Issue Type: Bug Components: Plugins and Lifecycle Affects Versions: 2.0.9

[jira] Commented: (MNG-3566) Phase prepare-package not available

[ http://jira.codehaus.org/browse/MNG-3566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=133552#action_133552 ] Joerg Schaible commented on MNG-3566: - Even following all pointers I found no reason why this phase

[jira] Reopened: (MECLIPSE-120) Force inter-project dependencies

[ http://jira.codehaus.org/browse/MECLIPSE-120?page=all ] Joerg Schaible reopened MECLIPSE-120: - "Sorry but we can't do this. This would present the user with a different set of dependency relations in eclipse than is really defined." Gosh

[jira] Commented: (MECLIPSE-120) Force inter-project dependencies

[ http://jira.codehaus.org/browse/MECLIPSE-120?page=comments#action_77004 ] Joerg Schaible commented on MECLIPSE-120: - bq. Your first problem is another issue (MECLIPSE-152), that I'd like to see solved there. Forcing snapshot versions on

[jira] Commented: (MECLIPSE-108) .wtpmodules with version 2.4 for javax.servlet:servlet-api:2.3

[ http://jira.codehaus.org/browse/MECLIPSE-108?page=comments#action_78646 ] Joerg Schaible commented on MECLIPSE-108: - The hard coded 2.4 value for the web facet also prevents you from deploying the app into a Tomcat 4.x runtime. > .wtpm

[jira] Commented: (MRELEASE-160) The next snapshot version is not used un submodules

[ http://jira.codehaus.org/browse/MRELEASE-160?page=comments#action_79350 ] Joerg Schaible commented on MRELEASE-160: - Hi Tom, I am not talking of the dryRun. The described behavior applies to the real release process. - Jörg > The nex

[jira] Commented: (SCM-190) Location of cvs-settings.xml should be in user.home and not in user.dir

[ http://jira.codehaus.org/browse/SCM-190?page=comments#action_79565 ] Joerg Schaible commented on SCM-190: You realize, that this sounds slightly strange for a component using a "maven-" prefix in its name? ;-) Personally I'd rather decrease

[jira] Commented: (MSUREFIRE-170) Classpath in XML report is wrong

[ http://jira.codehaus.org/browse/MSUREFIRE-170?page=comments#action_80682 ] Joerg Schaible commented on MSUREFIRE-170: -- If the trunk can be used together with upcoming Maven 2.0.5 ... ;-) > Classpath in XML report is wrong > --

[jira] Commented: (MAVENUPLOAD-1240) Please upload new version of xmlenc

[ http://jira.codehaus.org/browse/MAVENUPLOAD-1240?page=comments#action_80725 ] Joerg Schaible commented on MAVENUPLOAD-1240: - Step 1 is creating the bundle ... you did not provide one (re-read the instructions). See, it is a tedious

[jira] Commented: (MAVENUPLOAD-1280) jMimeMagic 0.1.1

[ http://jira.codehaus.org/browse/MAVENUPLOAD-1280?page=comments#action_83027 ] Joerg Schaible commented on MAVENUPLOAD-1280: - Some comments, Carlos might correct me: 1/ You've provided in the bundle a M1 project.xml, but the (automa

[jira] Commented: (MAVENUPLOAD-1280) jMimeMagic 0.1.1

[ http://jira.codehaus.org/browse/MAVENUPLOAD-1280?page=comments#action_83034 ] Joerg Schaible commented on MAVENUPLOAD-1280: - MAVENUPLOAD-373, hehehe, time flies I think it is enough to provide a new bundle URL here in a comment. B

[jira] Commented: (MNG-2589) Inherit transitive dependencies with runtime scope

[ http://jira.codehaus.org/browse/MNG-2589?page=comments#action_85292 ] Joerg Schaible commented on MNG-2589: - Should have been "Transitive dependencies of scope "compile" should be inherited with scope "runtime" only" > Inherit transitive d

[jira] Commented: (MNG-2676) maven-dependency-analyser shared component & plugin

[ http://jira.codehaus.org/browse/MNG-2676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_85973 ] Joerg Schaible commented on MNG-2676: - Hi Mark, looks great! A real help to identify the used deps. Biggest problem though

[jira] Commented: (MNG-2362) Deployed POM is not valid XML

[ http://jira.codehaus.org/browse/MNG-2362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_88542 ] Joerg Schaible commented on MNG-2362: - Hi Jason, the POM is not rewritten anymore installing or deploying the artifact wit

[jira] Commented: (MNG-2850) DependencyVisitor bug fix & more tests

[ http://jira.codehaus.org/browse/MNG-2850?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_88606 ] Joerg Schaible commented on MNG-2850: - Applied with svn 512020. > DependencyVisitor bug fix & more tests >

[jira] Created: (MRELEASE-201) Deployed POM is not valid XML

Deployed POM is not valid XML - Key: MRELEASE-201 URL: http://jira.codehaus.org/browse/MRELEASE-201 Project: Maven 2.x Release Plugin Issue Type: Bug Reporter: Joerg Schaible Attachments: MNG-

[jira] Commented: (MCHANGES-72) Build Failure using IBM JDK 1.4.2 SR7

[ http://jira.codehaus.org/browse/MCHANGES-72?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_89500 ] Joerg Schaible commented on MCHANGES-72: Hint: Caused by: java.lang.NoClassDefFoundError: com/sun/net/ssl/internal/s

[jira] Created: (MAVENUPLOAD-2478) jtnef 1.5.0 upload request

jtnef 1.5.0 upload request -- Key: MAVENUPLOAD-2478 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2478 Project: Maven Upload Requests Issue Type: Task Reporter: Joerg Schaible The Java TNEF package is

[jira] Commented: (MASSEMBLY-425) Inconsistant inheritance

[ http://jira.codehaus.org/browse/MASSEMBLY-425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=180892#action_180892 ] Joerg Schaible commented on MASSEMBLY-425: -- Therefore you should set the version of your

[jira] Created: (MAVENUPLOAD-2492) JAI 1.1.3

JAI 1.1.3 - Key: MAVENUPLOAD-2492 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2492 Project: Maven Upload Requests Issue Type: Task Reporter: Joerg Schaible http://people.apache.org/~joehni/jai_codec-1.1.3-bundle.ja

[jira] Created: (MAVENUPLOAD-2493) JAI ImageIO 1.1

JAI ImageIO 1.1 --- Key: MAVENUPLOAD-2493 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2493 Project: Maven Upload Requests Issue Type: Task Reporter: Joerg Schaible New version 1.1 of JAI ImageIO, this time with

[jira] Closed: (MASSEMBLY-336) Flag to inline POM dependencies in DependencySets

[ http://jira.codehaus.org/browse/MASSEMBLY-336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joerg Schaible closed MASSEMBLY-336. Resolution: Won't Fix Found a different way to solve my problem and I am not interested in ma

[jira] Created: (MECLIPSE-585) [regression] plugin fails to create Eclipse projects in 2.7

[regression] plugin fails to create Eclipse projects in 2.7 --- Key: MECLIPSE-585 URL: http://jira.codehaus.org/browse/MECLIPSE-585 Project: Maven 2.x Eclipse Plugin Issue Type: Bug

[jira] Commented: (MECLIPSE-585) [regression] plugin fails to create Eclipse projects in 2.7

[ http://jira.codehaus.org/browse/MECLIPSE-585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=183069#action_183069 ] Joerg Schaible commented on MECLIPSE-585: - I shuffled the vfs resources a bit, so the probl

[jira] Reopened: (MAVENUPLOAD-2492) JAI 1.1.3

[ http://jira.codehaus.org/browse/MAVENUPLOAD-2492?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joerg Schaible reopened MAVENUPLOAD-2492: - Can we at least publish the pom only then? If I have to prepare a different bundle f

[jira] Reopened: (MAVENUPLOAD-2493) JAI ImageIO 1.1

[ http://jira.codehaus.org/browse/MAVENUPLOAD-2493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joerg Schaible reopened MAVENUPLOAD-2493: - Can we at least publish the pom only then? If I have to prepare a different bundle f

[jira] Commented: (MRELEASE-460) Please upgrade to JDOM 1.1; current JDOM 1.0 contains a bug in parsing comments starting with hyphen

[ http://jira.codehaus.org/browse/MRELEASE-460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=183358#action_183358 ] Joerg Schaible commented on MRELEASE-460: - Just a reminder: JDOM has changed groupId with v

[jira] Created: (MAVENUPLOAD-2517) jsch-0.1.42

jsch-0.1.42 --- Key: MAVENUPLOAD-2517 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2517 Project: Maven Upload Requests Issue Type: Task Reporter: Joerg Schaible JSch is a pure Java implementation of SSH2. Version bu

[jira] Commented: (MJAR-121) blank space and new line in manifest classpath

[ http://jira.codehaus.org/browse/MJAR-121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=184241#action_184241 ] Joerg Schaible commented on MJAR-121: - And what's now actually your problem? > blank space and new

[jira] Commented: (MNG-4257) Add the possibility to have 2 dependencies with the same groupId:artifactId but not the same version

[ http://jira.codehaus.org/browse/MNG-4257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=184951#action_184951 ] Joerg Schaible commented on MNG-4257: - @Brian: Actually there is really an issue with this! Please

[jira] Commented: (MNG-4263) Dependencies resolution & the order in the declaration

[ http://jira.codehaus.org/browse/MNG-4263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=185127#action_185127 ] Joerg Schaible commented on MNG-4263: - Since M2.0.10 this is deterministic, in older versions there

[jira] Created: (MRELEASE-469) Plugin hangs in preparation while checking deps and plugins for snapshots

Plugin hangs in preparation while checking deps and plugins for snapshots - Key: MRELEASE-469 URL: http://jira.codehaus.org/browse/MRELEASE-469 Project: Maven 2.x Release Plugin

[jira] Closed: (MRELEASE-469) Plugin hangs in preparation while checking deps and plugins for snapshots

[ http://jira.codehaus.org/browse/MRELEASE-469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joerg Schaible closed MRELEASE-469. --- Resolution: Not A Bug Stupid me! I forgot that I colorized my Maven output last week (piping the

[jira] Commented: (MJAR-105) Regression: Build fails for an empty main jar with 2.2

[ http://jira.codehaus.org/browse/MJAR-105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=188523#action_188523 ] Joerg Schaible commented on MJAR-105: - With package type "pom" you cannot generate Eclipse projects

[jira] Commented: (MRELEASE-478) release:prepare creates excessive level in the directory structure when used with SVN client 1.6.3 and up

[ http://jira.codehaus.org/browse/MRELEASE-478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=188790#action_188790 ] Joerg Schaible commented on MRELEASE-478: - Well, as long as nobody knows what you provide f

[jira] Commented: (MRELEASE-479) Option to handle plugins missing explicit version number

[ http://jira.codehaus.org/browse/MRELEASE-479?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=189642#action_189642 ] Joerg Schaible commented on MRELEASE-479: - While this is true in general, there are excepti

[jira] Commented: (MEAR-66) finalName taken into account for full build but not for ear build

[ http://jira.codehaus.org/browse/MEAR-66?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=191371#action_191371 ] Joerg Schaible commented on MEAR-66: Do it the other way round. Drop the final name thing in the EJB

[jira] Commented: (MJAR-130) Sign goal fails on projects with maven-plugin packaging

[ http://jira.codehaus.org/browse/MJAR-130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=194610#action_194610 ] Joerg Schaible commented on MJAR-130: - The jar:sign goal is deprecated, use the jarsigner plugin.

[jira] Commented: (MAVENUPLOAD-1774) Sync de.berlios.jsunit

[ http://jira.codehaus.org/browse/MAVENUPLOAD-1774?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=196761#action_196761 ] Joerg Schaible commented on MAVENUPLOAD-1774: - The sync is broken since 19th Octobe

[jira] Commented: (MAVENUPLOAD-1774) Sync de.berlios.jsunit

[ http://jira.codehaus.org/browse/MAVENUPLOAD-1774?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=197058#action_197058 ] Joerg Schaible commented on MAVENUPLOAD-1774: - Are you sure? It's the last part of

[jira] Updated: (MAVENUPLOAD-1774) Sync de.berlios.jsunit

[ http://jira.codehaus.org/browse/MAVENUPLOAD-1774?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joerg Schaible updated MAVENUPLOAD-1774: Attachment: screenshot.png It's more to the bottom, see the attached screenshot. >

[jira] Commented: (MDEP-243) dependency:resolve decides to take older (incompatible) version for transitive dep

[ http://jira.codehaus.org/browse/MDEP-243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=198731#action_198731 ] Joerg Schaible commented on MDEP-243: - This works exactly as defined. The depMgmt section is used t

[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-tabpanel&focusedCommentId=200290#action_200290 ] Joerg Schaible commented on SUREFIRE-569: - As workaround simply unpack the jar with the dep

[jira] Created: (MDEP-245) goal to check classpath for duplicate resources/classes

goal to check classpath for duplicate resources/classes --- Key: MDEP-245 URL: http://jira.codehaus.org/browse/MDEP-245 Project: Maven 2.x Dependency Plugin Issue Type: New Feature

[jira] Commented: (MSUREFIRE-56) The "pertest" option for forking mode should be renamed more appropriately

[ http://jira.codehaus.org/browse/MSUREFIRE-56?page=comments#action_63285 ] Joerg Schaible commented on MSUREFIRE-56: - Backwards compatibility was already broken by renaming "perTest" to "pertest". > The "pertest" option for forking mode should be re

[jira] Commented: (MNG-1755) Improve support for in reactor builds

[ http://jira.codehaus.org/browse/MNG-1755?page=comments#action_63291 ] Joerg Schaible commented on MNG-1755: - Was about to suggest the same or at least something similar: Despite Mike's developerManagement the teamManagement would contain dev

[jira] Created: (MRELEASE-90) Exception if version is SNAPSHOT

Exception if version is SNAPSHOT Key: MRELEASE-90 URL: http://jira.codehaus.org/browse/MRELEASE-90 Project: Maven 2.x Release Plugin Type: Bug Versions: 2.0-beta-3 Reporter: Joerg Schaible If the project has a very simp

[jira] Created: (SCM-185) Validity check rejects valid protocol

Validity check rejects valid protocol - Key: SCM-185 URL: http://jira.codehaus.org/browse/SCM-185 Project: Maven SCM Type: Bug Components: maven-scm-provider-svn Versions: 1.0-beta-2 Reporter: Joerg Schaible Acco

[jira] Commented: (MRELEASE-96) Improve handling of Super POM snapshots.

[ http://jira.codehaus.org/browse/MRELEASE-96?page=comments#action_63918 ] Joerg Schaible commented on MRELEASE-96: Hi Brett, the scenario for a Super POM is different. Think of the Super POM as vehicle that does something similar to Gump. If you h

[jira] Commented: (MRELEASE-87) Poms are written with wrong encodings

[ http://jira.codehaus.org/browse/MRELEASE-87?page=comments#action_63919 ] Joerg Schaible commented on MRELEASE-87: JIRA did some own interpretation of the last comment, so the name of the developer contained originally: {noformat} ö ö € {noformat}

[jira] Created: (MNG-2237) Inherited plugin executed twice if child pom merges configuration

Inherited plugin executed twice if child pom merges configuration - Key: MNG-2237 URL: http://jira.codehaus.org/browse/MNG-2237 Project: Maven 2 Type: Bug Components: Inheritence and Interpolation

[jira] Commented: (WAGON-42) wagon-scm (svn provider) - large paths under windows breaks download.

[ http://jira.codehaus.org/browse/WAGON-42?page=comments#action_64161 ] Joerg Schaible commented on WAGON-42: - This might be a manifestation of http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4403166. Although Sun claims the bug is fixed, a lot of pe

[jira] Created: (MAVENUPLOAD-873) Upload JAI POMs

Upload JAI POMs --- Key: MAVENUPLOAD-873 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-873 Project: maven-upload-requests Type: Task Reporter: Joerg Schaible POMs for JAI are missing on ibiblio. Additional bundles: http://people.apache.org/~joe

[jira] Commented: (MAVENUPLOAD-873) Upload JAI POMs

[ http://jira.codehaus.org/browse/MAVENUPLOAD-873?page=comments#action_64622 ] Joerg Schaible commented on MAVENUPLOAD-873: > groupid should be com.sun.media for consistency (only three levels) OK. Although Sun often replaces the "javax." part

[jira] Commented: (MAVENUPLOAD-873) Upload JAI POMs

[ http://jira.codehaus.org/browse/MAVENUPLOAD-873?page=comments#action_64626 ] Joerg Schaible commented on MAVENUPLOAD-873: BTW: Sun refers both versions as 1.1.2_01 and 1.0_01. Should I adjust this also? If yes, is it enough to update the POMs

[jira] Commented: (MAVENUPLOAD-873) Upload JAI POMs

[ http://jira.codehaus.org/browse/MAVENUPLOAD-873?page=comments#action_64631 ] Joerg Schaible commented on MAVENUPLOAD-873: OK. All bundles are updated and contain _0x version scheme, distributionManagement with URLs to the latest page, that doe

[jira] Created: (MAVENUPLOAD-879) Upload acrobat-viewer-bean from Adobe

Upload acrobat-viewer-bean from Adobe - Key: MAVENUPLOAD-879 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-879 Project: maven-upload-requests Type: Task Reporter: Joerg Schaible This bundle contains the free acrobat-viewe

[jira] Commented: (MWAR-35) War packaging fails with long file names

[ http://jira.codehaus.org/browse/MWAR-35?page=comments#action_64640 ] Joerg Schaible commented on MWAR-35: The question is: Can you create and access (r/w) such a file with *Java*? We know the same behaviour deploying in Weblogic - Maven is not involved

[jira] Commented: (MAVENUPLOAD-873) Upload JAI POMs

[ http://jira.codehaus.org/browse/MAVENUPLOAD-873?page=comments#action_64718 ] Joerg Schaible commented on MAVENUPLOAD-873: Bundles updated again. > Upload JAI POMs > --- > > Key: MAVENUPLOAD-873 > URL: http://jira.

[jira] Created: (MEV-386) FOP 0.20.5 dependencies

FOP 0.20.5 dependencies --- Key: MEV-386 URL: http://jira.codehaus.org/browse/MEV-386 Project: Maven Evangelism Type: Improvement Components: Missing POM Reporter: Joerg Schaible Attachments: fop-0.20.5.patch The POM of fop:fop:0.20.5 w

[jira] Updated: (MEV-386) FOP 0.20.5 dependencies

[ http://jira.codehaus.org/browse/MEV-386?page=all ] Joerg Schaible updated MEV-386: --- Attachment: fop-0.20.5.patch > FOP 0.20.5 dependencies > --- > > Key: MEV-386 > URL: http://jira.codehaus.org/browse/MEV-386 >

[jira] Updated: (MEV-386) FOP 0.20.5 dependencies

[ http://jira.codehaus.org/browse/MEV-386?page=all ] Joerg Schaible updated MEV-386: --- Attachment: fop-0.20.5.patch > FOP 0.20.5 dependencies > --- > > Key: MEV-386 > URL: http://jira.codehaus.org/browse/MEV-386 >

[jira] Commented: (MEV-386) FOP 0.20.5 dependencies

[ http://jira.codehaus.org/browse/MEV-386?page=comments#action_64729 ] Joerg Schaible commented on MEV-386: Sorry, you have to go the the "Manage Attachments" to select the newest patch. > FOP 0.20.5 dependencies > --- > > Ke

[jira] Updated: (MEV-386) FOP 0.20.5 dependencies

[ http://jira.codehaus.org/browse/MEV-386?page=all ] Joerg Schaible updated MEV-386: --- Attachment: fop-0.20.5.patch > FOP 0.20.5 dependencies > --- > > Key: MEV-386 > URL: http://jira.codehaus.org/browse/MEV-386 >

[jira] Closed: (MNG-1571) Wrong calculation of transient dependecies if artifact is referenced from different scopes

[ http://jira.codehaus.org/browse/MNG-1571?page=all ] Joerg Schaible closed MNG-1571: --- Resolution: Fixed Fix Version: (was: 2.0.5) 2.0.4 Was fixed in 2.0.4 > Wrong calculation of transient dependecies if artifact is referenc

[jira] Created: (MNG-2289) Newer SNAPSHOT parents in the remote repository are ignored

Newer SNAPSHOT parents in the remote repository are ignored --- Key: MNG-2289 URL: http://jira.codehaus.org/browse/MNG-2289 Project: Maven 2 Type: Bug Components: Inheritence and Interpolation Versions:

<    1   2   3   4   5   >