[jira] [Created] (SUREFIRE-2134) add support for rerunFailingTestsCount option to TestNG provider

Ian Springer created SUREFIRE-2134: -- Summary: add support for rerunFailingTestsCount option to TestNG provider Key: SUREFIRE-2134 URL: https://issues.apache.org/jira/browse/SUREFIRE-2134 Project: Mav

[jira] [Created] (MSHADE-248) shading fails with "error in opening zip file" if createSourcesJar=true and an invalid sources jar file is encountered

Ian Springer created MSHADE-248: --- Summary: shading fails with "error in opening zip file" if createSourcesJar=true and an invalid sources jar file is encountered Key: MSHADE-248 URL: https://issues.apache.org/jira/b

[jira] [Commented] (MSHADE-248) shading fails with "error in opening zip file" if createSourcesJar=true and an invalid sources jar file is encountered

[ https://issues.apache.org/jira/browse/MSHADE-248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15858262#comment-15858262 ] Ian Springer commented on MSHADE-248: - It's our internal Nexus server, which proxies c

[jira] [Commented] (MSHADE-248) shading fails with "error in opening zip file" if createSourcesJar=true and an invalid sources jar file is encountered

[ https://issues.apache.org/jira/browse/MSHADE-248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15858270#comment-15858270 ] Ian Springer commented on MSHADE-248: - Here is the content of bsh-2.0b4-sources.jar:

[jira] [Commented] (MSHADE-248) shading fails with "error in opening zip file" if createSourcesJar=true and an invalid sources jar file is encountered

[ https://issues.apache.org/jira/browse/MSHADE-248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15858367#comment-15858367 ] Ian Springer commented on MSHADE-248: - What is extremely unlikely? I've been using Mav

[jira] [Commented] (MSHADE-248) shading fails with "error in opening zip file" if createSourcesJar=true and an invalid sources jar file is encountered

[ https://issues.apache.org/jira/browse/MSHADE-248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15858406#comment-15858406 ] Ian Springer commented on MSHADE-248: - Our Nexus repo has been running for 5 years or

[jira] [Commented] (MSHADE-248) shading fails with "error in opening zip file" if createSourcesJar=true and an invalid sources jar file is encountered

[ https://issues.apache.org/jira/browse/MSHADE-248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15858446#comment-15858446 ] Ian Springer commented on MSHADE-248: - Well, it turned out in this case, I am able to

[jira] [Created] (MENFORCER-348) add a graalvm enforcer rule

Ian Springer created MENFORCER-348: -- Summary: add a graalvm enforcer rule Key: MENFORCER-348 URL: https://issues.apache.org/jira/browse/MENFORCER-348 Project: Maven Enforcer Plugin Issue Typ

[jira] [Commented] (SUREFIRE-1827) The console output is not flushed

[ https://issues.apache.org/jira/browse/SUREFIRE-1827?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17446201#comment-17446201 ] Ian Springer commented on SUREFIRE-1827: I think we are also encountering this

[jira] Created: (MCOMPILER-162) when annotation processing is disabled by specifying none, target/generated-sources/annotations and target/generated-sources/test-annotations directories a

when annotation processing is disabled by specifying none, target/generated-sources/annotations and target/generated-sources/test-annotations directories are still created, passed to javac via -s option, and added to project sources dirs --

[jira] (MDEP-128) Support ability to specify multiple "includeScope" parameters

[ https://jira.codehaus.org/browse/MDEP-128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=294016#comment-294016 ] Ian Springer commented on MDEP-128: --- +1 on improving the docs. At the very least the descriptions o

[jira] (MNG-4226) Better detection of JAVA_HOME on Apple Mac OS X

[ https://jira.codehaus.org/browse/MNG-4226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=350382#comment-350382 ] Ian Springer commented on MNG-4226: --- When you run "java -version", the shell is going to run the fi

[jira] (SUREFIRE-898) error with 2.12.1 (works with 2.12)

[ https://jira.codehaus.org/browse/SUREFIRE-898?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=311120#comment-311120 ] Ian Springer commented on SUREFIRE-898: --- I'm still seeing this with 2.12.4 (and not with 2.

[jira] Commented: (MNG-1991) Can't get transitive dependencies from a war pom when this war is added as a depdency of a project

[ http://jira.codehaus.org/browse/MNG-1991?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=207349#action_207349 ] Ian Springer commented on MNG-1991: --- Note: The maven warpath plugin (http://static.appfuse.org/maven

[jira] Commented: (MNG-3641) Lack of error checks on profiles

[ http://jira.codehaus.org/browse/MNG-3641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=213203#action_213203 ] Ian Springer commented on MNG-3641: --- The current warning message is: "Profile with id: '" + explicit

[jira] Created: (MNG-4583) warning printed when a pom does not use an activated profile is poorly worded and also should not be printed for multi-module builds

warning printed when a pom does not use an activated profile is poorly worded and also should not be printed for multi-module builds Key: MNG-4583

[jira] Commented: (MNG-4583) warning printed when a pom does not use an activated profile is poorly worded and also should not be printed for multi-module builds

[ http://jira.codehaus.org/browse/MNG-4583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=213355#action_213355 ] Ian Springer commented on MNG-4583: --- > [WARNING] The requested profile "foo" could not be activated b

[jira] Commented: (MNG-4583) warning printed when a pom does not use an activated profile is poorly worded and also should not be printed for multi-module builds

[ http://jira.codehaus.org/browse/MNG-4583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=213369#action_213369 ] Ian Springer commented on MNG-4583: --- Great, it's good to hear that's already been addressed. Would y

[jira] Commented: (MNG-4583) warning printed when a pom does not use an activated profile is poorly worded and also should not be printed for multi-module builds

[ http://jira.codehaus.org/browse/MNG-4583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=213380#action_213380 ] Ian Springer commented on MNG-4583: --- Interesting. That's not how activation is described in the docs

[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-tabpanel&focusedCommentId=217651#action_217651 ] Ian Springer commented on MRESOURCES-104: - I think the cause of this is that when the tem

[jira] Issue Comment Edited: (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-tabpanel&focusedCommentId=217651#action_217651 ] Ian Springer edited comment on MRESOURCES-104 at 4/12/10 8:26 AM: -

[jira] Issue Comment Edited: (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-tabpanel&focusedCommentId=217651#action_217651 ] Ian Springer edited comment on MRESOURCES-104 at 4/12/10 9:22 AM: -

[jira] Created: (MRELEASE-396) release:branch goal does not honor autoVersionSubmodules=true configuration property

release:branch goal does not honor autoVersionSubmodules=true configuration property Key: MRELEASE-396 URL: http://jira.codehaus.org/browse/MRELEASE-396 Project: Mav

[jira] Created: (MRELEASE-397) release:prepare goal does not check early enough whether the specified tag already exists in SVN

release:prepare goal does not check early enough whether the specified tag already exists in SVN Key: MRELEASE-397 URL: http://jira.codehaus.org/browse/MRELEASE-397

[jira] Created: (MRELEASE-401) release:prepare should create the SVN tags parent dir if it doesn't already exist, rather than failing

release:prepare should create the SVN tags parent dir if it doesn't already exist, rather than failing -- Key: MRELEASE-401 URL: http://jira.codehaus.org/browse/MR

[jira] Commented: (MRELEASE-401) release:prepare should create the SVN tags parent dir if it doesn't already exist, rather than failing

[ http://jira.codehaus.org/browse/MRELEASE-401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160250#action_160250 ] Ian Springer commented on MRELEASE-401: --- I don't think so. 353 has the error: svn: Commit fa

[jira] Created: (MSUREFIRE-127) when fork is enabled, Surefire should use the same JVM running Maven (i.e. use java.home sysprop), rather than expecting java to be in the system PATH

when fork is enabled, Surefire should use the same JVM running Maven (i.e. use java.home sysprop), rather than expecting java to be in the system PATH ---

[jira] Commented: (MWAR-45) add config prop to specify webapp classes should be zipped and placed into WEB-INF/lib/xxx.jar instead of placed in WEB-INF/classes/

[ http://jira.codehaus.org/browse/MWAR-45?page=comments#action_67041 ] Ian Springer commented on MWAR-45: -- +1 to Torgeir's suggestion. I think having a boolean parameter for enabling the option is more intuitive. > add config prop to specify webapp classe

[jira] Created: (MJAR-45) SVN URLs wrong on generated Source Repository page

SVN URLs wrong on generated Source Repository page -- Key: MJAR-45 URL: http://jira.codehaus.org/browse/MJAR-45 Project: Maven 2.x Jar Plugin Type: Bug Versions: 2.0 Reporter: Ian Springer Priority: Min

[jira] Created: (MNG-2375) Generate docs for mojo goals should list whehter or not each parameter is read-only

Generate docs for mojo goals should list whehter or not each parameter is read-only --- Key: MNG-2375 URL: http://jira.codehaus.org/browse/MNG-2375 Project: Maven 2 Type: Improvement

[jira] Commented: (MEAR-15) Support of sar files

[ http://jira.codehaus.org/browse/MEAR-15?page=comments#action_68117 ] Ian Springer commented on MEAR-15: -- The correct way to configure a SAR bundled in an EAR is not via a connector module, but by adding a service module entry in META-INF/jboss-app.xml, e.

[jira] Commented: (MEAR-15) Support of sar files

[ http://jira.codehaus.org/browse/MEAR-15?page=comments#action_68125 ] Ian Springer commented on MEAR-15: -- Since connector elements are meant for configuring RARs, I think using them to configure SARs is a bit of a hack, even though it may work. My suggest

[jira] Created: (MEAR-31) add ability to configure JBoss-specific deployment options in plugin configuration that will result in a jboss-app.xml descriptor being generated

add ability to configure JBoss-specific deployment options in plugin configuration that will result in a jboss-app.xml descriptor being generated -

[jira] Created: (MRESOURCES-21) when pom specifies multiple resource directories, the directories should be copied in the order they are in the pom

when pom specifies multiple resource directories, the directories should be copied in the order they are in the pom --- Key: MRESOURCES-21 URL: http://jira.codehaus.or

[jira] Created: (MEAR-33) add option to include modules in EAR in exploded (i.e. directory) form, rather than as in jar form

add option to include modules in EAR in exploded (i.e. directory) form, rather than as in jar form -- Key: MEAR-33 URL: http://jira.codehaus.org/browse/MEAR-33

[jira] Updated: (MEAR-33) add option to include modules in EAR in exploded (i.e. directory) form, rather than as in jar form

[ http://jira.codehaus.org/browse/MEAR-33?page=all ] Ian Springer updated MEAR-33: - Attachment: MEAR-33.patch Here's a patch that implements the requested feature. > add option to include modules in EAR in exploded (i.e. directory) form, > rather than as

[jira] Commented: (MEAR-33) add option to include modules in EAR in exploded (i.e. directory) form, rather than as in jar form

[ http://jira.codehaus.org/browse/MEAR-33?page=comments#action_71314 ] Ian Springer commented on MEAR-33: -- Right, in my case, the EAR will ultimately be exploded in my product's distribution, and I also want all of the sub J2EE modules to be exp

[jira] Created: (MNG-2479) add support for optional 'packagingName' element in dependency blocks

add support for optional 'packagingName' element in dependency blocks - Key: MNG-2479 URL: http://jira.codehaus.org/browse/MNG-2479 Project: Maven 2 Issue Type: New Feature

[jira] Commented: (MNG-2479) add support for optional 'packagingName' element in dependency blocks

[ http://jira.codehaus.org/browse/MNG-2479?page=comments#action_71435 ] Ian Springer commented on MNG-2479: --- Hmm, I'm not sure I agree with this. If it was desired to override the default filename for transitive deps, this could be achieved by

[jira] Created: (MEAR-41) publish 2.3-SNAPSHOT to snapshots repo

publish 2.3-SNAPSHOT to snapshots repo --- Key: MEAR-41 URL: http://jira.codehaus.org/browse/MEAR-41 Project: Maven 2.x Ear Plugin Issue Type: Task Affects Versions: 2.3 Reporter: Ian Spri

[jira] Reopened: (MEAR-33) add option to include modules in EAR in exploded (i.e. directory) form, rather than as in jar form

[ http://jira.codehaus.org/browse/MEAR-33?page=all ] Ian Springer reopened MEAR-33: -- I just build 2.3-SNAPSHOT and tried this out. I added the following setting to my ear-plugin config: ejb,war,sar But when I run mvn install, I get the followin

[jira] Created: (MEAR-43) add ability to do filtering (i.e. template var replacement) for files in src/main/application/

add ability to do filtering (i.e. template var replacement) for files in src/main/application/ -- Key: MEAR-43 URL: http://jira.codehaus.org/browse/MEAR-43 Pr

[jira] Commented: (MEAR-43) add ability to do filtering (i.e. template var replacement) for files in src/main/application/

[ http://jira.codehaus.org/browse/MEAR-43?page=comments#action_75405 ] Ian Springer commented on MEAR-43: -- Actually, I think you'd also need a way to specify includes/excludes to specify which files should be filtered. This will allow users to s

[jira] Commented: (MIDEA-94) resolve source jars from localRepo w/o -DdownloadSources

[ http://jira.codehaus.org/browse/MIDEA-94?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_103296 ] Ian Springer commented on MIDEA-94: --- Shouldn't the same change be made for javadoc jars? > resolve source jars from localRe

[jira] Commented: (MRELEASE-217) BUILD FAILURE: The version could not be updated: ${version}

[ http://jira.codehaus.org/browse/MRELEASE-217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_108361 ] Ian Springer commented on MRELEASE-217: --- I am still getting this error with v2.0-beta-6 (mvn 2.0.7). I am doing the s

[jira] Created: (MRELEASE-292) during release:prepare, if one of the goals specified in preparationGoals fails, the release:prepare should abort/fail, but it continues along as if nothing bad happened

during release:prepare, if one of the goals specified in preparationGoals fails, the release:prepare should abort/fail, but it continues along as if nothing bad happened ---

[jira] Commented: (MRELEASE-292) during release:prepare, if one of the goals specified in preparationGoals fails, the release:prepare should abort/fail, but it continues along as if nothing bad happen

[ http://jira.codehaus.org/browse/MRELEASE-292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_109332 ] Ian Springer commented on MRELEASE-292: --- I am using Maven 2.0.7 on Windows XP, but my mvn.bat does appear to contain

[jira] Commented: (MRESOURCES-29) An escape mechanism for property interpolation is missing.

[ http://jira.codehaus.org/browse/MRESOURCES-29?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_111362 ] Ian Springer commented on MRESOURCES-29: I'm still willing to code up my previously suggested fix for this and sub

[jira] Commented: (WAGON-54) Scm Wagon not expanding ${user.home}

[ http://jira.codehaus.org/browse/WAGON-54?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=135160#action_135160 ] Ian Springer commented on WAGON-54: --- Can you please release wagon-scm 1.0-alpha6? I really would like

[jira] Created: (MNG-3756) having two properties that reference each other causes Maven to go into infinite loop

having two properties that reference each other causes Maven to go into infinite loop - Key: MNG-3756 URL: http://jira.codehaus.org/browse/MNG-3756 Project: Maven 2

[jira] Updated: (MNG-3756) having two properties that reference each other causes Maven to go into infinite loop

[ http://jira.codehaus.org/browse/MNG-3756?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ian Springer updated MNG-3756: -- Attachment: pom.xml > having two properties that reference each other causes Maven to go into > infinite loop

[jira] Commented: (MNG-3756) having two properties that reference each other causes Maven to go into infinite loop

[ http://jira.codehaus.org/browse/MNG-3756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=148225#action_148225 ] Ian Springer commented on MNG-3756: --- Sure, it looks like the key is indeed that is has to be within a

[jira] Commented: (MNG-3756) having two properties that reference each other causes Maven to go into infinite loop

[ http://jira.codehaus.org/browse/MNG-3756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=148284#action_148284 ] Ian Springer commented on MNG-3756: --- I don't understand why any recursion would come into play. I thi

[jira] Created: (MNG-3798) some additions for the http://maven.apache.org/powered-by-m2.html page

some additions for the http://maven.apache.org/powered-by-m2.html page -- Key: MNG-3798 URL: http://jira.codehaus.org/browse/MNG-3798 Project: Maven 2 Issue Type: Task

[jira] Commented: (MRELEASE-114) ${project.artifactId} was replaced with it's value during release:perform

[ http://jira.codehaus.org/browse/MRELEASE-114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_93448 ] Ian Springer commented on MRELEASE-114: --- I had ${maven.username} is the value of scm.developerConnection, and it was

[jira] Created: (MENFORCER-2) enforcer plugin is bound to 'default

enforcer plugin is bound to 'default Key: MENFORCER-2 URL: http://jira.codehaus.org/browse/MENFORCER-2 Project: Maven 2.x Enforcer Plugin Issue Type: Bug Reporter: Ian Springer Ass

[jira] Closed: (MENFORCER-2) enforcer plugin is bound to 'default

[ http://jira.codehaus.org/browse/MENFORCER-2?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ian Springer closed MENFORCER-2. Resolution: Incomplete > enforcer plugin is bound to 'default > > >

[jira] Created: (MENFORCER-3) enforcer plugin should be bound to the 'clean' lifecycle in addition to the 'default' lifecycle

enforcer plugin should be bound to the 'clean' lifecycle in addition to the 'default' lifecycle --- Key: MENFORCER-3 URL: http://jira.codehaus.org/browse/MENFORCER-3

[jira] Commented: (MENFORCER-3) enforcer plugin should be bound to the 'clean' lifecycle in addition to the 'default' lifecycle

[ http://jira.codehaus.org/browse/MENFORCER-3?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_94107 ] Ian Springer commented on MENFORCER-3: -- Ah, I didn't realize that was a Maven limitation. Thanks, Ian > enforcer plug

[jira] Closed: (MENFORCER-3) enforcer plugin should be bound to the 'clean' lifecycle in addition to the 'default' lifecycle

[ http://jira.codehaus.org/browse/MENFORCER-3?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ian Springer closed MENFORCER-3. Resolution: Won't Fix Maven does no allow plugins to bind to more than one phase, even if the phases ar

[jira] Created: (SUREFIRE-325) when parsing excludedGroups config prop, trim leading and trailing whitespace off of group names

when parsing excludedGroups config prop, trim leading and trailing whitespace off of group names Key: SUREFIRE-325 URL: http://jira.codehaus.org/browse/SUREFIRE-325

[jira] Commented: (MCOMPILER-6) improve documentation

[ http://jira.codehaus.org/browse/MCOMPILER-6?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_95043 ] Ian Springer commented on MCOMPILER-6: -- Here's one more: * The docs for the source and target config props should state

[jira] Commented: (SUREFIRE-157) Surefire Plugin fails to handle exception thrown from TestNG @BeforeTest method

[ http://jira.codehaus.org/browse/SUREFIRE-157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_95992 ] Ian Springer commented on SUREFIRE-157: --- This issue also exists for methods annotated with @BeforeSuite. > Surefire

[jira] Commented: (MRESOURCES-29) An escape mechanism for property interpolation is missing.

[ http://jira.codehaus.org/browse/MRESOURCES-29?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_99314 ] Ian Springer commented on MRESOURCES-29: An way to escape $'s should certainly be provided. But further, as the or

[jira] Commented: (WAGON-54) Scm Wagon not expanding ${user.home}

[ http://jira.codehaus.org/browse/WAGON-54?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_100075 ] Ian Springer commented on WAGON-54: --- I'm seeing the same issue. Why has nobody responded to this case yet? It seems like a p

[jira] Commented: (MEAR-43) add ability to do filtering (i.e. template var replacement) for files in src/main/application/

[ http://jira.codehaus.org/browse/MEAR-43?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_116366 ] Ian Springer commented on MEAR-43: -- Here's an example: 1) In your pom, add: [...] src/main/resources

[jira] Created: (MAVENUPLOAD-1899) Oracle JDBC driver for JDK 1.4/1.5, v10.2.0.3.0

Oracle JDBC driver for JDK 1.4/1.5, v10.2.0.3.0 --- Key: MAVENUPLOAD-1899 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1899 Project: maven-upload-requests Issue Type: Wish Reporter:

[jira] Commented: (MAVENUPLOAD-1899) Oracle JDBC driver for JDK 1.4/1.5, v10.2.0.3.0

[ http://jira.codehaus.org/browse/MAVENUPLOAD-1899?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_120701 ] Ian Springer commented on MAVENUPLOAD-1899: --- Ah, I didn't notice that http://repo1.maven.org/maven2/com/orac

[jira] Commented: (MAVENUPLOAD-1899) Oracle JDBC driver for JDK 1.4/1.5, v10.2.0.3.0

[ http://jira.codehaus.org/browse/MAVENUPLOAD-1899?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_120725 ] Ian Springer commented on MAVENUPLOAD-1899: --- Thanks. Fyi, the md5/sha1 files are in the wrong format (they co

[jira] Created: (MDEP-135) add a 'failIfArtifactNotFound' boolean property to copy goal

add a 'failIfArtifactNotFound' boolean property to copy goal Key: MDEP-135 URL: http://jira.codehaus.org/browse/MDEP-135 Project: Maven 2.x Dependency Plugin Issue Type: New Featur

[jira] Created: (MIDEA-111) add support for generating web and ejb facets for IntelliJ 7.x iml files

add support for generating web and ejb facets for IntelliJ 7.x iml files Key: MIDEA-111 URL: http://jira.codehaus.org/browse/MIDEA-111 Project: Maven 2.x IDEA Plugin Is

[jira] Commented: (MNG-3078) artifact of packaging 'tar.gz' / dependency of type 'tar.gz downloaded, but not saved to local repository

[ http://jira.codehaus.org/browse/MNG-3078?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_122674 ] Ian Springer commented on MNG-3078: --- I'm seeing this same issue w/ Maven 2.0.8 and an artifact with type "tgz" (rather than

[jira] Commented: (MNG-3125) XML Schema for maven-metadata.xml

[ http://jira.codehaus.org/browse/MNG-3125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_122683 ] Ian Springer commented on MNG-3125: --- The attached schema doesn't include the "snapshot", "release", and "latest" elements, w

[jira] Created: (MCOMPILER-44) 'outputDirectory' configuration property should not be read-only

'outputDirectory' configuration property should not be read-only Key: MCOMPILER-44 URL: http://jira.codehaus.org/browse/MCOMPILER-44 Project: Maven 2.x Compiler Plugin Issue Ty

[jira] Commented: (MCOMPILER-44) 'outputDirectory' configuration property should not be read-only

[ http://jira.codehaus.org/browse/MCOMPILER-44?page=comments#action_77177 ] Ian Springer commented on MCOMPILER-44: --- Correction: The resources plugin allows the 'outputDirectory' prop to be modified, but the clean plugin does not. I will f

[jira] Created: (MCLEAN-19) 'outputDirectory' configuration property should not be read-only

'outputDirectory' configuration property should not be read-only Key: MCLEAN-19 URL: http://jira.codehaus.org/browse/MCLEAN-19 Project: Maven 2.x Clean Plugin Issue Type: Bug

[jira] Commented: (MCLEAN-19) 'outputDirectory' configuration property should not be read-only

[ http://jira.codehaus.org/browse/MCLEAN-19?page=comments#action_77178 ] Ian Springer commented on MCLEAN-19: Note, I have filed a similar issue for the compiler plugin - http://jira.codehaus.org/browse/MCOMPILER-44. > 'outputDirectory' con

[jira] Commented: (MCOMPILER-44) 'outputDirectory' configuration property should not be read-only

[ http://jira.codehaus.org/browse/MCOMPILER-44?page=comments#action_77179 ] Ian Springer commented on MCOMPILER-44: --- Note, I have filed a similar issue for the clean plugin - http://jira.codehaus.org/browse/MCLEAN-19. > 'outputDirectory' c

[jira] Created: (MNG-2598) profile element in POM should support overriding project.build.directory

profile element in POM should support overriding project.build.directory Key: MNG-2598 URL: http://jira.codehaus.org/browse/MNG-2598 Project: Maven 2 Issue Type: Improv

[jira] Commented: (MCOMPILER-44) 'outputDirectory' configuration property should not be read-only

[ http://jira.codehaus.org/browse/MCOMPILER-44?page=comments#action_77191 ] Ian Springer commented on MCOMPILER-44: --- Note, after some more thought, I think it makes sense for the 'outputDirectory' prop to remain read-only, to force all plug

[jira] Commented: (MCLEAN-19) 'outputDirectory' configuration property should not be read-only

[ http://jira.codehaus.org/browse/MCLEAN-19?page=comments#action_77192 ] Ian Springer commented on MCLEAN-19: Note, after some more thought, I think it makes sense for the 'outputDirectory' prop to remain read-only, to force all plugins to sh

[jira] Created: (MEAR-47) since resourcesDir property is deprecated anyway, please make it optional and do not attempt to copy resources from it if is not explicitly set

since resourcesDir property is deprecated anyway, please make it optional and do not attempt to copy resources from it if is not explicitly set ---

[jira] Commented: (MEAR-43) add ability to do filtering (i.e. template var replacement) for files in src/main/application/

[ http://jira.codehaus.org/browse/MEAR-43?page=comments#action_80513 ] Ian Springer commented on MEAR-43: -- No, I think that would work. > add ability to do filtering (i.e. template var replacement) for files in > src/main/application/ > -

[jira] Created: (MEAR-49) if an artifact in the list of ear modules already exists in the ear, the ear mojo will copy it on top of itself, zeroing out the file

if an artifact in the list of ear modules already exists in the ear, the ear mojo will copy it on top of itself, zeroing out the file - Key: MEAR-49

[jira] Reopened: (MEAR-47) since resourcesDir property is deprecated anyway, please make it optional and do not attempt to copy resources from it if is not explicitly set

[ http://jira.codehaus.org/browse/MEAR-47?page=all ] Ian Springer reopened MEAR-47: -- Oops. In the patch I submitted, when removing the default value for the resourceDir field, I accidentally removed the @parameter Javadoc tag altogether. Please m

[jira] Commented: (MEAR-49) if an artifact in the list of ear modules already exists in the ear, the ear mojo will copy it on top of itself, zeroing out the file

[ http://jira.codehaus.org/browse/MEAR-49?page=comments#action_80566 ] Ian Springer commented on MEAR-49: -- It happens when the "dev" profile I mentioned in an earlier issue is enabled. When dev mode is enabled, things get build directly to the t

[jira] Updated: (MEAR-49) if an artifact in the list of ear modules already exists in the ear, the ear mojo will copy it on top of itself, zeroing out the file

[ http://jira.codehaus.org/browse/MEAR-49?page=all ] Ian Springer updated MEAR-49: - Attachment: on-build-m2-plugin.zip > if an artifact in the list of ear modules already exists in the ear, the ear > mojo will copy it on top of itself, zeroing out the file

[jira] Commented: (MEAR-43) add ability to do filtering (i.e. template var replacement) for files in src/main/application/

[ http://jira.codehaus.org/browse/MEAR-43?page=comments#action_80839 ] Ian Springer commented on MEAR-43: -- How about just leveraging the resources settings from the build section of the POM like the jar plugin does? > add ability to do filteri

[jira] Commented: (MEAR-43) add ability to do filtering (i.e. template var replacement) for files in src/main/application/

[ http://jira.codehaus.org/browse/MEAR-43?page=comments#action_80840 ] Ian Springer commented on MEAR-43: -- Oops, I meant to say the resources plugin, not the jar plugin. > add ability to do filtering (i.e. template var replacement) for files in

[jira] Created: (MNG-2744) checksum comparison should be case-insensitive

checksum comparison should be case-insensitive -- Key: MNG-2744 URL: http://jira.codehaus.org/browse/MNG-2744 Project: Maven 2 Issue Type: Bug Components: Artifacts and Repositories A

[jira] Commented: (MNG-2694) property in plugin dependency's systemPath is not resolved and causes "system-scoped dependency must specify an absolute path systemPath."

[ http://jira.codehaus.org/browse/MNG-2694?page=comments#action_84205 ] Ian Springer commented on MNG-2694: --- The same problem exists for system dependencies defined in a non-plugin pom.xml. Would someone please provide a fix for this? It's pr

[jira] Created: (MEAR-58) ear plugin should only copy modules if they are newer than the destination file

ear plugin should only copy modules if they are newer than the destination file --- Key: MEAR-58 URL: http://jira.codehaus.org/browse/MEAR-58 Project: Maven 2.x Ear Plugin

[jira] Commented: (MEAR-58) ear plugin should only copy modules if they are newer than the destination file

[ http://jira.codehaus.org/browse/MEAR-58?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_86305 ] Ian Springer commented on MEAR-58: -- Yeah, they do have something. I didn't use it in my patch, because I wanted only print the

[jira] Created: (MWAR-45) add config prop to specify webapp classes should be zipped and placed into WEB-INF/lib/xxx.jar instead of placed in WEB-INF/classes/

add config prop to specify webapp classes should be zipped and placed into WEB-INF/lib/xxx.jar instead of placed in WEB-INF/classes/ - Key: MWAR-45