[lang] 1.3 problems

classic Classic list List threaded Threaded
13 messages Options
Reply | Threaded
Open this post in threaded view
|

[lang] 1.3 problems

Henri Yandell
We've three 1.3 specific compile time problems. Do we move to 1.4, or
just fix these?

Two currently in SVN:

    [javac] /Users/hen/apache/commons-proper/lang/src/java/org/apache/commons/lang/text/ExtendedMessageFormat.java:356:
MessageFormat(java.lang.String,java.util.Locale) has private access in
java.text.MessageFormat
    [javac]         super(pattern, locale);
    [javac]         ^
    [javac] /Users/hen/apache/commons-proper/lang/src/java/org/apache/commons/lang/text/NumberMetaFormat.java:120:
cannot resolve symbol
    [javac] symbol  : method getIntegerInstance  (java.util.Locale)
    [javac] location: class java.text.NumberFormat
    [javac]                     .getIntegerInstance(getLocale()));

and one in the simplest solution to LANG-381.

Thoughts? 1.4 time?

Hen

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [lang] 1.3 problems

Ben Speakmon-3
1.4 time.

On Dec 1, 2007 8:20 PM, Henri Yandell <[hidden email]> wrote:

> We've three 1.3 specific compile time problems. Do we move to 1.4, or
> just fix these?
>
> Two currently in SVN:
>
>    [javac]
> /Users/hen/apache/commons-proper/lang/src/java/org/apache/commons/lang/text/ExtendedMessageFormat.java:356:
> MessageFormat(java.lang.String,java.util.Locale) has private access in
> java.text.MessageFormat
>    [javac]         super(pattern, locale);
>    [javac]         ^
>    [javac]
> /Users/hen/apache/commons-proper/lang/src/java/org/apache/commons/lang/text/NumberMetaFormat.java:120:
> cannot resolve symbol
>    [javac] symbol  : method getIntegerInstance  (java.util.Locale)
>    [javac] location: class java.text.NumberFormat
>    [javac]                     .getIntegerInstance(getLocale()));
>
> and one in the simplest solution to LANG-381.
>
> Thoughts? 1.4 time?
>
> Hen
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>
Reply | Threaded
Open this post in threaded view
|

RE: [lang] 1.3 problems

Gary Gregory
In reply to this post by Henri Yandell
1.4 time!

Gary

> -----Original Message-----
> From: Henri Yandell [mailto:[hidden email]]
> Sent: Saturday, December 01, 2007 8:21 PM
> To: Commons Developers List
> Subject: [lang] 1.3 problems
>
> We've three 1.3 specific compile time problems. Do we move to 1.4, or
> just fix these?
>
> Two currently in SVN:
>
>     [javac] /Users/hen/apache/commons-
> proper/lang/src/java/org/apache/commons/lang/text/ExtendedMessageFormat.j
> ava:356:
> MessageFormat(java.lang.String,java.util.Locale) has private access in
> java.text.MessageFormat
>     [javac]         super(pattern, locale);
>     [javac]         ^
>     [javac] /Users/hen/apache/commons-
> proper/lang/src/java/org/apache/commons/lang/text/NumberMetaFormat.java:
> 120:
> cannot resolve symbol
>     [javac] symbol  : method getIntegerInstance  (java.util.Locale)
>     [javac] location: class java.text.NumberFormat
>     [javac]                     .getIntegerInstance(getLocale()));
>
> and one in the simplest solution to LANG-381.
>
> Thoughts? 1.4 time?
>
> Hen
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [lang] 1.3 problems

Stephen Colebourne
In reply to this post by Henri Yandell
My preference is to keep this release and branch of [lang] as 1.3
compatible, primarily as part of the purpose of [lang] is to fill in JDK
holes for old JDKs.

I would then suggest that [lang] switches to Java 5, in a new package.

Stephen


Henri Yandell wrote:

> We've three 1.3 specific compile time problems. Do we move to 1.4, or
> just fix these?
>
> Two currently in SVN:
>
>     [javac] /Users/hen/apache/commons-proper/lang/src/java/org/apache/commons/lang/text/ExtendedMessageFormat.java:356:
> MessageFormat(java.lang.String,java.util.Locale) has private access in
> java.text.MessageFormat
>     [javac]         super(pattern, locale);
>     [javac]         ^
>     [javac] /Users/hen/apache/commons-proper/lang/src/java/org/apache/commons/lang/text/NumberMetaFormat.java:120:
> cannot resolve symbol
>     [javac] symbol  : method getIntegerInstance  (java.util.Locale)
>     [javac] location: class java.text.NumberFormat
>     [javac]                     .getIntegerInstance(getLocale()));
>
> and one in the simplest solution to LANG-381.
>
> Thoughts? 1.4 time?
>
> Hen
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [lang] 1.3 problems

Hanson Char
1.5+ time!

On Dec 2, 2007 1:45 AM, Stephen Colebourne <[hidden email]> wrote:

> My preference is to keep this release and branch of [lang] as 1.3
> compatible, primarily as part of the purpose of [lang] is to fill in JDK
> holes for old JDKs.
>
> I would then suggest that [lang] switches to Java 5, in a new package.
>
> Stephen
>
>
>
> Henri Yandell wrote:
> > We've three 1.3 specific compile time problems. Do we move to 1.4, or
> > just fix these?
> >
> > Two currently in SVN:
> >
> >     [javac] /Users/hen/apache/commons-proper/lang/src/java/org/apache/commons/lang/text/ExtendedMessageFormat.java:356:
> > MessageFormat(java.lang.String,java.util.Locale) has private access in
> > java.text.MessageFormat
> >     [javac]         super(pattern, locale);
> >     [javac]         ^
> >     [javac] /Users/hen/apache/commons-proper/lang/src/java/org/apache/commons/lang/text/NumberMetaFormat.java:120:
> > cannot resolve symbol
> >     [javac] symbol  : method getIntegerInstance  (java.util.Locale)
> >     [javac] location: class java.text.NumberFormat
> >     [javac]                     .getIntegerInstance(getLocale()));
> >
> > and one in the simplest solution to LANG-381.
> >
> > Thoughts? 1.4 time?
> >
> > Hen
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [hidden email]
> > For additional commands, e-mail: [hidden email]
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

RE: [lang] 1.3 problems

Jörg Schaible-2
In reply to this post by Stephen Colebourne
1.5 + new package!

Stephen Colebourne wrote:

> My preference is to keep this release and branch of [lang] as 1.3
> compatible, primarily as part of the purpose of [lang] is to
> fill in JDK
> holes for old JDKs.
>
> I would then suggest that [lang] switches to Java 5, in a new package.
>
> Stephen
>
>
> Henri Yandell wrote:
>> We've three 1.3 specific compile time problems. Do we move to 1.4,
>> or just fix these?
>>
>> Two currently in SVN:
>>
>>     [javac]
> /Users/hen/apache/commons-proper/lang/src/java/org/apache/comm
ons/lang/text/ExtendedMessageFormat.java:356:
>> MessageFormat(java.lang.String,java.util.Locale) has private access
>>     in java.text.MessageFormat [javac]         super(pattern,
>>     locale); [javac]         ^
>>     [javac]
> /Users/hen/apache/commons-proper/lang/src/java/org/apache/comm
ons/lang/text/NumberMetaFormat.java:120:

>> cannot resolve symbol
>>     [javac] symbol  : method getIntegerInstance  (java.util.Locale)
>>     [javac] location: class java.text.NumberFormat
>>     [javac]                     .getIntegerInstance(getLocale()));
>>
>> and one in the simplest solution to LANG-381.
>>
>> Thoughts? 1.4 time?
>>
>> Hen
>>
>>
> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [hidden email]
>> For additional commands, e-mail: [hidden email]
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [lang] 1.3 problems

Matt Benson
In reply to this post by Henri Yandell
--- Henri Yandell <[hidden email]> wrote:

> We've three 1.3 specific compile time problems. Do
> we move to 1.4, or
> just fix these?
>
> Two currently in SVN:
>
>     [javac]
>
/Users/hen/apache/commons-proper/lang/src/java/org/apache/commons/lang/text/ExtendedMessageFormat.java:356:
> MessageFormat(java.lang.String,java.util.Locale) has
> private access in
> java.text.MessageFormat
>     [javac]         super(pattern, locale);
>     [javac]         ^
>     [javac]
>
/Users/hen/apache/commons-proper/lang/src/java/org/apache/commons/lang/text/NumberMetaFormat.java:120:

> cannot resolve symbol
>     [javac] symbol  : method getIntegerInstance
> (java.util.Locale)
>     [javac] location: class java.text.NumberFormat
>     [javac]                    
> .getIntegerInstance(getLocale()));
>
> and one in the simplest solution to LANG-381.
>
> Thoughts? 1.4 time?

Ugh, sorry the subject didn't catch my attention
during perfunctory weekend email checking.  This
ExtendedMessageFormat stuff has sure been a can of
worms.  I don't think there's any reason to force a
JRE upgrade on my account.  I've fixed one of these
(will check in momentarily) and will be investigating
the other.

-Matt

>
> Hen
>
>
---------------------------------------------------------------------
> To unsubscribe, e-mail:
> [hidden email]
> For additional commands, e-mail:
> [hidden email]
>
>



      ____________________________________________________________________________________
Get easy, one-click access to your favorites.
Make Yahoo! your homepage.
http://www.yahoo.com/r/hs 

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [lang] 1.3 problems

Ben Speakmon-3
Another issue is that Sun has end-of-lifed JDK 1.3. It doesn't make sense to
me to continue to support a platform even Sun has given up on.

On Dec 3, 2007 7:26 AM, Matt Benson <[hidden email]> wrote:

> --- Henri Yandell <[hidden email]> wrote:
>
> > We've three 1.3 specific compile time problems. Do
> > we move to 1.4, or
> > just fix these?
> >
> > Two currently in SVN:
> >
> >     [javac]
> >
>
> /Users/hen/apache/commons-proper/lang/src/java/org/apache/commons/lang/text/ExtendedMessageFormat.java:356:
> > MessageFormat(java.lang.String,java.util.Locale) has
> > private access in
> > java.text.MessageFormat
> >     [javac]         super(pattern, locale);
> >     [javac]         ^
> >     [javac]
> >
>
> /Users/hen/apache/commons-proper/lang/src/java/org/apache/commons/lang/text/NumberMetaFormat.java:120:
> > cannot resolve symbol
> >     [javac] symbol  : method getIntegerInstance
> > (java.util.Locale)
> >     [javac] location: class java.text.NumberFormat
> >     [javac]
> > .getIntegerInstance(getLocale()));
> >
> > and one in the simplest solution to LANG-381.
> >
> > Thoughts? 1.4 time?
>
> Ugh, sorry the subject didn't catch my attention
> during perfunctory weekend email checking.  This
> ExtendedMessageFormat stuff has sure been a can of
> worms.  I don't think there's any reason to force a
> JRE upgrade on my account.  I've fixed one of these
> (will check in momentarily) and will be investigating
> the other.
>
> -Matt
>
> >
> > Hen
> >
> >
> ---------------------------------------------------------------------
> > To unsubscribe, e-mail:
> > [hidden email]
> > For additional commands, e-mail:
> > [hidden email]
> >
> >
>
>
>
>
>  ____________________________________________________________________________________
> Get easy, one-click access to your favorites.
> Make Yahoo! your homepage.
> http://www.yahoo.com/r/hs
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>
Reply | Threaded
Open this post in threaded view
|

Re: [lang] 1.3 problems

Christoph Kutzinski
That's not entirely true

http://java.sun.com/j2se/1.3/download.html
"On Solaris 8 - J2SE 1.3.1 is continuing in the Sun End of Life (EOL) process. The EOL transition period began Oct 25, 2004 and will continue until the the end of the Solaris 8 five year Vintage Support Period."

;-)

> Another issue is that Sun has end-of-lifed JDK 1.3. It doesn't make sense
> to
> me to continue to support a platform even Sun has given up on.
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [lang] 1.3 problems

Ben Speakmon-3
Point taken :)

On Dec 3, 2007 10:12 AM, Christoph Kutzinski <[hidden email]> wrote:

> That's not entirely true
>
> http://java.sun.com/j2se/1.3/download.html
> "On Solaris 8 - J2SE 1.3.1 is continuing in the Sun End of Life (EOL)
> process. The EOL transition period began Oct 25, 2004 and will continue
> until the the end of the Solaris 8 five year Vintage Support Period."
>
> ;-)
>
> > Another issue is that Sun has end-of-lifed JDK 1.3. It doesn't make
> sense
> > to
> > me to continue to support a platform even Sun has given up on.
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>
Reply | Threaded
Open this post in threaded view
|

Re: [lang] 1.3 problems

Matt Benson
In reply to this post by Ben Speakmon-3

--- Ben Speakmon <[hidden email]> wrote:

> Another issue is that Sun has end-of-lifed JDK 1.3.
> It doesn't make sense to
> me to continue to support a platform even Sun has
> given up on.

I know what it's like to work in slow-adoption shops.
My current shop is just _about_ to move from 1.4 to
1.5 .  While this isn't as drastic as being stuck on
1.3, the shop I worked for previously stayed on 1.2
pretty much until the place folded up in 2005.
Fundamental libs like commons-* should IMHO support
older JDKs if at all possible, despite the fact that
the drastic change represented by generics will force
us to go to Java 5+ for e.g. [collections].

-Matt

>
> On Dec 3, 2007 7:26 AM, Matt Benson
> <[hidden email]> wrote:
>
> > --- Henri Yandell <[hidden email]> wrote:
> >
> > > We've three 1.3 specific compile time problems.
> Do
> > > we move to 1.4, or
> > > just fix these?
> > >
> > > Two currently in SVN:
> > >
> > >     [javac]
> > >
> >
> >
>
/Users/hen/apache/commons-proper/lang/src/java/org/apache/commons/lang/text/ExtendedMessageFormat.java:356:

> > > MessageFormat(java.lang.String,java.util.Locale)
> has
> > > private access in
> > > java.text.MessageFormat
> > >     [javac]         super(pattern, locale);
> > >     [javac]         ^
> > >     [javac]
> > >
> >
> >
>
/Users/hen/apache/commons-proper/lang/src/java/org/apache/commons/lang/text/NumberMetaFormat.java:120:

> > > cannot resolve symbol
> > >     [javac] symbol  : method getIntegerInstance
> > > (java.util.Locale)
> > >     [javac] location: class
> java.text.NumberFormat
> > >     [javac]
> > > .getIntegerInstance(getLocale()));
> > >
> > > and one in the simplest solution to LANG-381.
> > >
> > > Thoughts? 1.4 time?
> >
> > Ugh, sorry the subject didn't catch my attention
> > during perfunctory weekend email checking.  This
> > ExtendedMessageFormat stuff has sure been a can of
> > worms.  I don't think there's any reason to force
> a
> > JRE upgrade on my account.  I've fixed one of
> these
> > (will check in momentarily) and will be
> investigating
> > the other.
> >
> > -Matt
> >
> > >
> > > Hen
> > >
> > >
> >
>
---------------------------------------------------------------------

> > > To unsubscribe, e-mail:
> > > [hidden email]
> > > For additional commands, e-mail:
> > > [hidden email]
> > >
> > >
> >
> >
> >
> >
> >
>
____________________________________________________________________________________
> > Get easy, one-click access to your favorites.
> > Make Yahoo! your homepage.
> > http://www.yahoo.com/r/hs
> >
> >
>
---------------------------------------------------------------------
> > To unsubscribe, e-mail:
> [hidden email]
> > For additional commands, e-mail:
> [hidden email]
> >
> >
>



      ____________________________________________________________________________________
Be a better friend, newshound, and
know-it-all with Yahoo! Mobile.  Try it now.  http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ 


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [lang] 1.3 problems

Paul Benedict
>
> --- Ben Speakmon <[hidden email]> wrote:
>
> > Another issue is that Sun has end-of-lifed JDK 1.3.
> > It doesn't make sense to
> > me to continue to support a platform even Sun has
> > given up on.
>

Since all contributions are on a volunteer-basis, if somebody really wants
it fixed for 1.3 JDK compat, he/she can produce a patch and test case since
it will minimize the effort involved. Otherwise, move on to the next ticket.
:-) Also if the POM doesn't specify 1.4 for compiling, it definitely should
now.

Paul
Reply | Threaded
Open this post in threaded view
|

Re: [lang] 1.3 problems

Henri Yandell
In reply to this post by Ben Speakmon-3
Yeah, let me boot up my Solaris 8 box ;)

Hen

On Dec 3, 2007 10:15 AM, Ben Speakmon <[hidden email]> wrote:

> Point taken :)
>
>
> On Dec 3, 2007 10:12 AM, Christoph Kutzinski <[hidden email]> wrote:
>
> > That's not entirely true
> >
> > http://java.sun.com/j2se/1.3/download.html
> > "On Solaris 8 - J2SE 1.3.1 is continuing in the Sun End of Life (EOL)
> > process. The EOL transition period began Oct 25, 2004 and will continue
> > until the the end of the Solaris 8 five year Vintage Support Period."
> >
> > ;-)
> >
> > > Another issue is that Sun has end-of-lifed JDK 1.3. It doesn't make
> > sense
> > > to
> > > me to continue to support a platform even Sun has given up on.
> > >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [hidden email]
> > For additional commands, e-mail: [hidden email]
> >
> >
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]