[jira] (MJAVADOC-355) Encoding problem if platform encoding used to run Maven is different from default platform encoding.
Christian Schulte created MJAVADOC-355: -- Summary: Encoding problem if platform encoding used to run Maven is different from default platform encoding. Key: MJAVADOC-355 URL: https://jira.codehaus.org/browse/MJAVADOC-355 Project: Maven 2.x Javadoc Plugin Issue Type: Wish Affects Versions: 2.9 Reporter: Christian Schulte Priority: Trivial When setting up a platform encoding in MAVEN_OPTS (e.g. '-Dfile.encoding=UTF-8'), the plugin writes command line argument files using that encoding. This encoding is not preserved when executing Javadoc which then reads these command line files using the real platform encoding. The platform encoding Maven is running with needs to be preserved in Javadoc. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MJAVADOC-355) Encoding problem if platform encoding used to run Maven is different from default platform encoding.
[ https://jira.codehaus.org/browse/MJAVADOC-355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Schulte updated MJAVADOC-355: --- Attachment: MJAVADOC-355.patch Patch passing the platform encoding to Javadoc. > Encoding problem if platform encoding used to run Maven is different from > default platform encoding. > - > > Key: MJAVADOC-355 > URL: https://jira.codehaus.org/browse/MJAVADOC-355 > Project: Maven 2.x Javadoc Plugin > Issue Type: Wish >Affects Versions: 2.9 >Reporter: Christian Schulte >Priority: Trivial > Attachments: MJAVADOC-355.patch > > > When setting up a platform encoding in MAVEN_OPTS (e.g. > '-Dfile.encoding=UTF-8'), the plugin writes command line argument files using > that encoding. This encoding is not preserved when executing Javadoc which > then reads these command line files using the real platform encoding. The > platform encoding Maven is running with needs to be preserved in Javadoc. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MECLIPSE-734) improve the attribute
Michael Isvy created MECLIPSE-734:
-
Summary: improve the attribute
Key: MECLIPSE-734
URL: https://jira.codehaus.org/browse/MECLIPSE-734
Project: Maven 2.x Eclipse Plugin
Issue Type: Improvement
Components: Core : .project
Reporter: Michael Isvy
Hi,
in .project file, project natures are declared as follows:
{code}
org.eclipse.jdt.core.javanature
org.eclipse.wst.common.project.facet.core.nature
org.eclipse.wst.common.modulecore.ModuleCoreNature
org.eclipse.jem.workbench.JavaEMFNature
org.springframework.ide.eclipse.core.springnature
{code}
Inside my POM file, when configuring maven-eclipse-plugin, I can use the
attribute as follows:
{code}
org.springframework.ide.eclipse.core.springnature
{code}
It works well, but it always adds the item at the end of all
elements. It would be nice to provide the possibility to insert this project
nature at the beginning. For instance, we could add an insert attribute like
this:
{code}
{code}
or a subtag:
{code}
...
{code}
Having the additional nature at first is only way to work with some of the
Eclipse decorators (see this issue for instance:
https://issuetracker.springsource.com/browse/STS-2938 )
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MWAR-294) Unwanted transitive dependencies added to the WAR with dependency management and Maven 3.
Marc Rohlfs created MWAR-294:
Summary: Unwanted transitive dependencies added to the WAR with
dependency management and Maven 3.
Key: MWAR-294
URL: https://jira.codehaus.org/browse/MWAR-294
Project: Maven 2.x WAR Plugin
Issue Type: Bug
Affects Versions: 2.3, 2.1.1
Environment: Apache Maven 3.0.4 (r1232337; 2012-01-17 09:44:56+0100)
Maven home: /opt/apache-maven-3.0.4
Java version: 1.6.0_26, vendor: Sun Microsystems Inc.
Java home: /usr/lib/jvm/java-6-sun-1.6.0.26/jre
Default locale: en_GB, platform encoding: UTF-8
OS name: "linux", version: "2.6.32-43-generic", arch: "i386", family: "unix"
Reporter: Marc Rohlfs
With Maven 3, unwanted libraries are added to the _WEB-INF/lib_ folder of the
packed web app in a multi-module build if:
* The WAR module has a JAR dependency with {{provided}} scope.
* The POM of the WAR module (or its parent POM) has a {{dependencyManagement}}
section that defines the transitive dependencies of the JAR module.
* The dependencies in the {{dependencyManagement}} section are *not* defined as
dependencies of the WAR module.
* The dependencies in the {{dependencyManagement}} section explicitly define
{{compile}} or {{runtime}} scope.
This leads to unwanted dependencies in the packaged web app or even duplicate
dependencies when using overlays.
When running the build with _Maven 2.2.1_, it works fine and doesn't add those
unwanted dependencies to the web app.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MWAR-294) Unwanted transitive dependencies added to the WAR with dependency management and Maven 3.
[
https://jira.codehaus.org/browse/MWAR-294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marc Rohlfs updated MWAR-294:
-
Attachment: MWAR-294.zip
> Unwanted transitive dependencies added to the WAR with dependency management
> and Maven 3.
> -
>
> Key: MWAR-294
> URL: https://jira.codehaus.org/browse/MWAR-294
> Project: Maven 2.x WAR Plugin
> Issue Type: Bug
>Affects Versions: 2.1.1, 2.3
> Environment: Apache Maven 3.0.4 (r1232337; 2012-01-17 09:44:56+0100)
> Maven home: /opt/apache-maven-3.0.4
> Java version: 1.6.0_26, vendor: Sun Microsystems Inc.
> Java home: /usr/lib/jvm/java-6-sun-1.6.0.26/jre
> Default locale: en_GB, platform encoding: UTF-8
> OS name: "linux", version: "2.6.32-43-generic", arch: "i386", family: "unix"
>Reporter: Marc Rohlfs
> Attachments: MWAR-294.zip
>
>
> With Maven 3, unwanted libraries are added to the _WEB-INF/lib_ folder of the
> packed web app in a multi-module build if:
> * The WAR module has a JAR dependency with {{provided}} scope.
> * The POM of the WAR module (or its parent POM) has a
> {{dependencyManagement}} section that defines the transitive dependencies of
> the JAR module.
> * The dependencies in the {{dependencyManagement}} section are *not* defined
> as dependencies of the WAR module.
> * The dependencies in the {{dependencyManagement}} section explicitly define
> {{compile}} or {{runtime}} scope.
> This leads to unwanted dependencies in the packaged web app or even duplicate
> dependencies when using overlays.
> When running the build with _Maven 2.2.1_, it works fine and doesn't add
> those unwanted dependencies to the web app.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (DOXIASITETOOLS-76) Missing inheritance of 'googleAdSenseClient', 'googleAdSenseSlot' and 'googleAnalyticsAccountId' elements.
Christian Schulte created DOXIASITETOOLS-76: --- Summary: Missing inheritance of 'googleAdSenseClient', 'googleAdSenseSlot' and 'googleAnalyticsAccountId' elements. Key: DOXIASITETOOLS-76 URL: https://jira.codehaus.org/browse/DOXIASITETOOLS-76 Project: Maven Doxia Sitetools Issue Type: Bug Components: Decoration model Affects Versions: 1.3 Reporter: Christian Schulte -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (DOXIASITETOOLS-76) Missing inheritance of 'googleAdSenseClient', 'googleAdSenseSlot' and 'googleAnalyticsAccountId' elements.
[ https://jira.codehaus.org/browse/DOXIASITETOOLS-76?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Schulte updated DOXIASITETOOLS-76: Attachment: DOXIASITETOOLS-76.patch Patch adding inheritance of the elements. > Missing inheritance of 'googleAdSenseClient', 'googleAdSenseSlot' and > 'googleAnalyticsAccountId' elements. > -- > > Key: DOXIASITETOOLS-76 > URL: https://jira.codehaus.org/browse/DOXIASITETOOLS-76 > Project: Maven Doxia Sitetools > Issue Type: Bug > Components: Decoration model >Affects Versions: 1.3 >Reporter: Christian Schulte > Attachments: DOXIASITETOOLS-76.patch > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MNG-5355) Case sensitivity changes in class names not detected by compiler
Ruben Jenster created MNG-5355: -- Summary: Case sensitivity changes in class names not detected by compiler Key: MNG-5355 URL: https://jira.codehaus.org/browse/MNG-5355 Project: Maven 2 & 3 Issue Type: Bug Affects Versions: 3.0.3 Environment: Apache Maven 3.0.3 (r1075438; 2011-02-28 18:31:09+0100) Maven home: /usr/share/maven Java version: 1.6.0_35, vendor: Apple Inc. Java home: /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home Default locale: en_US, platform encoding: MacRoman OS name: "mac os x", version: "10.7.5", arch: "x86_64", family: "mac" Reporter: Ruben Jenster Priority: Minor Attachments: compile.log The compiler doesn't detect case sensitivity changes in class names. The renamed class is not compiled. 1. Create a class named FooBAR 2. execute 'mvn compile' 3. Rename FooBAR to FooBar 4. execute 'mvn compile' 5. target/classes/FooBar.class does not exist Is this expected behaviour? Is a clean always required here? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MRRESOURCES-64) Mojo: process uses deprecated expression project.build.resources
[
https://jira.codehaus.org/browse/MRRESOURCES-64?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dennis Lundberg updated MRRESOURCES-64:
---
Description:
Updating from 1.2.1 to 1.3 causes Maven builds to report the following:
{noformat}
[WARNING] The parameter expression: 'project.build.resources' used in mojo:
'process' has been deprecated. Use 'project.resources' instead.
{noformat}
Looks like this was a side-effect of the fix for MRRESOURCES-57, see:
http://svn.apache.org/viewvc/maven/plugins/trunk/maven-remote-resources-plugin/src/main/java/org/apache/maven/plugin/resources/remote/ProcessRemoteResourcesMojo.java?r1=1057005&r2=1165423
The offending change seems to be:
{noformat}
@@ -313,7 +313,7 @@
/**
* The list of resources defined for the project.
*
- * @parameter expression="${project.resources}"
+ * @parameter default-value="${project.build.resources}"
* @readonly
* @required
{noformat}
was:
Updating from 1.2.1 to 1.3 causes Maven builds to report the following:
[WARNING] The parameter expression: 'project.build.resources' used in mojo:
'process' has been deprecated. Use 'project.resources' instead.
Looks like this was a side-effect of the fix for MRRESOURCES-57, see:
http://svn.apache.org/viewvc/maven/plugins/trunk/maven-remote-resources-plugin/src/main/java/org/apache/maven/plugin/resources/remote/ProcessRemoteResourcesMojo.java?r1=1057005&r2=1165423
The offending change seems to be:
@@ -313,7 +313,7 @@
/**
* The list of resources defined for the project.
*
- * @parameter expression="${project.resources}"
+ * @parameter default-value="${project.build.resources}"
* @readonly
* @required
> Mojo: process uses deprecated expression project.build.resources
>
>
> Key: MRRESOURCES-64
> URL: https://jira.codehaus.org/browse/MRRESOURCES-64
> Project: Maven 2.x Remote Resources Plugin
> Issue Type: Bug
>Reporter: SebbASF
>
> Updating from 1.2.1 to 1.3 causes Maven builds to report the following:
> {noformat}
> [WARNING] The parameter expression: 'project.build.resources' used in mojo:
> 'process' has been deprecated. Use 'project.resources' instead.
> {noformat}
> Looks like this was a side-effect of the fix for MRRESOURCES-57, see:
> http://svn.apache.org/viewvc/maven/plugins/trunk/maven-remote-resources-plugin/src/main/java/org/apache/maven/plugin/resources/remote/ProcessRemoteResourcesMojo.java?r1=1057005&r2=1165423
> The offending change seems to be:
> {noformat}
> @@ -313,7 +313,7 @@
> /**
> * The list of resources defined for the project.
> *
> - * @parameter expression="${project.resources}"
> + * @parameter default-value="${project.build.resources}"
> * @readonly
> * @required
> {noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MCOMPILER-182) Case sensitivity changes in class names not detected by compiler
[ https://jira.codehaus.org/browse/MCOMPILER-182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte moved MNG-5355 to MCOMPILER-182: --- Complexity: (was: Intermediate) Affects Version/s: (was: 3.0.3) 2.3.2 Key: MCOMPILER-182 (was: MNG-5355) Project: Maven 2.x Compiler Plugin (was: Maven 2 & 3) > Case sensitivity changes in class names not detected by compiler > > > Key: MCOMPILER-182 > URL: https://jira.codehaus.org/browse/MCOMPILER-182 > Project: Maven 2.x Compiler Plugin > Issue Type: Bug >Affects Versions: 2.3.2 > Environment: Apache Maven 3.0.3 (r1075438; 2011-02-28 18:31:09+0100) > Maven home: /usr/share/maven > Java version: 1.6.0_35, vendor: Apple Inc. > Java home: /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home > Default locale: en_US, platform encoding: MacRoman > OS name: "mac os x", version: "10.7.5", arch: "x86_64", family: "mac" >Reporter: Ruben Jenster >Priority: Minor > Attachments: compile.log > > > The compiler doesn't detect case sensitivity changes in class names. > The renamed class is not compiled. > 1. Create a class named FooBAR > 2. execute 'mvn compile' > 3. Rename FooBAR to FooBar > 4. execute 'mvn compile' > 5. target/classes/FooBar.class does not exist > Is this expected behaviour? Is a clean always required here? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MCOMPILER-182) Case sensitivity changes in class names not detected by compiler
[ https://jira.codehaus.org/browse/MCOMPILER-182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte closed MCOMPILER-182. Resolution: Fixed Fix Version/s: 2.6 Assignee: Robert Scholte Fixed as part of MCOMPILER-21. I've added an IT in [r1393086|http://svn.apache.org/viewvc?rev=1393086&view=rev] to be sure this won't happen again. We're working on more solid compilations, this is a very nice usecase to verify our improvements. Thanks. > Case sensitivity changes in class names not detected by compiler > > > Key: MCOMPILER-182 > URL: https://jira.codehaus.org/browse/MCOMPILER-182 > Project: Maven 2.x Compiler Plugin > Issue Type: Bug >Affects Versions: 2.3.2 > Environment: Apache Maven 3.0.3 (r1075438; 2011-02-28 18:31:09+0100) > Maven home: /usr/share/maven > Java version: 1.6.0_35, vendor: Apple Inc. > Java home: /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home > Default locale: en_US, platform encoding: MacRoman > OS name: "mac os x", version: "10.7.5", arch: "x86_64", family: "mac" >Reporter: Ruben Jenster >Assignee: Robert Scholte >Priority: Minor > Fix For: 2.6 > > Attachments: compile.log > > > The compiler doesn't detect case sensitivity changes in class names. > The renamed class is not compiled. > 1. Create a class named FooBAR > 2. execute 'mvn compile' > 3. Rename FooBAR to FooBar > 4. execute 'mvn compile' > 5. target/classes/FooBar.class does not exist > Is this expected behaviour? Is a clean always required here? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MSHARED-141) MavenCommandLineBuilder incorrectly adds system properties
[
https://jira.codehaus.org/browse/MSHARED-141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=310171#comment-310171
]
Robert Scholte commented on MSHARED-141:
I'm not sure if this will always work. For instance: IIUC there's a difference
of quoting arguments between Windows and Linux.
For Windows it is {{-Darg="some value with spaces"}}, whereas with Linux it's
{{'-Darg=some value with spaces'}} (correct me if I'm wrong).
> MavenCommandLineBuilder incorrectly adds system properties
> --
>
> Key: MSHARED-141
> URL: https://jira.codehaus.org/browse/MSHARED-141
> Project: Maven Shared Components
> Issue Type: Bug
> Components: maven-invoker
>Affects Versions: maven-invoker-2.0.7, maven-invoker-2.0.8,
> maven-invoker-2.0.9, maven-invoker-2.0.10, maven-invoker-2.0.11
>Reporter: Andrei Solntsev
>Priority: Minor
> Attachments: MSHARED-141-maven-invoker.patch
>
>
> Class MavenCommandLineBuilder adds system properties with spaces.
> For example, given the following properties: {skipTests=true, listScmChanges=}
> MavenCommandLineBuilder generates the following command line:
> cmd.exe /X /C "C:\Programs\apache-maven-2.2.1\bin\mvn.bat -B -N -e -D
> skipTests=true -D listScmChanges="
> The correct form is without spaces: "-DskipTests=true -DlistScmChanges"
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MSHARED-251) Option to change from mvn executable to mvnDebug executable
Robert Scholte created MSHARED-251:
--
Summary: Option to change from mvn executable to mvnDebug
executable
Key: MSHARED-251
URL: https://jira.codehaus.org/browse/MSHARED-251
Project: Maven Shared Components
Issue Type: Improvement
Components: maven-invoker
Affects Versions: maven-invoker-2.0.11
Reporter: Robert Scholte
The {{mvn}} executable is hardcoded. This means it is not possible to use the
{{mvnDebug}} to debug the code executed by the Invoker.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MNG-5102) Mixin POM fragments
[ https://jira.codehaus.org/browse/MNG-5102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tony Lampada updated MNG-5102: -- Attachment: daddy3.zip > Mixin POM fragments > --- > > Key: MNG-5102 > URL: https://jira.codehaus.org/browse/MNG-5102 > Project: Maven 2 & 3 > Issue Type: Wish > Components: POM >Affects Versions: 2.2.1 >Reporter: Anthony Whitford > Fix For: 3.1 > > Attachments: daddy3.zip, maven-tiles.zip > > > I am looking for a way to _mixin_ POM fragments into POMs. Note that this > idea is beyond parent pom inheritance because all projects inherit from a > corporate parent pom. The problem that I am running into is that the > corporate parent pom is turning into an _"everything but the kitchen sink"_ > POM and I'd like to dissect it into POM fragments relevant for individual > modules. > For example, I would like to have mixins for: > * Java projects (that include static code analysis plugins, javadoc, etc.) > * JPA projects (that include DDL generation) > * Flex projects (that include flexmojos, asdoc, etc.) > * Scala projects (that include the maven-scala-compiler plugin, scaladoc, > etc.) > * JavaScript projects (that include build plugins like > maven-yuicompressor-plugin with jslint and compress goals) > Hopefully, you get the idea. Without the ability to factor pom logic, we are > left with two symptoms: > # copy/paste duplication > # complex _"it does it all"_ parent poms (which slow down builds because more > plugins are loaded even though they might not do anything material) > Note that a project may include multiple mixins as I could have a project > that contains Java code, Scala code, and JavaScript. > Another idea is that the mixins could be parameterized, so that the ultimate > pom can be customized based on the parameters (like tokens). > I recall reading about Mixins coming in Maven 3.1, but could not find any > such issue to watch, so am creating one. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MNG-5102) Mixin POM fragments
[ https://jira.codehaus.org/browse/MNG-5102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=310175#comment-310175 ] Tony Lampada commented on MNG-5102: --- Now that maven-tiles has been successfully packed as an [open source project|https://github.com/maoo/maven-tiles/], I made a small project that demonstrates how, using maven-tiles, one can get the desired mixin behaviour. See attached [daddy3.zip|http://jira.codehaus.org/secure/attachment/61530/daddy3.zip] Thanks Maurizio! > Mixin POM fragments > --- > > Key: MNG-5102 > URL: https://jira.codehaus.org/browse/MNG-5102 > Project: Maven 2 & 3 > Issue Type: Wish > Components: POM >Affects Versions: 2.2.1 >Reporter: Anthony Whitford > Fix For: 3.1 > > Attachments: daddy3.zip, maven-tiles.zip > > > I am looking for a way to _mixin_ POM fragments into POMs. Note that this > idea is beyond parent pom inheritance because all projects inherit from a > corporate parent pom. The problem that I am running into is that the > corporate parent pom is turning into an _"everything but the kitchen sink"_ > POM and I'd like to dissect it into POM fragments relevant for individual > modules. > For example, I would like to have mixins for: > * Java projects (that include static code analysis plugins, javadoc, etc.) > * JPA projects (that include DDL generation) > * Flex projects (that include flexmojos, asdoc, etc.) > * Scala projects (that include the maven-scala-compiler plugin, scaladoc, > etc.) > * JavaScript projects (that include build plugins like > maven-yuicompressor-plugin with jslint and compress goals) > Hopefully, you get the idea. Without the ability to factor pom logic, we are > left with two symptoms: > # copy/paste duplication > # complex _"it does it all"_ parent poms (which slow down builds because more > plugins are loaded even though they might not do anything material) > Note that a project may include multiple mixins as I could have a project > that contains Java code, Scala code, and JavaScript. > Another idea is that the mixins could be parameterized, so that the ultimate > pom can be customized based on the parameters (like tokens). > I recall reading about Mixins coming in Maven 3.1, but could not find any > such issue to watch, so am creating one. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MRELEASE-785) Arguments containing spaces and quotes cause the forked maven process to fail
[
https://jira.codehaus.org/browse/MRELEASE-785?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Scholte closed MRELEASE-785.
---
Resolution: Fixed
Fix Version/s: 2.4
Fixed in [r1393175|http://svn.apache.org/viewvc?rev=1393175&view=rev]
I noticed that PLXUTILS-152 already has a test, so let's not be too paranoia.
I've upgraded to 3.0.8, the current most recent release.
Thanks!
> Arguments containing spaces and quotes cause the forked maven process to fail
> -
>
> Key: MRELEASE-785
> URL: https://jira.codehaus.org/browse/MRELEASE-785
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: prepare
>Affects Versions: 2.3.2
> Environment: *nix
>Reporter: Rob Elliot
>Assignee: Robert Scholte
> Fix For: 2.4
>
> Attachments: MRELEASE-785-maven-release-2.3.2.patch,
> MRELEASE-785-maven-release.patch
>
>
> The following config:
> {code:xml}
>
> maven-release-plugin
>
> forked-path
> false
> -Dgpg.passphrase="a phrase 'containing' quotes and
> spaces"
>
>
> {code}
> causes the forked clean verify to fail. This is preventing me using my gpg
> key as part of an automated release process.
> This is due to a bug in Plexus Utils which I have raised as issue 152
> PLXUTILS-152, and for which I have raised a pull request here:
> https://github.com/sonatype/plexus-utils/pull/5. I am raising an issue on
> the release plugin as when/if a fixed version of plexus utils is released the
> maven release plugin will need to upgrade to this new version to benefit.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MNG-5356) Make encrypt/decrypt logic pluggable
Anders Hammar created MNG-5356: -- Summary: Make encrypt/decrypt logic pluggable Key: MNG-5356 URL: https://jira.codehaus.org/browse/MNG-5356 Project: Maven 2 & 3 Issue Type: Improvement Environment: n/a Reporter: Anders Hammar It would be good if Maven Core facilitated the encryption (and decryption) logic to be replaceable. Today's solution is very much hard-coded to the plexus logic. This would make it possible for enterprise environments to re-use existing solutions, like for eg smart cards, for this. The default should be the current implementation though. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MDEP-380) copy-dependencies should be able to use the artifact's baseVersion
Bakito created MDEP-380: --- Summary: copy-dependencies should be able to use the artifact's baseVersion Key: MDEP-380 URL: https://jira.codehaus.org/browse/MDEP-380 Project: Maven 2.x Dependency Plugin Issue Type: New Feature Components: copy-dependencies Affects Versions: 2.5.1 Reporter: Bakito Attachments: maven-dependency-plugin.patch It should be possible to copy dependencies with their baseVersion. Currently the version used for snapshots is the resolvedVersion (timestamped version) org.apache.maven.artifact.DefaultArtifact.setResolvedVersion(String) which may be the timestamped snapshot version. When calling copy-dependencies I expect snapshots to have the snapshot version org.apache.maven.artifact.DefaultArtifact.getBaseVersion(). The attached patch introduces a new parameter 'useBaseVersion' which, if selected, sets the base version in the copied artifact's names. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
