On Wed, Feb 12, 2014 at 2:22 AM, Greg Trasuk <tras...@stratuscom.com> wrote:
> > > I have been using Maven to build applications (e.g. the samples at > https://github.com/trasukg/river-container-examples). The only thing I > find slightly irritating is that you end up with a proliferation of Maven > modules, which equates to a proliferation of Netbeans or Eclipse projects. > With Maven, that’s unavoidable, because Maven really really wants to have > only one artifact produced per module. So ‘hello-api’ requires its own > module, as does ‘hello-service’ (for the implementation code), and > ‘hello-module’ (the packaging for the container). ‘hello-dl’ would be > another, if there were a smart proxy. Avoiding separation of service api/impl/proxy into modules something to think about. > That’s also not specific to Jini projects; you get the same thing in JEE6 > projects - separate projects for the JPA module, EJB module, EJB API, Web > module, etc. Other build tools may be happier with multiple artifacts from > one project. Ant certainly is, but of course you drift into the > complexities of the current build with ‘classDepAndJar’. > Gradle is very flexible in this (and in many others too). > > I think the first step might be to split out the infrastructure services > like Reggie, Mahalo, and Outrigger into separate deliverables, leaving the > contents of jsk-platform in the core module. > +1 > > > > > On Feb 11, 2014, at 6:52 PM, Rafał Krupiński < > rafal.krupin...@sorcersoft.com> wrote: > > > Dnia 2014-02-11, wto o godzinie 15:59 +0100, Simon IJskes - QCG pisze: > >> On 11-02-14 11:35, Peter wrote: > >> > >>> We will need a new build system for java 8, this looks like a step in > that direction. In reality we need to adopt the build conventions used by > Rio. > >> > >> What are these? Maven? > > > > Not necessarily Maven, although Dennis mentions it. > > http://www.rio-project.org/conventions.html#Project_Modules > > > > It works very well for our River/Rio services. > > > > Regards > > Rafał Krupiński > > > >
