On 8 Jan 2014, at 20:03, Kristian Rosenvold
wrote:
> With spring, you can say:
>
> @Component
> class X implements Y,Z
>
> And at call site:
>
> @Inject
> private Y y;
>
> @Inject
> private Z z;
>
> And expect (scope dependent) to get the same instance of X in both y and z.
>
> Can I achie
Technically there should be separate *issues* no matter what, since
deciding how to *release* is typically a different process.
Kristian
2014/1/9 Stephen Connolly
> Well plexus is a separate (although related) community. We certainly can
> combine the vote thread for the maven community compon
Well plexus is a separate (although related) community. We certainly can
combine the vote thread for the maven community components, and we have
done so in the past... just a question of the release manager deciding that
they are fine coupling the releases of multiple components in one vote.
On 9
On 9 January 2014 17:37, Kristian Rosenvold
wrote:
> Create one jira ticket for each project and create a 'depends on' link
> between the issues.
I think there was talk about voting to release the lot as a bundle but
I've not done that - you might search the archive for it.
The other way is just
