[jira] Updated: (NPANDAY-332) nunit-console results in failure even though when you run nunit-ui there are no failures
[ https://issues.apache.org/jira/browse/NPANDAY-332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Ocaba updated NPANDAY-332: -- Priority: Minor (was: Major) > nunit-console results in failure even though when you run nunit-ui there are > no failures > - > > Key: NPANDAY-332 > URL: https://issues.apache.org/jira/browse/NPANDAY-332 > Project: NPanday > Issue Type: Bug >Affects Versions: 2.0 >Reporter: Joe Ocaba >Assignee: Joe Ocaba >Priority: Minor > Fix For: 2.0 > > > Unhandled Exception: > System.ArgumentException: Requested value '2.0.50727' was not found. >at System.Enum.Parse(Type enumType, String value, Boolean ignoreCase) >at NUnit.Core.RuntimeFramework.Parse(String s) >at NUnit.ConsoleRunner.ConsoleUi.MakeTestPackage(ConsoleOptions options) >at NUnit.ConsoleRunner.ConsoleUi.Execute(ConsoleOptions options) >at NUnit.ConsoleRunner.Runner.Main(String[] args) > [INFO] > > [ERROR] BUILD FAILURE > [INFO] > > [INFO] NPANDAY-1100-007: There are test failures. > NPANDAY-040-001: Could not execute: Command = CMD.EXE /X /C nunit-console > C:\Projects\apache-npanday-incubator\trunk\dotnet\assemblies\NPanday.Model.Settings\target/test-assemblies\NPanday.Model.Settings-test.dll > > /xml:C:\Projects\apache-npanday-incubator\trunk\dotnet\assemblies\NPanday.Model.Setting > s\target\nunit-reports\TEST-NPanday.Model.Settings-1.2.2-incubating-SNAPSHOT.xml > > /output:C:\Projects\apache-npanday-incubator\trunk\dotnet\assemblies\NPanday.Model.Settings\target\nunit-reports\TEST-NPanday.Model.Settings-1.2.2-incubating-SNAPSHOT-RESULTS.txt > /err:C:\Projects\apache-npanday-incubato > r\trunk\dotnet\assemblies\NPanday.Model.Settings\target\nunit-reports\TEST-NPanday.Model.Settings-1.2.2-incubating-SNAPSHOT-ERROR.txt > /labels /framework:2.0.50727, Result = -100 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (NPANDAY-231) Remove RDF repository and model
[ https://issues.apache.org/jira/browse/NPANDAY-231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Ocaba updated NPANDAY-231: -- Fix Version/s: (was: 2.0) 2.x Bumped to 2.x since it was discussed in the mailing list that we prioritize a release soon and we will include this after 2.0 > Remove RDF repository and model > --- > > Key: NPANDAY-231 > URL: https://issues.apache.org/jira/browse/NPANDAY-231 > Project: NPanday > Issue Type: Bug > Components: Maven Plugins >Reporter: Brett Porter >Priority: Critical > Fix For: 2.x > > > This will be a significant change to the way NPanday works internally, but > should have no external effect. We desire to have it more closely work with > Maven's dependency resolution, as the RDF adds no value and produces a number > of confusing results and error messages. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (NPANDAY-314) Adding a Maven artifact from VS plugin generates NPANDAY-180-017 error
[ https://issues.apache.org/jira/browse/NPANDAY-314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Ocaba updated NPANDAY-314: -- Fix Version/s: (was: 2.0) 2.x > Adding a Maven artifact from VS plugin generates NPANDAY-180-017 error > -- > > Key: NPANDAY-314 > URL: https://issues.apache.org/jira/browse/NPANDAY-314 > Project: NPanday > Issue Type: Bug >Affects Versions: 2.0 >Reporter: correc00 >Assignee: Joe Ocaba >Priority: Minor > Fix For: 2.x > > > When adding a Maven artifact from the VS Plugin the dependency entry in the > pom file cannot be found, the following example illustrates the problem: > The entry below is inserted into the POM when the artifact is added through > the VS plugin > > Solution1 > ClassLibrary1 > 1.0-SNAPSHOT > dotnet-library > > The correct entry required for mvn compile and install requires a "." before > the group Id: > > .Solution1 > ClassLibrary1 > 1.0-SNAPSHOT > dotnet-library > > See attached gif for the actual error. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (NPANDAY-298) 'npanday.plugin:maven-compile-plugin' does not exist or no valid version
[ https://issues.apache.org/jira/browse/NPANDAY-298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Ocaba updated NPANDAY-298: -- Fix Version/s: (was: 2.0) 2.x > 'npanday.plugin:maven-compile-plugin' does not exist or no valid version > > > Key: NPANDAY-298 > URL: https://issues.apache.org/jira/browse/NPANDAY-298 > Project: NPanday > Issue Type: Bug > Components: Maven Plugins >Reporter: asario >Priority: Minor > Fix For: 2.x > > > Hi, I'm very new to NPanday and I have this issue with version 1.1 and also > with the new fresh 1.2. I used the msi installer and checked all path > variables. The installation looks good everythings looks in place for me. But > I'm not be able to run successfully a generated pom. After generating pom for > the default applicaion from Visual Studio 'WindowsFormsApplication1' (simple > seelct new project 'Windows Form Application') I try to compile the project > and receive following build error: 'The plugin > 'npanday.plugin:maven-compile-plugin' does not exist or no valid version > could be found'. > When take a look in the project pom, i see in scetion build - plugins the > plugin maven-compile-plugin without a version tag. If I add a version tag > 1.2 then the next plugin is not found: > maven-resgen-plugin. If I add the version tag also for the > maven-resgen-plugin then the build stop with 'The plugin > 'npanday.plugin:maven-resolver-plugin' does not exist or no valid version > could be found'. This plugin is not added automaticly during the > installation. When i add all needed plugins in the pom the build work (see > attachment). > Do I have add the NPanday plugins manually in all poms in my project? -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (NPANDAY-293) AddIn file created by installer differs from maven-vsinstaller-plugin
[ https://issues.apache.org/jira/browse/NPANDAY-293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Ocaba updated NPANDAY-293: -- Fix Version/s: (was: 2.0) 2.x > AddIn file created by installer differs from maven-vsinstaller-plugin > - > > Key: NPANDAY-293 > URL: https://issues.apache.org/jira/browse/NPANDAY-293 > Project: NPanday > Issue Type: Bug >Reporter: Brett Porter >Priority: Minor > Fix For: 2.x > > > The About box is empty, and the version not displayed, when using the MSI to > install NPanday. This is because the .AddIn file generated in > ~/Documents/Visual Studio 200x/AddIns is different and does not contain the > About Box info and the same description tag. > It would be good if the AddIn got the console version from the assembly > version of the AddIn instead of parsing the description. I'm not sure if > there is an alternative for the About box that would make it available inside > the AddIn DLL instead - maybe as a resource? > If not, then the MSI WiX script generator needs to be changed to create an > identical AddIn file with the additional information. We should also add a > comment or automated way to DRY the info for the AddIn template. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (NPANDAY-290) Improve console output for integration tests
[ https://issues.apache.org/jira/browse/NPANDAY-290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Ocaba updated NPANDAY-290: -- Fix Version/s: (was: 2.0) 2.x > Improve console output for integration tests > > > Key: NPANDAY-290 > URL: https://issues.apache.org/jira/browse/NPANDAY-290 > Project: NPanday > Issue Type: Bug > Components: Maven Plugins >Reporter: Lars Corneliussen >Priority: Minor > Fix For: 2.x > > > Seems like some tests don't do a line feed: > 11695MsBuildCopyReferences(testMsBuildCopyReferences)..11637MsBuildErrorHandling(testMsBuildErrorsHandled)..9903ResGenWithErrorInFileName(testResGenWithErrorInFileName).. > Ok > And sometimes they say "OK" and are later listed as "FAILED". -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (NPANDAY-284) npanday breaks if localRepository is not default
[ https://issues.apache.org/jira/browse/NPANDAY-284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Ocaba updated NPANDAY-284: -- Fix Version/s: (was: 2.0) 2.x > npanday breaks if localRepository is not default > > > Key: NPANDAY-284 > URL: https://issues.apache.org/jira/browse/NPANDAY-284 > Project: NPanday > Issue Type: Bug > Components: Maven Plugins >Reporter: supkichen >Priority: Minor > Fix For: 2.x > > > In several places in the code, ~/.m2/* is hard-coded as the parent of the > maven repository directory. If it isn't, then you end up with two uac > directories, which causes problems. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (NPANDAY-113) Documentation for each Plugin
[ https://issues.apache.org/jira/browse/NPANDAY-113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Ocaba updated NPANDAY-113: -- Fix Version/s: (was: 2.0) 2.x > Documentation for each Plugin > - > > Key: NPANDAY-113 > URL: https://issues.apache.org/jira/browse/NPANDAY-113 > Project: NPanday > Issue Type: Bug > Components: Reference and Documentations >Reporter: Joe Ocaba >Priority: Minor > Fix For: 2.x > > > Very similar to how maven does it. located here > http://maven.apache.org/plugins/maven-deploy-plugin/ -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (NPANDAY-279) Migrate NPanday's dotnet pom's to "dotnet-*" types
[ https://issues.apache.org/jira/browse/NPANDAY-279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Ocaba updated NPANDAY-279: -- Fix Version/s: (was: 2.0) 2.x > Migrate NPanday's dotnet pom's to "dotnet-*" types > -- > > Key: NPANDAY-279 > URL: https://issues.apache.org/jira/browse/NPANDAY-279 > Project: NPanday > Issue Type: Bug > Components: Maven Plugins >Reporter: Lars Corneliussen >Priority: Minor > Fix For: 2.x > > > In NPanday 1.2 the "old" types have been deprecated, but are still supported. > The libs and netplugins that in NPanday itself still use the old types as > "netplugin", "executable" and "library". We should migrate all > packaging-types of the poms, and also all types on dependencies to the new > types. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (NPANDAY-347) compile fails on unix if sources in subfolder
[ https://issues.apache.org/jira/browse/NPANDAY-347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Ocaba updated NPANDAY-347: -- Fix Version/s: 2.0 > compile fails on unix if sources in subfolder > - > > Key: NPANDAY-347 > URL: https://issues.apache.org/jira/browse/NPANDAY-347 > Project: NPanday > Issue Type: Bug >Affects Versions: 1.2.1 > Environment: linux >Reporter: Luca Di Stefano >Priority: Critical > Fix For: 2.0 > > Attachments: dotnet-executable_linuxpath-1.patch > > > if the project contains source files in subfolder, the compiler plugin fails > to copy temporary files because is supposed the path separator is a backslash -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (NPANDAY-337) NPanday unusable under linux
[ https://issues.apache.org/jira/browse/NPANDAY-337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Ocaba updated NPANDAY-337: -- Fix Version/s: 2.0 > NPanday unusable under linux > > > Key: NPANDAY-337 > URL: https://issues.apache.org/jira/browse/NPANDAY-337 > Project: NPanday > Issue Type: Bug > Components: Maven Plugins >Affects Versions: 1.2.1 > Environment: Apache Maven 2.2.1 (rdebian-4) > Java version: 1.6.0_22 > OS name: "linux" version: "2.6.35-22-generic" arch: "amd64" Family: "unix" >Reporter: Vladimir Tsanev >Priority: Critical > Fix For: 2.0 > > Attachments: dotnet-executable.patch > > > Hi, I want integrate npanday in our build process but I have problems using > it under linux. The problems seems to be in the dotneet-executable component > which tries to do some strange escaping and finally fails since the Runtime > implementation parses the command using StringTokenizer which does not > repects any escaping when splititng arguments. so > /bin/sh -c "gmcs @/path/to/my/reposnsefile.rsp" > is actuallly splitted into this four parameters: > /bin/sh > -c > "gmcs > @/path/to/my/reposnsefile.rsp" > Which cannot be interpreted by the shell. > Probably you should leave the plexus commandline shell to take care of > escapeing. > I did not tried this on windows yet, but for linux I provide a patch that > works for me, at least to compile my modules. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
