I definitely prefer to generate the files into a separate directory hierarchy
(generated or gen) for a couple reasons.
1. Habit of organizing different types of files into directories.
classes, src, conf, meta, db, etc.
True, the generated sources *are* Java source files, but they're different because
they are machine generated.
2. Makes your "clean" target simple:
<delete dir="${gen.dir}" quiet="true"/>
3. Reduces likelihood that someone will accidentally check them into the repository.
In my view, nothing that is not an original source file should ever be put into source
control as this just invites things getting out of sync. Unfortunately, my current
company already had been "releasing" JARs into Perforce before I arrived, and it's a
fairly common occurrence that deployment issues arise because of this. Given that
doing a full build doesn't take more than two minutes, I don't see the big win with
doing this -- especially since this is a constant source of headaches. That's not my
call, however, yet. :)
That's my story and I'm sticking to it!
David Harkness
Sony Pictures Digital Networks
(310) 482-4756
-----Original Message-----
From: Justin Akehurst [mailto:[EMAIL PROTECTED]
Sent: Tuesday, July 08, 2003 4:39 PM
To: [EMAIL PROTECTED]
Subject: Re: [Xdoclet-user] XJavaDoc warnings
On Wed, 9 Jul 2003, Aslak Helles�y wrote:
> Justin Akehurst wrote:
>
> >When we run ant against our code, XDoclet is giving us this warning:
> >
> >[ejbdoclet] (xjavadoc.XJavaDoc 889 ) Ignoring class
> >com.versaly.ejb.session.PhoneServices in
> >/home/akehurst/workspace/Versaly_PocketNet/WEB-INF/classes/com/versal
> >y/ejb/session/PhoneServices.java.
> >It was generated (Tue Jul 08 15:28:36 PDT 2003) after XJavaDoc's timestamp
> >was reset (Tue Jul 08 06:33:08 PDT 2003)
> >
> >
> This happens when XJavaDoc finds a source file whose timestamp is
> fresher than the time XJavaDoc was started. I.e. generated after
> XJavaDoc was started. XjavaDoc ignores such sources to avoid predictable
> behaviour.
>
> This happens when:
> a) You're telling XDoclet to generate sources into the same place
> where
> your @tagged sources are. (Don't do that!)
> b) Some of your files have an incorrect (future) timestamp because some
> computer clock got messed up.
>
> Looking at the timestamps, it smells like b) to me.
It might be a).
We have our entity bean classes in com/versaly/ejb/entity/*Bean.java and our session
beans in com/versaly/ejb/session/*Services.java
We are having XDoclet create the Local and LocalHome classes in the same directory
that the @tagged files are in (com/versaly/ejb/entity and com/versaly/ejb/session).
What is commonly done in this case?
-Justin
-------------------------------------------------------
This SF.Net email sponsored by: Parasoft
Error proof Web apps, automate testing & more.
Download & eval WebKing and get a free book. www.parasoft.com/bulletproofapps
_______________________________________________
xdoclet-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/xdoclet-user
-------------------------------------------------------
This SF.Net email sponsored by: Parasoft
Error proof Web apps, automate testing & more.
Download & eval WebKing and get a free book.
www.parasoft.com/bulletproofapps
_______________________________________________
xdoclet-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/xdoclet-user
