Any project that want's to resolve references (transitive or not) need
the compile-plugin as extension in order to map from packaging to file
extension... dotnet-library -> dll, dotnet-executable -> exe
Workarround: Instead of specifying the packaging, you can also specify
the file extension as <type> in dependencies. This should work without
the compile-plugin, too. But it is not really a nice way.
Sorry for hinting here again, but how can we get beyond NPANDAY-412? It
is one of the last issues to be resolved for 1.3.1-incubating.
Am 02.05.11 22:25, schrieb John Fallows:
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.
