Igor Fedorenko-4 wrote: > > 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. >
The pkg-stationentry was originally meant to describe an assembly that we use for deployment to our actual targets. It has no (re-)sources of its own, therefore the POM packaging used to be good enough. However, it has its own dependencies. I won't be able argue with you whether these dependencies are appropriate or not, but it worked well, apart from the underlying issue that we now discovered. When I change it to a JAR packaging (I tried it just now), I'm having the same problems, probably since the main(...) is still not coming from the actual project, rather from a dependency. I tried the "Update Project Configuration" as well. -- View this message in context: http://www.nabble.com/Not-finding-main%28...%29-through-workspace-resolution-tp19103273p19110423.html Sent from the Maven Eclipse - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
