Notice of intent that I'm going to ask the infra team to close up the
dev list for HiveMind, while keeping the user list open.

Hen

On Fri, Apr 17, 2009 at 1:55 PM, Raffael Herzog <herzog@raffael.ch> wrote:


> However, the question remains: Are there people who would actually
> contribute?
>
> What do you think?

I won't contribute directly to it but it's sure i will do a
chenillekit module (http://tapestry.formos.com/nightly/chenille-kit/)
for the new project to bridge it to T5 IoC.
So after all a very nice idea.

-- 
Massimo
http://meridio.blogspot.com

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi Raffael,

I am all for this idea - not very familiar with OPS4J, but their
intentions sounds good.  Definitely would allow more contributions to
trickle in.

So, count me in.

Cheers,

Johan

Raffael Herzog wrote:
> Hi all
> 
> So, now it's official: HiveMind's development at Apache has stopped. Time to 
> move on and start over. ;)
> 
> For me, one thing is clear: I will branch HiveMind, one way or the other. 
> The question for me is: Which way?
> 
> As some of you may know, I'm developing and using HiveApp, an extension to 
> HiveMind which adds a VFS, ClassLoader management, built-in JMX support and 
> some useful services. There are many applications based on it in production 
> (and there will be many more) and its development continues, although it's 
> currently a one-man-show (everything's open though, and anyone is free to 
> join: http://hiveapp.raffael.ch/).
> 
> So, from this point of view, the obvious thing to do is to take HiveMind's 
> source code, integrate it into HiveApp's source tree, and just continue 
> like that.
> 
> However, now's the time to look further. ;) HiveMind, as it is now, is good, 
> but it's gotten a bit outdated, and development as officially stalled. I've 
> got many ideas what to do with HiveMind (you can find some of them in 
> HiveApp) and I'm sure, there are more people with ideas. This is the time 
> to progressively move forward, because there won't be any HiveMind 1.2 or 
> 2.0 anymore. But there may be a HiveSomethingElse 0.1.
> 
> The question is: If you had commit rights for HiveMind's source code 
> tomorrow, would you start contributing?
> 
> The idea is to branch HiveMind at OPS4J (http://www.ops4j.org/). OPS4J 
> stands for "Open Participation Software for Java", a relatively young and 
> active FOSS community. "Open Participation" means basically Wiki brought to 
> coding. Anyone can start contributing: Just register yourself, and you've 
> immediately got commit access to all of OPS4J's SVN. At OPS4J, if you find 
> a bug, you don't submit a patch which fixes it and wait for a committer to 
> apply your patch. At OPS4J, you commit the fix yourself. OPS4J provides all 
> the infrastructure one needs: Version control (SVN), bug tracking (JIRA), 
> Wiki (Confluence), CI (Bamboo), mailing lists, web space ...
> 
> Introduction to OPS4J: http://wiki.ops4j.org/display/ops4j/Introduction
> 
> I think, this community might be just the right thing to kickstart 
> HiveMind's development. I've already talked to some people at OPS4J about 
> it, they'd happily welcome the HiveMind community.
> 
> However, the question remains: Are there people who would actually 
> contribute?
> 
> What do you think?
> 
> Cheers,
>    Raffi
> 

- --
you too?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFJ6Ha7pHYnED7evioRAiDdAJ9pgRQ+B3B1bxHDaUqI0hNDhmF3RgCePRWH
Nx3ymRS0a/AkAsvdBTPlIp8=
=cV41
-----END PGP SIGNATURE-----

Hi all

So, now it's official: HiveMind's development at Apache has stopped. Time to 
move on and start over. ;)

For me, one thing is clear: I will branch HiveMind, one way or the other. 
The question for me is: Which way?

As some of you may know, I'm developing and using HiveApp, an extension to 
HiveMind which adds a VFS, ClassLoader management, built-in JMX support and 
some useful services. There are many applications based on it in production 
(and there will be many more) and its development continues, although it's 
currently a one-man-show (everything's open though, and anyone is free to 
join: http://hiveapp.raffael.ch/).

So, from this point of view, the obvious thing to do is to take HiveMind's 
source code, integrate it into HiveApp's source tree, and just continue 
like that.

However, now's the time to look further. ;) HiveMind, as it is now, is good, 
but it's gotten a bit outdated, and development as officially stalled. I've 
got many ideas what to do with HiveMind (you can find some of them in 
HiveApp) and I'm sure, there are more people with ideas. This is the time 
to progressively move forward, because there won't be any HiveMind 1.2 or 
2.0 anymore. But there may be a HiveSomethingElse 0.1.

The question is: If you had commit rights for HiveMind's source code 
tomorrow, would you start contributing?

The idea is to branch HiveMind at OPS4J (http://www.ops4j.org/). OPS4J 
stands for "Open Participation Software for Java", a relatively young and 
active FOSS community. "Open Participation" means basically Wiki brought to 
coding. Anyone can start contributing: Just register yourself, and you've 
immediately got commit access to all of OPS4J's SVN. At OPS4J, if you find 
a bug, you don't submit a patch which fixes it and wait for a committer to 
apply your patch. At OPS4J, you commit the fix yourself. OPS4J provides all 
the infrastructure one needs: Version control (SVN), bug tracking (JIRA), 
Wiki (Confluence), CI (Bamboo), mailing lists, web space ...

Introduction to OPS4J: http://wiki.ops4j.org/display/ops4j/Introduction

I think, this community might be just the right thing to kickstart 
HiveMind's development. I've already talked to some people at OPS4J about 
it, they'd happily welcome the HiveMind community.

However, the question remains: Are there people who would actually 
contribute?

What do you think?

Cheers,
   Raffi

-- 
The difference between theory and practice is that in theory, there is
no difference, but in practice, there is.

herzog@raffael.ch · Jabber: herzog@raffael.ch
PGP Key 0x5FFDB5DB5D1FF5F4 · http://keyserver.pgp.com

Nothing that I know of (beyond the usual suspects in the IoC world).

That's a very good point though and something for the Attic to
document if any of the HiveMind community identify an obvious
candidate.

On Thu, Apr 16, 2009 at 7:33 AM, Kevin Gilpin <kevin.gilpin@praxeon.com> wrote:
> Is there a recommendation to switch to an alternative framework?
>
> On Wed, Apr 15, 2009 at 11:20 PM, Henri Yandell <flamefew@gmail.com> wrote:
>>
>> A heads up for the HiveMind user community that the HiveMind project
>> has been 'moved to the Attic'. This means that the HiveMind developers
>> (more formally its Project Management Committee) have voted to retire
>> HiveMind and move the responsibility for its oversight over to the
>> Attic project.
>>
>> You can read more about the Apache Attic at http://attic.apache.org.
>>
>> HiveMind is the first project to move into the Attic, so the process
>> will be identified as we go along. You can follow this at
>> https://issues.apache.org/jira/browse/ATTIC-1 if you so wish.
>>
>> Thanks,
>>
>> Henri Yandell
>> on behalf of HiveMind + the Attic.
>
>
>
> --
> CTO
> Praxeon Inc
> kevin.gilpin@praxeon.com
>

Is there a recommendation to switch to an alternative framework?

On Wed, Apr 15, 2009 at 11:20 PM, Henri Yandell <flamefew@gmail.com> wrote:

> A heads up for the HiveMind user community that the HiveMind project
> has been 'moved to the Attic'. This means that the HiveMind developers
> (more formally its Project Management Committee) have voted to retire
> HiveMind and move the responsibility for its oversight over to the
> Attic project.
>
> You can read more about the Apache Attic at http://attic.apache.org.
>
> HiveMind is the first project to move into the Attic, so the process
> will be identified as we go along. You can follow this at
> https://issues.apache.org/jira/browse/ATTIC-1 if you so wish.
>
> Thanks,
>
> Henri Yandell
> on behalf of HiveMind + the Attic.
>



-- 
CTO
Praxeon Inc
kevin.gilpin@praxeon.com

On Thu, Apr 16, 2009 at 5:20 AM, Henri Yandell <flamefew@gmail.com> wrote:

> HiveMind is the first project to move into the Attic, so the process
> will be identified as we go along. You can follow this at
> https://issues.apache.org/jira/browse/ATTIC-1 if you so wish.

It's somehow sad and nice at the same time for HiveMind to be the
first one to be moved into the Attic.

HiveMind has been a nice project to work with plus it has settled the
base for future concepts in IoC containers.

Thanks to all developers

Cheers
-- 
Massimo
http://meridio.blogspot.com

A heads up for the HiveMind user community that the HiveMind project
has been 'moved to the Attic'. This means that the HiveMind developers
(more formally its Project Management Committee) have voted to retire
HiveMind and move the responsibility for its oversight over to the
Attic project.

You can read more about the Apache Attic at http://attic.apache.org.

HiveMind is the first project to move into the Attic, so the process
will be identified as we go along. You can follow this at
https://issues.apache.org/jira/browse/ATTIC-1 if you so wish.

Thanks,

Henri Yandell
on behalf of HiveMind + the Attic.

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi Henry,

So while the Attic group picks the project up, would you actively be
looking for a group to pick it up, or does a group have to 'announce'
itself to be considered?

Also, for practical things such as patches etc supplied, would these be
available after a closure?

Cheers,

Johan

Henri Yandell wrote:
> It's a direct reaction to the effort.
> 
> Users are trying to put together the release. There is no one in the
> project committers to support them. Therefore the project needs to be
> moved to the Attic which will have clear instructions and support for
> others to fork the project with Apache's blessing. Ideally it's not a
> fork but rather a closing down at Apache and a starting up elsewhere
> with a new group.
> 
> So now that the HiveMind committers have voted for that, the Attic
> group will be able to use it as a first use case to put together those
> instructions/blessing/steps.
> 
> Hope that helps - this is specifically to try to help the situation
> where a project has an active user base but no developer base, as with
> HiveMind.
> 
> Hen
> 
> On Thu, Mar 5, 2009 at 1:29 AM, Jochen Zimmermann <zet4080@gmx.de> wrote:
>> I don't get it ... could some one explain this decision?
>> There were some discussions on this list about HiveMind.
>> There was even the effort to do a maintenance release.
>> I grant you that there was not much reaction to it, but at least the HiveMind PMC
should have reacted in some way ... no one cared to answer to even direct questions about
help on this topic ...
>>
>> If you planned this anyway for some reasons you could have explained this in the
past instead of encourage further work and then simply stop answering questions ... that's
sort of weird, I think :-(
>>
>> Cheers,
>> Jochen
>>
>>
>>
>>
>> -------- Original-Nachricht --------
>>> Datum: Thu, 5 Mar 2009 09:31:38 +0100
>>> Von: Massimo Lusetti <mlusetti@gmail.com>
>>> An: dev@hivemind.apache.org
>>> Betreff: Re: [DRAFT] HiveMind Board Report - March 2009
>> - Show quoted text -
>>> On Wed, Mar 4, 2009 at 10:26 PM, James Carman
>>> <james@carmanconsulting.com> wrote:
>>>
>>>> Here's what I have:
>>>>
>>>> The HiveMind PMC has voted to move HiveMind into the "Attic."  Henri
>>>> Yandell has graciously offered to take care of presenting HiveMind to
>>>> the Attic PMC and the board for inclusion in the Attic.
>>>>
>>>> James Carman
>>> It has been a good library/framework to work with and served as a
>>> launch pad for next generation IoC but this seems the right decision.
>>>
>>> Thanks to all HiveMind developers!
>>>
>>> Regards
>>> --
>>> Massimo
>>> http://meridio.blogspot.com
> 
> 

- --
you too?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFJsOL6pHYnED7evioRAqcxAJ0d53cNE6Ewb8L3SVu8k/xwEHuVqgCeJxX6
dymNdQOuCR47lVnXjpEHWfo=
=VcXr
-----END PGP SIGNATURE-----

Thanks for that explanation - it makes the intention clear now :-)

-------- Original-Nachricht --------
> Datum: Thu, 5 Mar 2009 19:26:13 -0800
> Von: Henri Yandell <flamefew@gmail.com>
> An: dev@hivemind.apache.org
> Betreff: Re: [DRAFT] HiveMind Board Report - March 2009

> It's a direct reaction to the effort.
> 
> Users are trying to put together the release. There is no one in the
> project committers to support them. Therefore the project needs to be
> moved to the Attic which will have clear instructions and support for
> others to fork the project with Apache's blessing. Ideally it's not a
> fork but rather a closing down at Apache and a starting up elsewhere
> with a new group.
> 
> So now that the HiveMind committers have voted for that, the Attic
> group will be able to use it as a first use case to put together those
> instructions/blessing/steps.
> 
> Hope that helps - this is specifically to try to help the situation
> where a project has an active user base but no developer base, as with
> HiveMind.
> 
> Hen
> 
> On Thu, Mar 5, 2009 at 1:29 AM, Jochen Zimmermann <zet4080@gmx.de> wrote:
> > I don't get it ... could some one explain this decision?
> > There were some discussions on this list about HiveMind.
> > There was even the effort to do a maintenance release.
> > I grant you that there was not much reaction to it, but at least the
> HiveMind PMC should have reacted in some way ... no one cared to answer to
> even direct questions about help on this topic ...
> >
> > If you planned this anyway for some reasons you could have explained
> this in the past instead of encourage further work and then simply stop
> answering questions ... that's sort of weird, I think :-(
> >
> > Cheers,
> > Jochen
> >
> >
> >
> >
> > -------- Original-Nachricht --------
> >> Datum: Thu, 5 Mar 2009 09:31:38 +0100
> >> Von: Massimo Lusetti <mlusetti@gmail.com>
> >> An: dev@hivemind.apache.org
> >> Betreff: Re: [DRAFT] HiveMind Board Report - March 2009
> > - Show quoted text -
> >> On Wed, Mar 4, 2009 at 10:26 PM, James Carman
> >> <james@carmanconsulting.com> wrote:
> >>
> >> > Here's what I have:
> >> >
> >> > The HiveMind PMC has voted to move HiveMind into the "Attic."  Henri
> >> > Yandell has graciously offered to take care of presenting HiveMind to
> >> > the Attic PMC and the board for inclusion in the Attic.
> >> >
> >> > James Carman
> >>
> >> It has been a good library/framework to work with and served as a
> >> launch pad for next generation IoC but this seems the right decision.
> >>
> >> Thanks to all HiveMind developers!
> >>
> >> Regards
> >> --
> >> Massimo
> >> http://meridio.blogspot.com
> >

It's a direct reaction to the effort.

Users are trying to put together the release. There is no one in the
project committers to support them. Therefore the project needs to be
moved to the Attic which will have clear instructions and support for
others to fork the project with Apache's blessing. Ideally it's not a
fork but rather a closing down at Apache and a starting up elsewhere
with a new group.

So now that the HiveMind committers have voted for that, the Attic
group will be able to use it as a first use case to put together those
instructions/blessing/steps.

Hope that helps - this is specifically to try to help the situation
where a project has an active user base but no developer base, as with
HiveMind.

Hen

On Thu, Mar 5, 2009 at 1:29 AM, Jochen Zimmermann <zet4080@gmx.de> wrote:
> I don't get it ... could some one explain this decision?
> There were some discussions on this list about HiveMind.
> There was even the effort to do a maintenance release.
> I grant you that there was not much reaction to it, but at least the HiveMind PMC should
have reacted in some way ... no one cared to answer to even direct questions about help on
this topic ...
>
> If you planned this anyway for some reasons you could have explained this in the past
instead of encourage further work and then simply stop answering questions ... that's sort
of weird, I think :-(
>
> Cheers,
> Jochen
>
>
>
>
> -------- Original-Nachricht --------
>> Datum: Thu, 5 Mar 2009 09:31:38 +0100
>> Von: Massimo Lusetti <mlusetti@gmail.com>
>> An: dev@hivemind.apache.org
>> Betreff: Re: [DRAFT] HiveMind Board Report - March 2009
> - Show quoted text -
>> On Wed, Mar 4, 2009 at 10:26 PM, James Carman
>> <james@carmanconsulting.com> wrote:
>>
>> > Here's what I have:
>> >
>> > The HiveMind PMC has voted to move HiveMind into the "Attic."  Henri
>> > Yandell has graciously offered to take care of presenting HiveMind to
>> > the Attic PMC and the board for inclusion in the Attic.
>> >
>> > James Carman
>>
>> It has been a good library/framework to work with and served as a
>> launch pad for next generation IoC but this seems the right decision.
>>
>> Thanks to all HiveMind developers!
>>
>> Regards
>> --
>> Massimo
>> http://meridio.blogspot.com
>

Am Mittwoch, 4. März 2009 22.26:27 schrieb James Carman:
> Here's what I have:
>
> The HiveMind PMC has voted to move HiveMind into the "Attic."  Henri
> Yandell has graciously offered to take care of presenting HiveMind to
> the Attic PMC and the board for inclusion in the Attic.
>
> James Carman

That's a pity ... but no surprise, it was only a question of time ... :(

To explain myself, as I am one who at least talked about contributing to 
HiveMind, but never did:

What I am using and developing is an extension to HiveMind, a thing, that 
would always be a separate project. HiveApp, is I uninspiredly call it, is 
in production about 20 times, and that number is growing and will continue 
to grow.

I needed some things to be done differently, but those were things that the 
majority of "plain HiveMind" users wouldn't care about. This fact makes it 
very difficult for me to start contributing to HiveMind itself, because I'm 
often looking at things from a different perspective. Where some people 
wanted new features, my focus would rather be to open HiveMind to provide 
hooks at implementation-level, where I and possibly other people working at 
low-level could hook into and extend HiveMind.

As an example: HiveMind is largely designed to run within a web application 
server. The way I'm using it, I reverse things: Jetty is running within the 
HiveMind container. Therefore, it's very difficult for me to contribute "my 
things", as most people don't use HiveMind like that.

In the end, HiveMind is a great piece of code that "just works". One might 
actually consider to release HiveMind 3.1416 ... ;)

Cheers,
   Raffi

-- 
The difference between theory and practice is that in theory, there is
no difference, but in practice, there is.

herzog@raffael.ch · Jabber: herzog@raffael.ch
PGP Key 0x5FFDB5DB5D1FF5F4 · http://keyserver.pgp.com

I don't get it ... could some one explain this decision?
There were some discussions on this list about HiveMind.
There was even the effort to do a maintenance release. 
I grant you that there was not much reaction to it, but at least the HiveMind PMC should have
reacted in some way ... no one cared to answer to even direct questions about help on this
topic ... 

If you planned this anyway for some reasons you could have explained this in the past instead
of encourage further work and then simply stop answering questions ... that's sort of weird,
I think :-(

Cheers, 
Jochen




-------- Original-Nachricht --------
> Datum: Thu, 5 Mar 2009 09:31:38 +0100
> Von: Massimo Lusetti <mlusetti@gmail.com>
> An: dev@hivemind.apache.org
> Betreff: Re: [DRAFT] HiveMind Board Report - March 2009

> On Wed, Mar 4, 2009 at 10:26 PM, James Carman
> <james@carmanconsulting.com> wrote:
> 
> > Here's what I have:
> >
> > The HiveMind PMC has voted to move HiveMind into the "Attic."  Henri
> > Yandell has graciously offered to take care of presenting HiveMind to
> > the Attic PMC and the board for inclusion in the Attic.
> >
> > James Carman
> 
> It has been a good library/framework to work with and served as a
> launch pad for next generation IoC but this seems the right decision.
> 
> Thanks to all HiveMind developers!
> 
> Regards
> -- 
> Massimo
> http://meridio.blogspot.com

On Wed, Mar 4, 2009 at 10:26 PM, James Carman
<james@carmanconsulting.com> wrote:

> Here's what I have:
>
> The HiveMind PMC has voted to move HiveMind into the "Attic."  Henri
> Yandell has graciously offered to take care of presenting HiveMind to
> the Attic PMC and the board for inclusion in the Attic.
>
> James Carman

It has been a good library/framework to work with and served as a
launch pad for next generation IoC but this seems the right decision.

Thanks to all HiveMind developers!

Regards
-- 
Massimo
http://meridio.blogspot.com

Here's what I have:

The HiveMind PMC has voted to move HiveMind into the "Attic."  Henri
Yandell has graciously offered to take care of presenting HiveMind to
the Attic PMC and the board for inclusion in the Attic.

James Carman

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Btw, would be nice to know who is still on 1.3 - and indeed if anyone on
the list is, be worth knowing your thoughts.

Also, how many versions backward compatibility is desired?  A bit broad
of a question, but interesting to know.

Cheers,

Johan

Johan Lindquist wrote:
> +1 for reducing dependencies further - however, must tread carefully to
> preserve the users we have - so a +1 for 1.3 too ...  :)
> 
> Cheers,
> 
> Johan
> 
> Raffael Herzog wrote:
>> Am Dienstag, 6. Januar 2009 11.01:42 schrieb Johan Lindquist:
>>> After the discussions on the list, I decided to add the suggested
>>> road-map page to the WIKI
>>>
>>> http://cwiki.apache.org/HIVEMIND2/hivemind-v1.html
>>>
>>> It includes the suggestions from the list.
>> There's another thing that came to my mind: What about replacing jakarta-oro 
>> with java.util.regex? On the pro-side, this would further minimise the 
>> dependencies of HiveMind. On the con-side, this would mean to drop support 
>> for JDK 1.3 (therefore, it might be better to consider that for HiveMind 
>> 1.3, instead of 1.2).
> 
>> Thoughts/opinions?
> 
>> Cheers,
>>    Raffi
> 
> 

- --
you too?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFJfd74pHYnED7evioRAj2lAJ44Xz8SaheM3L95Ud3OqPtyzvo4iACeOlS6
kqeS7sp0nORf0mxWu8bJUPA=
=YUpC
-----END PGP SIGNATURE-----

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

+1 for reducing dependencies further - however, must tread carefully to
preserve the users we have - so a +1 for 1.3 too ...  :)

Cheers,

Johan

Raffael Herzog wrote:
> Am Dienstag, 6. Januar 2009 11.01:42 schrieb Johan Lindquist:
>> After the discussions on the list, I decided to add the suggested
>> road-map page to the WIKI
>>
>> http://cwiki.apache.org/HIVEMIND2/hivemind-v1.html
>>
>> It includes the suggestions from the list.
> 
> There's another thing that came to my mind: What about replacing jakarta-oro 
> with java.util.regex? On the pro-side, this would further minimise the 
> dependencies of HiveMind. On the con-side, this would mean to drop support 
> for JDK 1.3 (therefore, it might be better to consider that for HiveMind 
> 1.3, instead of 1.2).
> 
> Thoughts/opinions?
> 
> Cheers,
>    Raffi
> 

- --
you too?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFJfdnApHYnED7evioRAjMsAJ9dgTk7dAtuXK1rvIPXPskIxQzSwQCgrCEO
O5QtEysbjhZTOHK/ErJ7i2A=
=Vlzi
-----END PGP SIGNATURE-----

Am Dienstag, 6. Januar 2009 11.01:42 schrieb Johan Lindquist:
> After the discussions on the list, I decided to add the suggested
> road-map page to the WIKI
>
> http://cwiki.apache.org/HIVEMIND2/hivemind-v1.html
>
> It includes the suggestions from the list.

There's another thing that came to my mind: What about replacing jakarta-oro 
with java.util.regex? On the pro-side, this would further minimise the 
dependencies of HiveMind. On the con-side, this would mean to drop support 
for JDK 1.3 (therefore, it might be better to consider that for HiveMind 
1.3, instead of 1.2).

Thoughts/opinions?

Cheers,
   Raffi

-- 
The difference between theory and practice is that in theory, there is
no difference, but in practice, there is.

herzog@raffael.ch · Jabber: herzog@raffael.ch
PGP Key 0x5FFDB5DB5D1FF5F4 · http://keyserver.pgp.com

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

This is the tricky part - not sure how this could sensible be organised
without some support from the committers.  James, care to chime in here?

As for work, the website patch is in JIRA already & only requires (as
far as I remember) minor work still (HIVEMIND-198)

For a 1.2, the only thing remaining would be to verify the updated
libraries.  I should check if there is enough coverage in the unit tests
to allow us to simply switch versions and build.

Cheers,

Johan

Jochen Zimmermann wrote:
> Hi!
> 
> How could we organize working on this? Should we do things locally and
> open JIRA issues on it if we find code that must get updated?
> Or how would we do it?
> 
> Is there anybody from the committers left to comment Johans efforts?
> 
> Cheers,
> Jochen
> 
> 
> 
> ----- Original Message ----- From: "Johan Lindquist" <johan@kawoo.co.uk>
> To: <dev@hivemind.apache.org>
> Sent: Tuesday, January 06, 2009 11:01 AM
> Subject: Version 1.X Road Map
> 
> 
> Hi All,
> 
> After the discussions on the list, I decided to add the suggested
> road-map page to the WIKI
> 
> http://cwiki.apache.org/HIVEMIND2/hivemind-v1.html
> 
> It includes the suggestions from the list.
> 
> Cheers,
> 
> Johan
> 
>>

- --
you too?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFJZ2E/pHYnED7evioRAkIhAJwNdoHUhvXTqSj6hspOD1EvmwWazgCeL6ok
Q+P0meQEvMrHTFWxUsK7tVQ=
=C3ls
-----END PGP SIGNATURE-----

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

My bad - missed that.  WIKI page updated with below version info.

Cheers,

Johan

Raffael Herzog wrote:
> Am Dienstag, 6. Januar 2009 11.01:42 schrieb Johan Lindquist:
>> Hi All,
>>
>> After the discussions on the list, I decided to add the suggested
>> road-map page to the WIKI
>>
>> http://cwiki.apache.org/HIVEMIND2/hivemind-v1.html
>>
>> It includes the suggestions from the list.
> 
> Thanks, that roadmap makes sense. However, there's a mistake: Groovy's 
> groupId has changed to org.codehaus.groovy, so the latest version is not 
> 1.0-jsr-03, it's 1.5.6. I added a comment to the page.
> 
> Cheers,
>    Raffi
> 

- --
you too?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFJZNFWpHYnED7evioRAhSeAJ9qeNMDgACBeLe+4MlbQi5teyQ43QCeP5yN
jh1OovRxLchxLjYnu4ALU1E=
=zNPX
-----END PGP SIGNATURE-----

Am Dienstag, 6. Januar 2009 11.01:42 schrieb Johan Lindquist:
> Hi All,
>
> After the discussions on the list, I decided to add the suggested
> road-map page to the WIKI
>
> http://cwiki.apache.org/HIVEMIND2/hivemind-v1.html
>
> It includes the suggestions from the list.

Thanks, that roadmap makes sense. However, there's a mistake: Groovy's 
groupId has changed to org.codehaus.groovy, so the latest version is not 
1.0-jsr-03, it's 1.5.6. I added a comment to the page.

Cheers,
   Raffi

-- 
The difference between theory and practice is that in theory, there is
no difference, but in practice, there is.

herzog@raffael.ch · Jabber: herzog@raffael.ch
PGP Key 0x5FFDB5DB5D1FF5F4 · http://keyserver.pgp.com

Hi!

How could we organize working on this? Should we do things locally and open 
JIRA issues on it if we find code that must get updated?
Or how would we do it?

Is there anybody from the committers left to comment Johans efforts?

Cheers,
Jochen



----- Original Message ----- 
From: "Johan Lindquist" <johan@kawoo.co.uk>
To: <dev@hivemind.apache.org>
Sent: Tuesday, January 06, 2009 11:01 AM
Subject: Version 1.X Road Map


> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Hi All,
>
> After the discussions on the list, I decided to add the suggested
> road-map page to the WIKI
>
> http://cwiki.apache.org/HIVEMIND2/hivemind-v1.html
>
> It includes the suggestions from the list.
>
> Cheers,
>
> Johan
>
> - --
> you too?
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.6 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
>
> iD4DBQFJYywFpHYnED7evioRAm0NAJjXhvn7xBlO+cSok2HnEG4Xue0pAJ4pMY7j
> 0I8Bpspk7kGl+p20XXosnQ==
> =uO/n
> -----END PGP SIGNATURE-----
> 

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi All,

After the discussions on the list, I decided to add the suggested
road-map page to the WIKI

http://cwiki.apache.org/HIVEMIND2/hivemind-v1.html

It includes the suggestions from the list.

Cheers,

Johan

- --
you too?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD4DBQFJYywFpHYnED7evioRAm0NAJjXhvn7xBlO+cSok2HnEG4Xue0pAJ4pMY7j
0I8Bpspk7kGl+p20XXosnQ==
=uO/n
-----END PGP SIGNATURE-----

 Hi,

sorry for saying that, but I believe that Hivemind *is* dead.

Not because there are no more users or no interest, but because no one who is responsible
for that project does care anymore.

Every now and then there is a discussion that something should get done, everytime there is
some little discussion, and sometimes there is even work done (for example the task list from
Johan Lindquist) but then ..... nothing happens anymore.

It is correct that you can't give committer rights to unknown people, but right now there
is absolutely no chance to participate in the project. 
I know, we can fix bugs in the JIRA ... but there are bug fixes in the JIRA done, mostly by
Johan, that's true, but nevertheless: nothing happens to that bug fixes. And everyone who
is interested and is following the ongoings on this list notice that ... and that is not much
motivation to participate in any way.

If the actual committers do not have any time left (and that's perfectly understood, the most
of us must go to work and do such things in their spare time)  then at least ask if someone
volunteers and give committers rights to him/her (to make it clear: I'm not talking about
me).
Perhaps that does not work out either but you could try. 

No offence meant, perhaps I'm the one who is wrong and there is really not much interest in
a - even minor - release, then I apologize and give up :-)

Merry christmas to all of you, have nice holidays :-)

Cheers,
Jochen


-----Ursprüngliche Nachricht-----
Von: Johan Lindquist [mailto:johan@kawoo.co.uk] 
Gesendet: Samstag, 13. Dezember 2008 16:44
An: dev@hivemind.apache.org
Betreff: Re: HiveMind 1.2

Hi,

Updating/testing Hivemind with newer/latest versions of 3rd party
libraries is definately a good idea.  And I guess not just Javassist but
also Spring, Groovy etc should probably be tested as part of this.

This, together with some of the bug fixes already lined up & updating
the website with to be in Maven format would, in my opinion, make a good
candidate for a 1.2 release - I don't think it has be to more than that.

If nothing else, to simply get the momentum up (and provide some relief
to those who think the project is not active and therefore look
elsewhere for solutions). :)

Then the rest of the features in JIRA could constitute the 1.3
candidate, and perhaps moving all the docs to the WIKI - cause a common
complaint is as we all know the docs - the WIKI would help alleviate
this somewhat.

What say you out there? :)

Cheers,

Johan

Jochen Zimmermann wrote:
> Hi!
> 
> I'm not missing any functionality, it just feels a bit uncomfortable
> that there is no active development.
> 
> As I wrote more than once now, in my team I am not in a position to make
> decisions all alone, so I had some controversy about using Hivemind or
> not. People ask questions like: "what if Hivemind makes trouble (for
> example because of a newer Java Version), do we have enough knowledge
> about Hivemind and (perhaps more important) enough time to handle this
> alone?"
> 
> We use it and are happy with its functionality, but it is a weak point
> and we have a point "check the Spring Framework doing the job of
> Hivemind" on our TO-DO list (fortunately in the part that is labeled
> with "if we have time" ;-)
> 
> So what about maintenance? Update Hivemind and test it to work with the
> newest versions of for example c?
> This could be on a roadmap.
> 
> Regards,
> Jochen
> 
> ----- Original Message ----- From: "Johan Lindquist" <johan@kawoo.co.uk>
> To: <dev@hivemind.apache.org>
> Sent: Friday, December 12, 2008 8:31 PM
> Subject: Re: HiveMind 1.2
> 
> 
> Hi Raffael,
> 
> Don't think there is (ever was?) a roadmap  for beyond 1.1 - the JIRA
> cleanup was done in order to sort out what bugs/features could in
> theory be looked over and applied.   But  that doesn't constitute a
> roadmap for sure. :)
> 
> I get the impression that many of the existing users are overall happy
> with what Hivemind currently does and don't really expect it to do
> more (myself included to an extent).  Saying that though, there are
> some bug fixes which would be great to resolve, as well as a couple of
> new, nice features.  These could well constitute what gets done for
> 1.2 in my opinion
> 
> But beyond that, there is not much pending - would be great to hear
> what everyone else has to say on this.  Anything missing from
> Hivemind?  Anything that really bugs someone? :)
> 
> Cheers,
> 
> Johan
> 
> Raffael Herzog wrote:
>>>> Hi,
>>>>
>>>> Is there any roadmap for HiveMind 1.2? What was planned? What has been
> done
>>>> already? I mean, besides cleaning up Jira ... ;)
>>>>
>>>> If there isn't anything like that it would be nice, if someone who
>>>> knows/remembers those things could write a wiki page on that.
>>>>
>>>> Cheers,
>>>>    Raffi
>>>>
> 
>>

-- 
you too?

Hi,

Updating/testing Hivemind with newer/latest versions of 3rd party
libraries is definately a good idea.  And I guess not just Javassist but
also Spring, Groovy etc should probably be tested as part of this.

This, together with some of the bug fixes already lined up & updating
the website with to be in Maven format would, in my opinion, make a good
candidate for a 1.2 release - I don't think it has be to more than that.

If nothing else, to simply get the momentum up (and provide some relief
to those who think the project is not active and therefore look
elsewhere for solutions). :)

Then the rest of the features in JIRA could constitute the 1.3
candidate, and perhaps moving all the docs to the WIKI - cause a common
complaint is as we all know the docs - the WIKI would help alleviate
this somewhat.

What say you out there? :)

Cheers,

Johan

Jochen Zimmermann wrote:
> Hi!
> 
> I'm not missing any functionality, it just feels a bit uncomfortable
> that there is no active development.
> 
> As I wrote more than once now, in my team I am not in a position to make
> decisions all alone, so I had some controversy about using Hivemind or
> not. People ask questions like: "what if Hivemind makes trouble (for
> example because of a newer Java Version), do we have enough knowledge
> about Hivemind and (perhaps more important) enough time to handle this
> alone?"
> 
> We use it and are happy with its functionality, but it is a weak point
> and we have a point "check the Spring Framework doing the job of
> Hivemind" on our TO-DO list (fortunately in the part that is labeled
> with "if we have time" ;-)
> 
> So what about maintenance? Update Hivemind and test it to work with the
> newest versions of for example c?
> This could be on a roadmap.
> 
> Regards,
> Jochen
> 
> ----- Original Message ----- From: "Johan Lindquist" <johan@kawoo.co.uk>
> To: <dev@hivemind.apache.org>
> Sent: Friday, December 12, 2008 8:31 PM
> Subject: Re: HiveMind 1.2
> 
> 
> Hi Raffael,
> 
> Don't think there is (ever was?) a roadmap  for beyond 1.1 - the JIRA
> cleanup was done in order to sort out what bugs/features could in
> theory be looked over and applied.   But  that doesn't constitute a
> roadmap for sure. :)
> 
> I get the impression that many of the existing users are overall happy
> with what Hivemind currently does and don't really expect it to do
> more (myself included to an extent).  Saying that though, there are
> some bug fixes which would be great to resolve, as well as a couple of
> new, nice features.  These could well constitute what gets done for
> 1.2 in my opinion
> 
> But beyond that, there is not much pending - would be great to hear
> what everyone else has to say on this.  Anything missing from
> Hivemind?  Anything that really bugs someone? :)
> 
> Cheers,
> 
> Johan
> 
> Raffael Herzog wrote:
>>>> Hi,
>>>>
>>>> Is there any roadmap for HiveMind 1.2? What was planned? What has been
> done
>>>> already? I mean, besides cleaning up Jira ... ;)
>>>>
>>>> If there isn't anything like that it would be nice, if someone who
>>>> knows/remembers those things could write a wiki page on that.
>>>>
>>>> Cheers,
>>>>    Raffi
>>>>
> 
>>

-- 
you too?

Hi!

I'm not missing any functionality, it just feels a bit uncomfortable that 
there is no active development.

As I wrote more than once now, in my team I am not in a position to make 
decisions all alone, so I had some controversy about using Hivemind or not. 
People ask questions like: "what if Hivemind makes trouble (for example 
because of a newer Java Version), do we have enough knowledge about Hivemind 
and (perhaps more important) enough time to handle this alone?"

We use it and are happy with its functionality, but it is a weak point and 
we have a point "check the Spring Framework doing the job of Hivemind" on 
our TO-DO list (fortunately in the part that is labeled with "if we have 
time" ;-)

So what about maintenance? Update Hivemind and test it to work with the 
newest versions of for example javassist?
This could be on a roadmap.

Regards,
Jochen

----- Original Message ----- 
From: "Johan Lindquist" <johan@kawoo.co.uk>
To: <dev@hivemind.apache.org>
Sent: Friday, December 12, 2008 8:31 PM
Subject: Re: HiveMind 1.2


> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Hi Raffael,
>
> Don't think there is (ever was?) a roadmap  for beyond 1.1 - the JIRA
> cleanup was done in order to sort out what bugs/features could in
> theory be looked over and applied.   But  that doesn't constitute a
> roadmap for sure. :)
>
> I get the impression that many of the existing users are overall happy
> with what Hivemind currently does and don't really expect it to do
> more (myself included to an extent).  Saying that though, there are
> some bug fixes which would be great to resolve, as well as a couple of
> new, nice features.  These could well constitute what gets done for
> 1.2 in my opinion
>
> But beyond that, there is not much pending - would be great to hear
> what everyone else has to say on this.  Anything missing from
> Hivemind?  Anything that really bugs someone? :)
>
> Cheers,
>
> Johan
>
> Raffael Herzog wrote:
>> Hi,
>>
>> Is there any roadmap for HiveMind 1.2? What was planned? What has been
> done
>> already? I mean, besides cleaning up Jira ... ;)
>>
>> If there isn't anything like that it would be nice, if someone who
>> knows/remembers those things could write a wiki page on that.
>>
>> Cheers,
>>    Raffi
>>
>
> - --
> you too?
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.6 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
>
> iD8DBQFJQrwkpHYnED7evioRAsGcAJ4ouNmFrjiJfZ1/dAB7FEzzqX+DowCgmQYd
> nW6JLfBad4xbPeYxH8JskAw=
> =1twI
> -----END PGP SIGNATURE-----
> 

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi Raffael,

Don't think there is (ever was?) a roadmap  for beyond 1.1 - the JIRA
cleanup was done in order to sort out what bugs/features could in
theory be looked over and applied.   But  that doesn't constitute a
roadmap for sure. :)

I get the impression that many of the existing users are overall happy
with what Hivemind currently does and don't really expect it to do
more (myself included to an extent).  Saying that though, there are
some bug fixes which would be great to resolve, as well as a couple of
new, nice features.  These could well constitute what gets done for
1.2 in my opinion

But beyond that, there is not much pending - would be great to hear
what everyone else has to say on this.  Anything missing from
Hivemind?  Anything that really bugs someone? :)

Cheers,

Johan

Raffael Herzog wrote:
> Hi,
>
> Is there any roadmap for HiveMind 1.2? What was planned? What has been
done
> already? I mean, besides cleaning up Jira ... ;)
>
> If there isn't anything like that it would be nice, if someone who
> knows/remembers those things could write a wiki page on that.
>
> Cheers,
>    Raffi
>

- --
you too?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFJQrwkpHYnED7evioRAsGcAJ4ouNmFrjiJfZ1/dAB7FEzzqX+DowCgmQYd
nW6JLfBad4xbPeYxH8JskAw=
=1twI
-----END PGP SIGNATURE-----

Hi,

Is there any roadmap for HiveMind 1.2? What was planned? What has been done 
already? I mean, besides cleaning up Jira ... ;)

If there isn't anything like that it would be nice, if someone who 
knows/remembers those things could write a wiki page on that.

Cheers,
   Raffi

-- 
The difference between theory and practice is that in theory, there is
no difference, but in practice, there is.

herzog@raffael.ch · Jabber: herzog@raffael.ch
PGP Key 0x5FFDB5DB5D1FF5F4 · http://keyserver.pgp.com

     [ https://issues.apache.org/jira/browse/HIVEMIND-116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Johan Lindquist updated HIVEMIND-116:
-------------------------------------

    Attachment: hivemind-116-117.patch

Please find the patch attached providing one of the possible solutions to this. 

Note that due to the nature of this enhancement, it also fixes HIVEMIND-117

Comments are appreciated.

> add destroy-method attribute to the construct element of BuilderFactory
> -----------------------------------------------------------------------
>
>                 Key: HIVEMIND-116
>                 URL: https://issues.apache.org/jira/browse/HIVEMIND-116
>             Project: HiveMind
>          Issue Type: New Feature
>          Components: framework
>    Affects Versions: 1.1
>            Reporter: Richard Hensley
>         Attachments: hivemind-116-117.patch
>
>
> In order to keep object agnostic of container, please add attributes to the BuilderFactory
contruct element that support the standard lifecycle management of Hivemind. This request
is for the destroy step in the life cycle of a service. This attribute could be used instead
of RegistryShutdownListener and Discardable.
> The following is a specification should be a reasonable start.
> add a destroy-method attribute to the construct element recognized by BuilderFactory
> When the destroy-method is specified, the method must be a public void method taking
no parameters. This method is called when the registry is shutdown for primitive, singleton,
and pooled services. This method is
> called when the thread is cleaned up for a threaded service. When autowire-service is
enabled and destroy-method is not specified, BuilderFactory will introspect for a method called
destroyService() and
> treat it as a destroy-method. In the case of singleton and pooled services, if the service
implements the RegistryShutdownListener, the destroy-method is called before the RegistryShutdownListener.registryDidShutdown()
method. In the case of threaded services, if the service implements the Discardable interface,
the destroy-method is called before the
> Discardable.threadDidDiscardService() method.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

     [ https://issues.apache.org/jira/browse/HIVEMIND-213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Rob Harrop updated HIVEMIND-213:
--------------------------------

    Attachment: MessageFormatter.java

Updated version of MessageFormatter that passes the test case

> MessageFormatter should use ClassLoader of referenceClass when loading ResourceBundle
> -------------------------------------------------------------------------------------
>
>                 Key: HIVEMIND-213
>                 URL: https://issues.apache.org/jira/browse/HIVEMIND-213
>             Project: HiveMind
>          Issue Type: Bug
>          Components: framework
>    Affects Versions: 1.1.1
>            Reporter: Rob Harrop
>         Attachments: HIVEMIND-213.zip, MessageFormatter.java
>
>
> MessageFormatter always ignores the ClassLoader of referenceClass when loading resource
bundles. This makes using HiveMind in OSGi very difficult.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

     [ https://issues.apache.org/jira/browse/HIVEMIND-213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Rob Harrop updated HIVEMIND-213:
--------------------------------

    Attachment: HIVEMIND-213.zip

Test case in driver project. You'll need to munge the classpath a little bit.

I created a version of MessageFormatter against 1.1.1 that passes the test - I'll submit that
next.

> MessageFormatter should use ClassLoader of referenceClass when loading ResourceBundle
> -------------------------------------------------------------------------------------
>
>                 Key: HIVEMIND-213
>                 URL: https://issues.apache.org/jira/browse/HIVEMIND-213
>             Project: HiveMind
>          Issue Type: Bug
>          Components: framework
>    Affects Versions: 1.1.1
>            Reporter: Rob Harrop
>         Attachments: HIVEMIND-213.zip
>
>
> MessageFormatter always ignores the ClassLoader of referenceClass when loading resource
bundles. This makes using HiveMind in OSGi very difficult.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

    [ https://issues.apache.org/jira/browse/HIVEMIND-213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12651048#action_12651048
] 

Rob Harrop commented on HIVEMIND-213:
-------------------------------------

If you are happy to accept something like that then that won't be a problem. I'll try and
get on that today.

Rob

> MessageFormatter should use ClassLoader of referenceClass when loading ResourceBundle
> -------------------------------------------------------------------------------------
>
>                 Key: HIVEMIND-213
>                 URL: https://issues.apache.org/jira/browse/HIVEMIND-213
>             Project: HiveMind
>          Issue Type: Bug
>          Components: framework
>    Affects Versions: 1.1.1
>            Reporter: Rob Harrop
>
> MessageFormatter always ignores the ClassLoader of referenceClass when loading resource
bundles. This makes using HiveMind in OSGi very difficult.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

    [ https://issues.apache.org/jira/browse/HIVEMIND-213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12651045#action_12651045
] 

James Carman commented on HIVEMIND-213:
---------------------------------------

You may not need OSGI.  Just set up your own classloader and assert that it's used somehow?

> MessageFormatter should use ClassLoader of referenceClass when loading ResourceBundle
> -------------------------------------------------------------------------------------
>
>                 Key: HIVEMIND-213
>                 URL: https://issues.apache.org/jira/browse/HIVEMIND-213
>             Project: HiveMind
>          Issue Type: Bug
>          Components: framework
>    Affects Versions: 1.1.1
>            Reporter: Rob Harrop
>
> MessageFormatter always ignores the ClassLoader of referenceClass when loading resource
bundles. This makes using HiveMind in OSGi very difficult.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

    [ https://issues.apache.org/jira/browse/HIVEMIND-213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12651044#action_12651044
] 

Rob Harrop commented on HIVEMIND-213:
-------------------------------------

James,

I'll do my best. Getting a simple case to show this is going to be difficult because it needs
to run in OSGi. I'll see what I can do about providing a really simple Equinox app that highlights
this problem.

Rob

> MessageFormatter should use ClassLoader of referenceClass when loading ResourceBundle
> -------------------------------------------------------------------------------------
>
>                 Key: HIVEMIND-213
>                 URL: https://issues.apache.org/jira/browse/HIVEMIND-213
>             Project: HiveMind
>          Issue Type: Bug
>          Components: framework
>    Affects Versions: 1.1.1
>            Reporter: Rob Harrop
>
> MessageFormatter always ignores the ClassLoader of referenceClass when loading resource
bundles. This makes using HiveMind in OSGi very difficult.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

On Wed, Nov 26, 2008 at 8:27 AM, Johan Lindquist <johan@kawoo.co.uk> wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Hi James,
>
> No rush, but would allow better use of Hivemind in Maven - I suspect
> many other users might have fixed their poms already (if they use them)
> and forgotten about it :)
>
> And hope you get some rest :)


Thanks.  I'm sure I'll feel great after I chainsaw bayonet a few people
(Gears of War 2)! :)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi James,

No rush, but would allow better use of Hivemind in Maven - I suspect
many other users might have fixed their poms already (if they use them)
and forgotten about it :)

And hope you get some rest :)

Cheers,

Johan

James Carman wrote:
> On Wed, Nov 26, 2008 at 6:20 AM, Johan Lindquist <johan@kawoo.co.uk
> <mailto:johan@kawoo.co.uk>> wrote:
> 
>     -----BEGIN PGP SIGNED MESSAGE-----
>     Hash: SHA1
> 
>     Hi,
> 
>     I agree with that too - we have also been using it for 3 years now and
>     no major complaints.  A couple of things could of course be improved,
>     but they are definitely not showstoppers.
> 
>     One wish at this stage would be a official Maven 2.0 release of the
>     current trunk - we have cut our own release of the trunk to allow us to
>     use the Maven dependency stuff.  But again, nothing that can't be fixed
>     in your own pom in any case.
> 
> 
> I can cut a 1.1.2 release if folks really want one, based on maven 2.
>  I'm kind of swamped at work right now, but I'm getting ready to take my
> first vacation of the year here in a couple of weeks, so perhaps I can
> get that cooking while I'm at home (between rounds of Gears of War 2 of
> course :) on vacation.  
> 

- --
you too?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFJLU6upHYnED7evioRAhXyAJsGmi55k0RJ3r0zde/3rJNMX16GKQCfWTZ0
NJkPx9C+BM/+ZHi84IV3+jQ=
=NXbr
-----END PGP SIGNATURE-----

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi James,

Lacking the ability to 'juggle' issues in JIRA, I put forward the
following list a couple of months back:

http://cwiki.apache.org/confluence/display/HIVEMIND2/jira-issues-list

Should give you quick indicator what are candidates with patches at least.

Cheers,

Johan

James Carman wrote:
> It is great to hear that HiveMind does have a small, but devoted
> following still! :)  I still believe in HiveMind.  It does some things
> that the others just don't do.  I couldn't use HiveMind on our current
> project because the team members were afraid of the lack of
> documentation (the "book factor").  I'm happy with our current
> spring-based architecture, but there are definitely times that I wish we
> have HiveMind around for stuff like overriding service implementations.
> 
> I would encourage some of you devoted HiveMinders to submit some patches
> to anything you want to see in the 1.1.2 release and I'll do my best to
> get them in there (provided they have test cases and don't break
> anything else of course).  I'm sure I can get the other PMC members to
> vote for new members quite easily (I need 3 +1s I think), so maybe we
> can get some "new blood" in here and let them revive the project, but we
> can't do that without a "track record" which means community involvement
> and code patches.  Also, if you can't provide code patches, it might be
> helpful to put some votes out there in JIRA so that we know what folks
> are really wanting and we can concentrate our efforts.
> 
> 
> On Wed, Nov 26, 2008 at 6:24 AM, Jochen Zimmermann <zet4080@gmx.de
> <mailto:zet4080@gmx.de>> wrote:
> 
>     Sorry, hit the enter button accidentially :-)
> 
>     I agree too, we use Hivemind for company internal projects for some
>     time now and have no complaints and will use it for other projects
>     in the future.
> 
>     But sometimes I have problems to convince team members to stick to
>     Hivemind because there is no active development anymore ... so I can
>     understand the question if the project is dead or not because I had
>     some discussions because of that question in my team :-)
> 
>     Regards,
>     Jochen
> 
>     -------- Original-Nachricht --------
>     > Datum: Wed, 26 Nov 2008 09:10:57 -0200
>     > Von: Juliano Viana <juliano@logicstyle.com
>     <mailto:juliano@logicstyle.com>>
>     > An: dev@hivemind.apache.org <mailto:dev@hivemind.apache.org>
>     > Betreff: Re: [DISCUSS] [REPORT] HiveMind November 2008
> 
>     > Hello,
>     >
>     > Couldn't agree more.
>     > After using Hivemind over the last 4 years in many projects, I can
>     say I
>     > have no wish list for feature improvements at the moment. It could use
>     > better documentation but once you start using it , it simply works.
>     > I really don't believe using annotations as was planned for
>     Hivemind 2.0
>     > would be a big improvement in the way it works, maybe quite the
>     > opposite. So I believe this project, while no longer in active
>     > development, is far from dead.
>     >
>     > Regards,
>     >   - Juliano
>     > Johan Maasing wrote:
>     > > We use hivemind in our web portal, serving a lot of customers. So I
>     > > would say that our organization is pretty dependent on hivemind
>     and we
>     > > are slowly increasing the use of hivemind to wire together
>     frameworks,
>     > > both web-portals, plain java applications and webservice frameworks.
>     > > So why are we not involved in developing hivemind further?
>     > > Because "it just works". We have no big problems with hivemind,
>     it has
>     > > all the features we need. The configuration and
>     contribution-trick in
>     > > hivemind is a killer feature, I know no way to do the same thing as
>     > > easily in spring, guice or the others. Perhaps there is but I don't
>     > > know how. So for us hivemind is a very nice tool that just works.
>     > > So the hivemind project on apache might be slow and appear dead but
>     > > that shouldn't stop you from using it. It is mature, tested in
>     battle
>     > > and works.
>     > >
>     > > Cheers,
>     > > Johan
>     > >
>     > > 2008/11/18 James Carman <james@carmanconsulting.com
>     <mailto:james@carmanconsulting.com>>:
>     > >
>     > >> HiveMind hasn't been in active development for quite some time.
>     > >>
>     > >> On Tue, Nov 18, 2008 at 10:19 AM, fan_42
>     <frank.bommeli@noser.com <mailto:frank.bommeli@noser.com>>
>     > wrote:
>     > >>
>     > >>> I just stumbled up HiveMind.
>     > >>>
>     > >>> it sound interesting to me, but is it dead or is it on hold?
>     > >>>
>     > >>> --
>     > >>> View this message in context:
>     >
>     http://www.nabble.com/-DISCUSS---REPORT--HiveMind-November-2008-tp20437346p20561587.html
>     > >>> Sent from the HiveMind - Dev mailing list archive at Nabble.com.
>     > >>>
>     > >>>
>     > >>>
> 
> 

- --
you too?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFJLU0JpHYnED7evioRAukfAJ9HUHBJm/LZB7f4oztk7F6H4KYfNgCdHCyB
fcdiQiSCw41YU0B+JQ9/Ss8=
=xvby
-----END PGP SIGNATURE-----

It is great to hear that HiveMind does have a small, but devoted following
still! :)  I still believe in HiveMind.  It does some things that the others
just don't do.  I couldn't use HiveMind on our current project because the
team members were afraid of the lack of documentation (the "book factor").
 I'm happy with our current spring-based architecture, but there are
definitely times that I wish we have HiveMind around for stuff like
overriding service implementations.
I would encourage some of you devoted HiveMinders to submit some patches to
anything you want to see in the 1.1.2 release and I'll do my best to get
them in there (provided they have test cases and don't break anything else
of course).  I'm sure I can get the other PMC members to vote for new
members quite easily (I need 3 +1s I think), so maybe we can get some "new
blood" in here and let them revive the project, but we can't do that without
a "track record" which means community involvement and code patches.  Also,
if you can't provide code patches, it might be helpful to put some votes out
there in JIRA so that we know what folks are really wanting and we can
concentrate our efforts.

On Wed, Nov 26, 2008 at 6:24 AM, Jochen Zimmermann <zet4080@gmx.de> wrote:

> Sorry, hit the enter button accidentially :-)
>
> I agree too, we use Hivemind for company internal projects for some time
> now and have no complaints and will use it for other projects in the future.
>
> But sometimes I have problems to convince team members to stick to Hivemind
> because there is no active development anymore ... so I can understand the
> question if the project is dead or not because I had some discussions
> because of that question in my team :-)
>
> Regards,
> Jochen
>
> -------- Original-Nachricht --------
> > Datum: Wed, 26 Nov 2008 09:10:57 -0200
> > Von: Juliano Viana <juliano@logicstyle.com>
> > An: dev@hivemind.apache.org
> > Betreff: Re: [DISCUSS] [REPORT] HiveMind November 2008
>
> > Hello,
> >
> > Couldn't agree more.
> > After using Hivemind over the last 4 years in many projects, I can say I
> > have no wish list for feature improvements at the moment. It could use
> > better documentation but once you start using it , it simply works.
> > I really don't believe using annotations as was planned for Hivemind 2.0
> > would be a big improvement in the way it works, maybe quite the
> > opposite. So I believe this project, while no longer in active
> > development, is far from dead.
> >
> > Regards,
> >   - Juliano
> > Johan Maasing wrote:
> > > We use hivemind in our web portal, serving a lot of customers. So I
> > > would say that our organization is pretty dependent on hivemind and we
> > > are slowly increasing the use of hivemind to wire together frameworks,
> > > both web-portals, plain java applications and webservice frameworks.
> > > So why are we not involved in developing hivemind further?
> > > Because "it just works". We have no big problems with hivemind, it has
> > > all the features we need. The configuration and contribution-trick in
> > > hivemind is a killer feature, I know no way to do the same thing as
> > > easily in spring, guice or the others. Perhaps there is but I don't
> > > know how. So for us hivemind is a very nice tool that just works.
> > > So the hivemind project on apache might be slow and appear dead but
> > > that shouldn't stop you from using it. It is mature, tested in battle
> > > and works.
> > >
> > > Cheers,
> > > Johan
> > >
> > > 2008/11/18 James Carman <james@carmanconsulting.com>:
> > >
> > >> HiveMind hasn't been in active development for quite some time.
> > >>
> > >> On Tue, Nov 18, 2008 at 10:19 AM, fan_42 <frank.bommeli@noser.com>
> > wrote:
> > >>
> > >>> I just stumbled up HiveMind.
> > >>>
> > >>> it sound interesting to me, but is it dead or is it on hold?
> > >>>
> > >>> --
> > >>> View this message in context:
> >
> http://www.nabble.com/-DISCUSS---REPORT--HiveMind-November-2008-tp20437346p20561587.html
> > >>> Sent from the HiveMind - Dev mailing list archive at Nabble.com.
> > >>>
> > >>>
> > >>>
>

On Wed, Nov 26, 2008 at 6:20 AM, Johan Lindquist <johan@kawoo.co.uk> wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Hi,
>
> I agree with that too - we have also been using it for 3 years now and
> no major complaints.  A couple of things could of course be improved,
> but they are definitely not showstoppers.
>
> One wish at this stage would be a official Maven 2.0 release of the
> current trunk - we have cut our own release of the trunk to allow us to
> use the Maven dependency stuff.  But again, nothing that can't be fixed
> in your own pom in any case.


I can cut a 1.1.2 release if folks really want one, based on maven 2.  I'm
kind of swamped at work right now, but I'm getting ready to take my first
vacation of the year here in a couple of weeks, so perhaps I can get that
cooking while I'm at home (between rounds of Gears of War 2 of course :) on
vacation.

Sorry, hit the enter button accidentially :-)

I agree too, we use Hivemind for company internal projects for some time now and have no complaints
and will use it for other projects in the future.

But sometimes I have problems to convince team members to stick to Hivemind because there
is no active development anymore ... so I can understand the question if the project is dead
or not because I had some discussions because of that question in my team :-) 

Regards,
Jochen 

-------- Original-Nachricht --------
> Datum: Wed, 26 Nov 2008 09:10:57 -0200
> Von: Juliano Viana <juliano@logicstyle.com>
> An: dev@hivemind.apache.org
> Betreff: Re: [DISCUSS] [REPORT] HiveMind November 2008

> Hello,
> 
> Couldn't agree more.
> After using Hivemind over the last 4 years in many projects, I can say I 
> have no wish list for feature improvements at the moment. It could use 
> better documentation but once you start using it , it simply works.
> I really don't believe using annotations as was planned for Hivemind 2.0 
> would be a big improvement in the way it works, maybe quite the 
> opposite. So I believe this project, while no longer in active 
> development, is far from dead.
> 
> Regards,
>   - Juliano
> Johan Maasing wrote:
> > We use hivemind in our web portal, serving a lot of customers. So I
> > would say that our organization is pretty dependent on hivemind and we
> > are slowly increasing the use of hivemind to wire together frameworks,
> > both web-portals, plain java applications and webservice frameworks.
> > So why are we not involved in developing hivemind further?
> > Because "it just works". We have no big problems with hivemind, it has
> > all the features we need. The configuration and contribution-trick in
> > hivemind is a killer feature, I know no way to do the same thing as
> > easily in spring, guice or the others. Perhaps there is but I don't
> > know how. So for us hivemind is a very nice tool that just works.
> > So the hivemind project on apache might be slow and appear dead but
> > that shouldn't stop you from using it. It is mature, tested in battle
> > and works.
> >
> > Cheers,
> > Johan
> >
> > 2008/11/18 James Carman <james@carmanconsulting.com>:
> >   
> >> HiveMind hasn't been in active development for quite some time.
> >>
> >> On Tue, Nov 18, 2008 at 10:19 AM, fan_42 <frank.bommeli@noser.com>
> wrote:
> >>     
> >>> I just stumbled up HiveMind.
> >>>
> >>> it sound interesting to me, but is it dead or is it on hold?
> >>>
> >>> --
> >>> View this message in context:
> http://www.nabble.com/-DISCUSS---REPORT--HiveMind-November-2008-tp20437346p20561587.html
> >>> Sent from the HiveMind - Dev mailing list archive at Nabble.com.
> >>>
> >>>
> >>>