On 26 Aug 2006, at 02:35, Vadim Gritsenko wrote:
Jorg Heymans wrote:
Starting from a clean repo, mvn clean install runs through again
now, all dependencies (except for saxon 7.9.1 which is being
uploaded to maven central as we speak) are downloaded, all modules
compile, all tests pass.
Ummm, somehow it was failing for me - I've added logkit
dependencies in couple of places. I hope I've not screwed it up much.
ok i'll test again. In general, is logkit a <provided> dependency or
not? Reason i did this was because in cocoon-core/pom.xml someone
excluded all logkit artifacts from the avalon dependencies.
How can we move to the jar-verification stage now? Shall i make
one big bundle of my local repo or do people prefer to do a local
mvn install ?
When you release... please include latest change in xmlutil, fixes
very annoying NPEs in cocoon trunk.
sure, all builds are based on trunk, so whatever changes you make
will be in there.
Thanks
Jorg
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
