You have rights now.
Emmanuel
Stephane Nicoll wrote:
Sure. I don't seem to have dev rights on Jira though. Do I need to
contact somebody?
Thanks,
Stéphane
On 7/18/05, Emmanuel Venisse <[EMAIL PROTECTED]> wrote:
Stephane,
Can you add some issues for this features and assign them to you?
E
Sure. I don't seem to have dev rights on Jira though. Do I need to
contact somebody?
Thanks,
Stéphane
On 7/18/05, Emmanuel Venisse <[EMAIL PROTECTED]> wrote:
> Stephane,
>
> Can you add some issues for this features and assign them to you?
>
> Emmanuel
>
> Stephane Nicoll wrote:
> > Hello Vinc
Stephane,
Can you add some issues for this features and assign them to you?
Emmanuel
Stephane Nicoll wrote:
Hello Vincent,
- EAR plugin and ear packaging. This is being fixed as Stephane as published
a patch to JIRA and he's now going to get commit privs! Cool :-)
AFAIK, it has been appl
On Mon, 18 Jul 2005, Vincent Massol wrote:
Hi Vincent,
> Hi,
>
> Just a quick heads-up listing the blocking points for the m2 migration of
> the cargo project:
>
> - No jarjar feature to aggregate *and* publish the aggregated jar to a maven
> repo *and* make the aggregated jar a proper dependency
Hello Vincent,
> - EAR plugin and ear packaging. This is being fixed as Stephane as published
> a patch to JIRA and he's now going to get commit privs! Cool :-)
AFAIK, it has been applied now so it should be ok. Regarding EAR
plugin and EAR packaging in general, It would be very nice to have
conc
Hi,
Just a quick heads-up listing the blocking points for the m2 migration of
the cargo project:
- No fail-build-on-checkstyle-violation feature
- Missing Clirr plugin for m2. I've just added it to the matrix list.
Although it's not yet automated in m1 build, I'm using it at each delivery
to lis
