Re: Subprojects...

[James Carman]

I had no intention of having dependencies on Tapestry.  My stuff is split out so that there's just Hibernate specific stuff in one module and then I built Tapernate on top of that (notice that there's a hivemind-hibernate3 module and tapernate depends on that).  I agree that we shouldn't depend on Tapestry in the HiveMind modules subproject (I suggested the other day to Knut via IM that we could call the subproject "The Collective").

On 10/26/06, Jean-Francois Poilpret <[EMAIL PROTECTED]> wrote:

Hi,

A long time ago, I remember a discussion on this list notifying Hibernate
integration into HiveMind could not be added to the Apache source code base
due to licensing reasons, has something changed since then?

For my point (but I am biased), what I would like to avoid in HiveMind
subprojects is a dependency on Tapestry (I use HiveMind but not Tapestry),
such subprojects would be better hosted under the Tapestry umbrella.

Besides, I think it would be a good idea sicne currently, any developer
wishing to use HiveMind has to do some research to see what integration
facilities are available or not.

Cheers

Jean-Francois

-----Original Message-----
From: Achim Hügen [mailto:[EMAIL PROTECTED]]
Sent: Friday, October 27, 2006 4:14 AM
To: dev@hivemind.apache.org
Subject: Re: Subprojects...

Yes, why not.
We should restructure the svn repository then
to separate the main project and the subprojects.

Achim

Am Mon, 23 Oct 2006 15:28:40 +0200 schrieb James Carman
<[EMAIL PROTECTED]>:

> All,
>
> Should we create a subproject of HiveMind now to contain reusable modules
> like the ones that I've been creating over at JavaForge?  I've got
> libraries
> for stuff like Acegi, Hibernate, etc.
>
> James







___________________________________________________________________________
Découvrez une nouvelle façon d'obtenir des réponses à toutes vos questions !
Profitez des connaissances, des opinions et des expériences des internautes sur Yahoo! Questions/Réponses
http://fr.answers.yahoo.com