[jira] (MSCMPUB-18) publish-scm can fail with many files on linux
[ https://jira.codehaus.org/browse/MSCMPUB-18?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=365921#comment-365921 ] Cem Koc commented on MSCMPUB-18: I am hitting same error. Is there any workaround for this issue? publish-scm can fail with many files on linux - Key: MSCMPUB-18 URL: https://jira.codehaus.org/browse/MSCMPUB-18 Project: Maven SCM Publish Plugin Issue Type: Improvement Affects Versions: 1.1 Environment: Fedora 19+ (and certainly many of linux distro) Reporter: Charlie Mordant Hi, I have a pretty complete site to publish to a git repository. I'm unable to publish it because linux limits command arguments to ARG_MAX kernel argument (unmodifiable): http://unix.stackexchange.com/questions/38955/argument-list-too-long-for-ls And for sure, the command is veery long (more than two or three Jenkins console pages). This bug is at least blocker for my concern. The exact error: The error: Cannot run program /bin/sh (in directory /var/lib/jenkins/jobs/OsgiliathEF-Site-Deploy/workspace/target/scmpublish-checkout): error=7, Liste d'arguments trop longue An alternative could be either to pass a shell file containing arguments, either simply automate this task (what I'm doing now): * edit .gitignore and unignore target/staging directory * git add target/staging git commit -m Initial dist subtree commit * git subtree push --prefix target/staging origin gh-pages * rollback and delete last revision :) There are maybe best alternatives such as using xargs or make scalable equivalents of the command: http://www.gnu.org/software/coreutils/faq/coreutils-faq.html#Argument-list-too-long Best regards Charlie -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (SCM-740) Maven Release Plugin releases SNAPSHOT instead of STABLE version
[ https://jira.codehaus.org/browse/SCM-740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=343122#comment-343122 ] Cem Koc commented on SCM-740: - @Mark, Is there any timeline for release v1.10? Maven Release Plugin releases SNAPSHOT instead of STABLE version Key: SCM-740 URL: https://jira.codehaus.org/browse/SCM-740 Project: Maven SCM Issue Type: Bug Components: maven-scm-provider-git Environment: Everywhere with maven-scm-provider-gitexe of version 1.9 (and maybe older) Reporter: Jan Novotný Assignee: Mark Struberg Fix For: 1.10 Attachments: Wrong_base_directory_used1.patch If you have following project structure: - superproject [Git repository root] - projectA [release target] - projectB [release target] in other words you release subproject of a larger Git repository separately, you probably run at the same issue as we did. No recipe from above mentioned sources solves your problems and during release:prepare phase still no commit of stable pom.xml occurs. There is another bug in GitStatusConsumer class that checks output of the git status --porcelain command and verifies existency of the mentioned files on local filesystem. Regretfully it uses working directory instead of git repository root as the base folder and thus it constructs invalid path to the file where project folder directory is duplicated. Problem is better described here: http://blog.novoj.net/2014/01/24/maven-release-plugin-releases-snapshot-instead-of-stable-version -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (SCM-740) Maven Release Plugin releases SNAPSHOT instead of STABLE version
[ https://jira.codehaus.org/browse/SCM-740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=342832#comment-342832 ] Cem Koc commented on SCM-740: - Please vote this issue... Maven Release Plugin releases SNAPSHOT instead of STABLE version Key: SCM-740 URL: https://jira.codehaus.org/browse/SCM-740 Project: Maven SCM Issue Type: Bug Components: maven-scm-provider-git Environment: Everywhere with maven-scm-provider-gitexe of version 1.9 (and maybe older) Reporter: Jan Novotný Attachments: Wrong_base_directory_used1.patch If you have following project structure: - superproject [Git repository root] - projectA [release target] - projectB [release target] in other words you release subproject of a larger Git repository separately, you probably run at the same issue as we did. No recipe from above mentioned sources solves your problems and during release:prepare phase still no commit of stable pom.xml occurs. There is another bug in GitStatusConsumer class that checks output of the git status --porcelain command and verifies existency of the mentioned files on local filesystem. Regretfully it uses working directory instead of git repository root as the base folder and thus it constructs invalid path to the file where project folder directory is duplicated. Problem is better described here: http://blog.novoj.net/2014/01/24/maven-release-plugin-releases-snapshot-instead-of-stable-version -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (SCM-740) Maven Release Plugin releases SNAPSHOT instead of STABLE version
[ https://jira.codehaus.org/browse/SCM-740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=342821#comment-342821 ] Cem Koc commented on SCM-740: - I started to have same issue for a few days. Maven Release Plugin releases SNAPSHOT instead of STABLE version Key: SCM-740 URL: https://jira.codehaus.org/browse/SCM-740 Project: Maven SCM Issue Type: Bug Components: maven-scm-provider-git Environment: Everywhere with maven-scm-provider-gitexe of version 1.9 (and maybe older) Reporter: Jan Novotný Attachments: Wrong_base_directory_used1.patch If you have following project structure: - superproject [Git repository root] - projectA [release target] - projectB [release target] in other words you release subproject of a larger Git repository separately, you probably run at the same issue as we did. No recipe from above mentioned sources solves your problems and during release:prepare phase still no commit of stable pom.xml occurs. There is another bug in GitStatusConsumer class that checks output of the git status --porcelain command and verifies existency of the mentioned files on local filesystem. Regretfully it uses working directory instead of git repository root as the base folder and thus it constructs invalid path to the file where project folder directory is duplicated. Problem is better described here: http://blog.novoj.net/2014/01/24/maven-release-plugin-releases-snapshot-instead-of-stable-version -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (SCM-740) Maven Release Plugin releases SNAPSHOT instead of STABLE version
[ https://jira.codehaus.org/browse/SCM-740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=342821#comment-342821 ] Cem Koc edited comment on SCM-740 at 3/12/14 5:23 PM: -- I started to have same issue for a few days. @Andreas Dangel's comment is true workaround currently. Thanks. was (Author: cem koc): I started to have same issue for a few days. Maven Release Plugin releases SNAPSHOT instead of STABLE version Key: SCM-740 URL: https://jira.codehaus.org/browse/SCM-740 Project: Maven SCM Issue Type: Bug Components: maven-scm-provider-git Environment: Everywhere with maven-scm-provider-gitexe of version 1.9 (and maybe older) Reporter: Jan Novotný Attachments: Wrong_base_directory_used1.patch If you have following project structure: - superproject [Git repository root] - projectA [release target] - projectB [release target] in other words you release subproject of a larger Git repository separately, you probably run at the same issue as we did. No recipe from above mentioned sources solves your problems and during release:prepare phase still no commit of stable pom.xml occurs. There is another bug in GitStatusConsumer class that checks output of the git status --porcelain command and verifies existency of the mentioned files on local filesystem. Regretfully it uses working directory instead of git repository root as the base folder and thus it constructs invalid path to the file where project folder directory is duplicated. Problem is better described here: http://blog.novoj.net/2014/01/24/maven-release-plugin-releases-snapshot-instead-of-stable-version -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] Issue Comment Edited: (MWAR-249) War plugin doesn't let modify the contents of the exploded directory
[ http://jira.codehaus.org/browse/MWAR-249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=256095#action_256095 ] cem koc edited comment on MWAR-249 at 2/15/11 2:00 AM: --- But there is a two different behaviour between different versions of the war plugin. For example, this behaviour was different in 2.1-beta-1. If you modify war plugin version of the pom.xml, you can easily see that war plugin does not touch modified files. Please let me know after trying since this issue is a serious block for us for updating our war plugin. In many of our projects we are using such kind of pre-processing before package phase. Thanks was (Author: cem koc): But there is a two different behaviour between different versions of the war plugin. For example, this behaviour was different in 2.1-beta-1. If you modify war plugin version of the pom.xml, you can easily see that war plugin does not touch modified files. War plugin doesn't let modify the contents of the exploded directory -- Key: MWAR-249 URL: http://jira.codehaus.org/browse/MWAR-249 Project: Maven 2.x WAR Plugin Issue Type: Bug Affects Versions: 2.1, 2.2 Environment: maven 3 Reporter: cem koc Attachments: Test.zip Shortly I am trying to modify the contents of the exploded directory before package phase. I was successfully modifying contents of the exploded directories before updating my war plugin. My goal was 1) Creating an exploded directory of the sources. 2) Modifying contents with Replace plugin 3) Creating a war file including modified files To recreate issue, *) mvn clean prepare-package -- This will create as expected file. *) mvn clean package -- This will replace again modified file with old one. Thanks -- 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] Issue Comment Edited: (MWAR-249) War plugin doesn't let modify the contents of the exploded directory
[
http://jira.codehaus.org/browse/MWAR-249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=256124#action_256124
]
cem koc edited comment on MWAR-249 at 2/15/11 6:16 AM:
---
Hi,
It seems that default configuration of the war plugin changed. To make expected
behaviour as in this example cache parameter should be activated.
{code:xml}
plugin
artifactIdmaven-war-plugin/artifactId
version2.1.1/version
executions
execution
phasegenerate-resources/phase
goals
goalexploded/goal
/goals
/execution
/executions
configuration
useCachetrue/useCache
/configuration
/plugin
{code}
By the way at maven mail list Marc helped me to solve this problem.
http://maven.40175.n5.nabble.com/War-plugin-2-1-beta-1-problem-td3384365.html#a3385808
was (Author: cem koc):
Hi,
It seems that default configuration of the war plugin changed. To make expected
behaviour as in this example cache parameter should be activated.
{code:xml}
plugin
artifactIdmaven-war-plugin/artifactId
version2.1.1/version
executions
execution
phasegenerate-resources/phase
goals
goalexploded/goal
/goals
/execution
/executions
configuration
useCachetrue/useCache
/configuration
/plugin
{code}
By the way at maven mail list Marc helped me to solve this problem.
http://maven.40175.n5.nabble.com/War-plugin-2-1-beta-1-problem-td3384365.html#a3385808
War plugin doesn't let modify the contents of the exploded directory
--
Key: MWAR-249
URL: http://jira.codehaus.org/browse/MWAR-249
Project: Maven 2.x WAR Plugin
Issue Type: Bug
Affects Versions: 2.1, 2.2
Environment: maven 3
Reporter: cem koc
Attachments: Test.zip
Shortly I am trying to modify the contents of the exploded directory before
package phase. I was successfully modifying contents of the exploded
directories before updating my war plugin.
My goal was
1) Creating an exploded directory of the sources.
2) Modifying contents with Replace plugin
3) Creating a war file including modified files
To recreate issue,
*) mvn clean prepare-package -- This will create as expected file.
*) mvn clean package -- This will replace again modified file with old one.
Thanks
--
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: (MWAR-249) War plugin doesn't let modify the contents of the exploded directory
[
http://jira.codehaus.org/browse/MWAR-249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=256124#action_256124
]
cem koc commented on MWAR-249:
--
Hi,
It seems that default configuration of the war plugin changed. To make expected
behaviour as in this example cache parameter should be activated.
{code:xml}
plugin
artifactIdmaven-war-plugin/artifactId
version2.1.1/version
executions
execution
phasegenerate-resources/phase
goals
goalexploded/goal
/goals
/execution
/executions
configuration
useCachetrue/useCache
/configuration
/plugin
{code}
By the way at maven mail list Marc helped me to solve this problem.
http://maven.40175.n5.nabble.com/War-plugin-2-1-beta-1-problem-td3384365.html#a3385808
War plugin doesn't let modify the contents of the exploded directory
--
Key: MWAR-249
URL: http://jira.codehaus.org/browse/MWAR-249
Project: Maven 2.x WAR Plugin
Issue Type: Bug
Affects Versions: 2.1, 2.2
Environment: maven 3
Reporter: cem koc
Attachments: Test.zip
Shortly I am trying to modify the contents of the exploded directory before
package phase. I was successfully modifying contents of the exploded
directories before updating my war plugin.
My goal was
1) Creating an exploded directory of the sources.
2) Modifying contents with Replace plugin
3) Creating a war file including modified files
To recreate issue,
*) mvn clean prepare-package -- This will create as expected file.
*) mvn clean package -- This will replace again modified file with old one.
Thanks
--
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: (MWAR-249) War plugin doesn't let modify the contents of the exploded directory
[ http://jira.codehaus.org/browse/MWAR-249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=256135#action_256135 ] cem koc commented on MWAR-249: -- Without use cache directive, war plugin is replacing modified files which are modified at another phase. Use cache is protecting files which are modified at another phases. Without use cache 1) Copy files with war:exploded 2) Modify them with replace plugin 3) Replace all files at target folder with war:war at package phase. this is completely deleting modified files with are enhanced with another plugin With use cache 1) Copy files with war:exploded 2) Modify them with replace plugin 3) War:war without deleting modified files And as a result of this, It lets us for pre-processing before package phase at exploded folder. War plugin doesn't let modify the contents of the exploded directory -- Key: MWAR-249 URL: http://jira.codehaus.org/browse/MWAR-249 Project: Maven 2.x WAR Plugin Issue Type: Bug Affects Versions: 2.1, 2.2 Environment: maven 3 Reporter: cem koc Attachments: Test.zip Shortly I am trying to modify the contents of the exploded directory before package phase. I was successfully modifying contents of the exploded directories before updating my war plugin. My goal was 1) Creating an exploded directory of the sources. 2) Modifying contents with Replace plugin 3) Creating a war file including modified files To recreate issue, *) mvn clean prepare-package -- This will create as expected file. *) mvn clean package -- This will replace again modified file with old one. Thanks -- 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: (MWAR-249) War plugin doesn't let modify the contents of the exploded directory
War plugin doesn't let modify the contents of the exploded directory -- Key: MWAR-249 URL: http://jira.codehaus.org/browse/MWAR-249 Project: Maven 2.x WAR Plugin Issue Type: Bug Affects Versions: 2.1, 2.2 Environment: maven 3 Reporter: cem koc Attachments: Test.zip Shortly I am trying to modify the contents of the exploded directory before package phase. I was successfully modifying contents of the exploded directories before updating my war plugin. My goal was 1) Creating an exploded directory of the sources. 2) Modifying contents with Replace plugin 3) Creating a war file including modified files To recreate issue, *) mvn clean prepare-package -- This will create as expected file. *) mvn clean package -- This will replace again modified file with old one. Thanks -- 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: (MWAR-249) War plugin doesn't let modify the contents of the exploded directory
[ http://jira.codehaus.org/browse/MWAR-249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=256095#action_256095 ] cem koc commented on MWAR-249: -- But there is a two different behaviour between different versions of the war plugin. For example, this behaviour was different in 2.1-beta-1. If you modify war plugin version of the pom.xml, you can easily see that war plugin does not touch modified files. War plugin doesn't let modify the contents of the exploded directory -- Key: MWAR-249 URL: http://jira.codehaus.org/browse/MWAR-249 Project: Maven 2.x WAR Plugin Issue Type: Bug Affects Versions: 2.1, 2.2 Environment: maven 3 Reporter: cem koc Attachments: Test.zip Shortly I am trying to modify the contents of the exploded directory before package phase. I was successfully modifying contents of the exploded directories before updating my war plugin. My goal was 1) Creating an exploded directory of the sources. 2) Modifying contents with Replace plugin 3) Creating a war file including modified files To recreate issue, *) mvn clean prepare-package -- This will create as expected file. *) mvn clean package -- This will replace again modified file with old one. Thanks -- 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
