Re: UI for setting up runtime classpath

Cau Petre,

please read my comments 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.

The Runtime Classpath shouldn't be there IMO. The uispec is inconsistent 
in describing the classpath customizers, in the section 'Managing the 
Classpath' is describes the customizer with 'General CP', 'Runtime CP' 
and 'Boot CP' (Fig. 39) to be presented on all the Project Node, Build 
Target, Execution Profile. But when you look to the section 'Managing 
Build targets and Outputs' (Fig 46.) you can see that the CCBT 
customizer doesn't contain the 'Runtime CP' tab.

Chris, Jano, could you improve this. I would suggest to leave the 
section 'Managing the Classpath' for generic description of how the CP 
customizers should look like, what are the principles of classpath 
definition, inheritance, etc. In addition to this sections for specific 
objects in the project should define which classpath types can be 
defined for them and how they are customized using generic CP customizer.

>
> 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 ?

Sure, the Runtime Classpath customizer is already available on execution 
profiles. It should be removed from CCBT.
-vita