Richard Liang wrote: > Yes. it's good to put jetty JAR into deploy/build/test. Thanks a lot. > > Now I have several questions: > > 1) How to refer to the jars in "deploy/build/test"? > As Paulex suggested, defining another Class Variable "HDK_HOME" may be > a good option. But there may be problems for support.jar. Because if > you also check out the support project, you will have duplicate > support in build path: one is added through Class Variable, another > one is in Plug-in dependencies.
Let me back-up a moment... If you are planning to embed the Jetty code in the support bundle then you will need to make it a dependent JAR of the 'support' project, modify the Bundle-ClassPath: to refer to the Jetty JAR, and export any packages you want visible, etc. But if you plan to include the Jetty code as a stand-alone bundle you can copy it directly into a deploy/build/test/jetty directory with it's own manifest, like we do for ICU, Xerces, etc. in the JRE. So far we have been doing the latter. > 2) Do you think we shall put luni-kernel-stubs.jar and > security-kernel-stubs.jar into deploy/build instead of > deploy/jdk/jre/lib/boot/? Well we want people to be able to compile their Java code using a Harmony JDK, so they cannot be absent from there. Regards, Tim > Any suggestion? Thank a lot. > > Best regards, > Richard > > On 2/6/07, Tim Ellison <[EMAIL PROTECTED]> wrote: >> No, we don't want a new dependency on that directory or you will break >> the ability to develop a single module against the HDK [1]. >> >> The jetty JAR should be copied into the HDK (in deploy\build\test >> alongside the other test support JARs). >> >> [1] http://harmony.apache.org/hdk.html >> >> Regards, >> Tim >> >> >> >> Richard Liang wrote: >> > Thanks a lot. I will use the "Classpath Variable" solution. But I'm >> > always open to new >> > >> > On 2/6/07, Alex Blewitt <[EMAIL PROTECTED]> wrote: >> >> That seems like a reasonable solution, and also what's generally done >> >> in projects where there is a known dependency structure. I'd say go >> >> for it. >> >> >> >> Alex. >> >> >> >> On 06/02/07, Richard Liang <[EMAIL PROTECTED]> wrote: >> >> > Hello All, >> >> > >> >> > I'm going to write/enable some jetty based test cases for luni. And >> >> > now there is a question in Eclipse. To compile the jetty based test >> >> > cases, I have to add the jetty jars into luni's classpath. But the >> >> > jetty jars are put into "depends" folder. To avoid using absolute >> >> > path, I suggest we define a Classpath Variable "HARMONY_DEPENDS" >> which >> >> > refers to "depends", then we use this Classpath Variable to look for >> >> > the jars. The .classpath will contain entry like: >> >> > >> >> > <classpathentry kind="var" >> >> path="HARMONY_DEPENDS/jars/jetty/jetty-6.0.0.jar"/> >> >> > >> >> > But the problem of this option is that Eclipse users have to define >> >> > the "HARMONY_DEPENDS" manually when they set up a new Eclipse >> >> > environment. >> >> > >> >> > Any comments/suggestion? Thanks a lot >> >> > >> >> > Best regards, >> >> > -- >> >> > Richard Liang >> >> > China Development Lab, IBM >> >> > >> >> >> > >> > >> > >
