Igor,

the following bug actually comes from the mavenarchiver plugin from
m2e-extras (
https://github.com/sonatype/m2eclipse-extras/tree/master/org.sonatype.m2e.mavenarchiver),
which is required and installed by default with m2e-wtp.
Where should we manage related issues? I don't think there's a clear
statement about that, but I may have missed it.
We have the choice between bugzilla @ eclipse.org, jira @ sonatype.org or
the built-in github issue system.

regards,

Fred Bricon

2011/8/28 Christian Kaltepoth (JIRA) <[email protected]>

> Error message: No context maven session
> ---------------------------------------
>
>                 Key: MECLIPSEWTP-163
>                 URL: https://issues.sonatype.org/browse/MECLIPSEWTP-163
>             Project: Dev - M2E - WTP OSS
>          Issue Type: Bug
>    Affects Versions: 0.13.1
>         Environment: Fresh Eclipse Indigo installation + M2E 1.0.0 +
> M2E-WTP 0.13.1
>            Reporter: Christian Kaltepoth
>            Assignee: Fred Bricon
>         Attachments: seam-faces-m2e-wtp-bug.zip
>
> I've recently run into an issue which I thought was M2E related, but my
> tests showed that it only happens if M2E-WTP is installed.
>
> You can find the original issue here:
>
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=355292
>
>
> The problem occurs if I try to import the current snapshot of Seam Faces
> into my fresh installation of Eclipse Indigo (with m2e 1.0.0 and m2e-wtp
> 0.13.1 installed).
>
> I get the error message "No context maven session" for some of the pom.xml
> files after the import.
>
> Steps to reproduce:
>
>  * Unpack attached file "seam-faces-m2e-wtp-bug.zip" to some directory
> (UNPACK_DIR)
>  * Run "mvn install" once from the console to get all the dependencies.
>  * Use "Import -> Existing Maven Project" and choose
> "UNPACK_DIR/seam-faces/api/"
>  * You will see the error message "No context maven session" for the
> pom.xml
>
> I even found a workaround to fix this issue. Open
> "UNPACK_DIR/seamfaces/pom.xml" (the parent pom
> "org.jboss.seam.faces:seam-faces-parent" of the api module) and remove the
> parent element in there (referencing another parent
> "org.jboss.seam:seam-parent"). The error doesn't appear now anymore but I
> get tons of other errors due to the missing declarations from the second
> master pom.
>
>
> --
> This message is automatically generated by JIRA.
> -
> For more information on JIRA, see: http://www.atlassian.com/software/jira
>
>
>


-- 
"Have you tried turning it off and on again" - The IT Crowd
_______________________________________________
m2e-users mailing list
[email protected]
https://dev.eclipse.org/mailman/listinfo/m2e-users

Reply via email to