[armedbear-devel] No JSR-223 code in abcl-src-0.15.tar.gz

[Mark Evenson]

On 8/28/09 9:07 AM, Alessio Stalla wrote:
[…]
>> a) fix 'build.xml' to not include any scripting artifacts when compiled with
>> java5 in the absence of JSR-223
>
> Right, I can do that. I wasn't aware that build.xml was used for
> releases too when I added JSR-223 to it.

I committed a fix as [svn r12121][1] (our messages crossed in passing). 
  If you could look at this, I think we are ok.

[1]: http://trac.common-lisp.net/armedbear/changeset/12121

>> b) change the source archive targets to complain if Java6 is not used to
>> make a release
>>
>> c) use Java6 to make a release
>>
>> d) Test that this release works in both Java5/Java6
>
> Ok. I'll do all this and make some tests. Independent testing by
> someone else would be useful, I think.

I just finished testing under Mac OSX with the Apple Java VMs that a jar 
built with Java6 (and JSR-223 code) works with Java5.  With your 
assurance about the separate nature of the JSR-223 codebase, I think 
we're pretty safe on this, but further testing would be welcome.

> Does the 0.15 release lie in its own branch? If not, how can we
> backport the changes to build.xml to it?

Would you really go for a 0.15.1 release?  I would be more for starting 
the 0.16 release process soon.  The only problem there, is that I 
suspect that Erik is going to be real busy in September (personal 
reasons).  There is a branch for 0.15 ("branches/0.15.x/abcl"), so 
backporting the changes shouldn't be much of problem.  Making a release 
might be a bit tricky, because I think only Erik has the necessary 
authorization rights for pushing files onto Sourceforge.  Or maybe Ville 
can do that?  Alternatively, we could host the ABCL release on 
GoogleCode under my abcl-dynamic-install project (I already host 
pre-built 0.15 abcl.jar's there linked from the Cliki page.






-- 
"A screaming comes across the sky.  It has happened before, but there
is nothing to compare to it now."