I'll throw this out there . . . IDEA has really good support for Maven, out
of the box. I've been quite pleased to use it for Cayenne development. We
could probably push to get OSS licenses for the development team.
-- KevinOn Mon, Aug 11, 2008 at 6:40 PM, Andrus Adamchik <andru..bjectstyle.org>wrote:
> > On Aug 10, 2008, at 12:43 PM, Aristedes Maniatis wrote: > > >> 1. "mvn cayenne:modeler" does not work (CAY-1058) >> > > No idea about this one. I haven't used it myself, running CM from Eclipse > when in dev mode. > > 2. "mvn clean install" is required, not just once to bootstrap but every >> time I want to get recent changes into an assembly. So, packaging up the >> assembly does not detect changes to the source. In order to capture new jars >> they not only have to be rebuilt but also installed into .m2. >> > > True about assembly requirements. I guess I got so used to it that I don't > find it to be a drawback, however it would be nice if we could build > assemblies with a single command. Not sure how reorg would help with it tho. > > > 3. "mvn clean install" is not even enough. "mvn -P mac clean install" is >> required for me to get the OSX specific bits compiled right. >> > > This was a "feature" :-) But I guess we can replace it with the OS check > for everything but the assemblies (cause we want an ability to build non-mac > assemblies on Macs). Also not related to the folder structure. > > > 4. Still, even with all the above, odd things happen which are no doubt >> due to my cursory knowledge of maven's build process. But it means that I >> spent an inordinate amount of time trying to get the build system working >> after by upgrade to the latest Eclipse: probably about 6 hours in the last >> few days. Now, if only I'd spent those 6 hours working with Marcin on >> inheritance or improving the Cayenne documentation... >> > > Sorry to hear that :-/ > > >> I know in the past, the committers here have been lukewarm about maven, >> but no one wanted to put in the work to return to ant (fair enough!). Is it >> worth considering ant+ivy as a new approach which might deliver the best of >> both worlds? If so, I'm happy to work on this over a period of time. But I >> wouldn't want to start if that wasn't a communal long term goal. >> > > I actually think that Maven got much better over the years, partially due > to the maven developers fixing bugs, and partially due to the community > learning the best practices (same thing that happened to EJB, hehe). At this > point I am very much inclined to stick with Maven for Cayenne. And believe > it or not, after all the criticism that I voiced on this and other lists, I > am actually considering to switch a commercial customer from Ant to Maven > (and hoping that it works more predictably in a controlled environment)... > Unfortunately Ant doesn't scale well when the number of project modules > grows, so you have to use Maven. There is just no ideal build system that > fits all sizes, so you have to compromise :-/ > > Andrus > > > >
This archive was generated by hypermail 2.0.0 : Mon Aug 11 2008 - 20:23:12 EDT