On Tue, 2008-06-24 at 18:09 +0200, Mauro Manfrin wrote: > Sure, I'm glad to submit you my patches. > I prepared a zip file with the patches > (but how can I give it to you?).
i've created a project in JIRA: https://issues.apache.org/jira/browse/ECS please create an issue and attach your patch > I modified classes since the jakarta ECS SVN repository. > You will find the ConcreteElement class, and subsequent 5 classes adaptions. > Pay attention, these patches are based on the trunk, not the 1.4.2 version. > > What are you planning? A new release? A simple trunk commit? a simple commit will be the first stage once you've confirmed the first works, i'll look into creating a release > I benefit on these contact, for submitting you another very simple > evolution, really usefull for adoption of ecs in frameworks. > ECSDefaults can be configured only statically from a properties file, not > dinamically. > I think this is a purposeless. > But some features like CaseType, Codeset and most of all PrettyPrinting are > often needed to be changed dinamically > (for example in webapp lifecycle, switching from a test to a production > state). > So I propose you a very simple evolution of ECSDefaults class, exposing 3 > methods to change these default property values. > (how can I send you this version?) create aPatch ;-) (and submit using JIRA) - robet
signature.asc
Description: This is a digitally signed message part
