Thread: [Hibernate] XDoclet Hibernate subtasks

SourceForge Headquarters 225 Broadway Suite 1600 San Diego, CA 92101 +1 (858) 422-6466

Hello,

  Someone is working on a XDoclet subtask to hibernate ?

-- 
Best regards,
 Danilo                          mailto:da...@fl...

It already exists in CVS (The "Tools" module). This was written by Sebastien
Guimont but is currently kinda ownerless....

Its probably *not* working against the latest release of XDoclet though. I
would very much appreciate if someone would get it working against their
latest release.

----- Original Message -----
From: "Danilo Luiz Rheinheimer" <da...@fl...>
To: <hib...@li...>
Sent: Friday, November 08, 2002 12:04 PM
Subject: [Hibernate] XDoclet Hibernate subtasks

> Hello,
>
>   Someone is working on a XDoclet subtask to hibernate ?
>
> --
> Best regards,
>  Danilo                          mailto:da...@fl...
>
>
>
>
> -------------------------------------------------------
> This sf.net email is sponsored by: See the NEW Palm
> Tungsten T handheld. Power & Color in a compact size!
> http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0001en
> _______________________________________________
> hibernate-devel mailing list
> hib...@li...
> https://lists.sourceforge.net/lists/listinfo/hibernate-devel

I actually gave it a whirl against the latest XDoclet release (1.2.0 
beta 1 ) and it generates the mapping file no worries. From my initial 
glance it looked fine as well. I also tried it against a build from 
latest CVS. It was also fine, although it did generate some warning 
messages. I'll actually try the mapping file out though. Was there any 
known specific issues?

I remember that you (Gavin) mentioned that the Xdoclet team would take 
over the Hibernate task. Is that going to happen? I see some project 
branching going on there towards some Jakarta templates too.

Hmmmm any thoughts?

Gavin King wrote:

>It already exists in CVS (The "Tools" module). This was written by Sebastien
>Guimont but is currently kinda ownerless....
>
>Its probably *not* working against the latest release of XDoclet though. I
>would very much appreciate if someone would get it working against their
>latest release.
>
>----- Original Message -----
>From: "Danilo Luiz Rheinheimer" <da...@fl...>
>To: <hib...@li...>
>Sent: Friday, November 08, 2002 12:04 PM
>Subject: [Hibernate] XDoclet Hibernate subtasks
>
>
>  
>
>>Hello,
>>
>>  Someone is working on a XDoclet subtask to hibernate ?
>>
>>--
>>Best regards,
>> Danilo                          mailto:da...@fl...
>>
>>
>>
>>
>>-------------------------------------------------------
>>This sf.net email is sponsored by: See the NEW Palm
>>Tungsten T handheld. Power & Color in a compact size!
>>http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0001en
>>_______________________________________________
>>hibernate-devel mailing list
>>hib...@li...
>>https://lists.sourceforge.net/lists/listinfo/hibernate-devel
>>    
>>
>
>
>
>-------------------------------------------------------
>This sf.net email is sponsored by: See the NEW Palm 
>Tungsten T handheld. Power & Color in a compact size!
>http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0001en
>_______________________________________________
>hibernate-devel mailing list
>hib...@li...
>https://lists.sourceforge.net/lists/listinfo/hibernate-devel
>
>  
>

Hi Daniel, how's everyone :-)

> I actually gave it a whirl against the latest XDoclet release (1.2.0
> beta 1 ) and it generates the mapping file no worries.

Oh does it? Cool ... it was broken against a CVS snapshot I tried but
perhaps that was just a broken snapshot.....

> From my initial
> glance it looked fine as well. I also tried it against a build from
> latest CVS. It was also fine, although it did generate some warning
> messages. I'll actually try the mapping file out though. Was there any
> known specific issues?

The mapping document was specifically not generated ;)

Another issue is that the module should be updated to reflect our latest DTD
(hibernate-mapping-1.1.dtd) which is not a big job, I'm certain.

> I remember that you (Gavin) mentioned that the Xdoclet team would take
> over the Hibernate task. Is that going to happen? I see some project
> branching going on there towards some Jakarta templates too.

Ara will accept the Hibernate module into their codebase but we would need
to maintain it ourselves with *no* CVS access (at least initially). I would
much prefer it to live in their CVS repository but I am unwilling to
maintain the code myself using patches. I am very keen for this code to find
itself an "owner" since I have enough on my plate with the persistence
engine. The rest of our toolset was created and is being mainly maintained
by other people and I would like to see the same happen here.

Gavin

> > I remember that you (Gavin) mentioned that the Xdoclet team would
take
> > over the Hibernate task. Is that going to happen? I see some project
> > branching going on there towards some Jakarta templates too.
> 
> Ara will accept the Hibernate module into their codebase but we would
need
> to maintain it ourselves with *no* CVS access (at least initially). I
> would
> much prefer it to live in their CVS repository but I am unwilling to
> maintain the code myself using patches. I am very keen for this code
to
> find
> itself an "owner" since I have enough on my plate with the persistence
> engine. The rest of our toolset was created and is being mainly
maintained
> by other people and I would like to see the same happen here.

Ara is himself here to help :-)

I'm involved in a project that probably (90%) will use Hibernate. So
I'll have to use it myself and be sure I can't resist contributing to
open source projects :-) So wherever the module ends up in I'll
contribute. I think it's better for it to live in hibernate's cvs.

Btw, as described previously in xdoclet-devel we'll probably set up a
smart distributed module build system using Maven in xdoclet2. So you'll
host the module in hibernate's cvs, but we'll checkout it, build it and
bundle it and even test it. This way we'll be able to keep an eye on
what's going on in remotely hosted modules and still keep it separated.

Ara.

> Ara is himself here to help :-)

Excellent!

> I'm involved in a project that probably (90%) will use Hibernate. So
> I'll have to use it myself and be sure I can't resist contributing to
> open source projects :-) So wherever the module ends up in I'll
> contribute. I think it's better for it to live in hibernate's cvs.

Even excellenter :)

> Btw, as described previously in xdoclet-devel we'll probably set up a
> smart distributed module build system using Maven in xdoclet2. So you'll
> host the module in hibernate's cvs, but we'll checkout it, build it and
> bundle it and even test it. This way we'll be able to keep an eye on
> what's going on in remotely hosted modules and still keep it separated.

Great, sounds like a solution that keeps everyone happy. (PS. I'm very 
impressed with the whole "Maven distributed module build system".)

peace

Gavin

Thread: [Hibernate] XDoclet Hibernate subtasks

An object relational-mapping (ORM) library for Java

hibernate-devel