On 8/18/05, Marcelo Alcantara <[EMAIL PROTECTED]> wrote: > Hi Dan, > > Thank you very much for the reply. > > I still have some doubts and think that maybe you can help me. > > 1) > web > parent > common > war > > What would be contained inside the common and parent?? It would > generate different wars?? >
sorry i was following the best practice found in maven. Common only used if you have multiple project sharing jar If you want to see a good usage of parent, take a look http://svn.apache.org/repos/asf/maven/maven-1/plugins/trunk > 2) The whole big project (ear) would take some time to deploy. How > would each developer deploy small parts to tests their development > separatelly?? My developers will be doing junit tests on their session > ejbs...but at some points they will have to do something more > integrated. In your env, developer should be able test as much they can in term of session ejb. You can setup some continuous integration like continuum , cruisecontrol luntbuild, etc to build, deploy the ear and run integration from there. > > Thanks in advance! > > Marcelo > > > > On 8/17/05, dan tran <[EMAIL PROTECTED]> wrote: > > Marcelo, > > > > Maven promotes cohesive build, one artifact per project. this works out > > very well for us here with very big proeject. In your case, > > > > Your bussiness project will have many smaller projects under underneath. > > Then you will have on project on project to aggregate related sub project > > together. > > > > bussiness > > jar1 > > jar2 > > jar3 > > parent <- not artifact build but has common setting > > common <---- shared jar used by other > > ear? > > web > > parent > > common > > war > > etc... > > > > Hope it helps... > > > > But if you have specific question on deployment .. feel free to ping more > > > > -D > > > > On 8/17/05, Jesse McConnell <[EMAIL PROTECTED]> wrote: > > > sorry, not a clue :/ > > > > > > sure someone else on here has dealt with it though :) > > > > > > best of luck, > > > jesse > > > > > > On 8/17/05, Marcelo Alcantara <[EMAIL PROTECTED]> wrote: > > > > Hi Jesse, > > > > > > > > I am right now working with Maven 1. As I don´t feel safe in using > > > > Maven 2 yet (should I??). > > > > > > > > Any ideas for it based on Maven 1?? > > > > > > > > Regards, > > > > > > > > Marcelo > > > > > > > > On 8/17/05, Jesse McConnell <[EMAIL PROTECTED]> wrote: > > > > > you thinking maven 1 or 2? > > > > > > > > > > I can't speak to maven1, but this project design would be pretty easy > > > > > to implement and manage in m2. I think John is planning on making a > > > > > sample large project archetype to bootstrap the design layout of a > > > > > project like this.. > > > > > > > > > > but is really is pretty easy in m2, imo at least > > > > > > > > > > Jesse > > > > > > > > > > On 8/17/05, Marcelo Alcantara <[EMAIL PROTECTED]> wrote: > > > > > > Hi, > > > > > > > > > > > > I am working on a very big billing project with 40 developers, and I > > > > > > am intending to use maven on it. > > > > > > > > > > > > Some questions that are still in my mind. > > > > > > > > > > > > How do you usually devide the project into small units to ease > > > > > > development and local deployment/testing?? > > > > > > > > > > > > Actually I did a multiproject in the initial framework based on the > > > > > > following structure: > > > > > > > > > > > > project > > > > > > +--base (base configuration for other projects) > > > > > > +--common (common classes to be used between web and business > > > > > > modules) > > > > > > +--business (ejbs) > > > > > > +--web (web...) > > > > > > > > > > > > As I can see, it is not going to be a good idea to have a lot of > > > > > > ejbs > > > > > > into de business jar. Nor will be having all the web resources > > > > > > inside > > > > > > the web war. > > > > > > > > > > > > How do you usually do in your big projects?? > > > > > > > > > > > > Thanks for any help. > > > > > > > > > > > > -- > > > > > > Marcelo Alcantara > > > > > > Senior Developer/Architect > > > > > > -------------------------------------------------------- > > > > > > [EMAIL PROTECTED] > > > > > > +55 11 81968823 > > > > > > > > > > > > --------------------------------------------------------------------- > > > > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > -- > > > > > jesse mcconnell > > > > > > > > > > --------------------------------------------------------------------- > > > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > > > > > > > > > > > > > -- > > > > Marcelo Alcantara > > > > Senior Developer/Architect > > > > -------------------------------------------------------- > > > > [EMAIL PROTECTED] > > > > +55 11 81968823 > > > > > > > > --------------------------------------------------------------------- > > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > > > > > > > > -- > > > -- > > > jesse mcconnell > > > > > > --------------------------------------------------------------------- > > > 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] > > > > > > > -- > Marcelo Alcantara > Senior Developer/Architect > -------------------------------------------------------- > [EMAIL PROTECTED] > +55 11 81968823 > > --------------------------------------------------------------------- > 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]
