XDoclet stability was Re: more undocumented attrs

[Peter Donald <pe...@apache.org>]

Hi,

At 07:26 AM 6/22/2002 -0400, you wrote:
>On a related note, I'm still using the old XDoclet and have not upgraded.
>Upgrading will require lots of refactoring because the API changed.

As related to this. Your on their development lists - can you tell me when 
they are going to stabilize the API?

A whole chunk of my projects rely on XDoclet and I think it is a fantastic 
tool. However every 2-3 weeks I end up having to completely rewrite some of 
the tasks because the API changes. Is there a published API or anything 
that is stable like that?

It is getting very frustrating - so much so that I just don't bother 
updating the projects using xdoclet which of course causes a whole tree of 
failures in Gump. The instability of XDoclet is also halting a proposal I 
am trying to make in another project.

SO I guess I am asking when will it stop ? ;P

If the answer is not soon. Do you think it would be useful to do a quick 
hack using normal javadoc tool and velocity. Basically small and simple 
doing absolute minimum we need but at least stable? When/if XDoclet 
stabilizes we can revert to it. Beside Velocity is so much more intuitive 
for templating ;)


Cheers,

Peter Donald
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
"Faced with the choice between changing one's mind,
and proving that there is no need to do so - almost
everyone gets busy on the proof."
              - John Kenneth Galbraith
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~


--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>

RE: XDoclet stability was Re: more undocumented attrs

[Peter Donald <pe...@apache.org>]

At 10:06 PM 6/22/2002 +0430, you wrote:
> > As related to this. Your on their development lists - can you tell me
>when
> > they are going to stabilize the API?
>
>The v1.2 API is now considered stable. The transition to xjavadoc is
>done and only some minor internal enhancements will come before 1.2 is
>released.

Kool!

> > SO I guess I am asking when will it stop ? ;P
>
>I say in v2.0. We used to call it v1.3 but now it's called v2.0. What
>you can expect in v2.0:
>- Velocity as the template engine
>- What we call xtags, something which sits on top of xjavadoc and lets
>you model EjbSource/WebJspTag/Whatever as roles of the source class and
>do real OO instead of all those tag handlers.
>- And finally v2.0 will be submitted to Jakarta.

You guys rock! I am soooo looking forward to using velocity for it ;)

>Btw, have you tried the latest cvs code?

As of about 3 weeks ago. Will update again now ;)


Cheers,

Peter Donald
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
"Faced with the choice between changing one's mind,
and proving that there is no need to do so - almost
everyone gets busy on the proof."
              - John Kenneth Galbraith
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~


--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>

RE: XDoclet stability was Re: more undocumented attrs

[Ara Abrahamian <ar...@yahoo.com>]

> > As related to this. Your on their development lists - can you tell
me
> when
> > they are going to stabilize the API?
> 
> I'm just a casual observer at this point, as there was far too much
chaos
> going on with their codebase for me to deal with :)
> 
> I will be back into it after they release their new version.
> 
> Doesn't the CVS version of XDoclet have serious issues with Gump and
> classpaths?

Serious? Not AFAIK. The only thing I've seen mentioned in this list is
that xdoclet modules should only be loaded from taskdef's classpath, not
system classpath. If you follow that rule then you have no problems.
I've seen a message saying Gump is properly setup too.

> Ara - whats the status of this (if its still an issue, that is)?

No. We're fixing docs, fixing bugs and making last polishes.

Ara.


--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>

Re: XDoclet stability was Re: more undocumented attrs

[Erik Hatcher <ja...@ehatchersolutions.com>]

----- Original Message -----
From: "Peter Donald" <pe...@apache.org>

> As related to this. Your on their development lists - can you tell me when
> they are going to stabilize the API?

I'm just a casual observer at this point, as there was far too much chaos
going on with their codebase for me to deal with :)

I will be back into it after they release their new version.

Doesn't the CVS version of XDoclet have serious issues with Gump and
classpaths?

Ara - whats the status of this (if its still an issue, that is)?

    Erik



--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>

RE: XDoclet stability was Re: more undocumented attrs

[Ara Abrahamian <ar...@yahoo.com>]

I'll answer this one....

> As related to this. Your on their development lists - can you tell me
when
> they are going to stabilize the API?

The v1.2 API is now considered stable. The transition to xjavadoc is
done and only some minor internal enhancements will come before 1.2 is
released.

> A whole chunk of my projects rely on XDoclet and I think it is a
fantastic
> tool. However every 2-3 weeks I end up having to completely rewrite
some
> of
> the tasks because the API changes. Is there a published API or
anything
> that is stable like that?

Well, wait till it's stable :-) And it's now stable.

> It is getting very frustrating - so much so that I just don't bother
> updating the projects using xdoclet which of course causes a whole
tree of
> failures in Gump. The instability of XDoclet is also halting a
proposal I
> am trying to make in another project.

I know, I know. Fortunately or unfortunately XDoclet grew exponentially
and suddenly we found ourselves in lots of @tags and templates. XDoclet
started as a quick hack, 20KB only, look what happened to it! We're
moving towards a better architecture. Introducing xjavadoc was the first
step.

> SO I guess I am asking when will it stop ? ;P

I say in v2.0. We used to call it v1.3 but now it's called v2.0. What
you can expect in v2.0:
- Velocity as the template engine
- What we call xtags, something which sits on top of xjavadoc and lets
you model EjbSource/WebJspTag/Whatever as roles of the source class and
do real OO instead of all those tag handlers.
- And finally v2.0 will be submitted to Jakarta.

v1.2 will be out in 2 weeks. Stick to it until v2.0 is out. v2.0 will
have a totally new architecture, but until then the 1.x series are more
or less stable and you can expect only small changes. We had to fix some
stupid problems, for example javadoc isn't following javabean spec,
xjavadoc does and that alone meant a big refactoring!

> If the answer is not soon. Do you think it would be useful to do a
quick
> hack using normal javadoc tool and velocity. Basically small and
simple
> doing absolute minimum we need but at least stable? When/if XDoclet
> stabilizes we can revert to it. Beside Velocity is so much more
intuitive
> for templating ;)

Yeah Velocity is great and we're switching to it.

Btw, have you tried the latest cvs code?

Cheers,
Ara.


--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>