The following comment has been added to this issue:
Author: Colin Sampaleanu
Created: Wed, 6 Aug 2003 7:11 AM
Body:
Anybody have an idea about how to fix this? This is a _major_ piece of breakage that
has persisted for 7 months. Because of this issue, it is completely impossible to use
multiproject/reactor when you need to override the local repo in the project property
files. You end up getting
java.lang.ClassNotFoundException: velocity
at java.net.URLClassLoader$1.run(URLClassLoader.java:199)
There is actually another fundamental error which results in exactly the same error,
and that is changing the local repo after a set of plugins have been processed. So if
I create a new project, run
maven jar
to build it, all works fine. Then if I simply add a project property file with a local
repo override, and do
maven jar
again, I get the same ClassNotFoundException. I guess this is because the plugins
involved have already been processed and think that their dependencies have been
pulled down, and can't find them in the new local repo, which is empty. But local
repos are (should) be completely independent of the expanded plugins. Right now
anyways, there is no stated requirement that for every local repo there is a separate
expanded plugin dir.
So I think the whole fundamental way that plugin dependencies are handled should be
changed so that plugins can handle the repo changing, or alternately (a worse
solution) the link between them and the local repo should be explained better. But the
latter by itself is still not good enough without fixing the original problem
described in this bug report (that plugins do not read the override).
---------------------------------------------------------------------
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]
