atom feed7 messages in org.apache.roller.devRe: Mavenizing Roller
FromSent OnAttachments
DaveDec 30, 2009 2:58 pm 
Denis BalazucJan 3, 2010 11:51 am 
Matt RaibleJan 4, 2010 2:22 pm 
Denis BalazucJan 4, 2010 4:17 pm 
David JohnsonJan 5, 2010 6:56 am 
DaveJan 6, 2010 4:59 am 
Laszlo Csaba LorinczJan 9, 2010 4:58 pm 
Subject:Re: Mavenizing Roller
From:Denis Balazuc (den@balazuc.net)
Date:Jan 3, 2010 11:51:21 am
List:org.apache.roller.dev

Thank you Dave. It's great news for Roller. I look forward to try this at home and put R5.0 to work with Maven as soon as possible. I'll let you know if I encounter any difficulty.

Happy new year to all.

On Wed, Dec 30, 2009 at 5:58 PM, Dave <snoo@gmail.com> wrote:

Re: Mavenize Roller (https://issues.apache.org/jira/browse/ROL-1849)

I just did a complete Mavenization of Roller and comitted it into the roller_mavenized branch. I created the following Maven bundles:

test-utils: test utils (e.g. start/stop Derby task) roller-core: core Roller component planet-business: Planet POJOs and business logic planet-web: Planet webapp (under construction as before) weblogger-business: Weblogger POJOs and business logic weblogger-web: Weblogger webapp, rendering system, Struts2 UI weblogger-assembly: assembly that builds Roller distro

To build and run all unit tests, you do this:

svn co https://svn.apache.org/repos/asf/roller/branches/roller_mavenized cd roller_mavenized mvn install

You'll find the Roller webapp in weblogger-web/target/roller. To build a Roller distribution, you do this:

cd weblogger-assembly mvn assembly:single

And you will find Roller distribution files in weblogger-assembly/target

I still need to do a little work to trim down the number of jars in WEB-INF/lib but other than that, I'm ready to merge this into trunk. I think it will be a great improvement. It will make it easier for new developers to understand the Roller source code and to do development in Eclipse, IDEA, Netbeans and any other IDE that has Maven support. I know it is late in the "release cycle" but we will have time to work out the kinks as we create 5.0 betas and release candidates.

I hope to merge this work into the trunk this weekend. Does anybody object to this?