sverhagen wrote:
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.
I would suggest to try to reproduce this on small test projects. It
would help you to understand issue better and if you can't make it work
you can open a bug report and attach such test projects that would allow
us to reproduce this.
Thanks
Eugene
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
