I've made the workspace independent of building Jaxen

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

Hi all,

I hope the next public build on vmgump will be a full one, not an
Axis-only one, so that we can crawl back to normal operations.

The last thing I've seen was that jaxen now required Jelly and a few
Jelly taglibs to build, all of which depend directly or indirectly on
jaxen in turn.

To deal with the ton of circular dependencies Jaxen creates (it
already had circular dependencies with dom4j and xom) we'd now also
duplicate Jelly and probably even more, build them against a packaged
version of Jaxen, then build Jaxen against those versions of Jelly and
finally rebuild Jelly against the CVS version of Jaxen.

I totally lack the time and energy to do so right now and simply
tunred all jaxen dependencies into dependencies on packaged-jaxen
instead.  I've upgraded the installed Jaxen to 1.1-beta-6 to be more
Gump-like, though.

Feel free to revert it if you want to, but don't claim I didn't warn
you that:

(1) we've disabled nagging for Jaxen because the jaxen community asked
    us to.  Don't expect help.

(2) Jaxen's tests always fail in Gump.

(3) Jaxen's HEAD requires jelly-tags-xml, but at the same time the
    build of jelly-tags-xml was broken last time we tried it because
    of a backwards incompatible change in Jaxen.  What irony.

Stefan

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@gump.apache.org
For additional commands, e-mail: general-help@gump.apache.org

Re: I've made the workspace independent of building Jaxen

["Adam R. B. Jack" <aj...@apache.org>]

> Sorry about that, I was trying to debug why mail wasn't going out
(yesterday
> morning) and just selected an AXIS one 'cos I knew a nag ought go. I ran a
> full build right afterwards, but for some inexplicable reason it hung,
hence
> no more Gump builds. I've killed that, and hope the next run starts soon.

Ok, the usual:

Traceback (most recent call last):
  File "bin/integrate.py", line 113, in ?
    irun()
  File "bin/integrate.py", line 90, in irun
    result = getRunner(run).perform()
  File "/x1/gump/public/gump/python/gump/core/runner/runner.py", line 249,
in perform
    return self.performRun()
  File "/x1/gump/public/gump/python/gump/core/runner/demand.py", line 182,
in performRun
    module=project.getModule()
  File "/x1/gump/public/gump/python/gump/core/model/project.py", line 696,
in getModule
    if not self.inModule(): raise RuntimeError, 'Project [' + self.name + ']
not in a module.]'
RuntimeError: Project [saxpath] not in a module.]
Process Exit Code : 1

I've not (yet) taught vmgump to complain when it exits.

I started (a week ago) trying to make Gump2 not die in this case, it is too
annoying. Unfortunately I'm not quite there. Gump3 was smart enough to catch
such things earlier (or most, so far) but I'm close to patching Gump2 until
Gump3 grows wings and flies. I'll get back to that to commit a fix.

regards

Adam


---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@gump.apache.org
For additional commands, e-mail: general-help@gump.apache.org

Re: I've made the workspace independent of building Jaxen

["Adam R. B. Jack" <aj...@apache.org>]

> I hope the next public build on vmgump will be a full one, not an
> Axis-only one, so that we can crawl back to normal operations.

Sorry about that, I was trying to debug why mail wasn't going out (yesterday
morning) and just selected an AXIS one 'cos I knew a nag ought go. I ran a
full build right afterwards, but for some inexplicable reason it hung, hence
no more Gump builds. I've killed that, and hope the next run starts soon.

regards

Adam


---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@gump.apache.org
For additional commands, e-mail: general-help@gump.apache.org