Projects with packaging=pom are meant for project metadata inheritance
only but do not have any other behaviour associated with them, i.e. no
sources, resource, no dependencies (!), nothing (this is explained in
some details in [1] and [2]).
I am not sure what your actual goal is, but you should be able to run
your class after you a) change packaging to "jar" (or remove it, jar is
the default) and b) right-click, Manen->Update Project Configuration.
Let me know if this worked.
[1] http://maven.apache.org/pom.html#Inheritance
[2] http://www.sonatype.com/book/reference/lifecycle.html#d0e10037
sverhagen wrote:
I googled for this to no avail. I'd appreciate your help.
We have the following projects:
- "pkg-stationentry", dependency on "stationentry", I've posted a snippet of
its POM below
- "stationentry", has a Main.java with a main(...) method
I want to be able to run the main through "pkg-stationentry". I right-click
on the "pkg-stationentry" project in Eclipse, choose "Run As" "Java
Application". Now:
- With workspace resolution enabled: it does not find main
- With workspace resolution disabled: it does find and run main
Is this a bug or is this behaviour intended? It's for sure not how I desire
it to be, but perhaps there's a good explanation.
<artifactId>pkg-stationentry</artifactId>
<version>0.0.5-RC4</version>
<packaging>pom</packaging>
<dependencies>
<dependency>
<groupId>...</groupId>
<artifactId>stationentry</artifactId>
<version>0.0.7-SNAPSHOT</version>
</dependency>
</dependencies>
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
