[jira] Commented: (MDEPLOY-114) Add an option to not fail when remote file already exists and redeploy is forbidden
[ https://jira.codehaus.org/browse/MDEPLOY-114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=283061#comment-283061 ] Jaan Vajakas commented on MDEPLOY-114: -- Same problem here: if the deployment of a multi-module project fails in the middle (e. g. because of lost Internet connection) then I cannot resume the deployment. The Nexus web interface allows deleting artifacts one-by-one but this is very tedious in case of many submodules. An option like -Dredeploy=false with either behavior 1) or 2) would be very helpful indeed (or maybe just Nexus would need a better GUI for deleting multiple artifacts). I think such solutions would be simpler to use than the staging process if one does not need the staging process for other purposes (especially since one could use the usual deployment process and only in the case of failure would one need to take extra steps). > Add an option to not fail when remote file already exists and redeploy is > forbidden > --- > > Key: MDEPLOY-114 > URL: https://jira.codehaus.org/browse/MDEPLOY-114 > Project: Maven 2.x and 3.x Deploy Plugin > Issue Type: Wish > Components: deploy:deploy >Affects Versions: 2.4 >Reporter: Julien HENRY > Labels: contributers-welcome > > In my organisation we are using a MRM (Nexus) with redeployment of release > that is forbidden. > Sometimes the release:perform may fail in the middle of a multi-module > release. It means some modules were deployed but other are not. > Currently it is not possible to restart the release as it will fail on first > deployment (usually the parent pom of the multimodule) because the pom was > already deployed during the first attempt. > I would like to add an option to the deploy plugin that may deal with this > case. Perhaps an option like -Dredeploy=false that may either : > 1) check if the remote file already exists before trying to upload > 2) try to upload everytime but not fail the build > The problem with the second proposal is the error returned by Nexus is > authorization error so we may not be able to distinguish real authorization > error on a new file and redeploy attempt. > Caused by: org.apache.maven.wagon.authorization.AuthorizationException: > Access denied to: http://nexus.mycompany.com/ > content/repositories/myrepo/com/mycustomer/project/parent/3.2.0/parent-3.2.0.pom > at > org.apache.maven.wagon.shared.http.AbstractHttpClientWagon.put(AbstractHttpClientWagon.java:360) > Other options may be more complicated like implementing an atomic deploy > process on multimodule (may need a big change of the deploy protocol). -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MASSEMBLY-395) Module dependencies not included
[ https://jira.codehaus.org/browse/MASSEMBLY-395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=284693#comment-284693 ] Jaan Vajakas commented on MASSEMBLY-395: The problem is still there in assembly plugin 2.2.1 with Maven version 3.0.3. > Module dependencies not included > - > > Key: MASSEMBLY-395 > URL: https://jira.codehaus.org/browse/MASSEMBLY-395 > Project: Maven 2.x Assembly Plugin > Issue Type: Bug >Affects Versions: 2.2-beta-3 > Environment: Maven version: 2.0.9 > Java version: 1.5.0_09 > OS name: "windows xp" version: "5.1" arch: "x86" Family: "windows" >Reporter: Jaan Vajakas > Attachments: my-app.assembly-plugin-2.2.zip, my-app.zip > > > Maven assebly plugin 2.2-beta-3 does not include module dependencies, even > when the explicit true is used in > assembly descriptor. Maven assebly plugin 2.2-beta-2 did not have this issue. > See the attached project: running mvn package for the parent project my-app > creates a ZIP that contains only my-app-module1-1.0-SNAPSHOT.jar. If assembly > plugin 2.2-beta-2 is used (i.e. if one replaces 2.2-beta-3 with 2.2-beta-2 in > pom.xml of my-app) then the ZIP also contains my-app-module2-1.0-SNAPSHOT.jar > and junit-3.8.1.jar. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MASSEMBLY-395) Module dependencies not included
[ http://jira.codehaus.org/browse/MASSEMBLY-395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaan Vajakas updated MASSEMBLY-395: --- Attachment: my-app.assembly-plugin-2.2.zip The problem is still present in assembly plugin 2.2 with Maven version 3.0.1. Added new test project for assembly plugin 2.2: my-app.assembly-plugin-2.2.zip (the old one gave an error with version 2.2 because the binaries/useStrictFiltering element is not supported any more). > Module dependencies not included > - > > Key: MASSEMBLY-395 > URL: http://jira.codehaus.org/browse/MASSEMBLY-395 > Project: Maven 2.x Assembly Plugin > Issue Type: Bug >Affects Versions: 2.2-beta-3 > Environment: Maven version: 2.0.9 > Java version: 1.5.0_09 > OS name: "windows xp" version: "5.1" arch: "x86" Family: "windows" >Reporter: Jaan Vajakas > Attachments: my-app.assembly-plugin-2.2.zip, my-app.zip > > > Maven assebly plugin 2.2-beta-3 does not include module dependencies, even > when the explicit true is used in > assembly descriptor. Maven assebly plugin 2.2-beta-2 did not have this issue. > See the attached project: running mvn package for the parent project my-app > creates a ZIP that contains only my-app-module1-1.0-SNAPSHOT.jar. If assembly > plugin 2.2-beta-2 is used (i.e. if one replaces 2.2-beta-3 with 2.2-beta-2 in > pom.xml of my-app) then the ZIP also contains my-app-module2-1.0-SNAPSHOT.jar > and junit-3.8.1.jar. -- 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] (MASSEMBLY-395) Module dependencies not included
[ https://jira.codehaus.org/browse/MASSEMBLY-395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=356892#comment-356892 ] Jaan Vajakas commented on MASSEMBLY-395: Thank you! > Module dependencies not included > - > > Key: MASSEMBLY-395 > URL: https://jira.codehaus.org/browse/MASSEMBLY-395 > Project: Maven Assembly Plugin > Issue Type: Bug > Components: moduleSet >Affects Versions: 2.2-beta-3 > Environment: Maven version: 2.0.9 > Java version: 1.5.0_09 > OS name: "windows xp" version: "5.1" arch: "x86" Family: "windows" >Reporter: Jaan Vajakas >Assignee: Kristian Rosenvold > Fix For: 2.5.1 > > Attachments: my-app.assembly-plugin-2.2.zip, my-app.zip > > > Maven assebly plugin 2.2-beta-3 does not include module dependencies, even > when the explicit true is used in > assembly descriptor. Maven assebly plugin 2.2-beta-2 did not have this issue. > See the attached project: running mvn package for the parent project my-app > creates a ZIP that contains only my-app-module1-1.0-SNAPSHOT.jar. If assembly > plugin 2.2-beta-2 is used (i.e. if one replaces 2.2-beta-3 with 2.2-beta-2 in > pom.xml of my-app) then the ZIP also contains my-app-module2-1.0-SNAPSHOT.jar > and junit-3.8.1.jar. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] Commented: (MASSEMBLY-395) Module dependencies not included
[ http://jira.codehaus.org/browse/MASSEMBLY-395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=204613#action_204613 ] Jaan Vajakas commented on MASSEMBLY-395: The problem is still present in Maven assembly plugin 2.2-beta-5 with Maven 2.2.1. > Module dependencies not included > - > > Key: MASSEMBLY-395 > URL: http://jira.codehaus.org/browse/MASSEMBLY-395 > Project: Maven 2.x Assembly Plugin > Issue Type: Bug >Affects Versions: 2.2-beta-3 > Environment: Maven version: 2.0.9 > Java version: 1.5.0_09 > OS name: "windows xp" version: "5.1" arch: "x86" Family: "windows" >Reporter: Jaan Vajakas > Attachments: my-app.zip > > > Maven assebly plugin 2.2-beta-3 does not include module dependencies, even > when the explicit true is used in > assembly descriptor. Maven assebly plugin 2.2-beta-2 did not have this issue. > See the attached project: running mvn package for the parent project my-app > creates a ZIP that contains only my-app-module1-1.0-SNAPSHOT.jar. If assembly > plugin 2.2-beta-2 is used (i.e. if one replaces 2.2-beta-3 with 2.2-beta-2 in > pom.xml of my-app) then the ZIP also contains my-app-module2-1.0-SNAPSHOT.jar > and junit-3.8.1.jar. -- 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] (MRELEASE-858) Check if the SVN working copy URL matches connection URL
Jaan Vajakas created MRELEASE-858: - Summary: Check if the SVN working copy URL matches connection URL Key: MRELEASE-858 URL: https://jira.codehaus.org/browse/MRELEASE-858 Project: Maven Release Plugin Issue Type: Improvement Affects Versions: 2.4.2 Reporter: Jaan Vajakas I have several times made the mistake that I have used wrong and SVN URLs (which might point to another branch or another project) in pom.xml and when I run release:prepare, it happily creates an SVN tag of the connection URL, not the URL of the working copy (which could be obtained using the "svn info" command). So I think the release:prepare command should print an error message and refuse from running if the working copy URL doesn't match the connection URL in pom.xml . -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MASSEMBLY-395) Module dependencies not included
Module dependencies not included - Key: MASSEMBLY-395 URL: http://jira.codehaus.org/browse/MASSEMBLY-395 Project: Maven 2.x Assembly Plugin Issue Type: Bug Affects Versions: 2.2-beta-3 Environment: Maven version: 2.0.9 Java version: 1.5.0_09 OS name: "windows xp" version: "5.1" arch: "x86" Family: "windows" Reporter: Jaan Vajakas Attachments: my-app.zip Maven assebly plugin 2.2-beta-3 does not include module dependencies, even when the explicit true is used in assembly descriptor. Maven assebly plugin 2.2-beta-2 did not have this issue. See the attached project: running mvn package for the parent project my-app creates a ZIP that contains only my-app-module1-1.0-SNAPSHOT.jar. If assembly plugin 2.2-beta-2 is used (i.e. if one replaces 2.2-beta-3 with 2.2-beta-2 in pom.xml of my-app) then the ZIP also contains my-app-module2-1.0-SNAPSHOT.jar and junit-3.8.1.jar. -- 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: (MASSEMBLY-276) pom.properties and pom.xml missing from jar generated by jar-with-dependencies
pom.properties and pom.xml missing from jar generated by jar-with-dependencies -- Key: MASSEMBLY-276 URL: http://jira.codehaus.org/browse/MASSEMBLY-276 Project: Maven 2.x Assembly Plugin Issue Type: Bug Affects Versions: 2.2-beta-1 Reporter: Jaan Vajakas How to reproduce: * create a new project with mvn archetype:create -DgroupId=org.sample -DartifactId=sample2 * modify the pom.xml, adding maven-assembly-plugin configuration (see below) * run mvn assembly:directory or mvn assemby:assembly Expected result: the created directory target/sample2-1.0-SNAPSHOT-jar-with-dependencies.dir or JAR target/sample2-1.0-SNAPSHOT-jar-with-dependencies.jar should contain files META-INF/maven/org.sample/sample2/pom.properties and META-INF/maven/org.sample/sample2/pom.xml, as in the example in http://maven.apache.org/plugins/maven-assembly-plugin/usage.html. Actual result: no pom.xml and pom.properties in the created directory or JAR. This is the pom.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 org.sample sample2 jar 1.0-SNAPSHOT sample2 http://maven.apache.org junit junit 3.8.1 test maven-assembly-plugin 2.2-beta-1 jar-with-dependencies pluginrepo http://repo1.maven.org/maven2 true true -- 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] Commented: (MASSEMBLY-395) Module dependencies not included
[ http://jira.codehaus.org/browse/MASSEMBLY-395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=181821#action_181821 ] Jaan Vajakas commented on MASSEMBLY-395: The problem is still present in Maven assembly plugin 2.2-beta-4 with Maven 2.1.0. > Module dependencies not included > - > > Key: MASSEMBLY-395 > URL: http://jira.codehaus.org/browse/MASSEMBLY-395 > Project: Maven 2.x Assembly Plugin > Issue Type: Bug >Affects Versions: 2.2-beta-3 > Environment: Maven version: 2.0.9 > Java version: 1.5.0_09 > OS name: "windows xp" version: "5.1" arch: "x86" Family: "windows" >Reporter: Jaan Vajakas > Attachments: my-app.zip > > > Maven assebly plugin 2.2-beta-3 does not include module dependencies, even > when the explicit true is used in > assembly descriptor. Maven assebly plugin 2.2-beta-2 did not have this issue. > See the attached project: running mvn package for the parent project my-app > creates a ZIP that contains only my-app-module1-1.0-SNAPSHOT.jar. If assembly > plugin 2.2-beta-2 is used (i.e. if one replaces 2.2-beta-3 with 2.2-beta-2 in > pom.xml of my-app) then the ZIP also contains my-app-module2-1.0-SNAPSHOT.jar > and junit-3.8.1.jar. -- 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: (MAVENUPLOAD-2506) javax.servlet.servlet-api-2.3 sources are wrong
javax.servlet.servlet-api-2.3 sources are wrong --- Key: MAVENUPLOAD-2506 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2506 Project: Maven Upload Requests Issue Type: Bug Reporter: Jaan Vajakas The sources JAR http://mirrors.ibiblio.org/pub/mirrors/maven2/javax/servlet/servlet-api/2.3/servlet-api-2.3-sources.jar does not contain e.g. the interface javax.servlet.Filter. It seems that the 2.3 version has accidentally gotten its sources from 2.2. At least the hashes of servlet-api-2.3-sources.jar and servlet-api-2.2-sources.jar are identical: http://mirrors.ibiblio.org/pub/mirrors/maven2/javax/servlet/servlet-api/2.3/servlet-api-2.3-sources.jar.sha1 http://mirrors.ibiblio.org/pub/mirrors/maven2/javax/servlet/servlet-api/2.2/servlet-api-2.2-sources.jar.sha1 -- 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
