Fred,
On Tue, Jan 15, 2013 at 12:23 PM, Miguel Almeida <[email protected]>wrote: > > >> Your problem *may* be caused by the jetty plugin not supporting the >> workspace projects exposed by m2e. Finding out would require debugging >> jetty:run. have you asked the jetty plugin maintainers? >> > Trying on IRC (I'm asking Jesse), I might also try the mailing list. But I > take it it's a long shot. How or in what path are the workspace projects > exposed by m2e in? I take it that the plugin doesn't like workspace > projects very much, as when I run jetty:run-war it'll be expecting a > jar/war dependency and complain about the workspace project dependency [1] > > As Jesse McConnell points out, "that is something the jetty plugin will never do, it is intended to run on the command line and not care about editors or workspaces". What I don't understand is why m2e (or m2e-wtp) is failing to expose the overlay's resources to the warTest classpath.
_______________________________________________ m2e-users mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/m2e-users
