On Mon, Apr 19, 2010 at 8:22 AM, Christian López Espínola <[email protected]> wrote: > Hi Alexander, > > On Mon, Apr 19, 2010 at 2:12 PM, Alexander Lepekhine <[email protected]> > wrote: >> >> Recently I became the adherent of maven - the project building tool which >> substitutes ant. Maven uses declarative project description and greatly >> facilitate project dependency management. Has it sense to move argouml >> itself and modules projects under maven? >> The single problem I see is to have a repository where we shall store our >> artifacts. If somebody (Linus?) provides us with the repository I can do >> this job. >> > > I did the same proposal long time ago. But the way, some of the leaf > dependency projects that we manage (IICR Swidgets, Toolbar and maybe GEF, > I'm not sure about the latter) were migrated.
This was actually first proposed, and a lot of the initial work done by, Ludovic several years (4? 5?) ago. > One of the problems with migrating is that what we already have a working > system, with a relatively complex build process that *works*. So changing > that is not very simple, and adds no value to final users. > If we follow that way, I'd expect migrating the svn folder structure to the > common practices in mvn, and this adds more possible problems to the > migration. That was basically my opinion back then and I don't think it's changed much. Maven can be interesting for new projects, but its a lot of work for no gain for existing projects. For ArgoEclipse builds, all the dependencies are encoded in the Eclipse plugin structure and there's a specific Eclipse PDE (Plugin Development Environment) build procedure, so Maven would be a third dependency description and build environment. Tom ------------------------------------------------------ http://argouml.tigris.org/ds/viewMessage.do?dsForumId=450&dsMessageId=2590607 To unsubscribe from this discussion, e-mail: [[email protected]]. To be allowed to post to the list contact the mailing list moderator, email: [[email protected]]
