OK, I've downloaded 'Better Builds with Maven' and it shows me how I can build a J2EE project with ejb and web sub projects, with each of those projects relying on libraries. How would you suggest I refactor my "two webProjects depending on a common rootWebProject" to make use of the maven-ejb-plugin?
I would want the ability to build at least three separate webmodules -- one for testing the common web components, and one webmodule for each application using those common components. Would I have to build a library jar from the Java/.html code of the root web application, and have the three web applications depend on that? Are there any other reasonable options I should consider? -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Martijn Dashorst Sent: Wednesday, March 07, 2007 3:11 PM To: [email protected] Subject: Re: [Wicket-user] Best practices for project structure I'd suggest downloading 'better builds with maven', and base your project on that... There is no replacement for a good build tool and setup without IDE's. mvn eclipse:eclipse -DdownloadSources=true is your friend :) Martijn On 3/7/07, Frank Silbermann <[EMAIL PROTECTED]> wrote: > > > > Last year I created two Wicket applications for use by customers. The > two applications had a virtually identical navigation struction and > similar kinds of displays, so as you might expect, I built a great > many specialized Wicket panels and parent page classes to be shared by > both applications. > > I used an IDE mandated by my employer -- Jbuilder 2006 -- which > provides various "builds" (web build, ejb build, Javadoc build, etc.) > within the context of a single project. I created one project for > application A and another for application B. > > To avoid duplicating the objects I built that were used in both > applications, I placed them in a root project C upon which both > applications A and B were dependent. > > All three projects contained a web build: > > Root project C contained a Wicket web application for trying out my > reusable components. > Root project A contained a web build consisting of two Wicket applications: > (1) a Wicket application for playing with and testing the reusable > components built for that application only, and (2) a Wicket > application for the users. I also added (3) a non-Wicket stateless servlet. > Root project B likewise contained a web build consisting of two Wicket > applications: (1) a Wicket application for testing project B specific > components, and (2) a Wicket application for the users. > > I now have the opportunity to upgrade to JBuilder 2007, which is based > on Eclipse and is very different from JBuilder 2006. (This is > exciting because I may finally get to use the Wicket plug-in.) My > main concern is that in Eclipse every build type must be a separate > project. I do not like the results I get using the automatic JBuilder > 2007 import wizards; I get the impression that it's not designed for > the kind of project structure I was using. (In particular, most people > would probably consider it weird to have a Web project be dependent > upon another Web project.) > > What sort of Eclipse project structure would be appropriate for what > I've done? Should I create three Eclipse Web projects, with two of > them each depending upon the third? > > Or would Eclipse be confused by the attempt to make one web project > depend upon another? If so, should the root project C be divided into: > > a web project with the deployment information for testing, and a > simple Java project to contain the classes and HTML files against > which the deliverable applications will be compiled, and to be > incorporated into their deployment deliverables? > Is there any reason to divide projects A or B into muliple Eclipse projects? > > How, in Eclipse, do I specify whether a projects required dependency > should have its classes deployed in the deliverable (versus, say, the > kind of dependency that you can expect to already be deployed to the > web server's own lib directory)? > > ---------------------------------------------------------------------- > --- Take Surveys. Earn Cash. Influence the Future of IT Join > SourceForge.net's Techsay panel and you'll get the chance to share > your opinions on IT & business topics through brief surveys-and earn > cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEV > DEV _______________________________________________ > Wicket-user mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/wicket-user > > -- Learn Wicket at ApacheCon Europe: http://apachecon.com Join the wicket community at irc.freenode.net: ##wicket Wicket 1.2.5 will keep your server alive. Download Wicket now! http://wicketframework.org ------------------------------------------------------------------------ - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDE V _______________________________________________ Wicket-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-user ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Wicket-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-user
