Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [m2e-users] Making m2e understand new packaging types

What is the desired behaviour for projects with packaging=eba when
inside eclipse workspace?

--
Regards,
Igor

On 11-02-24 09:17 AM, Alasdair Nottingham wrote:
Although in my case I don't need the JDT nature etc because the
project doesn't contain javacode.

On 24 February 2011 13:59, Julien HENRY<henryju@xxxxxxxx>  wrote:
Hi,

Seems it is related to a bug I just reported here:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=338084

Regards,

Julien



----- Message d'origine ----
De : Alasdair Nottingham<not@xxxxxxxxxx>
À : m2e-users@xxxxxxxxxxx
Envoyé le : Jeu 24 février 2011, 14h 50min 01s
Objet : [m2e-users] Making m2e understand new packaging types

Hi,

I am a committer on the apache aries project and we have a  maven
plugin that creates a new packaging type called eba. When I  import
projects using m2e it flags projects with this packaging type with  the
error:

Unknown or missing lifecycle mapping (project packaging  type="eba")

What do I need to do to get m2e to cope with this packaging  type?

I'm using m2e 0.13 and the version of m2e I used prior to it moving  to
eclipse didn't seem to have a problem.

Thanks
Alasdair

--
Alasdair Nottingham
not@xxxxxxxxxx
_______________________________________________
m2e-users  mailing list
m2e-users@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/m2e-users

_______________________________________________
m2e-users mailing list
m2e-users@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/m2e-users






Back to the top