I'm afraid I cannot reproduce the problem you've described. However, the symptoms do look similar to the one described in this issue: https://issues.jboss.org/brows...
I would recommend importing a fresh copy of the kitchensink project as a Maven project, with no ./metadata directory present before import - the files here are created by the m2e integration. If you do continue to run into this problem, I'll also recommend deleting the .factorypath file from the root of the kitchensink project before importing it.
Vineet Reynolds
I'm afraid I cannot reproduce the problem you've described. However, the symptoms do look similar to the one described in this issue: https://issues.jboss.org/brows...
I would recommend importing a fresh copy of the kitchensink project as a Maven project, with no ./metadata directory present before import - the files here are created by the m2e integration. If you do continue to run into this problem, I'll also recommend deleting the .factorypath file from the root of the kitchensink project before importing it.
12:35 a.m., Monday May 20
Moderate this comment by email
Email address: vineet.reynolds@gmail.com | IP address: 209.132.188.34
Reply to this email with “Delete”, “Approve”, or “Spam”, or moderate from the Disqus moderation panel.