[jira] Commented: (MSITE-602) The staged site is deployed to the wrong place
[
https://jira.codehaus.org/browse/MSITE-602?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=275187#comment-275187
]
Dennis Lundberg commented on MSITE-602:
---
A first attempt to fix this was done in
[r1154621|http://svn.apache.org/viewvc?view=revision&revision=1154621].
Unfortunately Jenkins is reporting that the IT site-inheritance is failing when
run with Maven 2.2.1. The IT pass with Maven 3.0.3 though. Will need to
investigate more.
For those interested in testing this fix out, I have deployed a 3.1-SNAPSHOT
version.
> The staged site is deployed to the wrong place
> --
>
> Key: MSITE-602
> URL: https://jira.codehaus.org/browse/MSITE-602
> Project: Maven 2.x and 3.x Site Plugin
> Issue Type: Bug
> Components: site:stage(-deploy)
>Affects Versions: 2.3, 3.0
>Reporter: Dennis Lundberg
>Assignee: Dennis Lundberg
>
> When running 'mvn site:stage-deploy' the site is deployed to the wrong place.
> Below is the output from a test run performed on the Checkstyle Plugin
> project.
> {noformat}
> [INFO] --- maven-site-plugin:3.0:stage-deploy (default-cli) @
> maven-checkstyle-plugin ---
> [INFO] Using this server ID for stage deploy: apache.website
> [INFO] Using this base URL for stage deploy:
> scp://people.apache.org/www/maven.apache.org/plugins/maven-checkstyle-plugin-2.7-SNAPSHOT
> [INFO] Parent project loaded from repository:
> org.apache.maven.plugins:maven-plugins:pom:21
> [INFO] Parent project loaded from repository:
> org.apache.maven:maven-parent:pom:20
> [INFO] Parent project loaded from repository: org.apache:apache:pom:9
> : Keyboard interactive required, supplied password is ignored
> Password: :
> scp://people.apache.org/www/maven.apache.org/plugins/maven-checkstyle-plugin-2.7-SNAPSHOT/
> - Session: Opened
> [INFO] Pushing
> G:\apache\maven\trunks\plugins\maven-checkstyle-plugin\target\site
> [INFO]>>> to
> scp://people.apache.org/www/maven.apache.org/plugins/maven-checkstyle-plugin-2.7-SNAPSHOT/plugins/maven-checkstyle-plugin
> Executing command: mkdir -p
> /www/maven.apache.org/plugins/maven-checkstyle-plugin-2.7-SNAPSHOT/plugins/maven-checkstyle-plugin
> Executing command: mkdir -p
> /www/maven.apache.org/plugins/maven-checkstyle-plugin-2.7-SNAPSHOT/plugins/maven-checkstyle-plugin
> Executing command: scp -t
> "/www/maven.apache.org/plugins/maven-checkstyle-plugin-2.7-SNAPSHOT/plugins/maven-checkstyle-plugin/wagon592489540427231356.zip"
> Uploading: plugins/maven-checkstyle-plugin/wagon592489540427231356.zip to
> scp://people.apache.org/www/maven.apache.org/plugins/maven-checkstyle-plugin-2.7-SNAPSHOT/
> ###
> Transfer finished. 224640 bytes copied in 1.699 seconds
> Executing command: cd
> /www/maven.apache.org/plugins/maven-checkstyle-plugin-2.7-SNAPSHOT/plugins/maven-checkstyle-plugin;
> unzip -q -o wagon592489540427231356.zip; rm -f wagon592489540427231356.zip
> Executing command: chmod -Rf g+w,a+rX
> /www/maven.apache.org/plugins/maven-checkstyle-plugin-2.7-SNAPSHOT/
> scp://people.apache.org/www/maven.apache.org/plugins/maven-checkstyle-plugin-2.7-SNAPSHOT/
> - Session: Disconnecting
> scp://people.apache.org/www/maven.apache.org/plugins/maven-checkstyle-plugin-2.7-SNAPSHOT/
> - Session: Disconnected
> {noformat}
> Notice how it gets deployed to
> {noformat}
> /plugins/maven-checkstyle-plugin-2.7-SNAPSHOT/plugins/maven-checkstyle-plugin/
> {noformat}
> instead of
> {noformat}
> /plugins/maven-checkstyle-plugin-2.7-SNAPSHOT/
> {noformat}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MECLIPSE-293) javaee-api artifact version issue (EE5)
[ https://jira.codehaus.org/browse/MECLIPSE-293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte closed MECLIPSE-293. --- Resolution: Duplicate Assignee: Robert Scholte Duplicate of MECLIPSE-587, although this issue is much older, I've fixed it there. > javaee-api artifact version issue (EE5) > --- > > Key: MECLIPSE-293 > URL: https://jira.codehaus.org/browse/MECLIPSE-293 > Project: Maven 2.x Eclipse Plugin > Issue Type: Bug > Components: WTP support >Affects Versions: 2.4 >Reporter: Thierry Levieux >Assignee: Robert Scholte > > The javaee-api artifact version is 5 (See > http://weblogs.java.net/blog/ludo/archive/2007/01/java_ee_5_apis.html), > whereas eclipse/wtp and maven eclipse only recognizes 5.0 as a valid version. > I think the pom version is not consistent (for instance, glassfish V3 build > project uses 5.0 as artifact version), > but WE NEED a way/workaround to resolve correctly that library version. > I plan to contact Ludovic Champenois (project-owner) and check if he's > confortable with the javaee-api version... > Thanks > Thierry -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MASSEMBLY-334) Can not generate class-path from Manifest
[
https://jira.codehaus.org/browse/MASSEMBLY-334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=275189#comment-275189
]
Ondrej Zizka commented on MASSEMBLY-334:
Stevo, does that mean that you invoke maven-war-plugin in a jar artifact?
> Can not generate class-path from Manifest
> -
>
> Key: MASSEMBLY-334
> URL: https://jira.codehaus.org/browse/MASSEMBLY-334
> Project: Maven 2.x Assembly Plugin
> Issue Type: Bug
>Affects Versions: 2.2-beta-2
> Environment: Pc - Windows XP sp2
>Reporter: Damien
>
> I have a maven's projet multi-module.
> I have a problem when i launch mvn package assembly:assembly
> In the Manifest file, the class path does not generated.
> Pom project
> {code:xml}
>
> http://maven.apache.org/POM/4.0.0";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
> http://maven.apache.org/maven-v4_0_0.xsd";>
> 4.0.0
> com.ipsis.pacha
> Pacha
> pom
> 1.0-SNAPSHOT
> PACHA
>
>
>
>
>
> maven-antrun-plugin
>
>
>
> print-maven-runtime-classpath
> compile
>
>
>name="runtime-classpath"
>
> refid="maven.runtime.classpath" />
>
> message="maven.runtime.classpath=${runtime-classpath}" />
>
>
>
> run
>
>
>
>
> print-maven-test-classpath
> test-compile
>
>
>name="test-classpath"
>
> refid="maven.test.classpath" />
>
> message="maven.test.classpath=${test-classpath}" />
>
>
>
> run
>
>
>
>
>
>
> maven-compiler-plugin
>
>
> 1.6
> 1.6
> 512m
> 1024m
> true
> true
> true
>
> ${JAVA_HOME}\bin\javac.exe
> 1.6
>
>
>
>
>
> true
> maven-deploy-plugin
>
>
> true
>
>
>
>
> org.apache.maven.plugins
> maven-release-plugin
>
> deploy
>
>
>
>
> maven-surefire-plugin
>
>
>
> maven-eclipse-plugin
>
>
[jira] Commented: (MASSEMBLY-334) Can not generate class-path from Manifest
[
https://jira.codehaus.org/browse/MASSEMBLY-334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=275190#comment-275190
]
Ondrej Zizka commented on MASSEMBLY-334:
I have the same issue with Maven 2 - unable to make it put classpath to
MANIFEST.MF.
My project's structure is:
root
* core
* ...
* assembly - depends on all other modules.
> Can not generate class-path from Manifest
> -
>
> Key: MASSEMBLY-334
> URL: https://jira.codehaus.org/browse/MASSEMBLY-334
> Project: Maven 2.x Assembly Plugin
> Issue Type: Bug
>Affects Versions: 2.2-beta-2
> Environment: Pc - Windows XP sp2
>Reporter: Damien
>
> I have a maven's projet multi-module.
> I have a problem when i launch mvn package assembly:assembly
> In the Manifest file, the class path does not generated.
> Pom project
> {code:xml}
>
> http://maven.apache.org/POM/4.0.0";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
> http://maven.apache.org/maven-v4_0_0.xsd";>
> 4.0.0
> com.ipsis.pacha
> Pacha
> pom
> 1.0-SNAPSHOT
> PACHA
>
>
>
>
>
> maven-antrun-plugin
>
>
>
> print-maven-runtime-classpath
> compile
>
>
>name="runtime-classpath"
>
> refid="maven.runtime.classpath" />
>
> message="maven.runtime.classpath=${runtime-classpath}" />
>
>
>
> run
>
>
>
>
> print-maven-test-classpath
> test-compile
>
>
>name="test-classpath"
>
> refid="maven.test.classpath" />
>
> message="maven.test.classpath=${test-classpath}" />
>
>
>
> run
>
>
>
>
>
>
> maven-compiler-plugin
>
>
> 1.6
> 1.6
> 512m
> 1024m
> true
> true
> true
>
> ${JAVA_HOME}\bin\javac.exe
> 1.6
>
>
>
>
>
> true
> maven-deploy-plugin
>
>
> true
>
>
>
>
> org.apache.maven.plugins
> maven-release-plugin
>
> deploy
>
>
>
>
> maven-surefire-plugin
>
>
>
>
[jira] Issue Comment Edited: (MASSEMBLY-334) Can not generate class-path from Manifest
[
https://jira.codehaus.org/browse/MASSEMBLY-334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=275190#comment-275190
]
Ondrej Zizka edited comment on MASSEMBLY-334 at 8/7/11 5:54 AM:
I have the same issue with Maven 2 - unable to make it put classpath to
MANIFEST.MF.
My project's structure is:
* root
* core
* ...
* assembly - depends on all other modules.
was (Author: pekarna):
I have the same issue with Maven 2 - unable to make it put classpath to
MANIFEST.MF.
My project's structure is:
root
* core
* ...
* assembly - depends on all other modules.
> Can not generate class-path from Manifest
> -
>
> Key: MASSEMBLY-334
> URL: https://jira.codehaus.org/browse/MASSEMBLY-334
> Project: Maven 2.x Assembly Plugin
> Issue Type: Bug
>Affects Versions: 2.2-beta-2
> Environment: Pc - Windows XP sp2
>Reporter: Damien
>
> I have a maven's projet multi-module.
> I have a problem when i launch mvn package assembly:assembly
> In the Manifest file, the class path does not generated.
> Pom project
> {code:xml}
>
> http://maven.apache.org/POM/4.0.0";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
> http://maven.apache.org/maven-v4_0_0.xsd";>
> 4.0.0
> com.ipsis.pacha
> Pacha
> pom
> 1.0-SNAPSHOT
> PACHA
>
>
>
>
>
> maven-antrun-plugin
>
>
>
> print-maven-runtime-classpath
> compile
>
>
>name="runtime-classpath"
>
> refid="maven.runtime.classpath" />
>
> message="maven.runtime.classpath=${runtime-classpath}" />
>
>
>
> run
>
>
>
>
> print-maven-test-classpath
> test-compile
>
>
>name="test-classpath"
>
> refid="maven.test.classpath" />
>
> message="maven.test.classpath=${test-classpath}" />
>
>
>
> run
>
>
>
>
>
>
> maven-compiler-plugin
>
>
> 1.6
> 1.6
> 512m
> 1024m
> true
> true
> true
>
> ${JAVA_HOME}\bin\javac.exe
> 1.6
>
>
>
>
>
> true
> maven-deploy-plugin
>
>
> true
>
>
>
>
> org.apache.maven.plugins
> maven-release-plugin
>
> dep
[jira] Issue Comment Edited: (MASSEMBLY-334) Can not generate class-path from Manifest
[
https://jira.codehaus.org/browse/MASSEMBLY-334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=275190#comment-275190
]
Ondrej Zizka edited comment on MASSEMBLY-334 at 8/7/11 5:55 AM:
I have the same issue with Maven 2 - unable to make it put classpath to
MANIFEST.MF.
My project's structure is:
* root
** core
** ...
** assembly - depends on all other modules.
was (Author: pekarna):
I have the same issue with Maven 2 - unable to make it put classpath to
MANIFEST.MF.
My project's structure is:
* root
* core
* ...
* assembly - depends on all other modules.
> Can not generate class-path from Manifest
> -
>
> Key: MASSEMBLY-334
> URL: https://jira.codehaus.org/browse/MASSEMBLY-334
> Project: Maven 2.x Assembly Plugin
> Issue Type: Bug
>Affects Versions: 2.2-beta-2
> Environment: Pc - Windows XP sp2
>Reporter: Damien
>
> I have a maven's projet multi-module.
> I have a problem when i launch mvn package assembly:assembly
> In the Manifest file, the class path does not generated.
> Pom project
> {code:xml}
>
> http://maven.apache.org/POM/4.0.0";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
> http://maven.apache.org/maven-v4_0_0.xsd";>
> 4.0.0
> com.ipsis.pacha
> Pacha
> pom
> 1.0-SNAPSHOT
> PACHA
>
>
>
>
>
> maven-antrun-plugin
>
>
>
> print-maven-runtime-classpath
> compile
>
>
>name="runtime-classpath"
>
> refid="maven.runtime.classpath" />
>
> message="maven.runtime.classpath=${runtime-classpath}" />
>
>
>
> run
>
>
>
>
> print-maven-test-classpath
> test-compile
>
>
>name="test-classpath"
>
> refid="maven.test.classpath" />
>
> message="maven.test.classpath=${test-classpath}" />
>
>
>
> run
>
>
>
>
>
>
> maven-compiler-plugin
>
>
> 1.6
> 1.6
> 512m
> 1024m
> true
> true
> true
>
> ${JAVA_HOME}\bin\javac.exe
> 1.6
>
>
>
>
>
> true
> maven-deploy-plugin
>
>
> true
>
>
>
>
> org.apache.maven.plugins
> maven-release-plugin
>
>
[jira] Commented: (MECLIPSE-431) Non-project EJB dependencies need a version number in application.xml
[ https://jira.codehaus.org/browse/MECLIPSE-431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=275192#comment-275192 ] Robert Scholte commented on MECLIPSE-431: - I'm willing to apply these patches, but I'm missing an integration test to verify it (for now and for ever to prevent regression). Would be great if someone could provide one. See https://svn.apache.org/repos/asf/maven/plugins/trunk/maven-eclipse-plugin/src/it/ for some examples. These are just mini maven projects hitting the problem. > Non-project EJB dependencies need a version number in application.xml > - > > Key: MECLIPSE-431 > URL: https://jira.codehaus.org/browse/MECLIPSE-431 > Project: Maven 2.x Eclipse Plugin > Issue Type: Bug > Components: RAD support, WTP support >Affects Versions: 2.5.1 >Reporter: Michael Johns > Attachments: MECLIPSE-431.2.patch, MECLIPSE_431.3.patch, > MECLIPSE_431.4.patch, MECLIPSE-431.patch > > > This relates to issue MECLIPSE-430. When including EJBs that were built > previously (ie, not part of the same multi-module project as the ear), the > application.xml needs to include their version number. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MNG-5150) DepMgmt does incorrect scope updates of child deps of a profivedaffecting the runtime classpath
DepMgmt does incorrect scope updates of child deps of a profivedaffecting the runtime classpath --- Key: MNG-5150 URL: https://jira.codehaus.org/browse/MNG-5150 Project: Maven 2 & 3 Issue Type: Bug Components: Dependencies Affects Versions: 3.0.3, 3.0.2, 3.0.1, 3.0 Environment: any Reporter: Anders Hammar -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-5150) DepMgmt does incorrect scope updates of child deps of a profivedaffecting the runtime classpath
[ https://jira.codehaus.org/browse/MNG-5150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=275196#comment-275196 ] Anders Hammar commented on MNG-5150: I prematurely submitted this. Please do the following updates to the ticket: Summary: DepMgmt incorrectly updates scope of a provided dependency's child dependency (affecting the runtime classpath) Description: See issue MJBOSSPACK-40 for details, especially Benjamin's clarifications on difference between how Maven 2 and 3 behave. Test projects are available in that ticket. > DepMgmt does incorrect scope updates of child deps of a profivedaffecting the > runtime classpath > --- > > Key: MNG-5150 > URL: https://jira.codehaus.org/browse/MNG-5150 > Project: Maven 2 & 3 > Issue Type: Bug > Components: Dependencies >Affects Versions: 3.0, 3.0.1, 3.0.2, 3.0.3 > Environment: any >Reporter: Anders Hammar > -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MECLIPSE-676) linkedResources: vs
[ https://jira.codehaus.org/browse/MECLIPSE-676?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte closed MECLIPSE-676. --- Resolution: Fixed Fix Version/s: 2.9 Assignee: Robert Scholte Fixed in [rev. 1154754|http://svn.apache.org/viewvc?rev=1154754&view=rev] > linkedResources: vs > > > Key: MECLIPSE-676 > URL: https://jira.codehaus.org/browse/MECLIPSE-676 > Project: Maven 2.x Eclipse Plugin > Issue Type: Bug > Components: Core : .project >Affects Versions: 2.8 > Environment: Elipse 3.6, mvn 2.2.1, Mac OS X 10.6.5 >Reporter: Lutz Huehnken >Assignee: Robert Scholte > Fix For: 2.9 > > > When creating a link to another folder in Eclipse 3.6, it will generate a > snippet like this in the .project: > > > src/main/webapp/docroot/myfolder > 2 > > FOLDER_VAR/otherfolder/myfolder > > > When running eclipse:eclipse, the parsing / update of .project will fail with: > java.lang.IllegalArgumentException: No location node. > at > org.apache.maven.plugin.eclipse.LinkedResource.(LinkedResource.java:110) > at > org.apache.maven.plugin.eclipse.writers.EclipseProjectWriter.write(EclipseProjectWriter.java:155) > at > org.apache.maven.plugin.eclipse.EclipsePlugin.writeConfiguration(EclipsePlugin.java:1139) > Apparently, the plugin expects the element rather than > , which seems to be a bug. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MECLIPSE-499) Improve eclipse:eclipse excludes option
[ https://jira.codehaus.org/browse/MECLIPSE-499?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte closed MECLIPSE-499. --- Resolution: Fixed Fix Version/s: 2.9 Assignee: Robert Scholte Fixed in [rev. 1154761|http://svn.apache.org/viewvc?rev=1154761&view=rev] > Improve eclipse:eclipse excludes option > --- > > Key: MECLIPSE-499 > URL: https://jira.codehaus.org/browse/MECLIPSE-499 > Project: Maven 2.x Eclipse Plugin > Issue Type: Improvement > Components: Core : .project >Affects Versions: 2.5.1 >Reporter: Nick Stolwijk >Assignee: Robert Scholte > Fix For: 2.9 > > > The documentation don't reflect how to configure the exludes option. Please > include some documentation, like > List of [groupId]:[artifactId] -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MCOMPILER-157) Maven Compiler Plugin should add to compileSourceRoots for next plugins to consider as source directory for generated files
[ https://jira.codehaus.org/browse/MCOMPILER-157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=275219#comment-275219 ] Jérôme Verstrynge commented on MCOMPILER-157: - Hi, I have tried to above workaround, but it does not work. Here is the link to the StackOverflow question I created earlier today: http://stackoverflow.com/questions/6975298/generated-code-not-taken-into-account-in-maven-compile-process. > Maven Compiler Plugin should add to compileSourceRoots for next plugins to > consider as source directory for generated files > > > Key: MCOMPILER-157 > URL: https://jira.codehaus.org/browse/MCOMPILER-157 > Project: Maven 2.x Compiler Plugin > Issue Type: Bug >Affects Versions: 2.3.2 > Environment: Java 6 >Reporter: Zoran Regvart > Attachments: maven-compiler-plugin-add-compileSourceRoots.patch, > test-case.zip > > > Maven Compiler Plugin by relying on javac by default, on Java 6 platform > includes annotation processors in it's processing, these in end could > generate sources that are placed by default in > target/generated-sources/annotations. The later should be added to > compileSourceRoots so that next plugin in execution would consider those > sources. > Please, see the attached test case and consider the attached patch in the > next release of maven-compiler-plugin. > thanks, > Zoran -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MCOMPILER-157) Maven Compiler Plugin should add to compileSourceRoots for next plugins to consider as source directory for generated files
[ https://jira.codehaus.org/browse/MCOMPILER-157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=275222#comment-275222 ] Jérôme Verstrynge commented on MCOMPILER-157: - To be more precise, when I apply the workaround to the provided test case, it works. Yet, in my application, it does not work. The only difference is that I generate a java file where only a .aj file is generated in the test case. > Maven Compiler Plugin should add to compileSourceRoots for next plugins to > consider as source directory for generated files > > > Key: MCOMPILER-157 > URL: https://jira.codehaus.org/browse/MCOMPILER-157 > Project: Maven 2.x Compiler Plugin > Issue Type: Bug >Affects Versions: 2.3.2 > Environment: Java 6 >Reporter: Zoran Regvart > Attachments: maven-compiler-plugin-add-compileSourceRoots.patch, > test-case.zip > > > Maven Compiler Plugin by relying on javac by default, on Java 6 platform > includes annotation processors in it's processing, these in end could > generate sources that are placed by default in > target/generated-sources/annotations. The later should be added to > compileSourceRoots so that next plugin in execution would consider those > sources. > Please, see the attached test case and consider the attached patch in the > next release of maven-compiler-plugin. > thanks, > Zoran -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MNG-5150) DepMgmt incorrectly updates scope of a provided dependency's child dependency (affecting the runtime classpath)
[ https://jira.codehaus.org/browse/MNG-5150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter updated MNG-5150: -- Summary: DepMgmt incorrectly updates scope of a provided dependency's child dependency (affecting the runtime classpath) (was: DepMgmt does incorrect scope updates of child deps of a profivedaffecting the runtime classpath) > DepMgmt incorrectly updates scope of a provided dependency's child dependency > (affecting the runtime classpath) > --- > > Key: MNG-5150 > URL: https://jira.codehaus.org/browse/MNG-5150 > Project: Maven 2 & 3 > Issue Type: Bug > Components: Dependencies >Affects Versions: 3.0, 3.0.1, 3.0.2, 3.0.3 > Environment: any >Reporter: Anders Hammar > -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MNG-5150) DepMgmt incorrectly updates scope of a provided dependency's child dependency (affecting the runtime classpath)
[ https://jira.codehaus.org/browse/MNG-5150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter updated MNG-5150: -- Description: See issue MJBOSSPACK-40 for details, especially Benjamin's clarifications on difference between how Maven 2 and 3 behave. Test projects are available in that ticket. > DepMgmt incorrectly updates scope of a provided dependency's child dependency > (affecting the runtime classpath) > --- > > Key: MNG-5150 > URL: https://jira.codehaus.org/browse/MNG-5150 > Project: Maven 2 & 3 > Issue Type: Bug > Components: Dependencies >Affects Versions: 3.0, 3.0.1, 3.0.2, 3.0.3 > Environment: any >Reporter: Anders Hammar > > See issue MJBOSSPACK-40 for details, especially Benjamin's clarifications on > difference between how Maven 2 and 3 behave. Test projects are available in > that ticket. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-5030) Provide a way to get a raw XML for plugin to read
[
https://jira.codehaus.org/browse/MNG-5030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=275223#comment-275223
]
Evgeny Goldin commented on MNG-5030:
Another use case that can be *very* helpful to plugin authors is knowing a line
number of raw XML data. So first, plugin can be validated and
if error is found a message can be displayed specifying the line where user
made a mistake in configuring a plugin.
> Provide a way to get a raw XML for plugin to read
> -
>
> Key: MNG-5030
> URL: https://jira.codehaus.org/browse/MNG-5030
> Project: Maven 2 & 3
> Issue Type: New Feature
> Components: Plugin API
>Affects Versions: 3.0.2
>Reporter: Evgeny Goldin
>
> As a plugin author I may need to read its *{{}}* slightly
> different than Maven does it. It would be very nice to get a raw XML as an
> alternative to standard fields injection.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MCOMPILER-157) Maven Compiler Plugin should add to compileSourceRoots for next plugins to consider as source directory for generated files
[ https://jira.codehaus.org/browse/MCOMPILER-157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=275226#comment-275226 ] Jérôme Verstrynge commented on MCOMPILER-157: - I have performed some tests and here are my results: i) I have checked-out maven-compiler-plugin from the 2.3.3 release locally ii) I have applied the patch provided by Zoran iii) I confirm that the issue he reported is solved with this patch (and it does not break existing tests) iv) However, when generating a java file instead of an aspectj file, the java file is not taken into account in the compiling process (it is not part of the generated .jar) I am posting another test case to illustrate my point. Keep in mind that I am new to annotation processing, so I may miss something obvious. > Maven Compiler Plugin should add to compileSourceRoots for next plugins to > consider as source directory for generated files > > > Key: MCOMPILER-157 > URL: https://jira.codehaus.org/browse/MCOMPILER-157 > Project: Maven 2.x Compiler Plugin > Issue Type: Bug >Affects Versions: 2.3.2 > Environment: Java 6 >Reporter: Zoran Regvart > Attachments: maven-compiler-plugin-add-compileSourceRoots.patch, > test-case.zip > > > Maven Compiler Plugin by relying on javac by default, on Java 6 platform > includes annotation processors in it's processing, these in end could > generate sources that are placed by default in > target/generated-sources/annotations. The later should be added to > compileSourceRoots so that next plugin in execution would consider those > sources. > Please, see the attached test case and consider the attached patch in the > next release of maven-compiler-plugin. > thanks, > Zoran -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MCOMPILER-157) Maven Compiler Plugin should add to compileSourceRoots for next plugins to consider as source directory for generated files
[ https://jira.codehaus.org/browse/MCOMPILER-157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=275227#comment-275227 ] Jérôme Verstrynge commented on MCOMPILER-157: - Sorry, I meant 2.3.2 release. > Maven Compiler Plugin should add to compileSourceRoots for next plugins to > consider as source directory for generated files > > > Key: MCOMPILER-157 > URL: https://jira.codehaus.org/browse/MCOMPILER-157 > Project: Maven 2.x Compiler Plugin > Issue Type: Bug >Affects Versions: 2.3.2 > Environment: Java 6 >Reporter: Zoran Regvart > Attachments: maven-compiler-plugin-add-compileSourceRoots.patch, > test-case.zip > > > Maven Compiler Plugin by relying on javac by default, on Java 6 platform > includes annotation processors in it's processing, these in end could > generate sources that are placed by default in > target/generated-sources/annotations. The later should be added to > compileSourceRoots so that next plugin in execution would consider those > sources. > Please, see the attached test case and consider the attached patch in the > next release of maven-compiler-plugin. > thanks, > Zoran -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MCOMPILER-157) Maven Compiler Plugin should add to compileSourceRoots for next plugins to consider as source directory for generated files
[ https://jira.codehaus.org/browse/MCOMPILER-157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jérôme Verstrynge updated MCOMPILER-157: Attachment: TestCase2.zip > Maven Compiler Plugin should add to compileSourceRoots for next plugins to > consider as source directory for generated files > > > Key: MCOMPILER-157 > URL: https://jira.codehaus.org/browse/MCOMPILER-157 > Project: Maven 2.x Compiler Plugin > Issue Type: Bug >Affects Versions: 2.3.2 > Environment: Java 6 >Reporter: Zoran Regvart > Attachments: maven-compiler-plugin-add-compileSourceRoots.patch, > TestCase2.zip, test-case.zip > > > Maven Compiler Plugin by relying on javac by default, on Java 6 platform > includes annotation processors in it's processing, these in end could > generate sources that are placed by default in > target/generated-sources/annotations. The later should be added to > compileSourceRoots so that next plugin in execution would consider those > sources. > Please, see the attached test case and consider the attached patch in the > next release of maven-compiler-plugin. > thanks, > Zoran -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
