The following comment has been added to this issue:
Author: David Eric Pugh
Created: Thu, 3 Feb 2005 11:55 AM
Body:
The fundamental solution for quite a few of these types of "customizations" is
to reuse any existing .project or .classpath files. This way the Maven Eclipse
plugin doesn't have to attempt to be all things to all people.
I have started looking at the Maven 2 MOJO Eclipse plugin, where all the logic
is done in Java. This I think would make it simpler to load up an existing xml
document, and then manipulate it to do what we need.
Anyone have an example of a Maven 2 MOJO plugin working in Maven 1?
---------------------------------------------------------------------
View this comment:
http://jira.codehaus.org/browse/MPECLIPSE-70?page=comments#action_29539
---------------------------------------------------------------------
View the issue:
http://jira.codehaus.org/browse/MPECLIPSE-70
Here is an overview of the issue:
---------------------------------------------------------------------
Key: MPECLIPSE-70
Summary: Make it possible to add linked resources
Type: Improvement
Status: Unassigned
Priority: Minor
Original Estimate: 1 hour
Time Spent: Unknown
Remaining: 1 hour
Project: maven-eclipse-plugin
Versions:
1.9
Assignee:
Reporter: Felipe Leme
Created: Wed, 2 Feb 2005 11:08 AM
Updated: Thu, 3 Feb 2005 11:55 AM
Description:
I have some projects that share some common Java files (in a ../common
directory) and I need to access that directory as a source tree (I know that
having multiple source directory is not the maven way of doing things, but
sometimes that's a need).
So, one way to do this is creating a folder on the project as a link to an
existing one in the filesystem (or to an Eclipse variable). If I do so on
Eclipse, it generates an entry like the following in .project:
<linkedResources>
<link>
<name>folder_A</name>
<type>2</type>
<location>FOLDER_VARIABLE_NAME</location>
</link>
<link>
<name>file_B</name>
<type>1</type>
<location>/folder/location/on/filesystem</location>
</link>
</linkedResources>
So, I think it would be nice to have a property (similar to what we have on the
natures element) to add such links. Something like this:
maven.eclipse.links=folderA, fileB
maven.eclipse.links.folderA.name=folder_A
maven.eclipse.links.folderA.type=2
maven.eclipse.links.folderA.location=FOLDER_VARIABLE_NAME
maven.eclipse.links.fileB.name=file_B
maven.eclipse.links.fileB.type=1
maven.eclipse.links.fileB.location=/folder/location/on/filesystem
Optional, we could eliminate the need for a type variable by using variable or
path:
maven.eclipse.links.folderA.name=folder_A
maven.eclipse.links.folderA.variable=FOLDER_VARIABLE_NAME
maven.eclipse.links.fileB.name=file_B
maven.eclipse.links.fileB.path=/folder/location/on/filesystem
<j:if test="${context.getVariable('maven.eclipse.links') != null}">
<linkedResources>
<util:tokenize var="links" delim=",">
${maven.eclipse.links}
</util:tokenize>
<j:forEach var="link" items="${links}" trim="true">
<link>
<j:set var="name" value="maven.eclipse.links.${link}.name"/>
<j:set var="type" value="maven.eclipse.links.${link}.type"/>
<j:set var="location" value="maven.eclipse.links.${link}.location"/>
<name>${context.getVariable(name)}</name>
<type>${context.getVariable(link)}</type>
<location>${context.getVariable(location)}</location>
</link>
</linkedResources>
</j:if>
-- Felipe
---------------------------------------------------------------------
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]
