Conflicting lifecycle mapping

Try this artilce and see if you get same results -

Scott's Digital Community: Creating an Adobe Experience Manager project using Lazybones

If necessary - we will setup a connect session early next week.

im using Neon eclipse now, and the problem still exist

im currently using Oxygen on eclipse, sure will try Neon this time! thanks everyone!

Hi,

I am able to add the project to the AEM server without any issues. PFA screenshot below.

BTW Which eclipse version you are using. Use Eclipse Neon for J2EE IDEec

BTE, Which eclipse version you are using. Use Eclipse Neon - Eclipse IDE for Java EE developers.

Thanks,

Ratna Kumar.

What version of Eclipse are you using. See this artilce where we specify the version of Eclipse:

Creating an Adobe Experience Manager project using Lazybones

Can you try with that Eclipse version. I think it sounds like an IDE issue.

there's no problem in installing it using mvn,

the problem is in eclipse where i need to add the project to the aem server

I too just tested the article and it worked nicely. Please see the below screenshot for the same.

Thanks,

Ratna.

I just tested and it builds via Maven.

Try again and accept all the default values when entering the Lazybones commands.

Another suggestion - try this article  - similar - but see if you get same results or if it works:

Scott's Digital Community: Creating an Adobe Experience Manager project using Lazybones