[ https://issues.apache.org/jira/browse/NPANDAY-371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Khai Do updated NPANDAY-371: ---------------------------- Attachment: file-list.log the tjproj.dll in the test-assemblies folder looks correct (view attached file list), I assume that's why the tests worked. > npanday install phase creates a zero byte library > ------------------------------------------------- > > Key: NPANDAY-371 > URL: https://issues.apache.org/jira/browse/NPANDAY-371 > Project: NPanday > Issue Type: Bug > Components: Maven Plugins > Affects Versions: 1.2.1, 1.3-incubating > Environment: Apache Maven 2.2.1 (r801777; 2009-08-06 12:16:01-0700) > Java version: 1.6.0_22 > Java home: C:\Program Files\Java\jdk1.6.0_22\jre > Default locale: en_US, platform encoding: Cp1252 > OS name: "windows xp" version: "5.1" arch: "x86" Family: "windows" > Reporter: Khai Do > Attachments: console.log, file-list.log, pom.xml > > > I'm having a problem with NPanday. I created a simple C sharp project using > the npanday archetype. I am able to build it without any failures. The > problem is that when I run install phase it spits out a bad library file, the > the output > dll is zero bytes. It also gets installed to the local repository as a 0 > byte file. However when I execute the compile, test, or package phases the > output dll file is good, it's not empty and it has all the version info in > it. I do run a clean before every build. > Here's some additional info. I have tried npanday ver 1.2.1, > 1.2.2-incubating,and 1.3-incubating. I got the same result from all three. > I'm also using maven ver 2.2.1. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira