Hi Jorg,
There is also another issue related to excalibur in COCOON-1671 (See it
in point 2. about a console output: "NAMESPACE PREFIX!!!!"). I looked
into this but I was unable to find where the message is generated.
Perhaps it is already fixed and we need just to update the excalibur
jars in cocoon.
Best Regads,
Antonio Gallardo.
Jorg Heymans escribió:
Hi,
After having successfully wrestled the maven release process into
submission, i would like to announce the availability of all artifact
jars in current trunk for testing. They were released from tag
http://svn.apache.org/repos/asf/excalibur/tags/excalibur-first-maven2-release/
, the jars itself can be downloaded from
http://people.apache.org/repo/m2-snapshot-repository/excalibur-test-for-release/
(m2 style structure)
Notes
--------
- The jars aren't signed yet
- It seems that some classes have custom annotations in them
(discovered during javadoc generation). Do i need to do anything
special with this? For the moment no processing is done.
- A full clean install from the root executing all unit tests works
- As discussed before, i incremented all artifact versions by .01
- The maven poms are good enough for compilation and test running,
however they might need additional tweaking (dependency scopes) so
that ppl including them don't need to <exclude> everything. This is
not required for the release however, keep in mind though that i might
do a further point release after this one to get that metadata right.
Right, how do we now go about testing the jars for production and
release worthyness ?
Regards
Jorg
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
