[IcedTea] Where to put the new default NetX jar?

Joshua Sumali jsumali at redhat.com
Wed Feb 27 07:57:00 PST 2008


Lillian Angel wrote:
>
>
> Lillian Angel wrote:
>>
>>
>> Lillian Angel wrote:
>>> Hi,
>>>
>>> Joshua Sumali wrote:
>>>> Hi,
>>>>
>>>> I've recently refactored the NetX package names to follow proper 
>>>> conventions. As a result, the old default NetX application breaks 
>>>> since it relies on the old package naming. As a result, I've made a 
>>>> new default application jar similar to the old one, but I'm unsure 
>>>> of where to put it. Note that the old one is hosted on the original 
>>>> author's SourceForge page, which we don't have access to. We can 
>>>> either:
>>>>
>>>> 1. Host it somewhere online (e.g. icedtea.classpath.org)
>>>> 2. Include the jar with the built JRE, since NetX will be part of 
>>>> the JRE soon (as opposed to the SDK). If we do this, which 
>>>> directory in the JRE would be appropriate?
>>>
>>> I prefer this. Where to put it? maybe tools-copy? This dir can be 
>>> renamed to something more appropriate, but you can keep it with all 
>>> the tools stuff. I guess use your own discretion- anywhere is fine.
>>
>> Sorry, i meant to keep the netx jar in the tools-copy directory, and 
>> copy it out to the jre when building. In the JRE, I would think 
>> putting it in lib/.
>>
I think you meant the 'tools' directory as tools-copy is used for 
building hotspot :) But even then, the tools directory is supposed to be 
disappearing since I've moved tools/* to rt/* (all the NetX sources).

Hmm, which reminds me: if we decide to just include this default.jar in 
the JRE (say in lib/), I'd need to build this jar during the icedtea 
build process, and thus I'd also need somewhere to put the default.jar 
sources for building. tools/ doesn't seem too appropriate since the 
class files aren't going into any tools.jar. Perhaps a new 
icedtea/extra/ directory?
>>>
>>>> 3. Something better?
>>>>
>>>> Comments appreciated.
>>>
>>> just my two cents,
>>
>> Now four.
>> Lillian
>>




More information about the distro-pkg-dev mailing list