[jira] Closed: (MAVEN-224) remote and local repo overrides in project.properties does not work for plugins

[ji...@codehaus.org]

Message:

   The following issue has been closed.

   Resolver: Brett Porter
       Date: Tue, 23 Mar 2004 7:24 PM

works for me in RC2. You can put project.xml overrides in project.properties for the plugin for the dependencies and the repository.

These apply to only that plugin, which is what you'd expect. A plugin should not override anything for the project.

Note that anything specified in ~/build.properties will take global precedence however
---------------------------------------------------------------------
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: Closed
   Priority: Major
 Resolution: CANNOT REPRODUCE

 Original Estimate: Unknown
 Time Spent: Unknown
  Remaining: Unknown

    Project: maven
 Components: 
             core
   Fix Fors:
             1.0-rc3
   Versions:
             1.0-beta-8
             1.0-rc3

   Assignee: 
   Reporter: Colin Sampaleanu

    Created: Tue, 28 Jan 2003 2:41 PM
    Updated: Tue, 23 Mar 2004 7:24 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: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org