> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Ara
> Abrahamian
> Sent: 21. mars 2002 20:53
> To: [EMAIL PROTECTED]
> Subject: RE: [Xdoclet-devel] refactoring branch
>
>
> > I am not sure samples can even deploy on any ejb server.
> > Dmitri posted a message sometimes ago it was not deploying on Jboss.
> > So a bad result does not mean ...
>
> Bad bad. Dim, what the problems are? We should definitely try to fix
> samples and make them deployable. I know we were lazy to actually deploy
> the samples but.... My ideal is to see an ear file which deploys on all
> app servers ;-)
>

Let's all pull in that direction now. It's critical for xdoclet's success.
I'll do the WLS testing.
We should ensure the quality of what's already in before we add new
functionality. For example: value objects are very nice,
but IMHO deploying simple stuff on JBoss is far more important. There is too
much partially-working stuff now. Check the buglist!

> > > I'm actually quite surprised it has gone so well. I was
> > > scared shitless when I started to refactor. Kept telling
> > > myself: "You're gonna fuck it all up, and xjavadoc will never
> > > work". Now I'm very confident it'll be great!
>
> It certainly shows the quality of your work, Aslak :-)
>

Thanks! It's the funniest thing I ever coded. -And thanks for all the help
and tips on the way. Very helpful indeed.

> > It IS fabulous.  After Rickard invent ejbdoclet and Ara turned it in a
> > global generation tool, this is really the 3 tremendous step.
>
> Ah, life passes so fast, it was about a year ago....
>
> > It is also worth to mention it is as, if not more, easy to use than
> > javadoc from a "user" point of view.
> > The interface is clear, I even did not have to look the code to
> > understand.
> > Really a piece of cake.
> > That is also good news for the adoption of it by the developers.
>
> Btw, I think we should do a search/replace and replace all those
> classes()/methods()/etc with javabean-compatible getClasses()/etc
> methods. It's a piece of cake with IDEA :-)
>

Agree. To those who might not know: I kept the method names like that in
order to resemble javadoc more. Now that everything is cool, lets follow
JavaBeans coding standard.

> > > There are still some optimisations to be done, but as long as
> > > output is ok, we can do opts on main.
>
> Agree. I'm ill in bed currently :-( but I'll spend some time on the
> timestamp issue tomorrow.
>

Get well soon! I'm not sure what you mean by timestamp issue. -But I know
one thing: If xdoclet.jar is regenerated, xdoclet doesn't regenerate sources
as it used to do. We (you) should check xjavadoc.jar age too.

> > Do you think a good idea to push a alpha or beta version out in SF.
> > I mean once you try it you do not want to go back anymore even if bugs
> > will appear.
>
> Agree. We haven't tested specially the parser on many different source
> codes. Maybe a 1.2 beta for next weekend?
>

Isn't this a 2.0 alpha rather? When things start to stabilise, I'll spend
more time on Middlegen, XDoclet GUI and maybe even pick up the Reverse
XDoclet. I'll spend and less time on XDoclet.

> Cheers,
> Ara.
>
>
> _________________________________________________________
> Do You Yahoo!?
> Get your free @yahoo.com address at http://mail.yahoo.com
>
>
> _______________________________________________
> Xdoclet-devel mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/xdoclet-devel


_______________________________________________
Xdoclet-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/xdoclet-devel

Reply via email to