Eclipse, Maven, pom.xml error

1,287 views
Skip to first unread message

Ezio Ostorero

unread,
May 28, 2015, 3:50:19 AM5/28/15
to camunda-...@googlegroups.com
  Good Morning All,

  Disclaimer, I'm a Camunda newbie, therefore I'm starting from here: http://docs.camunda.org/7.2/guides/getting-started-guides/developing-process-applications/#set-up/eclipse

  Couldn't reach first base, tough :-|

  The supplied pom.xml file looks like broken, or there's something missing in my installation.
  I got this set of errors:

Multiple annotations found at this line:
    - Plugin execution not covered by lifecycle configuration:
org.apache.maven.plugins:maven-resources-plugin:2.5:testResources
(execution: default-
     testResources, phase: process-test-resources)
    - Plugin execution not covered by lifecycle configuration:
org.apache.maven.plugins:maven-resources-plugin:2.5:resources (execution:
default-resources,
     phase: process-resources)
    - Plugin execution not covered by lifecycle configuration:
org.apache.maven.plugins:maven-compiler-plugin:2.3.2:compile (execution:
default-compile,
     phase: compile)
    - Plugin execution not covered by lifecycle configuration:
org.apache.maven.plugins:maven-compiler-plugin:2.3.2:testCompile
(execution: default-
     testCompile, phase: test-compile)

  I did my share of googling and research, looks like the problem is well known, and widespread, in both Camunda and more generally M2E environments.

  I foud a good share of "try this", "maybe that", "add a plugin section", but no clear and reliable solution.

  Any ideas?

  Thanks in advance for your support,

        Ezio

Sebastian Menski

unread,
May 29, 2015, 3:24:27 AM5/29/15
to camunda-...@googlegroups.com, ezio.o...@gmail.com
Hi Ezio,

which line of the pom.xml seems to be broken for you?

Cheers,
Sebastian

Ezio Ostorero

unread,
May 29, 2015, 10:41:58 AM5/29/15
to camunda-...@googlegroups.com, ezio.o...@gmail.com
  Hello Sebastian!!

  The highlighted section looks to be this one:

  <packaging>war</packaging>

  For sake of completeness, here's my environment:

  OS: Mac OS X 10.8.5

  Eclipse: Kepler 20140224-0627

  Ciao,

       Ezio

Sebastian Menski

unread,
Jun 1, 2015, 3:29:11 AM6/1/15
to camunda-...@googlegroups.com, ezio.o...@gmail.com
Hi Ezio,

sorry but the pom is valid and this seems to be a problem with your eclipse installation. I'm not using eclipse by myself so I can't help you with this. Sorry.

Cheers,
Sebastian

thorben....@camunda.com

unread,
Jun 1, 2015, 3:31:12 AM6/1/15
to camunda-...@googlegroups.com, ezio.o...@gmail.com
Hi Ezio,

Does the issue prevent you from building the project in eclipse? I personally tend to ignore these issues unless they prevent building.

Cheers,
Thorben

Ezio Ostorero

unread,
Jun 1, 2015, 11:17:19 AM6/1/15
to camunda-...@googlegroups.com, ezio.o...@gmail.com
Hi Thorben.

  Well I was hoping that Maven could take the hasse of building a Java project off from me :-|

  So, I will have to do it the good? old way.
  Or, I can run the Maven build from command line.

  Neither is exactly straightforward ... I'll give it a try. Not being a Maven expert will bring me some hard time.

  Too bad, I am interested in BPM, but I'm pretty much stuck in Java, Maven and Eclipse nuts and bolts.

  Ciao,

                     Ezio

thorben....@camunda.com

unread,
Jun 1, 2015, 11:23:47 AM6/1/15
to camunda-...@googlegroups.com
Hi Ezio,

That is not exactly what I mean. Please do use Maven ;). It's just the eclipse integration that behaves strangely sometimes.

What happens if you attempt to build the project with Maven in eclipse? I.e. Right click on the project -> Run as -> Maven build with goals "clean install".

If you have maven installed as a command line tool, you can also build from command line. Some people prefer that anyway. You'll have to install Maven as a standalone application then (meaning that having only the m2eclipse plugin installed is not sufficient), see [1].

Cheers,
Thorben

[1] https://maven.apache.org/download.cgi#Installation

Ezio Ostorero

unread,
Jun 1, 2015, 11:46:43 AM6/1/15
to camunda-...@googlegroups.com
  Hi again Thorben.


>It's just the eclipse integration that behaves strangely sometimes

  Yup. From what I've been reading recently, that integration is erratical, at best.


>If you have maven installed as a command line tool, you can also build from command line. Some people prefer that anyway.

  YEAH! I'm an old-time Unix guy ... well nothing beats the command line :-)

  I have mvn installed as an utility on my Mac, so running it seems so far to be somehow working.

ezio$ mvn --version
Apache Maven 3.0.3 (r1075438; 2011-02-28 18:31:09+0100)
Maven home: /usr/share/maven
Java version: 1.8.0_45, vendor: Oracle Corporation
Java home: /Library/Java/JavaVirtualMachines/jdk1.8.0_45.jdk/Contents/Home/jre
Default locale: en_US, platform encoding: UTF-8
OS name: "mac os x", version: "10.8.5", arch: "x86_64", family: "mac"

  As for M2N:


>Right click on the project -> Run as -> Maven build with goals "clean install".

  I think here's the problem. "Run as" has no knowledge of Maven.
  "Run as" leads to "Run Configurations..." that brings up a pop-up with many choices, none of them looks like Maven.

  So I believe my Eclipse is confused: it is OK to create a Maven project, but not OK to run it.

  Thank you for your attention,

           Ezio

Ezio Ostorero

unread,
Jun 1, 2015, 1:56:10 PM6/1/15
to camunda-...@googlegroups.com
Well!!

It looks like the cmd-line mvn plus deploy is working fine.

Thank you Thorben for your advice.

  Ciao,

           Ezio
Reply all
Reply to author
Forward
0 new messages