Re: NPanday ArtifactTypes should get externalized

2011-01-11 Thread me
Hello Henning, (und Hallo auch auf Deutsch :-) It will give me an error about an unknown artifact type. I had to modify components/dotnet-core/scr/main/java/npanday/ArtifactType.java adding /** * Added to suit wsp-builder projects */ WSP("wsp", "library", "dll")

Re: NPanday ArtifactTypes should get externalized

2011-01-11 Thread Henning Groß
Hi Brett, hi @rest! Unfortunately I cannot provide you with a sample project as our alpha-stuff is in an internal repository. I will provide you with as much info as I think is needed. This mail will get long :) Situation: a VS-ClassLibrary-Project needs to be build, after compile, during pack

Re: NPanday ArtifactTypes should get externalized

2011-01-10 Thread Brett Porter
It should be possible, as long as you are adding the true flag to your plugin's use. This is all internal to Maven - if there is somewhere that NPanday can't pick that up then it might possibly need to be adjusted. What is the exact trace of the problem? Do you have a minimal test project you

NPanday ArtifactTypes should get externalized

2011-01-07 Thread Henning Gross
Hi! I need to build a special type of project. Namely wsp files. I have created a lifecycle and an ArtifactHandler for wsp files. Npanday will exit giving an error "unrecognized artifact type". I tracked it down in the sources and as far as I see it, artifact types have to be in dotnet-core

NPanday ArtifactTypes should get externalized

2011-01-07 Thread Henning Gross
Hi! I need to build a special type of project. Namely wsp files. I have created a lifecycle and an ArtifactHandler for wsp files. Npanday will exit giving an error "unrecognized artifact type". I tracked it down in the sources and as far as I see it, artifact types have to be in dotnet-core