> -----Original Message----- > From: M.-Leander Reimer [mailto:[EMAIL PROTECTED] > Sent: Wednesday, May 12, 2004 4:59 PM > To: Maven Users List > Subject: Suggested Eclipse Plugin Extension > > > Hi there, > > I just got the source for the Eclipse plugin from CVS and discovered > that I can already define additional "natures", which I really need. > There is another possible extension I would find useful. > > Problem: I am using the Together UML eclipse plugin, which requires > additional settings in the .project file, e.g. a directory where it > stores its model files, like > > <designRoot path="src/model"> > </designRoot> > > Solution: Would it be possible to include a custom merge file > that could > hold such information at the end of the project.jelly file > (just before > the closing </projectDescription>), like > > <j:import file="${maven.eclipse.projectmerge}" inherit="true"/> > > Well it works for me :-) , so the question is, would it be > possible to > include this permanently into the Maven eclipse plugins source?? >
Isn't it just much simpler to keep .project .classpath files in the CVS. .project file is even not changing that often (to my knowlegde almost never). I don't think that polution of maven's project.properties files with dozen of configuration settings for generating eclipse project descrptors makes much sense. You are in addition proposing even custom project.jelly file which in fact makes it even more complicated to maintain. Why would you prefer to keep in cvs project.jelly and not directly .project file? Michal --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
