On 11 September 2012 20:27, Oliver Heger wrote:
> Am 11.09.2012 00:08, schrieb sebb:
>
>> On 10 September 2012 20:33, Oliver Heger
>> wrote:
>>>
>>> Am 09.09.2012 14:26, schrieb sebb:
>>>
On 8 September 2012 15:45, Oliver Heger
wrote:
>
>
> Am 08.09.2012 03:44, schrieb sebb
Am 11.09.2012 00:08, schrieb sebb:
On 10 September 2012 20:33, Oliver Heger wrote:
Am 09.09.2012 14:26, schrieb sebb:
On 8 September 2012 15:45, Oliver Heger
wrote:
Am 08.09.2012 03:44, schrieb sebb:
On 7 September 2012 20:46, Oliver Heger
wrote:
Hi all,
the pom was updated to make
On 11 September 2012 19:22, Jörg Schaible wrote:
> sebb wrote:
>
>> On 10 September 2012 20:33, Oliver Heger
>> wrote:
>>> Am 09.09.2012 14:26, schrieb sebb:
>>>
On 8 September 2012 15:45, Oliver Heger
wrote:
>
> [snip]
>
> Some classes of [lang] are exposed in the public API of
>>
sebb wrote:
> On 10 September 2012 20:33, Oliver Heger
> wrote:
>> Am 09.09.2012 14:26, schrieb sebb:
>>
>>> On 8 September 2012 15:45, Oliver Heger
>>> wrote:
[snip]
Some classes of [lang] are exposed in the public API of
[configuration]. For
instance, variable substitution in
On 10 September 2012 20:33, Oliver Heger wrote:
> Am 09.09.2012 14:26, schrieb sebb:
>
>> On 8 September 2012 15:45, Oliver Heger
>> wrote:
>>>
>>> Am 08.09.2012 03:44, schrieb sebb:
>>>
On 7 September 2012 20:46, Oliver Heger
wrote:
>
>
> Hi all,
>
> the pom was up
Am 09.09.2012 14:26, schrieb sebb:
On 8 September 2012 15:45, Oliver Heger wrote:
Am 08.09.2012 03:44, schrieb sebb:
On 7 September 2012 20:46, Oliver Heger
wrote:
Hi all,
the pom was updated to make 2.0-SNAPSHOT the current development version.
This means we are free to implement major c
Am 09.09.2012 18:28, schrieb Benedikt Ritter:
Hi Oliver,
there are a lot of @author tags. As far as I know, the use of author
tags is deprecated in commons, so the mentioned developers and
contributors should be moved to pom.xml and changes.xml.
Yes, this is true. When changing code, e.g. when
Hi Oliver,
there are a lot of @author tags. As far as I know, the use of author
tags is deprecated in commons, so the mentioned developers and
contributors should be moved to pom.xml and changes.xml.
Benedikt
2012/9/7 Oliver Heger :
> Hi all,
>
> the pom was updated to make 2.0-SNAPSHOT the curr
On 8 September 2012 15:45, Oliver Heger wrote:
> Am 08.09.2012 03:44, schrieb sebb:
>
>> On 7 September 2012 20:46, Oliver Heger
>> wrote:
>>>
>>> Hi all,
>>>
>>> the pom was updated to make 2.0-SNAPSHOT the current development version.
>>> This means we are free to implement major changes withou
Am 08.09.2012 18:45, schrieb Ralph Goers:
If you are going to break compatibility the package names need to be changed.
I really dislike CombinedConfiguration. Having the combined nodes point into
other configuration nodes makes reloading fragile which is why it now copies
nodes. This means
If you are going to break compatibility the package names need to be changed.
I really dislike CombinedConfiguration. Having the combined nodes point into
other configuration nodes makes reloading fragile which is why it now copies
nodes. This means that a DynamicCombinedConfiguration that has
Am 08.09.2012 03:44, schrieb sebb:
On 7 September 2012 20:46, Oliver Heger wrote:
Hi all,
the pom was updated to make 2.0-SNAPSHOT the current development version.
This means we are free to implement major changes without having to enforce
binary backwards compatibility.
BC breakage will req
On 7 September 2012 20:46, Oliver Heger wrote:
> Hi all,
>
> the pom was updated to make 2.0-SNAPSHOT the current development version.
> This means we are free to implement major changes without having to enforce
> binary backwards compatibility.
BC breakage will require package and Maven coordin
Hi all,
the pom was updated to make 2.0-SNAPSHOT the current development
version. This means we are free to implement major changes without
having to enforce binary backwards compatibility.
The question is: What are the goals for version 2.0? I would recommend
to define a clear focus so that
14 matches
Mail list logo
