On 16.04.2008 08:35, Reinhard Poetz wrote:
URL: http://svn.apache.org/viewvc?rev=648313&view=rev
Log:
mv subprojects into trunk
Is there a reason for that? When I want to check out Cocoon trunk I
don't want to have all the subprojects of it, do I?
My first idea was to move our subprojects (SSF, Spring configurator,
JNet, Block Deployment) to cocoon/subprojects but this would have mae it
more difficult to run a complete build of trunk because you would have
to make sure that you build the subprojects first.
Of course this could be solved by having releases of all subprojects and
use them instead of the SNAPSHOTs, but we haven't reached that point yet
for JNet and Block Deployer.
Considering this I propose that we leave the subprojects _for now_ in
cocoon/trunk/subprojects and move them out as soon as all 4 subprojects
have been released.
WDYT?
As a temporary solution that's fine.
Joerg
