-----Original Message----- From: Steve Cohen [mailto:[email protected]] Sent: 24. februar 2009 14:34 To: Maven Users List Subject: Re: Mavenizing Existing Project Part Deux
OK. Since we're skipping the ant phase on this project, never having used it here, I'll go with your suggestions in #2. I'll start by making a branch, using the least dependent project (which depends on no others) for my first guinea pig. (I DO follow the trunk-branch-tag pattern). However, one question remains - in my present mode I always check everything into SVN, including all those .* files (.project etc.) which, by default, eclipse filters out. I do that to make checkout easier for the next guy, no configuration, etc. But it creates a problem here - it means that the "nature" of the project is predetermined at the time of the checkout. That's what I wanted, but I don't want it here. So I suppose the plan would be: 1. make a tag of current state and cut a branch at the same point. >Yes 2. delete from the branch all the .* files that determine configuration, IN THE REPOSITORY, not on a local copy, where Eclipse would immediately recreate these files. >Yes, and use svn ignore so they will not come back. 3. delete the local copy of the project. >Well not yet. Mavenize the branch first and make sure it works. Tha' POC. Then go to 3. 4. check it out again from the repository as a new project and specify maven in the wizards? >Haven't used m2eclipse, but I'll say yes :) > I would urge you to also learn to use maven with the commandline. I assume this is possible. Is it what you had in mind? Or is there a better way. Steve Jon Georg Berentsen wrote: > Hey! Great! > > Since mavnen config is pretty new to you, this is a great way to learn. > > 1) Is there some way to "change natures"? > No. > With Ant and scripts you can get a very specific build process, usually > with som quircks and/or workarounds. > I find using the Ant scripts and other scripts as inspiration and > documentation for building up the pom, the best way to use them. > But there are a bunch of tricks and tips in doing so. > I think we went thru a few previously in this tread. > > 2) Create a new Maven project, place in SVN, then move stuff to the > right places? > I always presume people have a branch, a tag and a trunk folder, but if > not have a look at some apache project and see how it's done. > I usually do a poc in a branch to see if it all works out. > (A copy or externals of the working trunk) > You do not want to mess up your code, fail, get a new order for > business/management, and desperatly revert trunk. > You also want to tag a stable last version of your Ant built project. > > - --------------------------------------------------------------------- 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]
