For the Slide 2.0 release, I suggest that we define JDOM-b9 as required. Our code is
b9-compatible anyway. So, if nobody objects, tomorrow I will replace lib/jdom-dev.jar
by lib/jdom.jar (which I downloaded as b9 from jdom.org).
The reason why I once checked-in jdom-dev.jar is that I couldn't find out how to
control GUMP (night build) to use a defined set of dependencies (e.g. the ones
checked-in at lib/). Instead, AFAIK, somwhere in GUMP were defined where to get the
JARs to compile against, e.g. the current state nightly taken from JDOM's CVS, in the
case of JDOM. So, from time to time, when the JDOM guys made changes which invalidated
our code, GUMP failed and that was the time for me to created a new jdom-dev.jar for
Slide. So far about history. See also attached mails I exchanged with Sam Ruby about 2
years ago ... unfortunately, nothing happend ever :-(.
Regards,
Peter
> -----Original Message-----
> From: Oliver Zeigermann [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, January 13, 2004 10:48
> To: Slide Developers Mailing List
> Subject: Re: jdom beta 9 vs jdom-dev conflict
>
>
> I have no idea, but CVS history tells me the JDOM lib has
> been compiled
> and checked in by Peter. Maybe he can help...
>
> Oliver
>
> Michael Hartmeier wrote:
> > I have problem running our proprietary stores with slide "current".
> >
> > We use an external library that's compiled against jdom
> beta 9, whereas
> > slide is compiled against jdom-dev (which is probably jdom
> "current").
> >
> > If I setup an web-application with both slide-kernel.jar and
> > external.jar, i get jvm link exceptions because slide-kernel.jar
> > references
> > org.jdom.Element org.jdom.Element.getParent
> > whereas external.jar references
> > org.jdom.Parent org.jdom.Element.getParent
> >
> > If slide intentionally uses using jdom-dev, that means I cannot use
> > external libraries unless I've compiled them against the property
> > version of jdom.
> >
> > Is possible to use jdom beta 9 in slide? I can point
> jdom.jar to beta 9
> > (in slide's build properties), build slide, and everything
> seems to work
> > property.
> >
> > Michael
> >
> >
> >
> >
> >
> >
> ---------------------------------------------------------------------
> > 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]
>
>
--- Begin Message ---
Hi,
I am a commiter (my account is "pnever") of the jakarta-slide project and I
would like to ask for 2 changes to the Slide's Gump process:
1) Usage of jdom_beta6 instead of jdom_beta8-dev as dependency.
For now this is just asking for the possibility - I need to discuss the
switch at the slide-dev list before it is made active.
BTW, in near future, we probably would like to upgrade to jdom_b7 - are the
dependencies something we can control ourselves in Gump?
2) Publishing of new jakarta-slide-webdav-testsuite.zip at
http://jakarta.apache.org/builds/jakarta-slide/nightly/<date>/.
The "release" target of the Slide build now additionally creates the archive
jakarta-slide-webdav-testsuite-<version>.zip which we would like to publish.
Remy Maucherat told me, that Gump uses the "full-dist" target and packages
in the nightly what is in the "dist" directory. If GUMP could zip the
testsuite folder separately, somebody interested mainly in a WebDAV
testsuite could download 2.3 MB instead of 12.5 MB.
BTW, wouldn't it be easier if GUMP used the "release" target and took over
into http://jakarta.apache.org/builds/jakarta-slide/nightly/<date>/ whatever
archives were then available in the "dist" directory?
Regards,
- Peter.
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
--- End Message ---
--- Begin Message ---
Peter Nevermann wrote:
>
> 1) Usage of jdom_beta6 instead of jdom_beta8-dev as dependency.
>
> For now this is just asking for the possibility - I need to discuss
the
> switch at the slide-dev list before it is made active.
> BTW, in near future, we probably would like to upgrade to jdom_b7 -
are the
> dependencies something we can control ourselves in Gump?
It is possible, but I am not inclined to do it. See
http://jakarta.apache.org/gump/faq.html#7 for details.
> 2) Publishing of new jakarta-slide-webdav-testsuite.zip at
> http://jakarta.apache.org/builds/jakarta-slide/nightly/<date>/.
>
> The "release" target of the Slide build now additionally creates the
archive
> jakarta-slide-webdav-testsuite-<version>.zip which we would like to
publish.
> Remy Maucherat told me, that Gump uses the "full-dist" target and
packages
> in the nightly what is in the "dist" directory. If GUMP could zip the
> testsuite folder separately, somebody interested mainly in a WebDAV
> testsuite could download 2.3 MB instead of 12.5 MB.
> BTW, wouldn't it be easier if GUMP used the "release" target and took
over
> into http://jakarta.apache.org/builds/jakarta-slide/nightly/<date>/
whatever
> archives were then available in the "dist" directory?
That can be done... I'm travelling at the moment, but can look into
setting
this up when I return.
- Sam Ruby
--
To unsubscribe, e-mail:
<mailto:[EMAIL PROTECTED]>
For additional commands, e-mail:
<mailto:[EMAIL PROTECTED]>
--- End Message ---
--- Begin Message ---
I would like to recall the following change request to the GUMP process
of
the jakarta-slide project.
Thanks, Peter.
> > 2) Publishing of new jakarta-slide-webdav-testsuite.zip at
> > http://jakarta.apache.org/builds/jakarta-slide/nightly/<date>/.
> >
> > The "release" target of the Slide build now additionally
> > creates the archive
> > jakarta-slide-webdav-testsuite-<version>.zip which we would
> > like to publish.
> > Remy Maucherat told me, that Gump uses the "full-dist"
> > target and packages
> > in the nightly what is in the "dist" directory. If GUMP
> > could zip the
> > testsuite folder separately, somebody interested mainly in a WebDAV
> > testsuite could download 2.3 MB instead of 12.5 MB.
> >
> > BTW, wouldn't it be easier if GUMP used the "release"
> > target and took over
> > into
http://jakarta.apache.org/builds/jakarta-slide/nightly/<date>/ whatever
> > archives were then available in the "dist" directory?
> That can be done... I'm travelling at the moment, but can look into
> setting this up when I return.
> - Sam Ruby
--
To unsubscribe, e-mail:
<mailto:[EMAIL PROTECTED]>
For additional commands, e-mail:
<mailto:[EMAIL PROTECTED]>
--
To unsubscribe, e-mail:
<mailto:[EMAIL PROTECTED]>
For additional commands, e-mail:
<mailto:[EMAIL PROTECTED]>
--- End Message ---
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
