Re: UI for setting up runtime classpath

Petr,

see below.

Petr Jiricka wrote:
> Hi team,
> 
> I have a question regarding the Compiled Classes target customizer.
> 
> The customizes has several tabs: General, General Classpath, Runtime 
> Classpath, Boot Classpath.
> 
> While I understand the purpose of General Classpath (this is what is 
> passed to the compiler, right ?), I don't understand why Runtime 
> Classpath and Boot Classpath are here.
> 
> First, I may not be building a runnable project, but a reusable library, 
> which can not be run on its own. So runtime classpath is not always 
> appropriate.
> 
> Secondly, My project could have several Compiled Classes targets (each 
> of which will have its own runtime classpath), but there may be only one 
> way to run it. So how will then the runtime classpath be determined ? 
> Which of the Compiled Classes targets will be used ?
> 
> Thirdly, I may not need to set up classpath for running my project at 
> all, when I for example run my project in a container (web server, J2EE 
> server). Then the server determines the classloading.
> 
> So setting runtime classpath on the Compile Classes target does not make 
> sense - instead the user should set it on the execution profile for 
> running a "main" class. Would not that make more sense ?

to be sure. the compiled classes b.t. customizer doesn't have the 
runtime cp list explicitly. unfortunately, in all of the classpath 
wrangling that we've done over the past 6 months the general classpath 
customizer section has fallen out of date and is mis-leading. the intent 
now is that no where are there classpath tabs called runtime or 
[implicitly] compile time. just Classpath, and Boot Classpath. whether 
it is run time or compile time is deducible by on which object you're 
looking at it from (b.t. or profile). i think that is consistent with 
what you're asking for.

thanks,
cL

-- 

ui.netbeans.org
interaction designer
[email protected]