[Fwd: Re: [Menda-developers] On tracking Eclipse-related goodies in CVS]
Status: Alpha
Brought to you by:
fmar
|
From: pope <apo...@ez...> - 2004-07-06 22:18:22
|
I don't know at what kind of plugins are you refering, but I am using about 10 plugins and none changed my .classpath and/or .project (except if I added AspectJ nature to a project). However I don't think there a general way to manage this files. Another solution will be to have the .classpath and .project generated from Ant with a custom task - and not the other way around as suggested in some posts ;-). (this way the 2 files will have not to be inside the CVS). But for this solution I really do not see the benefits. w8ing for opinions [Have a nice day] / [10x] --- Pope --- <<There are only solutions...>> Fernando Martins wrote: >http://weblog.isallineed.net/javagui/archives/000096.html > >Are you refering to this? > >Well, opinions seem to be quite different...(note Spring developer Colin >Sampaleanu's answer). >I personally prefer the Spring approach: keep .project and classpath in CVS >without any specific plugin (nature) in .project or Source/Api in the >.classpath. >That way it will work for everybody checking out the project. >If you do want to try to use some plugin, that is your bussiness, just don't >commit it back to CVS, since it could break other people's build. >Having a eclipse.project and eclipse.classpath, doesn't seem to resolve the >general problem, because if for example someone commits changes to >eclipse.classpath and you allready have your customized .classpath, you'll >have to merge (MANUALLY) the new changes from eclipse.classpath to your >.classpath. >The fact that maven can generate the files is not so revelant, because not >everybody will want to use maven just to have it generate files for eclipse. >Out of curiosity, is Maven able to generate files merging them with allready >existing files (which could have your customized plugins/Sources/Api) ? > >Fernando > >On Tuesday 06 July 2004 09:25, pope wrote: > > >>Hi! >> >>You have read the blogs regarding the including of .classpath and >>.project into CVS :-). >> >>[Have a nice day] / [10x] >>--- >>Pope >>--- >><<There are only solutions...>> >> >>Alex Rodioukov wrote: >> >> >>>Hi all, >>> >>>I'd like to suggest to move Eclipse-related files from the root of menda >>>project in CVS to somewhere else (or rename them). We've had a long >>>discussion with Fernando regarding this, without reaching any conclusions. >>> >>>My argument against having them under menda/ is when local changes are >>>made in Eclipse environment (being project or classpath settings) one >>>has to jump through the hoops to check those in to maintain consistency >>>(and you'll keep on seeing them under Team Sync perspective). >>> >>>Example: you add additional jars to Java Build Path/Libraries, you have >>>to check them in and to check modified .classpath in. If you have >>>Source/API docs attached to said jars you would have to modify >>>.classpath manually (removing local references), check it in, put your >>>settings back. >>> >>>PITA, if you'll ask me. >>> >>>Suggested solution: in order to maintain developer-friendly experience >>>we can rename .project to eclipse.project and .classpath to >>>eclipse.classpath (and whichever .* eclipse related files we have) and >>>move it to documentation folder, adding instructions on how to set-up >>>Eclipse using those files. >>> >>>Any opinions on the subject are very welcome :) >>> >>>Regards, >>> Alex >>> >>> >>>------------------------------------------------------- >>>This SF.Net email sponsored by Black Hat Briefings & Training. >>>Attend Black Hat Briefings & Training, Las Vegas July 24-29 - >>>digital self defense, top technical experts, no vendor pitches, >>>unmatched networking opportunities. Visit www.blackhat.com >>>_______________________________________________ >>>Menda-developers mailing list >>>Men...@li... >>>https://lists.sourceforge.net/lists/listinfo/menda-developers >>> >>> >>------------------------------------------------------- >>This SF.Net email sponsored by Black Hat Briefings & Training. >>Attend Black Hat Briefings & Training, Las Vegas July 24-29 - >>digital self defense, top technical experts, no vendor pitches, >>unmatched networking opportunities. Visit www.blackhat.com >>_______________________________________________ >>Menda-developers mailing list >>Men...@li... >>https://lists.sourceforge.net/lists/listinfo/menda-developers >> >> > > > -- [Have a nice day] / [10x] --- Pope --- <<There are only solutions...>> |