Thanks, that did the trick.
Now I feel stupid because I had
extensionstrue/extensions
there in the first place, but commented it out because I did not
understand what it was used for.
Cheers, Eric
On 4/7/2014 5:36 AM, Lars Corneliussen // Zen wrote:
OK, I found a solution. Instead of
dependency
groupIdnet.kolotyluk.windows.elevate/groupId
artifactIdelevate-common/artifactId
version0.0.21-SNAPSHOT/version
typedotnet-library/type
/dependency
I need to do
dependency
groupIdnet.kolotyluk.windows.elevate/groupId
The extensions lets the plugin hook in earlier and add packaging types and
corresponding lifecycle maps (means map initialize, compile, deploy, ++ to a
set of plugins)
-Ursprüngliche Nachricht-
Von: Eric Kolotyluk [mailto:eric.koloty...@gmail.com]
Gesendet: Montag, 7. April 2014 19:17
You need to have the compile-plugin with extension=true configured also when
resolving dependencies
It contains the mapping from dotnet-library to .dll - and also some logic
for resolving gac-licenses, ++
Ist hat done?
-Ursprüngliche Nachricht-
Von: Eric Kolotyluk
I do have extensiontrue/extension in my compile-plugin, but maven
still cannot find my dependency unless I use the system hack.
Cheers, Eric
On 4/7/2014 2:07 PM, Lars Corneliussen // Zen wrote:
You need to have the compile-plugin with extension=true configured also when
resolving
