[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
RE: [jdt-core-dev] extension point for initializing unbound classpath variables
|
Along these lines
1) Can we have an export/import on the Classpath variable definitions? It
would be nice to be able to export my values for a teammate to start with.
2) Can we set up the Java builder to ask for definition of a classpath
variable if not present but listed in the classpath of the project? (So when
I checkin a project and someone else checks it out, it asks them for values)
TIA,
-- Scott
==============================================================
Scott Stanchfield FGM, Inc. scott@xxxxxxx
Home Page: http://javadude.com scott@xxxxxxxxxxxx
Lead author of "Effective VisualAge for Java, Version 3"
http://javadude.com/evaj
VisualAge for Java Tips and Tricks http://javadude.com/vaj
AWT & Swing FAQ Manager, jGuru.com
Visit for Java Enlightenment! http://www.jguru.com
==============================================================
> -----Original Message-----
> From: jdt-core-dev-admin@xxxxxxxxxxx
> [mailto:jdt-core-dev-admin@xxxxxxxxxxx]On Behalf Of Jim des
> Rivieres/OTT/OTI
> Sent: Monday, November 19, 2001 11:57 AM
> To: jdt-core-dev@xxxxxxxxxxx
> Subject: [jdt-core-dev] extension point for initializing unbound
> classpath variables
>
>
>
> Attached is a proposal for a new JDT core extension point that would allow
> a plug-in to
> declare that it is responsible for initializing a particular classpath
> variable.
>
>
>
> Doc for the new API class and extension point:
>
>
>
> Please send comments and questions to this mailing list.
>
> ---jeem
> (See attached file: ClasspathVariableInitializer.java)
> (See attached file: classpathVariableInitializer.html)
> (See attached file: uninit-classpath-vars.html)
