You need to configure the maven-compile-plugin as an extension:
http://incubator.apache.org/npanday/docs/1.5.0-incubating-SNAPSHOT/plugins/m
aven-compile-plugin/usage.html
-Ursprüngliche Nachricht-
Von: Eric Kolotyluk [mailto:eric.koloty...@gmail.com]
Gesendet: Montag, 7. April 2014 02
4 5: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
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 [mailto:eric.kolot
y DLL artifact
I do have true in my compile-plugin, but maven still
cannot find my dependency unless I use the 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 dependencies
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 [mailto:eric.kol
Well, I think if all you want is a simple exe, you are better off with just
using visual studio and run the build from there... or via msbuild.
NPanday is overkill then.
But it pays of for bigger projects :-)
-Ursprüngliche Nachricht-
Von: Eric Kolotyluk [mailto:eric.koloty...@gmail.com]
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, the
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:
[INFO]
e: AW: AssemblyInfo.cs problems
OK, I entered a JIRA issue for this.
Cheers, Eric
On 4/14/2014 1:37 AM, Lars Corneliussen // Zen wrote:
> Yes. That looks like a bug!
>
> -Ursprüngliche Nachricht-
> Von: Eric Kolotyluk [mailto:eric.koloty...@gmail.com]
> Gesendet: Sonntag, 13. A
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 us
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 :-))
_
L
gives error on multi-module project
Hello,
Yes I have mixed the versions 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/02a0fa919534fc4afee4ae407f8e597f
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 n
13 matches
Mail list logo
