On 10/11/06, David Walluck <[EMAIL PROTECTED]> wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Peter Reilly wrote:
> I have modified the ant script to
> *NOT* dot include /etc/ant.conf if ANT_HOME is set.
> The reasoning is that if ANT_HOME is set, there is a 99%
> chance that the user will not want ANT_HOME to be set
> to something else, or that the user wants "rpm_mode" which
> will cause the contents of /etc/ant.d/* to be added to the ant classpath.
I am just going to put my reply as a list of items, because I think they
all need to be addressed by the patch:
1.) This is going a bit too far, isn't it? Setting one property does not
mean that the user has overridden them all or even wants to.
2.) In accordance with other packaged applications, a user's
$HOME/.antrc should override any settings in ant.conf.
3.) In particular, in accordance with java-functions (which for example
allows JAVA_HOME to be overridden from the environment), the ant script
should allow this too.
4.) I thought the way to override /etc/ant.d was to set OPT_JAR_LIST to
empty.
Thanks for the reply,
I will roll back the change where script/ant does not dot call /etc/ant.conf
if ANT_HOME is set.
Is there a pointer to documentation on how to use jpackage ant
so it can be placed in the ant manual.
The current entry has this:
"""
The JPackage project distributes an RPM version of Ant. With this
version, it is not necessary to set JAVA_HOME or ANT_HOME
environment variables and the RPM installer will correctly place the
Ant executable on your path. The ANT_HOME environment variable will
be ignored, if set, when running the JPackage version of Ant.
Optional jars for the JPackage version are handled in two ways. The
easiest, and best way is to get these external libraries from JPackage
if JPackage has them available. (Note: for each such library, you will
have to get both the external package itself (e.g.
oro-2.0.8-2jpp.noarch.rpm) and the small library that links ant and
the external package (e.g. ant-apache-oro-1.6.2-3jpp.noarch.rpm).
However, JPackage does not package proprietary software, and since
some of the optional packages depend on proprietary jars, they must be
handled as follows. This may violate the spirit of JPackage, but it is
necessary if you need these proprietary packages. For example, suppose
you want to install support for starteam, which jpackage does not
support:
1. Decide where you want to deploy the extra jars. One option is in
$ANT_HOME/lib, which, for JPackage is usually /usr/share/ant/lib.
Another, less messy option is to create an .ant/lib subdirectory of
your home directory and place your non-jpackage ant jars there,
thereby avoiding mixing jpackage libraries with non-jpacakge stuff in
the same folder. More information on where Ant finds its libraries is
available here
2. Download a non-jpackage binary distribution from the regular
Apache Ant site
3. Unzip or untar the distribution into a temporary directory
4. Copy the linking jar, in this case ant-starteam.jar, into the
library directory you chose in step 1 above.
5. Copy the proprietary jar itself into the same directory.
Finally, if for some reason you are running on a system with both the
JPackage and Apache versions of Ant available, if you should want to
run the Apache version (which will have to be specified with an
absolute file name, not found on the path), you should use Ant's
--noconfig command-line switch to avoid JPackage's classpath
mechanism.
"""
Peter
- --
Sincerely,
David Walluck
<[EMAIL PROTECTED]>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)
Comment: Using GnuPG with Mandriva - http://enigmail.mozdev.org
iD8DBQFFLEW7N5thZBYlTwkRAkvOAKCMadXEM5BBr6tpEBMLRiTb8n5fdwCfUasB
+JXkNpup/Ik7tU4TZu4FsNM=
=xV7X
-----END PGP SIGNATURE-----
_______________________________________________
JPackage-discuss mailing list
[EMAIL PROTECTED]
https://www.zarb.org/mailman/listinfo/jpackage-discuss
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
