The IBM jdk isn't different at its core, I just made sure all of it's libraries were in the ant task's classpath.
diongillard wrote: > > The best way to run certain IBM tasks is to use the supplied ws_ant > batch file or shell script. > > That way the environment is set up for you and there's no jdk issues. > > On Fri, Jul 11, 2008 at 5:17 AM, JerodLass <[EMAIL PROTECTED]> > wrote: >> >> I'm still interested, but I solved my EJB problem a different way. >> >> >> >> Jerod Lass wrote: >>> >>> I am trying to use retroweaver to compile gradle, but since i am on a >>> 1.4 >>> jdk, other 1.5 classes in gradle's classpath (starting with slf4j after >>> I >>> retro-wove gradle) arent able to be used. I could take each one out and >>> use >>> retroweaver on them, but this would take a long time and I don't know >>> anything about retroweaver anyway(yet, but I am very interested). Let >>> me >>> know if you figure out a jdk 1.4-compatible gradle distribution or if I >>> can >>> help out. >>> >>> -Jerod >>> >>> On Thu, Jul 10, 2008 at 11:48 AM, Hans Dockter <[EMAIL PROTECTED]> wrote: >>> >>>> >>>> On Jul 10, 2008, at 6:26 PM, Jerod Lass wrote: >>>> >>>> Is there a way to run gradle with the 1.5 jdk but tell it to compile >>>>> everything with a specific 1.4 jdk? >>>>> >>>> >>>> To Gradle compile task delegates to the Ant javac task. You can set >>>> most >>>> of >>>> the options via the Gradle task. Have a look at: http:// >>>> ant.apache.org/manual/CoreTasks/javac.html >>>> >>>> This task has the options fork an executable. So this looks pretty >>>> straight >>>> forward. >>>> >>>> Even if only the ant task uses 1.4, it should work. It's only the ant >>>>> task that needs and IBM-specific 1.4 jdk. Thanks >>>>> >>>> >>>> I don't see a way to execute an Ant task with a different JDK within >>>> the >>>> same JVM Gradle is running. I guess you have to use an external process >>>> for >>>> this. An ugly way of doing this would be to provide a build xml or a >>>> groovy >>>> script which calls the Ant task. You could call the script with the IBM >>>> JDK >>>> from your build.gradle file. Not very nice but it should work. >>>> >>>> Providing a JDK 1.4 compatible Gradle looks like the easiest solution. >>>> >>>> - Hans >>>> >>>> >>>> -- >>>> Hans Dockter >>>> Gradle Project lead >>>> http://www.gradle.org >>>> >>>> >>>> >>>> >>>> >>>> --------------------------------------------------------------------- >>>> To unsubscribe from this list, please visit: >>>> >>>> http://xircles.codehaus.org/manage_email >>>> >>>> >>>> >>> >>> >> >> -- >> View this message in context: >> http://www.nabble.com/gradle-with-a-1.4-jdk-tp18385565p18389946.html >> Sent from the gradle-user mailing list archive at Nabble.com. >> >> >> --------------------------------------------------------------------- >> To unsubscribe from this list, please visit: >> >> http://xircles.codehaus.org/manage_email >> >> >> > > > > -- > dIon Gillard > There are only two kinds of programming languages: those people always > bitch about and those nobody uses. (Bjarne Stroustrup) > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > > > -- View this message in context: http://www.nabble.com/gradle-with-a-1.4-jdk-tp18385565p18404297.html Sent from the gradle-user mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
