You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@excalibur.apache.org by Shash Chatterjee <sh...@badfw.org> on 2005/07/16 22:03:52 UTC
Excalibur and JDK-1.3
Guys,
I am trying to get Excalibur tagged and the RC's released (not going to
get time to do all of it at once, but I'll do as many as I can).
Started with Framework, running into a problem with framework-impl and
logkit.
http://wiki.apache.org/excalibur/ReleaseManagement says to make sure and
compile with JDK-1.3 (I am using Sun jdk-1.3.1_15). Of course,
o.a.a.f.logger.Jdk14Logger does not compile. Similar issues with logkit.
Are we supposed to overlook this rule?
Shash
Re: Excalibur and JDK-1.3
Posted by Antonio Gallardo <ag...@agssa.net>.
Shash Chatterjee wrote:
> Guys,
>
> I am trying to get Excalibur tagged and the RC's released (not going
> to get time to do all of it at once, but I'll do as many as I can).
> Started with Framework, running into a problem with framework-impl and
> logkit.
>
> http://wiki.apache.org/excalibur/ReleaseManagement says to make sure
> and compile with JDK-1.3 (I am using Sun jdk-1.3.1_15). Of course,
> o.a.a.f.logger.Jdk14Logger does not compile. Similar issues with logkit.
>
> Are we supposed to overlook this rule?
Try to use java 1.4 and in Ant set compiler target=1.3
Best Regards,
Antonio Gallardo
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@excalibur.apache.org
For additional commands, e-mail: dev-help@excalibur.apache.org
Re: Excalibur and JDK-1.3
Posted by "Sasvata (Shash) Chatterjee" <sh...@badfw.org>.
Leo/All,
> It ain't a rule, its a guideline :-)
>
>IIRC compiling for target=1.3 with 1.4 gave us some issues with some little
>bit of code somewhere at some point, and I think it was Peter Donald who
>pointed that out; I think this was related to logkit itself (which I believe
>could actually still compile using 1.2). We've probably got bits of code
>spread all over the codebase that will only compile against 1.4.
>
>I'm not against building jars using 1.4, as long as we ship buildable source
>distributions so that people that need to can replace particular jars with
>1.3-compatible ones that can otherwise be trusted to be the same.
>
>
Sounds good. I will build with Sun jdk-1.4.2_08 and set
maven.compile.target=1.3.
However, I am running into yet another problem, I would really
appreciate if another committer could try it (say, on logkit)and tell me
if it is my machine/env. or something else.
I am on Win-XP (latest updates/SPs), and Cygwin. I am able to run the
Maven (1.0.2) excalibur:release goal just fine, when using jdk-1.3.
Using, JDK-1.4, or 1.5, makes the build hang when it gets to one of
the <ant:exec> tags, starting with when it invokes "gpg", but also with
the "ssh" and "svn" invocations. I have tried maven-1.1-beta, same
behavior. I have tried making the command "gpg.exe", I have tried the
spawn="true" attribute of <ant:exec>, I have tried wrapping the
executables in a batch file, I have tried using a windows command shell,
rather than Cygwin/Bash shell. I have tried pretty much everything.
Nothing seems to work.
In a fit of rage, I spent all day yesterday installing Fedora Core 4 on
a spare disk....I am done with it. I am playing with the Eclipse
install and setting up the Java env. now, so will be able to try there
soon. In the meantime, someone please try on Win-XP and let me know.
Thanks,
Shash
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@excalibur.apache.org
For additional commands, e-mail: dev-help@excalibur.apache.org
Re: Excalibur and JDK-1.3
Posted by Leo Simons <ma...@leosimons.com>.
Hi shash!
On 16-07-2005 22:03, "Shash Chatterjee" <sh...@badfw.org> wrote:
> I am trying to get Excalibur tagged and the RC's released (not going to get
> time to do all of it at once, but I'll do as many as I can). Started with
> Framework, running into a problem with framework-impl and logkit.
>
> http://wiki.apache.org/excalibur/ReleaseManagement says to make sure and
> compile with JDK-1.3 (I am using Sun jdk-1.3.1_15). Of course,
> o.a.a.f.logger.Jdk14Logger does not compile. Similar issues with logkit.
>
> Are we supposed to overlook this rule?
It ain't a rule, its a guideline :-)
IIRC compiling for target=1.3 with 1.4 gave us some issues with some little
bit of code somewhere at some point, and I think it was Peter Donald who
pointed that out; I think this was related to logkit itself (which I believe
could actually still compile using 1.2). We've probably got bits of code
spread all over the codebase that will only compile against 1.4.
I'm not against building jars using 1.4, as long as we ship buildable source
distributions so that people that need to can replace particular jars with
1.3-compatible ones that can otherwise be trusted to be the same.
IOW, as long as the source distro is of good quality I wouldn't feel too bad
about bending a few rules if you need to. Projects like cocoon have long
since given up on binary distros, and in fact I know from trying out
gump+jdk 1.3 that there's a whole bunch of vital dependencies for most of
the apache java projects which you can't compile on a 1.3 jdk out of the
box. Its a mess. Don't spend tooooo much time trying to clean it :-)
Cheers,
Leo
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@excalibur.apache.org
For additional commands, e-mail: dev-help@excalibur.apache.org