Discussion:
Picocontainer c.f. Composer
John Patterson
2008-08-04 12:46:32 UTC
Permalink
Hi, I have used picocontainer in the past and switched to guice due its Java
5 goodness but missed the flexibility of pico. It looks like you guys have
done some good things with 2.x despite the sparse documentation and I would
like to move back to pico but am a bit worried about its longevity.

Will Apache Composer be based on pico?

When is Composer expected to have a release?

Cheers,

John
--
View this message in context: http://www.nabble.com/Picocontainer-c.f.-Composer-tp18810606p18810606.html
Sent from the NanoContainer - PicoContainer - Users mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email
Paul Hammant
2008-08-04 14:57:18 UTC
Permalink
Composer would have been based on PicoContainer, yes. But the move
has been called off. Jason from the Maven project had a greater
affinity to XBean-Reflect ( http://www.google.com/search?q=xbean
+reflect ) some time after the initial agreement. We looked at that a
felt that we could not / should not change PicoContainer to use it.
We have moved and repackaged the code and documentation, but in the
end just deleted from Apache.

PicoContainer is here to stay. Guice was a wake-up call for us (the
same idea but different and 3 years later ;). We will be pushing
PicoContainer relentlessly for the next few years, including further
into the generic space. I hope you notice that we have a greater
enthusiasm for releases now than we did in the 1.x era.

Regards,

- Paul
Post by John Patterson
Hi, I have used picocontainer in the past and switched to guice due its Java
5 goodness but missed the flexibility of pico. It looks like you guys have
done some good things with 2.x despite the sparse documentation and I would
like to move back to pico but am a bit worried about its longevity.
Will Apache Composer be based on pico?
When is Composer expected to have a release?
Cheers,
John
--
View this message in context: http://www.nabble.com/Picocontainer-c.f.-Composer-tp18810606p18810606.html
Sent from the NanoContainer - PicoContainer - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
http://xircles.codehaus.org/manage_email
---------------------------------------------------------------------
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email
John Patterson
2008-08-04 15:44:37 UTC
Permalink
Post by Paul Hammant
Composer would have been based on PicoContainer, yes. But the move
has been called off. Jason from the Maven project had a greater
affinity to XBean-Reflect ( http://www.google.com/search?q=xbean
+reflect ) some time after the initial agreement. We looked at that a
felt that we could not / should not change PicoContainer to use it.
We have moved and repackaged the code and documentation, but in the
end just deleted from Apache.
PicoContainer is here to stay. Guice was a wake-up call for us (the
same idea but different and 3 years later ;). We will be pushing
PicoContainer relentlessly for the next few years, including further
into the generic space. I hope you notice that we have a greater
enthusiasm for releases now than we did in the 1.x era.
Good to hear. One thing that pissed me off with Guice is that they have not
had a release - even just bug fixes - for over a year. I think Guice 2 has
some lifecycle support planned but this has been possible with pico for
ages.

I'm with you fellas!
--
View this message in context: http://www.nabble.com/Picocontainer-c.f.-Composer-tp18810606p18813819.html
Sent from the NanoContainer - PicoContainer - Users mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email
Paul Hammant
2008-08-04 15:59:19 UTC
Permalink
Well healthy competition should keep everyone on their toes ;-)

Regards,

- Paul
Post by John Patterson
Post by Paul Hammant
Composer would have been based on PicoContainer, yes. But the move
has been called off. Jason from the Maven project had a greater
affinity to XBean-Reflect ( http://www.google.com/search?q=xbean
+reflect ) some time after the initial agreement. We looked at that a
felt that we could not / should not change PicoContainer to use it.
We have moved and repackaged the code and documentation, but in the
end just deleted from Apache.
PicoContainer is here to stay. Guice was a wake-up call for us (the
same idea but different and 3 years later ;). We will be pushing
PicoContainer relentlessly for the next few years, including further
into the generic space. I hope you notice that we have a greater
enthusiasm for releases now than we did in the 1.x era.
Good to hear. One thing that pissed me off with Guice is that they have not
had a release - even just bug fixes - for over a year. I think Guice 2 has
some lifecycle support planned but this has been possible with pico for
ages.
I'm with you fellas!
--
View this message in context: http://www.nabble.com/Picocontainer-c.f.-Composer-tp18810606p18813819.html
Sent from the NanoContainer - PicoContainer - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
http://xircles.codehaus.org/manage_email
---------------------------------------------------------------------
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email
pchacin
2008-08-05 09:40:48 UTC
Permalink
Hi

I'm new to picocontainer, but so far, I think is far better than guice
and others, mostly when we consider the ratio of weight/features, which
I still find impressive.

Guice is attracting too much attention for the little it offers, maybe
just because the "google" brand. maybe you guys at the picocontainer
team should do a little more of marketing and (re)gain the position it
deserves in the niche of dependency injection.

Regards
Post by Paul Hammant
Well healthy competition should keep everyone on their toes ;-)
Regards,
- Paul
Post by John Patterson
Post by Paul Hammant
Composer would have been based on PicoContainer, yes. But the move
has been called off. Jason from the Maven project had a greater
affinity to XBean-Reflect ( http://www.google.com/search?q=xbean
+reflect ) some time after the initial agreement. We looked at that a
felt that we could not / should not change PicoContainer to use it.
We have moved and repackaged the code and documentation, but in the
end just deleted from Apache.
PicoContainer is here to stay. Guice was a wake-up call for us (the
same idea but different and 3 years later ;). We will be pushing
PicoContainer relentlessly for the next few years, including further
into the generic space. I hope you notice that we have a greater
enthusiasm for releases now than we did in the 1.x era.
Good to hear. One thing that pissed me off with Guice is that they have not
had a release - even just bug fixes - for over a year. I think Guice 2 has
some lifecycle support planned but this has been possible with pico for
ages.
I'm with you fellas!
--
http://www.nabble.com/Picocontainer-c.f.-Composer-tp18810606p18813819.html
Sent from the NanoContainer - PicoContainer - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
http://xircles.codehaus.org/manage_email
---------------------------------------------------------------------
http://xircles.codehaus.org/manage_email
--
========================================================================
0 0 0 Pablo Chacin | Dept. d'Arquitectura de Computadors
0 0 0 e-mail: pchacin-***@public.gmane.org | UPC-Campus Nord. Modul D6-212
0 0 0 phone: +34 +93 405 4059 | Jordi Girona, 1-3
U P C fax: +34 +93 401 7055 | 08034 Barcelona - SPAIN
www: http://personals.ac.upc.es/pchacin
========================================================================


---------------------------------------------------------------------
To unsubscribe from this list, please visit:

http://xircles.codehaus.org/manage_email
Loading...