[jira] Commented: (MASSEMBLY-516) Error in Example for sharing-descriptors?
[ http://jira.codehaus.org/browse/MASSEMBLY-516?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=252278#action_252278 ] Jeff Campbell commented on MASSEMBLY-516: - It is also important to note that the descriptor xml file MUST be in /src/main/resources/assemblies (not /src/main/resources/assembly). It seems that half the maven-assembly-plugin documentation indicates that assembly xml files should go in either: /src/main/resources/assembly or /src/main/resources/assemblies I wish there was a better defined standard and that the documentation would be consistent. It might be good to add to this fix the ability to look in either of these to paths for the descriptor xml file. Error in Example for sharing-descriptors? - Key: MASSEMBLY-516 URL: http://jira.codehaus.org/browse/MASSEMBLY-516 Project: Maven 2.x Assembly Plugin Issue Type: Bug Environment: - Reporter: Knut Pape Assignee: John Casey Fix For: 2.3 On Page http://maven.apache.org/plugins/maven-assembly-plugin/examples/sharing-descriptors.html It says that the assembly file from a jar on the class-path shoulld be included the following way: descriptors descriptormyassembly.xml/descriptor /descriptors This didn't work for me. After some fidling (I'm pritty sure that the problem was not a spelling mistake) I came to the following solution: Instead of referencing the assembly by filename I referenced it by it's ID and voila - it worked: descriptorRefs descriptorRefmy-assembly-descriptor-id/descriptorRef /descriptorRefs -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (ARCHETYPE-176) Cannot use -DarchetypeRepository if you have mirrors * in your settings.xml file
Cannot use -DarchetypeRepository if you have mirrors * in your settings.xml file Key: ARCHETYPE-176 URL: http://jira.codehaus.org/browse/ARCHETYPE-176 Project: Maven Archetype Issue Type: Bug Components: Creator, Generator Affects Versions: 2.0-alpha-3 Environment: Java 6 Maven 2.0.9 Reporter: Jeff Campbell I'm using the following command to create a new project from a custom archetype from a 3rd party Maven repo (only the relevant portion of the command is below): mvn archetype:generate -DarchetypeRepository=http://somehost.com/mvnrepo .(other -D params for thecustom archetype)... But, because I have the following in my settings.xml file, I cannot access the repository specified by the -DarchetypeRepository: mirrors mirror idmy.nexus/id name Nexus Mirror/name urlhttp://somehost:8081/nexus/content/groups/public/url mirrorOf*/mirrorOf /mirror /mirrors Work around(s): 1. Don't use mirrors section all together in the settings.xml file. 2. List every single possible maven repo site mirror, in Nexus, that I can possibly think of to hopefully cover every possible custom archetype that will ever be used? (yikes!) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (ARCHETYPE-172) calling mvn archetype:generate -DinteractiveMode=false still prompts user Y:
calling mvn archetype:generate -DinteractiveMode=false still prompts user Y: -- Key: ARCHETYPE-172 URL: http://jira.codehaus.org/browse/ARCHETYPE-172 Project: Maven Archetype Issue Type: Bug Components: Generator Affects Versions: 2.0-alpha-3, 2.0-alpha-2 Reporter: Jeff Campbell I have a simple script that calls maven archetype from the command line with the full archetype command-line. The script hangs because the archetype:generate prompts for the user to hit Y: at the command prompt even thought I specified -DinteractiveMode=false in the script. Expected Results: Maven archetype:generate executes with-out prompting the user for any input when using -DinteractiveMode=false -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MANTTASKS-87) Using a pom.xml for dependencies, in which the pom.xml has a parent pom.xml will cause a Error downloading parent pom error
Using a pom.xml for dependencies, in which the pom.xml has a parent pom.xml will cause a Error downloading parent pom error - Key: MANTTASKS-87 URL: http://jira.codehaus.org/browse/MANTTASKS-87 Project: Maven 2.x Ant Tasks Issue Type: Bug Components: POM Integration Affects Versions: 2.0.7 Environment: WindowsXP Ant version 1.7.0 Reporter: Jeff Campbell Priority: Blocker Using a pom.xml for dependencies, in which the pom.xml has a parent pom.xml will cause a Error downloading parent pom error. This WAS NOT a bug with version 2.0.6 of the maven-ant-tasks (new issue to maven-ant-tasks-2.0.7.jar and still an issue with the latest maven-ant-tasks-2.0.8-SNAPSHOT.jar (as of the writting of this bug)). Just to see if I had done something wrong with the pom.xml file I tried to run a Maven goal against the pom.xml file. I found that if I run mvn clean from this same directory (where the build.xml and pom.xml file is located), using Maven-2.0.7, I get a build successfull (it was able to find the parent pom.xml file... so this seems to be isolated to JUST the maven-ant-task not being able to find the parent pom.xml) Sample of the pom.xml file project xmlns=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; modelVersion4.0.0/modelVersion groupIdintuit.sbconnect/groupId artifactIdsbclogin/artifactId version1.0.3/version nameSBCLogin/name parent groupIdmygroup/groupId artifactIdCommonPOM/artifactId version1.0.2/version /parent dependencies dependency groupIdmyothergroup/groupId artifactIdmyartifact/artifactId version1.0/version /dependency /dependencies /project Line in Ant build.xml file that causes the error: artifact:pom id=maven.project file=pom.xml/ Error that occurs when this line is executed in ant: Error downloading parent pom: Missing: -- 1) mygroup:CommonPOM:pom:1.0.2 Path to dependency: 1) unspecified:unspecified:jar:0.0 2) mygroup:CommonPOM:pom:1.0.2 -- 1 required artifact is missing. for artifact: unspecified:unspecified:jar:0.0 from the specified remote repositories: central (http://repo1.maven.org/maven2) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MPMD-56) targetJdk support for jdk 1.6
targetJdk support for jdk 1.6 - Key: MPMD-56 URL: http://jira.codehaus.org/browse/MPMD-56 Project: Maven 2.x PMD Plugin Issue Type: Bug Components: PMD Affects Versions: 2.2 Environment: Any Reporter: Jeff Campbell Currently you can only set a targetJdk to 1.3, 1.4, and 1.5 what about 1.6? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
