The following comment has been added to this issue:
Author: Felipe Leme
Created: Wed, 2 Feb 2005 9:44 PM
Body:
> If you can change the plugin to update an existing one rather than
> overwrite, you get that benefit too.
Do you mean adding a merge capability to the plugin? Yes, that would solve the
problem, although I have the feeling it would be pretty hard to implement (I
might be wrong though).
> If you are using a variable, each user will still need to set
> something up manually.
Yes, but that set must be done only once. In fact, it's not even necessary to
use the GUI, it's just a matter of adding some lines to a properties file on
the workspace.
> If you are using a path, each user will still have to do something
> manually to get it in the right place/change the property.
I couldn't agree less that using the path is evil. I just mention it to be
totally compatible to what Eclipse offers (besides, some companies do have
pre-defined paths, as other tools like Rational Rose might need them).
> This is the right thing to do in some cases. Too often changes are
> made to scratch an itch that are for someone's personal benefit
> rather than the wider set of users.
Yes, I know. But sometimes (not necessarily in this case) the change is generic
enough...
---------------------------------------------------------------------
View this comment:
http://jira.codehaus.org/browse/MPECLIPSE-70?page=comments#action_29528
---------------------------------------------------------------------
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: Wed, 2 Feb 2005 9:44 PM
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]
