Agreed. The setup instructions are pretty brief as it is (though you do have to
infer them from the Ant-based instructions in the BUILD file - we might want to
add an Eclipse-specific version). What you suggest seems like it could actually
make things more complicated.
On Thursday, May 28, 2009, at 05:38AM, "Christopher Brind"
<[email protected]> wrote:
>I'm not really keen on the idea. The only thing I really had to do to get
>things compiling in Eclipse was add a reference to the plugin.jar since I am
>on Mac and Apple's JRE doesn't include it by default.
>
>There's also the subtle implication that everyone is using Eclipse, but I
>know Todd uses Emacs and I wouldn't want to put off NetBeans fans by being
>too Eclipse heavy in the project documentation.
>
>If think if people are going to developer *for* Pivot the "pain" of setting
>up their environment will actually work as an aid to learning about all the
>different bits of Pivot. =)
>
>Cheers,
>Chris
>
>
>2009/5/28 Sandro Martini <[email protected]>
>
>> Hi to all,
>> what do you think on adding a reference to most common jar (needed by
>> Pivot) in some subprojects, to have them already pre-configured in
>> Eclipse ?
>>
>> For example:
>> - the wtk subproject needs the Java Plugin2 jar (), and the Java
>> Compiler (tools.jar)
>> - the demos subproject will need the Java Web Start jar (javaws.jsr)
>> - and others could apply in the future
>> - maybe this could also be useful for stax jars ... but for them it's
>> more simpler today having jars in a lib subdir
>>
>> Eclipse Environment Variables defined and pointing to jars in my
>> environment:
>> JAVA_PLUGIN_LIB -> C:/jdk1.6.0/jre/lib/plugin.jar
>> JAVA_COMPILER_LIB -> C:/jdk1.6.0/lib/tools.jar
>> JAVA_WEB_START_LIB -> C:/jdk1.6.0/jre/lib/javaws.jar
>>
>> I haven't tried to put variables inside the value, referring to JDK
>> (and maybe also to JRE) as other eclipse variables, but in any case i
>> prefer to keep all things inside the development environment, without
>> pointing of having to change global variables, so any process that
>> needs a different JAVA_HOME or any other variable will set them only
>> for its use.
>>
>> In my development environment this is the setup, and i think it's a
>> little simpler, or at least a little clear for developers.
>> Without this, for example the wtk subproject given compilation errors
>> and there isn't inside a file with what to do ... ok, but there is in
>> the general documentation. So, having in the project Build Path
>> (eclipse) a link to a not-defined variable, could be simpler to fix
>> it.
>>
>>
>> Thanks,
>> Sandro
>>
>
