What prompted me to start looking into JPackage is that Fedora Core 4
included it in the distro, and I realized how much sysadmin time it
would save. Packages that are not servers (not Tomcat) are simple
libraries that sit in known locations and can be referenced in a
build or upgraded in a consistent manner.
They are placed under /usr/share/java. E.g.:
[andru..age ~]$ rpm -ql jakarta-commons-logging-1.0.4-2jpp
/usr/share/doc/jakarta-commons-logging-1.0.4
/usr/share/doc/jakarta-commons-logging-1.0.4/LICENSE.txt
/usr/share/doc/jakarta-commons-logging-1.0.4/PROPOSAL.html
/usr/share/doc/jakarta-commons-logging-1.0.4/RELEASE-NOTES.txt
/usr/share/doc/jakarta-commons-logging-1.0.4/STATUS.html
/usr/share/java/commons-logging-1.0.4.jar
/usr/share/java/commons-logging-api-1.0.4.jar
/usr/share/java/commons-logging-api.jar
/usr/share/java/commons-logging.jar
/usr/share/java/jakarta-commons-logging-1.0.4.jar
/usr/share/java/jakarta-commons-logging-api-1.0.4.jar
/usr/share/java/jakarta-commons-logging-api.jar
/usr/share/java/jakarta-commons-logging.jar
Modeler upgrades would also be seamless...
Andrus
On Sep 5, 2005, at 3:10 PM, Cris Daniluk wrote:
> Where would you envision installing the JARs? Couldn't this
> conceivably create a conflict with the JARs that might be deployed in
> a WAR file, etc?
>
> On 9/5/05, Andrus Adamchik <andru..bjectstyle.org> wrote:
>
>>> building the rpms is pretty easy once you have a .spec file, and
>>> i'd be
>>> happy to throw one together as a sample. might even have time later
>>> this
>>> week to put one together, and will submit to jira along with
>>> building
>>> instructions when its done.
>>>
>>
>> That'd be great!
>>
>> Andrus
>>
>>
>
>
This archive was generated by hypermail 2.0.0 : Mon Sep 05 2005 - 15:52:38 EDT