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 179863 - Compilation task in Java Card projects should refer to class.path property in project.properties
Summary: Compilation task in Java Card projects should refer to class.path property in...
Status: RESOLVED INVALID
Alias: None
Product: javacard
Classification: Unclassified
Component: Java Card (show other bugs)
Version: 6.x
Hardware: PC Windows XP
: P3 normal (vote)
Assignee: _ tboudreau
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-01-26 04:09 UTC by msmirnov
Modified: 2010-02-16 11:35 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 msmirnov 2010-01-26 04:09:34 UTC
Compilation task in different types of Java Card projects in build-impl.xml contain the followoing classpath reference:

	<classpath/>

This element is updated automatically when some dependencies are added to the project. For example after adding dependency on ClassicLibrary it is updated to:
   
        <classpath>
                <pathelement path="${dependency.ClassicLibrary3.origin}/dist/ClassicLibrary3.cap"/>
	</classpath>

I suggest to refer to "class.path" property from project.properties instead. I.e.

	<classpath path="${class.path}"/>

This property is also automatically updated after changing project's dependencies. Thus there wouldn't be need to change build-impl.xml at all. Because build-impl.xml file is intended to be project independent and its header says "don't edit this file". So project dependent things should go to build.xml and project.properties files. Otherwise what is the reason for adding and updating class.path property if it isn't used in any other project files.
Comment 1 _ tboudreau 2010-01-26 10:36:08 UTC
The reason for doing it this way is so that we can *deprecate and get rid of* the class.path property.  It is only updated now because a few things are still using it that haven't been cleaned up, and I need to verify with Anki that none of the RI's Ant tasks are depending on it.

Are you finding you need to *manually* edit build-impl.xml after changing dependencies?  If so, that is definitely a bug.

If you just don't like that it is rewritten when dependencies change, that, however, is by design.
Comment 2 _ tboudreau 2010-02-16 11:35:01 UTC
Closing;  issue is as designed.