You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openoffice.apache.org by Pedro Giffuni <pf...@apache.org> on 2012/02/12 04:23:43 UTC

[code] (stax-api) Anyone still uses Java 5?

Hi;

We currently carry an old version(1.0) of StAX-api that is
under copyleft. This library is supposed to be needed by
Saxon-B but we don't really use this library because
is now part of OpenJDK 1.6 and upper so we only need it
when trying to use an old version of Java and we are not
using the system-saxon. 

The latest version of this library (1.2) is now under
Apache License 2:

http://stax.codehaus.org/

I started to update it but I can't really test it:
deinstalling jdk6 to bring back jdk5 and rebuild
everything is not exactly fun ;).

Anyone wants to play a bit with a patch? Alternatively
we could just leave things as they are and drop
StaX out of the distribution after 3.4-Release.

Pedro.


Re: [code] (stax-api) Anyone still uses Java 5?

Posted by Pedro Giffuni <pf...@apache.org>.
On 02/13/12 12:01, Jürgen Schmidt wrote:
...
>
> I agree that we should move into a code freeze mode as soon as we have 
> the neon replacement. But in general I would strongly suggest that we 
> move this kind of changes after the release and focus on bug fixing at 
> the moment. Our primary goal should be really to get the 3.4 finished.
>


The big updates (from my side) are finished: I only updated a couple of
components that were very inflexible and you can't set up with configure.
FWIW, my local package does use updated versions of saxon,
beanshell, etc.

cheers,

Pedro.


Re: [code] (stax-api) Anyone still uses Java 5?

Posted by Jürgen Schmidt <jo...@googlemail.com>.
On 2/13/12 5:48 PM, Pedro Giffuni wrote:
> On 02/13/12 11:24, Rob Weir wrote:
>> On Sun, Feb 12, 2012 at 8:34 PM, Pedro Giffuni<pf...@apache.org> wrote:
>>> Hmm...
>>>
>>> On 02/12/12 17:06, Rob Weir wrote:
>>> ...
>>>
>>>> Anyone wants to play a bit with a patch? Alternatively we could just
>>>> leave
>>>> things as they are and drop StaX out of the distribution after
>>>> 3.4-Release.
>>>> +1 for changing after 3.4.
>>>>
>>>>
>>> Rob's message arrived *after* I committed the update.
>>> It's a low risk update though; it helps a bit with the license
>>> clearance issues and the instructions for using the prebuilt
>>> distribution were just too outdated so let's wait to see what
>>> the buildbot thinks about it.
>>>
>> Low risk, but not zero. At the very least, since we've already
>> started a formal QA pass for 3.4, it would be great if any changes
>> made from now on mentioned what, if anything, should be retested.
>> This probably also means that changes should come with a BZ issue
>> where such information is recorded.
>
> In my build, and in the buildbots so far, the impact has been
> zero and I am ready to revert if there is any need, but I see
> your point.
>
> I think we should still update some components: the security
> stuff I mentioned earlier and apache-commons. I can open
> bugzilla items for those. FWIW, I had a look at updating icc
> and Lucene but those are very high risk IMHO.
>> I'm open to arguments that we're not at that point in the 3.4 release
>> cycle yet. But I think at some point we want to engage that level of
>> change discipline.
> We should go further indeed: when we are ready for a release
> we should call a code freeze: I suggest that should be called right
> after the neon replacement is finished. We should probably be
> thinking on branching after that too.

I agree that we should move into a code freeze mode as soon as we have 
the neon replacement. But in general I would strongly suggest that we 
move this kind of changes after the release and focus on bug fixing at 
the moment. Our primary goal should be really to get the 3.4 finished.

Juergen

>
> Pedro.
>
>
>> -Rob
>>
>>> FWIW, I am more worried about some other updates that
>>> should be done for security reasons; nss and libxmlsec,
>>> but I have currently no plans to touch those.
>>>
>>> Cheers,
>>>
>>> Pedro.
>>>
>


Re: [code] (stax-api) Anyone still uses Java 5?

Posted by Pedro Giffuni <pf...@apache.org>.
On 02/13/12 11:24, Rob Weir wrote:
> On Sun, Feb 12, 2012 at 8:34 PM, Pedro Giffuni<pf...@apache.org>  wrote:
>> Hmm...
>>
>> On 02/12/12 17:06, Rob Weir wrote:
>> ...
>>
>>> Anyone wants to play a bit with a patch? Alternatively we could just leave
>>> things as they are and drop StaX out of the distribution after 3.4-Release.
>>> +1 for changing after 3.4.
>>>
>>>
>> Rob's message arrived *after* I committed the update.
>> It's a low risk update though; it helps a bit with the license
>> clearance issues and the instructions for using the prebuilt
>> distribution were just too outdated so let's wait to see what
>> the buildbot thinks about it.
>>
> Low risk, but not zero.  At the very least, since we've already
> started a formal QA pass for 3.4, it would be great if any changes
> made from now on mentioned what, if anything, should be retested.
> This probably also means that changes should come with a BZ issue
> where such information is recorded.

In my build, and in the buildbots so far, the impact has been
zero and I am ready to revert if there is any need, but I see
your point.

I think we should still update some components: the security
stuff I mentioned earlier and apache-commons. I can open
bugzilla items for those. FWIW, I had a look at updating icc
and Lucene but those are very high risk IMHO.
> I'm open to arguments that we're not at that point in the 3.4 release
> cycle yet.  But I think at some point we want to engage that level of
> change discipline.
We should go further indeed: when we are ready for a release
we should call a code freeze: I suggest that should be called right
after the neon replacement is finished. We should probably be
thinking on branching after that too.

Pedro.


> -Rob
>
>> FWIW, I am more worried about some other updates that
>> should be done for security reasons; nss and libxmlsec,
>> but I have currently no plans to touch those.
>>
>> Cheers,
>>
>> Pedro.
>>


Re: [code] (stax-api) Anyone still uses Java 5?

Posted by Rob Weir <ro...@apache.org>.
On Sun, Feb 12, 2012 at 8:34 PM, Pedro Giffuni <pf...@apache.org> wrote:
> Hmm...
>
> On 02/12/12 17:06, Rob Weir wrote:
> ...
>
>> Anyone wants to play a bit with a patch? Alternatively we could just leave
>> things as they are and drop StaX out of the distribution after 3.4-Release.
>> +1 for changing after 3.4.
>>
>>
>
> Rob's message arrived *after* I committed the update.
> It's a low risk update though; it helps a bit with the license
> clearance issues and the instructions for using the prebuilt
> distribution were just too outdated so let's wait to see what
> the buildbot thinks about it.
>

Low risk, but not zero.  At the very least, since we've already
started a formal QA pass for 3.4, it would be great if any changes
made from now on mentioned what, if anything, should be retested.
This probably also means that changes should come with a BZ issue
where such information is recorded.

I'm open to arguments that we're not at that point in the 3.4 release
cycle yet.  But I think at some point we want to engage that level of
change discipline.

-Rob

> FWIW, I am more worried about some other updates that
> should be done for security reasons; nss and libxmlsec,
> but I have currently no plans to touch those.
>
> Cheers,
>
> Pedro.
>

Re: [code] (stax-api) Anyone still uses Java 5?

Posted by Pedro Giffuni <pf...@apache.org>.
Hmm...

On 02/12/12 17:06, Rob Weir wrote:
...
> Anyone wants to play a bit with a patch? Alternatively we could just 
> leave things as they are and drop StaX out of the distribution after 
> 3.4-Release.
> +1 for changing after 3.4.
>
>

Rob's message arrived *after* I committed the update.
It's a low risk update though; it helps a bit with the license
clearance issues and the instructions for using the prebuilt
distribution were just too outdated so let's wait to see what
the buildbot thinks about it.

FWIW, I am more worried about some other updates that
should be done for security reasons; nss and libxmlsec,
but I have currently no plans to touch those.

Cheers,

Pedro.


Re: [code] (stax-api) Anyone still uses Java 5?

Posted by Rob Weir <ro...@apache.org>.
On Sat, Feb 11, 2012 at 10:23 PM, Pedro Giffuni <pf...@apache.org> wrote:
> Hi;
>
> We currently carry an old version(1.0) of StAX-api that is
> under copyleft. This library is supposed to be needed by
> Saxon-B but we don't really use this library because
> is now part of OpenJDK 1.6 and upper so we only need it
> when trying to use an old version of Java and we are not
> using the system-saxon.
>
> The latest version of this library (1.2) is now under
> Apache License 2:
>
> http://stax.codehaus.org/
>
> I started to update it but I can't really test it:
> deinstalling jdk6 to bring back jdk5 and rebuild
> everything is not exactly fun ;).
>
> Anyone wants to play a bit with a patch? Alternatively
> we could just leave things as they are and drop
> StaX out of the distribution after 3.4-Release.
>

+1 for changing after 3.4.

> Pedro.
>

Re: [code] (stax-api) Anyone still uses Java 5?

Posted by Pedro Giffuni <pf...@apache.org>.
On 02/12/12 08:55, Carl Marcum wrote:
> On 02/11/2012 10:23 PM, Pedro Giffuni wrote:
>> Hi;
>>
>> We currently carry an old version(1.0) of StAX-api that is
>> under copyleft. This library is supposed to be needed by
>> Saxon-B but we don't really use this library because
>> is now part of OpenJDK 1.6 and upper so we only need it
>> when trying to use an old version of Java and we are not
>> using the system-saxon.
>>
>> The latest version of this library (1.2) is now under
>> Apache License 2:
>>
>> http://stax.codehaus.org/
>>
>> I started to update it but I can't really test it:
>> deinstalling jdk6 to bring back jdk5 and rebuild
>> everything is not exactly fun ;).
>>
>> Anyone wants to play a bit with a patch? Alternatively
>> we could just leave things as they are and drop
>> StaX out of the distribution after 3.4-Release.
>>
>> Pedro.
>>
>>
>
> +1 on dropping Java 5.
>
> The only reason I could see to keep Java 5 would be to not break users 
> programs or a due to a platform we wish to support that could not use 
> Java 6.
>
> I checked Oracle's compatibility page for Java SE 5 to 6 [1] and 
> virtually all programs that were built on 5 will run on 6.
>
> I am even running Java 6 on a Win 2000 instance I keep for testing.
> Supported platforms for Java 6 [2].
>
> [1] 
> http://www.oracle.com/technetwork/java/javase/compatibility-137541.html
>
> [2] 
> http://www.oracle.com/technetwork/java/javase/system-configurations-135212.html
>
> Best regards,
> Carl

Some of the Java stuff that we carry was actually developed with
Java 4 so I am rather surprised that everything seems to work!

I committed an update to the StaX API as revision 1243337;
since it is only used for older versions of Java it's doubtful
anyone will notice any difference.

FWIW, the instructions to use the binary version were outdated
and it seems all other Apache projects decided to abandon the
old StaX version we had in the repository:
https://issues.apache.org/jira/browse/XMLBEANS-308

cheers,

Pedro.


Re: [code] (stax-api) Anyone still uses Java 5?

Posted by Carl Marcum <cm...@apache.org>.
On 02/11/2012 10:23 PM, Pedro Giffuni wrote:
> Hi;
>
> We currently carry an old version(1.0) of StAX-api that is
> under copyleft. This library is supposed to be needed by
> Saxon-B but we don't really use this library because
> is now part of OpenJDK 1.6 and upper so we only need it
> when trying to use an old version of Java and we are not
> using the system-saxon.
>
> The latest version of this library (1.2) is now under
> Apache License 2:
>
> http://stax.codehaus.org/
>
> I started to update it but I can't really test it:
> deinstalling jdk6 to bring back jdk5 and rebuild
> everything is not exactly fun ;).
>
> Anyone wants to play a bit with a patch? Alternatively
> we could just leave things as they are and drop
> StaX out of the distribution after 3.4-Release.
>
> Pedro.
>
>

+1 on dropping Java 5.

The only reason I could see to keep Java 5 would be to not break users 
programs or a due to a platform we wish to support that could not use 
Java 6.

I checked Oracle's compatibility page for Java SE 5 to 6 [1] and 
virtually all programs that were built on 5 will run on 6.

I am even running Java 6 on a Win 2000 instance I keep for testing.
Supported platforms for Java 6 [2].

[1] http://www.oracle.com/technetwork/java/javase/compatibility-137541.html

[2] 
http://www.oracle.com/technetwork/java/javase/system-configurations-135212.html

Best regards,
Carl