maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brett Porter (JIRA)" <j...@codehaus.org>
Subject [jira] Commented: (MRELEASE-406) release:perform ignores environment variables
Date Wed, 29 Sep 2010 15:03:33 GMT

    [ http://jira.codehaus.org/browse/MRELEASE-406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=236854#action_236854
] 

Brett Porter commented on MRELEASE-406:
---------------------------------------

I tried this with Maven 2.0.10 + 2.0-beta-8; 2.0.10 + 2.0; 3.0-RC3 + 2.0 - no problems on
any of them.

I put your settings.xml into ~/.m2, removed the local repository, and ran the command you
gave against the POM. I had to modify the settings to user /internal instead of /central as
I'm using Archiva, but the env var was used. In the POM I used a different SVN repository
in the SCM element and I changed the deployment URL to ${env.proxyURL}/test which worked for
deployment too.

There's a possibility this is Windows specific, so I'll have to try it there. Have you tried
with more recent versions of Maven and/or the release plugin?



> release:perform ignores environment variables
> ---------------------------------------------
>
>                 Key: MRELEASE-406
>                 URL: http://jira.codehaus.org/browse/MRELEASE-406
>             Project: Maven 2.x Release Plugin
>          Issue Type: Bug
>          Components: perform
>    Affects Versions: 2.0-beta-8
>         Environment: WinXP Maven 2.0.9
>            Reporter: James Nord
>            Assignee: Brett Porter
>            Priority: Blocker
>         Attachments: mvn2.0.10.log, mvn2.0.10_debug.log, mvn2.1.0-RC3.log, pom.xml, settings.xml
>
>
> Our settings.xml is shared across many sites and we use reository mirrors at each of
our sites.
> The mirrors are setup in the settings.xml as ${proxyURL}/repopath
> the users set an environment variable to point to the nexus cache at their paticular
site -
>  eg http://maven-proxy-east.mycorp.com/nexus/content/repositories
> This woks fine for normal working (compile, site deploy etc..)  but release:perform fails
as it tries to download from
> ${proxyURL}/central/org/apache/mave....
> It would appear that environment variables are not passed to the forked process doing
the release.
> -- settings.xml snippet --
> 		<mirror>
> 			<id>central-mirror</id>
> 			<name>Maven Central [nexus mirror]</name>
> 			<url>${proxyURL}/central</url>
> 			<mirrorOf>central</mirrorOf>
> 		</mirror>
> -- end settings.xml snippet --
> output from release:perfrom
> D:\workspaces\TestProject>set | grep proxyURL
> proxyURL=http://maven-proxy-east.mycorp.com/nexus/content/repositories
> D:\workspaces\TestProject>mvn release:perform
> [INFO] Scanning for projects...
> [INFO] Searching repository for plugin with prefix: 'release'.
> [INFO] ------------------------------------------------------------------------
> [INFO] Building Test Project
> [INFO]    task-segment: [release:perform] (aggregator-style)
> [INFO] ------------------------------------------------------------------------
> [INFO] [release:perform]
> [INFO] Checking out the project to perform the release ...
> [INFO] Executing: cmd.exe /X /C "svn --non-interactive checkout https://svnserver.mycorp.com/repos/scratch/tags/testproj-0.0.1
> checkout"
> [INFO] Working directory: D:\workspaces\TestProject\target
> [INFO] Executing goals 'deploy site-deploy'...
> [WARNING] Maven will be executed in interactive mode, but no input stream has been configured
for this MavenInvoker inst
> ance.
> [INFO] [INFO] Scanning for projects...
> [INFO] [INFO] ------------------------------------------------------------------------
> [INFO] [INFO] Building Test Project
> [INFO] [INFO]    task-segment: [deploy, site-deploy]
> [INFO] [INFO] ------------------------------------------------------------------------
> [INFO] Downloading: ${proxyURL}/releases/org/apache/maven/plugins/maven-deploy-plugin/2.4/maven-deploy-plugin-2.4.pom
> [INFO] Downloading: ${proxyURL}/central/org/apache/maven/plugins/maven-deploy-plugin/2.4/maven-deploy-plugin-2.4.pom
> [INFO] Downloading: ${proxyURL}/releases/org/apache/maven/plugins/maven-deploy-plugin/2.4/maven-deploy-plugin-2.4.pom
> [INFO] Downloading: ${proxyURL}/thirdparty/org/apache/maven/plugins/maven-deploy-plugin/2.4/maven-deploy-plugin-2.4.pom
> [INFO] Downloading: ${proxyURL}/central/org/apache/maven/plugins/maven-deploy-plugin/2.4/maven-deploy-plugin-2.4.pom
> [INFO] Downloading: ${proxyURL}/codehaus/org/apache/maven/plugins/maven-deploy-plugin/2.4/maven-deploy-plugin-2.4.pom
> [INFO] Downloading: ${proxyURL}/java.net/org/apache/maven/plugins/maven-deploy-plugin/2.4/maven-deploy-plugin-2.4.pom
> [INFO] Downloading: ${proxyURL}/jboss/org/apache/maven/plugins/maven-deploy-plugin/2.4/maven-deploy-plugin-2.4.pom
> [INFO] [INFO] ------------------------------------------------------------------------
> [INFO] [ERROR] BUILD ERROR
> [INFO] [INFO] ------------------------------------------------------------------------
> [INFO] [INFO] Error building POM (may not be this project's POM).

-- 
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

        

Mime
View raw message