Message:
The following issue has been closed.
Resolver: Brett Porter
Date: Tue, 30 Dec 2003 9:55 PM
do you mean when placed in the unpacked plugins directory?
I don't think that should be allowed necessarily as that directory can get toasted,
for example by thte bootstrap (although so does $MAVEN_HOME/plugins).
Not being able to write to $MAVEN_HOME is a wider issue for plugin installation and
requires a further look. I'll open a new issue.
---------------------------------------------------------------------
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-435
Here is an overview of the issue:
---------------------------------------------------------------------
Key: MAVEN-435
Summary: jar files placed in plugins directory are not auto expanded
Type: Bug
Status: Closed
Priority: Major
Resolution: WON'T FIX
Original Estimate: Unknown
Time Spent: Unknown
Remaining: Unknown
Project: maven
Components:
plugin manager
Fix Fors:
1.1
Versions:
1.0-beta-10
Assignee:
Reporter: dion gillard
Created: Mon, 19 May 2003 12:43 AM
Updated: Tue, 30 Dec 2003 9:55 PM
Environment: Win2k, Maven cvs HEAD as of 2003-05-19.
Description:
if a new plugin jar file is placed in the plugins directory. It sits there and is not
expanded. If the file is moved to %MAVEN_HOME%\plugins, it is expanded into the
maven.local.home/plugins directory.
Given a user may not have write access to %MAVEN_HOME% this seems strange.
---------------------------------------------------------------------
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]
