JDK 1.4 dependencies

[Conor MacNeill <co...@cortexebusiness.com.au>]

I have been looking at the removal of dependencies from the gump profile 
which can be satisfied by JDK 1.4.

In some respects this is quite straight forward, just remove the 
dependencies on things like jaxp and jsse. I am a little hesitant to follow 
that course because in reality the projects do depend on these facilities, 
it's just that JDK1.4 provides these facilities directly.

What I am looking for is a way to have Gump recognize that these facilities 
are provided by the JDK and to skip the check for the package jars. I 
thought of adding a <jdk version="1.4+"/> to the project definitions, the 
result would be to check the JDK version first and the the package jars.

Thoughts?
Conor


--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>

Re: JDK 1.4 dependencies

[Conor MacNeill <co...@cortexebusiness.com.au>]

Sam Ruby wrote:
> 
> A simpler approach may be to simply change <depend project="jsse"/> to 
> <option project="jsse"/>, and provide a documentation page listing the 
> packages which are required to be installed, based on the version of the 
> JDK you are using.
> 

Simple is good :-). I'll start by making the JAXP dependencies optional 
tomorrow.

Conor



--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>

Re: JDK 1.4 dependencies

[Sam Ruby <ru...@apache.org>]

Conor MacNeill wrote:
> I have been looking at the removal of dependencies from the gump profile 
> which can be satisfied by JDK 1.4.
> 
> In some respects this is quite straight forward, just remove the 
> dependencies on things like jaxp and jsse. I am a little hesitant to 
> follow that course because in reality the projects do depend on these 
> facilities, it's just that JDK1.4 provides these facilities directly.
> 
> What I am looking for is a way to have Gump recognize that these 
> facilities are provided by the JDK and to skip the check for the package 
> jars. I thought of adding a <jdk version="1.4+"/> to the project 
> definitions, the result would be to check the JDK version first and the 
> the package jars.

It seems to me that there are two different types of dependencies which 
are "obsoleted" by JDK 1.4.  To illustrate the other kind: there are 
projects that depend on Xalan.  Not the version shipped with the JDK, 
but on a later version.  That's what the bootclasspath stuff is for.

A simpler approach may be to simply change <depend project="jsse"/> to 
<option project="jsse"/>, and provide a documentation page listing the 
packages which are required to be installed, based on the version of the 
JDK you are using.

- Sam Ruby




--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>