The following comment has been added to this issue:
Author: Eric Pugh
Created: Fri, 10 Sep 2004 10:44 AM
Body:
Yeah, really we should check IF a maven_home_local exists, if so, use that. failing
that, go with maven_home. Not sure my Ant Jujitsu is up to that complex if logic..
If you can contribute a patch, that would be great.. Otherwise I'm tempted to leave
it..
I am more tempted to just use the maven plugin:install goal since we can assume that
maven_home exists then you have maven and can just call that maybe?
Eric
---------------------------------------------------------------------
View this comment:
http://opensource.atlassian.com/projects/xdoclet/browse/XDT-722?page=comments#action_14808
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/xdoclet/browse/XDT-722
Here is an overview of the issue:
---------------------------------------------------------------------
Key: XDT-722
Summary: install target in build script requires world-writable rights in maven
installation dir
Type: Bug
Status: Open
Priority: Major
Original Estimate: Unknown
Time Spent: Unknown
Remaining: Unknown
Project: XDoclet
Components:
Build Process
Maven Plugin
Versions:
1.2 Beta 3
Assignee: xdoclet-devel (Use for new issues)
Reporter: Andrew Stevens
Created: Mon, 24 Nov 2003 6:17 PM
Updated: Fri, 10 Sep 2004 10:44 AM
Environment: Linux (Mandrake 9.1), Maven versions beta 9 and RC1
Description:
In xdoclet/maven/build.xml, the install target tries to copy various files into
${env.MAVEN_HOME}/plugins and ${env.MAVEN_HOME}/repository
On my machine, I have a shared installation for Maven in
/usr/local/java/maven-{version} According to the installation instructions on
maven.apache.org, I set the MAVEN_HOME environment variable to this directory and add
$MAVEN_HOME/bin to the PATH in .bash_profile
With previous versions of Maven, I found I had I had to make the repository & plugin
directories under $MAVEN_HOME world-writeable, as Maven would try to download various
jars into there when running goals for the first time; the xdoclet build script
therefore had no problem installing the generated plugin either. However, when I
upgraded to Maven RC1 I discovered I no longer had to open up the access rights on
those directories, as Maven would download things to ~/.maven in each user's home
directory instead. Unfortunately, the XDoclet plugin build script is still trying to
copy things into the shared directories :-( This causes the XDoclet build to fail.
It would be nice if it could behave the same way Maven itself does, so I can leave the
directories read-only.
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/xdoclet/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
-------------------------------------------------------
This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170
Project Admins to receive an Apple iPod Mini FREE for your judgement on
who ports your project to Linux PPC the best. Sponsored by IBM.
Deadline: Sept. 13. Go here: http://sf.net/ppc_contest.php
_______________________________________________
xdoclet-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/xdoclet-devel
