Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [m2e-users] M2e incorrectly showing build errors in Eclipse

Project with packaging=pom can only be used for configuration
inheritance, i.e. as <parent> pom of other projects, and/or as build
aggregator, i.e. have <module> element(s). Don't use them for anything
else. In your case you need to restructure your codebase to move java
code to a separate module project.

--
Regards,
Igor

On 12-04-03 11:52 AM, Knute Snortum wrote:
That's odd.  That's the opposite of my experience.  In the graphical pom
editor, I can't even change the packaging to something different than
"pom", and if you do it manually, you get an error: "Project build
error: packaging with value 'jar' is invalid.  Aggregator projects
require 'pom' as packaging."  This pom.xml is the parent of four other
modules.

How does m2e do parent/module type projects?

-----Original Message-----
From: m2e-users-bounces@xxxxxxxxxxx
[mailto:m2e-users-bounces@xxxxxxxxxxx] On Behalf Of Igor Fedorenko
Sent: Tuesday, April 03, 2012 4:05 AM
To: m2e-users@xxxxxxxxxxx
Subject: Re: [m2e-users] M2e incorrectly showing build errors in Eclipse

m2e does not support compilation of java classes (or execution of
anything maven plugins for that matter) for projects with packaging=pom.
You need to use packaging=jar or more specific packaging to compile java
classes.

--
Regards,
Igor

On 12-04-02 8:03 PM, Knute Snortum wrote:
A maven project in Eclipse is showing build errors because it is not
correctly reading the dependencies from the pom.xml file. I know it is

m2e because I can run a maven install manually without any problems.
If I had the errors Eclispe shows, maven would never pass its tests.

Version: Indigo Service Release 2

Build id: 20120216-1857

Org.eclipse.m2e.core: 1.0.200.20111223-1245

The imports in one of the Java files that are show "red exes":

*import*_junit_.framework.TestCase;

*import*_org.hibernate.Session_;

*import*_org.hibernate.SessionFactory_;

*import*_org.hibernate.cfg_.Configuration;

The dependency nodes in the pom.xml look like this:

<dependency>

<groupId>_junit_</groupId>

<artifactId>_junit_</artifactId>

<version>4.10</version>

</dependency>

...

<dependency>

<groupId>org.hibernate</groupId>

<artifactId>_hibernate_-core</artifactId>

<version>4.1.1.Final</version>

</dependency>

The pom is non-trivial but certainly not that complex: a parent with
four moduals. The moduals are all fine; only the parent. I don't know
if this list accepts attachments but I will try to attach the parent
pom file.

Knute Snortum

Developer

Catalyst IT Services



_______________________________________________
m2e-users mailing list
m2e-users@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/m2e-users
_______________________________________________
m2e-users mailing list
m2e-users@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/m2e-users
_______________________________________________
m2e-users mailing list
m2e-users@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/m2e-users


Back to the top