This is precisely what the ignore functionality does - it updates the
workspace lifecycle mapping metadata.It is supported in 4.3 - but
you may have an older version of the m2e plugin.
In any case, I've added it to source control (under ides/eclipse) and
updated README. Please try
On 29-04-2014 10:29, Hans Schwäbli wrote:
It is a bit more tricky than I thought to get that sources working in
Eclipse.
First I have to check jbehave-core out. But then I don't must import
it into Eclipse. First I have to configure the settings.xml with the
company proxy settings I need and
Hello Gavião,
maybe I didn't spend enough time to discover why it did not work after I
found a solution. It had a lot of compile errors if I don't pre-build it
outside Eclipse before importing it.
I don't know if copying the settings.xml to the .m2 folder would fix the
problem. I can put
Thank you.
I forgot about the page which explains the JBehave source building. So I
didn't see that I need to use that settings.xml file.
But I think my biggest mistake was when importing the maven project into
Eclipse. The import wizard shows me the plugins which can't be found. There
I can
Yes, the m2e plugin is very annoying in this. IMO it's one of the
worst design decisions they've made when migrating from the original
m2eclipse plugin. But with recent versions, Eclipse allows you to mark
as ignored these errors without modifying the pom.xml. The feature is
marked as
