[jira] Commented: (NPANDAY-316) Trying to import WPF-project on 64-bit system (VS 2008) throws FileLoadException
[ https://issues.apache.org/jira/browse/NPANDAY-316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12918873#action_12918873 ] Adelita L. Padilla commented on NPANDAY-316: Hi, I was able to replicate the FileLoadException when running importing VS2010 wpf projects on a 64bit machine. I've applied your fix that you've attached here - http://npanday.codeplex.com/workitem/13824 in the branch created for VS2010 support (https://svn.apache.org/repos/asf/incubator/npanday/branches/npanday-vs2010-support/) Thanks! Trying to import WPF-project on 64-bit system (VS 2008) throws FileLoadException Key: NPANDAY-316 URL: https://issues.apache.org/jira/browse/NPANDAY-316 Project: NPanday Issue Type: Bug Reporter: artemfedorenko Priority: Minor Fix For: Backlog When trying to import a solution with WPF-project on 64 bit system in Visual Studio 2008 (for other versions also will be the case I think) NPanday throws the following exception: Could not load file or assembly 'PresentationCore, Version=3.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040) at System.Reflection.Assembly._nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity, Assembly locationHint, StackCrawlMark stackMark, Boolean throwOnFileNotFound, Boolean forIntrospection) at System.Reflection.Assembly.nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity, Assembly locationHint, StackCrawlMark stackMark, Boolean throwOnFileNotFound, Boolean forIntrospection) at System.Reflection.Assembly.InternalLoad(AssemblyName assemblyRef, Evidence assemblySecurity, StackCrawlMark stackMark, Boolean forIntrospection) at System.Reflection.Assembly.Load(AssemblyName assemblyRef) at NPanday.ProjectImporter.Converter.Algorithms.AbstractPomConverter.ResolveDependency(Reference reference) at NPanday.ProjectImporter.Converter.Algorithms.AbstractPomConverter.AddProjectReferenceDependency(Reference reference) at NPanday.ProjectImporter.Converter.Algorithms.AbstractPomConverter.AddProjectReferenceDependenciesToList() at NPanday.ProjectImporter.Converter.Algorithms.NormalPomConverter.ConvertProjectToPomModel(Boolean writePom, String scmTag) at NPanday.ProjectImporter.Converter.Algorithms.AbstractPomConverter.ConvertProjectToPomModel(String scmTag) at NPanday.ProjectImporter.Converter.PomConverter.ConvertProjectToPomModel(ProjectDigest projectDigest, String mainPomFile, Model parent, String groupId, Boolean writePom, String scmTag) Fusion log is the following: === Pre-bind state information === LOG: User = **\ LOG: DisplayName = PresentationCore, Version=3.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35, processorArchitecture=AMD64 (Fully-specified) LOG: Appbase = file:///C:/Program Files (x86)/Microsoft Visual Studio 9.0/Common7/IDE/ LOG: Initial PrivatePath = NULL Calling assembly : NPanday.ProjectImporterEngine, Version=0.0.0.0, Culture=neutral, PublicKeyToken=null. === LOG: This bind starts in LoadFrom load context. WRN: Native image will not be probed in LoadFrom context. Native image will only be probed in default load context, like with Assembly.Load(). LOG: Using application configuration file: C:\Program Files (x86)\Microsoft Visual Studio 9.0\Common7\IDE\devenv.exe.Config LOG: Using machine configuration file from C:\Windows\Microsoft.NET\Framework\v2.0.50727\config\machine.config. LOG: Post-policy reference: PresentationCore, Version=3.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35, processorArchitecture=AMD64 ERR: An assembly with different processor architecture is already loaded. As you can see from fusion log NPanday tries to load an assembly with different architecture (AMD64) than the one that was already loaded. The problem here is that PresentationCore.dll (among some other dll) is used by visual studio itself (especially the case for VS 2010 whose UI is based on WPF) so is loaded with VS studio. And visual studio is by nature a 32 bit application. So when NPanday tries to import an app on 64 bit system it 'founds' the 64-bit version of this dll and loads it using FULL assembly name with processorArchitecture causing the the above error. I created a small patch forcing assembly load without processorArchitecture parameter (anyway its architecture is not important for NPanday at the time of import as it is not used in POM). It worked as supposed also on my 64 bit system and imported solution without any problem. -- This message is
[jira] Created: (NPANDAY-329) Support for VS2010 WCF Project
Support for VS2010 WCF Project -- Key: NPANDAY-329 URL: https://issues.apache.org/jira/browse/NPANDAY-329 Project: NPanday Issue Type: New Feature Affects Versions: 2.0 Reporter: Adelita L. Padilla Fix For: 2.0 Import and Compile successfully a VS2010 WCF project. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (NPANDAY-288) Support for VS 2010 and .NET Framework 4.0
[ https://issues.apache.org/jira/browse/NPANDAY-288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adelita L. Padilla resolved NPANDAY-288. Resolution: Fixed Support for VS 2010 and .NET Framework 4.0 -- Key: NPANDAY-288 URL: https://issues.apache.org/jira/browse/NPANDAY-288 Project: NPanday Issue Type: New Feature Affects Versions: 2.0 Reporter: Lars Corneliussen Assignee: Adelita L. Padilla Fix For: 2.0 VS 2010 and .NET Framework 4.0 has shipped a while ago. We also have a patch in the queue that does some of the work: * 6036 by crimmc, http://npanday.codeplex.com/Project/Download/FileDownload.aspx?DownloadId=124562 blockquote Here are the changes, this release holds: 1. Allow to work with .NET Framework 4.0 gac files. Added (gac_msil4) archive type; 2. Allow to use embeded resources when building DLLs (added for NHibernate); 3. Allow to compile ASP.NET projects with dependencies from 4.0 gac files; 4. Alow to run NUnit tests developed with .NET Framework 4.0; 5. Allow to run NPanday on Windows 7 systems; /blockquote -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (NPANDAY-328) Support for VS2010 WPF Project
[ https://issues.apache.org/jira/browse/NPANDAY-328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12920496#action_12920496 ] Adelita L. Padilla commented on NPANDAY-328: r1022057 - added checking on importing projects (VS2010) on a 64-bit machine (correct the path of includeSources ) Support for VS2010 WPF Project -- Key: NPANDAY-328 URL: https://issues.apache.org/jira/browse/NPANDAY-328 Project: NPanday Issue Type: New Feature Affects Versions: 2.0 Reporter: Adelita L. Padilla Fix For: 2.0 Import and compile successfully a VS 2010 WPF project. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (NPANDAY-328) Support for VS2010 WPF Project
[ https://issues.apache.org/jira/browse/NPANDAY-328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12921673#action_12921673 ] Adelita L. Padilla commented on NPANDAY-328: Add the ff paths to your Path Env Var: C:\Program Files (x86)\Microsoft SDKs\Windows\v7.0A\bin\NETFX 4.0 Tools;C:\Windows\Microsoft.NET\Framework\v4.0.30319; Support for VS2010 WPF Project -- Key: NPANDAY-328 URL: https://issues.apache.org/jira/browse/NPANDAY-328 Project: NPanday Issue Type: New Feature Affects Versions: 2.0 Reporter: Adelita L. Padilla Fix For: 2.0 Import and compile successfully a VS 2010 WPF project. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Issue Comment Edited: (NPANDAY-329) Support for VS2010 WCF Project
[ https://issues.apache.org/jira/browse/NPANDAY-329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12921668#action_12921668 ] Adelita L. Padilla edited comment on NPANDAY-329 at 10/16/10 6:38 AM: -- Fix with the changes committed for NPANDAY-328. Add the ff paths to your Path Env Var: C:\Program Files (x86)\Microsoft SDKs\Windows\v7.0A\bin\NETFX 4.0 Tools;C:\Windows\Microsoft.NET\Framework\v4.0.30319; was (Author: apadilla): Fix with the changes committed for NPANDAY-328. Support for VS2010 WCF Project -- Key: NPANDAY-329 URL: https://issues.apache.org/jira/browse/NPANDAY-329 Project: NPanday Issue Type: New Feature Affects Versions: 2.0 Reporter: Adelita L. Padilla Fix For: 2.0 Import and Compile successfully a VS2010 WCF project. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (NPANDAY-330) Support for VS2010 MVC Project
[ https://issues.apache.org/jira/browse/NPANDAY-330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adelita L. Padilla resolved NPANDAY-330. Resolution: Fixed merged to trunk in r1023237 Support for VS2010 MVC Project -- Key: NPANDAY-330 URL: https://issues.apache.org/jira/browse/NPANDAY-330 Project: NPanday Issue Type: New Feature Affects Versions: 2.0 Reporter: Adelita L. Padilla Fix For: 2.0 Import and Compile VS2010 MVC project -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Issue Comment Edited: (NPANDAY-328) Support for VS2010 WPF Project
[ https://issues.apache.org/jira/browse/NPANDAY-328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12921664#action_12921664 ] Adelita L. Padilla edited comment on NPANDAY-328 at 10/16/10 6:39 AM: -- Hi Artem! Thanks for you patch. I've applied it in branch and it works fine. I am now able to build successfully a WPF project. I also added the ff paths in my Path Env Var: C:\Program Files (x86)\Microsoft SDKs\Windows\v7.0A\bin\NETFX 4.0 Tools;C:\Windows\Microsoft.NET\Framework\v4.0.30319; was (Author: apadilla): Hi Artem! Thanks for you patch. I've applied it in branch and it works fine. I am now able to build successfully a WPF project. Support for VS2010 WPF Project -- Key: NPANDAY-328 URL: https://issues.apache.org/jira/browse/NPANDAY-328 Project: NPanday Issue Type: New Feature Affects Versions: 2.0 Reporter: Adelita L. Padilla Fix For: 2.0 Import and compile successfully a VS 2010 WPF project. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (NPANDAY-336) Add Integration Tests for VS 2010 supported projects (WPF, WCF and MVC)
[ https://issues.apache.org/jira/browse/NPANDAY-336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12927336#action_12927336 ] Adelita L. Padilla commented on NPANDAY-336: added ITs for WCF, WPF and MVC Projects in npanday-its/trunk (r1029973) Add Integration Tests for VS 2010 supported projects (WPF, WCF and MVC) --- Key: NPANDAY-336 URL: https://issues.apache.org/jira/browse/NPANDAY-336 Project: NPanday Issue Type: Task Affects Versions: 2.0 Reporter: Adelita L. Padilla Assignee: Adelita L. Padilla Fix For: 2.0 Add integration tests for VS 2010 supported projects (WPF, WCF and MVC) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (NPANDAY-336) Add Integration Tests for VS 2010 supported projects (WPF, WCF and MVC)
[ https://issues.apache.org/jira/browse/NPANDAY-336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adelita L. Padilla resolved NPANDAY-336. Resolution: Fixed Add Integration Tests for VS 2010 supported projects (WPF, WCF and MVC) --- Key: NPANDAY-336 URL: https://issues.apache.org/jira/browse/NPANDAY-336 Project: NPanday Issue Type: Task Affects Versions: 2.0 Reporter: Adelita L. Padilla Assignee: Adelita L. Padilla Fix For: 2.0 Add integration tests for VS 2010 supported projects (WPF, WCF and MVC) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (NPANDAY-348) Import Error when importing WPF projects in VS 2010 on a 64-bit system
[ https://issues.apache.org/jira/browse/NPANDAY-348?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12930994#action_12930994 ] Adelita L. Padilla commented on NPANDAY-348: Hi Marecor, I was able to replicate this on both trunk and branch for VS 2010 support. However when i place this path: C:\Program Files (x86)\Microsoft SDKs\Windows\v7.0A\bin\NETFX 4.0 Tools; before the other SDKs, it works fine. Can you verify this on your end? Thanks! Import Error when importing WPF projects in VS 2010 on a 64-bit system -- Key: NPANDAY-348 URL: https://issues.apache.org/jira/browse/NPANDAY-348 Project: NPanday Issue Type: Bug Components: Project Importer Environment: npanday-branches\npanday-vs2010-support Windows 7 (64 bit) Visual Studio 2010 Reporter: Marecor M Baclay Fix For: 2.0 Attachments: ImportError.png NPanday Import Error message box will appear after clicking Generate POM with WPF projects in VS 2010. Will attach screen shot after this. Thanks! -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (NPANDAY-348) Import Error when importing WPF projects in VS 2010 on a 64-bit system
[ https://issues.apache.org/jira/browse/NPANDAY-348?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adelita L. Padilla reassigned NPANDAY-348: -- Assignee: Adelita L. Padilla Import Error when importing WPF projects in VS 2010 on a 64-bit system -- Key: NPANDAY-348 URL: https://issues.apache.org/jira/browse/NPANDAY-348 Project: NPanday Issue Type: Bug Components: Project Importer Environment: npanday-branches\npanday-vs2010-support Windows 7 (64 bit) Visual Studio 2010 Reporter: Marecor M Baclay Assignee: Adelita L. Padilla Fix For: 2.0 Attachments: ImportError.png NPanday Import Error message box will appear after clicking Generate POM with WPF projects in VS 2010. Will attach screen shot after this. Thanks! -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (NPANDAY-335) NPanday on Visual Studio only starts on Debug Mode
[ https://issues.apache.org/jira/browse/NPANDAY-335?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adelita L. Padilla reassigned NPANDAY-335: -- Assignee: Adelita L. Padilla (was: Joe Ocaba) NPanday on Visual Studio only starts on Debug Mode -- Key: NPANDAY-335 URL: https://issues.apache.org/jira/browse/NPANDAY-335 Project: NPanday Issue Type: Bug Affects Versions: 2.0 Reporter: Joe Ocaba Assignee: Adelita L. Padilla Fix For: 2.0 Attachments: 335.patch There is a problem with the addin in starting from Visual Studio, but the commands from the command line are working fine. It works fine if you run NPanday under debug mode -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (NPANDAY-341) command execution fails if paths with space
[ https://issues.apache.org/jira/browse/NPANDAY-341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adelita L. Padilla reassigned NPANDAY-341: -- Assignee: Adelita L. Padilla command execution fails if paths with space --- Key: NPANDAY-341 URL: https://issues.apache.org/jira/browse/NPANDAY-341 Project: NPanday Issue Type: Bug Components: Maven Plugins Affects Versions: 1.2.1 Environment: linux mono Reporter: Luca Di Stefano Assignee: Adelita L. Padilla Priority: Minor Attachments: dotnet-executable_whitespaces-1.patch, dotnet-executable_whitespaces-2.patch Original Estimate: 0h Remaining Estimate: 0h I know linux environment is not yet supported. Only for keep trace. Error: Could not find a part of the path /home/luca/Work/egov/trash/dotnet/SharpForgeNPandayTestApp//home/luca/Work/egov/trash/dotnet/SharpForgeNPandayTestApp/SharpForgeNPandayTestApp/SharpForge. [INFO] [ERROR] BUILD ERROR [INFO] [INFO] NPANDAY-1501-002: Unable to execute resgen: Vendor = MONO, frameworkVersion = null Embedded error: NPANDAY-070-000: Execution Path = unknown, Command = [/home/luca/Work/egov/trash/dotnet/SharpForgeNPandayTestApp/SharpForgeNPandayTestApp/SharpForge ListPage Template1.resx, /home/luca/Work/egov/trash/dotnet/SharpForgeNPandayTestApp/SharpForgeNPandayTestApp/target/assembly-resources/resource/it.bz.prov.Apps.SharpForgeNPandayTestApp..SharpForge ListPage Template1.resources] NPANDAY-040-001: Could not execute: Command = resgen /home/luca/Work/egov/trash/dotnet/SharpForgeNPandayTestApp/SharpForgeNPandayTestApp/SharpForge ListPage Template1.resx /home/luca/Work/egov/trash/dotnet/SharpForgeNPandayTestApp/SharpForgeNPandayTestApp/target/assembly-resources/resource/it.bz.prov.Apps.SharpForgeNPandayTestApp..SharpForge ListPage Template1.resources, Result = 1 [INFO] [INFO] Trace org.apache.maven.lifecycle.LifecycleExecutionException: NPANDAY-1501-002: Unable to execute resgen: Vendor = MONO, frameworkVersion = null at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:719) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138) at org.apache.maven.cli.MavenCli.main(MavenCli.java:362) at org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:616) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Caused by: org.apache.maven.plugin.MojoExecutionException: NPANDAY-1501-002: Unable to execute resgen: Vendor = MONO, frameworkVersion = null at npanday.plugin.resgen.ExistingResxGenerator.execute(ExistingResxGenerator.java:594) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694) ... 17 more Caused by: npanday.executable.ExecutionException: NPANDAY-070-000: Execution Path = unknown, Command = [/home/luca/Work/egov/trash/dotnet/SharpForgeNPandayTestApp/SharpForgeNPandayTestApp/SharpForge ListPage Template1.resx, /home/luca/Work/egov/trash/dotnet/SharpForgeNPandayTestApp/SharpForgeNPandayTestApp/target/assembly-resources/resource/it.bz.prov.Apps.SharpForgeNPandayTestApp..SharpForge ListPage Template1.resources] at
[jira] Commented: (NPANDAY-337) NPanday unusable under linux
[ https://issues.apache.org/jira/browse/NPANDAY-337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12932861#action_12932861 ] Adelita L. Padilla commented on NPANDAY-337: Hi, I applied your patch but when building projects in Windows, I got the same error you have when building in linux. I've merged your patch with the patch attached in NPANDAY-341, did some modifications and it works fine in Windows (r1035948). Can you try this on your end? Thanks! 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 Assignee: Adelita L. Padilla 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.
[jira] Commented: (NPANDAY-341) command execution fails if paths with space
[ https://issues.apache.org/jira/browse/NPANDAY-341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12933315#action_12933315 ] Adelita L. Padilla commented on NPANDAY-341: Hi Luca, I've applied the changes you mentioned and it worked fine on my end (Windows). Can you try this on your end as well? I've attached the patch. Thanks! command execution fails if paths with space --- Key: NPANDAY-341 URL: https://issues.apache.org/jira/browse/NPANDAY-341 Project: NPanday Issue Type: Bug Components: Maven Plugins Affects Versions: 1.2.1 Environment: linux mono Reporter: Luca Di Stefano Assignee: Adelita L. Padilla Priority: Minor Attachments: 341.patch, dotnet-executable_whitespaces-1.patch, dotnet-executable_whitespaces-2.patch, NPANDAY-341.zip Original Estimate: 0h Remaining Estimate: 0h I know linux environment is not yet supported. Only for keep trace. Error: Could not find a part of the path /home/luca/Work/egov/trash/dotnet/SharpForgeNPandayTestApp//home/luca/Work/egov/trash/dotnet/SharpForgeNPandayTestApp/SharpForgeNPandayTestApp/SharpForge. [INFO] [ERROR] BUILD ERROR [INFO] [INFO] NPANDAY-1501-002: Unable to execute resgen: Vendor = MONO, frameworkVersion = null Embedded error: NPANDAY-070-000: Execution Path = unknown, Command = [/home/luca/Work/egov/trash/dotnet/SharpForgeNPandayTestApp/SharpForgeNPandayTestApp/SharpForge ListPage Template1.resx, /home/luca/Work/egov/trash/dotnet/SharpForgeNPandayTestApp/SharpForgeNPandayTestApp/target/assembly-resources/resource/it.bz.prov.Apps.SharpForgeNPandayTestApp..SharpForge ListPage Template1.resources] NPANDAY-040-001: Could not execute: Command = resgen /home/luca/Work/egov/trash/dotnet/SharpForgeNPandayTestApp/SharpForgeNPandayTestApp/SharpForge ListPage Template1.resx /home/luca/Work/egov/trash/dotnet/SharpForgeNPandayTestApp/SharpForgeNPandayTestApp/target/assembly-resources/resource/it.bz.prov.Apps.SharpForgeNPandayTestApp..SharpForge ListPage Template1.resources, Result = 1 [INFO] [INFO] Trace org.apache.maven.lifecycle.LifecycleExecutionException: NPANDAY-1501-002: Unable to execute resgen: Vendor = MONO, frameworkVersion = null at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:719) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138) at org.apache.maven.cli.MavenCli.main(MavenCli.java:362) at org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:616) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Caused by: org.apache.maven.plugin.MojoExecutionException: NPANDAY-1501-002: Unable to execute resgen: Vendor = MONO, frameworkVersion = null at npanday.plugin.resgen.ExistingResxGenerator.execute(ExistingResxGenerator.java:594) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694) ... 17 more Caused by: npanday.executable.ExecutionException: NPANDAY-070-000: Execution Path = unknown, Command = [/home/luca/Work/egov/trash/dotnet/SharpForgeNPandayTestApp/SharpForgeNPandayTestApp/SharpForge ListPage Template1.resx,
[jira] Work started: (NPANDAY-348) Import Error when importing WPF projects in VS 2010 on a 64-bit system
[ https://issues.apache.org/jira/browse/NPANDAY-348?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on NPANDAY-348 started by Adelita L. Padilla. Import Error when importing WPF projects in VS 2010 on a 64-bit system -- Key: NPANDAY-348 URL: https://issues.apache.org/jira/browse/NPANDAY-348 Project: NPanday Issue Type: Bug Components: Project Importer Environment: npanday-branches\npanday-vs2010-support Windows 7 (64 bit) Visual Studio 2010 Reporter: Marecor M Baclay Assignee: Adelita L. Padilla Fix For: 2.0 Attachments: ImportError.png NPanday Import Error message box will appear after clicking Generate POM with WPF projects in VS 2010. Will attach screen shot after this. Thanks! -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (NPANDAY-316) Trying to import WPF-project on 64-bit system (VS 2008) throws FileLoadException
[ https://issues.apache.org/jira/browse/NPANDAY-316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adelita L. Padilla reassigned NPANDAY-316: -- Assignee: Adelita L. Padilla Trying to import WPF-project on 64-bit system (VS 2008) throws FileLoadException Key: NPANDAY-316 URL: https://issues.apache.org/jira/browse/NPANDAY-316 Project: NPanday Issue Type: Bug Reporter: artemfedorenko Assignee: Adelita L. Padilla Priority: Minor Fix For: 2.0 When trying to import a solution with WPF-project on 64 bit system in Visual Studio 2008 (for other versions also will be the case I think) NPanday throws the following exception: Could not load file or assembly 'PresentationCore, Version=3.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040) at System.Reflection.Assembly._nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity, Assembly locationHint, StackCrawlMark stackMark, Boolean throwOnFileNotFound, Boolean forIntrospection) at System.Reflection.Assembly.nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity, Assembly locationHint, StackCrawlMark stackMark, Boolean throwOnFileNotFound, Boolean forIntrospection) at System.Reflection.Assembly.InternalLoad(AssemblyName assemblyRef, Evidence assemblySecurity, StackCrawlMark stackMark, Boolean forIntrospection) at System.Reflection.Assembly.Load(AssemblyName assemblyRef) at NPanday.ProjectImporter.Converter.Algorithms.AbstractPomConverter.ResolveDependency(Reference reference) at NPanday.ProjectImporter.Converter.Algorithms.AbstractPomConverter.AddProjectReferenceDependency(Reference reference) at NPanday.ProjectImporter.Converter.Algorithms.AbstractPomConverter.AddProjectReferenceDependenciesToList() at NPanday.ProjectImporter.Converter.Algorithms.NormalPomConverter.ConvertProjectToPomModel(Boolean writePom, String scmTag) at NPanday.ProjectImporter.Converter.Algorithms.AbstractPomConverter.ConvertProjectToPomModel(String scmTag) at NPanday.ProjectImporter.Converter.PomConverter.ConvertProjectToPomModel(ProjectDigest projectDigest, String mainPomFile, Model parent, String groupId, Boolean writePom, String scmTag) Fusion log is the following: === Pre-bind state information === LOG: User = **\ LOG: DisplayName = PresentationCore, Version=3.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35, processorArchitecture=AMD64 (Fully-specified) LOG: Appbase = file:///C:/Program Files (x86)/Microsoft Visual Studio 9.0/Common7/IDE/ LOG: Initial PrivatePath = NULL Calling assembly : NPanday.ProjectImporterEngine, Version=0.0.0.0, Culture=neutral, PublicKeyToken=null. === LOG: This bind starts in LoadFrom load context. WRN: Native image will not be probed in LoadFrom context. Native image will only be probed in default load context, like with Assembly.Load(). LOG: Using application configuration file: C:\Program Files (x86)\Microsoft Visual Studio 9.0\Common7\IDE\devenv.exe.Config LOG: Using machine configuration file from C:\Windows\Microsoft.NET\Framework\v2.0.50727\config\machine.config. LOG: Post-policy reference: PresentationCore, Version=3.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35, processorArchitecture=AMD64 ERR: An assembly with different processor architecture is already loaded. As you can see from fusion log NPanday tries to load an assembly with different architecture (AMD64) than the one that was already loaded. The problem here is that PresentationCore.dll (among some other dll) is used by visual studio itself (especially the case for VS 2010 whose UI is based on WPF) so is loaded with VS studio. And visual studio is by nature a 32 bit application. So when NPanday tries to import an app on 64 bit system it 'founds' the 64-bit version of this dll and loads it using FULL assembly name with processorArchitecture causing the the above error. I created a small patch forcing assembly load without processorArchitecture parameter (anyway its architecture is not important for NPanday at the time of import as it is not used in POM). It worked as supposed also on my 64 bit system and imported solution without any problem. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Work started: (NPANDAY-316) Trying to import WPF-project on 64-bit system (VS 2008) throws FileLoadException
[ https://issues.apache.org/jira/browse/NPANDAY-316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on NPANDAY-316 started by Adelita L. Padilla. Trying to import WPF-project on 64-bit system (VS 2008) throws FileLoadException Key: NPANDAY-316 URL: https://issues.apache.org/jira/browse/NPANDAY-316 Project: NPanday Issue Type: Bug Reporter: artemfedorenko Assignee: Adelita L. Padilla Priority: Minor Fix For: 2.0 When trying to import a solution with WPF-project on 64 bit system in Visual Studio 2008 (for other versions also will be the case I think) NPanday throws the following exception: Could not load file or assembly 'PresentationCore, Version=3.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040) at System.Reflection.Assembly._nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity, Assembly locationHint, StackCrawlMark stackMark, Boolean throwOnFileNotFound, Boolean forIntrospection) at System.Reflection.Assembly.nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity, Assembly locationHint, StackCrawlMark stackMark, Boolean throwOnFileNotFound, Boolean forIntrospection) at System.Reflection.Assembly.InternalLoad(AssemblyName assemblyRef, Evidence assemblySecurity, StackCrawlMark stackMark, Boolean forIntrospection) at System.Reflection.Assembly.Load(AssemblyName assemblyRef) at NPanday.ProjectImporter.Converter.Algorithms.AbstractPomConverter.ResolveDependency(Reference reference) at NPanday.ProjectImporter.Converter.Algorithms.AbstractPomConverter.AddProjectReferenceDependency(Reference reference) at NPanday.ProjectImporter.Converter.Algorithms.AbstractPomConverter.AddProjectReferenceDependenciesToList() at NPanday.ProjectImporter.Converter.Algorithms.NormalPomConverter.ConvertProjectToPomModel(Boolean writePom, String scmTag) at NPanday.ProjectImporter.Converter.Algorithms.AbstractPomConverter.ConvertProjectToPomModel(String scmTag) at NPanday.ProjectImporter.Converter.PomConverter.ConvertProjectToPomModel(ProjectDigest projectDigest, String mainPomFile, Model parent, String groupId, Boolean writePom, String scmTag) Fusion log is the following: === Pre-bind state information === LOG: User = **\ LOG: DisplayName = PresentationCore, Version=3.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35, processorArchitecture=AMD64 (Fully-specified) LOG: Appbase = file:///C:/Program Files (x86)/Microsoft Visual Studio 9.0/Common7/IDE/ LOG: Initial PrivatePath = NULL Calling assembly : NPanday.ProjectImporterEngine, Version=0.0.0.0, Culture=neutral, PublicKeyToken=null. === LOG: This bind starts in LoadFrom load context. WRN: Native image will not be probed in LoadFrom context. Native image will only be probed in default load context, like with Assembly.Load(). LOG: Using application configuration file: C:\Program Files (x86)\Microsoft Visual Studio 9.0\Common7\IDE\devenv.exe.Config LOG: Using machine configuration file from C:\Windows\Microsoft.NET\Framework\v2.0.50727\config\machine.config. LOG: Post-policy reference: PresentationCore, Version=3.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35, processorArchitecture=AMD64 ERR: An assembly with different processor architecture is already loaded. As you can see from fusion log NPanday tries to load an assembly with different architecture (AMD64) than the one that was already loaded. The problem here is that PresentationCore.dll (among some other dll) is used by visual studio itself (especially the case for VS 2010 whose UI is based on WPF) so is loaded with VS studio. And visual studio is by nature a 32 bit application. So when NPanday tries to import an app on 64 bit system it 'founds' the 64-bit version of this dll and loads it using FULL assembly name with processorArchitecture causing the the above error. I created a small patch forcing assembly load without processorArchitecture parameter (anyway its architecture is not important for NPanday at the time of import as it is not used in POM). It worked as supposed also on my 64 bit system and imported solution without any problem. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (NPANDAY-339) Npanday.Plugin size 0 in repo
[ https://issues.apache.org/jira/browse/NPANDAY-339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adelita L. Padilla resolved NPANDAY-339. Resolution: Fixed Npanday.Plugin size 0 in repo - Key: NPANDAY-339 URL: https://issues.apache.org/jira/browse/NPANDAY-339 Project: NPanday Issue Type: Bug Components: Repository Affects Versions: 1.2.1 Environment: 1.2.2-incubating Reporter: Luca Di Stefano Fix For: 1.3-incubating This plugin has size 0 in repo, and make impossible to use npanday 1.2.2-incubating Name: NPanday.Plugin-1.2.2-incubating-20101021.032458-5-4b435f4d76e2f0e6.dll Size: 0 Bytes 3K downloaded (NPanday.Plugin-1.2.2-incubating-20101021.032458-5.pom) 27-ott-2010 9.56.43 npanday.dao.impl.ProjectDaoImpl storeProjectAndResolveDependencies INFO: NPANDAY-180-024: resolving pom artifact: npanday.plugin:NPanday.Plugin:pom:1.2.2-incubating-SNAPSHOT 27-ott-2010 9.56.43 npanday.PathUtil getDotNetArtifact AVVERTENZA: NPANDAY-1005-0001: Error copying dependency npanday.plugin:NPanday.Plugin:library:4b435f4d76e2f0e6:1.2.2-incubating-SNAPSHOT:runtime File C:\var\cache \maven\repository\npanday\plugin\NPanday.Plugin\1.2.2-incubating-20101021.032458-5\NPanday.Plugin-1.2.2-incubating-20101021.032458-5-4b435f4d76e2f0e6. dll does not exist 27-ott-2010 9.56.43 npanday.dao.impl.ProjectDaoImpl storeProjectAndResolveDependencies INFO: NPANDAY-180-018: Not found in local repository, now retrieving artifact from wagon:npanday.plugin:NPanday.Plugin:library:4b435f4d76e2f0e6:1.2.2- incubating-SNAPSHOT, Failed Path Check = C:\Documents and Settings\pb00018.WPIT\My Documents\Development\WindowsFormsApplication3\target\NPanday.Plugi n.dll Downloading: https://samson.prov.bz/artifactory/repo//npanday/plugin/NPanday.Plugin/1.2.2-incubating-SNAPSHOT/NPanday.Plugin-1.2.2-incubating-20101021 .032458-5-4b435f4d76e2f0e6.dll 0b downloaded (NPanday.Plugin-1.2.2-incubating-20101021.032458-5-4b435f4d76e2f0e6.dll) [INFO] Unable to find resource 'npanday.plugin:NPanday.Plugin:library:4b435f4d76e2f0e6:1.2.2-incubating-SNAPSHOT' in repository egov-default (https:// samson.prov.bz/artifactory/repo/) 27-ott-2010 9.56.47 npanday.dao.impl.ProjectDaoImpl storeProjectAndResolveDependencies GRAVE: NPANDAY-180-0201: Error resolving artifact. Reason: org.apache.maven.artifact.resolver.ArtifactNotFoundException: Unable to download the artifact from any repository Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=npanday.plugin -DartifactId=NPanday.Plugin -Dversion=1.2.2-incubating-20101021.032458-5 -Dclassifier=4b435f4d76 e2f0e6 -Dpackaging=library -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=npanday.plugin -DartifactId=NPanday.Plugin -Dversion=1.2.2-incubating-20101021.032458-5 -Dclassifier=4b435f4d76e2 f0e6 -Dpackaging=library -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] npanday.plugin:NPanday.Plugin:library:1.2.2-incubating-20101021.032458-5 from the specified remote repositories: central (http://repo1.maven.org/maven2), egov-default (https://samson.prov.bz/artifactory/repo/) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:228) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:90) at npanday.dao.impl.ProjectDaoImpl.storeProjectAndResolveDependencies(ProjectDaoImpl.java:767) at npanday.dao.impl.ProjectDaoImpl.storeProjectAndResolveDependencies(ProjectDaoImpl.java:414) at npanday.artifact.impl.AssemblyResolverImpl.resolveTransitivelyFor(AssemblyResolverImpl.java:131) at npanday.artifact.impl.ArtifactInstallerImpl.resolveAndInstallNetDependenciesForProfile(ArtifactInstallerImpl.java:166) at npanday.plugin.resolver.NetDependencyResolverMojo.execute(NetDependencyResolverMojo.java:163) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348) at
[jira] Work started: (NPANDAY-349) NPanday not building resource files correctly
[ https://issues.apache.org/jira/browse/NPANDAY-349?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on NPANDAY-349 started by Adelita L. Padilla. NPanday not building resource files correctly - Key: NPANDAY-349 URL: https://issues.apache.org/jira/browse/NPANDAY-349 Project: NPanday Issue Type: Bug Components: Maven Plugins Reporter: Adelita L. Padilla Assignee: Adelita L. Padilla Priority: Minor Fix For: 1.3-incubating Steps to replicate: 1. Create a WebApp project 2. Add resource files 3. Build the project (msbuild) Actual Result: A bin directory has been generated. In it are generated folders also for each of the resource files corresponding to the ResourceFiles directory in the webapp. 4. Delete the bin directory and build the project with NPanday Actual Result: The bin directory wasn't generated either in the project directory nor in the target directory. Expected Result: bin folder with the corresponding resources files should be generated in the target directory. There's a workaround for this issue and that is to add the MSBuild plugin snippet in the pom, plugin groupIdnpanday.plugin/groupId artifactIdNPanday.Plugin.Msbuild.JavaBinding/artifactId extensionstrue/extensions executions execution goals goalcompile/goal /goals /execution /executions /plugin As of now, NPanday automatically adds the plugin configuration if it doesn't exists in the pom. This might trigger builds twice. It might be better to look at the resource plugin. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (NPANDAY-349) NPanday not building resource files correctly
[ https://issues.apache.org/jira/browse/NPANDAY-349?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adelita L. Padilla resolved NPANDAY-349. Resolution: Fixed fixed in r1041711 NPanday not building resource files correctly - Key: NPANDAY-349 URL: https://issues.apache.org/jira/browse/NPANDAY-349 Project: NPanday Issue Type: Bug Components: Maven Plugins Reporter: Adelita L. Padilla Assignee: Adelita L. Padilla Priority: Minor Fix For: 1.3-incubating Steps to replicate: 1. Create a WebApp project 2. Add resource files 3. Build the project (msbuild) Actual Result: A bin directory has been generated. In it are generated folders also for each of the resource files corresponding to the ResourceFiles directory in the webapp. 4. Delete the bin directory and build the project with NPanday Actual Result: The bin directory wasn't generated either in the project directory nor in the target directory. Expected Result: bin folder with the corresponding resources files should be generated in the target directory. There's a workaround for this issue and that is to add the MSBuild plugin snippet in the pom, plugin groupIdnpanday.plugin/groupId artifactIdNPanday.Plugin.Msbuild.JavaBinding/artifactId extensionstrue/extensions executions execution goals goalcompile/goal /goals /execution /executions /plugin As of now, NPanday automatically adds the plugin configuration if it doesn't exists in the pom. This might trigger builds twice. It might be better to look at the resource plugin. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Work stopped: (NPANDAY-349) NPanday not building resource files correctly
[ https://issues.apache.org/jira/browse/NPANDAY-349?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on NPANDAY-349 stopped by Adelita L. Padilla. NPanday not building resource files correctly - Key: NPANDAY-349 URL: https://issues.apache.org/jira/browse/NPANDAY-349 Project: NPanday Issue Type: Bug Components: Maven Plugins Reporter: Adelita L. Padilla Assignee: Adelita L. Padilla Priority: Minor Fix For: 1.3-incubating Steps to replicate: 1. Create a WebApp project 2. Add resource files 3. Build the project (msbuild) Actual Result: A bin directory has been generated. In it are generated folders also for each of the resource files corresponding to the ResourceFiles directory in the webapp. 4. Delete the bin directory and build the project with NPanday Actual Result: The bin directory wasn't generated either in the project directory nor in the target directory. Expected Result: bin folder with the corresponding resources files should be generated in the target directory. There's a workaround for this issue and that is to add the MSBuild plugin snippet in the pom, plugin groupIdnpanday.plugin/groupId artifactIdNPanday.Plugin.Msbuild.JavaBinding/artifactId extensionstrue/extensions executions execution goals goalcompile/goal /goals /execution /executions /plugin As of now, NPanday automatically adds the plugin configuration if it doesn't exists in the pom. This might trigger builds twice. It might be better to look at the resource plugin. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (NPANDAY-337) NPanday unusable under linux
[ https://issues.apache.org/jira/browse/NPANDAY-337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adelita L. Padilla resolved NPANDAY-337. Resolution: Fixed 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 Assignee: Adelita L. Padilla Priority: Critical Fix For: 1.3-incubating 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.
[jira] Commented: (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:comment-tabpanelfocusedCommentId=12966484#action_12966484 ] Adelita L. Padilla commented on NPANDAY-298: Hi asario! I don't see any attachments. Can you attach it again? By the way, can you attach your settings.xml too? Thanks! '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.0 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 version1.2/version 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] Resolved: (NPANDAY-341) command execution fails if paths with space
[ https://issues.apache.org/jira/browse/NPANDAY-341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adelita L. Padilla resolved NPANDAY-341. Resolution: Fixed Fixed in r1042532. Thanks! command execution fails if paths with space --- Key: NPANDAY-341 URL: https://issues.apache.org/jira/browse/NPANDAY-341 Project: NPanday Issue Type: Bug Components: Maven Plugins Affects Versions: 1.2.1 Environment: linux mono Reporter: Luca Di Stefano Assignee: Adelita L. Padilla Priority: Minor Fix For: 1.3-incubating Attachments: 341.patch, dotnet-executable_whitespaces-1.patch, dotnet-executable_whitespaces-2.patch, NPANDAY-341.zip Original Estimate: 0h Remaining Estimate: 0h I know linux environment is not yet supported. Only for keep trace. Error: Could not find a part of the path /home/luca/Work/egov/trash/dotnet/SharpForgeNPandayTestApp//home/luca/Work/egov/trash/dotnet/SharpForgeNPandayTestApp/SharpForgeNPandayTestApp/SharpForge. [INFO] [ERROR] BUILD ERROR [INFO] [INFO] NPANDAY-1501-002: Unable to execute resgen: Vendor = MONO, frameworkVersion = null Embedded error: NPANDAY-070-000: Execution Path = unknown, Command = [/home/luca/Work/egov/trash/dotnet/SharpForgeNPandayTestApp/SharpForgeNPandayTestApp/SharpForge ListPage Template1.resx, /home/luca/Work/egov/trash/dotnet/SharpForgeNPandayTestApp/SharpForgeNPandayTestApp/target/assembly-resources/resource/it.bz.prov.Apps.SharpForgeNPandayTestApp..SharpForge ListPage Template1.resources] NPANDAY-040-001: Could not execute: Command = resgen /home/luca/Work/egov/trash/dotnet/SharpForgeNPandayTestApp/SharpForgeNPandayTestApp/SharpForge ListPage Template1.resx /home/luca/Work/egov/trash/dotnet/SharpForgeNPandayTestApp/SharpForgeNPandayTestApp/target/assembly-resources/resource/it.bz.prov.Apps.SharpForgeNPandayTestApp..SharpForge ListPage Template1.resources, Result = 1 [INFO] [INFO] Trace org.apache.maven.lifecycle.LifecycleExecutionException: NPANDAY-1501-002: Unable to execute resgen: Vendor = MONO, frameworkVersion = null at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:719) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138) at org.apache.maven.cli.MavenCli.main(MavenCli.java:362) at org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:616) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Caused by: org.apache.maven.plugin.MojoExecutionException: NPANDAY-1501-002: Unable to execute resgen: Vendor = MONO, frameworkVersion = null at npanday.plugin.resgen.ExistingResxGenerator.execute(ExistingResxGenerator.java:594) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694) ... 17 more Caused by: npanday.executable.ExecutionException: NPANDAY-070-000: Execution Path = unknown, Command = [/home/luca/Work/egov/trash/dotnet/SharpForgeNPandayTestApp/SharpForgeNPandayTestApp/SharpForge ListPage Template1.resx,
[jira] Updated: (NPANDAY-334) Update Integration Tests in relation with the UAC PAB removal enhancements
[ https://issues.apache.org/jira/browse/NPANDAY-334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adelita L. Padilla updated NPANDAY-334: --- Attachment: NPANDAY-334.patch Hi, I've attached a patch that fix some of the failing ITs (based on r1043282). After applying this in my local, I only got 4 failing ITs. Thanks! Update Integration Tests in relation with the UAC PAB removal enhancements Key: NPANDAY-334 URL: https://issues.apache.org/jira/browse/NPANDAY-334 Project: NPanday Issue Type: Task Affects Versions: 1.3-incubating Reporter: Joe Ocaba Assignee: Joe Ocaba Fix For: 1.3-incubating Attachments: NPANDAY-334.patch Currently most of the integration tests are failing because they aren't updated yet with the new merged branches. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (NPANDAY-359) Test Failures on ProjectImporter module
Test Failures on ProjectImporter module --- Key: NPANDAY-359 URL: https://issues.apache.org/jira/browse/NPANDAY-359 Project: NPanday Issue Type: Bug Components: Project Importer Affects Versions: 1.3-incubating Reporter: Adelita L. Padilla Fix For: 1.3-incubating Building NPanday from trunk will result to test failures in ProjectImporter module. As a workaround , I commented the ff line in trunk/dotnet/pom.xml: testSourceDirectorysrc/test/csharp/testSourceDirectory -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (NPANDAY-350) Output Directory is hardcoded to be under target.
[
https://issues.apache.org/jira/browse/NPANDAY-350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12970439#action_12970439
]
Adelita L. Padilla commented on NPANDAY-350:
After adding this line directory in the pom, the output directory would
actually be the one specified in that tag and not target.
Output Directory is hardcoded to be under target.
-
Key: NPANDAY-350
URL: https://issues.apache.org/jira/browse/NPANDAY-350
Project: NPanday
Issue Type: Bug
Affects Versions: 1.3-incubating
Reporter: Joe Ocaba
Assignee: Joe Ocaba
Fix For: 1.3-incubating
The output directory should respect what is set by the POM, so we need to
have to look up the location. Make us backtrack to the mojos, where we have
access to ${project.build.directory}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (NPANDAY-360) Local Repository not displaying correct artifacts from the local repository
[ https://issues.apache.org/jira/browse/NPANDAY-360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adelita L. Padilla reassigned NPANDAY-360: -- Assignee: Adelita L. Padilla Local Repository not displaying correct artifacts from the local repository --- Key: NPANDAY-360 URL: https://issues.apache.org/jira/browse/NPANDAY-360 Project: NPanday Issue Type: Bug Components: Visual Studio Add-in Affects Versions: 1.3-incubating Reporter: Adelita L. Padilla Assignee: Adelita L. Padilla Attachments: addMavenArtifactError.png Steps to reproduce: 1) Open a project 2) Start NPanday 3) Right click on the project and select 'Add Maven Artifact..' Actual Behavior: The artifacts displayed on the 'Local' tab is not correct. (See attached file) Expected Behavior: 'Local' tab should be able to display the correct artifacts from the local repository defined in the settings.xml. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (NPANDAY-360) Local Repository not displaying correct artifacts from the local repository
[ https://issues.apache.org/jira/browse/NPANDAY-360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adelita L. Padilla resolved NPANDAY-360. Resolution: Fixed Fix Version/s: 1.3-incubating Fixed in r 1049437 Local Repository not displaying correct artifacts from the local repository --- Key: NPANDAY-360 URL: https://issues.apache.org/jira/browse/NPANDAY-360 Project: NPanday Issue Type: Bug Components: Visual Studio Add-in Affects Versions: 1.3-incubating Reporter: Adelita L. Padilla Assignee: Adelita L. Padilla Fix For: 1.3-incubating Attachments: addMavenArtifactError.png Steps to reproduce: 1) Open a project 2) Start NPanday 3) Right click on the project and select 'Add Maven Artifact..' Actual Behavior: The artifacts displayed on the 'Local' tab is not correct. (See attached file) Expected Behavior: 'Local' tab should be able to display the correct artifacts from the local repository defined in the settings.xml. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (NPANDAY-357) Add 'deploy' option to 'Current NPanday Project' menu options
[ https://issues.apache.org/jira/browse/NPANDAY-357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12971613#action_12971613 ] Adelita L. Padilla commented on NPANDAY-357: Hi Paul G, We've tried and tested your patch and it works fine. Applied it in r1049474 Thanks! Add 'deploy' option to 'Current NPanday Project' menu options - Key: NPANDAY-357 URL: https://issues.apache.org/jira/browse/NPANDAY-357 Project: NPanday Issue Type: Improvement Components: Visual Studio Add-in Affects Versions: 1.2.1 Environment: Windows Reporter: Paul G Fix For: 1.3-incubating Attachments: NPANDAY-357.patch When working with multiple projects and multiple teams there needs to be an option to deploy new builds out to a remote repository so that other teams can can download the update. Currently the user has to drop out of Visual Studio and run 'mvn deploy' to do this - which is a bit nasty. It's a quick job, took me 3 mins to add the feature to Connect.cs (and it worked!). -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (NPANDAY-357) Add 'deploy' option to 'Current NPanday Project' menu options
[ https://issues.apache.org/jira/browse/NPANDAY-357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adelita L. Padilla resolved NPANDAY-357. Resolution: Fixed Fix Version/s: 1.3-incubating Add 'deploy' option to 'Current NPanday Project' menu options - Key: NPANDAY-357 URL: https://issues.apache.org/jira/browse/NPANDAY-357 Project: NPanday Issue Type: Improvement Components: Visual Studio Add-in Affects Versions: 1.2.1 Environment: Windows Reporter: Paul G Fix For: 1.3-incubating Attachments: NPANDAY-357.patch When working with multiple projects and multiple teams there needs to be an option to deploy new builds out to a remote repository so that other teams can can download the update. Currently the user has to drop out of Visual Studio and run 'mvn deploy' to do this - which is a bit nasty. It's a quick job, took me 3 mins to add the feature to Connect.cs (and it worked!). -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (NPANDAY-239) VS Add-In messes up settings.xml
[ https://issues.apache.org/jira/browse/NPANDAY-239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adelita L. Padilla reassigned NPANDAY-239: -- Assignee: Adelita L. Padilla VS Add-In messes up settings.xml Key: NPANDAY-239 URL: https://issues.apache.org/jira/browse/NPANDAY-239 Project: NPanday Issue Type: Bug Components: Visual Studio Add-in Reporter: Lars Corneliussen Assignee: Adelita L. Padilla Fix For: 1.3-incubating With the fix for [workitem:11837] now the settings.xml is reformatted and all comments are stripped out. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (NPANDAY-333) Dependecy of type 'gac' is not resolved correclty
[ https://issues.apache.org/jira/browse/NPANDAY-333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12973164#action_12973164 ] Adelita L. Padilla commented on NPANDAY-333: Hi Artem, Thanks for your patch. But this is already fixed in r1036072 with Joe's latest revisions. Can you verify if it's working on your end? Thanks! Dependecy of type 'gac' is not resolved correclty - Key: NPANDAY-333 URL: https://issues.apache.org/jira/browse/NPANDAY-333 Project: NPanday Issue Type: Bug Components: Repository Affects Versions: 1.3-incubating Reporter: Artem Fedorenko Fix For: 1.3-incubating Attachments: GACArtifacts.patch In current (revision 1025844) trunk revision of the codebase after merging UAC and PAB removal branch to trunk there is a problem with resolving dependencies from old (.NET 1.1-3.5) GAC - NPnday tries to load them directly from c:\Windows\assembly\. It should be c:\Windows\assembly\GAC (or c:\Windows\assembly\GAC_32, c:\Windows\assembly\GAC_64, c:\Windows\assembly\GAC_MSIL - depending of type). This issue does not concerns dependencies from new (.NET 4.0) GAC. I created a little patch fixing this issue - will attach to this issue -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (NPANDAY-239) VS Add-In messes up settings.xml
[ https://issues.apache.org/jira/browse/NPANDAY-239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adelita L. Padilla updated NPANDAY-239: --- Fix Version/s: (was: Backlog) 1.3-incubating VS Add-In messes up settings.xml Key: NPANDAY-239 URL: https://issues.apache.org/jira/browse/NPANDAY-239 Project: NPanday Issue Type: Bug Components: Visual Studio Add-in Reporter: Lars Corneliussen Assignee: Adelita L. Padilla Fix For: 1.3-incubating With the fix for [workitem:11837] now the settings.xml is reformatted and all comments are stripped out. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (NPANDAY-239) VS Add-In messes up settings.xml
[ https://issues.apache.org/jira/browse/NPANDAY-239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12973165#action_12973165 ] Adelita L. Padilla commented on NPANDAY-239: While investigating on this one, I've encountered this error -- http://npanday.codeplex.com/workitem/11837. VS Add-In messes up settings.xml Key: NPANDAY-239 URL: https://issues.apache.org/jira/browse/NPANDAY-239 Project: NPanday Issue Type: Bug Components: Visual Studio Add-in Reporter: Lars Corneliussen Assignee: Adelita L. Padilla Fix For: 1.3-incubating With the fix for [workitem:11837] now the settings.xml is reformatted and all comments are stripped out. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (NPANDAY-333) Dependecy of type 'gac' is not resolved correclty
[ https://issues.apache.org/jira/browse/NPANDAY-333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adelita L. Padilla resolved NPANDAY-333. Resolution: Fixed Assignee: Adelita L. Padilla Dependecy of type 'gac' is not resolved correclty - Key: NPANDAY-333 URL: https://issues.apache.org/jira/browse/NPANDAY-333 Project: NPanday Issue Type: Bug Components: Repository Affects Versions: 1.3-incubating Reporter: Artem Fedorenko Assignee: Adelita L. Padilla Fix For: 1.3-incubating Attachments: GACArtifacts.patch In current (revision 1025844) trunk revision of the codebase after merging UAC and PAB removal branch to trunk there is a problem with resolving dependencies from old (.NET 1.1-3.5) GAC - NPnday tries to load them directly from c:\Windows\assembly\. It should be c:\Windows\assembly\GAC (or c:\Windows\assembly\GAC_32, c:\Windows\assembly\GAC_64, c:\Windows\assembly\GAC_MSIL - depending of type). This issue does not concerns dependencies from new (.NET 4.0) GAC. I created a little patch fixing this issue - will attach to this issue -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (NPANDAY-239) VS Add-In messes up settings.xml
[ https://issues.apache.org/jira/browse/NPANDAY-239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12973577#action_12973577 ] Adelita L. Padilla commented on NPANDAY-239: added checking in SettingsUtil.cs so that VS will not crash when profiles tag is existing (r1051454) VS Add-In messes up settings.xml Key: NPANDAY-239 URL: https://issues.apache.org/jira/browse/NPANDAY-239 Project: NPanday Issue Type: Bug Components: Visual Studio Add-in Reporter: Lars Corneliussen Assignee: Adelita L. Padilla Fix For: 1.3-incubating With the fix for [workitem:11837] now the settings.xml is reformatted and all comments are stripped out. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (NPANDAY-326) misc. improvements
[ https://issues.apache.org/jira/browse/NPANDAY-326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12977727#action_12977727 ] Adelita L. Padilla commented on NPANDAY-326: Hi Henrik, I've tried and tested your patch and it works fine. I'll apply this in trunk. Thanks! misc. improvements -- Key: NPANDAY-326 URL: https://issues.apache.org/jira/browse/NPANDAY-326 Project: NPanday Issue Type: Improvement Components: Maven Plugins Affects Versions: 1.2.1 Reporter: Henrik Bie Priority: Minor Fix For: 1.3-incubating Attachments: 1.2.1.patch Added @parameter to parameters unsafe and testUnsafe. Added parameters warn, testWarn, nowarn and testNowarn. NPANDAY-068-003: Language is now compilerContext.getCompilerRequirement().getLanguage() instead of compilerContext.getCompilerRequirement().getVendor() -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (NPANDAY-326) misc. improvements
[ https://issues.apache.org/jira/browse/NPANDAY-326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adelita L. Padilla resolved NPANDAY-326. Resolution: Fixed Fixed in r1055407. misc. improvements -- Key: NPANDAY-326 URL: https://issues.apache.org/jira/browse/NPANDAY-326 Project: NPanday Issue Type: Improvement Components: Maven Plugins Affects Versions: 1.2.1 Reporter: Henrik Bie Priority: Minor Fix For: 1.3-incubating Attachments: 1.2.1.patch Added @parameter to parameters unsafe and testUnsafe. Added parameters warn, testWarn, nowarn and testNowarn. NPANDAY-068-003: Language is now compilerContext.getCompilerRequirement().getLanguage() instead of compilerContext.getCompilerRequirement().getVendor() -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (NPANDAY-239) VS Add-In messes up settings.xml
[ https://issues.apache.org/jira/browse/NPANDAY-239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adelita L. Padilla resolved NPANDAY-239. Resolution: Fixed Fixed in r1055807. VS Add-In messes up settings.xml Key: NPANDAY-239 URL: https://issues.apache.org/jira/browse/NPANDAY-239 Project: NPanday Issue Type: Bug Components: Visual Studio Add-in Reporter: Lars Corneliussen Assignee: Adelita L. Padilla Fix For: 1.3-incubating With the fix for [workitem:11837] now the settings.xml is reformatted and all comments are stripped out. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (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 ] Adelita L. Padilla resolved NPANDAY-347. Resolution: Fixed Fixed in r1057494 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 Assignee: Adelita L. Padilla Priority: Critical Fix For: 1.3-incubating 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] Created: (NPANDAY-365) Error when deploying documentation for plugins
Error when deploying documentation for plugins -- Key: NPANDAY-365 URL: https://issues.apache.org/jira/browse/NPANDAY-365 Project: NPanday Issue Type: Bug Components: Maven Plugins Affects Versions: 1.3-incubating Reporter: Adelita L. Padilla Priority: Minor Fix For: 2.0 When deploying documentation for plugins module, this error occurs: Embedded error: Error rendering Maven report: Error extracting plugin descriptor: 'No mojo definitions were found for plugin: npanday.plugin:custom-lifecycle-maven-plugin.' -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (NPANDAY-365) Error when deploying documentation for plugins
[ https://issues.apache.org/jira/browse/NPANDAY-365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adelita L. Padilla resolved NPANDAY-365. Resolution: Not A Problem Fix Version/s: (was: 2.0) 1.3-incubating Plugins module need to run install first before site deployment. Error when deploying documentation for plugins -- Key: NPANDAY-365 URL: https://issues.apache.org/jira/browse/NPANDAY-365 Project: NPanday Issue Type: Bug Components: Maven Plugins Affects Versions: 1.3-incubating Reporter: Adelita L. Padilla Priority: Minor Fix For: 1.3-incubating When deploying documentation for plugins module, this error occurs: Embedded error: Error rendering Maven report: Error extracting plugin descriptor: 'No mojo definitions were found for plugin: npanday.plugin:custom-lifecycle-maven-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-367) Building a project that contains a maven artifact from a remote repository generates a new .m2groupId folder
[ https://issues.apache.org/jira/browse/NPANDAY-367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adelita L. Padilla updated NPANDAY-367: --- Summary: Building a project that contains a maven artifact from a remote repository generates a new .m2groupId folder (was: Building a project that contains a maven artifact from a remote repository generates a .m2 folder) Building a project that contains a maven artifact from a remote repository generates a new .m2groupId folder Key: NPANDAY-367 URL: https://issues.apache.org/jira/browse/NPANDAY-367 Project: NPanday Issue Type: Bug Reporter: Adelita L. Padilla Priority: Minor Fix For: 2.0 A new .m2 folder is generated after building a project with a dependency Steps to reproduce: 1) Create a new project 2) Generate POM 3) Add a new maven artifact from a remote repository 4) Click on Build Actual Behavior: A new .m2 folder is generated in the user_home directory Expected Behavior: No generation of a new .m2 folder should be happening -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (NPANDAY-367) Building a project that contains a maven artifact from a remote repository generates a new .m2groupId folder
[ https://issues.apache.org/jira/browse/NPANDAY-367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12988547#action_12988547 ] Adelita L. Padilla commented on NPANDAY-367: Hi Wendy, I revised the title of the issue. The new generated folder is .m2+GroupId (e.g, .m2NPanday). This may be affected by the removal of the uac/gac directories. This affects 1.3-incubating. Building a project that contains a maven artifact from a remote repository generates a new .m2groupId folder Key: NPANDAY-367 URL: https://issues.apache.org/jira/browse/NPANDAY-367 Project: NPanday Issue Type: Bug Reporter: Adelita L. Padilla Priority: Minor Fix For: 2.0 A new .m2 folder is generated after building a project with a dependency Steps to reproduce: 1) Create a new project 2) Generate POM 3) Add a new maven artifact from a remote repository 4) Click on Build Actual Behavior: A new .m2 folder is generated in the user_home directory Expected Behavior: No generation of a new .m2 folder should be happening -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (NPANDAY-367) Building a project that contains a maven artifact from a remote repository generates a new .m2groupId folder
[ https://issues.apache.org/jira/browse/NPANDAY-367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adelita L. Padilla updated NPANDAY-367: --- Assignee: Adelita L. Padilla Building a project that contains a maven artifact from a remote repository generates a new .m2groupId folder Key: NPANDAY-367 URL: https://issues.apache.org/jira/browse/NPANDAY-367 Project: NPanday Issue Type: Bug Reporter: Adelita L. Padilla Assignee: Adelita L. Padilla Fix For: 2.0 A new .m2 folder is generated after building a project with a dependency Steps to reproduce: 1) Create a new project 2) Generate POM 3) Add a new maven artifact from a remote repository 4) Click on Build Actual Behavior: A new .m2 folder is generated in the user_home directory Expected Behavior: No generation of a new .m2 folder should be happening -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Resolved: (NPANDAY-367) Building a project that contains a maven artifact from a remote repository generates a new .m2groupId folder
[ https://issues.apache.org/jira/browse/NPANDAY-367?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adelita L. Padilla resolved NPANDAY-367. Resolution: Fixed Fixed in r1065518 Building a project that contains a maven artifact from a remote repository generates a new .m2groupId folder Key: NPANDAY-367 URL: https://issues.apache.org/jira/browse/NPANDAY-367 Project: NPanday Issue Type: Bug Reporter: Adelita L. Padilla Assignee: Adelita L. Padilla Fix For: 2.0 A new .m2 folder is generated after building a project with a dependency Steps to reproduce: 1) Create a new project 2) Generate POM 3) Add a new maven artifact from a remote repository 4) Click on Build Actual Behavior: A new .m2 folder is generated in the user_home directory Expected Behavior: No generation of a new .m2 folder should be happening -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Assigned: (NPANDAY-368) pom should be correctly updated when adding/renaming/removing a service reference
[ https://issues.apache.org/jira/browse/NPANDAY-368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adelita L. Padilla reassigned NPANDAY-368: -- Assignee: Adelita L. Padilla pom should be correctly updated when adding/renaming/removing a service reference - Key: NPANDAY-368 URL: https://issues.apache.org/jira/browse/NPANDAY-368 Project: NPanday Issue Type: New Feature Reporter: Adelita L. Padilla Assignee: Adelita L. Padilla Priority: Minor Steps to reproduce: 1) Create a project (VS2008/VS2010) 2) Generate a POM 3) Add a new service reference Actual Behavior: POM file was not updated correctly (Service Reference should be added like that of a Web Reference) Expected Behavior: Pom should be correctly updated. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Assigned: (NPANDAY-363) Service Reference is not deleted from pom when removing it in the project
[ https://issues.apache.org/jira/browse/NPANDAY-363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adelita L. Padilla reassigned NPANDAY-363: -- Assignee: Adelita L. Padilla Service Reference is not deleted from pom when removing it in the project - Key: NPANDAY-363 URL: https://issues.apache.org/jira/browse/NPANDAY-363 Project: NPanday Issue Type: Bug Affects Versions: 1.2.1 Environment: Visual Studio 2010 Reporter: Marecor M Baclay Assignee: Adelita L. Padilla Fix For: 2.0 Steps: 1. Create a WPF project in VS 2010. 2. Right Click on the References of the project then click on Add Service Reference 3. In the Address field, input the Service Reference URL (i.e. http://www.webservicex.net/sendsmsworld.asmx?WSDL) then click Go 4. Click OK Actual Result: includeSourceService%20References/ServiceReference1/Reference.cs/includeSource has been added in includeSources tag in the pom.xml file of the project 5. Remove the Service Reference Actual Result: includeSourceService%20References/ServiceReference1/Reference.cs/includeSource is not deleted in the pom.xml file of the project Expected Result: the Service Reference should be removed from the pom.xml file. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (NPANDAY-362) npanday-settings.xml in local repository is not overwritten on a new install of npanday.
[ https://issues.apache.org/jira/browse/NPANDAY-362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12994737#comment-12994737 ] Adelita L. Padilla commented on NPANDAY-362: Fixed in r1070828. allows npanday-settings.xml to be overwritten. npanday-settings.xml in local repository is not overwritten on a new install of npanday. Key: NPANDAY-362 URL: https://issues.apache.org/jira/browse/NPANDAY-362 Project: NPanday Issue Type: Bug Components: Visual Studio Add-in Affects Versions: 1.3-incubating Reporter: Joe Ocaba Assignee: Adelita L. Padilla Priority: Minor Fix For: 2.0 npanday-settings.xml should reflect the correct version of frameworks in the path. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Assigned: (NPANDAY-362) npanday-settings.xml in local repository is not overwritten on a new install of npanday.
[ https://issues.apache.org/jira/browse/NPANDAY-362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adelita L. Padilla reassigned NPANDAY-362: -- Assignee: Adelita L. Padilla npanday-settings.xml in local repository is not overwritten on a new install of npanday. Key: NPANDAY-362 URL: https://issues.apache.org/jira/browse/NPANDAY-362 Project: NPanday Issue Type: Bug Components: Visual Studio Add-in Affects Versions: 1.3-incubating Reporter: Joe Ocaba Assignee: Adelita L. Padilla Priority: Minor Fix For: 2.0 npanday-settings.xml should reflect the correct version of frameworks in the path. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (NPANDAY-362) npanday-settings.xml in local repository is not overwritten on a new install of npanday.
[ https://issues.apache.org/jira/browse/NPANDAY-362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12996519#comment-12996519 ] Adelita L. Padilla commented on NPANDAY-362: fixed in r1072064. check first if project's frameworkVersion is present in the existing npanday-settings.xml before overwriting npanday-settings.xml in local repository is not overwritten on a new install of npanday. Key: NPANDAY-362 URL: https://issues.apache.org/jira/browse/NPANDAY-362 Project: NPanday Issue Type: Bug Components: Visual Studio Add-in Affects Versions: 1.3-incubating Reporter: Joe Ocaba Assignee: Adelita L. Padilla Priority: Minor Fix For: 2.0 npanday-settings.xml should reflect the correct version of frameworks in the path. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (NPANDAY-379) Exception not catch properly when default path for npanday-settings.xml is used
Exception not catch properly when default path for npanday-settings.xml is used
---
Key: NPANDAY-379
URL: https://issues.apache.org/jira/browse/NPANDAY-379
Project: NPanday
Issue Type: Bug
Affects Versions: 1.3-incubating
Reporter: Adelita L. Padilla
Priority: Minor
Fix For: 1.3.1-incubating
Steps to reproduce:
1) Removed npanday-settings.xml in the user_home directory
2) Open and build a project using NPanday
3) Noticed that the build was successful, but there was an exception thrown.
See logs below:
[INFO] [NPanday.Plugin.Settings.JavaBinding:generate-settings {execution:
default-generate-settings}]
org.apache.maven.plugin.MojoExecutionException:
at
npanday.plugin.StringConfigurationAppender.append(StringConfigurationAppender.java:37)
at npanday.plugin.AbstractMojo.getDOMSourceFor(AbstractMojo.java:274)
at npanday.plugin.AbstractMojo.execute(AbstractMojo.java:132)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556)
Expected Behavior: Exception should be handled correctly.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Assigned: (NPANDAY-379) Exception not caught properly when default path for npanday-settings.xml is used
[
https://issues.apache.org/jira/browse/NPANDAY-379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adelita L. Padilla reassigned NPANDAY-379:
--
Assignee: Adelita L. Padilla
Exception not caught properly when default path for npanday-settings.xml is
used
Key: NPANDAY-379
URL: https://issues.apache.org/jira/browse/NPANDAY-379
Project: NPanday
Issue Type: Bug
Affects Versions: 1.3-incubating
Reporter: Adelita L. Padilla
Assignee: Adelita L. Padilla
Priority: Minor
Fix For: 1.3.1-incubating
Steps to reproduce:
1) Removed npanday-settings.xml in the user_home directory
2) Open and build a project using NPanday
3) Noticed that the build was successful, but there was an exception thrown.
See logs below:
[INFO] [NPanday.Plugin.Settings.JavaBinding:generate-settings {execution:
default-generate-settings}]
org.apache.maven.plugin.MojoExecutionException:
at
npanday.plugin.StringConfigurationAppender.append(StringConfigurationAppender.java:37)
at npanday.plugin.AbstractMojo.getDOMSourceFor(AbstractMojo.java:274)
at npanday.plugin.AbstractMojo.execute(AbstractMojo.java:132)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556)
Expected Behavior: Exception should be handled correctly.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (NPANDAY-377) released registry-config.xml contains a hardcoded path
[
https://issues.apache.org/jira/browse/NPANDAY-377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adelita L. Padilla reassigned NPANDAY-377:
--
Assignee: Adelita L. Padilla
released registry-config.xml contains a hardcoded path
--
Key: NPANDAY-377
URL: https://issues.apache.org/jira/browse/NPANDAY-377
Project: NPanday
Issue Type: Bug
Affects Versions: 1.3-incubating
Reporter: Adelita L. Padilla
Assignee: Adelita L. Padilla
Priority: Minor
Fix For: 1.3.1-incubating
Extract the jar file found in
http://vmbuild.apache.org/archiva/repository/staged-npanday/npanday/dotnet-core/
Noticed that the registry-config.xml file contains a hardcoded path (The
{user.home} of the release manager was hardcoded).
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (NPANDAY-377) released registry-config.xml contains a hardcoded path
[
https://issues.apache.org/jira/browse/NPANDAY-377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adelita L. Padilla resolved NPANDAY-377.
Resolution: Fixed
Fixed in r1083725.
released registry-config.xml contains a hardcoded path
--
Key: NPANDAY-377
URL: https://issues.apache.org/jira/browse/NPANDAY-377
Project: NPanday
Issue Type: Bug
Affects Versions: 1.3-incubating
Reporter: Adelita L. Padilla
Assignee: Adelita L. Padilla
Priority: Minor
Fix For: 1.3.1-incubating
Extract the jar file found in
http://vmbuild.apache.org/archiva/repository/staged-npanday/npanday/dotnet-core/
Noticed that the registry-config.xml file contains a hardcoded path (The
{user.home} of the release manager was hardcoded).
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (NPANDAY-383) update groupID to org.apache.npanday
update groupID to org.apache.npanday Key: NPANDAY-383 URL: https://issues.apache.org/jira/browse/NPANDAY-383 Project: NPanday Issue Type: Task Affects Versions: 1.3-incubating Reporter: Adelita L. Padilla Update groupId to org.apache.npanday so that the released artifacts would sync'd to central. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Work started] (NPANDAY-397) NPanday adds 'maven-test-plugin' configuration to pom file based on NUnit.Framework reference in project and not based on test project selected in Project Unit Test
[ https://issues.apache.org/jira/browse/NPANDAY-397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on NPANDAY-397 started by Adelita L. Padilla. NPanday adds 'maven-test-plugin' configuration to pom file based on NUnit.Framework reference in project and not based on test project selected in Project Unit Tests window Key: NPANDAY-397 URL: https://issues.apache.org/jira/browse/NPANDAY-397 Project: NPanday Issue Type: Bug Components: Project Importer Affects Versions: 1.2.1 Reporter: Adelita L. Padilla Assignee: Adelita L. Padilla Fix For: 1.3.1-incubating Steps to reproduce: 1) Start NPanday and open project 2) Right-click on project then select 'Generate Solution's POM Information...' 3) Provide all needed information and click 'Generate Poms' 4) In Project Unit Test window, select a project then click 'OK' Result:maven-test-plugin configuration was not added to the pom even if the project was selected in the Project Unit Tests window 5) Add nunit as maven reference 6) Generate POM again, then in the Project Unit Test window unselect the project Result: maven-test-plugin configuration was added even if no project was selected in the Project Unit Test window Actual Behavior: If not project was selected in the Project Unit Test window but there is a nunit dependency, generated pom file contains a maven-test-plugin configuration. Expected Behavior: maven-test-plugin configuration should only appear in the pom if a project was selected in the Project Unit Test window. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (NPANDAY-403) successful generation of poms after clicking on 'Cancel' button
successful generation of poms after clicking on 'Cancel' button --- Key: NPANDAY-403 URL: https://issues.apache.org/jira/browse/NPANDAY-403 Project: NPanday Issue Type: Bug Components: Project Importer Affects Versions: 1.2.1 Reporter: Adelita L. Padilla Priority: Minor Fix For: 1.3.1-incubating Pom files were generated successfully even if 'Cancel' button was clicked. 1) Start NPanday 2) Open Project 2) Right-click on project then select 'Generate Solution's POM Information...' 3) Provide all needed information and click 'Generate Poms' 4) In Project Unit Test window, click the 'Close' button on the upper right side of the form 5) Click on 'Cancel' button Result:POMs were successfully generated Actual Behavior: POMs were successfully generated. Expected Behavior: Import window should be closed and no POMs should be generated -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (NPANDAY-397) NPanday adds 'maven-test-plugin' configuration to pom file based on NUnit.Framework reference in project and not based on test project selected in Project Unit Tests wi
[ https://issues.apache.org/jira/browse/NPANDAY-397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adelita L. Padilla resolved NPANDAY-397. Resolution: Fixed Fixed in r1092043 NPanday adds 'maven-test-plugin' configuration to pom file based on NUnit.Framework reference in project and not based on test project selected in Project Unit Tests window Key: NPANDAY-397 URL: https://issues.apache.org/jira/browse/NPANDAY-397 Project: NPanday Issue Type: Bug Components: Project Importer Affects Versions: 1.2.1 Reporter: Adelita L. Padilla Assignee: Adelita L. Padilla Fix For: 1.3.1-incubating Steps to reproduce: 1) Start NPanday and open project 2) Right-click on project then select 'Generate Solution's POM Information...' 3) Provide all needed information and click 'Generate Poms' 4) In Project Unit Test window, select a project then click 'OK' Result:maven-test-plugin configuration was not added to the pom even if the project was selected in the Project Unit Tests window 5) Add nunit as maven reference 6) Generate POM again, then in the Project Unit Test window unselect the project Result: maven-test-plugin configuration was added even if no project was selected in the Project Unit Test window Actual Behavior: If not project was selected in the Project Unit Test window but there is a nunit dependency, generated pom file contains a maven-test-plugin configuration. Expected Behavior: maven-test-plugin configuration should only appear in the pom if a project was selected in the Project Unit Test window. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (NPANDAY-403) successful generation of poms after clicking on 'Cancel' button
[ https://issues.apache.org/jira/browse/NPANDAY-403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adelita L. Padilla updated NPANDAY-403: --- Fix Version/s: (was: 1.3.1-incubating) 1.3.2-incubating successful generation of poms after clicking on 'Cancel' button --- Key: NPANDAY-403 URL: https://issues.apache.org/jira/browse/NPANDAY-403 Project: NPanday Issue Type: Bug Components: Project Importer Affects Versions: 1.2.1 Reporter: Adelita L. Padilla Priority: Minor Fix For: 1.3.2-incubating Pom files were generated successfully even if 'Cancel' button was clicked. 1) Start NPanday 2) Open Project 2) Right-click on project then select 'Generate Solution's POM Information...' 3) Provide all needed information and click 'Generate Poms' 4) In Project Unit Test window, click the 'Close' button on the upper right side of the form 5) Click on 'Cancel' button Result:POMs were successfully generated Actual Behavior: POMs were successfully generated. Expected Behavior: Import window should be closed and no POMs should be generated -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (NPANDAY-428) Issues while removing/adding a dependency in the project
Issues while removing/adding a dependency in the project Key: NPANDAY-428 URL: https://issues.apache.org/jira/browse/NPANDAY-428 Project: NPanday Issue Type: Bug Components: Visual Studio Add-in Affects Versions: 1.4-incubating Reporter: Adelita L. Padilla Fix For: 1.4.1-incubating Steps to reproduce: 1) Start NPanday 2) Open 'ProjectA' 3) Generate POMs 4) Right click on 'ProjectA', then select 'Current NPanday Project Install' 5) Add a new 'ProjectB' to the solution 6) Generate POMs 7) Add 'ProjectA' as dependency to 'ProjectB' (Add Maven Artifact) 8) Build the whole solution 9) Remove 'ProjectA' as dependency to 'ProjectB' Actual Behavior: POM file for ProjectB was not updated correctly. Configuration for the dependency for 'ProjectA' was not removed in POM Expected Behavior: POM file for ProjectB should be updated properly. 10) Add 'ProjectA' again to 'ProjectB' Actual Behavior: Error in Adding Artifact Dependency.. pops up because the dependency was not removed in the POM. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (NPANDAY-430) Poms should not be generated when importing flat project with modules below
Poms should not be generated when importing flat project with modules below Key: NPANDAY-430 URL: https://issues.apache.org/jira/browse/NPANDAY-430 Project: NPanday Issue Type: Bug Components: Project Importer Affects Versions: 1.4-incubating Reporter: Adelita L. Padilla Priority: Minor Fix For: 1.4.1-incubating Steps to reproduce: 1) Open attached project 2) Start NPanday 3) Right click on Solution then click 'Generate Solution's POM Information...' Actual Behavior: POMs were successfully generated Expected Behavior: POMs should not be generated, instead a pop-up window stating: Project Importer failed with project [PROJECT_NAME_ALONG_WITH_PATH]. Project directory structure may not be supported. should be displayed. Here's the [documentation|http://incubator.apache.org/npanday/docs/1.4.0-incubating/guide/reference/supported-dir-structures.html] for supported project structures. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (NPANDAY-430) Poms should not be generated when importing flat project with modules below
[ https://issues.apache.org/jira/browse/NPANDAY-430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adelita L. Padilla closed NPANDAY-430. -- Resolution: Not A Problem Sorry for filing. Reread documentation and flat-multi projects are supported although it's not recommended. http://incubator.apache.org/npanday/docs/1.4.0-incubating/guide/reference/supported-dir-structures.html Thanks! Poms should not be generated when importing flat project with modules below Key: NPANDAY-430 URL: https://issues.apache.org/jira/browse/NPANDAY-430 Project: NPanday Issue Type: Bug Components: Project Importer Affects Versions: 1.4-incubating Reporter: Adelita L. Padilla Priority: Minor Fix For: 1.4.1-incubating Attachments: Solution1.zip Steps to reproduce: 1) Open attached project 2) Start NPanday 3) Right click on Solution then click 'Generate Solution's POM Information...' Actual Behavior: POMs were successfully generated Expected Behavior: POMs should not be generated, instead a pop-up window stating: Project Importer failed with project [PROJECT_NAME_ALONG_WITH_PATH]. Project directory structure may not be supported. should be displayed. Here's the [documentation|http://incubator.apache.org/npanday/docs/1.4.0-incubating/guide/reference/supported-dir-structures.html] for supported project structures. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (NPANDAY-432) Webreference removing/adding issue
Webreference removing/adding issue
--
Key: NPANDAY-432
URL: https://issues.apache.org/jira/browse/NPANDAY-432
Project: NPanday
Issue Type: Bug
Affects Versions: 1.4-incubating
Reporter: Adelita L. Padilla
Priority: Minor
Fix For: 1.4.1-incubating
Steps to reproduce:
1) Start NPanday
2) Open project
3) Delete existing web reference
4) Add a new web reference
Actual Behavior:
Web reference was adding and wsdl plugin configuration was correctly updated in
the pom. However includeSources was not updated successfully.
In the output window, this error was also displayed:
{Error on webservice create: The process cannot access the file
'C:\Users\apadilla\Desktop\TestWebReference\ClassLibrary1\pom.xml' because it
is being used by another process.}
When renaming the web reference, this is also displayed in the output window:
{Error on webservice rename: The process cannot access the file
'C:\Users\apadilla\Desktop\TestWebReference\ClassLibrary1\pom.xml' because it
is being used by another process.}
Expected Behavior:
POM files should be correctly updated when adding/renaming a web reference and
no error message should be displayed in the output window.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (NPANDAY-434) issue while adding/removing dependency
issue while adding/removing dependency --- Key: NPANDAY-434 URL: https://issues.apache.org/jira/browse/NPANDAY-434 Project: NPanday Issue Type: Bug Affects Versions: 1.4-incubating Reporter: Adelita L. Padilla Priority: Minor Fix For: 1.4.1-incubating Steps to reproduce: 1) Start NPanday 2) Open ProjectA 3) Generate POM 4) Right click on Project then select Current NPanday Project Install 5) Add new ProjectB to Solution 6) Generate POM 7) Add ProjectA as dependency to ProjectB through Add Maven Artifact 8) Build entire solution 9) Remove ProjectA as dependency to ProjectB Actual Behavior: ProjectA was not removed. Expected Behavior: ProjectA should be remove as dependency to ProjectB. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (NPANDAY-432) Webreference removing/adding issue
[
https://issues.apache.org/jira/browse/NPANDAY-432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adelita L. Padilla resolved NPANDAY-432.
Resolution: Fixed
Fixed in r1127458.
Webreference removing/adding issue
--
Key: NPANDAY-432
URL: https://issues.apache.org/jira/browse/NPANDAY-432
Project: NPanday
Issue Type: Bug
Affects Versions: 1.4-incubating
Reporter: Adelita L. Padilla
Priority: Minor
Fix For: 1.4.1-incubating
Steps to reproduce:
1) Start NPanday
2) Open project
3) Delete existing web reference
4) Add a new web reference
Actual Behavior:
Web reference was adding and wsdl plugin configuration was correctly updated
in the pom. However includeSources was not updated successfully.
In the output window, this error was also displayed:
{Error on webservice create: The process cannot access the file
'C:\Users\apadilla\Desktop\TestWebReference\ClassLibrary1\pom.xml' because it
is being used by another process.}
When renaming the web reference, this is also displayed in the output window:
{Error on webservice rename: The process cannot access the file
'C:\Users\apadilla\Desktop\TestWebReference\ClassLibrary1\pom.xml' because it
is being used by another process.}
Expected Behavior:
POM files should be correctly updated when adding/renaming a web reference
and no error message should be displayed in the output window.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (NPANDAY-433) source file deleted in pom when removing it in the project even if NPanday is not launched
[ https://issues.apache.org/jira/browse/NPANDAY-433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adelita L. Padilla reassigned NPANDAY-433: -- Assignee: Adelita L. Padilla source file deleted in pom when removing it in the project even if NPanday is not launched -- Key: NPANDAY-433 URL: https://issues.apache.org/jira/browse/NPANDAY-433 Project: NPanday Issue Type: Bug Affects Versions: 1.4-incubating Reporter: Adelita L. Padilla Assignee: Adelita L. Padilla Priority: Minor Fix For: 1.4.1-incubating Steps to reproduce: 1) Start NPanday 2) Open project 3) Stop NPanday (Tools Add-in Manager - then uncheck NPanday) 4) Delete source file Actual Behavior: source file was deleted in pom.xml Expected Behavior: source file should not be deleted in pom.xml since NPanday is not launched. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Work started] (NPANDAY-433) source file deleted in pom when removing it in the project even if NPanday is not launched
[ https://issues.apache.org/jira/browse/NPANDAY-433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on NPANDAY-433 started by Adelita L. Padilla. source file deleted in pom when removing it in the project even if NPanday is not launched -- Key: NPANDAY-433 URL: https://issues.apache.org/jira/browse/NPANDAY-433 Project: NPanday Issue Type: Bug Affects Versions: 1.4-incubating Reporter: Adelita L. Padilla Assignee: Adelita L. Padilla Priority: Minor Fix For: 1.4.1-incubating Steps to reproduce: 1) Start NPanday 2) Open project 3) Stop NPanday (Tools Add-in Manager - then uncheck NPanday) 4) Delete source file Actual Behavior: source file was deleted in pom.xml Expected Behavior: source file should not be deleted in pom.xml since NPanday is not launched. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (NPANDAY-433) source file deleted in pom when removing it in the project even if NPanday is not launched
[ https://issues.apache.org/jira/browse/NPANDAY-433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adelita L. Padilla updated NPANDAY-433: --- Assignee: (was: Adelita L. Padilla) source file deleted in pom when removing it in the project even if NPanday is not launched -- Key: NPANDAY-433 URL: https://issues.apache.org/jira/browse/NPANDAY-433 Project: NPanday Issue Type: Bug Affects Versions: 1.4-incubating Reporter: Adelita L. Padilla Priority: Minor Fix For: 1.4.1-incubating Steps to reproduce: 1) Start NPanday 2) Open project 3) Stop NPanday (Tools Add-in Manager - then uncheck NPanday) 4) Delete source file Actual Behavior: source file was deleted in pom.xml Expected Behavior: source file should not be deleted in pom.xml since NPanday is not launched. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (NPANDAY-433) source file deleted in pom when removing it in the project even if NPanday is not launched
[ https://issues.apache.org/jira/browse/NPANDAY-433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adelita L. Padilla resolved NPANDAY-433. Resolution: Fixed Fixed in r1127766. source file deleted in pom when removing it in the project even if NPanday is not launched -- Key: NPANDAY-433 URL: https://issues.apache.org/jira/browse/NPANDAY-433 Project: NPanday Issue Type: Bug Affects Versions: 1.4-incubating Reporter: Adelita L. Padilla Priority: Minor Fix For: 1.4.1-incubating Steps to reproduce: 1) Start NPanday 2) Open project 3) Stop NPanday (Tools Add-in Manager - then uncheck NPanday) 4) Delete source file Actual Behavior: source file was deleted in pom.xml Expected Behavior: source file should not be deleted in pom.xml since NPanday is not launched. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (NPANDAY-434) issue while adding/removing dependency
[ https://issues.apache.org/jira/browse/NPANDAY-434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adelita L. Padilla reassigned NPANDAY-434: -- Assignee: Adelita L. Padilla issue while adding/removing dependency --- Key: NPANDAY-434 URL: https://issues.apache.org/jira/browse/NPANDAY-434 Project: NPanday Issue Type: Bug Affects Versions: 1.4-incubating Reporter: Adelita L. Padilla Assignee: Adelita L. Padilla Priority: Minor Fix For: 1.4.1-incubating Steps to reproduce: 1) Start NPanday 2) Open ProjectA 3) Generate POM 4) Right click on Project then select Current NPanday Project Install 5) Add new ProjectB to Solution 6) Generate POM 7) Add ProjectA as dependency to ProjectB through Add Maven Artifact 8) Build entire solution 9) Remove ProjectA as dependency to ProjectB Actual Behavior: ProjectA was not removed. Expected Behavior: ProjectA should be remove as dependency to ProjectB. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Work started] (NPANDAY-434) issue while adding/removing dependency
[ https://issues.apache.org/jira/browse/NPANDAY-434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on NPANDAY-434 started by Adelita L. Padilla. issue while adding/removing dependency --- Key: NPANDAY-434 URL: https://issues.apache.org/jira/browse/NPANDAY-434 Project: NPanday Issue Type: Bug Affects Versions: 1.4-incubating Reporter: Adelita L. Padilla Assignee: Adelita L. Padilla Priority: Minor Fix For: 1.4.1-incubating Steps to reproduce: 1) Start NPanday 2) Open ProjectA 3) Generate POM 4) Right click on Project then select Current NPanday Project Install 5) Add new ProjectB to Solution 6) Generate POM 7) Add ProjectA as dependency to ProjectB through Add Maven Artifact 8) Build entire solution 9) Remove ProjectA as dependency to ProjectB Actual Behavior: ProjectA was not removed. Expected Behavior: ProjectA should be remove as dependency to ProjectB. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Work stopped] (NPANDAY-434) issue while adding/removing dependency
[ https://issues.apache.org/jira/browse/NPANDAY-434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on NPANDAY-434 stopped by Adelita L. Padilla. issue while adding/removing dependency --- Key: NPANDAY-434 URL: https://issues.apache.org/jira/browse/NPANDAY-434 Project: NPanday Issue Type: Bug Affects Versions: 1.4-incubating Reporter: Adelita L. Padilla Assignee: Adelita L. Padilla Priority: Minor Fix For: 1.4.1-incubating Steps to reproduce: 1) Start NPanday 2) Open ProjectA 3) Generate POM 4) Right click on Project then select Current NPanday Project Install 5) Add new ProjectB to Solution 6) Generate POM 7) Add ProjectA as dependency to ProjectB through Add Maven Artifact 8) Build entire solution 9) Remove ProjectA as dependency to ProjectB Actual Behavior: ProjectA was not removed. Expected Behavior: ProjectA should be remove as dependency to ProjectB. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (NPANDAY-428) Issues while removing/adding a dependency in the project
[ https://issues.apache.org/jira/browse/NPANDAY-428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adelita L. Padilla reassigned NPANDAY-428: -- Assignee: Adelita L. Padilla Issues while removing/adding a dependency in the project Key: NPANDAY-428 URL: https://issues.apache.org/jira/browse/NPANDAY-428 Project: NPanday Issue Type: Bug Components: Visual Studio Add-in Affects Versions: 1.4-incubating Reporter: Adelita L. Padilla Assignee: Adelita L. Padilla Fix For: 1.4.1-incubating Steps to reproduce: 1) Start NPanday 2) Open 'ProjectA' 3) Generate POMs 4) Right click on 'ProjectA', then select 'Current NPanday Project Install' 5) Add a new 'ProjectB' to the solution 6) Generate POMs 7) Add 'ProjectA' as dependency to 'ProjectB' (Add Maven Artifact) 8) Build the whole solution 9) Remove 'ProjectA' as dependency to 'ProjectB' Actual Behavior: POM file for ProjectB was not updated correctly. Configuration for the dependency for 'ProjectA' was not removed in POM Expected Behavior: POM file for ProjectB should be updated properly. 10) Add 'ProjectA' again to 'ProjectB' Actual Behavior: Error in Adding Artifact Dependency.. pops up because the dependency was not removed in the POM. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (NPANDAY-437) Source file delete from project should delete includeSource node from pom file
Source file delete from project should delete includeSource node from pom file Key: NPANDAY-437 URL: https://issues.apache.org/jira/browse/NPANDAY-437 Project: NPanday Issue Type: Bug Affects Versions: 1.4-incubating Reporter: Adelita L. Padilla Priority: Minor Fix For: 1.4.1-incubating Steps to reproduce: 1) Start NPanday 2) Open Project 3) Generate POM files 4) Delete source file (Properties AssemblyInfo.cs) in solution explorer Actual Behavior: includeSource for AssemblyInfo.cs was not deleted in POM file Expected Behavior: includeSource for AssemblyInfo.cs should be deleted in POM file -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (NPANDAY-438) NPanday.Plugin.Msbuild.JavaBinding plugin does not support framework version 2.0
NPanday.Plugin.Msbuild.JavaBinding plugin does not support framework version 2.0
Key: NPANDAY-438
URL: https://issues.apache.org/jira/browse/NPANDAY-438
Project: NPanday
Issue Type: Bug
Affects Versions: 1.4-incubating
Reporter: Adelita L. Padilla
Priority: Minor
Fix For: 1.4.1-incubating
Steps to reproduce:
1) Create a VS 2010 web application project with a 2.0 .Net Framework
2) Add a resource file to the project
3) Generate POM files
4) Build project
Actual Behavior:
Unable to build project successfully:
{quote}
Microsoft (R) Build Engine Version 2.0.50727.4927
[Microsoft .NET Framework, Version 2.0.50727.4959]
Copyright (C) Microsoft Corporation 2005. All rights reserved.
C:\Program Files
(x86)\MSBuild\Microsoft\VisualStudio\v10.0\Web\Microsoft.Web.Publishing.targets(412,3):
error MSB4067: The element ItemDefinitionGroup beneath element Project is
unrecognized.
Exception occcurred: System.Exception: MSBuild exited with code: 1
at NPanday.Plugin.Msbuild.MsbuildMojo.Execute()
at NPanday.Plugin.AbstractMojo.Execute()
at NPanday.Plugin.Loader.PluginLoader.Main(String[] args)
NPanday: End Process = 5/31/2011 6:26:00 PM; exit code = 1
{quote}
\\
To be able to have a successful build I manually added this in Environment
Variables:
{quote}
Variable name: MSBuildExtensionsPath32
Variable value: C:\Program Files (x86)\MSBuild\
{quote}
Then add:
{quote}
%MSBuildExtensionsPath32%
{quote}
to variable name 'PATH'.
Then I manually revised the .csproj with the ff:
{quote}
Import
Project=$(MSBuildExtensionsPath32)\Microsoft\VisualStudio\v10.0\WebApplications\Microsoft.WebApplication.targets
/
{quote}
to
{quote}
Import
Project=$(MSBuildExtensionsPath32)\Microsoft\VisualStudio\v8.0\WebApplications\Microsoft.WebApplication.targets
/
{quote}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (NPANDAY-438) NPanday.Plugin.Msbuild.JavaBinding plugin does not support framework version 2.0
[
https://issues.apache.org/jira/browse/NPANDAY-438?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adelita L. Padilla updated NPANDAY-438:
---
Description:
Steps to reproduce:
1) Create a VS 2010 web application project with a 2.0 .Net Framework
2) Add a resource file to the project
3) Generate POM files
4) Build project
Actual Behavior:
Unable to build project successfully:
{noformat}
Microsoft (R) Build Engine Version 2.0.50727.4927
[Microsoft .NET Framework, Version 2.0.50727.4959]
Copyright (C) Microsoft Corporation 2005. All rights reserved.
C:\Program Files
(x86)\MSBuild\Microsoft\VisualStudio\v10.0\Web\Microsoft.Web.Publishing.targets(412,3):
error MSB4067: The element ItemDefinitionGroup beneath element Project is
unrecognized.
Exception occcurred: System.Exception: MSBuild exited with code: 1
at NPanday.Plugin.Msbuild.MsbuildMojo.Execute()
at NPanday.Plugin.AbstractMojo.Execute()
at NPanday.Plugin.Loader.PluginLoader.Main(String[] args)
NPanday: End Process = 5/31/2011 6:26:00 PM; exit code = 1
{noformat}
\\
To be able to have a successful build I manually added this in Environment
Variables:
{noformat}
Variable name: MSBuildExtensionsPath32
Variable value: C:\Program Files (x86)\MSBuild\
{noformat}
Then add:
{noformat}
%MSBuildExtensionsPath32%
{noformat}
to variable name 'PATH'.
Then I manually revised the .csproj with the ff:
{noformat}
Import
Project=$(MSBuildExtensionsPath32)\Microsoft\VisualStudio\v10.0\WebApplications\Microsoft.WebApplication.targets
/
{noformat}
to
{noformat}
Import
Project=$(MSBuildExtensionsPath32)\Microsoft\VisualStudio\v8.0\WebApplications\Microsoft.WebApplication.targets
/
{noformat}
was:
Steps to reproduce:
1) Create a VS 2010 web application project with a 2.0 .Net Framework
2) Add a resource file to the project
3) Generate POM files
4) Build project
Actual Behavior:
Unable to build project successfully:
{quote}
Microsoft (R) Build Engine Version 2.0.50727.4927
[Microsoft .NET Framework, Version 2.0.50727.4959]
Copyright (C) Microsoft Corporation 2005. All rights reserved.
C:\Program Files
(x86)\MSBuild\Microsoft\VisualStudio\v10.0\Web\Microsoft.Web.Publishing.targets(412,3):
error MSB4067: The element ItemDefinitionGroup beneath element Project is
unrecognized.
Exception occcurred: System.Exception: MSBuild exited with code: 1
at NPanday.Plugin.Msbuild.MsbuildMojo.Execute()
at NPanday.Plugin.AbstractMojo.Execute()
at NPanday.Plugin.Loader.PluginLoader.Main(String[] args)
NPanday: End Process = 5/31/2011 6:26:00 PM; exit code = 1
{quote}
\\
To be able to have a successful build I manually added this in Environment
Variables:
{quote}
Variable name: MSBuildExtensionsPath32
Variable value: C:\Program Files (x86)\MSBuild\
{quote}
Then add:
{quote}
%MSBuildExtensionsPath32%
{quote}
to variable name 'PATH'.
Then I manually revised the .csproj with the ff:
{quote}
Import
Project=$(MSBuildExtensionsPath32)\Microsoft\VisualStudio\v10.0\WebApplications\Microsoft.WebApplication.targets
/
{quote}
to
{quote}
Import
Project=$(MSBuildExtensionsPath32)\Microsoft\VisualStudio\v8.0\WebApplications\Microsoft.WebApplication.targets
/
{quote}
NPanday.Plugin.Msbuild.JavaBinding plugin does not support framework version
2.0
Key: NPANDAY-438
URL: https://issues.apache.org/jira/browse/NPANDAY-438
Project: NPanday
Issue Type: Bug
Affects Versions: 1.4-incubating
Reporter: Adelita L. Padilla
Priority: Minor
Fix For: 1.4.1-incubating
Steps to reproduce:
1) Create a VS 2010 web application project with a 2.0 .Net Framework
2) Add a resource file to the project
3) Generate POM files
4) Build project
Actual Behavior:
Unable to build project successfully:
{noformat}
Microsoft (R) Build Engine Version 2.0.50727.4927
[Microsoft .NET Framework, Version 2.0.50727.4959]
Copyright (C) Microsoft Corporation 2005. All rights reserved.
C:\Program Files
(x86)\MSBuild\Microsoft\VisualStudio\v10.0\Web\Microsoft.Web.Publishing.targets(412,3):
error MSB4067: The element ItemDefinitionGroup beneath element Project
is unrecognized.
Exception occcurred: System.Exception: MSBuild exited with code: 1
at NPanday.Plugin.Msbuild.MsbuildMojo.Execute()
at NPanday.Plugin.AbstractMojo.Execute()
at NPanday.Plugin.Loader.PluginLoader.Main(String[] args)
NPanday: End Process = 5/31/2011 6:26:00 PM; exit code = 1
{noformat}
\\
To be able to have a successful build I manually added this in Environment
Variables:
{noformat}
Variable name: MSBuildExtensionsPath32
Variable value: C:\Program Files (x86)\MSBuild\
{noformat}
Then add:
{noformat}
%MSBuildExtensionsPath32%
{noformat}
to variable name 'PATH'.
Then I manually revised the
