[jira] (MANTTASKS-244) access (build) plugins configuration section from ant task
cforce created MANTTASKS-244: Summary: access (build) plugins configuration section from ant task Key: MANTTASKS-244 URL: https://jira.codehaus.org/browse/MANTTASKS-244 Project: Maven Ant Tasks Issue Type: New Feature Reporter: cforce We would like to read aspectj plugin (http://mojo.codehaus.org/aspectj-maven-plugin/) weaveDependencies list and aspectLibraries list to be able to know how to instrumnet aspectj build in ant using dependency managment from maven -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MANTTASKS-243) Motion Chart does not show graphic view when browsing on https
cforce created MANTTASKS-243: Summary: Motion Chart does not show graphic view when browsing on https Key: MANTTASKS-243 URL: https://jira.codehaus.org/browse/MANTTASKS-243 Project: Maven Ant Tasks Issue Type: Bug Environment: SonarQube Version 3.7, Motion Chart 1.5, Windows Service on 2008 srv Reporter: cforce When we call the web frontend dashbaord with motion charts on http it works but on https(verisign cert) there are no charts rendered - flash it not loaded in the widget for the graphics. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MANTTASKS-243) Motion Chart does not show graphic view when browsing on https
[ https://jira.codehaus.org/browse/MANTTASKS-243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=333884#comment-333884 ] cforce commented on MANTTASKS-243: -- Sory, worng category, but can't move or change away from manttasks. Motion Chart does not show graphic view when browsing on https Key: MANTTASKS-243 URL: https://jira.codehaus.org/browse/MANTTASKS-243 Project: Maven Ant Tasks Issue Type: Bug Environment: SonarQube Version 3.7, Motion Chart 1.5, Windows Service on 2008 srv Reporter: cforce When we call the web frontend dashbaord with motion charts on http it works but on https(verisign cert) there are no charts rendered - flash it not loaded in the widget for the graphics. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MANTTASKS-243) Motion Chart does not show graphic view when browsing on https
[ https://jira.codehaus.org/browse/MANTTASKS-243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] cforce updated MANTTASKS-243: - Description: When we call the web frontend dashbaord with motion charts on http it works but on https(verisign cert) there are no charts rendered - flash it not loaded in the widget for the graphics. Instead i se circle for loading any data all the waym without sucessfully loading it. was:When we call the web frontend dashbaord with motion charts on http it works but on https(verisign cert) there are no charts rendered - flash it not loaded in the widget for the graphics. Motion Chart does not show graphic view when browsing on https Key: MANTTASKS-243 URL: https://jira.codehaus.org/browse/MANTTASKS-243 Project: Maven Ant Tasks Issue Type: Bug Environment: SonarQube Version 3.7, Motion Chart 1.5, Windows Service on 2008 srv Reporter: cforce When we call the web frontend dashbaord with motion charts on http it works but on https(verisign cert) there are no charts rendered - flash it not loaded in the widget for the graphics. Instead i se circle for loading any data all the waym without sucessfully loading it. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MANTTASKS-177) artifact:dependencies ignores settings-security.xml and sends password hash to repository
[
https://jira.codehaus.org/browse/MANTTASKS-177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=328787#comment-328787
]
cforce commented on MANTTASKS-177:
--
Are there any beta build artefact`s for download?
Will this ever be released??
How can a MAJOR bug be on track this 5 MONTHS!!!
artifact:dependencies ignores settings-security.xml and sends password hash
to repository
-
Key: MANTTASKS-177
URL: https://jira.codehaus.org/browse/MANTTASKS-177
Project: Maven 2.x Ant Tasks
Issue Type: Bug
Components: dependencies task
Affects Versions: 2.1.0
Environment: Mac OS X, Ant 1.7.1, Maven 2.2.1, maven-ant-tasks 2.1.0,
Sonatype Nexus Open Source Edition 1.5.0
Reporter: Ross Mellgren
Assignee: Olivier Lamy
Fix For: 3.0.0-beta-1
Attachments: decrypt.patch
I have a mirror repository configured in .m2/settings.xml, and its server
entry uses an encrypted password in password, using the master password set
in .m2/settings-security.xml.
I followed this guide:
http://maven.apache.org/guides/mini/guide-encryption.html
I get authentication errors every time i use
{code:xml}
?xml version=1.0 ?
settings
mirrors
mirror
idpaytronix-public/id
urlhttps://greylock.corp.paytronix.com/nexus/content/groups/public/url
mirrorOf*/mirrorOf
/mirror
/mirrors
servers
server
idpaytronix-public/id
usernamermellgren/username
!-- password element omitted --
/server
/servers
/settings
{code}
I switched to http and then used tcpdump to watch the request, then decoded
the Authorization header. The {mumblemumble} password hash was sent not the
decrypted password.
Looking into maven-ant-tasks.jar, I see a META-INF/plexus/components.xml
which does not include plexus-sec-dispatcher from maven-core. I tried
spinning my own copy of maven-ant-tasks with the appropriate component for
plexus-sec-dispatcher added, but it didn't work, so I think I'm out of my
depth in the troubleshooting/rectification department.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MRELEASE-138) release:prepare fails when checking in modified POMs of a multi-modules project
[
https://jira.codehaus.org/browse/MRELEASE-138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=327111#comment-327111
]
cforce commented on MRELEASE-138:
-
I wanna checkout my code from multiple modules! Arg, will this ever be
solved
release:prepare fails when checking in modified POMs of a multi-modules
project
---
Key: MRELEASE-138
URL: https://jira.codehaus.org/browse/MRELEASE-138
Project: Maven 2.x Release Plugin
Issue Type: Bug
Components: scm
Affects Versions: 2.0-beta-4
Environment: WinXP + Eclipse
Reporter: ol
Assignee: Robert Scholte
Priority: Critical
Attachments: MRELEASE-138.patch
Here is the project structure on the disk :
{noformat}
c:\javadev\prj\myproject\module1
c:\javadev\prj\myproject\module2
c:\javadev\prj\myproject\master
{noformat}
These 3 folders represent the 3 eclipse projects, each one containing a
pom.xml.
The master project's pom is the parent of the modules.
When I execute the release:prepare goal, Everything works fine (it asks to me
the tag name, the next dev version, ...) until I receive this error :
{noformat}
[INFO] Checking in modified POMs...
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] An error is occurred in the checkin process:
C:\javadev\prj\myproject\module1\pom.xml was not contained in
C:\javadev\prj\myproject\master
[INFO]
[DEBUG] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: An error is occurred
in the checkin process: C:\javadev\prj\myproject\module1\pom.xml was not
contained in C:\javadev\prj\myproject\master
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:559)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:488)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:458)
{noformat}
The problem is that the project structure is the only one that can be used
with eclipse.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MRELEASE-261) release:prepare should support flat directory multi-module projects
[ https://jira.codehaus.org/browse/MRELEASE-261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=327110#comment-327110 ] cforce commented on MRELEASE-261: - I wanna checkout my code from multiple modules! Arg, will this ever be solved release:prepare should support flat directory multi-module projects --- Key: MRELEASE-261 URL: https://jira.codehaus.org/browse/MRELEASE-261 Project: Maven 2.x Release Plugin Issue Type: Improvement Components: prepare Environment: linux / maven2 / svn Reporter: paul.whe...@gmail.com Assignee: Maria Odea Ching Fix For: 2.0 Attachments: flatProject.main.patch, flatProject.test.patch, maven-release-issue.tar.gz, maven-release-issue.zip, MRELEASE-261.patch, MRELEASE-261-sample-project.zip, MRELEASE-261-with-its.patch, MRELEASE-261-with-its-v3.patch, odd-tags.png, PrepareReleaseMojo.patch What I mean by flat file structure firstly. parent/pom.xml module1/pom.xml module2/pom.xml . . . module15/pom.xml the parent references the modules like so modules module../module1/module module../module2/module . . . module../module15/module /modules When i release:prepare only the parent project is tagged the modules projects versions are incremented etc but the modules are not tagged in svn. I use this structure as i use eclipse as my IDE. I would love to see a fix for the issue marked as closed here http://jira.codehaus.org/browse/MRELEASE-138. I am currenrly tagging by hand each submodule of the projects but it would be so nice to have the release plugin do this for me. forgive my english. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MNG-3472) configuration possibilities to limit size of local repository
[ https://jira.codehaus.org/browse/MNG-3472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=313161#comment-313161 ] cforce commented on MNG-3472: - I think maven should provide at least the method to be able t purge the local repository similar to the nexus server option (number of snapshots, release and days to keep, delete spnaphosts if released), also this job must be triggered from external tool, like ej. jenkins or devscript. Would be great if someone can posts plugin or scripts which can do such work in the meantime. Pleas repopen this issue. configuration possibilities to limit size of local repository - Key: MNG-3472 URL: https://jira.codehaus.org/browse/MNG-3472 Project: Maven 2 3 Issue Type: Improvement Components: Settings Affects Versions: 2.0.8 Reporter: manuel aldana it would be great to make repository-size configurable, for instance by setting the maximum number of downloads of a snapshot-version to be kept. thus the explosion of local repository size can be reduced. especially when you are working with many in-house multi-module projects which are marked as snapshots before released , can increase repository size significantly. see mailing-list discussion: http://www.nabble.com/limit-size-of-local-repository%2C-limit-number-of-snapshots-td16147475s177.html -- 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] (MNG-3472) configuration possibilities to limit size of local repository
[ https://jira.codehaus.org/browse/MNG-3472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=313161#comment-313161 ] cforce edited comment on MNG-3472 at 11/8/12 9:51 AM: -- I think maven should provide at least the method to be able t purge the local repository similar to the nexus server option (number of snapshots, release and days to keep, delete spnaphosts if released), also this job must be triggered from external tool, like ej. jenkins or devscript. Would be great if someone can posts plugin or scripts which can do such work in the meantime. Here is my answer: http://stackoverflow.com/questions/1308263/wiping-out-maven-local-repository-on-build-machine Pleas repopen this issue. was (Author: cforce): I think maven should provide at least the method to be able t purge the local repository similar to the nexus server option (number of snapshots, release and days to keep, delete spnaphosts if released), also this job must be triggered from external tool, like ej. jenkins or devscript. Would be great if someone can posts plugin or scripts which can do such work in the meantime. Pleas repopen this issue. configuration possibilities to limit size of local repository - Key: MNG-3472 URL: https://jira.codehaus.org/browse/MNG-3472 Project: Maven 2 3 Issue Type: Improvement Components: Settings Affects Versions: 2.0.8 Reporter: manuel aldana it would be great to make repository-size configurable, for instance by setting the maximum number of downloads of a snapshot-version to be kept. thus the explosion of local repository size can be reduced. especially when you are working with many in-house multi-module projects which are marked as snapshots before released , can increase repository size significantly. see mailing-list discussion: http://www.nabble.com/limit-size-of-local-repository%2C-limit-number-of-snapshots-td16147475s177.html -- 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] (MNG-5237) Cannot download maven dependencies through proxy
[ https://jira.codehaus.org/browse/MNG-5237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=300503#comment-300503 ] cforce commented on MNG-5237: - Yes, actually we use NTLM proxy! Please fix this! Cannot download maven dependencies through proxy Key: MNG-5237 URL: https://jira.codehaus.org/browse/MNG-5237 Project: Maven 2 3 Issue Type: Bug Components: Dependencies Affects Versions: 3.0.4 Environment: windows xp64 using cygwin Reporter: Niels Mordt-Ostergaard Assignee: Jason van Zyl Using proxy in settings.xml, I was able to download maven dependencies in 3.0.3, but this seems to be broken with 3.0.4: Proxy definition in settings.xml (hidden ip adress below, but correct proxy ip on my system): proxies proxy idoptional/id activetrue/active protocolhttp/protocol username/username password/password hostxxx.xx.xx.xx/host port8080/port nonProxyHostslocalhost|127.0.0.1/nonProxyHosts /proxy /proxies Output from 3.0.3: $ mvn -V clean Apache Maven 3.0.3 (r1075438; 2011-02-28 18:31:09+0100) Maven home: C:\Program Files\apache-maven-3.0.3 Java version: 1.6.0_24, vendor: Sun Microsystems Inc. Java home: C:\Program Files\Java\jdk1.6.0_24\jre Default locale: no_NO, platform encoding: Cp1252 OS name: windows xp, version: 5.2, arch: amd64, family: windows [INFO] Scanning for projects... [INFO] [INFO] [INFO] Building xxx hidden xxx [INFO] Downloading: http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-clean-plugin/2.4.1/maven-clean-plugin-2.4.1.pom Downloaded: http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-clean-plugin/2.4.1/maven-clean-plugin-2.4.1.pom (5 KB at 4.9 KB/sec) . and so on... Output from 3.0.4: $ mvn -V clean Apache Maven 3.0.4 (r1232337; 2012-01-17 09:44:56+0100) Maven home: C:\Program Files\apache-maven-3.0.4 Java version: 1.6.0_24, vendor: Sun Microsystems Inc. Java home: C:\Program Files\Java\jdk1.6.0_24\jre Default locale: no_NO, platform encoding: Cp1252 OS name: windows xp, version: 5.2, arch: amd64, family: windows [INFO] Scanning for projects... [INFO] [INFO] [INFO] Building xxx hidden xxx [INFO] Downloading: http://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-clean-plugin/2.4.1/maven-clean-plugin-2.4.1.pom [INFO] [INFO] BUILD FAILURE [INFO] [INFO] Total time: 0.390s [INFO] Finished at: Fri Feb 03 13:14:35 CET 2012 [INFO] Final Memory: 5M/490M [INFO] [ERROR] Plugin org.apache.maven.plugins:maven-clean-plugin:2.4.1 or one of its dependencies could not be resolved: Failed to read artifact descriptor for org.apache.maven.plugins:maven-clean-plugin:jar:2.4.1: Could not transfer artifact org.apache.maven.plugins:maven-clean-plugin:pom:2.4.1 from/to central (http://repo.maven.apache.org/maven2): Access denied to: http://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-clean-plugin/2.4.1/maven-clean-plugin-2.4.1.pom, ReasonPhrase:Forbidden. - [Help 1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/PluginResolutionException -- 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] (MNG-5237) Cannot download maven dependencies through proxy
[ https://jira.codehaus.org/browse/MNG-5237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=298075#comment-298075 ] cforce commented on MNG-5237: - We are using Windows XP and also configured proxy in settings.xml on Maven 3.04. It look likes Maven is not using the proxy settings from M2-Home/conf/settings.xml but the one from windows (Internet explorer). If its configured in ie it works, if not then not. If i configure the same in maven settings.xml it does make any difference. For notice: In oor case the m2 server (nexus mirror) is in noproxy string of our enterprise proxy config. We get some kind of socks connection error. Cannot download maven dependencies through proxy Key: MNG-5237 URL: https://jira.codehaus.org/browse/MNG-5237 Project: Maven 2 3 Issue Type: Bug Components: Dependencies Affects Versions: 3.0.4 Environment: windows xp64 using cygwin Reporter: Niels Mordt-Ostergaard Using proxy in settings.xml, I was able to download maven dependencies in 3.0.3, but this seems to be broken with 3.0.4: Proxy definition in settings.xml (hidden ip adress below, but correct proxy ip on my system): proxies proxy idoptional/id activetrue/active protocolhttp/protocol username/username password/password hostxxx.xx.xx.xx/host port8080/port nonProxyHostslocalhost|127.0.0.1/nonProxyHosts /proxy /proxies Output from 3.0.3: $ mvn -V clean Apache Maven 3.0.3 (r1075438; 2011-02-28 18:31:09+0100) Maven home: C:\Program Files\apache-maven-3.0.3 Java version: 1.6.0_24, vendor: Sun Microsystems Inc. Java home: C:\Program Files\Java\jdk1.6.0_24\jre Default locale: no_NO, platform encoding: Cp1252 OS name: windows xp, version: 5.2, arch: amd64, family: windows [INFO] Scanning for projects... [INFO] [INFO] [INFO] Building xxx hidden xxx [INFO] Downloading: http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-clean-plugin/2.4.1/maven-clean-plugin-2.4.1.pom Downloaded: http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-clean-plugin/2.4.1/maven-clean-plugin-2.4.1.pom (5 KB at 4.9 KB/sec) . and so on... Output from 3.0.4: $ mvn -V clean Apache Maven 3.0.4 (r1232337; 2012-01-17 09:44:56+0100) Maven home: C:\Program Files\apache-maven-3.0.4 Java version: 1.6.0_24, vendor: Sun Microsystems Inc. Java home: C:\Program Files\Java\jdk1.6.0_24\jre Default locale: no_NO, platform encoding: Cp1252 OS name: windows xp, version: 5.2, arch: amd64, family: windows [INFO] Scanning for projects... [INFO] [INFO] [INFO] Building xxx hidden xxx [INFO] Downloading: http://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-clean-plugin/2.4.1/maven-clean-plugin-2.4.1.pom [INFO] [INFO] BUILD FAILURE [INFO] [INFO] Total time: 0.390s [INFO] Finished at: Fri Feb 03 13:14:35 CET 2012 [INFO] Final Memory: 5M/490M [INFO] [ERROR] Plugin org.apache.maven.plugins:maven-clean-plugin:2.4.1 or one of its dependencies could not be resolved: Failed to read artifact descriptor for org.apache.maven.plugins:maven-clean-plugin:jar:2.4.1: Could not transfer artifact org.apache.maven.plugins:maven-clean-plugin:pom:2.4.1 from/to central (http://repo.maven.apache.org/maven2): Access denied to: http://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-clean-plugin/2.4.1/maven-clean-plugin-2.4.1.pom, ReasonPhrase:Forbidden. - [Help 1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/PluginResolutionException -- 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-2802) Concurrent-safe access to local Maven repository
[ https://jira.codehaus.org/browse/MNG-2802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=278089#comment-278089 ] cforce commented on MNG-2802: - This issue hits us most on a Jenkins buidl server, where all Maven builds use same repo folder. Having many dupes of local repos will use a lot of local hard disk space. Maybe there is a Maven Jenkins Plugin for Jenkins which coordinates the Concurrent access? Concurrent-safe access to local Maven repository Key: MNG-2802 URL: https://jira.codehaus.org/browse/MNG-2802 Project: Maven 2 3 Issue Type: Improvement Components: Artifacts and Repositories Reporter: Stepan Roh Assignee: John Casey Fix For: Issues to be reviewed for 3.x It seems that access to local Maven repository is not concurrent-safe that is multiple Mavens running in parallel may damage contents of local Maven repository. It would be a nice improvement, because sharing of local repository will lower the need for contacting any other repository. I know that Maven proxy can be used, but that adds another layer which may unnecessarily stress the machine it runs on. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MRELEASE-647) Error on SVN tagging in Maven release
Error on SVN tagging in Maven release -- Key: MRELEASE-647 URL: http://jira.codehaus.org/browse/MRELEASE-647 Project: Maven 2.x Release Plugin Issue Type: Bug Environment: Wiondows Server 2008, Tomcat 7, Jenkis 1.3.9.6 + Hudson Maven Release Plug-in Plug-in 0.6.1, Maven 3 Reporter: cforce Checking out from the scm (https://sid-repo.de/svn/e2etrace/trunk ) does work and regular svn tag from hdsuon also, only tagging via mave release plugin faults with following error. Tomcat is running on local user account not system account. The scm server is using a self signed certficate. Manual Svn (SlikSVN 1.6.12 is installed) update from cmd prompt console as local user in workspace does work without problems. [INFO] [INFO] BUILD FAILURE [INFO] [INFO] Total time: 17.547s [INFO] Finished at: Tue Feb 08 14:49:11 CET 2011 [INFO] Final Memory: 14M/309M [INFO] mavenExecutionResult exceptions not empty org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-release-plugin:2.0:prepare (default-cli) on project e2etrace: Unable to tag SCM Provider message: The svn tag command failed. Command output: svn: Can't connect to host 'sid-repo.de': No connection could be made because the target machine actively refused it. at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:199) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:148) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:140) 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:314) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:151) at org.jvnet.hudson.maven3.launcher.Maven3Launcher.main(Maven3Launcher.java:79) 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.launchStandard(Launcher.java:329) at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:239) at org.jvnet.hudson.maven3.agent.Maven3Main.launch(Maven3Main.java:145) at hudson.maven.Maven3Builder.call(Maven3Builder.java:124) at hudson.maven.Maven3Builder.call(Maven3Builder.java:71) at hudson.remoting.UserRequest.perform(UserRequest.java:114) at hudson.remoting.UserRequest.perform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:270) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:619) Caused by: org.apache.maven.plugin.MojoFailureException: Unable to tag SCM Provider message: The svn tag command failed. Command output: svn: Can't connect to host 'sid-repo.de': No connection could be made because the target machine actively refused it. at org.apache.maven.plugins.release.PrepareReleaseMojo.prepareRelease(PrepareReleaseMojo.java:219) at org.apache.maven.plugins.release.PrepareReleaseMojo.execute(PrepareReleaseMojo.java:181) at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:107) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:195) ... 27 more Caused by: org.apache.maven.shared.release.scm.ReleaseScmCommandException: Unable to tag SCM Provider message: The svn tag command failed. Command output: svn: Can't connect to host 'sid-repo.de': No connection could be made because the target machine actively refused it. at
[jira] Commented: (MRELEASE-647) Error on SVN tagging in Maven release
[ http://jira.codehaus.org/browse/MRELEASE-647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=255060#action_255060 ] cforce commented on MRELEASE-647: - Tortoise checkout and copy from trunk to tags folder on server https://sid-repo.de/svn/e2etrace also works without porblems Error on SVN tagging in Maven release -- Key: MRELEASE-647 URL: http://jira.codehaus.org/browse/MRELEASE-647 Project: Maven 2.x Release Plugin Issue Type: Bug Environment: Wiondows Server 2008, Tomcat 7, Jenkis 1.3.9.6 + Hudson Maven Release Plug-in Plug-in 0.6.1, Maven 3 Reporter: cforce Checking out from the scm (https://sid-repo.de/svn/e2etrace/trunk ) does work and regular svn tag from hdsuon also, only tagging via mave release plugin faults with following error. Tomcat is running on local user account not system account. The scm server is using a self signed certficate. Manual Svn (SlikSVN 1.6.12 is installed) update from cmd prompt console as local user in workspace does work without problems. [INFO] [INFO] BUILD FAILURE [INFO] [INFO] Total time: 17.547s [INFO] Finished at: Tue Feb 08 14:49:11 CET 2011 [INFO] Final Memory: 14M/309M [INFO] mavenExecutionResult exceptions not empty org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-release-plugin:2.0:prepare (default-cli) on project e2etrace: Unable to tag SCM Provider message: The svn tag command failed. Command output: svn: Can't connect to host 'sid-repo.de': No connection could be made because the target machine actively refused it. at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:199) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:148) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:140) 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:314) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:151) at org.jvnet.hudson.maven3.launcher.Maven3Launcher.main(Maven3Launcher.java:79) 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.launchStandard(Launcher.java:329) at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:239) at org.jvnet.hudson.maven3.agent.Maven3Main.launch(Maven3Main.java:145) at hudson.maven.Maven3Builder.call(Maven3Builder.java:124) at hudson.maven.Maven3Builder.call(Maven3Builder.java:71) at hudson.remoting.UserRequest.perform(UserRequest.java:114) at hudson.remoting.UserRequest.perform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:270) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:619) Caused by: org.apache.maven.plugin.MojoFailureException: Unable to tag SCM Provider message: The svn tag command failed. Command output: svn: Can't connect to host 'sid-repo.de': No connection could be made because the target machine actively refused it. at org.apache.maven.plugins.release.PrepareReleaseMojo.prepareRelease(PrepareReleaseMojo.java:219) at org.apache.maven.plugins.release.PrepareReleaseMojo.execute(PrepareReleaseMojo.java:181) at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:107) at
