To whom may concern, A general consideration of this I believe general Problem . Any of us which have for whatever reason done an investment in Maven 1.0.2, pretty heavy as in our case , are at moment in kind of Limbo.
We found inherent bugs in the Maven 1.0.2, that is not know where and if will be solved : namely leak due to buggy version of Jelly libraries http://jira.codehaus.org/browse/MAVEN-1294. That for small project is not visible but when you start using multiprojects of more then 20 projects and run reports and use the dashboard for aggregating the results than you hit the upper physical memory management of the JDK ... On the other side that bus is claimed to be solved since Maven 1.1-Beta and as Maven 1.1 claims to be backward compatible that would be the natural next try .... But there you find that the Entities are no longer supported ..... show stopper :-( I understand the new concept implemented in Maven 2.x ... and it makes definitely sense ... but we need a sort of continuous support to maintain our investment ... A simple solution would be to allow those which have such a need to move to Maven 1.1 and still using entities ... knowing anyway that if a restructuring is needed Maven 2 is there ....another solution could be to fix the Jelly problem directly in the 1.0.x stream ? Any help to clarify those points will be greatly accepted ... Best Regards Michele [EMAIL PROTECTED] re.com 23/03/2006 17:37 Please respond to "Maven Users List" <[EMAIL PROTECTED] To .org> "Maven Users List" <users@maven.apache.org> cc Subject Re: [Maven-1.1] Migration 1.0.2 to 1.1 Entity problem Hello Arnaud, I got the impression that it is a bit more complex ... I tried to endorse the JDK with the correct xerses implementation ... but I think that would fix in case only the ENTITY System reference .... :-( Could it be that the problem is the internally used parser (xpp3) that parse the POM and it explicitely disable the Entities declaration ... in that case what would be the fix ? Any help is welcome ... Regards Michele "Arnaud HERITIER" <[EMAIL PROTECTED] m> 23/03/2006 17:22 Please respond to "Maven Users List" To <[EMAIL PROTECTED] "Maven Users List" <users@maven.apache.org> .org> cc Subject Re: [Maven-1.1] Migration 1.0.2 to 1.1 Entity problem The tip in the compatibility issues for Entities and JDK 1.4 must fix it arnaud* * On 3/23/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > To whom it may concern, > > I can read at the compatibility issue page that : > > Parse errors on previously 'valid' project files > > > project.xml files that used to work in older versions of Maven may now > present parse errors. The parser in Maven 1.1 is much less tolerant of > invalid project.xml files to avoid silently masking syntax errors. Some > XML > features are not enabled (such as DOCTYPE ENTITY declarations) - see the > FAQ for an explanation. and then in the FAQ it is stated : > > > "As of Maven 1.1, external entities will not be enabled by default in > project.xml, and their use is discouraged in Maven 1.0.x as well. There > will still be the ability to use them, but it will have to be enabled. " > > That is unfortunately our case ..... in order to make the first part of > the migration fast, Can anyone explaining how to enable external entities > in Project.xml with Maven 1.x .... > > Best Regards > > Michele > > > > This e-mail, including attachments, is intended for the person(s) or > company named and may contain confidential and/or legally privileged > information. Unauthorized disclosure, copying or use of this information > may be unlawful and is prohibited. If you are not the intended recipient, > please delete this message and notify the sender > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > This e-mail, including attachments, is intended for the person(s) or company named and may contain confidential and/or legally privileged information. Unauthorized disclosure, copying or use of this information may be unlawful and is prohibited. If you are not the intended recipient, please delete this message and notify the sender --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] This e-mail, including attachments, is intended for the person(s) or company named and may contain confidential and/or legally privileged information. Unauthorized disclosure, copying or use of this information may be unlawful and is prohibited. If you are not the intended recipient, please delete this message and notify the sender --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
