Re: [Fwd: [jira] Closed: (MNG-2339) ${project.*} are interpreted in the wrong place]
Joerg Heinicke pisze: Eventually ... Joerg Yep... But can we start to think about pushing minimal version require for working with Cocoon? I know that 2.0.9 is not released yet but it looks like Maven folks are planning the release already. I'm very motivated to remove all these crap MNG-2339 introduced to our POMs. -- Best regards, Grzegorz Kossakowski
Re: [#COCOON-2168] ResourceReader produces Java Heap Overflow when reading a huge resource - ASF JIRA
Antonio Gallardo pisze: 1MB Makes sense. +1 -- Best regards, Grzegorz Kossakowski
[continuum] BUILD ERROR: Apache Cocoon [build root]
Online report : http://vmbuild.apache.org/continuum/buildResult.action?buildId=62691projectId=51 Build statistics: State: Error Previous State: Ok Started at: Fri 7 Mar 2008 19:56:16 -0800 Finished at: Fri 7 Mar 2008 19:57:58 -0800 Total time: 1m 41s Build Trigger: Schedule Build Number: 0 Exit code: 0 Building machine hostname: vmbuild.apache.org Operating system : Linux(unknown) Java Home version : java version 1.4.2_15 Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_15-b02) Java HotSpot(TM) Client VM (build 1.4.2_15-b02, mixed mode) Builder version : Maven version: 2.0.7 Java version: 1.4.2_15 OS name: linux version: 2.6.20-16-server arch: i386 SCM Changes: No files changed Dependencies Changes: No dependencies changed Build Error: Provider message: The svn command failed. Command output: --- svn: PROPFIND request failed on '/repos/asf/cocoon/trunk' svn: PROPFIND of '/repos/asf/cocoon/trunk': could not connect to server (http://svn.apache.org) ---
Re: [Fwd: [jira] Closed: (MNG-2339) ${project.*} are interpreted in the wrong place]
On 07.03.2008 17:41, Grzegorz Kossakowski wrote: Yep... But can we start to think about pushing minimal version require for working with Cocoon? I know that 2.0.9 is not released yet but it looks like Maven folks are planning the release already. I'm very motivated to remove all these crap MNG-2339 introduced to our POMs. Can you describe what the current situation is? I thought we have problems only when using Java 1.4. You are talking about fixes to our POMs because of this issue. In which cases exactly do they apply and why not in the other ones? Are they only for Java 5 or has Java 5 never been a problem? Depending on the answer to the last question we could just recommend (i.e. not enforce) either use Maven 2.0.9 or Java 5. If removing all the crap breaks Cocoon with Java 5 as well I definitely prefer to raise the minimal required Maven version. If not I'm fine either way. Joerg
