using unjar with all caps packages

[Doug Reed <dr...@1viewnetwork.com>]

Hello,
We're in the process of moving our build system into ant and an interesting
problem
has come up. Hopefully, others have seen this. For some reason, one of our
third party
vendors has decided on an all caps package name. Like, COM.whatever instead
of com.whatever.
Our old build system could cope with this, and we just imported this stuff
as is. Ant is
converting the all caps COM to lowercase, and this is breaking our existing
code.
Doing a straight jar -xvf on this jar file preserves the capitalization, so
it seems to be
an ant related issue. I've leafed through the docs and didn't see a mention
of this.
I've considered mucking with the Ant code to see what's going on and
changing our source that
imports this stuff. Does anyone have any thoughts on how to get Ant to
preserve the capitalization
of this package through configuration?

Regards,
Doug Reed

RE: using unjar with all caps packages

[Doug Reed <dr...@1viewnetwork.com>]

Conor,

Ant release version 1.2 on win2k.

Regards,
Doug

-----Original Message-----
From: Conor MacNeill [mailto:conor@ebinteractive.com.au]
Sent: Wednesday, November 01, 2000 9:46 PM
To: ant-user@jakarta.apache.org
Subject: RE: using unjar with all caps packages


Doug,

exactly what is breaking? What operating system? What version of ant?

--
Conor MacNeill
conor@cortexebusiness.com.au
Cortex eBusiness
http://www.cortexebusiness.com.au

> -----Original Message-----
> From: Doug Reed [mailto:dreed@1viewnetwork.com]
> Sent: Thursday, 2 November 2000 15:02
> To: ant-user@jakarta.apache.org
> Subject: using unjar with all caps packages
>
>
> Hello,
> We're in the process of moving our build system into ant and an
> interesting
> problem
> has come up. Hopefully, others have seen this. For some reason, one of our
> third party
> vendors has decided on an all caps package name. Like,
> COM.whatever instead
> of com.whatever.
> Our old build system could cope with this, and we just imported this stuff
> as is. Ant is
> converting the all caps COM to lowercase, and this is breaking
> our existing
> code.
> Doing a straight jar -xvf on this jar file preserves the
> capitalization, so
> it seems to be
> an ant related issue. I've leafed through the docs and didn't see
> a mention
> of this.
> I've considered mucking with the Ant code to see what's going on and
> changing our source that
> imports this stuff. Does anyone have any thoughts on how to get Ant to
> preserve the capitalization
> of this package through configuration?
>
> Regards,
> Doug Reed
>
>

RE: using unjar with all caps packages

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

Doug,

exactly what is breaking? What operating system? What version of ant?

--
Conor MacNeill
conor@cortexebusiness.com.au
Cortex eBusiness
http://www.cortexebusiness.com.au

> -----Original Message-----
> From: Doug Reed [mailto:dreed@1viewnetwork.com]
> Sent: Thursday, 2 November 2000 15:02
> To: ant-user@jakarta.apache.org
> Subject: using unjar with all caps packages
>
>
> Hello,
> We're in the process of moving our build system into ant and an
> interesting
> problem
> has come up. Hopefully, others have seen this. For some reason, one of our
> third party
> vendors has decided on an all caps package name. Like,
> COM.whatever instead
> of com.whatever.
> Our old build system could cope with this, and we just imported this stuff
> as is. Ant is
> converting the all caps COM to lowercase, and this is breaking
> our existing
> code.
> Doing a straight jar -xvf on this jar file preserves the
> capitalization, so
> it seems to be
> an ant related issue. I've leafed through the docs and didn't see
> a mention
> of this.
> I've considered mucking with the Ant code to see what's going on and
> changing our source that
> imports this stuff. Does anyone have any thoughts on how to get Ant to
> preserve the capitalization
> of this package through configuration?
>
> Regards,
> Doug Reed
>
>