Thanks dIon, this answers the question I had in MAVEN-567... So all I need to do is rm -rf the plugins directory if the repository gets cleaned out?
- Brett > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > Sent: Thursday, 7 August 2003 12:09 PM > To: [EMAIL PROTECTED] > Subject: [jira] Created: (MAVEN-659) Processed plugins can't > handle local repo changing > > > Message: > > A new issue has been created in JIRA. > > --------------------------------------------------------------------- > View the issue: > > http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-659 > > > Here is an overview of the issue: > --------------------------------------------------------------------- > Key: MAVEN-659 > Summary: Processed plugins can't handle local repo changing > Type: Bug > > Status: Unassigned > Priority: Major > > Time Spent: Unknown > Remaining: Unknown > > Project: maven > Components: > core > Fix Fors: > 1.0-final > Versions: > 1.0-beta-10 > 1.0-rc1 > > Assignee: > Reporter: dion gillard > > Created: Wed, 6 Aug 2003 9:08 PM > Updated: Wed, 6 Aug 2003 9:08 PM > > Description: > 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. > > > > > --------------------------------------------------------------------- > 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] >
