[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
RE: [aspectj-dev] project-specific settings

Those projects (loadtime5, weaver5) would be set to Java 5 source
compliance, and would continue using the JRE15_LIB variable that they
already depend on.  This mode of working means that a project using any
Java5 stuff is set to Java 5 compliance (i.e. compliance can't be set per
source folder, but even if it could that would be messier).   

_____________________________________________
From: aspectj-dev-bounces@xxxxxxxxxxx
[mailto:aspectj-dev-bounces@xxxxxxxxxxx] On Behalf Of Ron Bodkin
Sent: October 6, 2005 8:49 AM
To: 'AspectJ developer discussions'
Subject: RE: [aspectj-dev] project-specific settings

This sounds good but how will you allow building the sources in java5-src?

_____________________________________________
From: aspectj-dev-bounces@xxxxxxxxxxx
[mailto:aspectj-dev-bounces@xxxxxxxxxxx] On Behalf Of Mik Kersten
Sent: Thursday, October 06, 2005 11:44 AM
To: 'AspectJ developer discussions'
Subject: [aspectj-dev] project-specific settings


In order to make it easier to ensure that Java 5 source language constructs
and libraries don't accidentally get used where they shouldn't, and to make
it easier for potential contributors to check out a compiling AspectJ source
tree, we could consider checking in the following project-specific settings:
- Setting the source compliance (screenshot below).
- Configuring the classpath to use a JRE variable rather than the default
container.

To give this a try I committed project settings for ajdoc.  Note that this
means that you need a JRE14_LIB variable defined.  But I think that the need
to define such variables locally is obvious to most Eclipse developers and
won't require special instructions.

Mik





--
Mik Kersten, http://kerstens.org/mik 
 << File: ATT00068.txt >>  << File: ATT00631.txt >> 

<<attachment: winmail.dat>>