Hi, While trying to extract CDK module dependencies to build another project (SMSD), I finally realised that I was trying to re-invent project dependency management.
In other words, it might be an idea to break up the CDK into a 'family' of projects, and use existing dependency tools to connect them. gilleain On 4/16/11, Egon Willighagen <egon.willigha...@gmail.com> wrote: > On Sat, Apr 16, 2011 at 7:45 AM, Nina Jeliazkova > <jeliazkova.n...@gmail.com> wrote: >> On 16 April 2011 08:19, Egon Willighagen <egon.willigha...@gmail.com> >> wrote: >> But not mavenized , and maven is becoming more of a standard approach to >> define Java dependencies these days :) > > Yeah, and I still hate it :) Anyway, Dmitry suggested Maven as an > option for modularization, and just wanted to point out that it > already is. > >> Deploying and configuring all separate jars into a maven dependencies / >> repository is quite a work though. > > Indeed. Ideally, this would automatically follow from the @cdk.module > annotation too, but I have no time to explore that myself and invite > others to develop solutions. > >> I would like to suggest the following. The project that is used to deploy >> jars into the maven repository in my previous mail is this one (the URL >> has >> already been sent to this list): >> https://ambit.svn.sourceforge.net/svnroot/ambit/trunk/cdk-maven >> It doesn't build the CDK, just imposes maven structure of the modules and >> deploys the binary jars into a repository. It should be trivial to extend >> CDK build file to copy the jars into the mavenized structure of this >> project. The proposal is to have the mavenized structure above into the >> CDK >> source tree, just next to the current one, and use it to deploy the jars >> into a maven repository. (I know some prefer to keep the ant build system >> as >> it is :) > > Let me make clear that I am absolutely *not* against this. Probably > the right place to do this automatically copying into a Maven > repository would be Nightly. > > Patches for parallel build/deploy setups are welcome! > >> CDK jars not being registered in a public maven repository is a major show >> stopper of making derivative projects available via maven infrastructure, >> hope this could help move things in that direction. > > Yet there are currently at least two Maven repositories around. > > Just make sure the CDK git repository does not need to contain a > password for uploading :) > > Egon > > -- > Dr E.L. Willighagen > Postdoctoral Researcher > Institutet för miljömedicin > Karolinska Institutet (http://ki.se/imm) > Homepage: http://egonw.github.com/ > LinkedIn: http://se.linkedin.com/in/egonw > Blog: http://chem-bla-ics.blogspot.com/ > PubList: http://www.citeulike.org/user/egonw/tag/papers > > ------------------------------------------------------------------------------ > Benefiting from Server Virtualization: Beyond Initial Workload > Consolidation -- Increasing the use of server virtualization is a top > priority.Virtualization can reduce costs, simplify management, and improve > application availability and disaster protection. Learn more about boosting > the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev > _______________________________________________ > Cdk-user mailing list > Cdk-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/cdk-user > ------------------------------------------------------------------------------ Benefiting from Server Virtualization: Beyond Initial Workload Consolidation -- Increasing the use of server virtualization is a top priority.Virtualization can reduce costs, simplify management, and improve application availability and disaster protection. Learn more about boosting the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev _______________________________________________ Cdk-user mailing list Cdk-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/cdk-user
