+1
Arnaud
On Sat, Feb 23, 2008 at 7:27 PM, Joakim Erdfelt [EMAIL PROTECTED] wrote:
Here's my +1
Initially I was a little skeptical that we could pull off a TLP, I had
this feeling that we hadn't yet reached the level of interest and
participation that Continuum has, but since this email
Hi Dario,
I've already applied MRM-687 and MRM-692. I still need to take a further
look at the rest.
Anyway, could you also provide tests for MRM-687 and MRM-206? :-)
Thanks again!
-Deng
On Fri, Feb 15, 2008 at 12:06 AM, Dário Oliveros [EMAIL PROTECTED]
wrote:
Hi there,
I've recently
I'd surely love to see archiva make the TLP... which I think it deserves.
I'm not good with words when it comes to things like charters... so I'll
leave that to the experts.
Also, I see great things happening to Archiva with Deng as chair so I do not
have any better nominees in mind.
^_^
On
Hello,
I've repackaged and improved the spring support for plexus components in a
dedicated poject
--
https://svn.apache.org/repos/asf/maven/archiva/branches/springy/plexus-spring/
This new module provides runtime translation from plexus component
descriptors to a Spring XML context, using a
Can someone confirm the plexus behavior for IoC :
When the target field is a Map or a Collection and no role-hint is
specified, inject all component implementations
When the target field is the component interface and no role-hint is
specified, inject the no-hint component or the one with
On 25/02/2008, at 10:23 PM, nicolas de loof wrote:
Can someone confirm the plexus behavior for IoC :
When the target field is a Map or a Collection and no role-hint is
specified, inject all component implementations
When the target field is the component interface and no role-hint is
On plexus XML descriptors, the field-name seems to be optional... (
CacheFailuresTransferTest.xml)
This makes things more complex on the spring side. Is this a common use case
or can we live without this feature ?
I've found the bug in archiva-proxy CacheFailuresTransferTest : there was
some
On 26/02/2008, at 1:46 AM, nicolas de loof wrote:
On plexus XML descriptors, the field-name seems to be optional... (
CacheFailuresTransferTest.xml)
Yes, I think it will attempt to guess based on the interface type if
there is only one.
This makes things more complex on the spring
This makes things more complex on the spring side. Is this a common
use case
or can we live without this feature ?
If that's not doable, can we throw an unsupported exception if it's
not given?
An ApplicationContextException is thrown in such case on current codebase. I
will
archiva-proxy CacheFailuresTransferTest and archiva-policies
CachedFailuresPolicyTest no pass running under spring applicationContext.
I've added a minimal Contextualizable support for components that do lookup
in the plexusContainer.
Some more work required to build full archiva with spring ;-)
Hi Brett, all,
Have you considered using OSGi instead of [Plexus|Spring] ? I'm not an
expert of one or the other, but i try to do some projects with OSGi
since a few months and i like it.
Best regards,
Brett Porter a écrit :
Hi,
Given the discussion yesterday, I played around with some
Hi Carlos,
Thanks for your answer,
Carlos Sanchez a écrit :
spring has good integration with OSGi to enable Spring beans to be
OSGi services.
Yes, i'm aware that this integration exist and i've read a couple of
meetings reports related to it on the Equinox wiki, but why bother with
the
Hi Nicolas,
Sorry, I have looked at the recent updates to the code, hence my
question. Is this 'ready' enough to be used outside Archiva? I'd like to
integrate this into Continuum.
I think it might make sense to have this module in Plexus SVN repo - wdyt?
Good stuff!
Cheers,
Rahul
nicolas
Opps, I meant...
I haven't looked at the recent updates to the code...
PS: Sorry about the earlier empty msg.
/me slaps wrist - need to reinstall my mail client!
Rahul
On Tue, Feb 26, 2008 at 9:47 AM, Rahul Thakur
[EMAIL PROTECTED] wrote:
Hi Rahul,
Thanks for yout interest for this plexus-to-spring migration helper.
The code is still early experimental and requires some more testing : it
only has been tested on 2 archiva testcases and requires many fixes and
testcases to get stable.
Please give me one week to test it more, add
OK, this is just my personal opinion:
I think choice of Spring OSGi is influenced by a few things:
1) Archiva is looking to garner more contributions from the community.
Moving to Spring would, IMO, definately lessen the learning curve. There
is a comprehensive documentation and large user
+1
Thanks for starting this discussion Brett.
Not being tied to Maven also presents us with the option to grow beyond
the scope of a Maven repository manager so what we can support other
similar tools if the niche presents itself.
On Mon, 2008-02-25 at 13:04 +1100, Brett Porter wrote:
Ok,
nicolas,
This is way cool!
A very slick way of helping the transition.
I'm looking forward to some free time to dive into it.
- Joakim
nicolas de loof wrote:
Hi Rahul,
Thanks for yout interest for this plexus-to-spring migration helper.
The code is still early experimental and requires
18 matches
Mail list logo
