When a non-NPanday project (in an independent Maven execution) depends on a
dotnet-executable, and tries to resolve transitive dependencies for that
project, such as dotnet-library, the build breaks for the non-NPanday
project because it fails to resolve the transitive dotnet-library
dependency.

The original dependency was not for the dotnet-executable itself, but for a
separate classifier on that project, so the NPanday plugin was not necessary
in the non-NPanday project to resolve the immediate dependency.  However, in
order to avoid the breakage when attempting to resolve the dotnet-library
transitive dependency, we had to add in the NPanday plugin as an extension
in the non-NPanday project.

Is this an expected requirement?  Is it specific to NPanday, or a general
requirement for Maven?

One could imagine there being enough information in the dotnet-executable
pom to alleviate the need for specifying the NPanday extension plugin again
in the non-NPanday project to resolve the transitive dotnet-library
dependency.

tc,
-john.
-- 
>|< Kaazing Corporation >|<
John Fallows | CTO | +1.650.960.8148
444 Castro St, Suite 1100 | Mountain View, CA 94041, USA

Reply via email to