[jira] Created: (MANT-67) The build script fails to generate plexus/components.xml file.
The build script fails to generate plexus/components.xml file. -- Key: MANT-67 URL: https://jira.codehaus.org/browse/MANT-67 Project: Maven 2.x Ant Plugin Issue Type: Bug Affects Versions: 2.3 Environment: Gentoo/Linux, maven-2.2.1, maven-ant-plugin 2.3 Reporter: Kasun Gajasinghe The generated build script by maven-ant-plugin fails to generate the components.xml file when run. It compiles successfully, and builds the jar (without META-INF/plexus/components.xml file). But it fails the tests saying Component descriptor cannot be found in the component repository Reproduce steps - * Get a project that _generates_ components.xml file. One need of mine was maven-runtime at https://svn.apache.org/repos/asf/maven/shared/tags/maven-shared-components-15/maven-runtime * run mvn ant:ant * run ant (I ran ant -Dmaven.settings.offline=true. it doesn't matter anyway) Here's the error log. Buildfile: build.xml test-offline: get-deps: compile: [mkdir] Created dir: /home/me/maven-runtime/target/classes [javac] Compiling 9 source files to /home/me/maven-runtime/target/classes compile-tests: [mkdir] Created dir: /home/me/maven-runtime/target/test-classes [javac] Compiling 5 source files to /home/me/maven-runtime/target/test-classes [copy] Copying 13 files to /home/me/maven-runtime/target/test-classes test-junit-present: test-junit-status: junit-missing: test: [mkdir] Created dir: /home/me/maven-runtime/target/test-reports [junit] Running org.apache.maven.shared.runtime.DefaultMavenRuntimeTest [junit] Testsuite: org.apache.maven.shared.runtime.DefaultMavenRuntimeTest [junit] Tests run: 1, Failures: 0, Errors: 1, Time elapsed: 0.597 sec [junit] Tests run: 1, Failures: 0, Errors: 1, Time elapsed: 0.597 sec [junit] [junit] Testcase: testGetProjectPropertiesWithFileUrl took 0.259 sec [junit] Caused an ERROR [junit] Component descriptor cannot be found in the component repository: org.apache.maven.shared.runtime.MavenRuntime. [junit] org.codehaus.plexus.component.repository.exception.ComponentLookupException: Component descriptor cannot be found in the component repository: org.apache.maven.shared.runtime.MavenRuntime. [junit] at org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:323) [junit] at org.codehaus.plexus.PlexusTestCase.lookup(PlexusTestCase.java:216) [junit] at org.apache.maven.shared.runtime.DefaultMavenRuntimeTest.setUp(DefaultMavenRuntimeTest.java:68) [junit] BUILD FAILED /home/me/maven-runtime/maven-build.xml:155: Test org.apache.maven.shared.runtime.DefaultMavenRuntimeTest failed Total time: 3 seconds -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MASSEMBLY-565) jar-with-dependencies: class from the source in project does NOT override the class in jar dependency
jar-with-dependencies: class from the source in project does NOT override the class in jar dependency - Key: MASSEMBLY-565 URL: https://jira.codehaus.org/browse/MASSEMBLY-565 Project: Maven 2.x Assembly Plugin Issue Type: Bug Affects Versions: 2.2.1 Environment: % mvn -version Apache Maven 3.0.3 (r1075438; 2011-02-28 18:31:09+0100) Maven home: /home/jmv/apps/apache-maven3 Java version: 1.6.0_25, vendor: Sun Microsystems Inc. Java home: /home/jmv/apps/jdk1.6.0_25/jre Default locale: fr_FR, platform encoding: UTF-8 OS name: linux, version: 2.6.38-10-generic, arch: amd64, family: unix Reporter: Jean-Marc Vanel Attachments: maven_bug_build_override_class.zip When running plugin maven-assembly-plugin 2.2.1 with jar-with-dependencies, and there is a class C1 in src/main/java/ that overrides a class C1 in some dependency, in the resulting XXX-jar-with-dependencies.jar the C1.class comes from the dependency, not from the source in project. I would except the class from the source in project to override the corresponding class in jar dependency, So the executable jar is not built correctly. This is particularly annoying, because the tests pass, but the executable jar is not correct. You can see this in the test project attached, where I override class TestCase of JUnit , adding a main , and setting this overriden class as the main class: % java -jar target/maven_bug_build_override_class-1.0-SNAPSHOT-jar-with-dependencies.jar Exception in thread main java.lang.NoSuchMethodError: main ( the original class TestCase of JUnit has no main ). In the test project attached,I kept all the Maven plugins that are in my original project, because they might have a relation with the issue. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-4112) Set property containing the currently executing maven version.
[ https://jira.codehaus.org/browse/MNG-4112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=273424#comment-273424 ] Paul Gier commented on MNG-4112: Added the new properties in [r1147597|http://svn.apache.org/viewvc?view=revisionrevision=1147597]. Added integration test in [r1147598|http://svn.apache.org/viewvc?view=revisionrevision=1147598]. Set property containing the currently executing maven version. -- Key: MNG-4112 URL: https://jira.codehaus.org/browse/MNG-4112 Project: Maven 2 3 Issue Type: Improvement Reporter: Paul Gier Assignee: Paul Gier Fix For: 3.1 Attachments: MNG-4112-maven-embedder.patch It would be helpful to have an easy way to access the current version of maven. This might be accomplished by setting a property like maven.version during startup that would be available to the pom and/or to plugins. This could be used to record what version of maven was used during the build to facilitate build reproducibility. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MNG-5134) Standard documentation for build-in properties
Standard documentation for build-in properties -- Key: MNG-5134 URL: https://jira.codehaus.org/browse/MNG-5134 Project: Maven 2 3 Issue Type: Improvement Components: Documentation: General Reporter: Paul Gier Priority: Minor The Maven site documentation should include a reference to all the available properties. There are a couple of existing locations of property documentation, but nothing on the official Maven site from what I can tell. http://docs.codehaus.org/display/MAVENUSER/MavenPropertiesGuide http://www.sonatype.com/books/mvnref-book/reference/resource-filtering-sect-properties.html -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MNG-5134) Standard documentation for build-in properties
[ https://jira.codehaus.org/browse/MNG-5134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul Gier updated MNG-5134: --- Fix Version/s: 3.0.4 Standard documentation for build-in properties -- Key: MNG-5134 URL: https://jira.codehaus.org/browse/MNG-5134 Project: Maven 2 3 Issue Type: Improvement Components: Documentation: General Reporter: Paul Gier Priority: Minor Fix For: 3.0.4 The Maven site documentation should include a reference to all the available properties. There are a couple of existing locations of property documentation, but nothing on the official Maven site from what I can tell. http://docs.codehaus.org/display/MAVENUSER/MavenPropertiesGuide http://www.sonatype.com/books/mvnref-book/reference/resource-filtering-sect-properties.html -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MNG-4112) Set property containing the currently executing maven version.
[ https://jira.codehaus.org/browse/MNG-4112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paul Gier closed MNG-4112. -- Resolution: Fixed Fix Version/s: 3.0.4 Set property containing the currently executing maven version. -- Key: MNG-4112 URL: https://jira.codehaus.org/browse/MNG-4112 Project: Maven 2 3 Issue Type: Improvement Reporter: Paul Gier Assignee: Paul Gier Fix For: 3.0.4, 3.1 Attachments: MNG-4112-maven-embedder.patch It would be helpful to have an easy way to access the current version of maven. This might be accomplished by setting a property like maven.version during startup that would be available to the pom and/or to plugins. This could be used to record what version of maven was used during the build to facilitate build reproducibility. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
