[
https://issues.apache.org/jira/browse/NPANDAY-371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brett Porter resolved NPANDAY-371.
----------------------------------
Resolution: Cannot Reproduce
Assignee: Brett Porter
Unable to reproduce this issue - and realise it is still very old. If anyone
spots it again with a more recent version, please reopen.
I did look at the differences in the code between the install plugin in 1.2.1
and 1.3 - the only change was the addition of one logging line, so it seems the
cause was elsewhere.
> 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.4-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
> Assignee: Brett Porter
> Fix For: 1.5.0-incubating
>
> Attachments: console.log, file-list.log, pom-bad.xml, pom-good.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 was sent by Atlassian JIRA
(v6.2#6252)
