[Webical-developers] Project structure refactoring

[Ivo v. D. <ivo...@gm...>]

Hi,

To make developing plugins possible without to much hassle we need webical
to produce a jar file which is uploaded to a maven repository (or deployed
in some other form). This jar can then be set as a compile time dependency
which gets rid of the need to manually checkout webical and configure the
project dependencies and enables continues integration as well.
The problem is that our project already has a package type and maven won't
allow multiple artifacts per pom. The sollution would be to either use ant
scripting or refactor the project structure to multiple modules (a parent
with two children: the jar and the war project). I've tested out both and I
really dislike the first since you need to hack up the entire build process
which leaves a mess in the pom and causes all kinds of problems with release
and packaging plugins.
I think it would be best to hack up our current project. This follows the
maven standards and leads to a more transparant build. This does however
mean that I need to move around all sources in the repository which will
lead to some merging problems for the other developers, but I really think
it's worth it.

WDYT?

Ivo

PS. I've attached a zip containing the project structure (hope it gets
through the mailinglist filters)

-- 
Ivo van Dongen
Func. Internet Integration
W http://www.func.nl
T +31 20 4230000
F +31 20 4223500