AW: Maven release gives error on multi-module project

1.4 and 1.5, but then I found why it skipped the type dll dependencies. Finally I used only the version 1.5 for both plugins with a little hack: https://github.com/octavian-h/npanday/commit/02a0fa919534fc4afee4ae407f8e597fd7f5e6a7 Octavian 2014-12-08 11:00 GMT+02:00 Lars Corneliussen // Zen m

AW: Determining next steps for the NPanday

Hi Roman, even though it hurts I think retiring the project is the right thing to do. Not because of the quality of NPanday, but just because the (developer!) community is effectively gone. While I'm still using NPanday every day (1.5 snapshot), it is all on the same project and there is no

AW: NPanday compile plugin doesn't get dll dependencies

Hi Octavian, sorry for not replying earlier. In 1.5 we changed the artifact types to start with a dotnet-. http://incubator.apache.org/npanday/docs/1.5.0-incubating-SNAPSHOT/guide/advanced/project-types.html I'm not sure if we ever supported dll explicitly. The thing is, that maven would

AW: Maven release gives error on multi-module project

Do you mix the versions 1.4 and 1.5? I'm pretty sure we have some bugs around the release lifecycle in NPanday 1.5, though this one seems strange But shouldn't maven resolve the project.version? @Brett, any idea? @Octavian: Could you provide a zip file (if your example project is real :-)) _

AW: AssemblyInfo.cs problems

Yes. That looks like a bug! -Ursprüngliche Nachricht- Von: Eric Kolotyluk [mailto:eric.koloty...@gmail.com] Gesendet: Sonntag, 13. April 2014 01:26 An: npanday-users@incubator.apache.org Betreff: AssemblyInfo.cs problems I am trying to build my project, but it fails because:

AW: Building an executable from modules

Also: There is no living equivalent to ueber-jar in .NET. Modules were made for that, but they never actually got there - they are never linked to and deployed separately. People are using ILmerge for combining assemblies. But it also has drawbacks. When a references b, and b is merged to c,

AW: Building an executable from modules

I have never tried that. Don't think anyone is maintaining it. I'd rather use dotnet-library and then at the end merge with ilmerge You could use the exec-plugin for that, allthough I'd like to have a maven-ilmerge-plugin. -Ursprüngliche Nachricht- Von: Eric Kolotyluk

AW: AW: Maven cannot see my DLL artifact

artifact 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

AW: AW: Can't compile a library

:36 AM, Lars Corneliussen // Zen wrote: http://incubator.apache.org/npanday/docs/1.5.0-incubating-SNAPSHOT/plu gins/m aven-compile-plugin/usage.html

AW: Maven cannot see my DLL artifact

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