Re: cvs commit: incubator-geronimo project.xml

[Jacek Laskowski <jl...@apache.org>]

dain@apache.org wrote:

> dain        2004/09/01 21:31:08
> 
>   Modified:    applications/jmxdebug project.xml
>                applications/demo project.xml
>                etc      version-info.ent
>                .        project.xml
>   Log:
>   Changed version tags to use entity references

Awesome! I really like the idea of using the entity references. I have 
seen it the first time in OpenEJB2 (I guess it was Dave who made the 
changes) and I was deeply entertained.

I haven't seen it anywhere, but in Geronimo and OpenEJB (which simply 
means I don't spend too much time reading others' code :)). I think 
people tend to use highly complicated solutions before using such simple 
ones.

I hope others have also so much fun reading the code. These're lessons 
you'll never have a chance to take at no charge!

Just couldn't resist to not send it to the ML :)

Jacek

Re: cvs commit: incubator-geronimo project.xml

[David Blevins <da...@visi.com>]

On Thu, Sep 02, 2004 at 09:18:31AM -0400, Patrick Mueller wrote:
> Jacek Laskowski wrote:
> >Awesome! I really like the idea of using the entity references. I have 
> >seen it the first time in OpenEJB2 (I guess it was Dave who made the 
> >changes) and I was deeply entertained.
> 

> I've been burned on this kind of thing way too many times, with
> folks using either lamo parsers or even just regex's to read XML
> files.  I gave up.

Regex XML parsing... yikes. 

> Although ... one thing I have done is to make use of Ant's replace bits 
> to sort of simulate this.  Keep a 'template' with a 'macro' in it in 
> some kind of a template directory, then generate the real file from the 
> template and a value for the macros.  

Actually we are working towards that.  We'd like to be able to
manipulate the version-info.ent file at release time to dynamically
switch all the SNAPSHOT versions to their real versions, check that
file in, tag cvs, then roll the file back.

Consolodating all the version information into one file is the first
step as keeping templates of all our build files and j2ee-*-plan.xml
files would be a total nightmare.

-David

Re: cvs commit: incubator-geronimo project.xml

[Patrick Mueller <pm...@yahoo.com>]

Jacek Laskowski wrote:

> dain@apache.org wrote:
> 
>> dain        2004/09/01 21:31:08
>>
>>   Modified:    applications/jmxdebug project.xml
>>                applications/demo project.xml
>>                etc      version-info.ent
>>                .        project.xml
>>   Log:
>>   Changed version tags to use entity references
> 
> 
> Awesome! I really like the idea of using the entity references. I have 
> seen it the first time in OpenEJB2 (I guess it was Dave who made the 
> changes) and I was deeply entertained.

I like using entity references also.  Except that they require you use a 
REAL XML parser to 'expand' them.  I've been burned on this kind of 
thing way too many times, with folks using either lamo parsers or even 
just regex's to read XML files.  I gave up.

Although ... one thing I have done is to make use of Ant's replace bits 
to sort of simulate this.  Keep a 'template' with a 'macro' in it in 
some kind of a template directory, then generate the real file from the 
template and a value for the macros.  Not as dynamic as using entities, 
but it solves the problem of people reading my files with lamo parsers.

-- 
Patrick Mueller
pmuellr@yahoo.com