This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 157812 - Support ant-like path-like-structures for classpath
Summary: Support ant-like path-like-structures for classpath
Status: RESOLVED DUPLICATE of bug 116185
Alias: None
Product: projects
Classification: Unclassified
Component: Ant Freeform (show other bugs)
Version: 6.x
Hardware: All All
: P4 blocker (vote)
Assignee: Milan Kubec
URL:
Keywords:
: 157811 (view as bug list)
Depends on:
Blocks:
 
Reported: 2009-02-02 21:17 UTC by argelbargel
Modified: 2009-02-19 20:14 UTC (History)
0 users

See Also:
Issue Type: ENHANCEMENT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description argelbargel 2009-02-02 21:17:31 UTC
It would be great, if the <classpath>-node in java-data would support ant-like path-structures. While the current
implementation is adequate for projects with few dependencies on jars or class-folders, it quite laborious for projects
with many dependencies. I'm working an a large project which depends on 50+ jars in three different folders.

While this is no problem in ant, where i simply use three filesets (**/*.jar) to build up my classpath, i have to add
all those jars by hand to the my custom project.xml I could add them via the gui after creating the rest by hand
(source-folders etc.), or try to create the project.xml via ant, of course. But then I would have to update the
project.xml everytime the libraries change (added/removed/renamed).
Comment 1 argelbargel 2009-02-02 21:20:02 UTC
*** Issue 157811 has been marked as a duplicate of this issue. ***
Comment 2 Jesse Glick 2009-02-02 22:09:57 UTC
Please try

http://wiki.netbeans.org/AutomaticProjects

if you have not already and let me know how it works for you.

*** This issue has been marked as a duplicate of 116185 ***
Comment 3 argelbargel 2009-02-02 23:04:05 UTC
@jglick: in fact, i've tried it with Automatic Projects first, but our build-file seems to be so foobared (e.g. works
great for installations, though its of little use for development/ci purposes) that the build-listener for autoproject
cannot make sense out of it (misses required source-folders and libraries) :-/

Writing my own project.xml files for the few components of the project i'm developing on, seemed much easier than trying
to pick that behemoth apart into more manageable pieces (for autoprojects or stupid humans) and i got quite far quite
fast 'til now, except for the classpath-management...

As the needed libraries/patternset-definition are declared in their own xml-files, I'm gonna to create a properties-file
containing the classpath from them via ant for now, until either 116185 make it into a release or we're able to invest
the time to create a better/more flexible build-system...


Comment 4 Jesse Glick 2009-02-02 23:29:17 UTC
Please file bugs for autoproject if you have noticed specific aspects of the project that it fails to pick up on, since
these may be fixable. I presume that you run _something_ when you want to test source changes you have made, even if
that it not the main "official" script.