Yes, perhaps, but I actually don't want to declare the dependency in the POM and since I'm never actually running any of the classes from Maven I shouldn't have to. There's a long story around this, but to simplify, I have multiple projects that constitute my "product". The creation of the product's "kit" collects all the jar files together and the script that launches the product puts all the jar files on the classpath, to satisfy the runtime dependency requirement.
Let me first focus on the behavior of an Eclipse launcher and its classpath properties when neither Maven nor m2e are involved. One can add an arbitrary Eclipse project to any launcher's classpath. When one does this, one has the option to "Add required projects of selected projects" (as the UI puts it). E.g., suppose Eclipse Project X depends on Eclipse Project Y. When I add Project X to the launcher one gets to say whether or not Project Y should be added to the classpath as well. I assume that the launcher's classpath implicitly also acquires the projects' library dependencies.
Now let's add Maven/m2e to the story: By analogy with the non-Maven/m2e scenario, I think it'd be sensible if when one adds an Eclipse project that has the Maven nature to a launcher's classpath that the Maven dependencies of that project also (implicitly) get added to the launcher's classpath. Of course, I have no idea whether the architecture of launchers allows for this (i.e., allows for m2e to have this "contribute to classpath" feature). That's really what I'm asking about though.
Nat
