Am 17.02.2011 08:34, schrieb Jörg Schaible:
Hi,
Oliver Heger wrote:
Am 17.02.2011 02:10, schrieb Ralph Goers:
Thanks. But I have a larger issue.
We have been doing performance testing and the synchronization in
AbstractFileConfiguration, DynamicCombinedConfiguration, and
MultiFileHierarchi
Hi,
Oliver Heger wrote:
> Am 17.02.2011 02:10, schrieb Ralph Goers:
>> Thanks. But I have a larger issue.
>>
>> We have been doing performance testing and the synchronization in
>> AbstractFileConfiguration, DynamicCombinedConfiguration, and
>> MultiFileHierarchicalConfiguration are showing up
As I see it, the problem with the experimental branch is that we haven't yet
"flipped" the configuration so that everything is based on a
HierarchicalConfiguration nor have we gotten rid of the attribute splitting
stuff. The reloading is mostly a problem with how CombinedConfiguration works -
h
Am 17.02.2011 02:10, schrieb Ralph Goers:
Thanks. But I have a larger issue.
We have been doing performance testing and the synchronization in
AbstractFileConfiguration, DynamicCombinedConfiguration, and
MultiFileHierarchicalConfiguration are showing up as predominant hot spots.
These woul
Am 16.02.2011 22:48, schrieb Jörg Schaible:
Hi Oliver,
The sources are already compiled using the higher JDK by then (and mvn
test won't clean that compile run).
-Rahul
Yes, but I hoped that the excluded classes would not be loaded at all,
so it would not be a problem that they have been
Thanks. But I have a larger issue.
We have been doing performance testing and the synchronization in
AbstractFileConfiguration, DynamicCombinedConfiguration, and
MultiFileHierarchicalConfiguration are showing up as predominant hot spots.
These would be easy to fix if I could use java.util.co
Hi Oliver,
Oliver Heger wrote:
> Am 16.02.2011 22:05, schrieb Rahul Akolkar:
>> On Wed, Feb 16, 2011 at 3:45 PM, Oliver Heger
>> wrote:
>>> Am 15.02.2011 21:23, schrieb Oliver Heger:
Am 10.02.2011 13:09, schrieb sebb:
>
>>
>
> FYI:
>
> Note that the Commons Parent
Am 16.02.2011 22:05, schrieb Rahul Akolkar:
On Wed, Feb 16, 2011 at 3:45 PM, Oliver Heger
wrote:
Am 15.02.2011 21:23, schrieb Oliver Heger:
Am 10.02.2011 13:09, schrieb sebb:
FYI:
Note that the Commons Parent POM was changed some while ago to add
profiles java-1.4, java-1.3 etc. which
On Wed, Feb 16, 2011 at 3:45 PM, Oliver Heger
wrote:
> Am 15.02.2011 21:23, schrieb Oliver Heger:
>>
>> Am 10.02.2011 13:09, schrieb sebb:
>>>
>>>
>>> FYI:
>>>
>>> Note that the Commons Parent POM was changed some while ago to add
>>> profiles java-1.4, java-1.3 etc. which change the Java version
Am 15.02.2011 21:23, schrieb Oliver Heger:
Am 10.02.2011 13:09, schrieb sebb:
On 10 February 2011 07:27, Ralph Goers wrote:
On Feb 9, 2011, at 11:04 PM, Oliver Heger wrote:
Am 10.02.2011 00:48, schrieb Ralph Goers:
On Feb 9, 2011, at 2:54 PM, Jörg Schaible wrote:
Hi Ralph,
Ralph Goers w
Am 10.02.2011 13:09, schrieb sebb:
On 10 February 2011 07:27, Ralph Goers wrote:
On Feb 9, 2011, at 11:04 PM, Oliver Heger wrote:
Am 10.02.2011 00:48, schrieb Ralph Goers:
On Feb 9, 2011, at 2:54 PM, Jörg Schaible wrote:
Hi Ralph,
Ralph Goers wrote:
The latest versions of Maven requir
On 10 February 2011 07:27, Ralph Goers wrote:
>
> On Feb 9, 2011, at 11:04 PM, Oliver Heger wrote:
>
>> Am 10.02.2011 00:48, schrieb Ralph Goers:
>>>
>>> On Feb 9, 2011, at 2:54 PM, Jörg Schaible wrote:
>>>
Hi Ralph,
Ralph Goers wrote:
> The latest versions of Maven require
On Feb 9, 2011, at 11:04 PM, Oliver Heger wrote:
> Am 10.02.2011 00:48, schrieb Ralph Goers:
>>
>> On Feb 9, 2011, at 2:54 PM, Jörg Schaible wrote:
>>
>>> Hi Ralph,
>>>
>>> Ralph Goers wrote:
>>>
The latest versions of Maven require JDK 1.5. The pom (or the Commons
Parent) should b
Am 10.02.2011 00:48, schrieb Ralph Goers:
On Feb 9, 2011, at 2:54 PM, Jörg Schaible wrote:
Hi Ralph,
Ralph Goers wrote:
The latest versions of Maven require JDK 1.5. The pom (or the Commons
Parent) should be specifying that the target for Commons Configuration is
1.4. I've run this build
On Feb 9, 2011, at 2:54 PM, Jörg Schaible wrote:
> Hi Ralph,
>
> Ralph Goers wrote:
>
>> The latest versions of Maven require JDK 1.5. The pom (or the Commons
>> Parent) should be specifying that the target for Commons Configuration is
>> 1.4. I've run this build many times successfully (I us
Hi Ralph,
Ralph Goers wrote:
> The latest versions of Maven require JDK 1.5. The pom (or the Commons
> Parent) should be specifying that the target for Commons Configuration is
> 1.4. I've run this build many times successfully (I use 1.6). I don't
> see any problem requiring the build to use
The latest versions of Maven require JDK 1.5. The pom (or the Commons Parent)
should be specifying that the target for Commons Configuration is 1.4. I've
run this build many times successfully (I use 1.6). I don't see any problem
requiring the build to use Maven 2.2.x or Maven 3 and/or have a
Hi,
because of the dependency to VFS 2.0 (SNAPSHOT) which requires Java 1.5,
it is currently not possible to build [configuration] with a JDK 1.4:
the vfs jar causes a bad class version error.
I am not sure what would be the best strategy to solve this problem.
Probably we need some Maven ma
18 matches
Mail list logo