The following comment has been added to this issue:
Author: Rogelio Robles
Created: Thu, 14 Aug 2003 10:16 PM
Body:
I need to support a closed building/deployment environment because the production
releases are built and deployed by our SCM admin team. They use a clean and closed
build box, using only officially approved tools: jdk, ant, maven.
'remote' repositories are stored in our SCM server and project stakeholders
(developers and SCM admin team) get them through snapshots when is worth to do it.
The structure that I have is this:
/root
/<scm-user-view-id>
/projectX
/component1
/component2
/component3
/thirdparty
/maven
/repo
/internal
/repo
As you can see the <scm-user-view-id> is different for all the stakeholders of the
project so I can't use hard coded absolute directory names for the repositories
location. Then I use relative URLs for references:
In component1's project.properties file I have:
maven.repo.remote=file:../../thirdparty/maven/repo, file:../../internal/repo
This produces:
Attempting to download commons-lang-1.0.1.jar.
WARNING: Failed to download commons-lang-1.0.1.jar.
And I don't get the artifacts installed in my local repository.
At the beginning I was under the impression that I can't use relative URLs, but I
tested moving the 'remote' repositories as siblings of my components, under projectX,
and everything works fine, with this:
maven.repo.remote=file:../thirdparty/maven/repo, file:../internal/repo
---------------------------------------------------------------------
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-224
Here is an overview of the issue:
---------------------------------------------------------------------
Key: MAVEN-224
Summary: remote and local repo overrides in project.properties does not work for
plugins
Type: Bug
Status: Unassigned
Priority: Major
Time Spent: Unknown
Remaining: Unknown
Project: maven
Components:
core
Fix Fors:
1.0-final
Versions:
1.0-beta-8
1.0-final
Assignee:
Reporter: Colin Sampaleanu
Created: Tue, 28 Jan 2003 2:41 PM
Updated: Sun, 3 Aug 2003 8:59 PM
Environment: cvs HEAD from 2003-1-28, win2k
Description:
It is possible to override both the local and remote repos by using entris such as the
following in a project's project.properties file:
--- from project.properties
# override remote repo since we want to also point to a cvs based remote repo
# to get some jars not found at ibiblio
maven.repo.remote=http://www.ibiblio.com/maven/,http://some.where/else/,file:../../shared/repository
# overrid local repo since we want to allow this set of related source projects
# to be built from multiple locations without conflicting
maven.repo.local=../mavenrepo
----
However, while this works for satisfying dependencies declared in the project's
project.xml file, when building that project, if using any plugins, it does not
override the repos that a plugin itself will use when trying to satisfy it's own
dependencies specified in its own project.xml file. The only solution would seem to be
to modify each plugin in the maven plugins dir to point to the correct repo,
relatively impractical since there are a lot of plugins, and they get blown away on
rebuilding maven.
---------------------------------------------------------------------
JIRA INFORMATION:
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
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
