drop Scala 2.8 support (error deprecated use sys.error) #115

Closed
idot opened this Issue Nov 12, 2011 · 5 comments

Comments

Projects
None yet
4 participants
@idot

idot commented Nov 12, 2011

scalaxb generated scalaxb class leads to warnings when compiling with scala 2.9.1

scalaxb/scalaxb.scala:628: method error in object Predef is deprecated: Use sys.error(message) instead

case _ => error("unknown DataRecord.")
@eed3si9n

This comment has been minimized.

Show comment
Hide comment
@eed3si9n

eed3si9n Nov 12, 2011

Owner

I've been keeping 2.8.1 compatibility around since many of the major players in the community are still on it.
Maybe it's time to start generating 2.9.1 code by default and add option flag?

Owner

eed3si9n commented Nov 12, 2011

I've been keeping 2.8.1 compatibility around since many of the major players in the community are still on it.
Maybe it's time to start generating 2.9.1 code by default and add option flag?

@idot

This comment has been minimized.

Show comment
Hide comment
@idot

idot Nov 13, 2011

On Nov 12, 2011, at 6:51 AM, eugene yokota wrote:

I've been keeping 2.8.1 compatibility around since many of the major players in the community are still on it.
Maybe it's time to starte generating 2.9.1 code by default and add option flag?


Reply to this email directly or view it on GitHub:
#115 (comment)

Oh, I understand. Now that I started compiling everything with deprecation it just gets more noisy.
I think its easier for you to keep source compatibility until they really remove error from Predef
and I don't really care about warnings not coming from my code.

idot commented Nov 13, 2011

On Nov 12, 2011, at 6:51 AM, eugene yokota wrote:

I've been keeping 2.8.1 compatibility around since many of the major players in the community are still on it.
Maybe it's time to starte generating 2.9.1 code by default and add option flag?


Reply to this email directly or view it on GitHub:
#115 (comment)

Oh, I understand. Now that I started compiling everything with deprecation it just gets more noisy.
I think its easier for you to keep source compatibility until they really remove error from Predef
and I don't really care about warnings not coming from my code.

@ghost ghost assigned eed3si9n Feb 22, 2012

@fommil

This comment has been minimized.

Show comment
Hide comment
@fommil

fommil Mar 6, 2013

I was just about to file this as well :-)

I also get a lot of deprecation warnings for Elem.apply:

method error in object Predef is deprecated: Use `sys.error(message)` instead
method apply in object Elem is deprecated: Use the other apply method in this object

fommil commented Mar 6, 2013

I was just about to file this as well :-)

I also get a lot of deprecation warnings for Elem.apply:

method error in object Predef is deprecated: Use `sys.error(message)` instead
method apply in object Elem is deprecated: Use the other apply method in this object
@cmacher

This comment has been minimized.

Show comment
Hide comment

cmacher commented Apr 11, 2013

+1

@eed3si9n

This comment has been minimized.

Show comment
Hide comment
@eed3si9n

eed3si9n Apr 13, 2013

Owner

@fommil Elem.apply got deprecated in 2.10. I am guessing people still want 2.9.x support.

Owner

eed3si9n commented Apr 13, 2013

@fommil Elem.apply got deprecated in 2.10. I am guessing people still want 2.9.x support.

@eed3si9n eed3si9n closed this in 51a4059 Apr 13, 2013

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment