cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jorg Heymans ...@domek.be>
Subject [M10N] end of first flattening round
Date Fri, 06 Jan 2006 01:43:39 GMT

Moved following blocks :

- core
- mocks
- session-fw
- authentication-fw

they are all located in /trunk now.


you should get :

[INFO] Apache Cocoon .......................................... SUCCESS
[2.582s]
[INFO] Cocoon Core ............................................ SUCCESS
[41.436s]
[INFO] Core Mocks ............................................. SUCCESS
[0.696s]
[INFO] Session Framework ...................................... SUCCESS
[0.091s]
[INFO] Session Framework Implementation ....................... SUCCESS
[2.732s]
[INFO] Session Framework Sample Application ................... SUCCESS
[0.519s]
[INFO] Authentication Framework ............................... SUCCESS
[0.067s]
[INFO] Authentication Framework Implementation ................ SUCCESS
[3.651s]
[INFO] Authentication Framework Sample Application ............ SUCCESS
[0.489s]


[INFO] BUILD SUCCESSFUL


Notes
======

- tests are currently not compiling because of corrupt HtmlUnit poms, so
always run with -Dmaven.test.skip=true.
- the block structure is maven compliant already but probably does not
resemble our true block structure quite yet. This is easy to do so once
we nail down the block layout together with the deployer. For now i've
put the WEB-INF/xconfs in resources.
- the java directories still have non-java files in them. Someone should
still do something like "find . -name 'all-files-not-ending-in-java' |
xargs svn delete " on the java directories
- i applied the naming convention of the maven repo, we can argue about
this later for now it'll do.
- things are still pretty rough overall, expect improvements soon
especially wrt eclipse plugin integration.
- we should use this minimal setup of core + 2 basic interdependent
blocks to get the deployer going and formalize the block structure
before we start adding more complicated blocks.
- if people want something easy to help out, start looking at the
assembly format for binary releases. We'll need it quite soon. Also the
Htmlunit pom needs to be added to cvs.apache.org (alternatively log this
in maven jira under "maven evangelism" or ping the htmlunit authors
directly)


That's all for now, 'night folks



Jorg


Mime
View raw message