Hi Francis, thanks for your tips.
The procedure you described has several disadvantages for me. At the moment it seem as if I could only checkout the whole maven branch - otherwise it won't build. But instead of having the individual projects I have the whole maven directory treated as one project in the Package explorer (which of course it isn't). Following your advice I used "import existing projects into workspace" for empire-db and empire-db-example. Then of course I have the sources appear twice, first under their project node and second under the maven node - which is not really a problem but not nice either. I tried to run the SampleApp but it could not find the configuration file. Also when synchronizing with svn it shows me a number of files it wants to add to the repository - like , the classpath file, the project file and everything under target. These files and folders should probably be added to svn ignore. What I dislike most, is that I have to check out the root into my workspace and then use "import existing projects into workspace". Isn't there a more convenient way to do it? I am currently working on a project for a customer for which I have to use Maven. I can check out the project into the workspace, call mvn eclipse:eclipse, use refresh and then run the project. This is a very convenient way, and I would like to have something similar for Empire-db. But this project has no eclipse project dependencies. I really don't mind calling one or two maven command from the command line, but I don't like to move files around (as with import project into workspace etc.). For Jörg it seems to work, but without the appropriate command in the SVN repository view (which I still could not manage to have it appear) it's very inconvenient to use. I would be happy if I could check out the individual projects directly and run the maven eclipse:eclipse command. I am sorry for being so late with my criticism - I really should have evaluated it earlier. Rainer > -----Ursprüngliche Nachricht----- > Von: Francis De Brabandere [mailto:[email protected]] > Gesendet: Freitag, 13. Februar 2009 16:30 > An: [email protected] > Betreff: Re: using Maven > > Hi Rainer, > > the simplest way to get going is not installing an eclipse plugin but > running the commands as explained in one of my my previous mails. > > mvn eclipse:eclipse -DdownloadSources=true > (for cleaning up first: mvn clean eclipse:clean eclipse:eclipse > -DdownloadSources=true) > > after that in eclipse: > file - import - existing projects into workspace > > select the folder where you checked out the maven branch and click > finish > all projects hould be imported and ready for use now. > > the alternative is using m2eclipse plugin or q4e plugin > I only tested the m2eclipse plugin and if you use that one you can > skip the eclipse:eclipse command and select import existing maven > project in the import menu > > and don't install both eclipse maven plugins as that is looking for > trouble. > > I hope this helps > > On Fri, Feb 13, 2009 at 4:13 PM, Rainer Döbele <[email protected]> > wrote: > > Hi Franics, > > > > Being a Maven newbe I wonder whether you could give me some advice on > how to use it. > > > > I have both Maven and the Maven Eclipse Plugin installed but unlike > Jörg I don't have the Option to "Check out as Maven project" within the > SVN Repository View (for some reason). > > > > Now if I check out the entire maven branch into my workspace and call > "mvn eclipse:eclipse" it reports "build successful". > > > > However in the Package Explorer I only have the maven node with its > subnodes but none of them is marked as a project. Thus I cannot compile > or run anything. I also have a bin and a target folder but there's not > much in there. > > > > If I only check out an example project (e.g. the empire-db-example) > and call mvn eclipse:eclipse I get the following error: > > org.apache.maven.reactor.MavenExecutionException: Cannot find parent: > org.apache > > .empire-db:empire-db-examples for project: org.apache.empire- > db:empire-db-exampl > > e:jar:2.0.5-SNAPSHOT for project org.apache.empire-db:empire-db- > example:jar:2.0. > > 5-SNAPSHOT > > > > So what is the recommended way for checking the files out and running > the examples? > > > > Rainer > > > >> -----Ursprüngliche Nachricht----- > >> Von: Francis De Brabandere [mailto:[email protected]] > >> Gesendet: Donnerstag, 12. Februar 2009 23:09 > >> An: [email protected] > >> Betreff: Re: mavenized project > >> > >> well depends on what the release dist should look like, it won't be > >> the same as before > >> > >> On Tue, Feb 10, 2009 at 9:43 PM, Rainer Döbele <[email protected]> > wrote: > >> > Sounds good. > >> > Thanks for your evalation Jörg. > >> > And even more for your work Francis. > >> > > >> > So before we merge the maven branch with the trunk is there > anything > >> else to consider? > >> > If not I would call for a vote to merge the branches. > >> > > >> > Regards > >> > Rainer > >> > > >> > > >> > Jörg Reiher wrote: > >> >> re: mavenized project > >> >> > >> >> Hi, > >> >> I used m2e (just found out it wasn't even the latest release but > 0.96 > >> (September 2008)) > >> >> I haven't done a big evaluation of the available tools when I > installed > >> it, just wanted to > know if there is any working plugin, cause when > I > >> worked at a company where Maven was used > (about 1.5 years ago) it > was a > >> big pain to keep > >> >> Eclipse project and Maven in synch... always switching between > console > >> and Eclipse, refreshing > the project; now it seems to be much much > better > >> - m2e did what I expected, so I didn't bother > trying other > plugins. > >> >> > >> >> Greets > >> >> jorg > >> >> > >> > > >> > >> > >> > >> -- > >> http://www.somatik.be > >> Microsoft gives you windows, Linux gives you the whole house. > > > > > > -- > http://www.somatik.be > Microsoft gives you windows, Linux gives you the whole house.
