On Nov 7, 2008, at 5:54 AM, Oleg Kalnichevski wrote:

On Fri, 2008-11-07 at 01:58 +0100, Thorsten Scherler wrote:
On Thu, 2008-11-06 at 17:36 -0500, Ryan McKinley wrote:


Oleg, if you are comfortable with maven, can you give that a crack?
If not -- i will try to throw something together

ryan

Sure. If you can live with the Ant build being completely broken
while I
am busy moving stuff around, I can take of the basic Maven setup.

I also think It should be feasible to use maven to manage dependencies
and build component artifacts (jars) while using Ant to generate
release
packages and manage web site content.

Would that work for you, guys?


sounds great.  Thanks!

Yeah, perfect.

Awesome. :)

BTW IMO the build had been broken for a while actually so no worries.

salu2


Folks

I laid out the basic Maven compliant multi-module project structure and
created two modules: Droids Core and Droids Dynamic. Core was set up
according to the Maven guidelines. The structure of Dymanic was left
intact, albeit it took a bit more verbose pom.xml to get it to work with
Maven.

If we go with maven, I think we should make our directory layout play nicely with maven. We should ditch the "depot" directory and add all the standard src/main/java folders.

Perhaps we can look at:
http://svn.apache.org/repos/asf/wicket/trunk/
as an example.  They do many of the things we will want/need to do.

Rather then "module-xxx" and "depot", maybe we can have:

/trunk/
/trunk/droids-core
/trunk/droids-norobots
/trunk/droids-solr
/trunk/droids-dynamic (perhaps droids-spring?)
/trunk/droids-xxx


Ant builds are utterly broken.


(its been broken for a while, so don't worry about it)


As the next step I am going to move Norobots stuff to a separate module.

Please review the changes and assess the damage done so far.


I say -- forge ahead and don't be shy about renaming folders/directory structure so it plays nicely with maven.

thanks!
ryan

Reply via email to