[jira] [Commented] (MENFORCER-270) option to forbid plugin snapshot versions only when releasing

[ https://issues.apache.org/jira/browse/MENFORCER-270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16038637#comment-16038637 ] Joerg Schaible commented on MENFORCER-270: -- You already have this. The release

[jira] [Commented] (MNG-6267) Support resolving "~" in values given to CLI Option "-s"

[ https://issues.apache.org/jira/browse/MNG-6267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16111347#comment-16111347 ] Joerg Schaible commented on MNG-6267: - ~ expansion is a functionality of bash. Adding su

[jira] [Commented] (MTOOLCHAINS-18) toolchain.xml file should support environment variables

[ https://issues.apache.org/jira/browse/MTOOLCHAINS-18?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16125995#comment-16125995 ] Joerg Schaible commented on MTOOLCHAINS-18: --- This is typical in Linux enviro

[jira] [Commented] (MNG-6284) inside should raise a warning

[ https://issues.apache.org/jira/browse/MNG-6284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16167442#comment-16167442 ] Joerg Schaible commented on MNG-6284: - It is absolutely fine to define even executions f

[jira] [Commented] (MNG-6284) inside should raise a warning

[ https://issues.apache.org/jira/browse/MNG-6284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16167501#comment-16167501 ] Joerg Schaible commented on MNG-6284: - It binds to the lifecycle when I declare the plug

[jira] [Updated] (MNG-6141) Dependency management overrides are not transitive and should be considered an anti-pattern.

[ https://issues.apache.org/jira/browse/MNG-6141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joerg Schaible updated MNG-6141: Attachment: MNG-6141-2.zip Extended example, where * parent inherits maven-parent and manages junit, *

[jira] [Updated] (MNG-6141) Dependency management overrides are not transitive and should be considered an anti-pattern.

[ https://issues.apache.org/jira/browse/MNG-6141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joerg Schaible updated MNG-6141: Attachment: (was: MNG-6141-2.zip) > Dependency management overrides are not transitive and should

[jira] [Updated] (MNG-6141) Dependency management overrides are not transitive and should be considered an anti-pattern.

[ https://issues.apache.org/jira/browse/MNG-6141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joerg Schaible updated MNG-6141: Attachment: MNG-6141-3.zip Updated example. Replaces MNG-6141-2.zip > Dependency management overrides

[jira] [Comment Edited] (MNG-6141) Dependency management overrides are not transitive and should be considered an anti-pattern.

[ https://issues.apache.org/jira/browse/MNG-6141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16216635#comment-16216635 ] Joerg Schaible edited comment on MNG-6141 at 10/24/17 10:08 AM: --

[jira] [Created] (MDEP-619) snapshotsOnly is not always respected

Joerg Schaible created MDEP-619: --- Summary: snapshotsOnly is not always respected Key: MDEP-619 URL: https://issues.apache.org/jira/browse/MDEP-619 Project: Maven Dependency Plugin Issue Type: B

[jira] [Commented] (MPIR-373) upgrade from 2.9 to 3.0.0 introduce additional warning issue

[ https://issues.apache.org/jira/browse/MPIR-373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16554117#comment-16554117 ] Joerg Schaible commented on MPIR-373: - Please, can we reopen this issue? It does not ma

[jira] [Commented] (MPIR-373) upgrade from 2.9 to 3.0.0 introduce additional warning issue

[ https://issues.apache.org/jira/browse/MPIR-373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16558059#comment-16558059 ] Joerg Schaible commented on MPIR-373: - Well, actually this issue is caused by Maven Cor

[jira] [Commented] (MPIR-373) upgrade from 2.9 to 3.0.0 introduce additional warning issue

[ https://issues.apache.org/jira/browse/MPIR-373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16559400#comment-16559400 ] Joerg Schaible commented on MPIR-373: - It would certainly help, if we simply add the me

[jira] [Commented] (MNG-6450) Allow importing a POM with a classifier

[ https://issues.apache.org/jira/browse/MNG-6450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16565150#comment-16565150 ] Joerg Schaible commented on MNG-6450: - I am not sure, if we can really overview the con

[jira] [Created] (MCHANGES-393) Default for teamlist is wrong

Joerg Schaible created MCHANGES-393: --- Summary: Default for teamlist is wrong Key: MCHANGES-393 URL: https://issues.apache.org/jira/browse/MCHANGES-393 Project: Maven Changes Plugin Issue Ty

[jira] [Commented] (MPIR-373) upgrade from 2.9 to 3.0.0 introduce additional warning issue

[ https://issues.apache.org/jira/browse/MPIR-373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16577884#comment-16577884 ] Joerg Schaible commented on MPIR-373: - Well, a simple line of warning is certainly a bi

[jira] [Commented] (MPIR-373) upgrade from 2.9 to 3.0.0 introduce additional warning issue

[ https://issues.apache.org/jira/browse/MPIR-373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16587134#comment-16587134 ] Joerg Schaible commented on MPIR-373: - Yes, according to the code it skips the license

[jira] [Commented] (MCOMPILER-279) Passing multiple --add-exports args to the compilerArgs is not supported

[ https://issues.apache.org/jira/browse/MCOMPILER-279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15534081#comment-15534081 ] Joerg Schaible commented on MCOMPILER-279: -- Maybe it is better to keep that ma

[jira] [Commented] (MNG-6000) activeProfiles in pom.xml

[ https://issues.apache.org/jira/browse/MNG-6000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15765549#comment-15765549 ] Joerg Schaible commented on MNG-6000: - This is already possible using file exists. > ac

[jira] [Commented] (MNG-6141) Dependency management overrides are not transitive and should be considered an anti-pattern.

[ https://issues.apache.org/jira/browse/MNG-6141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15786367#comment-15786367 ] Joerg Schaible commented on MNG-6141: - Sorry, but this is a perfectly legal situation! W

[jira] [Commented] (MNG-6141) Dependency management overrides are not transitive and should be considered an anti-pattern.

[ https://issues.apache.org/jira/browse/MNG-6141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15786501#comment-15786501 ] Joerg Schaible commented on MNG-6141: - No, they are not public. However, even the maven-

[jira] [Commented] (MNG-6141) Dependency management overrides are not transitive and should be considered an anti-pattern.

[ https://issues.apache.org/jira/browse/MNG-6141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15787514#comment-15787514 ] Joerg Schaible commented on MNG-6141: - I know, but if you set such defaults in a parent,

[jira] [Commented] (MNG-5567) Zip files are not included in classpaths at all

[ https://issues.apache.org/jira/browse/MNG-5567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15848143#comment-15848143 ] Joerg Schaible commented on MNG-5567: - Still I have major concerns to include this at al

[jira] [Commented] (MNG-5567) Zip files are not included in classpaths at all

[ https://issues.apache.org/jira/browse/MNG-5567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15848793#comment-15848793 ] Joerg Schaible commented on MNG-5567: - bq. First of all, how are ZIP files going to have

[jira] [Commented] (MNG-5567) Zip files are not included in classpaths at all

[ https://issues.apache.org/jira/browse/MNG-5567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15848811#comment-15848811 ] Joerg Schaible commented on MNG-5567: - For me those two issues are not related apart fro

[jira] [Commented] (MNG-5567) Zip files are not included in classpaths at all

[ https://issues.apache.org/jira/browse/MNG-5567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15849018#comment-15849018 ] Joerg Schaible commented on MNG-5567: - OK, that makes sense. However, it does not help f

[jira] [Commented] (MINSTALL-135) Copy and unpack dependency plugin not behaving when used simultaneously

[ https://issues.apache.org/jira/browse/MINSTALL-135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15901568#comment-15901568 ] Joerg Schaible commented on MINSTALL-135: - This issue has nothing to do with the

[jira] [Created] (MDEPLOY-247) Version 3.0.0-M1 breaks deploy using alt*DeploymentRepository with old syntax on Windows using

Joerg Schaible created MDEPLOY-247: -- Summary: Version 3.0.0-M1 breaks deploy using alt*DeploymentRepository with old syntax on Windows using Key: MDEPLOY-247 URL: https://issues.apache.org/jira/browse/MDEPLOY-247

[jira] [Updated] (MDEPLOY-247) Version 3.0.0-M1 breaks deploy using alt*DeploymentRepository with old syntax on Windows

[ https://issues.apache.org/jira/browse/MDEPLOY-247?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joerg Schaible updated MDEPLOY-247: --- Summary: Version 3.0.0-M1 breaks deploy using alt*DeploymentRepository with old syntax on Wi

[jira] [Commented] (MNG-6596) maven should not make assumptions on the location of the parent pom

[ https://issues.apache.org/jira/browse/MNG-6596?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16773919#comment-16773919 ] Joerg Schaible commented on MNG-6596: - I simply assume that Pieter does not know, that

[jira] [Commented] (MNG-6658) Maven 3.6.1 breaks build when using custom source folder

[ https://issues.apache.org/jira/browse/MNG-6658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16845199#comment-16845199 ] Joerg Schaible commented on MNG-6658: - The question is if it is caused by the weird lay

[jira] [Commented] (MASSEMBLY-752) [PATCH] Option to ignore empty directories in fileSet directory

[ https://issues.apache.org/jira/browse/MASSEMBLY-752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17364791#comment-17364791 ] Joerg Schaible commented on MASSEMBLY-752: -- Is there any reason, why this pat

[jira] [Comment Edited] (MASSEMBLY-752) [PATCH] Option to ignore empty directories in fileSet directory

[ https://issues.apache.org/jira/browse/MASSEMBLY-752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17364791#comment-17364791 ] Joerg Schaible edited comment on MASSEMBLY-752 at 6/17/21, 8:41 AM:

[jira] [Commented] (MNG-5846) Maven 3.3.3 ignores repository definition for "central"

[ https://issues.apache.org/jira/browse/MNG-5846?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14599688#comment-14599688 ] Joerg Schaible commented on MNG-5846: - It's not! If your settings.xml defines a mirror f

[jira] [Commented] (MNG-5846) Maven 3.3.3 ignores repository definition for "central"

[ https://issues.apache.org/jira/browse/MNG-5846?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14599816#comment-14599816 ] Joerg Schaible commented on MNG-5846: - The example demonstrates simply, how Maven works

[jira] [Comment Edited] (MNG-5862) POM XML parser needs XInclude and/or XML Entity support

[ https://issues.apache.org/jira/browse/MNG-5862?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14636857#comment-14636857 ] Joerg Schaible edited comment on MNG-5862 at 7/22/15 12:42 PM: ---

[jira] [Comment Edited] (MNG-5862) POM XML parser needs XInclude and/or XML Entity support

[ https://issues.apache.org/jira/browse/MNG-5862?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14636857#comment-14636857 ] Joerg Schaible edited comment on MNG-5862 at 7/22/15 12:41 PM: ---

[jira] [Commented] (MNG-5862) POM XML parser needs XInclude and/or XML Entity support

[ https://issues.apache.org/jira/browse/MNG-5862?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14636857#comment-14636857 ] Joerg Schaible commented on MNG-5862: - Maven 1 hat XInclude and entity support and it wa

[jira] [Commented] (MSHADE-204) Multiple JDBC drivers not supported

[ https://issues.apache.org/jira/browse/MSHADE-204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14728133#comment-14728133 ] Joerg Schaible commented on MSHADE-204: --- You have to set the ServicesResourceTransfo

[jira] [Commented] (MNG-5727) unexpected InvalidArtifactRTException from ProjectBuilder#build

[ https://issues.apache.org/jira/browse/MNG-5727?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14948609#comment-14948609 ] Joerg Schaible commented on MNG-5727: - Or this overriding the scope in a "later" depende

[jira] [Commented] (MNG-5939) Problem doing release when sources are generate as well

[ https://issues.apache.org/jira/browse/MNG-5939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15028424#comment-15028424 ] Joerg Schaible commented on MNG-5939: - Typically this has nothing to do with Maven, but

[jira] [Commented] (MNG-5939) Problem doing release when sources are generate as well

[ https://issues.apache.org/jira/browse/MNG-5939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15028777#comment-15028777 ] Joerg Schaible commented on MNG-5939: - You have configured the sources plugin to run two

[jira] Commented: (MJARSIGNER-12) It should be possible to save the keystore in one location for multi module projects

[ http://jira.codehaus.org/browse/MJARSIGNER-12?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=264672#action_264672 ] Joerg Schaible commented on MJARSIGNER-12: -- We do this and use the dependency plugin to c

[jira] Commented: (MEAR-138) Ear plugin doesn't attach jars with timestamp

[ http://jira.codehaus.org/browse/MEAR-138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=265206#action_265206 ] Joerg Schaible commented on MEAR-138: - You may configure the ejb-plugin instead to use non-unique v

[jira] Commented: (MEAR-138) Ear plugin doesn't attach jars with timestamp

[ http://jira.codehaus.org/browse/MEAR-138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=265301#action_265301 ] Joerg Schaible commented on MEAR-138: - The only problem with my solution is, that it does not work

[jira] Commented: (MPIR-220) IOException: Failed to open file During Site generation

[ http://jira.codehaus.org/browse/MPIR-220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=265506#action_265506 ] Joerg Schaible commented on MPIR-220: - Simply take the two dependencies from MPIR-222, they are ava

[jira] Commented: (MDEP-231) Create a single dependency resolution plugin

[ https://jira.codehaus.org/browse/MDEP-231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=272459#comment-272459 ] Joerg Schaible commented on MDEP-231: - What's the difference to existing "get" goal? > Create a

[jira] Commented: (MNG-5127) CLONE - Maven profile activation does not work when profile is defined in inherited 'parent' pom

[ https://jira.codehaus.org/browse/MNG-5127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=272497#comment-272497 ] Joerg Schaible commented on MNG-5127: - It's closed, because it behaves as designed. Profiles are

[jira] Commented: (MNG-5127) CLONE - Maven profile activation does not work when profile is defined in inherited 'parent' pom

[ https://jira.codehaus.org/browse/MNG-5127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=272567#comment-272567 ] Joerg Schaible commented on MNG-5127: - Just in case you mean "activeByDefault": It's active *unle

[jira] Commented: (MRELEASE-699) release:update-versions should support -DreleaseVersion too (not only -DdevelopmentVersion), so it also supports not suffixing the version with -SNAPSHOT

[ https://jira.codehaus.org/browse/MRELEASE-699?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=274961#comment-274961 ] Joerg Schaible commented on MRELEASE-699: - The more interesting question is: Why do you w

[jira] Commented: (MWAR-260) Patch to provide new war-overlay type

[ https://jira.codehaus.org/browse/MWAR-260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=279045#comment-279045 ] Joerg Schaible commented on MWAR-260: - Why do you need a new packaging type? We do this since yea

[jira] Commented: (MWAR-260) Patch to provide new war-overlay type

[ https://jira.codehaus.org/browse/MWAR-260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=279052#comment-279052 ] Joerg Schaible commented on MWAR-260: - bq. Does it need to declare two dependencies for each over

[jira] Commented: (MWAR-260) Patch to provide new war-overlay type

[ https://jira.codehaus.org/browse/MWAR-260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=279112#comment-279112 ] Joerg Schaible commented on MWAR-260: - OK, it seems you have a slightly different model in mind.

[jira] Commented: (MWAR-260) Patch to provide new war-overlay type

[ https://jira.codehaus.org/browse/MWAR-260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=279168#comment-279168 ] Joerg Schaible commented on MWAR-260: - Hi Alex, bq. You would expect the following: Exaclty. bq

[jira] Commented: (MJAVADOC-325) Incorrect -link is generated for 1.5

[ https://jira.codehaus.org/browse/MJAVADOC-325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=279899#comment-279899 ] Joerg Schaible commented on MJAVADOC-325: - Oracle uses dots for the official links to the

[jira] Commented: (MEAR-143) Plugin does not respect transitive dependency scopes properly

[ https://jira.codehaus.org/browse/MEAR-143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=280127#comment-280127 ] Joerg Schaible commented on MEAR-143: - This works for us since years and I am sure we're not alon

[jira] Commented: (MEAR-143) Plugin does not respect transitive dependency scopes properly

[ https://jira.codehaus.org/browse/MEAR-143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=280177#comment-280177 ] Joerg Schaible commented on MEAR-143: - This is exactly how dependencyManagement works! http://mav

[jira] Commented: (MNG-1977) Global dependency exclusions

[ https://jira.codehaus.org/browse/MNG-1977?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=281586#comment-281586 ] Joerg Schaible commented on MNG-1977: - bq. compile -> compile = runtime bq. This would make many

[jira] Commented: (MWAR-81) Request enhancement to pattern matching for packagingIncludes/packagingExcludes functionality (regular expressions?)

[ https://jira.codehaus.org/browse/MWAR-81?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=282176#comment-282176 ] Joerg Schaible commented on MWAR-81: Have a look at: http://maven.apache.org/plugins/maven-assembl

[jira] Commented: (MWAR-81) Request enhancement to pattern matching for packagingIncludes/packagingExcludes functionality (regular expressions?)

[ https://jira.codehaus.org/browse/MWAR-81?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=28#comment-28 ] Joerg Schaible commented on MWAR-81: This is what I mean: You don't have to patch anything, it alr

[jira] Issue Comment Edited: (MWAR-81) Request enhancement to pattern matching for packagingIncludes/packagingExcludes functionality (regular expressions?)

[ https://jira.codehaus.org/browse/MWAR-81?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=28#comment-28 ] Joerg Schaible edited comment on MWAR-81 at 10/27/11 9:06 AM: -- This is wh

[jira] Commented: (MNG-2903) Snapshots are being packaged with datestamps in their filename instead of "SNAPSHOT",

[ https://jira.codehaus.org/browse/MNG-2903?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=284060#comment-284060 ] Joerg Schaible commented on MNG-2903: - The difference is based on the fact, how the snapshot arti

[jira] Created: (MNG-5207) [Regression] Maven 3 fails to calculate proper build order

[Regression] Maven 3 fails to calculate proper build order -- Key: MNG-5207 URL: https://jira.codehaus.org/browse/MNG-5207 Project: Maven 2 & 3 Issue Type: Bug Components: Rea

[jira] Updated: (MNG-5207) [Regression] Maven 3 fails to calculate proper build order

[ https://jira.codehaus.org/browse/MNG-5207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joerg Schaible updated MNG-5207: Attachment: MNG-5207.tgz Attachment contains demo project. First run script _prepare.sh_ in directory _pr

[jira] Commented: (MNG-2363) does not work in a multi-project build

[ https://jira.codehaus.org/browse/MNG-2363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=285046#comment-285046 ] Joerg Schaible commented on MNG-2363: - Works for inherited profiles in Maven 3 only. > does not

[jira] (MWAR-267) Maven WAR plugin does not copy dependencies of type "bundle" into WEB-INF/lib

[ https://jira.codehaus.org/browse/MWAR-267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=289244#comment-289244 ] Joerg Schaible commented on MWAR-267: - Actually this complete list of types is nonsense! Every Ma

[jira] (MWAR-257) dependentWarExcludes is deprecated but

[ https://jira.codehaus.org/browse/MWAR-257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=289245#comment-289245 ] Joerg Schaible commented on MWAR-257: - The deprecation should be simply reverted. Even the plugin

[jira] (MNG-5235) Profiles not activated according to property values

[ https://jira.codehaus.org/browse/MNG-5235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=290303#comment-290303 ] Joerg Schaible commented on MNG-5235: - This is by design. Properties are explicitly not mentioned

[jira] (MSITE-604) Properties from settings.xml are not recognized in site distribution management

[ https://jira.codehaus.org/browse/MSITE-604?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joerg Schaible updated MSITE-604: - Attachment: MSITE-604.tgz We face the same problems. In our case we deploy the site documentation to ou

[jira] (MSITE-604) Properties from settings.xml are not recognized in site distribution management

[ https://jira.codehaus.org/browse/MSITE-604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=290463#comment-290463 ] Joerg Schaible edited comment on MSITE-604 at 2/1/12 5:23 AM: -- We face

[jira] (MSITE-604) Properties from settings.xml are not recognized in site distribution management

[ https://jira.codehaus.org/browse/MSITE-604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=290463#comment-290463 ] Joerg Schaible edited comment on MSITE-604 at 2/1/12 5:23 AM: -- We face

[jira] (MNG-5237) Cannot download maven dependencies through proxy

[ https://jira.codehaus.org/browse/MNG-5237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=290696#comment-290696 ] Joerg Schaible commented on MNG-5237: - Take a closer look at the URLs. Maven central has been mov

[jira] (MRELEASE-735) Profile activation working unpredictably

[ https://jira.codehaus.org/browse/MRELEASE-735?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=290995#comment-290995 ] Joerg Schaible commented on MRELEASE-735: - You should definitely also document the Maven

[jira] (MDEP-346) maven-dependency-plugin violates artifact dependencies, causing unstable incremental builds

[ https://jira.codehaus.org/browse/MDEP-346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=293149#comment-293149 ] Joerg Schaible commented on MDEP-346: - It's easy: Use copy-dependencies (resp. unpack-dependencie

[jira] (MDEP-346) maven-dependency-plugin violates artifact dependencies, causing unstable incremental builds

[ https://jira.codehaus.org/browse/MDEP-346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=293154#comment-293154 ] Joerg Schaible commented on MDEP-346: - But this *is* the whole point: With copy/unpack you don't

[jira] (MNG-5178) Substitute environment variable M2_HOME by M3_HOME

[ https://jira.codehaus.org/browse/MNG-5178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=293671#comment-293671 ] Joerg Schaible commented on MNG-5178: - And why do you set the env variable at all?

[jira] (MRELEASE-749) release:prepare copies contents of source of Subversion branch into release tag

[ https://jira.codehaus.org/browse/MRELEASE-749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=294081#comment-294081 ] Joerg Schaible commented on MRELEASE-749: - ?? This is exactly how it should work. A rele

[jira] (MRELEASE-749) release:prepare copies contents of source of Subversion branch into release tag

[ https://jira.codehaus.org/browse/MRELEASE-749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=294090#comment-294090 ] Joerg Schaible commented on MRELEASE-749: - How did you create the branch? When you do thi

[jira] Commented: (MRELEASE-594) release:prepare should stop when there is snapshots in dependencies management

[ http://jira.codehaus.org/browse/MRELEASE-594?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=234744#action_234744 ] Joerg Schaible commented on MRELEASE-594: - Such a functionality must be activated via confi

[jira] Commented: (MRELEASE-594) release:prepare should stop when there is snapshots in dependencies management

[ http://jira.codehaus.org/browse/MRELEASE-594?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=234770#action_234770 ] Joerg Schaible commented on MRELEASE-594: - @Thomas: Yes, it has to. The parent is an artifa

[jira] Created: (MNG-4834) Site descriptor of parent is no longer found in local repository

Site descriptor of parent is no longer found in local repository Key: MNG-4834 URL: http://jira.codehaus.org/browse/MNG-4834 Project: Maven 2 & 3 Issue Type: Bug Affects Ve

[jira] Updated: (MNG-4834) Site descriptor of parent is no longer found in local repository

[ http://jira.codehaus.org/browse/MNG-4834?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joerg Schaible updated MNG-4834: Attachment: MNG-4834-remote-repo.tgz The remote repository with the parent pom. Referenced in the settings

[jira] Updated: (MNG-4834) Site descriptor of parent is no longer found in local repository

[ http://jira.codehaus.org/browse/MNG-4834?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joerg Schaible updated MNG-4834: Attachment: MNG-4834.tgz Archive with the projects for the parent pom and the main artifact. Calling {nofo

[jira] Reopened: (MNG-4834) Site descriptor of parent is no longer found in local repository

[ http://jira.codehaus.org/browse/MNG-4834?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joerg Schaible reopened MNG-4834: - No, you may not install the parent pom locally. Then it's always found. Therefore I've provided the "remote"

[jira] Commented: (MNG-4834) [regression] MavenProject.getParent() ignores configured repositories

[ http://jira.codehaus.org/browse/MNG-4834?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=236459#action_236459 ] Joerg Schaible commented on MNG-4834: - OK, thanks for looking into it. > [regression] MavenProject

[jira] Commented: (MEV-667) plexus-utils-1.0.4.pom contains no valid XML

[ http://jira.codehaus.org/browse/MEV-667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=240301#action_240301 ] Joerg Schaible commented on MEV-667: It's a simple replace "s/ø/o/" in Tryvge's last name. > plexus

[jira] Commented: (MNG-2172) 's are not used when evaluating

[ http://jira.codehaus.org/browse/MNG-2172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=241977#action_241977 ] Joerg Schaible commented on MNG-2172: - You silently imply that dependency management is only applie

[jira] Commented: (MNG-4885) Why incremental build is not supported natively by Maven?

[ http://jira.codehaus.org/browse/MNG-4885?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=243119#action_243119 ] Joerg Schaible commented on MNG-4885: - It is more a problem of the plugins and the concept of plugi

[jira] Commented: (MDEP-251) Artifacts qualifier are NOT taken into accounts correctly

[ http://jira.codehaus.org/browse/MDEP-251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=243724#action_243724 ] Joerg Schaible commented on MDEP-251: - @Andreas Brieg: Maven is absolute correct. Different classif

[jira] Commented: (MPIR-212) src/main/java does not exist for non-jar project

[ http://jira.codehaus.org/browse/MPIR-212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=247665#action_247665 ] Joerg Schaible commented on MPIR-212: - Same here for a cutsom plugin with an own packaging type (sp

[jira] Commented: (MJAVADOC-279) Javadoc plugin doesn't set dependencies correctly when pom uses classifiers

[ http://jira.codehaus.org/browse/MJAVADOC-279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=251054#action_251054 ] Joerg Schaible commented on MJAVADOC-279: - And it happens for M2 only (at least using site

[jira] Commented: (MARCHETYPES-37) The POM of generated projects should have xml prolog/header specifying encoding

[ http://jira.codehaus.org/browse/MARCHETYPES-37?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=251601#action_251601 ] Joerg Schaible commented on MARCHETYPES-37: --- The XML spec defines UTF-8 if the header i

[jira] Created: (MPIR-222) Error reported for ZipException caused by dependency of type pom

Error reported for ZipException caused by dependency of type pom Key: MPIR-222 URL: http://jira.codehaus.org/browse/MPIR-222 Project: Maven 2.x Project Info Reports Plugin Issu

[jira] Commented: (MPH-79) help:active-profiles does not list active inherited profiles

[ http://jira.codehaus.org/browse/MPH-79?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=261234#action_261234 ] Joerg Schaible commented on MPH-79: --- It is required to document the fact that the activation of the pro

[jira] Commented: (MSHARED-191) Specification-Version must not contain "-SNAPSHOT"

[ http://jira.codehaus.org/browse/MSHARED-191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=261787#action_261787 ] Joerg Schaible commented on MSHARED-191: At least there is a workaround: http://article.gma

[jira] Commented: (MSITE-579) SCM URLs Incorrect for Multi-Module Build Where Module Name != artifactId

[ http://jira.codehaus.org/browse/MSITE-579?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=263033#action_263033 ] Joerg Schaible commented on MSITE-579: -- @James, it has a long history (MNG-3244 and linked ones).

[jira] [Commented] (MNG-5227) The 'optional' flag of a dependency should be manageable.

[ https://issues.apache.org/jira/browse/MNG-5227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15130835#comment-15130835 ] Joerg Schaible commented on MNG-5227: - I just reported MNG-1577, the patch was provided

[jira] [Commented] (MNG-5227) The 'optional' flag of a dependency should be manageable.

[ https://issues.apache.org/jira/browse/MNG-5227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15130839#comment-15130839 ] Joerg Schaible commented on MNG-5227: - Oh, well. And managing the scope is *essential*.

[jira] [Commented] (MNG-5227) The 'optional' flag of a dependency should be manageable.

[ https://issues.apache.org/jira/browse/MNG-5227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15130852#comment-15130852 ] Joerg Schaible commented on MNG-5227: - If your fix means that the dependencyManagement c

[jira] [Commented] (MNG-5227) The 'optional' flag of a dependency should be manageable.

[ https://issues.apache.org/jira/browse/MNG-5227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15130858#comment-15130858 ] Joerg Schaible commented on MNG-5227: - However, there's no need to drop the scope now. I

  1   2   3   4   5   >