Ant: To dist or not to dist...
- From: Karsten Wutzke <kwutzke@xxxxxx>
- Date: Tue, 10 Jul 2007 09:45:41 -0700
Hello!
I still see no reason as to why I should write my build.xml's dist
target to put the created JAR file into the dist directory and not the
root directory.
Here my dir tree:
<root>
+--build
+--dist
| +--app.jar
+--lib
| +--lib1.jar
| +--lib2.jar
| +--lib3.jar
+--src
I have a packaged Swing GUI application, the manifest should (but
doesn't have to) use libraries specified via the Class-Path: lib/
lib1.jar lib/lib2.jar lib/lib3.jar line, so putting the JAR into dist
seems to be somewhat inappropriate. The lib dir is in the project root
(where build.xml is) and it seems to be the perfect place to also put
the JAR file into the root.
I regularly launch the JAR file to see if everything is working.
Maybe someone can explain to me why "disting" to the dist dir parallel
to the lib dir is preferrable (as I keep reading in a smart book).
Of course I can change the manifest to include the libs from the
parent dir's lib with "Class-Path: ../lib/lib1.jar ../lib/lib2.jar ../
lib/lib3.jar". I just imagine moving the dist JAR into some other dir,
then the manifest entries would actually reference the parent dir's
lib dir files which I find very confusing. I find putting the JAR into
a dir along with a subdir lib much more intuitive.
Perhaps the question must be answered what the dist file is there
for...? Is it made for launching at all? Just for deployment? The
concept of dist is a little unclear to me...
TIA
Karsten
.
- Prev by Date: Re: changing build.xml
- Next by Date: Configuring NetBeans, JBoss and MySQL
- Previous by thread: Re: Sun Studio Enterprise Builder 8 and NetBeans 5.5
- Next by thread: Configuring NetBeans, JBoss and MySQL
- Index(es):
Relevant Pages
|
