I'm just thinking, in the case of tools.jar, that a prepopulated variable/expression might be appropriate rather than requiring each user to have to specify this profile. And if the built in version doesn't suffice for platform X running DontCallMeJavaVM, they can always use the profile.
What do you think? - Brett John Casey wrote: > Build it in how? Anything having to do with system paths is going to be > really fragile, we knew that. But, it's also what profiles were designed > to do...the only problem is in detecting the specific JVM (rather than > just the OS). I agree that it seems a little complex, but the concept of > system scoped dependencies inherently means you have to be *very* > careful to handle multiple environments. > > If you have any ideas on how to make this cleaner, I'd be eager to > discuss it. > > -john --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
