[jira] [Commented] (MSHADE-372) Shade plugin dependencies not resolvable from snapshot repository
[
https://issues.apache.org/jira/browse/MSHADE-372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17147211#comment-17147211
]
Michael Heuer commented on MSHADE-372:
--
See e.g.
[https://amplab.cs.berkeley.edu/jenkins/job/cannoli/HADOOP_VERSION=2.7.5,SCALA_VERSION=2.11,SPARK_VERSION=2.4.6,label=ubuntu/lastBuild/console]
[https://amplab.cs.berkeley.edu/jenkins/job/cannoli/HADOOP_VERSION=2.7.5,SCALA_VERSION=2.12,SPARK_VERSION=2.4.6,label=ubuntu/2032/console]
> Shade plugin dependencies not resolvable from snapshot repository
> -
>
> Key: MSHADE-372
> URL: https://issues.apache.org/jira/browse/MSHADE-372
> Project: Maven Shade Plugin
> Issue Type: Bug
>Affects Versions: 3.2.0
>Reporter: Michael Heuer
>Priority: Major
>
> Given
> {code:xml}
>
>
>
> org.apache.maven.plugins
> maven-shade-plugin
>
>
> org.bdgenomics.adam
> adam-shade-spark2_${scala.version.prefix}
> ${adam.version}
>
>
> {code}
> With a snapshot version (e.g. 0.32.0-SNAPSHOT) resolution of this dependency
> appears to be looking in the wrong snapshot repository
> {code}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-shade-plugin:3.2.0:shade (default) on project
> cannoli-assembly-spark2_2.12: Execution default of goal
> org.apache.maven.plugins:maven-shade-plugin:3.2.0:shade failed: Plugin
> org.apache.maven.plugins:maven-shade-plugin:3.2.0 or one of its dependencies
> could not be resolved: Failure to find
> org.bdgenomics.adam:adam-shade-spark2_2.12:jar:0.32.0-SNAPSHOT in
> https://repository.apache.org/snapshots was cached in the local repository,
> resolution will not be reattempted until the update interval of
> apache.snapshots has elapsed or updates are forced -> [Help 1]
> {code}
> org.bdgenomics.adam:adam-shade-spark2_${scala.version.prefix}:0.32.0-SNAPSHOT
> is in fact present in the Sonatype snapshots repository
> https://oss.sonatype.org/content/repositories/snapshots/org/bdgenomics/adam/adam-shade-spark2_2.12/0.32.0-SNAPSHOT/
> This snapshot repository is included in our parent pom via oss-parent
> {code:xml}
>
> org.sonatype.oss
> oss-parent
> 9
>
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Created] (MSHADE-372) Shade plugin dependencies not resolvable from snapshot repository
Michael Heuer created MSHADE-372:
Summary: Shade plugin dependencies not resolvable from snapshot
repository
Key: MSHADE-372
URL: https://issues.apache.org/jira/browse/MSHADE-372
Project: Maven Shade Plugin
Issue Type: Bug
Affects Versions: 3.2.0
Reporter: Michael Heuer
Given
{code:xml}
org.apache.maven.plugins
maven-shade-plugin
org.bdgenomics.adam
adam-shade-spark2_${scala.version.prefix}
${adam.version}
{code}
With a snapshot version (e.g. 0.32.0-SNAPSHOT) resolution of this dependency
appears to be looking in the wrong snapshot repository
{code}
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-shade-plugin:3.2.0:shade (default) on project
cannoli-assembly-spark2_2.12: Execution default of goal
org.apache.maven.plugins:maven-shade-plugin:3.2.0:shade failed: Plugin
org.apache.maven.plugins:maven-shade-plugin:3.2.0 or one of its dependencies
could not be resolved: Failure to find
org.bdgenomics.adam:adam-shade-spark2_2.12:jar:0.32.0-SNAPSHOT in
https://repository.apache.org/snapshots was cached in the local repository,
resolution will not be reattempted until the update interval of
apache.snapshots has elapsed or updates are forced -> [Help 1]
{code}
org.bdgenomics.adam:adam-shade-spark2_${scala.version.prefix}:0.32.0-SNAPSHOT
is in fact present in the Sonatype snapshots repository
https://oss.sonatype.org/content/repositories/snapshots/org/bdgenomics/adam/adam-shade-spark2_2.12/0.32.0-SNAPSHOT/
This snapshot repository is included in our parent pom via oss-parent
{code:xml}
org.sonatype.oss
oss-parent
9
{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] (MASSEMBLY-728) Assembly plugin = 2.5 thinks my group ID is too big
[ https://jira.codehaus.org/browse/MASSEMBLY-728?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=356088#comment-356088 ] Michael Heuer commented on MASSEMBLY-728: - @krosenvold, I see the text you added in the faq entry, but it doesn't say where to set tarLongFileMode=posix. Is that a plugin configuration parameter or something that goes in the assembly descriptor? Assembly plugin = 2.5 thinks my group ID is too big Key: MASSEMBLY-728 URL: https://jira.codehaus.org/browse/MASSEMBLY-728 Project: Maven Assembly Plugin Issue Type: Bug Affects Versions: 2.5 Reporter: Andrew Todd Assignee: Kristian Rosenvold Fix For: 2.5.2 My OS X user's primary group ID is quite large, around 110075129. Up until assembly 2.4.1, I have had no troubles. However, in 2.5, I get this error when trying to create an assembly: [ERROR] Failed to execute goal org.apache.maven.plugins:maven-assembly-plugin:2.5:single (assemble-command-line) on project crypto-monster: Execution assemble-command-line of goal org.apache.maven.plugins:maven-assembly-plugin:2.5:single failed: group id '110075129' is too big ( 2097151 ) - [Help 1] I am using JDK 7 to build. Have not tested with 8. I have noticed that the error seems to be specific to assembly of a .tar.gz artifact. Assembling a .zip file does not cause this error. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MDEPLOY-177) Maven release:perform hangs when downloading maven-metadata.xml
[
https://jira.codehaus.org/browse/MDEPLOY-177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=354697#comment-354697
]
Michael Heuer commented on MDEPLOY-177:
---
Hello Robert,
Unfortunately I am no longer able to reproduce the issue since we now release
to Maven Central via Sonatype OSS Nexus, which doesn't use scp for the deploy
step.
http://tinyurl.com/pjo52mp
(link to
http://search.maven.org/#search|gav|1|g%3A%22org.biojava%22%20AND%20a%3A%22biojava-legacy%22,
which Jira doesn't handle)
Maven release:perform hangs when downloading maven-metadata.xml
---
Key: MDEPLOY-177
URL: https://jira.codehaus.org/browse/MDEPLOY-177
Project: Maven Deploy Plugin
Issue Type: Bug
Components: deploy:deploy
Affects Versions: 2.8.1
Environment: $ mvn -v
Apache Maven 3.2.1 (ea8b2b07643dbb1b84b6d16e1f08391b666bc1e9;
2014-02-14T11:37:52-06:00)
Maven home: /usr/local/Cellar/maven/3.2.1/libexec
Java version: 1.7.0_51, vendor: Oracle Corporation
Java home: /Library/Java/JavaVirtualMachines/jdk1.7.0_51.jdk/Contents/Home/jre
Default locale: en_US, platform encoding: UTF-8
OS name: mac os x, version: 10.9.2, arch: x86_64, family: mac
Reporter: Michael Heuer
Priority: Critical
Attachments: deploy-debug.txt, release-perform-3.0.5.txt,
release-perform-debug.txt
When attempting to mvn release:perform
{code:none}
$ mvn release:perform
...
[INFO] [INFO]
[INFO] [INFO] Building biojava-legacy 1.8.5
[INFO] [INFO]
[INFO] [INFO]
[INFO] [INFO] maven-source-plugin:2.2.1:jar (attach-sources) @
biojava-legacy
[INFO] [INFO]
[INFO] [INFO] maven-source-plugin:2.2.1:jar (attach-sources) @
biojava-legacy
[INFO] [INFO]
[INFO] [INFO] --- maven-source-plugin:2.2.1:jar (attach-sources) @
biojava-legacy ---
[INFO] [INFO]
[INFO] [INFO] --- maven-javadoc-plugin:2.9.1:jar (attach-javadocs) @
biojava-legacy ---
[INFO] [INFO] Not executing Javadoc as the project is not a Java
classpath-capable package
[INFO] [INFO]
[INFO] [INFO] --- maven-install-plugin:2.4:install (default-install) @
biojava-legacy ---
[INFO] [INFO] Installing
/Users/xxx/working/biojava-legacy/target/checkout/pom.xml to
/Users/xxx/.m2/repository/org/biojava/biojava-legacy/1.8.5/biojava-legacy-1.8.5.pom
[INFO] [INFO]
[INFO] [INFO] --- maven-deploy-plugin:2.8.1:deploy (default-deploy) @
biojava-legacy ---
[INFO] Uploading:
scp://cloudportal.open-bio.org/home/websites/biojava.org/html/static/download/maven/org/biojava/biojava-legacy/1.8.5/biojava-legacy-1.8.5.pom
[INFO] 4/9 KB
[INFO] 8/9 KB
[INFO] 9/9 KB
[INFO]
[INFO] Uploaded:
scp://cloudportal.open-bio.org/home/websites/biojava.org/html/static/download/maven/org/biojava/biojava-legacy/1.8.5/biojava-legacy-1.8.5.pom
(9 KB at 3.0 KB/sec)
[INFO] Downloading:
scp://cloudportal.open-bio.org/home/websites/biojava.org/html/static/download/maven/org/biojava/biojava-legacy/maven-metadata.xml
[INFO] 750/750 B
[INFO] 751/750 B
{code}
the build hangs at this point. It appears there might be a difference
between the expected file size and the downloaded file size, but no
warning/error messages appear, the build just hangs.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (SUREFIRE-948) Module with unit test failure does not match reactor summary
[ https://jira.codehaus.org/browse/SUREFIRE-948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=354408#comment-354408 ] Michael Heuer commented on SUREFIRE-948: @Tibor The upstream issue linked above was closed as not able to reproduce. We've since moved on to version 2.17 and have not seen this occur again. You may close this as WontFix or Invalid; thanks for checking up on it. Module with unit test failure does not match reactor summary Key: SUREFIRE-948 URL: https://jira.codehaus.org/browse/SUREFIRE-948 Project: Maven Surefire Issue Type: Bug Components: Maven Surefire Plugin Affects Versions: 2.13 Reporter: Michael Heuer Assignee: Tibor Digana Priority: Critical Since moving from 2.12.4 to 2.13 we have started to notice an occasional mismatch between a module with a unit test failure and the failed module reactor summary. $ mvn install ... [INFO] [INFO] Forking gl-oauth-apache 1.0-SNAPSHOT [INFO] ... [INFO] --- maven-surefire-plugin:2.13:test (default-test) @ gl-oauth-apache --- [INFO] Surefire report directory: /Users/xxx/working/genotype-list-trunk/gl-oauth-group/gl-oauth-apache/target/surefire-reports ... Failed tests: AccessTokenDetailsTest.testTokenValidateResponse:41-checkToAndFromString:51 expected:12344 but was:12345 Tests run: 7, Failures: 1, Errors: 0, Skipped: 0 [INFO] [INFO] Reactor Summary: [INFO] [INFO] gl-service-spark .. SUCCESS [5.579s] [INFO] gl-service-explorer ... SUCCESS [0.648s] [INFO] gl-service-webapp . SUCCESS [1.300s] [INFO] gl-service-webroot SUCCESS [0.357s] [INFO] gl-service-functional-tests ... SUCCESS [17.700s] [INFO] gl-service-performance-tests .. SUCCESS [0.738s] [INFO] gl-client . SUCCESS [1:02.566s] [INFO] gl-client-functional-tests SUCCESS [15.716s] [INFO] gl-tools .. FAILURE [6.031s] [INFO] gl-web SKIPPED [INFO] gl-oauth-group SKIPPED [INFO] gl-oauth-apache ... SKIPPED [INFO] toy-portal SKIPPED [INFO] toy-rest-app .. SKIPPED [INFO] glsw-oauth SKIPPED [INFO] gl-jetty .. SKIPPED [INFO] [INFO] BUILD FAILURE [INFO] ... [INFO] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.13:test (default-test) on project gl-oauth-apache: There are test failures. We have logged an issue here http://code.google.com/p/genotype-list/issues/detail?id=70 and will be working on replicating the issue in a test case project. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MCHECKSTYLE-252) Version 2.13 includes non-source files in checks
[ https://jira.codehaus.org/browse/MCHECKSTYLE-252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=354372#comment-354372 ] Michael Heuer commented on MCHECKSTYLE-252: --- I first noticed it here https://svn.code.sf.net/p/dishevelled/code/trunk/worm-plot-cytoscape3-app/ with parent pom here https://svn.code.sf.net/p/dishevelled/code/trunk/parent/ I don't imagine it would be too difficult to come up with an empty test case; I'll see if I can do that this afternoon. Version 2.13 includes non-source files in checks Key: MCHECKSTYLE-252 URL: https://jira.codehaus.org/browse/MCHECKSTYLE-252 Project: Maven Checkstyle Plugin Issue Type: Bug Affects Versions: 2.13 Reporter: Michael Heuer Updating maven-checkstyle-plugin to version 2.13 and running $ mvn site now includes non-source files in its checks, e.g. COPYING COPYING.LESSER target/generated-classes/cobertura/cobertura.properties While it is rather amusing to have checkstyle complain that COPYING (the text of the GNU General Public License) doesn't include a license header, it seems that the default source root or one of the other properties new to version 2.13 does not have an appropriate default value. The target directory should also be excluded by default. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MCHECKSTYLE-252) Version 2.13 includes non-source files in checks
[ https://jira.codehaus.org/browse/MCHECKSTYLE-252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Heuer updated MCHECKSTYLE-252: -- Attachment: mcheckstyle-252.tar.gz Test case extracted from code on dishevelled.org. Version 2.13 includes non-source files in checks Key: MCHECKSTYLE-252 URL: https://jira.codehaus.org/browse/MCHECKSTYLE-252 Project: Maven Checkstyle Plugin Issue Type: Bug Affects Versions: 2.13 Reporter: Michael Heuer Attachments: mcheckstyle-252.tar.gz Updating maven-checkstyle-plugin to version 2.13 and running $ mvn site now includes non-source files in its checks, e.g. COPYING COPYING.LESSER target/generated-classes/cobertura/cobertura.properties While it is rather amusing to have checkstyle complain that COPYING (the text of the GNU General Public License) doesn't include a license header, it seems that the default source root or one of the other properties new to version 2.13 does not have an appropriate default value. The target directory should also be excluded by default. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MCHECKSTYLE-252) Version 2.13 includes non-source files in checks
Michael Heuer created MCHECKSTYLE-252: - Summary: Version 2.13 includes non-source files in checks Key: MCHECKSTYLE-252 URL: https://jira.codehaus.org/browse/MCHECKSTYLE-252 Project: Maven Checkstyle Plugin Issue Type: Bug Affects Versions: 2.13 Reporter: Michael Heuer Updating maven-checkstyle-plugin to version 2.13 and running $ mvn site now includes non-source files in its checks, e.g. COPYING COPYING.LESSER target/generated-classes/cobertura/cobertura.properties While it is rather amusing to have checkstyle complain that COPYING (the text of the GNU General Public License) doesn't include a license header, it seems that the default source root or one of the other properties new to version 2.13 does not have an appropriate default value. The target directory should also be excluded by default. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MCHECKSTYLE-252) Version 2.13 includes non-source files in checks
[ https://jira.codehaus.org/browse/MCHECKSTYLE-252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=354322#comment-354322 ] Michael Heuer commented on MCHECKSTYLE-252: --- Looks like the relevant change is this commit http://svn.apache.org/viewvc/maven/plugins/tags/maven-checkstyle-plugin-2.13/src/main/java/org/apache/maven/plugin/checkstyle/CheckstyleViolationCheckMojo.java?r1=1618904r2=1618905; Version 2.13 includes non-source files in checks Key: MCHECKSTYLE-252 URL: https://jira.codehaus.org/browse/MCHECKSTYLE-252 Project: Maven Checkstyle Plugin Issue Type: Bug Affects Versions: 2.13 Reporter: Michael Heuer Updating maven-checkstyle-plugin to version 2.13 and running $ mvn site now includes non-source files in its checks, e.g. COPYING COPYING.LESSER target/generated-classes/cobertura/cobertura.properties While it is rather amusing to have checkstyle complain that COPYING (the text of the GNU General Public License) doesn't include a license header, it seems that the default source root or one of the other properties new to version 2.13 does not have an appropriate default value. The target directory should also be excluded by default. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MCHECKSTYLE-252) Version 2.13 includes non-source files in checks
[ https://jira.codehaus.org/browse/MCHECKSTYLE-252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=354322#comment-354322 ] Michael Heuer edited comment on MCHECKSTYLE-252 at 10/13/14 10:19 PM: -- Looks like the relevant change may be this commit http://svn.apache.org/viewvc/maven/plugins/tags/maven-checkstyle-plugin-2.13/src/main/java/org/apache/maven/plugin/checkstyle/CheckstyleViolationCheckMojo.java?r1=1618904r2=1618905; and similar in the reporting classes. was (Author: heuermh): Looks like the relevant change is this commit http://svn.apache.org/viewvc/maven/plugins/tags/maven-checkstyle-plugin-2.13/src/main/java/org/apache/maven/plugin/checkstyle/CheckstyleViolationCheckMojo.java?r1=1618904r2=1618905; Version 2.13 includes non-source files in checks Key: MCHECKSTYLE-252 URL: https://jira.codehaus.org/browse/MCHECKSTYLE-252 Project: Maven Checkstyle Plugin Issue Type: Bug Affects Versions: 2.13 Reporter: Michael Heuer Updating maven-checkstyle-plugin to version 2.13 and running $ mvn site now includes non-source files in its checks, e.g. COPYING COPYING.LESSER target/generated-classes/cobertura/cobertura.properties While it is rather amusing to have checkstyle complain that COPYING (the text of the GNU General Public License) doesn't include a license header, it seems that the default source root or one of the other properties new to version 2.13 does not have an appropriate default value. The target directory should also be excluded by default. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MDEPLOY-177) Maven release:perform hangs when downloading maven-metadata.xml
[
https://jira.codehaus.org/browse/MDEPLOY-177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Heuer updated MDEPLOY-177:
--
Comment: was deleted
(was: release:perform fails with maven 3.2.1, succeeds with maven 3.0.5)
Maven release:perform hangs when downloading maven-metadata.xml
---
Key: MDEPLOY-177
URL: https://jira.codehaus.org/browse/MDEPLOY-177
Project: Maven Deploy Plugin
Issue Type: Bug
Components: deploy:deploy
Affects Versions: 2.8.1
Environment: $ mvn -v
Apache Maven 3.2.1 (ea8b2b07643dbb1b84b6d16e1f08391b666bc1e9;
2014-02-14T11:37:52-06:00)
Maven home: /usr/local/Cellar/maven/3.2.1/libexec
Java version: 1.7.0_51, vendor: Oracle Corporation
Java home: /Library/Java/JavaVirtualMachines/jdk1.7.0_51.jdk/Contents/Home/jre
Default locale: en_US, platform encoding: UTF-8
OS name: mac os x, version: 10.9.2, arch: x86_64, family: mac
Reporter: Michael Heuer
Priority: Critical
Attachments: deploy-debug.txt, release-perform-3.0.5.txt,
release-perform-debug.txt
When attempting to mvn release:perform
{code:none}
$ mvn release:perform
...
[INFO] [INFO]
[INFO] [INFO] Building biojava-legacy 1.8.5
[INFO] [INFO]
[INFO] [INFO]
[INFO] [INFO] maven-source-plugin:2.2.1:jar (attach-sources) @
biojava-legacy
[INFO] [INFO]
[INFO] [INFO] maven-source-plugin:2.2.1:jar (attach-sources) @
biojava-legacy
[INFO] [INFO]
[INFO] [INFO] --- maven-source-plugin:2.2.1:jar (attach-sources) @
biojava-legacy ---
[INFO] [INFO]
[INFO] [INFO] --- maven-javadoc-plugin:2.9.1:jar (attach-javadocs) @
biojava-legacy ---
[INFO] [INFO] Not executing Javadoc as the project is not a Java
classpath-capable package
[INFO] [INFO]
[INFO] [INFO] --- maven-install-plugin:2.4:install (default-install) @
biojava-legacy ---
[INFO] [INFO] Installing
/Users/xxx/working/biojava-legacy/target/checkout/pom.xml to
/Users/xxx/.m2/repository/org/biojava/biojava-legacy/1.8.5/biojava-legacy-1.8.5.pom
[INFO] [INFO]
[INFO] [INFO] --- maven-deploy-plugin:2.8.1:deploy (default-deploy) @
biojava-legacy ---
[INFO] Uploading:
scp://cloudportal.open-bio.org/home/websites/biojava.org/html/static/download/maven/org/biojava/biojava-legacy/1.8.5/biojava-legacy-1.8.5.pom
[INFO] 4/9 KB
[INFO] 8/9 KB
[INFO] 9/9 KB
[INFO]
[INFO] Uploaded:
scp://cloudportal.open-bio.org/home/websites/biojava.org/html/static/download/maven/org/biojava/biojava-legacy/1.8.5/biojava-legacy-1.8.5.pom
(9 KB at 3.0 KB/sec)
[INFO] Downloading:
scp://cloudportal.open-bio.org/home/websites/biojava.org/html/static/download/maven/org/biojava/biojava-legacy/maven-metadata.xml
[INFO] 750/750 B
[INFO] 751/750 B
{code}
the build hangs at this point. It appears there might be a difference
between the expected file size and the downloaded file size, but no
warning/error messages appear, the build just hangs.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MDEPLOY-177) Maven release:perform hangs when downloading maven-metadata.xml
[
https://jira.codehaus.org/browse/MDEPLOY-177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=344061#comment-344061
]
Michael Heuer commented on MDEPLOY-177:
---
It turns out the successful biojava version 3.0.8 release was performed with
maven version 3.0.4.
I tried the biojava-legacy 1.8.5 release with maven version 3.0.5 and was also
successful (see attached release-perform-3.0.5.txt).
This identifies a regression, although if that is in maven proper, or wagon, or
wagon-ssh, or release, or deploy I cannot say. I would appreciate advice on
what to do next with this issue. Thank you.
Maven release:perform hangs when downloading maven-metadata.xml
---
Key: MDEPLOY-177
URL: https://jira.codehaus.org/browse/MDEPLOY-177
Project: Maven Deploy Plugin
Issue Type: Bug
Components: deploy:deploy
Affects Versions: 2.8.1
Environment: $ mvn -v
Apache Maven 3.2.1 (ea8b2b07643dbb1b84b6d16e1f08391b666bc1e9;
2014-02-14T11:37:52-06:00)
Maven home: /usr/local/Cellar/maven/3.2.1/libexec
Java version: 1.7.0_51, vendor: Oracle Corporation
Java home: /Library/Java/JavaVirtualMachines/jdk1.7.0_51.jdk/Contents/Home/jre
Default locale: en_US, platform encoding: UTF-8
OS name: mac os x, version: 10.9.2, arch: x86_64, family: mac
Reporter: Michael Heuer
Priority: Critical
Attachments: deploy-debug.txt, release-perform-debug.txt
When attempting to mvn release:perform
{code:none}
$ mvn release:perform
...
[INFO] [INFO]
[INFO] [INFO] Building biojava-legacy 1.8.5
[INFO] [INFO]
[INFO] [INFO]
[INFO] [INFO] maven-source-plugin:2.2.1:jar (attach-sources) @
biojava-legacy
[INFO] [INFO]
[INFO] [INFO] maven-source-plugin:2.2.1:jar (attach-sources) @
biojava-legacy
[INFO] [INFO]
[INFO] [INFO] --- maven-source-plugin:2.2.1:jar (attach-sources) @
biojava-legacy ---
[INFO] [INFO]
[INFO] [INFO] --- maven-javadoc-plugin:2.9.1:jar (attach-javadocs) @
biojava-legacy ---
[INFO] [INFO] Not executing Javadoc as the project is not a Java
classpath-capable package
[INFO] [INFO]
[INFO] [INFO] --- maven-install-plugin:2.4:install (default-install) @
biojava-legacy ---
[INFO] [INFO] Installing
/Users/xxx/working/biojava-legacy/target/checkout/pom.xml to
/Users/xxx/.m2/repository/org/biojava/biojava-legacy/1.8.5/biojava-legacy-1.8.5.pom
[INFO] [INFO]
[INFO] [INFO] --- maven-deploy-plugin:2.8.1:deploy (default-deploy) @
biojava-legacy ---
[INFO] Uploading:
scp://cloudportal.open-bio.org/home/websites/biojava.org/html/static/download/maven/org/biojava/biojava-legacy/1.8.5/biojava-legacy-1.8.5.pom
[INFO] 4/9 KB
[INFO] 8/9 KB
[INFO] 9/9 KB
[INFO]
[INFO] Uploaded:
scp://cloudportal.open-bio.org/home/websites/biojava.org/html/static/download/maven/org/biojava/biojava-legacy/1.8.5/biojava-legacy-1.8.5.pom
(9 KB at 3.0 KB/sec)
[INFO] Downloading:
scp://cloudportal.open-bio.org/home/websites/biojava.org/html/static/download/maven/org/biojava/biojava-legacy/maven-metadata.xml
[INFO] 750/750 B
[INFO] 751/750 B
{code}
the build hangs at this point. It appears there might be a difference
between the expected file size and the downloaded file size, but no
warning/error messages appear, the build just hangs.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MDEPLOY-177) Maven release:perform hangs when downloading maven-metadata.xml
[
https://jira.codehaus.org/browse/MDEPLOY-177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Heuer updated MDEPLOY-177:
--
Attachment: release-perform-3.0.5.txt
release:perform fails with maven 3.2.1, succeeds with maven 3.0.5
Maven release:perform hangs when downloading maven-metadata.xml
---
Key: MDEPLOY-177
URL: https://jira.codehaus.org/browse/MDEPLOY-177
Project: Maven Deploy Plugin
Issue Type: Bug
Components: deploy:deploy
Affects Versions: 2.8.1
Environment: $ mvn -v
Apache Maven 3.2.1 (ea8b2b07643dbb1b84b6d16e1f08391b666bc1e9;
2014-02-14T11:37:52-06:00)
Maven home: /usr/local/Cellar/maven/3.2.1/libexec
Java version: 1.7.0_51, vendor: Oracle Corporation
Java home: /Library/Java/JavaVirtualMachines/jdk1.7.0_51.jdk/Contents/Home/jre
Default locale: en_US, platform encoding: UTF-8
OS name: mac os x, version: 10.9.2, arch: x86_64, family: mac
Reporter: Michael Heuer
Priority: Critical
Attachments: deploy-debug.txt, release-perform-3.0.5.txt,
release-perform-debug.txt
When attempting to mvn release:perform
{code:none}
$ mvn release:perform
...
[INFO] [INFO]
[INFO] [INFO] Building biojava-legacy 1.8.5
[INFO] [INFO]
[INFO] [INFO]
[INFO] [INFO] maven-source-plugin:2.2.1:jar (attach-sources) @
biojava-legacy
[INFO] [INFO]
[INFO] [INFO] maven-source-plugin:2.2.1:jar (attach-sources) @
biojava-legacy
[INFO] [INFO]
[INFO] [INFO] --- maven-source-plugin:2.2.1:jar (attach-sources) @
biojava-legacy ---
[INFO] [INFO]
[INFO] [INFO] --- maven-javadoc-plugin:2.9.1:jar (attach-javadocs) @
biojava-legacy ---
[INFO] [INFO] Not executing Javadoc as the project is not a Java
classpath-capable package
[INFO] [INFO]
[INFO] [INFO] --- maven-install-plugin:2.4:install (default-install) @
biojava-legacy ---
[INFO] [INFO] Installing
/Users/xxx/working/biojava-legacy/target/checkout/pom.xml to
/Users/xxx/.m2/repository/org/biojava/biojava-legacy/1.8.5/biojava-legacy-1.8.5.pom
[INFO] [INFO]
[INFO] [INFO] --- maven-deploy-plugin:2.8.1:deploy (default-deploy) @
biojava-legacy ---
[INFO] Uploading:
scp://cloudportal.open-bio.org/home/websites/biojava.org/html/static/download/maven/org/biojava/biojava-legacy/1.8.5/biojava-legacy-1.8.5.pom
[INFO] 4/9 KB
[INFO] 8/9 KB
[INFO] 9/9 KB
[INFO]
[INFO] Uploaded:
scp://cloudportal.open-bio.org/home/websites/biojava.org/html/static/download/maven/org/biojava/biojava-legacy/1.8.5/biojava-legacy-1.8.5.pom
(9 KB at 3.0 KB/sec)
[INFO] Downloading:
scp://cloudportal.open-bio.org/home/websites/biojava.org/html/static/download/maven/org/biojava/biojava-legacy/maven-metadata.xml
[INFO] 750/750 B
[INFO] 751/750 B
{code}
the build hangs at this point. It appears there might be a difference
between the expected file size and the downloaded file size, but no
warning/error messages appear, the build just hangs.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MDEPLOY-177) Maven release:perform hangs when downloading maven-metadata.xml
[
https://jira.codehaus.org/browse/MDEPLOY-177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=343966#comment-343966
]
Michael Heuer commented on MDEPLOY-177:
---
The 1.8.5 release has a dependency on wagon-ssh version 2.6
{code:xml}
extensions
extension
groupIdorg.apache.maven.wagon/groupId
artifactIdwagon-ssh/artifactId
version2.6/version
/extension
/extensions
{code}
I tried deploying 1.8.6-SNAPSHOT with versions 2.5 and 2.4 with the same result
{code:none}
$ mvn -e -X deploy --debug
...
[DEBUG] Using connector WagonRepositoryConnector with priority 0.0 for
scp://cloudportal.open-bio.org/home/websites/biojava.org/html/static/download/maven/
with username=mheuer
Downloading:
scp://cloudportal.open-bio.org/home/websites/biojava.org/html/static/download/maven/org/biojava/biojava-legacy/1.8.6-SNAPSHOT/maven-metadata.xml
603/602 B
{code}
Another developer was able to cut a release (version 3.0.8) from a different
codebase to the same maven repository recently, see e.g.
https://github.com/biojava/biojava/releases
http://biojava.org/download/maven/org/biojava/biojava/maven-metadata.xml
http://biojava.org/download/maven/org/biojava/biojava/3.0.8/biojava-3.0.8.pom
The pom files are kept in sync as much as possible (whitespace formatting aside)
https://github.com/biojava/biojava/blob/master/pom.xml
https://github.com/biojava/biojava-legacy/blob/master/pom.xml
Maven release:perform hangs when downloading maven-metadata.xml
---
Key: MDEPLOY-177
URL: https://jira.codehaus.org/browse/MDEPLOY-177
Project: Maven Deploy Plugin
Issue Type: Bug
Components: deploy:deploy
Affects Versions: 2.8.1
Environment: $ mvn -v
Apache Maven 3.2.1 (ea8b2b07643dbb1b84b6d16e1f08391b666bc1e9;
2014-02-14T11:37:52-06:00)
Maven home: /usr/local/Cellar/maven/3.2.1/libexec
Java version: 1.7.0_51, vendor: Oracle Corporation
Java home: /Library/Java/JavaVirtualMachines/jdk1.7.0_51.jdk/Contents/Home/jre
Default locale: en_US, platform encoding: UTF-8
OS name: mac os x, version: 10.9.2, arch: x86_64, family: mac
Reporter: Michael Heuer
Priority: Critical
Attachments: deploy-debug.txt, release-perform-debug.txt
When attempting to mvn release:perform
{code:none}
$ mvn release:perform
...
[INFO] [INFO]
[INFO] [INFO] Building biojava-legacy 1.8.5
[INFO] [INFO]
[INFO] [INFO]
[INFO] [INFO] maven-source-plugin:2.2.1:jar (attach-sources) @
biojava-legacy
[INFO] [INFO]
[INFO] [INFO] maven-source-plugin:2.2.1:jar (attach-sources) @
biojava-legacy
[INFO] [INFO]
[INFO] [INFO] --- maven-source-plugin:2.2.1:jar (attach-sources) @
biojava-legacy ---
[INFO] [INFO]
[INFO] [INFO] --- maven-javadoc-plugin:2.9.1:jar (attach-javadocs) @
biojava-legacy ---
[INFO] [INFO] Not executing Javadoc as the project is not a Java
classpath-capable package
[INFO] [INFO]
[INFO] [INFO] --- maven-install-plugin:2.4:install (default-install) @
biojava-legacy ---
[INFO] [INFO] Installing
/Users/xxx/working/biojava-legacy/target/checkout/pom.xml to
/Users/xxx/.m2/repository/org/biojava/biojava-legacy/1.8.5/biojava-legacy-1.8.5.pom
[INFO] [INFO]
[INFO] [INFO] --- maven-deploy-plugin:2.8.1:deploy (default-deploy) @
biojava-legacy ---
[INFO] Uploading:
scp://cloudportal.open-bio.org/home/websites/biojava.org/html/static/download/maven/org/biojava/biojava-legacy/1.8.5/biojava-legacy-1.8.5.pom
[INFO] 4/9 KB
[INFO] 8/9 KB
[INFO] 9/9 KB
[INFO]
[INFO] Uploaded:
scp://cloudportal.open-bio.org/home/websites/biojava.org/html/static/download/maven/org/biojava/biojava-legacy/1.8.5/biojava-legacy-1.8.5.pom
(9 KB at 3.0 KB/sec)
[INFO] Downloading:
scp://cloudportal.open-bio.org/home/websites/biojava.org/html/static/download/maven/org/biojava/biojava-legacy/maven-metadata.xml
[INFO] 750/750 B
[INFO] 751/750 B
{code}
the build hangs at this point. It appears there might be a difference
between the expected file size and the downloaded file size, but no
warning/error messages appear, the build just hangs.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MDEPLOY-177) Maven release:perform hangs when downloading maven-metadata.xml
Michael Heuer created MDEPLOY-177: - Summary: Maven release:perform hangs when downloading maven-metadata.xml Key: MDEPLOY-177 URL: https://jira.codehaus.org/browse/MDEPLOY-177 Project: Maven Deploy Plugin Issue Type: Bug Components: deploy:deploy Affects Versions: 2.8.1 Environment: $ mvn -v Apache Maven 3.2.1 (ea8b2b07643dbb1b84b6d16e1f08391b666bc1e9; 2014-02-14T11:37:52-06:00) Maven home: /usr/local/Cellar/maven/3.2.1/libexec Java version: 1.7.0_51, vendor: Oracle Corporation Java home: /Library/Java/JavaVirtualMachines/jdk1.7.0_51.jdk/Contents/Home/jre Default locale: en_US, platform encoding: UTF-8 OS name: mac os x, version: 10.9.2, arch: x86_64, family: mac Reporter: Michael Heuer Priority: Critical When attempting to mvn release:perform $ mvn release:perform ... [INFO] [INFO] [INFO] [INFO] Building biojava-legacy 1.8.5 [INFO] [INFO] [INFO] [INFO] [INFO] [INFO] maven-source-plugin:2.2.1:jar (attach-sources) @ biojava-legacy [INFO] [INFO] [INFO] [INFO] maven-source-plugin:2.2.1:jar (attach-sources) @ biojava-legacy [INFO] [INFO] [INFO] [INFO] --- maven-source-plugin:2.2.1:jar (attach-sources) @ biojava-legacy --- [INFO] [INFO] [INFO] [INFO] --- maven-javadoc-plugin:2.9.1:jar (attach-javadocs) @ biojava-legacy --- [INFO] [INFO] Not executing Javadoc as the project is not a Java classpath-capable package [INFO] [INFO] [INFO] [INFO] --- maven-install-plugin:2.4:install (default-install) @ biojava-legacy --- [INFO] [INFO] Installing /Users/xxx/working/biojava-legacy/target/checkout/pom.xml to /Users/xxx/.m2/repository/org/biojava/biojava-legacy/1.8.5/biojava-legacy-1.8.5.pom [INFO] [INFO] [INFO] [INFO] --- maven-deploy-plugin:2.8.1:deploy (default-deploy) @ biojava-legacy --- [INFO] Uploading: scp://cloudportal.open-bio.org/home/websites/biojava.org/html/static/download/maven/org/biojava/biojava-legacy/1.8.5/biojava-legacy-1.8.5.pom [INFO] 4/9 KB [INFO] 8/9 KB [INFO] 9/9 KB [INFO] [INFO] Uploaded: scp://cloudportal.open-bio.org/home/websites/biojava.org/html/static/download/maven/org/biojava/biojava-legacy/1.8.5/biojava-legacy-1.8.5.pom (9 KB at 3.0 KB/sec) [INFO] Downloading: scp://cloudportal.open-bio.org/home/websites/biojava.org/html/static/download/maven/org/biojava/biojava-legacy/maven-metadata.xml [INFO] 750/750 B [INFO] 751/750 B the build hangs at this point. It appears there might be a difference between the expected file size and the downloaded file size, but no warning/error messages appear, the build just hangs. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MDEPLOY-177) Maven release:perform hangs when downloading maven-metadata.xml
[
https://jira.codehaus.org/browse/MDEPLOY-177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Heuer updated MDEPLOY-177:
--
Description:
When attempting to mvn release:perform
{code:none}
$ mvn release:perform
...
[INFO] [INFO]
[INFO] [INFO] Building biojava-legacy 1.8.5
[INFO] [INFO]
[INFO] [INFO]
[INFO] [INFO] maven-source-plugin:2.2.1:jar (attach-sources) @
biojava-legacy
[INFO] [INFO]
[INFO] [INFO] maven-source-plugin:2.2.1:jar (attach-sources) @
biojava-legacy
[INFO] [INFO]
[INFO] [INFO] --- maven-source-plugin:2.2.1:jar (attach-sources) @
biojava-legacy ---
[INFO] [INFO]
[INFO] [INFO] --- maven-javadoc-plugin:2.9.1:jar (attach-javadocs) @
biojava-legacy ---
[INFO] [INFO] Not executing Javadoc as the project is not a Java
classpath-capable package
[INFO] [INFO]
[INFO] [INFO] --- maven-install-plugin:2.4:install (default-install) @
biojava-legacy ---
[INFO] [INFO] Installing
/Users/xxx/working/biojava-legacy/target/checkout/pom.xml to
/Users/xxx/.m2/repository/org/biojava/biojava-legacy/1.8.5/biojava-legacy-1.8.5.pom
[INFO] [INFO]
[INFO] [INFO] --- maven-deploy-plugin:2.8.1:deploy (default-deploy) @
biojava-legacy ---
[INFO] Uploading:
scp://cloudportal.open-bio.org/home/websites/biojava.org/html/static/download/maven/org/biojava/biojava-legacy/1.8.5/biojava-legacy-1.8.5.pom
[INFO] 4/9 KB
[INFO] 8/9 KB
[INFO] 9/9 KB
[INFO]
[INFO] Uploaded:
scp://cloudportal.open-bio.org/home/websites/biojava.org/html/static/download/maven/org/biojava/biojava-legacy/1.8.5/biojava-legacy-1.8.5.pom
(9 KB at 3.0 KB/sec)
[INFO] Downloading:
scp://cloudportal.open-bio.org/home/websites/biojava.org/html/static/download/maven/org/biojava/biojava-legacy/maven-metadata.xml
[INFO] 750/750 B
[INFO] 751/750 B
{code}
the build hangs at this point. It appears there might be a difference between
the expected file size and the downloaded file size, but no warning/error
messages appear, the build just hangs.
was:
When attempting to mvn release:perform
$ mvn release:perform
...
[INFO] [INFO]
[INFO] [INFO] Building biojava-legacy 1.8.5
[INFO] [INFO]
[INFO] [INFO]
[INFO] [INFO] maven-source-plugin:2.2.1:jar (attach-sources) @
biojava-legacy
[INFO] [INFO]
[INFO] [INFO] maven-source-plugin:2.2.1:jar (attach-sources) @
biojava-legacy
[INFO] [INFO]
[INFO] [INFO] --- maven-source-plugin:2.2.1:jar (attach-sources) @
biojava-legacy ---
[INFO] [INFO]
[INFO] [INFO] --- maven-javadoc-plugin:2.9.1:jar (attach-javadocs) @
biojava-legacy ---
[INFO] [INFO] Not executing Javadoc as the project is not a Java
classpath-capable package
[INFO] [INFO]
[INFO] [INFO] --- maven-install-plugin:2.4:install (default-install) @
biojava-legacy ---
[INFO] [INFO] Installing
/Users/xxx/working/biojava-legacy/target/checkout/pom.xml to
/Users/xxx/.m2/repository/org/biojava/biojava-legacy/1.8.5/biojava-legacy-1.8.5.pom
[INFO] [INFO]
[INFO] [INFO] --- maven-deploy-plugin:2.8.1:deploy (default-deploy) @
biojava-legacy ---
[INFO] Uploading:
scp://cloudportal.open-bio.org/home/websites/biojava.org/html/static/download/maven/org/biojava/biojava-legacy/1.8.5/biojava-legacy-1.8.5.pom
[INFO] 4/9 KB
[INFO] 8/9 KB
[INFO] 9/9 KB
[INFO]
[INFO] Uploaded:
scp://cloudportal.open-bio.org/home/websites/biojava.org/html/static/download/maven/org/biojava/biojava-legacy/1.8.5/biojava-legacy-1.8.5.pom
(9 KB at 3.0 KB/sec)
[INFO] Downloading:
scp://cloudportal.open-bio.org/home/websites/biojava.org/html/static/download/maven/org/biojava/biojava-legacy/maven-metadata.xml
[INFO] 750/750 B
[INFO] 751/750 B
the build hangs at this point. It appears there might be a difference between
the expected file size and the downloaded file size, but no warning/error
messages appear, the build just hangs.
Maven release:perform hangs when downloading maven-metadata.xml
---
Key: MDEPLOY-177
URL: https://jira.codehaus.org/browse/MDEPLOY-177
Project: Maven Deploy Plugin
Issue Type: Bug
Components: deploy:deploy
Affects Versions: 2.8.1
Environment: $ mvn -v
Apache Maven 3.2.1 (ea8b2b07643dbb1b84b6d16e1f08391b666bc1e9;
2014-02-14T11:37:52-06:00)
Maven home: /usr/local/Cellar/maven/3.2.1/libexec
Java version: 1.7.0_51, vendor: Oracle Corporation
Java home: /Library/Java/JavaVirtualMachines/jdk1.7.0_51.jdk/Contents/Home/jre
Default locale: en_US, platform encoding: UTF-8
OS name: mac os x, version: 10.9.2, arch: x86_64, family: mac
Reporter: Michael Heuer
Priority: Critical
[jira] (MDEPLOY-177) Maven release:perform hangs when downloading maven-metadata.xml
[
https://jira.codehaus.org/browse/MDEPLOY-177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=343884#comment-343884
]
Michael Heuer commented on MDEPLOY-177:
---
Hello Robert,
Thank you for the quick reply.
The biojava project has its own Maven repository because it depends on
non-Maven Central artifacts and we haven't found time to migrate everything
over to Sonatype OSS Nexus. As for why we don't run Nexus or something similar
as our repository manager, that is a fair question.
This may be a problem with scp but I find it odd that download/upload works ok
for biojava-legacy-1.8.5.pom and then hangs on the second file.
Travis CI run at/around the same time I was attempting to perform this release
https://travis-ci.org/biojava/biojava-legacy/builds/21911708
https://travis-ci.org/biojava/biojava-legacy/builds/21911712
Does it modify maven-metadata.xml in some way? I wouldn't think it has write
permissions to our repo.
I'll try running with --debug this evening.
Maven release:perform hangs when downloading maven-metadata.xml
---
Key: MDEPLOY-177
URL: https://jira.codehaus.org/browse/MDEPLOY-177
Project: Maven Deploy Plugin
Issue Type: Bug
Components: deploy:deploy
Affects Versions: 2.8.1
Environment: $ mvn -v
Apache Maven 3.2.1 (ea8b2b07643dbb1b84b6d16e1f08391b666bc1e9;
2014-02-14T11:37:52-06:00)
Maven home: /usr/local/Cellar/maven/3.2.1/libexec
Java version: 1.7.0_51, vendor: Oracle Corporation
Java home: /Library/Java/JavaVirtualMachines/jdk1.7.0_51.jdk/Contents/Home/jre
Default locale: en_US, platform encoding: UTF-8
OS name: mac os x, version: 10.9.2, arch: x86_64, family: mac
Reporter: Michael Heuer
Priority: Critical
When attempting to mvn release:perform
{code:none}
$ mvn release:perform
...
[INFO] [INFO]
[INFO] [INFO] Building biojava-legacy 1.8.5
[INFO] [INFO]
[INFO] [INFO]
[INFO] [INFO] maven-source-plugin:2.2.1:jar (attach-sources) @
biojava-legacy
[INFO] [INFO]
[INFO] [INFO] maven-source-plugin:2.2.1:jar (attach-sources) @
biojava-legacy
[INFO] [INFO]
[INFO] [INFO] --- maven-source-plugin:2.2.1:jar (attach-sources) @
biojava-legacy ---
[INFO] [INFO]
[INFO] [INFO] --- maven-javadoc-plugin:2.9.1:jar (attach-javadocs) @
biojava-legacy ---
[INFO] [INFO] Not executing Javadoc as the project is not a Java
classpath-capable package
[INFO] [INFO]
[INFO] [INFO] --- maven-install-plugin:2.4:install (default-install) @
biojava-legacy ---
[INFO] [INFO] Installing
/Users/xxx/working/biojava-legacy/target/checkout/pom.xml to
/Users/xxx/.m2/repository/org/biojava/biojava-legacy/1.8.5/biojava-legacy-1.8.5.pom
[INFO] [INFO]
[INFO] [INFO] --- maven-deploy-plugin:2.8.1:deploy (default-deploy) @
biojava-legacy ---
[INFO] Uploading:
scp://cloudportal.open-bio.org/home/websites/biojava.org/html/static/download/maven/org/biojava/biojava-legacy/1.8.5/biojava-legacy-1.8.5.pom
[INFO] 4/9 KB
[INFO] 8/9 KB
[INFO] 9/9 KB
[INFO]
[INFO] Uploaded:
scp://cloudportal.open-bio.org/home/websites/biojava.org/html/static/download/maven/org/biojava/biojava-legacy/1.8.5/biojava-legacy-1.8.5.pom
(9 KB at 3.0 KB/sec)
[INFO] Downloading:
scp://cloudportal.open-bio.org/home/websites/biojava.org/html/static/download/maven/org/biojava/biojava-legacy/maven-metadata.xml
[INFO] 750/750 B
[INFO] 751/750 B
{code}
the build hangs at this point. It appears there might be a difference
between the expected file size and the downloaded file size, but no
warning/error messages appear, the build just hangs.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MDEPLOY-177) Maven release:perform hangs when downloading maven-metadata.xml
[
https://jira.codehaus.org/browse/MDEPLOY-177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=343895#comment-343895
]
Michael Heuer commented on MDEPLOY-177:
---
Still happens with --debug via release:perform
{code:none}
$ mvn -X release:perform --debug
...
[INFO] [DEBUG] Configuring mojo
org.apache.maven.plugins:maven-deploy-plugin:2.8.1:deploy from plugin realm
ClassRealm[pluginorg.apache.maven.plugins:maven-deploy-plugin:2.8.1, parent:
sun.misc.Launcher$AppClassLoader@713c817]
[INFO] [DEBUG] Configuring mojo
'org.apache.maven.plugins:maven-deploy-plugin:2.8.1:deploy' with basic
configurator --
[INFO] [DEBUG] (f) artifact = org.biojava:biojava-legacy:pom:1.8.5
[INFO] [DEBUG] (f) attachedArtifacts = []
[INFO] [DEBUG] (f) deployAtEnd = false
[INFO] [DEBUG] (s) localRepository =id: local
[INFO] url: file:///Users/heuermh/.m2/repository/
[INFO]layout: default
[INFO] snapshots: [enabled = true, update = always]
[INFO] releases: [enabled = true, update = always]
[INFO]
[INFO] [DEBUG] (f) offline = false
[INFO] [DEBUG] (f) packaging = pom
[INFO] [DEBUG] (f) pomFile =
/Users/heuermh/working/biojava-legacy/target/checkout/pom.xml
[INFO] [DEBUG] (f) reactorProjects = [MavenProject:
org.biojava:biojava-legacy:1.8.5 @
/Users/heuermh/working/biojava-legacy/target/checkout/pom.xml, MavenProject:
org.biojava:bytecode:1.8.5 @
/Users/heuermh/working/biojava-legacy/target/checkout/bytecode/pom.xml,
MavenProject: org.biojava:core:1.8.5 @
/Users/heuermh/working/biojava-legacy/target/checkout/core/pom.xml,
MavenProject: org.biojava:alignment:1.8.5 @
/Users/heuermh/working/biojava-legacy/target/checkout/alignment/pom.xml,
MavenProject: org.biojava:biosql:1.8.5 @
/Users/heuermh/working/biojava-legacy/target/checkout/biosql/pom.xml,
MavenProject: org.biojava:blast:1.8.5 @
/Users/heuermh/working/biojava-legacy/target/checkout/blast/pom.xml,
MavenProject: org.biojava:das:1.8.5 @
/Users/heuermh/working/biojava-legacy/target/checkout/das/pom.xml,
MavenProject: org.biojava:sequencing:1.8.5 @
/Users/heuermh/working/biojava-legacy/target/checkout/sequencing/pom.xml,
MavenProject: org.biojava:gui:1.8.5 @
/Users/heuermh/working/biojava-legacy/target/checkout/gui/pom.xml,
MavenProject: org.biojava:phylo:1.8.5 @
/Users/heuermh/working/biojava-legacy/target/checkout/phylo/pom.xml]
[INFO] [DEBUG] (f) retryFailedDeploymentCount = 1
[INFO] [DEBUG] (f) skip = false
[INFO] [DEBUG] (f) updateReleaseInfo = true
[INFO] [DEBUG] (f) project = MavenProject: org.biojava:biojava-legacy:1.8.5 @
/Users/heuermh/working/biojava-legacy/target/checkout/pom.xml
[INFO] [DEBUG] -- end configuration --
[INFO] [DEBUG] Using connector WagonRepositoryConnector with priority 0.0 for
scp://cloudportal.open-bio.org/home/websites/biojava.org/html/static/download/maven/
with username=mheuer
[INFO] Uploading:
scp://cloudportal.open-bio.org/home/websites/biojava.org/html/static/download/maven/org/biojava/biojava-legacy/1.8.5/biojava-legacy-1.8.5.pom
[INFO] 4/9 KB
[INFO] 8/9 KB
[INFO] 9/9 KB
[INFO]
[INFO] Uploaded:
scp://cloudportal.open-bio.org/home/websites/biojava.org/html/static/download/maven/org/biojava/biojava-legacy/1.8.5/biojava-legacy-1.8.5.pom
(9 KB at 2.9 KB/sec)
[INFO] Downloading:
scp://cloudportal.open-bio.org/home/websites/biojava.org/html/static/download/maven/org/biojava/biojava-legacy/maven-metadata.xml
[INFO] 751/750 B
{code}
On the server side
{code:none}
4 -rw-rw-r-- 1 apache apache 750 Mar 31 03:30 maven-metadata.xml
4 -rw-rw-r-- 1 apache apache 32 Mar 31 03:30 maven-metadata.xml.md5
4 -rw-rw-r-- 1 apache apache 40 Mar 31 03:30 maven-metadata.xml.sha1
{code}
the checksums are valid
{code:none}
$ md5sum maven-metadata.xml
74c93817f3cc47c9dd4958b2d1cf8f69 maven-metadata.xml
$ cat maven-metadata.xml.md5
74c93817f3cc47c9dd4958b2d1cf8f69
$ sha1sum maven-metadata.xml
b8865ab6744fb26ba9400f1ef906cb6145f86631 maven-metadata.xml
$ cat maven-metadata.xml.sha1
b8865ab6744fb26ba9400f1ef906cb6145f86631
{code}
maven-metadata.xml was last touched by the deploy of a snapshot for the next
snapshot version (1.8.6-SNAPSHOT), presumably by Travis CI
{code:xml}
$ cat maven-metadata.xml
?xml version=1.0 encoding=UTF-8?
metadata
groupIdorg.biojava/groupId
artifactIdbiojava-legacy/artifactId
versioning
release1.8.4/release
versions
version3.0-beta1/version
version1.8-beta1/version
version1.8-beta2-SNAPSHOT/version
version1.8/version
version1.8.1-SNAPSHOT/version
version1.8.1/version
version1.8.2-SNAPSHOT/version
version1.8.2/version
version1.8.3-SNAPSHOT/version
version1.8.4-SNAPSHOT/version
version1.8.4/version
version1.8.5-SNAPSHOT/version
version1.8.6-SNAPSHOT/version
/versions
lastUpdated20140331033047/lastUpdated
/versioning
/metadata
{code}
It looks the same when
[jira] (MDEPLOY-177) Maven release:perform hangs when downloading maven-metadata.xml
[
https://jira.codehaus.org/browse/MDEPLOY-177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Heuer updated MDEPLOY-177:
--
Attachment: deploy-debug.txt
Maven release:perform hangs when downloading maven-metadata.xml
---
Key: MDEPLOY-177
URL: https://jira.codehaus.org/browse/MDEPLOY-177
Project: Maven Deploy Plugin
Issue Type: Bug
Components: deploy:deploy
Affects Versions: 2.8.1
Environment: $ mvn -v
Apache Maven 3.2.1 (ea8b2b07643dbb1b84b6d16e1f08391b666bc1e9;
2014-02-14T11:37:52-06:00)
Maven home: /usr/local/Cellar/maven/3.2.1/libexec
Java version: 1.7.0_51, vendor: Oracle Corporation
Java home: /Library/Java/JavaVirtualMachines/jdk1.7.0_51.jdk/Contents/Home/jre
Default locale: en_US, platform encoding: UTF-8
OS name: mac os x, version: 10.9.2, arch: x86_64, family: mac
Reporter: Michael Heuer
Priority: Critical
Attachments: deploy-debug.txt, release-perform-debug.txt
When attempting to mvn release:perform
{code:none}
$ mvn release:perform
...
[INFO] [INFO]
[INFO] [INFO] Building biojava-legacy 1.8.5
[INFO] [INFO]
[INFO] [INFO]
[INFO] [INFO] maven-source-plugin:2.2.1:jar (attach-sources) @
biojava-legacy
[INFO] [INFO]
[INFO] [INFO] maven-source-plugin:2.2.1:jar (attach-sources) @
biojava-legacy
[INFO] [INFO]
[INFO] [INFO] --- maven-source-plugin:2.2.1:jar (attach-sources) @
biojava-legacy ---
[INFO] [INFO]
[INFO] [INFO] --- maven-javadoc-plugin:2.9.1:jar (attach-javadocs) @
biojava-legacy ---
[INFO] [INFO] Not executing Javadoc as the project is not a Java
classpath-capable package
[INFO] [INFO]
[INFO] [INFO] --- maven-install-plugin:2.4:install (default-install) @
biojava-legacy ---
[INFO] [INFO] Installing
/Users/xxx/working/biojava-legacy/target/checkout/pom.xml to
/Users/xxx/.m2/repository/org/biojava/biojava-legacy/1.8.5/biojava-legacy-1.8.5.pom
[INFO] [INFO]
[INFO] [INFO] --- maven-deploy-plugin:2.8.1:deploy (default-deploy) @
biojava-legacy ---
[INFO] Uploading:
scp://cloudportal.open-bio.org/home/websites/biojava.org/html/static/download/maven/org/biojava/biojava-legacy/1.8.5/biojava-legacy-1.8.5.pom
[INFO] 4/9 KB
[INFO] 8/9 KB
[INFO] 9/9 KB
[INFO]
[INFO] Uploaded:
scp://cloudportal.open-bio.org/home/websites/biojava.org/html/static/download/maven/org/biojava/biojava-legacy/1.8.5/biojava-legacy-1.8.5.pom
(9 KB at 3.0 KB/sec)
[INFO] Downloading:
scp://cloudportal.open-bio.org/home/websites/biojava.org/html/static/download/maven/org/biojava/biojava-legacy/maven-metadata.xml
[INFO] 750/750 B
[INFO] 751/750 B
{code}
the build hangs at this point. It appears there might be a difference
between the expected file size and the downloaded file size, but no
warning/error messages appear, the build just hangs.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MDEPLOY-177) Maven release:perform hangs when downloading maven-metadata.xml
[
https://jira.codehaus.org/browse/MDEPLOY-177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Heuer updated MDEPLOY-177:
--
Attachment: release-perform-debug.txt
Maven release:perform hangs when downloading maven-metadata.xml
---
Key: MDEPLOY-177
URL: https://jira.codehaus.org/browse/MDEPLOY-177
Project: Maven Deploy Plugin
Issue Type: Bug
Components: deploy:deploy
Affects Versions: 2.8.1
Environment: $ mvn -v
Apache Maven 3.2.1 (ea8b2b07643dbb1b84b6d16e1f08391b666bc1e9;
2014-02-14T11:37:52-06:00)
Maven home: /usr/local/Cellar/maven/3.2.1/libexec
Java version: 1.7.0_51, vendor: Oracle Corporation
Java home: /Library/Java/JavaVirtualMachines/jdk1.7.0_51.jdk/Contents/Home/jre
Default locale: en_US, platform encoding: UTF-8
OS name: mac os x, version: 10.9.2, arch: x86_64, family: mac
Reporter: Michael Heuer
Priority: Critical
Attachments: deploy-debug.txt, release-perform-debug.txt
When attempting to mvn release:perform
{code:none}
$ mvn release:perform
...
[INFO] [INFO]
[INFO] [INFO] Building biojava-legacy 1.8.5
[INFO] [INFO]
[INFO] [INFO]
[INFO] [INFO] maven-source-plugin:2.2.1:jar (attach-sources) @
biojava-legacy
[INFO] [INFO]
[INFO] [INFO] maven-source-plugin:2.2.1:jar (attach-sources) @
biojava-legacy
[INFO] [INFO]
[INFO] [INFO] --- maven-source-plugin:2.2.1:jar (attach-sources) @
biojava-legacy ---
[INFO] [INFO]
[INFO] [INFO] --- maven-javadoc-plugin:2.9.1:jar (attach-javadocs) @
biojava-legacy ---
[INFO] [INFO] Not executing Javadoc as the project is not a Java
classpath-capable package
[INFO] [INFO]
[INFO] [INFO] --- maven-install-plugin:2.4:install (default-install) @
biojava-legacy ---
[INFO] [INFO] Installing
/Users/xxx/working/biojava-legacy/target/checkout/pom.xml to
/Users/xxx/.m2/repository/org/biojava/biojava-legacy/1.8.5/biojava-legacy-1.8.5.pom
[INFO] [INFO]
[INFO] [INFO] --- maven-deploy-plugin:2.8.1:deploy (default-deploy) @
biojava-legacy ---
[INFO] Uploading:
scp://cloudportal.open-bio.org/home/websites/biojava.org/html/static/download/maven/org/biojava/biojava-legacy/1.8.5/biojava-legacy-1.8.5.pom
[INFO] 4/9 KB
[INFO] 8/9 KB
[INFO] 9/9 KB
[INFO]
[INFO] Uploaded:
scp://cloudportal.open-bio.org/home/websites/biojava.org/html/static/download/maven/org/biojava/biojava-legacy/1.8.5/biojava-legacy-1.8.5.pom
(9 KB at 3.0 KB/sec)
[INFO] Downloading:
scp://cloudportal.open-bio.org/home/websites/biojava.org/html/static/download/maven/org/biojava/biojava-legacy/maven-metadata.xml
[INFO] 750/750 B
[INFO] 751/750 B
{code}
the build hangs at this point. It appears there might be a difference
between the expected file size and the downloaded file size, but no
warning/error messages appear, the build just hangs.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MDEPLOY-177) Maven release:perform hangs when downloading maven-metadata.xml
[
https://jira.codehaus.org/browse/MDEPLOY-177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=343896#comment-343896
]
Michael Heuer commented on MDEPLOY-177:
---
What is going on? Now deploy of a snapshot won't work either
{code:none}
$ mvn deploy --debug
...
[DEBUG] (f) project = MavenProject: org.biojava:biojava-legacy:1.8.6-SNAPSHOT
@ /Users/heuermh/working/biojava-legacy/pom.xml
[DEBUG] -- end configuration --
[DEBUG] Using connector WagonRepositoryConnector with priority 0.0 for
scp://cloudportal.open-bio.org/home/websites/biojava.org/html/static/download/maven/
with username=mheuer
Downloading:
scp://cloudportal.open-bio.org/home/websites/biojava.org/html/static/download/maven/org/biojava/biojava-legacy/1.8.6-SNAPSHOT/maven-metadata.xml
603/602 B
{code}
Full debug output attached.
Maven release:perform hangs when downloading maven-metadata.xml
---
Key: MDEPLOY-177
URL: https://jira.codehaus.org/browse/MDEPLOY-177
Project: Maven Deploy Plugin
Issue Type: Bug
Components: deploy:deploy
Affects Versions: 2.8.1
Environment: $ mvn -v
Apache Maven 3.2.1 (ea8b2b07643dbb1b84b6d16e1f08391b666bc1e9;
2014-02-14T11:37:52-06:00)
Maven home: /usr/local/Cellar/maven/3.2.1/libexec
Java version: 1.7.0_51, vendor: Oracle Corporation
Java home: /Library/Java/JavaVirtualMachines/jdk1.7.0_51.jdk/Contents/Home/jre
Default locale: en_US, platform encoding: UTF-8
OS name: mac os x, version: 10.9.2, arch: x86_64, family: mac
Reporter: Michael Heuer
Priority: Critical
Attachments: deploy-debug.txt, release-perform-debug.txt
When attempting to mvn release:perform
{code:none}
$ mvn release:perform
...
[INFO] [INFO]
[INFO] [INFO] Building biojava-legacy 1.8.5
[INFO] [INFO]
[INFO] [INFO]
[INFO] [INFO] maven-source-plugin:2.2.1:jar (attach-sources) @
biojava-legacy
[INFO] [INFO]
[INFO] [INFO] maven-source-plugin:2.2.1:jar (attach-sources) @
biojava-legacy
[INFO] [INFO]
[INFO] [INFO] --- maven-source-plugin:2.2.1:jar (attach-sources) @
biojava-legacy ---
[INFO] [INFO]
[INFO] [INFO] --- maven-javadoc-plugin:2.9.1:jar (attach-javadocs) @
biojava-legacy ---
[INFO] [INFO] Not executing Javadoc as the project is not a Java
classpath-capable package
[INFO] [INFO]
[INFO] [INFO] --- maven-install-plugin:2.4:install (default-install) @
biojava-legacy ---
[INFO] [INFO] Installing
/Users/xxx/working/biojava-legacy/target/checkout/pom.xml to
/Users/xxx/.m2/repository/org/biojava/biojava-legacy/1.8.5/biojava-legacy-1.8.5.pom
[INFO] [INFO]
[INFO] [INFO] --- maven-deploy-plugin:2.8.1:deploy (default-deploy) @
biojava-legacy ---
[INFO] Uploading:
scp://cloudportal.open-bio.org/home/websites/biojava.org/html/static/download/maven/org/biojava/biojava-legacy/1.8.5/biojava-legacy-1.8.5.pom
[INFO] 4/9 KB
[INFO] 8/9 KB
[INFO] 9/9 KB
[INFO]
[INFO] Uploaded:
scp://cloudportal.open-bio.org/home/websites/biojava.org/html/static/download/maven/org/biojava/biojava-legacy/1.8.5/biojava-legacy-1.8.5.pom
(9 KB at 3.0 KB/sec)
[INFO] Downloading:
scp://cloudportal.open-bio.org/home/websites/biojava.org/html/static/download/maven/org/biojava/biojava-legacy/maven-metadata.xml
[INFO] 750/750 B
[INFO] 751/750 B
{code}
the build hangs at this point. It appears there might be a difference
between the expected file size and the downloaded file size, but no
warning/error messages appear, the build just hangs.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MDEPLOY-177) Maven release:perform hangs when downloading maven-metadata.xml
[
https://jira.codehaus.org/browse/MDEPLOY-177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=343896#comment-343896
]
Michael Heuer edited comment on MDEPLOY-177 at 3/31/14 8:59 PM:
A deploy of a snapshot won't work either
{code:none}
$ mvn deploy --debug
...
[DEBUG] (f) project = MavenProject: org.biojava:biojava-legacy:1.8.6-SNAPSHOT
@ /Users/heuermh/working/biojava-legacy/pom.xml
[DEBUG] -- end configuration --
[DEBUG] Using connector WagonRepositoryConnector with priority 0.0 for
scp://cloudportal.open-bio.org/home/websites/biojava.org/html/static/download/maven/
with username=mheuer
Downloading:
scp://cloudportal.open-bio.org/home/websites/biojava.org/html/static/download/maven/org/biojava/biojava-legacy/1.8.6-SNAPSHOT/maven-metadata.xml
603/602 B
{code}
Full debug output attached.
was (Author: heuermh):
What is going on? Now deploy of a snapshot won't work either
{code:none}
$ mvn deploy --debug
...
[DEBUG] (f) project = MavenProject: org.biojava:biojava-legacy:1.8.6-SNAPSHOT
@ /Users/heuermh/working/biojava-legacy/pom.xml
[DEBUG] -- end configuration --
[DEBUG] Using connector WagonRepositoryConnector with priority 0.0 for
scp://cloudportal.open-bio.org/home/websites/biojava.org/html/static/download/maven/
with username=mheuer
Downloading:
scp://cloudportal.open-bio.org/home/websites/biojava.org/html/static/download/maven/org/biojava/biojava-legacy/1.8.6-SNAPSHOT/maven-metadata.xml
603/602 B
{code}
Full debug output attached.
Maven release:perform hangs when downloading maven-metadata.xml
---
Key: MDEPLOY-177
URL: https://jira.codehaus.org/browse/MDEPLOY-177
Project: Maven Deploy Plugin
Issue Type: Bug
Components: deploy:deploy
Affects Versions: 2.8.1
Environment: $ mvn -v
Apache Maven 3.2.1 (ea8b2b07643dbb1b84b6d16e1f08391b666bc1e9;
2014-02-14T11:37:52-06:00)
Maven home: /usr/local/Cellar/maven/3.2.1/libexec
Java version: 1.7.0_51, vendor: Oracle Corporation
Java home: /Library/Java/JavaVirtualMachines/jdk1.7.0_51.jdk/Contents/Home/jre
Default locale: en_US, platform encoding: UTF-8
OS name: mac os x, version: 10.9.2, arch: x86_64, family: mac
Reporter: Michael Heuer
Priority: Critical
Attachments: deploy-debug.txt, release-perform-debug.txt
When attempting to mvn release:perform
{code:none}
$ mvn release:perform
...
[INFO] [INFO]
[INFO] [INFO] Building biojava-legacy 1.8.5
[INFO] [INFO]
[INFO] [INFO]
[INFO] [INFO] maven-source-plugin:2.2.1:jar (attach-sources) @
biojava-legacy
[INFO] [INFO]
[INFO] [INFO] maven-source-plugin:2.2.1:jar (attach-sources) @
biojava-legacy
[INFO] [INFO]
[INFO] [INFO] --- maven-source-plugin:2.2.1:jar (attach-sources) @
biojava-legacy ---
[INFO] [INFO]
[INFO] [INFO] --- maven-javadoc-plugin:2.9.1:jar (attach-javadocs) @
biojava-legacy ---
[INFO] [INFO] Not executing Javadoc as the project is not a Java
classpath-capable package
[INFO] [INFO]
[INFO] [INFO] --- maven-install-plugin:2.4:install (default-install) @
biojava-legacy ---
[INFO] [INFO] Installing
/Users/xxx/working/biojava-legacy/target/checkout/pom.xml to
/Users/xxx/.m2/repository/org/biojava/biojava-legacy/1.8.5/biojava-legacy-1.8.5.pom
[INFO] [INFO]
[INFO] [INFO] --- maven-deploy-plugin:2.8.1:deploy (default-deploy) @
biojava-legacy ---
[INFO] Uploading:
scp://cloudportal.open-bio.org/home/websites/biojava.org/html/static/download/maven/org/biojava/biojava-legacy/1.8.5/biojava-legacy-1.8.5.pom
[INFO] 4/9 KB
[INFO] 8/9 KB
[INFO] 9/9 KB
[INFO]
[INFO] Uploaded:
scp://cloudportal.open-bio.org/home/websites/biojava.org/html/static/download/maven/org/biojava/biojava-legacy/1.8.5/biojava-legacy-1.8.5.pom
(9 KB at 3.0 KB/sec)
[INFO] Downloading:
scp://cloudportal.open-bio.org/home/websites/biojava.org/html/static/download/maven/org/biojava/biojava-legacy/maven-metadata.xml
[INFO] 750/750 B
[INFO] 751/750 B
{code}
the build hangs at this point. It appears there might be a difference
between the expected file size and the downloaded file size, but no
warning/error messages appear, the build just hangs.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MDEPLOY-177) Maven release:perform hangs when downloading maven-metadata.xml
[
https://jira.codehaus.org/browse/MDEPLOY-177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=343898#comment-343898
]
Michael Heuer commented on MDEPLOY-177:
---
If this is what you mean, it works via command line scp
{code:none}
$ scp -vvv
mhe...@cloudportal.open-bio.org:/home/websites/biojava.org/html/static/download/maven/org/biojava/biojava-legacy/1.8.6-SNAPSHOT/maven-metadata.xml
.
...
debug1: Sending command: scp -v -f
/home/websites/biojava.org/html/static/download/maven/org/biojava/biojava-legacy/1.8.6-SNAPSHOT/maven-metadata.xml
debug2: channel 0: request exec confirm 1
debug2: callback done
debug2: channel 0: open confirm rwindow 0 rmax 32768
debug2: channel 0: rcvd adjust 2097152
debug2: channel_input_status_confirm: type 99 id 0
debug2: exec request accepted on channel 0
debug2: channel 0: rcvd ext data 49
Sending file modes: C0644 602 maven-metadata.xml
debug2: channel 0: written 49 to efd 7
Sink: C0644 602 maven-metadata.xml
maven-metadata.xml
100% 602 0.6KB/s 00:00
debug2: channel 0: rcvd eof
...
Transferred: sent 3284, received 3708 bytes, in 0.3 seconds
Bytes per second: sent 9709.3, received 10962.9
debug1: Exit status 0
{code}
Maven release:perform hangs when downloading maven-metadata.xml
---
Key: MDEPLOY-177
URL: https://jira.codehaus.org/browse/MDEPLOY-177
Project: Maven Deploy Plugin
Issue Type: Bug
Components: deploy:deploy
Affects Versions: 2.8.1
Environment: $ mvn -v
Apache Maven 3.2.1 (ea8b2b07643dbb1b84b6d16e1f08391b666bc1e9;
2014-02-14T11:37:52-06:00)
Maven home: /usr/local/Cellar/maven/3.2.1/libexec
Java version: 1.7.0_51, vendor: Oracle Corporation
Java home: /Library/Java/JavaVirtualMachines/jdk1.7.0_51.jdk/Contents/Home/jre
Default locale: en_US, platform encoding: UTF-8
OS name: mac os x, version: 10.9.2, arch: x86_64, family: mac
Reporter: Michael Heuer
Priority: Critical
Attachments: deploy-debug.txt, release-perform-debug.txt
When attempting to mvn release:perform
{code:none}
$ mvn release:perform
...
[INFO] [INFO]
[INFO] [INFO] Building biojava-legacy 1.8.5
[INFO] [INFO]
[INFO] [INFO]
[INFO] [INFO] maven-source-plugin:2.2.1:jar (attach-sources) @
biojava-legacy
[INFO] [INFO]
[INFO] [INFO] maven-source-plugin:2.2.1:jar (attach-sources) @
biojava-legacy
[INFO] [INFO]
[INFO] [INFO] --- maven-source-plugin:2.2.1:jar (attach-sources) @
biojava-legacy ---
[INFO] [INFO]
[INFO] [INFO] --- maven-javadoc-plugin:2.9.1:jar (attach-javadocs) @
biojava-legacy ---
[INFO] [INFO] Not executing Javadoc as the project is not a Java
classpath-capable package
[INFO] [INFO]
[INFO] [INFO] --- maven-install-plugin:2.4:install (default-install) @
biojava-legacy ---
[INFO] [INFO] Installing
/Users/xxx/working/biojava-legacy/target/checkout/pom.xml to
/Users/xxx/.m2/repository/org/biojava/biojava-legacy/1.8.5/biojava-legacy-1.8.5.pom
[INFO] [INFO]
[INFO] [INFO] --- maven-deploy-plugin:2.8.1:deploy (default-deploy) @
biojava-legacy ---
[INFO] Uploading:
scp://cloudportal.open-bio.org/home/websites/biojava.org/html/static/download/maven/org/biojava/biojava-legacy/1.8.5/biojava-legacy-1.8.5.pom
[INFO] 4/9 KB
[INFO] 8/9 KB
[INFO] 9/9 KB
[INFO]
[INFO] Uploaded:
scp://cloudportal.open-bio.org/home/websites/biojava.org/html/static/download/maven/org/biojava/biojava-legacy/1.8.5/biojava-legacy-1.8.5.pom
(9 KB at 3.0 KB/sec)
[INFO] Downloading:
scp://cloudportal.open-bio.org/home/websites/biojava.org/html/static/download/maven/org/biojava/biojava-legacy/maven-metadata.xml
[INFO] 750/750 B
[INFO] 751/750 B
{code}
the build hangs at this point. It appears there might be a difference
between the expected file size and the downloaded file size, but no
warning/error messages appear, the build just hangs.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MCHECKSTYLE-188) Unable to instantiate DoubleCheckedLockingCheck exception after upgrading from version 3.9.1 to 3.10
Michael Heuer created MCHECKSTYLE-188: - Summary: Unable to instantiate DoubleCheckedLockingCheck exception after upgrading from version 3.9.1 to 3.10 Key: MCHECKSTYLE-188 URL: https://jira.codehaus.org/browse/MCHECKSTYLE-188 Project: Maven 2.x Checkstyle Plugin Issue Type: Bug Affects Versions: 2.10 Environment: $ mvn -v Apache Maven 3.0.5 (r01de14724cdef164cd33c7c8c2fe155faf9602da; 2013-02-19 07:51:28-0600) Maven home: /Users/mheuer/bin/maven-latest Java version: 1.6.0_37, vendor: Apple Inc. Java home: /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home Default locale: en_US, platform encoding: MacRoman OS name: mac os x, version: 10.7.5, arch: x86_64, family: mac Reporter: Michael Heuer After upgrading from version 3.9.1 to version 3.10 $ mvn -e site ... Error during page generation: Error rendering Maven report: Failed during checkstyle configuration: cannot initialize module TreeWalker - Unable to instantiate DoubleCheckedLocking: Unable to instantiate DoubleCheckedLockingCheck - [Help 1] org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-site-plugin:3.2:site (default-site) on project dsh-midi-cytoscape3-app: Error during page generation at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:217) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59) at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156) at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537) at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196) at org.apache.maven.cli.MavenCli.main(MavenCli.java:141) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290) at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230) at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409) at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352) Caused by: org.apache.maven.plugin.MojoExecutionException: Error during page generation at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:143) at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209) ... 19 more Caused by: org.apache.maven.doxia.siterenderer.RendererException: Error rendering Maven report: Failed during checkstyle configuration at org.apache.maven.plugins.site.ReportDocumentRenderer.renderDocument(ReportDocumentRenderer.java:233) at org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderModule(DefaultSiteRenderer.java:319) at org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(DefaultSiteRenderer.java:135) at org.apache.maven.plugins.site.SiteMojo.renderLocale(SiteMojo.java:175) at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:138) ... 21 more Caused by: org.apache.maven.reporting.MavenReportException: Failed during checkstyle configuration at org.apache.maven.plugin.checkstyle.AbstractCheckstyleReport.executeReport(AbstractCheckstyleReport.java:260) at org.apache.maven.plugin.checkstyle.CheckstyleReport.executeReport(CheckstyleReport.java:339) at org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.java:196) at org.apache.maven.plugins.site.ReportDocumentRenderer.renderDocument(ReportDocumentRenderer.java:219) ... 25 more Caused by: com.puppycrawl.tools.checkstyle.api.CheckstyleException: cannot initialize module TreeWalker - Unable to instantiate DoubleCheckedLocking at com.puppycrawl.tools.checkstyle.Checker.setupChild(Checker.java:178) at
[jira] (MCHECKSTYLE-188) Unable to instantiate DoubleCheckedLockingCheck exception after upgrading from version 3.9.1 to 3.10
[ https://jira.codehaus.org/browse/MCHECKSTYLE-188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Heuer updated MCHECKSTYLE-188: -- Attachment: mcheckstyle188.tar.gz Failure case attached. There might some incompatibility with checkstyle 5.6 and the checkstyle.xml configuration, but I've been using that configuration for several years without issue and did not see any items in the release notes for 2.10 about incompatible configuration items. Unable to instantiate DoubleCheckedLockingCheck exception after upgrading from version 3.9.1 to 3.10 Key: MCHECKSTYLE-188 URL: https://jira.codehaus.org/browse/MCHECKSTYLE-188 Project: Maven 2.x Checkstyle Plugin Issue Type: Bug Affects Versions: 2.10 Environment: $ mvn -v Apache Maven 3.0.5 (r01de14724cdef164cd33c7c8c2fe155faf9602da; 2013-02-19 07:51:28-0600) Maven home: /Users/mheuer/bin/maven-latest Java version: 1.6.0_37, vendor: Apple Inc. Java home: /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home Default locale: en_US, platform encoding: MacRoman OS name: mac os x, version: 10.7.5, arch: x86_64, family: mac Reporter: Michael Heuer Attachments: mcheckstyle188.tar.gz After upgrading from version 3.9.1 to version 3.10 $ mvn -e site ... Error during page generation: Error rendering Maven report: Failed during checkstyle configuration: cannot initialize module TreeWalker - Unable to instantiate DoubleCheckedLocking: Unable to instantiate DoubleCheckedLockingCheck - [Help 1] org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-site-plugin:3.2:site (default-site) on project dsh-midi-cytoscape3-app: Error during page generation at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:217) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59) at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156) at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537) at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196) at org.apache.maven.cli.MavenCli.main(MavenCli.java:141) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290) at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230) at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409) at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352) Caused by: org.apache.maven.plugin.MojoExecutionException: Error during page generation at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:143) at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209) ... 19 more Caused by: org.apache.maven.doxia.siterenderer.RendererException: Error rendering Maven report: Failed during checkstyle configuration at org.apache.maven.plugins.site.ReportDocumentRenderer.renderDocument(ReportDocumentRenderer.java:233) at org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderModule(DefaultSiteRenderer.java:319) at org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(DefaultSiteRenderer.java:135) at org.apache.maven.plugins.site.SiteMojo.renderLocale(SiteMojo.java:175) at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:138) ... 21 more Caused by: org.apache.maven.reporting.MavenReportException: Failed during checkstyle configuration at org.apache.maven.plugin.checkstyle.AbstractCheckstyleReport.executeReport(AbstractCheckstyleReport.java:260)
[jira] (MCHECKSTYLE-189) Unable to instantiate DoubleCheckedLockingCheck exception after upgrading from version 2.9.1 to 2.10
Michael Heuer created MCHECKSTYLE-189: - Summary: Unable to instantiate DoubleCheckedLockingCheck exception after upgrading from version 2.9.1 to 2.10 Key: MCHECKSTYLE-189 URL: https://jira.codehaus.org/browse/MCHECKSTYLE-189 Project: Maven 2.x Checkstyle Plugin Issue Type: Bug Affects Versions: 2.10 Environment: $ mvn -v Apache Maven 3.0.5 (r01de14724cdef164cd33c7c8c2fe155faf9602da; 2013-02-19 07:51:28-0600) Maven home: /Users/mheuer/bin/maven-latest Java version: 1.6.0_37, vendor: Apple Inc. Java home: /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home Default locale: en_US, platform encoding: MacRoman OS name: mac os x, version: 10.7.5, arch: x86_64, family: mac Reporter: Michael Heuer Attachments: mcheckstyle188.tar.gz After upgrading from version 3.9.1 to version 3.10 $ mvn -e site ... Error during page generation: Error rendering Maven report: Failed during checkstyle configuration: cannot initialize module TreeWalker - Unable to instantiate DoubleCheckedLocking: Unable to instantiate DoubleCheckedLockingCheck - [Help 1] org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-site-plugin:3.2:site (default-site) on project dsh-midi-cytoscape3-app: Error during page generation at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:217) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59) at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156) at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537) at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196) at org.apache.maven.cli.MavenCli.main(MavenCli.java:141) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290) at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230) at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409) at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352) Caused by: org.apache.maven.plugin.MojoExecutionException: Error during page generation at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:143) at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209) ... 19 more Caused by: org.apache.maven.doxia.siterenderer.RendererException: Error rendering Maven report: Failed during checkstyle configuration at org.apache.maven.plugins.site.ReportDocumentRenderer.renderDocument(ReportDocumentRenderer.java:233) at org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderModule(DefaultSiteRenderer.java:319) at org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(DefaultSiteRenderer.java:135) at org.apache.maven.plugins.site.SiteMojo.renderLocale(SiteMojo.java:175) at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:138) ... 21 more Caused by: org.apache.maven.reporting.MavenReportException: Failed during checkstyle configuration at org.apache.maven.plugin.checkstyle.AbstractCheckstyleReport.executeReport(AbstractCheckstyleReport.java:260) at org.apache.maven.plugin.checkstyle.CheckstyleReport.executeReport(CheckstyleReport.java:339) at org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.java:196) at org.apache.maven.plugins.site.ReportDocumentRenderer.renderDocument(ReportDocumentRenderer.java:219) ... 25 more Caused by: com.puppycrawl.tools.checkstyle.api.CheckstyleException: cannot initialize module TreeWalker - Unable to instantiate DoubleCheckedLocking at com.puppycrawl.tools.checkstyle.Checker.setupChild(Checker.java:178) at com.puppycrawl.tools.checkstyle.api.AutomaticBean.configure(AutomaticBean.java:184) at org.apache.maven.plugin.checkstyle.DefaultCheckstyleExecutor.executeCheckstyle(DefaultCheckstyleExecutor.java:172) at
[jira] (MCHECKSTYLE-188) Unable to instantiate DoubleCheckedLockingCheck exception after upgrading from version 3.9.1 to 3.10
[ https://jira.codehaus.org/browse/MCHECKSTYLE-188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Heuer closed MCHECKSTYLE-188. - Resolution: Incomplete Invalid issue, wrong version numbers in issue title. If only issues could be editable. Unable to instantiate DoubleCheckedLockingCheck exception after upgrading from version 3.9.1 to 3.10 Key: MCHECKSTYLE-188 URL: https://jira.codehaus.org/browse/MCHECKSTYLE-188 Project: Maven 2.x Checkstyle Plugin Issue Type: Bug Affects Versions: 2.10 Environment: $ mvn -v Apache Maven 3.0.5 (r01de14724cdef164cd33c7c8c2fe155faf9602da; 2013-02-19 07:51:28-0600) Maven home: /Users/mheuer/bin/maven-latest Java version: 1.6.0_37, vendor: Apple Inc. Java home: /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home Default locale: en_US, platform encoding: MacRoman OS name: mac os x, version: 10.7.5, arch: x86_64, family: mac Reporter: Michael Heuer Attachments: mcheckstyle188.tar.gz After upgrading from version 3.9.1 to version 3.10 $ mvn -e site ... Error during page generation: Error rendering Maven report: Failed during checkstyle configuration: cannot initialize module TreeWalker - Unable to instantiate DoubleCheckedLocking: Unable to instantiate DoubleCheckedLockingCheck - [Help 1] org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-site-plugin:3.2:site (default-site) on project dsh-midi-cytoscape3-app: Error during page generation at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:217) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59) at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156) at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537) at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196) at org.apache.maven.cli.MavenCli.main(MavenCli.java:141) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290) at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230) at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409) at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352) Caused by: org.apache.maven.plugin.MojoExecutionException: Error during page generation at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:143) at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209) ... 19 more Caused by: org.apache.maven.doxia.siterenderer.RendererException: Error rendering Maven report: Failed during checkstyle configuration at org.apache.maven.plugins.site.ReportDocumentRenderer.renderDocument(ReportDocumentRenderer.java:233) at org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderModule(DefaultSiteRenderer.java:319) at org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(DefaultSiteRenderer.java:135) at org.apache.maven.plugins.site.SiteMojo.renderLocale(SiteMojo.java:175) at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:138) ... 21 more Caused by: org.apache.maven.reporting.MavenReportException: Failed during checkstyle configuration at org.apache.maven.plugin.checkstyle.AbstractCheckstyleReport.executeReport(AbstractCheckstyleReport.java:260) at org.apache.maven.plugin.checkstyle.CheckstyleReport.executeReport(CheckstyleReport.java:339) at org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.java:196) at
[jira] (MCHECKSTYLE-189) Unable to instantiate DoubleCheckedLockingCheck exception after upgrading from version 2.9.1 to 2.10
[
https://jira.codehaus.org/browse/MCHECKSTYLE-189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=320479#comment-320479
]
Michael Heuer commented on MCHECKSTYLE-189:
---
Tar via cygwin should work on windows.
The problem is in fact with a custom configuration checkstyle.xml which
includes
{code:xml}
module name=DoubleCheckedLocking/
{code}
The release notes for Checkstyle 5.5 -- 5.6 say
bq. Removed the DoubleCheckedLocking check, as in Java 5 (and beyond), using
the volatile keyword addresses the issue. See here for more details.
The release notes for Maven Checkstyle Plugin 2.9.1 -- 2.10 do not mention
this change.
I think both projects have failed with regards to semantic versioning -- even
though this is not a strict binary-incompatible change, it is a
configuration-incompatible change. Updating a minor version of a maven plugin
should not cause existing projects to break.
Unable to instantiate DoubleCheckedLockingCheck exception after upgrading
from version 2.9.1 to 2.10
Key: MCHECKSTYLE-189
URL: https://jira.codehaus.org/browse/MCHECKSTYLE-189
Project: Maven 2.x Checkstyle Plugin
Issue Type: Bug
Affects Versions: 2.10
Environment: $ mvn -v
Apache Maven 3.0.5 (r01de14724cdef164cd33c7c8c2fe155faf9602da; 2013-02-19
07:51:28-0600)
Maven home: /Users/mheuer/bin/maven-latest
Java version: 1.6.0_37, vendor: Apple Inc.
Java home: /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home
Default locale: en_US, platform encoding: MacRoman
OS name: mac os x, version: 10.7.5, arch: x86_64, family: mac
Reporter: Michael Heuer
Attachments: mcheckstyle188.tar.gz
After upgrading from version 3.9.1 to version 3.10
$ mvn -e site
...
Error during page generation: Error rendering Maven report: Failed during
checkstyle configuration: cannot initialize module TreeWalker - Unable to
instantiate DoubleCheckedLocking: Unable to instantiate
DoubleCheckedLockingCheck - [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
goal org.apache.maven.plugins:maven-site-plugin:3.2:site (default-site) on
project dsh-midi-cytoscape3-app: Error during page generation
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:217)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
at
org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
at
org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
at
org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
Caused by: org.apache.maven.plugin.MojoExecutionException: Error during page
generation
at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:143)
at
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
... 19 more
Caused by: org.apache.maven.doxia.siterenderer.RendererException: Error
rendering Maven report: Failed during checkstyle configuration
at
org.apache.maven.plugins.site.ReportDocumentRenderer.renderDocument(ReportDocumentRenderer.java:233)
at
org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderModule(DefaultSiteRenderer.java:319)
at
org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(DefaultSiteRenderer.java:135)
at org.apache.maven.plugins.site.SiteMojo.renderLocale(SiteMojo.java:175)
at
[jira] (MCHECKSTYLE-189) Unable to instantiate DoubleCheckedLockingCheck exception after upgrading from version 2.9.1 to 2.10
[ https://jira.codehaus.org/browse/MCHECKSTYLE-189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=320487#comment-320487 ] Michael Heuer commented on MCHECKSTYLE-189: --- Fair enough, thanks. Unable to instantiate DoubleCheckedLockingCheck exception after upgrading from version 2.9.1 to 2.10 Key: MCHECKSTYLE-189 URL: https://jira.codehaus.org/browse/MCHECKSTYLE-189 Project: Maven 2.x Checkstyle Plugin Issue Type: Bug Affects Versions: 2.10 Environment: $ mvn -v Apache Maven 3.0.5 (r01de14724cdef164cd33c7c8c2fe155faf9602da; 2013-02-19 07:51:28-0600) Maven home: /Users/mheuer/bin/maven-latest Java version: 1.6.0_37, vendor: Apple Inc. Java home: /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home Default locale: en_US, platform encoding: MacRoman OS name: mac os x, version: 10.7.5, arch: x86_64, family: mac Reporter: Michael Heuer Attachments: mcheckstyle188.tar.gz After upgrading from version 3.9.1 to version 3.10 $ mvn -e site ... Error during page generation: Error rendering Maven report: Failed during checkstyle configuration: cannot initialize module TreeWalker - Unable to instantiate DoubleCheckedLocking: Unable to instantiate DoubleCheckedLockingCheck - [Help 1] org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-site-plugin:3.2:site (default-site) on project dsh-midi-cytoscape3-app: Error during page generation at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:217) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59) at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156) at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537) at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196) at org.apache.maven.cli.MavenCli.main(MavenCli.java:141) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290) at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230) at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409) at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352) Caused by: org.apache.maven.plugin.MojoExecutionException: Error during page generation at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:143) at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209) ... 19 more Caused by: org.apache.maven.doxia.siterenderer.RendererException: Error rendering Maven report: Failed during checkstyle configuration at org.apache.maven.plugins.site.ReportDocumentRenderer.renderDocument(ReportDocumentRenderer.java:233) at org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderModule(DefaultSiteRenderer.java:319) at org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(DefaultSiteRenderer.java:135) at org.apache.maven.plugins.site.SiteMojo.renderLocale(SiteMojo.java:175) at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:138) ... 21 more Caused by: org.apache.maven.reporting.MavenReportException: Failed during checkstyle configuration at org.apache.maven.plugin.checkstyle.AbstractCheckstyleReport.executeReport(AbstractCheckstyleReport.java:260) at org.apache.maven.plugin.checkstyle.CheckstyleReport.executeReport(CheckstyleReport.java:339) at org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.java:196) at org.apache.maven.plugins.site.ReportDocumentRenderer.renderDocument(ReportDocumentRenderer.java:219) ... 25 more Caused by: com.puppycrawl.tools.checkstyle.api.CheckstyleException: cannot initialize module TreeWalker - Unable to instantiate
[jira] (SUREFIRE-948) Module with unit test failure does not match reactor summary
[ https://jira.codehaus.org/browse/SUREFIRE-948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=316727#comment-316727 ] Michael Heuer commented on SUREFIRE-948: In this particular case, maven was run with the -rf option $ mvn clean install -rf :gl-service-spark Maven version 3.0.4, JDK version 1.6.0_37-b06-434, x86_64 or 1.7.0_10, x86_64 on OSX. Module with unit test failure does not match reactor summary Key: SUREFIRE-948 URL: https://jira.codehaus.org/browse/SUREFIRE-948 Project: Maven Surefire Issue Type: Bug Components: Maven Surefire Plugin Affects Versions: 2.13 Reporter: Michael Heuer Priority: Critical Since moving from 2.12.4 to 2.13 we have started to notice an occasional mismatch between a module with a unit test failure and the failed module reactor summary. $ mvn install ... [INFO] [INFO] Forking gl-oauth-apache 1.0-SNAPSHOT [INFO] ... [INFO] --- maven-surefire-plugin:2.13:test (default-test) @ gl-oauth-apache --- [INFO] Surefire report directory: /Users/xxx/working/genotype-list-trunk/gl-oauth-group/gl-oauth-apache/target/surefire-reports ... Failed tests: AccessTokenDetailsTest.testTokenValidateResponse:41-checkToAndFromString:51 expected:12344 but was:12345 Tests run: 7, Failures: 1, Errors: 0, Skipped: 0 [INFO] [INFO] Reactor Summary: [INFO] [INFO] gl-service-spark .. SUCCESS [5.579s] [INFO] gl-service-explorer ... SUCCESS [0.648s] [INFO] gl-service-webapp . SUCCESS [1.300s] [INFO] gl-service-webroot SUCCESS [0.357s] [INFO] gl-service-functional-tests ... SUCCESS [17.700s] [INFO] gl-service-performance-tests .. SUCCESS [0.738s] [INFO] gl-client . SUCCESS [1:02.566s] [INFO] gl-client-functional-tests SUCCESS [15.716s] [INFO] gl-tools .. FAILURE [6.031s] [INFO] gl-web SKIPPED [INFO] gl-oauth-group SKIPPED [INFO] gl-oauth-apache ... SKIPPED [INFO] toy-portal SKIPPED [INFO] toy-rest-app .. SKIPPED [INFO] glsw-oauth SKIPPED [INFO] gl-jetty .. SKIPPED [INFO] [INFO] BUILD FAILURE [INFO] ... [INFO] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.13:test (default-test) on project gl-oauth-apache: There are test failures. We have logged an issue here http://code.google.com/p/genotype-list/issues/detail?id=70 and will be working on replicating the issue in a test case project. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (SUREFIRE-948) Module with unit test failure does not match reactor summary
Michael Heuer created SUREFIRE-948: -- Summary: Module with unit test failure does not match reactor summary Key: SUREFIRE-948 URL: https://jira.codehaus.org/browse/SUREFIRE-948 Project: Maven Surefire Issue Type: Bug Components: Maven Surefire Plugin Affects Versions: 2.13 Reporter: Michael Heuer Since moving from 2.12.4 to 2.13 we have started to notice an occasional mismatch between a module with a unit test failure and the failed module reactor summary. $ mvn install ... [INFO] [INFO] Forking gl-oauth-apache 1.0-SNAPSHOT [INFO] ... [INFO] --- maven-surefire-plugin:2.13:test (default-test) @ gl-oauth-apache --- [INFO] Surefire report directory: /Users/xxx/working/genotype-list-trunk/gl-oauth-group/gl-oauth-apache/target/surefire-reports ... Failed tests: AccessTokenDetailsTest.testTokenValidateResponse:41-checkToAndFromString:51 expected:12344 but was:12345 Tests run: 7, Failures: 1, Errors: 0, Skipped: 0 [INFO] [INFO] Reactor Summary: [INFO] [INFO] gl-service-spark .. SUCCESS [5.579s] [INFO] gl-service-explorer ... SUCCESS [0.648s] [INFO] gl-service-webapp . SUCCESS [1.300s] [INFO] gl-service-webroot SUCCESS [0.357s] [INFO] gl-service-functional-tests ... SUCCESS [17.700s] [INFO] gl-service-performance-tests .. SUCCESS [0.738s] [INFO] gl-client . SUCCESS [1:02.566s] [INFO] gl-client-functional-tests SUCCESS [15.716s] [INFO] gl-tools .. FAILURE [6.031s] [INFO] gl-web SKIPPED [INFO] gl-oauth-group SKIPPED [INFO] gl-oauth-apache ... SKIPPED [INFO] toy-portal SKIPPED [INFO] toy-rest-app .. SKIPPED [INFO] glsw-oauth SKIPPED [INFO] gl-jetty .. SKIPPED [INFO] [INFO] BUILD FAILURE [INFO] ... [INFO] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.13:test (default-test) on project gl-oauth-apache: There are test failures. We have logged an issue here http://code.google.com/p/genotype-list/issues/detail?id=70 and will be working on replicating the issue in a test case project. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-3328) Allow multiple profile activation properties.
[
http://jira.codehaus.org/browse/MNG-3328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=247555#action_247555
]
Michael Heuer commented on MNG-3328:
This issue makes our cross-platform build a mess, tracked as
Maven profiles appear not to be able to fully discriminate MacOSX 10.6.x, Apple
JDK 1.6.x, x86_64
http://code.google.com/p/piccolo2d/issues/detail?id=151
Allow multiple profile activation properties.
-
Key: MNG-3328
URL: http://jira.codehaus.org/browse/MNG-3328
Project: Maven 2 3
Issue Type: Improvement
Components: Profiles
Affects Versions: 2.0.8
Reporter: Paul Gier
Fix For: 3.x / Backlog
The pom model should be changed to allow multiple properties to activate a
profile. So the profile activation section could look something like this:
{code:xml}
activation
properties
my-prop-1some-value/my-prop-1
my-prop-2another-value/my-prop-2
/properties
/activation
{code}
This would provide more flexibility in profile activation.
--
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: (MGPG-19) Site descriptor does not get signed
[ http://jira.codehaus.org/browse/MGPG-19?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=215032#action_215032 ] Michael Heuer commented on MGPG-19: --- Is there a workaround for this problem? This is preventing me from being able to stage in Nexus, see https://issues.sonatype.org/browse/OSSRH-321 Site descriptor does not get signed --- Key: MGPG-19 URL: http://jira.codehaus.org/browse/MGPG-19 Project: Maven 2.x GPG Plugin Issue Type: Bug Affects Versions: 1.0-alpha-4 Reporter: Stephen Connolly Priority: Blocker When the site descriptor is an attached artifact, the GPG signature is not generated. Steps to reproduce: svn co https://svn.apache.org/repos/asf/maven/surefire/tags/surefire-...@898285 surefire-2.5 cd surefire-2.5 mvn site:attach-descriptor gpg:sign -Papache-release -N ls target/*.asc if there is a surefire-2.5-site.xml.asc then this bug is fixed. -- 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] Reopened: (MAVENUPLOAD-2572) upload new version 0.8.90 of tango-icon-theme, note license and groupId have changed
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2572?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Heuer reopened MAVENUPLOAD-2572: The URL above works for me. upload new version 0.8.90 of tango-icon-theme, note license and groupId have changed Key: MAVENUPLOAD-2572 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2572 Project: Maven Upload Requests Issue Type: Wish Reporter: Michael Heuer Assignee: Carlos Sanchez The Tango Desktop Project exists to help create a consistent graphical user interface experience for free and Open Source software. The Tango icon theme is a basic set of desktop icons that follow the style guidelines. The set has been created as a proof of concept for the style, but works rather well as a replacement for the base theme under GNOME and KDE. -- 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: (MAVENUPLOAD-2572) upload new version 0.8.90 of tango-icon-theme, note license and groupId have changed
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2572?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=199173#action_199173 ] Michael Heuer commented on MAVENUPLOAD-2572: Great, thanks Carlos. upload new version 0.8.90 of tango-icon-theme, note license and groupId have changed Key: MAVENUPLOAD-2572 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2572 Project: Maven Upload Requests Issue Type: Wish Reporter: Michael Heuer Assignee: Carlos Sanchez The Tango Desktop Project exists to help create a consistent graphical user interface experience for free and Open Source software. The Tango icon theme is a basic set of desktop icons that follow the style guidelines. The set has been created as a proof of concept for the style, but works rather well as a replacement for the base theme under GNOME and KDE. -- 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-2572) upload new version 0.8.90 of tango-icon-theme, note license and groupId have changed
upload new version 0.8.90 of tango-icon-theme, note license and groupId have changed Key: MAVENUPLOAD-2572 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2572 Project: Maven Upload Requests Issue Type: Wish Reporter: Michael Heuer The Tango Desktop Project exists to help create a consistent graphical user interface experience for free and Open Source software. The Tango icon theme is a basic set of desktop icons that follow the style guidelines. The set has been created as a proof of concept for the style, but works rather well as a replacement for the base theme under GNOME and KDE. -- 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] Reopened: (ARCHETYPE-70) Add project description as a mojo parameter
[
http://jira.codehaus.org/browse/ARCHETYPE-70?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Heuer reopened ARCHETYPE-70:
I am re-opening this issue because I still cannot see how to accomplish this,
with version 2.0-alpha-3. How about some documentation about how this was
addressed?
Specifically,
1) How do you define a parameter in an archetype project that must be made
accessible to Velocity templates in the archetype?
2) How do you specify a value for the new parameter when running mvn
archetype:create/generate?
Add project description as a mojo parameter
---
Key: ARCHETYPE-70
URL: http://jira.codehaus.org/browse/ARCHETYPE-70
Project: Maven Archetype
Issue Type: New Feature
Components: Plugin
Reporter: Michael Heuer
Priority: Minor
Fix For: 2.0-alpha-1
Attachments: patch.txt
For my archetype bundle, I require the project description as a parameter.
I use it in the pom.xml
description${description}/description
in a license HEADER.txt
/*
${artifactId} ${description}
Copyright ...
in a package.html
html
body
p${description}/p
/body
/html
and so on.
The attached patch to MavenArchetypeMojo.java provides a project description
parameter in addition to project groupId, artifactId, and version:
$ mvn -X archetype:create
-DgroupId=foo
-DartifactId=bar
-Dversion=1.0-SNAPSHOT
-Ddescription=bar description. ...
--
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: (ARCHETYPE-70) Add project description as a mojo parameter
[
http://jira.codehaus.org/browse/ARCHETYPE-70?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_107698
]
Michael Heuer commented on ARCHETYPE-70:
What about the fix for the current version?
The patch provided is very simple and causes no problems if a project
description parameter is not provided.
If it would help get this fix committed, I might also be able to contribute a
simple unit test, patches to documentation, etc.
Add project description as a mojo parameter
---
Key: ARCHETYPE-70
URL: http://jira.codehaus.org/browse/ARCHETYPE-70
Project: Maven Archetype
Issue Type: New Feature
Components: Plugin
Reporter: Michael Heuer
Priority: Minor
Attachments: patch.txt
For my archetype bundle, I require the project description as a parameter.
I use it in the pom.xml
description${description}/description
in a license HEADER.txt
/*
${artifactId} ${description}
Copyright ...
in a package.html
html
body
p${description}/p
/body
/html
and so on.
The attached patch to MavenArchetypeMojo.java provides a project description
parameter in addition to project groupId, artifactId, and version:
$ mvn -X archetype:create
-DgroupId=foo
-DartifactId=bar
-Dversion=1.0-SNAPSHOT
-Ddescription=bar description. ...
--
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-70) Add project description as a mojo parameter
Add project description as a mojo parameter
---
Key: ARCHETYPE-70
URL: http://jira.codehaus.org/browse/ARCHETYPE-70
Project: Maven Archetype
Issue Type: New Feature
Components: Plugin
Reporter: Michael Heuer
Priority: Minor
Attachments: patch.txt
For my archetype bundle, I require the project description as a parameter.
I use it in the pom.xml
description${description}/description
in a license HEADER.txt
/*
${artifactId} ${description}
Copyright ...
in a package.html
html
body
p${description}/p
/body
/html
and so on.
The attached patch to MavenArchetypeMojo.java provides a project description
parameter in addition to project groupId, artifactId, and version:
$ mvn -X archetype:create
-DgroupId=foo
-DartifactId=bar
-Dversion=1.0-SNAPSHOT
-Ddescription=bar description. ...
--
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-1386) new version to upload, groupId=org.tango-project artifactId=tango-icon-theme version=0.8.0
new version to upload, groupId=org.tango-project artifactId=tango-icon-theme version=0.8.0 -- Key: MAVENUPLOAD-1386 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1386 Project: maven-upload-requests Issue Type: Task Reporter: Michael Heuer The Tango Desktop Project exists to create a consistent user experience for free and Open Source software with graphical user interfaces. -- 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
