I Get where you are coming from. But if you did want to make a breaking
change then this would be a really appropriate place to do it. I mean if not
on a major version number then when?
Just a thought.
James
On 5 Feb 2011 00:03, "Stephen Colebourne" <scolebou...@joda.org> wrote:
> The problem is that the major release number is mostly about removing
> a few deprecated methods. Were I to make this change it would break
> user code, which no other change so far would cause. I don't want to
> get into the JAR-hell situation.
>
> Stephen
>
>
> On 4 February 2011 23:57, James Richardson <ja...@time4tea.net> wrote:
>> Well there is a major release version coming up... That would be an
>> appropriate time to make a breaking change, no?
>> James
>>
>> On 4 Feb 2011 23:43, "Stephen Colebourne" <scolebou...@joda.org> wrote:
>>> On 4 February 2011 23:39, Viktor Hedefalk <hedef...@gmail.com> wrote:
>>>> I guess the most obvious backwards compatability issue would be if
>>>> someone had implemented his own DateTimeParser. Hopefully that
>>>> shouldn't be too common though, it's really just an internal
>>>> interface, right?
>>>
>>> Unfortunately, no. I have encouraged users to implement this interface
>>> to solve some formatting issues. Thus I can't change it. Nor would I
>>> want to create a DateTimeParser2.
>>>
>>> Stephen
>>>
>>>
>>>
------------------------------------------------------------------------------
>>> The modern datacenter depends on network connectivity to access
resources
>>> and provide services. The best practices for maximizing a physical
>>> server's
>>> connectivity to a physical network are well understood - see how these
>>> rules translate into the virtual world?
>>> http://p.sf.net/sfu/oracle-sfdevnlfb
>>> _______________________________________________
>>> Joda-interest mailing list
>>> Joda-interest@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/joda-interest
>>>
>>
>>
------------------------------------------------------------------------------
>> The modern datacenter depends on network connectivity to access resources
>> and provide services. The best practices for maximizing a physical
server's
>> connectivity to a physical network are well understood - see how these
>> rules translate into the virtual world?
>> http://p.sf.net/sfu/oracle-sfdevnlfb
>> _______________________________________________
>> Joda-interest mailing list
>> Joda-interest@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/joda-interest
>>
>>
>
>
------------------------------------------------------------------------------
> The modern datacenter depends on network connectivity to access resources
> and provide services. The best practices for maximizing a physical
server's
> connectivity to a physical network are well understood - see how these
> rules translate into the virtual world?
> http://p.sf.net/sfu/oracle-sfdevnlfb
> _______________________________________________
> Joda-interest mailing list
> Joda-interest@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/joda-interest
>
------------------------------------------------------------------------------
The modern datacenter depends on network connectivity to access resources
and provide services. The best practices for maximizing a physical server's
connectivity to a physical network are well understood - see how these
rules translate into the virtual world?
http://p.sf.net/sfu/oracle-sfdevnlfb
_______________________________________________
Joda-interest mailing list
Joda-interest@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/joda-interest
