[Gump] cocoon-sax build error

[Stefan Bodewig <bo...@apache.org>]

Hi,

I think I see why the build currently fails in Gump.

The Xalan jar that can be downloaded from the mvn repository contains
java_cup and bcel and regex and a few other things while the one Gump
currently builds does not.  So if you build Cocoon the normal way you
get the additional dependencies for free (and without control over their
version, I may add).

I'll see whether I can make the Xalan build produce the same jar that
can be found in the mvn repo - looks possible - and once Gump produces
that I think the cocoon-sax build will be fixed.  You should be able to
remove the bcel test dependency as well after that.

Stefan

Re: [Gump] cocoon-sax build error

[Simone Tripodi <si...@gmail.com>]

Hi Stefan,
thanks a lot for the incredible analysis you've done!!!
Have a nice day,
Simo

http://people.apache.org/~simonetripodi/
http://www.99soft.org/



On Mon, Jun 28, 2010 at 9:21 AM, Stefan Bodewig <bo...@apache.org> wrote:
> Hi,
>
> I think I see why the build currently fails in Gump.
>
> The Xalan jar that can be downloaded from the mvn repository contains
> java_cup and bcel and regex and a few other things while the one Gump
> currently builds does not.  So if you build Cocoon the normal way you
> get the additional dependencies for free (and without control over their
> version, I may add).
>
> I'll see whether I can make the Xalan build produce the same jar that
> can be found in the mvn repo - looks possible - and once Gump produces
> that I think the cocoon-sax build will be fixed.  You should be able to
> remove the bcel test dependency as well after that.
>
> Stefan
>

Re: [Gump] cocoon-sax build error

[Stefan Bodewig <bo...@apache.org>]

On 2010-06-28, Stefan Bodewig wrote:

> I'll see whether I can make the Xalan build produce the same jar that
> can be found in the mvn repo - looks possible - and once Gump produces
> that I think the cocoon-sax build will be fixed.

well, sort of

<http://gump.zones.apache.org/gump/test/cocoon3/cocoon-sax/index.html>

No more classloader issues but a whole lot of test failures.

The next Gump run will split the unit tests from building cocoon-sax (by
setting maven.test.skip.exec to true) and this should allow the other
modules to get built while whoever understand the test failures can work
on making them pass without any rush.

There will be a new Gump project cocoon-sax-test and surefire reports
will be available.

Stefan