This is more of a maven question probably, but I have an app that
needs versions of the jars built with jdk 1.5 and I'm using the
http://build.clojure.org/snapshots repo where they appear to be built
with 1.6. Are there versions (or plans to support 1.5 versions) in a
maven repo somewhere?
Thanks
No, but you can change the configs and recompile.
Clojure itself uses Ant, so "ant" on a machine with only Java 1.5
should do the trick. To install that custom JAR in your local Maven
repository, download the "Maven Ant Tasks" JAR and run:
ant -lib /path/to/maven-ant-tasks.jar ci-build
Contrib u
I figured as much. The issue for me is the Netbeans plugin must have
1.5 java and I was hoping to get these from a repo. I suppose I can
build the 1.5 versions and publish them (somewhere). I'll look into
this.
Thanks,
Eric
On Mar 21, 8:50 pm, Stuart Sierra wrote:
> No, but you can change th
On Mar 21, 2010, at 8:50 PM, Stuart Sierra wrote:
No, but you can change the configs and recompile.
Clojure itself uses Ant, so "ant" on a machine with only Java 1.5
should do the trick. To install that custom JAR in your local Maven
repository, download the "Maven Ant Tasks" JAR and run:
ant
Actually, this is more complicated than I thought. The build
processes will use whatever default version of Java is installed
locally.
Maven has config options for the Java *compiler* version to use, but
that will only work for .java source files (of which there are non in
contrib). The version
By the way, Ant has the same problem: you can specify a target JDK
version in the "javac" task, but not the "java" task. So the Clojure
compiler runs with the default "java" executable on the local machine.
-SS
On Mar 22, 11:54 am, Stuart Sierra
wrote:
> Actually, this is more complicated than
Do we really care what they are built with, or only that they target
1.5? (i.e. javac's -target option)
On Mar 22, 2010, at 11:54 AM, Stuart Sierra wrote:
Actually, this is more complicated than I thought. The build
processes will use whatever default version of Java is installed
locally.
I'll try this out since I'm stuck and wanted to get out of the
business of building my own versions of clojure/-contrib (hence the
move to maven).
What do other projects do that have maven repos with similar
contraints? Are there separate entries in the repo?
On Mar 22, 3:53 pm, Rich Hickey wrot
The new version of the maven-clojure-compiler plugin now supports the
toolchains API to solve this ( running maven under 1.6, compiling with 1.5)
but that won't help clojure itself:
You can read more about this at:
http://maven.apache.org/guides/mini/guide-using-toolchains.html
I really need t
Hi Eric,
Eric Thorsen writes:
> This is more of a maven question probably, but I have an app that
> needs versions of the jars built with jdk 1.5 and I'm using the
> http://build.clojure.org/snapshots repo where they appear to be built
> with 1.6. Are there versions (or plans to support 1.5 ver
I was grabbing the snapshots of clojure and clojure-contrib and using
them in a Netbeans plugin (which needs 1.5. Netbeans just crashes in
an RT call).
(System/getProperty "java.vm.version")
The above returns the running jvm version. I was looking at the jar
manifest to see what it was built with
On Mar 23, 9:08 am, Eric Thorsen wrote:
> Having the target=1.5 property set for the clojure-contrib build might
> get me where I need to be. I just have not had a chance to try it
> yet.
The clojure-contrib build does not call javac, so it shouldn't matter.
-SS
--
You received this message b
On Mar 23, 9:08 am, Eric Thorsen wrote:
> The above returns the running jvm version. I was looking at the jar
> manifest to see what it was built with which is where I saw the 1.6
> reference for clojure-contrib.
Oh, it's the JAR manifest that's the problem? Maybe this will help:
http://maven.a
On Mar 23, 9:08 am, Eric Thorsen wrote:
> The above returns the running jvm version. I was looking at the jar
> manifest to see what it was built with which is where I saw the 1.6
> reference for clojure-contrib.
If the JAR manifest is the problem, the following pom.xml lines will
change it:
On Mar 23, 9:43 am, Stuart Sierra wrote:
> If the JAR manifest is the problem, the following pom.xml lines will
> change it:
Yet another option is to supply a completely custom manifest file that
omits the Build-Jdk line altogether.
But I still think the correct solution is to install JDK 1.5 on
15 matches
Mail list logo
