I've got something locally here that does just that i.e. update the file that's there (if there), otherwise generate from scratch - got it working for the .project file, thinking about the .classpath one at the moment - bit more stuff in that one. It uses jstl to do the work, and would therefore suit those folks that want to make changes and store the files in source control, and those that want to generate them.
I'll submit something very soon. > -----Original Message----- > From: J�rg Schaible [mailto:[EMAIL PROTECTED] > Sent: 12 May 2004 16:46 > To: Maven Users List > Subject: RE: Suggested Eclipse Plugin Extension > > Maczka Michal wrote on Wednesday, May 12, 2004 5:12 PM: > > 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). > > Well, keeping the dependencies in sync is pain, but you're > basically right, the plugin should just *upate* the > dependencies and the classpath and not necessarily creating anything. > > Regards, > J�rg > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
