JDEE

At Wed, 29 Jul 2009 18:13:59 +0200,
Tobias Gerdin wrote:
> When using JDEE for J2ME development, it is not very convenient that the
> classpath always includes the Java SE JRE rt.jar (even if it's not present in
> jde-global-classpath), since it renders the class name qualification algorithm
> more ambiguous.
> 
> For instance, if I try to complete the class 'Image', I need to specify if I denote
> java.awt.Image or javax.microedition.lcdui.Image, even though the former class
> isn't present in J2ME. This also confuses the automatic adder of import statements.
> 
> Would would be the best solution to solve this?

The way I currently avoid importing from jarfiles I'm not interested
in, is to have per-project customizations of
jde-import-excluded-classes. You could blanket exclude all java.awt if
you wanted.  Is that sufficient for your needs?

Cheers,
Len.

At Thu, 30 Jul 2009 09:10:57 +1200,
Len Trigg wrote:
> 
> At Wed, 29 Jul 2009 18:13:59 +0200,
> Tobias Gerdin wrote:
> > When using JDEE for J2ME development, it is not very convenient that the
> > classpath always includes the Java SE JRE rt.jar (even if it's not present in
> > jde-global-classpath), since it renders the class name qualification algorithm
> > more ambiguous.
> > 
> > For instance, if I try to complete the class 'Image', I need to specify if I denote
> > java.awt.Image or javax.microedition.lcdui.Image, even though the former class
> > isn't present in J2ME. This also confuses the automatic adder of import statements.
> > 
> > Would would be the best solution to solve this?
> 
> The way I currently avoid importing from jarfiles I'm not interested
> in, is to have per-project customizations of
> jde-import-excluded-classes. You could blanket exclude all java.awt if
> you wanted.  Is that sufficient for your needs?
> 
> Cheers,
> Len.

I was not aware of this variable, thank you.

It would be nice with some kind of canned configuration for some common
"profiles" though (such as Java SE, J2ME, Android...).

-Tobias

There actually has been thought put into this.  One of the subsequent
releases will give the option for a much more robust (and thus, more
complicated) path setup.  However, the majority uses JEE for the J2EE
and J2SE profiles.

Thanks for your input Tobias.


Tobias Gerdin writes:
 > At Thu, 30 Jul 2009 09:10:57 +1200,
 > Len Trigg wrote:
 > > 
 > > At Wed, 29 Jul 2009 18:13:59 +0200,
 > > Tobias Gerdin wrote:
 > > > When using JDEE for J2ME development, it is not very convenient that the
 > > > classpath always includes the Java SE JRE rt.jar (even if it's not present in
 > > > jde-global-classpath), since it renders the class name qualification algorithm
 > > > more ambiguous.
 > > > 
 > > > For instance, if I try to complete the class 'Image', I need to specify if I denote
 > > > java.awt.Image or javax.microedition.lcdui.Image, even though the former class
 > > > isn't present in J2ME. This also confuses the automatic adder of import statements.
 > > > 
 > > > Would would be the best solution to solve this?
 > > 
 > > The way I currently avoid importing from jarfiles I'm not interested
 > > in, is to have per-project customizations of
 > > jde-import-excluded-classes. You could blanket exclude all java.awt if
 > > you wanted.  Is that sufficient for your needs?
 > > 
 > > Cheers,
 > > Len.
 > 
 > I was not aware of this variable, thank you.
 > 
 > It would be nice with some kind of canned configuration for some common
 > "profiles" though (such as Java SE, J2ME, Android...).
 > 
 > -Tobias
 > 
 > ------------------------------------------------------------------------------
 > Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
 > trial. Simplify your report design, integration and deployment - and focus on 
 > what you do best, core application coding. Discover what's new with 
 > Crystal Reports now.  http://p.sf.net/sfu/bobj-july
 > _______________________________________________
 > jdee-users mailing list
 > jdee-users@...
 > https://lists.sourceforge.net/lists/listinfo/jdee-users


-- 
Paul Landes
landes@...