You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hc.apache.org by Michael Becke <be...@u.washington.edu> on 2003/05/03 14:52:36 UTC
Maven build
The current version of the maven build for HttpClient is non
functional. This is because JSSE and JCE, which are build
requirements, are no longer available on ibiblio. I think we have only
two options for fixing this:
1) Require JSSE and JCE be available locally for the build. Either
they would be included in CVS or would need to be downloaded separately.
2) Remove JSSE and JCE from the build requirements. This will make the
maven build only available on JDK 1.4+ machines.
Do we have any other choices? What would everyone prefer?
Mike
Re: Maven build
Posted by Michael Becke <be...@u.washington.edu>.
Sounds like we should remove the explicit dependencies on JSSE and JCE
for the short term. This will require 1.4 or manually adding JSSE and
JCE to compile with Maven. If there are no objections I will make the
change to project.xml.
Mike
On Saturday, May 3, 2003, at 10:15 AM, dion@multitask.com.au wrote:
> We have permission from Sun recently to scrape the approval screens as
> part of a distribution for Maven, so hopefully in the next release it
> will
> be a simple yes on the user's behalf to download these Sun licensed
> jars.
> --
> dIon Gillard, Multitask Consulting
> Blog: http://www.freeroller.net/page/dion/Weblog
> Work: http://www.multitask.com.au
>
>
> Ryan Hoegg <rh...@isisnetworks.net> wrote on 03/05/2003 11:23:03 PM:
>
>> I have the same issue in XML-RPC. We chose option 1, and required a
>> separate download. After talking informally with some maven folks, I
>> think this is the usual approach. One must click through certain
>> agreements with Sun to get JSSE, and it's not kosher to circumvent
>> that. Thay have the same issues with Javamail, and that is how it was
>> handled with commons-email, so there is some precedent for this in
> Commons.
>>
>> On the bright side, one of the features being looked at for maven 1.0
>> stable is more flexible repository handling. One might be able to
>> define a hierarchy or repositories, so for example one's organization
>> could host its own repository that is free from the legal restrictions
>> of ibiblio.
>>
>> --
>> Ryan Hoegg
>> ISIS Networks
>> http://www.isisnetworks.net
>>
>> Michael Becke wrote:
>>
>>> The current version of the maven build for HttpClient is non
>>> functional. This is because JSSE and JCE, which are build
>>> requirements, are no longer available on ibiblio. I think we have
>>> only two options for fixing this:
>>>
>>> 1) Require JSSE and JCE be available locally for the build. Either
>>> they would be included in CVS or would need to be downloaded
> separately.
>>> 2) Remove JSSE and JCE from the build requirements. This will make
>>> the maven build only available on JDK 1.4+ machines.
>>>
>>> Do we have any other choices? What would everyone prefer?
>>>
>>> Mike
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail:
> commons-httpclient-dev-unsubscribe@jakarta.apache.org
>> For additional commands, e-mail:
> commons-httpclient-dev-help@jakarta.apache.org
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> commons-httpclient-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail:
> commons-httpclient-dev-help@jakarta.apache.org
>
Re: Maven build
Posted by di...@multitask.com.au.
We have permission from Sun recently to scrape the approval screens as
part of a distribution for Maven, so hopefully in the next release it will
be a simple yes on the user's behalf to download these Sun licensed jars.
--
dIon Gillard, Multitask Consulting
Blog: http://www.freeroller.net/page/dion/Weblog
Work: http://www.multitask.com.au
Ryan Hoegg <rh...@isisnetworks.net> wrote on 03/05/2003 11:23:03 PM:
> I have the same issue in XML-RPC. We chose option 1, and required a
> separate download. After talking informally with some maven folks, I
> think this is the usual approach. One must click through certain
> agreements with Sun to get JSSE, and it's not kosher to circumvent
> that. Thay have the same issues with Javamail, and that is how it was
> handled with commons-email, so there is some precedent for this in
Commons.
>
> On the bright side, one of the features being looked at for maven 1.0
> stable is more flexible repository handling. One might be able to
> define a hierarchy or repositories, so for example one's organization
> could host its own repository that is free from the legal restrictions
> of ibiblio.
>
> --
> Ryan Hoegg
> ISIS Networks
> http://www.isisnetworks.net
>
> Michael Becke wrote:
>
> > The current version of the maven build for HttpClient is non
> > functional. This is because JSSE and JCE, which are build
> > requirements, are no longer available on ibiblio. I think we have
> > only two options for fixing this:
> >
> > 1) Require JSSE and JCE be available locally for the build. Either
> > they would be included in CVS or would need to be downloaded
separately.
> > 2) Remove JSSE and JCE from the build requirements. This will make
> > the maven build only available on JDK 1.4+ machines.
> >
> > Do we have any other choices? What would everyone prefer?
> >
> > Mike
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
commons-httpclient-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail:
commons-httpclient-dev-help@jakarta.apache.org
>
Re: Maven build
Posted by Ryan Hoegg <rh...@isisnetworks.net>.
I have the same issue in XML-RPC. We chose option 1, and required a
separate download. After talking informally with some maven folks, I
think this is the usual approach. One must click through certain
agreements with Sun to get JSSE, and it's not kosher to circumvent
that. Thay have the same issues with Javamail, and that is how it was
handled with commons-email, so there is some precedent for this in Commons.
On the bright side, one of the features being looked at for maven 1.0
stable is more flexible repository handling. One might be able to
define a hierarchy or repositories, so for example one's organization
could host its own repository that is free from the legal restrictions
of ibiblio.
--
Ryan Hoegg
ISIS Networks
http://www.isisnetworks.net
Michael Becke wrote:
> The current version of the maven build for HttpClient is non
> functional. This is because JSSE and JCE, which are build
> requirements, are no longer available on ibiblio. I think we have
> only two options for fixing this:
>
> 1) Require JSSE and JCE be available locally for the build. Either
> they would be included in CVS or would need to be downloaded separately.
> 2) Remove JSSE and JCE from the build requirements. This will make
> the maven build only available on JDK 1.4+ machines.
>
> Do we have any other choices? What would everyone prefer?
>
> Mike