[jira] Updated: (NPANDAY-186) Remove the uac and pab directories
[ https://issues.apache.org/jira/browse/NPANDAY-186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Ocaba updated NPANDAY-186: -- Component/s: Repository Priority: Major (was: Minor) Affects Version/s: 2.0 Fix Version/s: (was: Backlog) 2.0 Assignee: Joe Ocaba Issue Type: Improvement (was: Bug) > Remove the uac and pab directories > -- > > Key: NPANDAY-186 > URL: https://issues.apache.org/jira/browse/NPANDAY-186 > Project: NPanday > Issue Type: Improvement > Components: Repository >Affects Versions: 2.0 >Reporter: Wendy Smoak >Assignee: Joe Ocaba > Fix For: 2.0 > > > As discussed on > http://npanday.codeplex.com/WorkItem/View.aspx?WorkItemId=10557 > brettporter wrote Oct 16 at 7:47 AM > "I think adding configuration parameters to relocate uac and pab is overkill > considering that the time would be better invested in removing their use." > This would allow NPanday to function using only the normal Maven local > repository. -- 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-186) Remove the uac and pab directories
[ https://issues.apache.org/jira/browse/NPANDAY-186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on NPANDAY-186 started by Joe Ocaba. > Remove the uac and pab directories > -- > > Key: NPANDAY-186 > URL: https://issues.apache.org/jira/browse/NPANDAY-186 > Project: NPanday > Issue Type: Improvement > Components: Repository >Affects Versions: 2.0 >Reporter: Wendy Smoak >Assignee: Joe Ocaba > Fix For: 2.0 > > > As discussed on > http://npanday.codeplex.com/WorkItem/View.aspx?WorkItemId=10557 > brettporter wrote Oct 16 at 7:47 AM > "I think adding configuration parameters to relocate uac and pab is overkill > considering that the time would be better invested in removing their use." > This would allow NPanday to function using only the normal Maven local > repository. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (NPANDAY-186) Remove the uac and pab directories
[ https://issues.apache.org/jira/browse/NPANDAY-186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12918810#action_12918810 ] Joe Ocaba commented on NPANDAY-186: --- Intial fix for the removal of the uac and pab directories. the output is already in the maven covention default repository. however there is a problem with the npanday.plugin.runner.exe since its unable to use the target directory as the holder of dependencies. > Remove the uac and pab directories > -- > > Key: NPANDAY-186 > URL: https://issues.apache.org/jira/browse/NPANDAY-186 > Project: NPanday > Issue Type: Improvement > Components: Repository >Affects Versions: 2.0 >Reporter: Wendy Smoak >Assignee: Joe Ocaba > Fix For: 2.0 > > > As discussed on > http://npanday.codeplex.com/WorkItem/View.aspx?WorkItemId=10557 > brettporter wrote Oct 16 at 7:47 AM > "I think adding configuration parameters to relocate uac and pab is overkill > considering that the time would be better invested in removing their use." > This would allow NPanday to function using only the normal Maven local > repository. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (NPANDAY-186) Remove the uac and pab directories
[ https://issues.apache.org/jira/browse/NPANDAY-186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12920854#action_12920854 ] Joe Ocaba commented on NPANDAY-186: --- There is a problem with building the npanday system from scratch. If I would build from the specific branches like the dotnet/assemblies/ the output in the target directory is correct as well as the one in the .m2/repository/ however when It comes up to the plugins/netplugins it seems that it is copying 0 size files from the needed dependencies i.e. NPanday.Logging.dll has a file size of zero. With this error message: Embedded error: NPANDAY-063-000: Execution Path = C:\Projects\apache-npanday-incubator\branches\npanday-uac-removed\plugins\netplugins\bin, Command = [targetAssemblyFile=C:\Projects\apache-npanday-incubator\branches\npanday-uac-removed\plugins\netplugins\NPanday.Plugin.Addin\target\NPanday.Plugin.Ad din.dll, outputDirectory=C:\Projects\apache-npanday-incubator\branches\npanday-uac-removed\plugins\netplugins\NPanday.Plugin.Addin, groupId=npanday.plugin, artifactId=NPanday.Plugin.Addin, artifactVersion=1.2.2-incubating-SNAPSHOT, startProcessAssembly=C:\Projects\apache-npanday-incubator\branches\n panday-uac-removed\plugins\netplugins\bin\NPanday.Plugin.MojoGenerator.exe, pluginArtifactPath=C:\Projects\apache-npanday-incubator\branches\npanday-uac-removed\plugins\netplugins\bin\NPanday.Plugin.dll] NPANDAY-040-001: Could not execute: Command = CMD.EXE /X /C NPanday.Plugin.Runner.exe targetAssemblyFile=C:\Projects\apache-npanday-incubator\branches\npanday-uac-removed\plugins\netplugins\NPanday.Plugin.Addin\target\NPanday.Plugin.Addin.dll outputDirectory=C:\Projects\apache-npanday-incubator\bran ches\npanday-uac-removed\plugins\netplugins\NPanday.Plugin.Addin groupId=npanday.plugin artifactId=NPanday.Plugin.Addin artifactVersion=1.2.2-incubating-SNAPSHOT startProcessAssembly=C:\Projects\apache-npanday-incubator\branches\npanday-uac-removed\plugins\netplugins\bin\NPanday.Plugin.MojoGenerator .exe pluginArtifactPath=C:\Projects\apache-npanday-incubator\branches\npanday-uac-removed\plugins\netplugins\bin\NPanday.Plugin.dll, Result = 1 any ideas on which part may be missing? thanks, > Remove the uac and pab directories > -- > > Key: NPANDAY-186 > URL: https://issues.apache.org/jira/browse/NPANDAY-186 > Project: NPanday > Issue Type: Improvement > Components: Repository >Affects Versions: 2.0 >Reporter: Wendy Smoak >Assignee: Joe Ocaba > Fix For: 2.0 > > > As discussed on > http://npanday.codeplex.com/WorkItem/View.aspx?WorkItemId=10557 > brettporter wrote Oct 16 at 7:47 AM > "I think adding configuration parameters to relocate uac and pab is overkill > considering that the time would be better invested in removing their use." > This would allow NPanday to function using only the normal Maven local > repository. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (NPANDAY-186) Remove the uac and pab directories
[ https://issues.apache.org/jira/browse/NPANDAY-186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12921259#action_12921259 ] Joe Ocaba commented on NPANDAY-186: --- Found the issue with the file size zero. There was a problem int he PathUtil.java I'm now experiencing this error, [INFO] Unhandled Exception: System.Resources.MissingManifestResourceException: Could not find any resources appropriate for the specified culture or the neutral culture. Make sure "NPanday.Plugin.MojoGenerator.resources" was correctly embedded or linked into assembly "NPanday.Plugin.MojoGenerator" at compile time, or that all the satellite assemblies required are loadable and fully signed. [INFO]at System.Resources.ResourceManager.InternalGetResourceSet(CultureInfo culture, Boolean createIfNotExists, Boolean tryParents) [INFO]at System.Resources.ResourceManager.InternalGetResourceSet(CultureInfo culture, Boolean createIfNotExists, Boolean tryParents) [INFO]at System.Resources.ResourceManager.InternalGetResourceSet(CultureInfo culture, Boolean createIfNotExists, Boolean tryParents) [INFO]at System.Resources.ResourceManager.GetObject(String name, CultureInfo culture, Boolean wrapUnmanagedMemStream) [INFO]at System.Resources.ResourceManager.GetObject(String name) [INFO]at NPanday.Plugin.MojoGenerator.Generator.BuildPluginProject(AppDomain applicationDomain, FileInfo pluginArtifact, FileInfo outputDirectory, String groupId, String artifactId, String version) [INFO]at NPanday.Plugin.MojoGenerator.Generator.Main(String[] args) NPanday: End Process = 10/15/2010 3:04:24 PM; exit code = -532459699 [INFO] still under the plugins/netplugins module I'll double check the other resource building modules > Remove the uac and pab directories > -- > > Key: NPANDAY-186 > URL: https://issues.apache.org/jira/browse/NPANDAY-186 > Project: NPanday > Issue Type: Improvement > Components: Repository >Affects Versions: 2.0 >Reporter: Wendy Smoak >Assignee: Joe Ocaba > Fix For: 2.0 > > > As discussed on > http://npanday.codeplex.com/WorkItem/View.aspx?WorkItemId=10557 > brettporter wrote Oct 16 at 7:47 AM > "I think adding configuration parameters to relocate uac and pab is overkill > considering that the time would be better invested in removing their use." > This would allow NPanday to function using only the normal Maven local > repository. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (NPANDAY-332) nunit-console results in failure even though when you run nunit-ui there are no failures
nunit-console results in failure even though when you run nunit-ui there are no failures - Key: NPANDAY-332 URL: https://issues.apache.org/jira/browse/NPANDAY-332 Project: NPanday Issue Type: Bug Affects Versions: 2.0 Reporter: Joe Ocaba Assignee: Joe Ocaba Fix For: 2.0 Unhandled Exception: System.ArgumentException: Requested value '2.0.50727' was not found. at System.Enum.Parse(Type enumType, String value, Boolean ignoreCase) at NUnit.Core.RuntimeFramework.Parse(String s) at NUnit.ConsoleRunner.ConsoleUi.MakeTestPackage(ConsoleOptions options) at NUnit.ConsoleRunner.ConsoleUi.Execute(ConsoleOptions options) at NUnit.ConsoleRunner.Runner.Main(String[] args) [INFO] [ERROR] BUILD FAILURE [INFO] [INFO] NPANDAY-1100-007: There are test failures. NPANDAY-040-001: Could not execute: Command = CMD.EXE /X /C nunit-console C:\Projects\apache-npanday-incubator\trunk\dotnet\assemblies\NPanday.Model.Settings\target/test-assemblies\NPanday.Model.Settings-test.dll /xml:C:\Projects\apache-npanday-incubator\trunk\dotnet\assemblies\NPanday.Model.Setting s\target\nunit-reports\TEST-NPanday.Model.Settings-1.2.2-incubating-SNAPSHOT.xml /output:C:\Projects\apache-npanday-incubator\trunk\dotnet\assemblies\NPanday.Model.Settings\target\nunit-reports\TEST-NPanday.Model.Settings-1.2.2-incubating-SNAPSHOT-RESULTS.txt /err:C:\Projects\apache-npanday-incubato r\trunk\dotnet\assemblies\NPanday.Model.Settings\target\nunit-reports\TEST-NPanday.Model.Settings-1.2.2-incubating-SNAPSHOT-ERROR.txt /labels /framework:2.0.50727, Result = -100 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (NPANDAY-186) Remove the uac and pab directories
[ https://issues.apache.org/jira/browse/NPANDAY-186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Ocaba resolved NPANDAY-186. --- Resolution: Fixed Merged UAC and PAB removal branch to trunk. trunk now uses the maven convention repository. However there could be an issue with building Npanday from a fresh repo, because it is no longer being built by an older released version. I think we can avoid this once we can do a release containing this fix. > Remove the uac and pab directories > -- > > Key: NPANDAY-186 > URL: https://issues.apache.org/jira/browse/NPANDAY-186 > Project: NPanday > Issue Type: Improvement > Components: Repository >Affects Versions: 2.0 >Reporter: Wendy Smoak >Assignee: Joe Ocaba > Fix For: 2.0 > > > As discussed on > http://npanday.codeplex.com/WorkItem/View.aspx?WorkItemId=10557 > brettporter wrote Oct 16 at 7:47 AM > "I think adding configuration parameters to relocate uac and pab is overkill > considering that the time would be better invested in removing their use." > This would allow NPanday to function using only the normal Maven local > repository. -- 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-tabpanel&focusedCommentId=12923707#action_12923707 ] Joe Ocaba commented on NPANDAY-333: --- great catch Artem. I'm testing the patch now. > 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: 2.0 >Reporter: Artem Fedorenko > 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] Created: (NPANDAY-334) Update Integration Tests in relation with the .NET 4, VS2010 and UAC & PAB removal enhancements
Update Integration Tests in relation with the .NET 4, VS2010 and UAC & PAB removal enhancements --- Key: NPANDAY-334 URL: https://issues.apache.org/jira/browse/NPANDAY-334 Project: NPanday Issue Type: Task Affects Versions: 2.0 Reporter: Joe Ocaba Assignee: Joe Ocaba Fix For: 2.0 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-335) NPanday on Visual Studio only starts on Debug Mode
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: Joe Ocaba Fix For: 2.0 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] Commented: (NPANDAY-314) Adding a Maven artifact from VS plugin generates NPANDAY-180-017 error
[ https://issues.apache.org/jira/browse/NPANDAY-314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12924825#action_12924825 ] Joe Ocaba commented on NPANDAY-314: --- The groupID generated comes from the company name that was registered on the machine. You can look here http://www.real-knowledge.com/naming.htm on how to change the registered name. Hope this helps, > Adding a Maven artifact from VS plugin generates NPANDAY-180-017 error > -- > > Key: NPANDAY-314 > URL: https://issues.apache.org/jira/browse/NPANDAY-314 > Project: NPanday > Issue Type: Bug >Affects Versions: 2.0 >Reporter: correc00 >Priority: Minor > Fix For: 2.0 > > > When adding a Maven artifact from the VS Plugin the dependency entry in the > pom file cannot be found, the following example illustrates the problem: > The entry below is inserted into the POM when the artifact is added through > the VS plugin > > Solution1 > ClassLibrary1 > 1.0-SNAPSHOT > dotnet-library > > The correct entry required for mvn compile and install requires a "." before > the group Id: > > .Solution1 > ClassLibrary1 > 1.0-SNAPSHOT > dotnet-library > > See attached gif for the actual error. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (NPANDAY-314) Adding a Maven artifact from VS plugin generates NPANDAY-180-017 error
[ https://issues.apache.org/jira/browse/NPANDAY-314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Ocaba updated NPANDAY-314: -- Affects Version/s: 2.0 Fix Version/s: (was: Backlog) 2.0 Assignee: Joe Ocaba > Adding a Maven artifact from VS plugin generates NPANDAY-180-017 error > -- > > Key: NPANDAY-314 > URL: https://issues.apache.org/jira/browse/NPANDAY-314 > Project: NPanday > Issue Type: Bug >Affects Versions: 2.0 >Reporter: correc00 >Assignee: Joe Ocaba >Priority: Minor > Fix For: 2.0 > > > When adding a Maven artifact from the VS Plugin the dependency entry in the > pom file cannot be found, the following example illustrates the problem: > The entry below is inserted into the POM when the artifact is added through > the VS plugin > > Solution1 > ClassLibrary1 > 1.0-SNAPSHOT > dotnet-library > > The correct entry required for mvn compile and install requires a "." before > the group Id: > > .Solution1 > ClassLibrary1 > 1.0-SNAPSHOT > dotnet-library > > See attached gif for the actual error. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (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:comment-tabpanel&focusedCommentId=12924827#action_12924827 ] Joe Ocaba commented on NPANDAY-334: --- There are still some tests that are testing specifics under the former implementation. > 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: 2.0 >Reporter: Joe Ocaba >Assignee: Joe Ocaba > Fix For: 2.0 > > > 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] Commented: (NPANDAY-314) Adding a Maven artifact from VS plugin generates NPANDAY-180-017 error
[ https://issues.apache.org/jira/browse/NPANDAY-314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12924857#action_12924857 ] Joe Ocaba commented on NPANDAY-314: --- I agree that would be a better behavior to use the solution name alone if there is no company name registered. The original use case for the usage of the registered company name was to give automation in the event that the solution name would omit the company name. > Adding a Maven artifact from VS plugin generates NPANDAY-180-017 error > -- > > Key: NPANDAY-314 > URL: https://issues.apache.org/jira/browse/NPANDAY-314 > Project: NPanday > Issue Type: Bug >Affects Versions: 2.0 >Reporter: correc00 >Assignee: Joe Ocaba >Priority: Minor > Fix For: 2.0 > > > When adding a Maven artifact from the VS Plugin the dependency entry in the > pom file cannot be found, the following example illustrates the problem: > The entry below is inserted into the POM when the artifact is added through > the VS plugin > > Solution1 > ClassLibrary1 > 1.0-SNAPSHOT > dotnet-library > > The correct entry required for mvn compile and install requires a "." before > the group Id: > > .Solution1 > ClassLibrary1 > 1.0-SNAPSHOT > dotnet-library > > See attached gif for the actual error. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (NPANDAY-343) Can't successfully build projects (VS 2005 and VS 2008) - Build Error due to Access is denied
[ https://issues.apache.org/jira/browse/NPANDAY-343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Ocaba resolved NPANDAY-343. --- Resolution: Fixed Fix Version/s: 2.0 Fixed the part of the code that tried to log the response file directly to C: > Can't successfully build projects (VS 2005 and VS 2008) - Build Error due to > Access is denied > - > > Key: NPANDAY-343 > URL: https://issues.apache.org/jira/browse/NPANDAY-343 > Project: NPanday > Issue Type: Bug >Reporter: Adelita L. Padilla >Assignee: Joe Ocaba > Fix For: 2.0 > > > Steps to reproduce: > 1) Create a project > 2) Generate a pom > 3) Build the project > Expected Behavior: Project should be built successfully > Actual Behavior: Error when building project: > [INFO] NPANDAY-066-013: Found Vendor = Vendor = MICROSOFT, Vendor Version = > 3.5, Framework Version = 3.5, Executable Paths = > [C:\Windows\Microsoft.NET\Framework64\v3.5, C:\Program > Files\Microsoft.NET\SDK\v2.0 64bit] > [INFO] NPANDAY-068-003: Compiling Artifact: Vendor = MICROSOFT, Language = > MICROSOFT, Assembly Name = C:\Users\apadilla\Documents\Visual Studio > 2008\Projects\ClassLibrary2\ClassLibrary2\target\ClassLibrary2.dll > [INFO] > > [ERROR] BUILD ERROR > [INFO] > > [INFO] NPANDAY-900-006: Unable to Compile: Language = C_SHARP, Vendor = null, > ArtifactType = library, Source Directory = C:\Users\apadilla\Documents\Visual > Studio 2008\Projects\ClassLibrary2\ClassLibrary2 > Embedded error: Error while creating response file for the commands. > c:\responsefile.txt (Access is denied) > This maybe related to the removal of uac. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (NPANDAY-343) Can't successfully build projects (VS 2005 and VS 2008) - Build Error due to Access is denied
[ https://issues.apache.org/jira/browse/NPANDAY-343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Ocaba reassigned NPANDAY-343: - Assignee: Joe Ocaba > Can't successfully build projects (VS 2005 and VS 2008) - Build Error due to > Access is denied > - > > Key: NPANDAY-343 > URL: https://issues.apache.org/jira/browse/NPANDAY-343 > Project: NPanday > Issue Type: Bug >Reporter: Adelita L. Padilla >Assignee: Joe Ocaba > Fix For: 2.0 > > > Steps to reproduce: > 1) Create a project > 2) Generate a pom > 3) Build the project > Expected Behavior: Project should be built successfully > Actual Behavior: Error when building project: > [INFO] NPANDAY-066-013: Found Vendor = Vendor = MICROSOFT, Vendor Version = > 3.5, Framework Version = 3.5, Executable Paths = > [C:\Windows\Microsoft.NET\Framework64\v3.5, C:\Program > Files\Microsoft.NET\SDK\v2.0 64bit] > [INFO] NPANDAY-068-003: Compiling Artifact: Vendor = MICROSOFT, Language = > MICROSOFT, Assembly Name = C:\Users\apadilla\Documents\Visual Studio > 2008\Projects\ClassLibrary2\ClassLibrary2\target\ClassLibrary2.dll > [INFO] > > [ERROR] BUILD ERROR > [INFO] > > [INFO] NPANDAY-900-006: Unable to Compile: Language = C_SHARP, Vendor = null, > ArtifactType = library, Source Directory = C:\Users\apadilla\Documents\Visual > Studio 2008\Projects\ClassLibrary2\ClassLibrary2 > Embedded error: Error while creating response file for the commands. > c:\responsefile.txt (Access is denied) > This maybe related to the removal of uac. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (NPANDAY-332) nunit-console results in failure even though when you run nunit-ui there are no failures
[ https://issues.apache.org/jira/browse/NPANDAY-332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Ocaba updated NPANDAY-332: -- Priority: Minor (was: Major) > nunit-console results in failure even though when you run nunit-ui there are > no failures > - > > Key: NPANDAY-332 > URL: https://issues.apache.org/jira/browse/NPANDAY-332 > Project: NPanday > Issue Type: Bug >Affects Versions: 2.0 >Reporter: Joe Ocaba >Assignee: Joe Ocaba >Priority: Minor > Fix For: 2.0 > > > Unhandled Exception: > System.ArgumentException: Requested value '2.0.50727' was not found. >at System.Enum.Parse(Type enumType, String value, Boolean ignoreCase) >at NUnit.Core.RuntimeFramework.Parse(String s) >at NUnit.ConsoleRunner.ConsoleUi.MakeTestPackage(ConsoleOptions options) >at NUnit.ConsoleRunner.ConsoleUi.Execute(ConsoleOptions options) >at NUnit.ConsoleRunner.Runner.Main(String[] args) > [INFO] > > [ERROR] BUILD FAILURE > [INFO] > > [INFO] NPANDAY-1100-007: There are test failures. > NPANDAY-040-001: Could not execute: Command = CMD.EXE /X /C nunit-console > C:\Projects\apache-npanday-incubator\trunk\dotnet\assemblies\NPanday.Model.Settings\target/test-assemblies\NPanday.Model.Settings-test.dll > > /xml:C:\Projects\apache-npanday-incubator\trunk\dotnet\assemblies\NPanday.Model.Setting > s\target\nunit-reports\TEST-NPanday.Model.Settings-1.2.2-incubating-SNAPSHOT.xml > > /output:C:\Projects\apache-npanday-incubator\trunk\dotnet\assemblies\NPanday.Model.Settings\target\nunit-reports\TEST-NPanday.Model.Settings-1.2.2-incubating-SNAPSHOT-RESULTS.txt > /err:C:\Projects\apache-npanday-incubato > r\trunk\dotnet\assemblies\NPanday.Model.Settings\target\nunit-reports\TEST-NPanday.Model.Settings-1.2.2-incubating-SNAPSHOT-ERROR.txt > /labels /framework:2.0.50727, Result = -100 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (NPANDAY-231) Remove RDF repository and model
[ https://issues.apache.org/jira/browse/NPANDAY-231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Ocaba updated NPANDAY-231: -- Fix Version/s: (was: 2.0) 2.x Bumped to 2.x since it was discussed in the mailing list that we prioritize a release soon and we will include this after 2.0 > Remove RDF repository and model > --- > > Key: NPANDAY-231 > URL: https://issues.apache.org/jira/browse/NPANDAY-231 > Project: NPanday > Issue Type: Bug > Components: Maven Plugins >Reporter: Brett Porter >Priority: Critical > Fix For: 2.x > > > This will be a significant change to the way NPanday works internally, but > should have no external effect. We desire to have it more closely work with > Maven's dependency resolution, as the RDF adds no value and produces a number > of confusing results and error messages. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (NPANDAY-314) Adding a Maven artifact from VS plugin generates NPANDAY-180-017 error
[ https://issues.apache.org/jira/browse/NPANDAY-314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Ocaba updated NPANDAY-314: -- Fix Version/s: (was: 2.0) 2.x > Adding a Maven artifact from VS plugin generates NPANDAY-180-017 error > -- > > Key: NPANDAY-314 > URL: https://issues.apache.org/jira/browse/NPANDAY-314 > Project: NPanday > Issue Type: Bug >Affects Versions: 2.0 >Reporter: correc00 >Assignee: Joe Ocaba >Priority: Minor > Fix For: 2.x > > > When adding a Maven artifact from the VS Plugin the dependency entry in the > pom file cannot be found, the following example illustrates the problem: > The entry below is inserted into the POM when the artifact is added through > the VS plugin > > Solution1 > ClassLibrary1 > 1.0-SNAPSHOT > dotnet-library > > The correct entry required for mvn compile and install requires a "." before > the group Id: > > .Solution1 > ClassLibrary1 > 1.0-SNAPSHOT > dotnet-library > > See attached gif for the actual error. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (NPANDAY-298) 'npanday.plugin:maven-compile-plugin' does not exist or no valid version
[ https://issues.apache.org/jira/browse/NPANDAY-298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Ocaba updated NPANDAY-298: -- Fix Version/s: (was: 2.0) 2.x > 'npanday.plugin:maven-compile-plugin' does not exist or no valid version > > > Key: NPANDAY-298 > URL: https://issues.apache.org/jira/browse/NPANDAY-298 > Project: NPanday > Issue Type: Bug > Components: Maven Plugins >Reporter: asario >Priority: Minor > Fix For: 2.x > > > Hi, I'm very new to NPanday and I have this issue with version 1.1 and also > with the new fresh 1.2. I used the msi installer and checked all path > variables. The installation looks good everythings looks in place for me. But > I'm not be able to run successfully a generated pom. After generating pom for > the default applicaion from Visual Studio 'WindowsFormsApplication1' (simple > seelct new project 'Windows Form Application') I try to compile the project > and receive following build error: 'The plugin > 'npanday.plugin:maven-compile-plugin' does not exist or no valid version > could be found'. > When take a look in the project pom, i see in scetion build - plugins the > plugin maven-compile-plugin without a version tag. If I add a version tag > 1.2 then the next plugin is not found: > maven-resgen-plugin. If I add the version tag also for the > maven-resgen-plugin then the build stop with 'The plugin > 'npanday.plugin:maven-resolver-plugin' does not exist or no valid version > could be found'. This plugin is not added automaticly during the > installation. When i add all needed plugins in the pom the build work (see > attachment). > Do I have add the NPanday plugins manually in all poms in my project? -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (NPANDAY-293) AddIn file created by installer differs from maven-vsinstaller-plugin
[ https://issues.apache.org/jira/browse/NPANDAY-293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Ocaba updated NPANDAY-293: -- Fix Version/s: (was: 2.0) 2.x > AddIn file created by installer differs from maven-vsinstaller-plugin > - > > Key: NPANDAY-293 > URL: https://issues.apache.org/jira/browse/NPANDAY-293 > Project: NPanday > Issue Type: Bug >Reporter: Brett Porter >Priority: Minor > Fix For: 2.x > > > The About box is empty, and the version not displayed, when using the MSI to > install NPanday. This is because the .AddIn file generated in > ~/Documents/Visual Studio 200x/AddIns is different and does not contain the > About Box info and the same description tag. > It would be good if the AddIn got the console version from the assembly > version of the AddIn instead of parsing the description. I'm not sure if > there is an alternative for the About box that would make it available inside > the AddIn DLL instead - maybe as a resource? > If not, then the MSI WiX script generator needs to be changed to create an > identical AddIn file with the additional information. We should also add a > comment or automated way to DRY the info for the AddIn template. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (NPANDAY-290) Improve console output for integration tests
[ https://issues.apache.org/jira/browse/NPANDAY-290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Ocaba updated NPANDAY-290: -- Fix Version/s: (was: 2.0) 2.x > Improve console output for integration tests > > > Key: NPANDAY-290 > URL: https://issues.apache.org/jira/browse/NPANDAY-290 > Project: NPanday > Issue Type: Bug > Components: Maven Plugins >Reporter: Lars Corneliussen >Priority: Minor > Fix For: 2.x > > > Seems like some tests don't do a line feed: > 11695MsBuildCopyReferences(testMsBuildCopyReferences)..11637MsBuildErrorHandling(testMsBuildErrorsHandled)..9903ResGenWithErrorInFileName(testResGenWithErrorInFileName).. > Ok > And sometimes they say "OK" and are later listed as "FAILED". -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (NPANDAY-284) npanday breaks if localRepository is not default
[ https://issues.apache.org/jira/browse/NPANDAY-284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Ocaba updated NPANDAY-284: -- Fix Version/s: (was: 2.0) 2.x > npanday breaks if localRepository is not default > > > Key: NPANDAY-284 > URL: https://issues.apache.org/jira/browse/NPANDAY-284 > Project: NPanday > Issue Type: Bug > Components: Maven Plugins >Reporter: supkichen >Priority: Minor > Fix For: 2.x > > > In several places in the code, ~/.m2/* is hard-coded as the parent of the > maven repository directory. If it isn't, then you end up with two uac > directories, which causes problems. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (NPANDAY-113) Documentation for each Plugin
[ https://issues.apache.org/jira/browse/NPANDAY-113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Ocaba updated NPANDAY-113: -- Fix Version/s: (was: 2.0) 2.x > Documentation for each Plugin > - > > Key: NPANDAY-113 > URL: https://issues.apache.org/jira/browse/NPANDAY-113 > Project: NPanday > Issue Type: Bug > Components: Reference and Documentations >Reporter: Joe Ocaba >Priority: Minor > Fix For: 2.x > > > Very similar to how maven does it. located here > http://maven.apache.org/plugins/maven-deploy-plugin/ -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (NPANDAY-279) Migrate NPanday's dotnet pom's to "dotnet-*" types
[ https://issues.apache.org/jira/browse/NPANDAY-279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Ocaba updated NPANDAY-279: -- Fix Version/s: (was: 2.0) 2.x > Migrate NPanday's dotnet pom's to "dotnet-*" types > -- > > Key: NPANDAY-279 > URL: https://issues.apache.org/jira/browse/NPANDAY-279 > Project: NPanday > Issue Type: Bug > Components: Maven Plugins >Reporter: Lars Corneliussen >Priority: Minor > Fix For: 2.x > > > In NPanday 1.2 the "old" types have been deprecated, but are still supported. > The libs and netplugins that in NPanday itself still use the old types as > "netplugin", "executable" and "library". We should migrate all > packaging-types of the poms, and also all types on dependencies to the new > types. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (NPANDAY-347) compile fails on unix if sources in subfolder
[ https://issues.apache.org/jira/browse/NPANDAY-347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Ocaba updated NPANDAY-347: -- Fix Version/s: 2.0 > compile fails on unix if sources in subfolder > - > > Key: NPANDAY-347 > URL: https://issues.apache.org/jira/browse/NPANDAY-347 > Project: NPanday > Issue Type: Bug >Affects Versions: 1.2.1 > Environment: linux >Reporter: Luca Di Stefano >Priority: Critical > Fix For: 2.0 > > Attachments: dotnet-executable_linuxpath-1.patch > > > if the project contains source files in subfolder, the compiler plugin fails > to copy temporary files because is supposed the path separator is a backslash -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (NPANDAY-337) NPanday unusable under linux
[ https://issues.apache.org/jira/browse/NPANDAY-337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Ocaba updated NPANDAY-337: -- Fix Version/s: 2.0 > NPanday unusable under linux > > > Key: NPANDAY-337 > URL: https://issues.apache.org/jira/browse/NPANDAY-337 > Project: NPanday > Issue Type: Bug > Components: Maven Plugins >Affects Versions: 1.2.1 > Environment: Apache Maven 2.2.1 (rdebian-4) > Java version: 1.6.0_22 > OS name: "linux" version: "2.6.35-22-generic" arch: "amd64" Family: "unix" >Reporter: Vladimir Tsanev >Priority: Critical > Fix For: 2.0 > > Attachments: dotnet-executable.patch > > > Hi, I want integrate npanday in our build process but I have problems using > it under linux. The problems seems to be in the dotneet-executable component > which tries to do some strange escaping and finally fails since the Runtime > implementation parses the command using StringTokenizer which does not > repects any escaping when splititng arguments. so > /bin/sh -c "gmcs @/path/to/my/reposnsefile.rsp" > is actuallly splitted into this four parameters: > /bin/sh > -c > "gmcs > @/path/to/my/reposnsefile.rsp" > Which cannot be interpreted by the shell. > Probably you should leave the plexus commandline shell to take care of > escapeing. > I did not tried this on windows yet, but for linux I provide a patch that > works for me, at least to compile my modules. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (NPANDAY-332) nunit-console results in failure even though when you run nunit-ui there are no failures
[ https://issues.apache.org/jira/browse/NPANDAY-332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Ocaba updated NPANDAY-332: -- Fix Version/s: (was: 2.0) 2.x > nunit-console results in failure even though when you run nunit-ui there are > no failures > - > > Key: NPANDAY-332 > URL: https://issues.apache.org/jira/browse/NPANDAY-332 > Project: NPanday > Issue Type: Bug >Affects Versions: 2.0 >Reporter: Joe Ocaba >Assignee: Joe Ocaba >Priority: Minor > Fix For: 2.x > > > Unhandled Exception: > System.ArgumentException: Requested value '2.0.50727' was not found. >at System.Enum.Parse(Type enumType, String value, Boolean ignoreCase) >at NUnit.Core.RuntimeFramework.Parse(String s) >at NUnit.ConsoleRunner.ConsoleUi.MakeTestPackage(ConsoleOptions options) >at NUnit.ConsoleRunner.ConsoleUi.Execute(ConsoleOptions options) >at NUnit.ConsoleRunner.Runner.Main(String[] args) > [INFO] > > [ERROR] BUILD FAILURE > [INFO] > > [INFO] NPANDAY-1100-007: There are test failures. > NPANDAY-040-001: Could not execute: Command = CMD.EXE /X /C nunit-console > C:\Projects\apache-npanday-incubator\trunk\dotnet\assemblies\NPanday.Model.Settings\target/test-assemblies\NPanday.Model.Settings-test.dll > > /xml:C:\Projects\apache-npanday-incubator\trunk\dotnet\assemblies\NPanday.Model.Setting > s\target\nunit-reports\TEST-NPanday.Model.Settings-1.2.2-incubating-SNAPSHOT.xml > > /output:C:\Projects\apache-npanday-incubator\trunk\dotnet\assemblies\NPanday.Model.Settings\target\nunit-reports\TEST-NPanday.Model.Settings-1.2.2-incubating-SNAPSHOT-RESULTS.txt > /err:C:\Projects\apache-npanday-incubato > r\trunk\dotnet\assemblies\NPanday.Model.Settings\target\nunit-reports\TEST-NPanday.Model.Settings-1.2.2-incubating-SNAPSHOT-ERROR.txt > /labels /framework:2.0.50727, Result = -100 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (NPANDAY-325) Additional parameters for wix-maven-plugin
[ https://issues.apache.org/jira/browse/NPANDAY-325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Ocaba updated NPANDAY-325: -- Fix Version/s: (was: 2.0) 2.x > Additional parameters for wix-maven-plugin > -- > > Key: NPANDAY-325 > URL: https://issues.apache.org/jira/browse/NPANDAY-325 > Project: NPanday > Issue Type: Bug >Reporter: Dmitry L >Assignee: Joe Ocaba >Priority: Minor > Fix For: 2.x > > > Currently this is no parameter for processor architecture (-arch) in > CandleMojo. > Also there are other parameters which are not defined in wix mojos and it > would be inefficient to add all those parameters into wix-maven-plugin one by > one. A single parameter should used to pass additional arguments into > light/candle as is. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (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:comment-tabpanel&focusedCommentId=12930364#action_12930364 ] Joe Ocaba commented on NPANDAY-335: --- I've tried the 1.2 version and placed the Npanday.VisualStudio.Addin.dll alone in an arbitrary directory and it was able to run the addin. I think you could back track on the zero size addin generated by the vsinstaller plugin? > 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: Joe Ocaba > 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] Commented: (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:comment-tabpanel&focusedCommentId=12930621#action_12930621 ] Joe Ocaba commented on NPANDAY-335: --- Hi Adelita, Yup, my bad it did need those dependencies after all. +1 on adding them to a "bin directory" either in my documents or in the program files > 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: Joe Ocaba > 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] Created: (NPANDAY-350) Output Directory is hardcoded to be under 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
Reporter: Joe Ocaba
Assignee: Joe Ocaba
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] 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-tabpanel&focusedCommentId=12933252#action_12933252
]
Joe Ocaba commented on NPANDAY-350:
---
I plan to add the modifications from the compiler plugin since, it has access
to the ${project.build.directory}
> 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
>Reporter: Joe Ocaba
>Assignee: Joe Ocaba
>
> 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] Resolved: (NPANDAY-332) nunit-console results in failure even though when you run nunit-ui there are no failures
[ https://issues.apache.org/jira/browse/NPANDAY-332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Ocaba resolved NPANDAY-332. --- Resolution: Fixed Fix Version/s: (was: 2.x) 2.0 Blocker for NPANDAY-334 Added fix in trunk. There was a problem with the version not getting locating the proper framework argument that was being passed to the NUnit console command. > nunit-console results in failure even though when you run nunit-ui there are > no failures > - > > Key: NPANDAY-332 > URL: https://issues.apache.org/jira/browse/NPANDAY-332 > Project: NPanday > Issue Type: Bug >Affects Versions: 2.0 >Reporter: Joe Ocaba >Assignee: Joe Ocaba >Priority: Minor > Fix For: 2.0 > > > Unhandled Exception: > System.ArgumentException: Requested value '2.0.50727' was not found. >at System.Enum.Parse(Type enumType, String value, Boolean ignoreCase) >at NUnit.Core.RuntimeFramework.Parse(String s) >at NUnit.ConsoleRunner.ConsoleUi.MakeTestPackage(ConsoleOptions options) >at NUnit.ConsoleRunner.ConsoleUi.Execute(ConsoleOptions options) >at NUnit.ConsoleRunner.Runner.Main(String[] args) > [INFO] > > [ERROR] BUILD FAILURE > [INFO] > > [INFO] NPANDAY-1100-007: There are test failures. > NPANDAY-040-001: Could not execute: Command = CMD.EXE /X /C nunit-console > C:\Projects\apache-npanday-incubator\trunk\dotnet\assemblies\NPanday.Model.Settings\target/test-assemblies\NPanday.Model.Settings-test.dll > > /xml:C:\Projects\apache-npanday-incubator\trunk\dotnet\assemblies\NPanday.Model.Setting > s\target\nunit-reports\TEST-NPanday.Model.Settings-1.2.2-incubating-SNAPSHOT.xml > > /output:C:\Projects\apache-npanday-incubator\trunk\dotnet\assemblies\NPanday.Model.Settings\target\nunit-reports\TEST-NPanday.Model.Settings-1.2.2-incubating-SNAPSHOT-RESULTS.txt > /err:C:\Projects\apache-npanday-incubato > r\trunk\dotnet\assemblies\NPanday.Model.Settings\target\nunit-reports\TEST-NPanday.Model.Settings-1.2.2-incubating-SNAPSHOT-ERROR.txt > /labels /framework:2.0.50727, Result = -100 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (NPANDAY-350) Output Directory is hardcoded to be under target.
[
https://issues.apache.org/jira/browse/NPANDAY-350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joe Ocaba updated NPANDAY-350:
--
Affects Version/s: 2.0
Fix Version/s: 2.0
> 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: 2.0
>Reporter: Joe Ocaba
>Assignee: Joe Ocaba
> Fix For: 2.0
>
>
> 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] Created: (NPANDAY-351) NPanday does not respect the configured repository in the pom
NPanday does not respect the configured repository in the pom
-
Key: NPANDAY-351
URL: https://issues.apache.org/jira/browse/NPANDAY-351
Project: NPanday
Issue Type: Bug
Reporter: Joe Ocaba
Assignee: Joe Ocaba
Fix For: 2.0
NPanday can't locate dependencies from the configured repositories in the
pom.xml
i.e.
test
file:${basedir}/test-repo
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (NPANDAY-329) Support for VS2010 WCF Project
[ https://issues.apache.org/jira/browse/NPANDAY-329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Ocaba updated NPANDAY-329: -- Fix Version/s: (was: 2.0) 1.3-incubating > 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: 1.3-incubating > > > 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] Updated: (NPANDAY-330) Support for VS2010 MVC Project
[ https://issues.apache.org/jira/browse/NPANDAY-330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Ocaba updated NPANDAY-330: -- Fix Version/s: (was: 2.0) 1.3-incubating > 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: 1.3-incubating > > > 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] Updated: (NPANDAY-347) compile fails on unix if sources in subfolder
[ https://issues.apache.org/jira/browse/NPANDAY-347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Ocaba updated NPANDAY-347: -- Fix Version/s: (was: 2.0) 1.3-incubating > compile fails on unix if sources in subfolder > - > > Key: NPANDAY-347 > URL: https://issues.apache.org/jira/browse/NPANDAY-347 > Project: NPanday > Issue Type: Bug >Affects Versions: 1.2.1 > Environment: linux >Reporter: Luca Di Stefano >Priority: Critical > Fix For: 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] Updated: (NPANDAY-337) NPanday unusable under linux
[ https://issues.apache.org/jira/browse/NPANDAY-337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Ocaba updated NPANDAY-337: -- Fix Version/s: (was: 2.0) 1.3-incubating > 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] Updated: (NPANDAY-328) Support for VS2010 WPF Project
[ https://issues.apache.org/jira/browse/NPANDAY-328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Ocaba updated NPANDAY-328: -- Fix Version/s: (was: 2.0) 1.3-incubating > 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: 1.3-incubating > > > 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] Updated: (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 ] Joe Ocaba updated NPANDAY-288: -- Fix Version/s: (was: 2.0) 1.3-incubating > 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: 1.3-incubating > > Attachments: vs2010andDotnet4.patch > > > 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 > > 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; > -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (NPANDAY-343) Can't successfully build projects (VS 2005 and VS 2008) - Build Error due to Access is denied
[ https://issues.apache.org/jira/browse/NPANDAY-343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Ocaba updated NPANDAY-343: -- Fix Version/s: (was: 2.0) 1.3-incubating > Can't successfully build projects (VS 2005 and VS 2008) - Build Error due to > Access is denied > - > > Key: NPANDAY-343 > URL: https://issues.apache.org/jira/browse/NPANDAY-343 > Project: NPanday > Issue Type: Bug >Reporter: Adelita L. Padilla >Assignee: Joe Ocaba > Fix For: 1.3-incubating > > > Steps to reproduce: > 1) Create a project > 2) Generate a pom > 3) Build the project > Expected Behavior: Project should be built successfully > Actual Behavior: Error when building project: > [INFO] NPANDAY-066-013: Found Vendor = Vendor = MICROSOFT, Vendor Version = > 3.5, Framework Version = 3.5, Executable Paths = > [C:\Windows\Microsoft.NET\Framework64\v3.5, C:\Program > Files\Microsoft.NET\SDK\v2.0 64bit] > [INFO] NPANDAY-068-003: Compiling Artifact: Vendor = MICROSOFT, Language = > MICROSOFT, Assembly Name = C:\Users\apadilla\Documents\Visual Studio > 2008\Projects\ClassLibrary2\ClassLibrary2\target\ClassLibrary2.dll > [INFO] > > [ERROR] BUILD ERROR > [INFO] > > [INFO] NPANDAY-900-006: Unable to Compile: Language = C_SHARP, Vendor = null, > ArtifactType = library, Source Directory = C:\Users\apadilla\Documents\Visual > Studio 2008\Projects\ClassLibrary2\ClassLibrary2 > Embedded error: Error while creating response file for the commands. > c:\responsefile.txt (Access is denied) > This maybe related to the removal of uac. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (NPANDAY-351) NPanday does not respect the configured repository in the pom
[
https://issues.apache.org/jira/browse/NPANDAY-351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joe Ocaba updated NPANDAY-351:
--
Fix Version/s: (was: 2.0)
1.3-incubating
> NPanday does not respect the configured repository in the pom
> -
>
> Key: NPANDAY-351
> URL: https://issues.apache.org/jira/browse/NPANDAY-351
> Project: NPanday
> Issue Type: Bug
>Reporter: Joe Ocaba
>Assignee: Joe Ocaba
> Fix For: 1.3-incubating
>
>
> NPanday can't locate dependencies from the configured repositories in the
> pom.xml
> i.e.
>
>
> test
> file:${basedir}/test-repo
>
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[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 ] Joe Ocaba updated NPANDAY-334: -- Affects Version/s: (was: 2.0) 1.3-incubating Fix Version/s: (was: 2.0) 1.3-incubating > 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 > > > 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] Updated: (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 ] Joe Ocaba updated NPANDAY-339: -- Fix Version/s: (was: 2.0) 1.3-incubating > 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.lifec
[jira] Updated: (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 ] Joe Ocaba updated NPANDAY-336: -- Fix Version/s: (was: 2.0) 1.3-incubating > 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: 1.3-incubating > > > 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] Updated: (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 ] Joe Ocaba updated NPANDAY-348: -- Fix Version/s: (was: 2.0) 1.3-incubating > 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: 1.3-incubating > > 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] Updated: (NPANDAY-326) misc. improvements
[ https://issues.apache.org/jira/browse/NPANDAY-326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Ocaba updated NPANDAY-326: -- Fix Version/s: (was: 2.0) 1.3-incubating > 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] Updated: (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 ] Joe Ocaba updated NPANDAY-335: -- Affects Version/s: (was: 2.0) 1.3-incubating Fix Version/s: (was: 2.0) 1.3-incubating > 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: 1.3-incubating >Reporter: Joe Ocaba >Assignee: Adelita L. Padilla > Fix For: 1.3-incubating > > 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] Updated: (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 ] Joe Ocaba updated NPANDAY-333: -- Affects Version/s: (was: 2.0) 1.3-incubating Fix Version/s: (was: 2.0) 1.3-incubating > 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-349) NPanday not building resource files correctly
[ https://issues.apache.org/jira/browse/NPANDAY-349?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Ocaba updated NPANDAY-349: -- Fix Version/s: (was: 2.0) 1.3-incubating > 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 >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, > > npanday.plugin > NPanday.Plugin.Msbuild.JavaBinding > true > > > > compile > > > > > As of now, NPanday automatically adds the 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] Updated: (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:all-tabpanel
]
Joe Ocaba updated NPANDAY-350:
--
Affects Version/s: (was: 2.0)
1.3-incubating
Fix Version/s: (was: 2.0)
1.3-incubating
> 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] Updated: (NPANDAY-332) nunit-console results in failure even though when you run nunit-ui there are no failures
[ https://issues.apache.org/jira/browse/NPANDAY-332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Ocaba updated NPANDAY-332: -- Fix Version/s: (was: 2.0) 1.3-incubating > nunit-console results in failure even though when you run nunit-ui there are > no failures > - > > Key: NPANDAY-332 > URL: https://issues.apache.org/jira/browse/NPANDAY-332 > Project: NPanday > Issue Type: Bug >Affects Versions: 2.0 >Reporter: Joe Ocaba >Assignee: Joe Ocaba >Priority: Minor > Fix For: 1.3-incubating > > > Unhandled Exception: > System.ArgumentException: Requested value '2.0.50727' was not found. >at System.Enum.Parse(Type enumType, String value, Boolean ignoreCase) >at NUnit.Core.RuntimeFramework.Parse(String s) >at NUnit.ConsoleRunner.ConsoleUi.MakeTestPackage(ConsoleOptions options) >at NUnit.ConsoleRunner.ConsoleUi.Execute(ConsoleOptions options) >at NUnit.ConsoleRunner.Runner.Main(String[] args) > [INFO] > > [ERROR] BUILD FAILURE > [INFO] > > [INFO] NPANDAY-1100-007: There are test failures. > NPANDAY-040-001: Could not execute: Command = CMD.EXE /X /C nunit-console > C:\Projects\apache-npanday-incubator\trunk\dotnet\assemblies\NPanday.Model.Settings\target/test-assemblies\NPanday.Model.Settings-test.dll > > /xml:C:\Projects\apache-npanday-incubator\trunk\dotnet\assemblies\NPanday.Model.Setting > s\target\nunit-reports\TEST-NPanday.Model.Settings-1.2.2-incubating-SNAPSHOT.xml > > /output:C:\Projects\apache-npanday-incubator\trunk\dotnet\assemblies\NPanday.Model.Settings\target\nunit-reports\TEST-NPanday.Model.Settings-1.2.2-incubating-SNAPSHOT-RESULTS.txt > /err:C:\Projects\apache-npanday-incubato > r\trunk\dotnet\assemblies\NPanday.Model.Settings\target\nunit-reports\TEST-NPanday.Model.Settings-1.2.2-incubating-SNAPSHOT-ERROR.txt > /labels /framework:2.0.50727, Result = -100 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (NPANDAY-186) Remove the uac and pab directories
[ https://issues.apache.org/jira/browse/NPANDAY-186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Ocaba updated NPANDAY-186: -- Fix Version/s: (was: 2.0) 1.3-incubating > Remove the uac and pab directories > -- > > Key: NPANDAY-186 > URL: https://issues.apache.org/jira/browse/NPANDAY-186 > Project: NPanday > Issue Type: Improvement > Components: Repository >Affects Versions: 2.0 >Reporter: Wendy Smoak >Assignee: Joe Ocaba > Fix For: 1.3-incubating > > > As discussed on > http://npanday.codeplex.com/WorkItem/View.aspx?WorkItemId=10557 > brettporter wrote Oct 16 at 7:47 AM > "I think adding configuration parameters to relocate uac and pab is overkill > considering that the time would be better invested in removing their use." > This would allow NPanday to function using only the normal Maven local > repository. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (NPANDAY-342) deploy sources artifacts to npanday asset repo
[ https://issues.apache.org/jira/browse/NPANDAY-342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Ocaba updated NPANDAY-342: -- Fix Version/s: (was: 2.0) 1.3-incubating > deploy sources artifacts to npanday asset repo > -- > > Key: NPANDAY-342 > URL: https://issues.apache.org/jira/browse/NPANDAY-342 > Project: NPanday > Issue Type: Improvement > Components: Repository >Affects Versions: 1.2.1 >Reporter: Luca Di Stefano >Priority: Trivial > Fix For: 1.3-incubating > > > deploy sources artifacts of npanday project in npanday repository. > This is useful for plugin debugging and for contributions -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (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 ] Joe Ocaba updated NPANDAY-341: -- Fix Version/s: (was: 2.0) 1.3-incubating > 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, > /home/luca/Work/egov/trash/dotnet/SharpForgeNPandayTestApp/SharpForgeNP
[jira] Updated: (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 ] Joe Ocaba updated NPANDAY-316: -- Fix Version/s: (was: 2.0) 1.3-incubating > 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: 1.3-incubating > > > 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] 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-tabpanel&focusedCommentId=12966377#action_12966377 ] Joe Ocaba commented on NPANDAY-357: --- Thanks Paul, We will try out your patch and apply it after testing. > 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 > 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-69) NPanday needs to be more synchronized and automated
[ https://issues.apache.org/jira/browse/NPANDAY-69?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Ocaba resolved NPANDAY-69. -- Resolution: Fixed Fix Version/s: (was: Backlog) 1.3-incubating Assignee: Joe Ocaba Fix with NPANDAY-157, NPANDAY-212, NPANDAY-178 > NPanday needs to be more synchronized and automated > --- > > Key: NPANDAY-69 > URL: https://issues.apache.org/jira/browse/NPANDAY-69 > Project: NPanday > Issue Type: Bug >Reporter: Joe Ocaba >Assignee: Joe Ocaba >Priority: Minor > Fix For: 1.3-incubating > > > Each time there is a new addition like a resx or other sources to the > project, it will not be reflected towards the pom and if you would do a re > import the needed tags like scm and the version of the parent tags. > Our final goal would be to have npanday running on the background. All the > user has to do is import the project and if the user has any modifications > done in VS then it should be reflected in the pom. At the moment this is only > applicable with references. > If ever we also need to re import then tags like scm, parents and other > important tags should be preserved. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (NPANDAY-354) Addin 'resync references' feature fails if using remote repositories but there is no 'mirrors' section in Settings.xml file.
[ https://issues.apache.org/jira/browse/NPANDAY-354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Ocaba resolved NPANDAY-354. --- Resolution: Fixed Fix Version/s: 1.3-incubating Assignee: Joe Ocaba Applied patch provided by Paul in trunk. > Addin 'resync references' feature fails if using remote repositories but > there is no 'mirrors' section in Settings.xml file. > > > Key: NPANDAY-354 > URL: https://issues.apache.org/jira/browse/NPANDAY-354 > Project: NPanday > Issue Type: Bug > Components: Visual Studio Add-in >Affects Versions: 1.2.1 > Environment: Windows >Reporter: Paul G >Assignee: Joe Ocaba >Priority: Minor > Fix For: 1.3-incubating > > Attachments: NPANDAY-354.patch > > > ProjectImporterEngine's Reference.cs throws an NPE at line 283 unless > settings.xml has a 'mirrors' section defined. > Woraround: Create an empty 'mirrors' section. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (NPANDAY-351) NPanday does not respect the configured repository in the pom
[
https://issues.apache.org/jira/browse/NPANDAY-351?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joe Ocaba resolved NPANDAY-351.
---
Resolution: Fixed
Fix committed in trunk for 1.3-incubating
Added Artifact Resolver to look up to remote repositories in projectDaoImpl.
> NPanday does not respect the configured repository in the pom
> -
>
> Key: NPANDAY-351
> URL: https://issues.apache.org/jira/browse/NPANDAY-351
> Project: NPanday
> Issue Type: Bug
>Reporter: Joe Ocaba
>Assignee: Joe Ocaba
> Fix For: 1.3-incubating
>
>
> NPanday can't locate dependencies from the configured repositories in the
> pom.xml
> i.e.
>
>
> test
> file:${basedir}/test-repo
>
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (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 ] Joe Ocaba resolved NPANDAY-334. --- Resolution: Fixed Updated ITs, everything is building successfully now. There were configuration issues that were also causing the error like: * Which .NET framework was set first in the Environment Path * $(MSBuildBinPath)\Microsoft.WinFX.targets should be added on the project file so that it can be recognized as a WPF project * nunit-console version If there are users which will have failures on some of the ITs it could be caused by these configs on the user's machine. 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] Commented: (NPANDAY-354) Addin 'resync references' feature fails if using remote repositories but there is no 'mirrors' section in Settings.xml file.
[ https://issues.apache.org/jira/browse/NPANDAY-354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12977589#action_12977589 ] Joe Ocaba commented on NPANDAY-354: --- The changes are there and yup you are pointing at the correct location. Maybe you can do another checkout? or and svn clean up then update? > Addin 'resync references' feature fails if using remote repositories but > there is no 'mirrors' section in Settings.xml file. > > > Key: NPANDAY-354 > URL: https://issues.apache.org/jira/browse/NPANDAY-354 > Project: NPanday > Issue Type: Bug > Components: Visual Studio Add-in >Affects Versions: 1.2.1 > Environment: Windows >Reporter: Paul G >Assignee: Joe Ocaba >Priority: Minor > Fix For: 1.3-incubating > > Attachments: NPANDAY-354.patch > > > ProjectImporterEngine's Reference.cs throws an NPE at line 283 unless > settings.xml has a 'mirrors' section defined. > Woraround: Create an empty 'mirrors' section. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (NPANDAY-362) npanday-settings.xml in local repository is not overwritten on a new install of npanday.
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 Priority: Minor npanday-settings.xml should reflect the correct version of frameworks in the path. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (NPANDAY-342) deploy sources artifacts to npanday asset repo
[ https://issues.apache.org/jira/browse/NPANDAY-342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Ocaba reassigned NPANDAY-342: - Assignee: Joe Ocaba > deploy sources artifacts to npanday asset repo > -- > > Key: NPANDAY-342 > URL: https://issues.apache.org/jira/browse/NPANDAY-342 > Project: NPanday > Issue Type: Improvement > Components: Repository >Affects Versions: 1.2.1 >Reporter: Luca Di Stefano >Assignee: Joe Ocaba >Priority: Trivial > Fix For: 1.3-incubating > > > deploy sources artifacts of npanday project in npanday repository. > This is useful for plugin debugging and for contributions -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (NPANDAY-356) Addin 'resync references' feature fails to download latest SNAPSHOT from remote repo if older snapshot file already exists locally.
[
https://issues.apache.org/jira/browse/NPANDAY-356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joe Ocaba resolved NPANDAY-356.
---
Resolution: Fixed
Assignee: Joe Ocaba
Applied patch in trunk.
> Addin 'resync references' feature fails to download latest SNAPSHOT from
> remote repo if older snapshot file already exists locally.
> ---
>
> Key: NPANDAY-356
> URL: https://issues.apache.org/jira/browse/NPANDAY-356
> Project: NPanday
> Issue Type: Bug
> Components: Visual Studio Add-in
>Affects Versions: 1.2.1
> Environment: Windows
>Reporter: Paul G
>Assignee: Joe Ocaba
> Fix For: 1.3-incubating
>
> Attachments: NPANDAY-356.patch
>
>
> The VisualStudio.Addin's ReferenceManager.cs simply checks for the presence
> of a snapshot artifact file in the local repo, and if it's present it copies
> it to the project's reference folder. No attempt to check the remote snapshot
> state
> To fix this I did the following:
> In ReferenceManager.cs line 94, replace:
> if (!artifact.FileInfo.Exists)
> with
> if (!artifact.FileInfo.Exists || artifact.Version.EndsWith("SNAPSHOT"))
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (NPANDAY-342) deploy sources artifacts to npanday asset repo
[ https://issues.apache.org/jira/browse/NPANDAY-342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Ocaba resolved NPANDAY-342. --- Resolution: Fixed Deployed the artifacts and also added the maven-source-plugin in the npanday-release profile > deploy sources artifacts to npanday asset repo > -- > > Key: NPANDAY-342 > URL: https://issues.apache.org/jira/browse/NPANDAY-342 > Project: NPanday > Issue Type: Improvement > Components: Repository >Affects Versions: 1.2.1 >Reporter: Luca Di Stefano >Assignee: Joe Ocaba >Priority: Trivial > Fix For: 1.3-incubating > > > deploy sources artifacts of npanday project in npanday repository. > This is useful for plugin debugging and for contributions -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (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:comment-tabpanel&focusedCommentId=12981600#action_12981600 ] Joe Ocaba commented on NPANDAY-363: --- The supported behavior was "Add Web Reference" and not add "Add Service Reference". In VS2010 the "Add Web Reference" is not easily visible as before in VS2008. In order to view the "Add Web Reference" in VS2010 you have to click on "Add Service Reference" > click on Advance > from here you can now see the "Add Web Reference" button. So this isn't a regression, since this hasn't been supported yet. We could add this as a feature enhancement and maybe include it in 2.0? > 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 > > 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: > Service%20References/ServiceReference1/Reference.cs > has been added in tag in the pom.xml file of the project > 5. Remove the Service Reference > Actual Result: > Service%20References/ServiceReference1/Reference.cs > 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. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (NPANDAY-231) Remove RDF repository and model
[ https://issues.apache.org/jira/browse/NPANDAY-231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Ocaba reassigned NPANDAY-231: - Assignee: Joe Ocaba > Remove RDF repository and model > --- > > Key: NPANDAY-231 > URL: https://issues.apache.org/jira/browse/NPANDAY-231 > Project: NPanday > Issue Type: Bug > Components: Maven Plugins >Reporter: Brett Porter >Assignee: Joe Ocaba >Priority: Critical > Fix For: 2.0 > > > This will be a significant change to the way NPanday works internally, but > should have no external effect. We desire to have it more closely work with > Maven's dependency resolution, as the RDF adds no value and produces a number > of confusing results and error messages. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (NPANDAY-231) Remove RDF repository and model
[ https://issues.apache.org/jira/browse/NPANDAY-231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12994185#comment-12994185 ] Joe Ocaba commented on NPANDAY-231: --- I was planning on removing the repositoryConverter its IMPL and IT and replace the stub portion of that in the ProjectDaoImpl, and leave the model part for now. > Remove RDF repository and model > --- > > Key: NPANDAY-231 > URL: https://issues.apache.org/jira/browse/NPANDAY-231 > Project: NPanday > Issue Type: Bug > Components: Maven Plugins >Reporter: Brett Porter >Assignee: Joe Ocaba >Priority: Critical > Fix For: 2.0 > > > This will be a significant change to the way NPanday works internally, but > should have no external effect. We desire to have it more closely work with > Maven's dependency resolution, as the RDF adds no value and produces a number > of confusing results and error messages. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Resolved: (NPANDAY-314) Adding a Maven artifact from VS plugin generates NPANDAY-180-017 error
[ https://issues.apache.org/jira/browse/NPANDAY-314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Ocaba resolved NPANDAY-314. --- Resolution: Fixed Fixed in trunk, behavior now changed as discussed in the issue. note: in VS2010 Microsoft is automatically added if there is company name registered is blank. > Adding a Maven artifact from VS plugin generates NPANDAY-180-017 error > -- > > Key: NPANDAY-314 > URL: https://issues.apache.org/jira/browse/NPANDAY-314 > Project: NPanday > Issue Type: Bug >Affects Versions: 1.3-incubating >Reporter: correc00 >Assignee: Joe Ocaba >Priority: Minor > Fix For: 2.0 > > > When adding a Maven artifact from the VS Plugin the dependency entry in the > pom file cannot be found, the following example illustrates the problem: > The entry below is inserted into the POM when the artifact is added through > the VS plugin > > Solution1 > ClassLibrary1 > 1.0-SNAPSHOT > dotnet-library > > The correct entry required for mvn compile and install requires a "." before > the group Id: > > .Solution1 > ClassLibrary1 > 1.0-SNAPSHOT > dotnet-library > > See attached gif for the actual error. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (NPANDAY-375) When building an executable project, by default it is not executable from target
When building an executable project, by default it is not executable from target
Key: NPANDAY-375
URL: https://issues.apache.org/jira/browse/NPANDAY-375
Project: NPanday
Issue Type: Improvement
Components: Maven Plugins
Affects Versions: 1.3-incubating
Reporter: Joe Ocaba
Fix For: 2.0
Since the dependencies are not in the target directory the exe file will not
run successfully. As proposed solution by Lars in the devlist would be to use
the maven-dependency-plugin. We could automate the adding of the plugin on
executable project types.
org.apache.maven.plugins
maven-dependency-plugin
2.2
copy-dependencies
package
copy-dependencies
${project.build.directory}
true
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (NPANDAY-375) When building an executable project, by default it is not executable from target
[
https://issues.apache.org/jira/browse/NPANDAY-375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13001311#comment-13001311
]
Joe Ocaba commented on NPANDAY-375:
---
I mean to add the plugin in the project's pom.xml automatically. Like what we
do with aspx projects and wpf projects.
> When building an executable project, by default it is not executable from
> target
>
>
> Key: NPANDAY-375
> URL: https://issues.apache.org/jira/browse/NPANDAY-375
> Project: NPanday
> Issue Type: Improvement
> Components: Maven Plugins
>Affects Versions: 1.3-incubating
>Reporter: Joe Ocaba
> Fix For: 2.0
>
>
> Since the dependencies are not in the target directory the exe file will not
> run successfully. As proposed solution by Lars in the devlist would be to use
> the maven-dependency-plugin. We could automate the adding of the plugin on
> executable project types.
>
> org.apache.maven.plugins
> maven-dependency-plugin
> 2.2
>
>
>copy-dependencies
>package
>
> copy-dependencies
>
>
> ${project.build.directory}
> true
>
>
>
>
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Resolved: (NPANDAY-325) Additional parameters for wix-maven-plugin
[ https://issues.apache.org/jira/browse/NPANDAY-325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Ocaba resolved NPANDAY-325. --- Resolution: Fixed Applied patch as submitted by Dmitry L from http://npanday.codeplex.com/workitem/14105 > Additional parameters for wix-maven-plugin > -- > > Key: NPANDAY-325 > URL: https://issues.apache.org/jira/browse/NPANDAY-325 > Project: NPanday > Issue Type: Bug >Reporter: Dmitry L >Assignee: Joe Ocaba >Priority: Minor > Fix For: 2.0 > > > Currently this is no parameter for processor architecture (-arch) in > CandleMojo. > Also there are other parameters which are not defined in wix mojos and it > would be inefficient to add all those parameters into wix-maven-plugin one by > one. A single parameter should used to pass additional arguments into > light/candle as is. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (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 ] Joe Ocaba updated NPANDAY-362: -- Fix Version/s: (was: 2.0) 1.3.1-incubating > 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: 1.3.1-incubating > > > 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] Updated: (NPANDAY-373) Custom Lifecycle Plugin does not bind the produced artifact
[
https://issues.apache.org/jira/browse/NPANDAY-373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joe Ocaba updated NPANDAY-373:
--
Fix Version/s: (was: 2.0)
1.3.1-incubating
> Custom Lifecycle Plugin does not bind the produced artifact
> ---
>
> Key: NPANDAY-373
> URL: https://issues.apache.org/jira/browse/NPANDAY-373
> Project: NPanday
> Issue Type: Bug
> Components: Maven Plugins
>Affects Versions: 1.2, 1.2.1
>Reporter: Lars Corneliussen
>Assignee: Lars Corneliussen
> Fix For: 1.3.1-incubating
>
> Original Estimate: 2h
> Remaining Estimate: 2h
>
> When building the sources using the custom lifecycle plugin, the produced
> main artifact is not bound to ${project.file}
> This results in an error when trying to install:
> {noformat}
> [ERROR] BUILD ERROR
> [INFO]
>
> [INFO] The packaging for this project did not assign a file to the build
> artifact
> {noformat}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (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 ] Joe Ocaba updated NPANDAY-363: -- Fix Version/s: (was: 2.0) 1.3.1-incubating > 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: 1.3.1-incubating > > > 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: > Service%20References/ServiceReference1/Reference.cs > has been added in tag in the pom.xml file of the project > 5. Remove the Service Reference > Actual Result: > Service%20References/ServiceReference1/Reference.cs > 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] 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 ] Joe Ocaba updated NPANDAY-367: -- Affects Version/s: 1.3-incubating Fix Version/s: (was: 2.0) 1.3.1-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 >Affects Versions: 1.3-incubating >Reporter: Adelita L. Padilla >Assignee: Adelita L. Padilla > Fix For: 1.3.1-incubating > > > 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] Updated: (NPANDAY-325) Additional parameters for wix-maven-plugin
[ https://issues.apache.org/jira/browse/NPANDAY-325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Ocaba updated NPANDAY-325: -- Affects Version/s: 1.2.1 Fix Version/s: (was: 2.0) 1.3.1-incubating > Additional parameters for wix-maven-plugin > -- > > Key: NPANDAY-325 > URL: https://issues.apache.org/jira/browse/NPANDAY-325 > Project: NPanday > Issue Type: Bug >Affects Versions: 1.2.1 >Reporter: Dmitry L >Assignee: Joe Ocaba >Priority: Minor > Fix For: 1.3.1-incubating > > > Currently this is no parameter for processor architecture (-arch) in > CandleMojo. > Also there are other parameters which are not defined in wix mojos and it > would be inefficient to add all those parameters into wix-maven-plugin one by > one. A single parameter should used to pass additional arguments into > light/candle as is. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (NPANDAY-376) Intermittent error caused by updating npanday-settings.xml
[ https://issues.apache.org/jira/browse/NPANDAY-376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Ocaba updated NPANDAY-376: -- Affects Version/s: (was: 1.3-incubating) Fix Version/s: 1.3.1-incubating > Intermittent error caused by updating npanday-settings.xml > --- > > Key: NPANDAY-376 > URL: https://issues.apache.org/jira/browse/NPANDAY-376 > Project: NPanday > Issue Type: Bug >Reporter: Adelita L. Padilla >Assignee: Adelita L. Padilla >Priority: Minor > Fix For: 1.3.1-incubating > > > Steps to Reproduce: > 1) Delete npanday-settings.xml > 2) Build project. > Actual Behavior: Build error cause it's unable to locate the Executable path > Expected Behavior: Build should be successful since npanday-settings.xml is > already generated. > Workaround: Build project again. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (NPANDAY-361) Configurable .M2 Folder and npanday-settings.xml lookup
[ https://issues.apache.org/jira/browse/NPANDAY-361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Ocaba updated NPANDAY-361: -- Fix Version/s: (was: 2.0) 1.3.1-incubating > Configurable .M2 Folder and npanday-settings.xml lookup > --- > > Key: NPANDAY-361 > URL: https://issues.apache.org/jira/browse/NPANDAY-361 > Project: NPanday > Issue Type: Bug > Components: Maven Plugins >Affects Versions: 1.2.1 > Environment: Windows Server 2008 64 bit, Tomcat Hudson >Reporter: Terence Mill >Assignee: Adelita L. Padilla > Fix For: 1.3.1-incubating > > > We are trying to build our software projects with npanday on CI hudson server > on windows server 2008, while hudson runs as system user. > The ndpanday plugin uses hard coded Local Maven Repository path and ignores > our Maven settings.xml property defined via xml property > The Plugin searches npanday-settings.xml at system user folder instead of > searching in path. > We can't and don't want create directory at this place and the server must > run on system account. There is a thread ( > http://npanday.codeplex.com/Thread/View.aspx?ThreadId=214981 ) also disussing > the problem and already indentified one occourence of fixed path usage in > code (http://npanday.codeplex.com/SourceControl/changeset/view/60509#432200 > Line 43) . > The error we get is this one: > [ERROR] Unhandled Exception: System.IO.DirectoryNotFoundException: Could not > find a part of the path > 'C:\Windows\system32\config\systemprofile\.m2\npanday-settings.xml' > A solution would be to use the as base path for lookup or > better to let use define a property in Maven settings.xml (global/or use) > wher to search npanday specific configuration files. > Even better would be to include the sdk and framework path settings as > profile properties in Maven the settings.xml, for exmaple like is done for > Sonar .Net integration: > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; > xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.0.0 > http://maven.apache.org/xsd/settings-1.0.0.xsd";> > C:/srv/usrhome/maven/repository > false > > > Nexus > Nexus Public Mirror > > https://server.com/nexus/content/groups/public > * > > > > > dotnet > > false > > > > > > C:/srv/DOTNet/Microsoft.NET/Framework/v2.0.50727 > > C:/srv/DOTNet/Microsoft.NET/Framework/v3.5 > > C:/WINDOWS/Microsoft.NET/Framework/v4.0.30319 > > > C:/Program Files > (x86)/Reference > > Assemblies/Microsoft/Framework/Silverlight/v3.0 > C:/Program Files > (x86)/Reference > > Assemblies/Microsoft/Framework/Silverlight/v4.0 > > > C:/srv/DOTNet/GallioBundle-3.2.603.0 > > C:/srv/DOTNet/Microsoft > Fxcop_10.0 > > > C:/srv/DOTNet/PartCover4 > > > C:/srv/DOTNet/SourceMonitor2.63 > > > > > > I then can compile the project via "mvn clean compile -Pdotnet" -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (NPANDAY-314) Adding a Maven artifact from VS plugin generates NPANDAY-180-017 error
[ https://issues.apache.org/jira/browse/NPANDAY-314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Ocaba updated NPANDAY-314: -- Affects Version/s: 1.2.1 Fix Version/s: (was: 2.0) 1.3.1-incubating > Adding a Maven artifact from VS plugin generates NPANDAY-180-017 error > -- > > Key: NPANDAY-314 > URL: https://issues.apache.org/jira/browse/NPANDAY-314 > Project: NPanday > Issue Type: Bug >Affects Versions: 1.2.1, 1.3-incubating >Reporter: correc00 >Assignee: Joe Ocaba >Priority: Minor > Fix For: 1.3.1-incubating > > > When adding a Maven artifact from the VS Plugin the dependency entry in the > pom file cannot be found, the following example illustrates the problem: > The entry below is inserted into the POM when the artifact is added through > the VS plugin > > Solution1 > ClassLibrary1 > 1.0-SNAPSHOT > dotnet-library > > The correct entry required for mvn compile and install requires a "." before > the group Id: > > .Solution1 > ClassLibrary1 > 1.0-SNAPSHOT > dotnet-library > > See attached gif for the actual error. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (NPANDAY-231) Remove RDF repository and model
[ https://issues.apache.org/jira/browse/NPANDAY-231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13004941#comment-13004941 ] Joe Ocaba commented on NPANDAY-231: --- RE Added some repository converter, after continued work on the removal of the model it was still looking up for a repository convert, changed implementation from using rdf. There are a lot of tests that are still failing on the https://svn.apache.org/repos/asf/incubator/npanday/branches/rdf-model-removal branch due to the major behavior changes. > Remove RDF repository and model > --- > > Key: NPANDAY-231 > URL: https://issues.apache.org/jira/browse/NPANDAY-231 > Project: NPanday > Issue Type: Bug > Components: Maven Plugins >Reporter: Brett Porter >Assignee: Joe Ocaba >Priority: Critical > Fix For: 2.0 > > > This will be a significant change to the way NPanday works internally, but > should have no external effect. We desire to have it more closely work with > Maven's dependency resolution, as the RDF adds no value and produces a number > of confusing results and error messages. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (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
]
Joe Ocaba updated NPANDAY-377:
--
Description:
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).
was:
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).
Fix Version/s: 1.3.1-incubating
> 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
>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] [Assigned] (NPANDAY-123) PATH should not have to be set for both Visual Studio AddIn or mvn command-line to function
[ https://issues.apache.org/jira/browse/NPANDAY-123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Ocaba reassigned NPANDAY-123: - Assignee: Joe Ocaba > PATH should not have to be set for both Visual Studio AddIn or mvn > command-line to function > --- > > Key: NPANDAY-123 > URL: https://issues.apache.org/jira/browse/NPANDAY-123 > Project: NPanday > Issue Type: Bug >Reporter: Brett Porter >Assignee: Joe Ocaba >Priority: Minor > Fix For: 1.3.1-incubating > > > some utilities are called from within the assemblies - such as gacutil (see > item #9904) - assuming that they are on the path. However, the default > configuration for the Visual Studio application does not establish that. To > minimise configuration for new users, the application should be able to > locate the framework paths and construct full paths to such executables. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (NPANDAY-382) Add Unique NPanday Numbers to thrown Errors for easier diagnostics
Add Unique NPanday Numbers to thrown Errors for easier diagnostics -- Key: NPANDAY-382 URL: https://issues.apache.org/jira/browse/NPANDAY-382 Project: NPanday Issue Type: Improvement Affects Versions: 1.3-incubating, 1.3.1-incubating Reporter: Joe Ocaba Priority: Minor Fix For: 2.0 There are already some Unique numbers but there are also some errors that are just plain texts. Adding in the unique number would be better. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (NPANDAY-123) PATH should not have to be set for both Visual Studio AddIn or mvn command-line to function
[ https://issues.apache.org/jira/browse/NPANDAY-123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Ocaba resolved NPANDAY-123. --- Resolution: Fixed Fixed in trunk. Added a default value for NetHome so that gacutil and xsd are no longer needed to be set in the environment Path > PATH should not have to be set for both Visual Studio AddIn or mvn > command-line to function > --- > > Key: NPANDAY-123 > URL: https://issues.apache.org/jira/browse/NPANDAY-123 > Project: NPanday > Issue Type: Bug >Reporter: Brett Porter >Assignee: Joe Ocaba >Priority: Minor > Fix For: 1.3.1-incubating > > > some utilities are called from within the assemblies - such as gacutil (see > item #9904) - assuming that they are on the path. However, the default > configuration for the Visual Studio application does not establish that. To > minimise configuration for new users, the application should be able to > locate the framework paths and construct full paths to such executables. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (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:comment-tabpanel&focusedCommentId=13010582#comment-13010582
]
Joe Ocaba commented on NPANDAY-377:
---
I can build on trunk successfully with the revision.
Maybe its a configuration issue with settings.xml?
> 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] [Assigned] (NPANDAY-380) IndexOutOfRangeExcpetion in SettingsGeneratorMojo.GetVendorsFromMicrosoft
[ https://issues.apache.org/jira/browse/NPANDAY-380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Ocaba reassigned NPANDAY-380: - Assignee: Joe Ocaba > IndexOutOfRangeExcpetion in SettingsGeneratorMojo.GetVendorsFromMicrosoft > - > > Key: NPANDAY-380 > URL: https://issues.apache.org/jira/browse/NPANDAY-380 > Project: NPanday > Issue Type: Bug > Components: Maven Plugins >Affects Versions: 1.3-incubating > Environment: Windows 7 Pro, 32-bit. Visual Studio 2010. Maven 3.0.2, > JDK 1.6.0_22 >Reporter: Peter Johnson >Assignee: Joe Ocaba > Fix For: 1.3.1-incubating > > > I created a simple project using the maven-archetype-dotnet-simple archetype. > Without making any changes I attempted to build the project via "mvn > package". Got this error: > Exception occcurred: System.IndexOutOfRangeException: Index was outside the > bounds of the array. >at > NPanday.Plugin.Settings.SettingsGeneratorMojo.GetVendorsForMicrosoft(RegistryKey > microsoftRegistryKey) >at NPanday.Plugin.Settings.SettingsGeneratorMojo.Execute() >at NPanday.Plugin.AbstractMojo.Execute() >at NPanday.Plugin.Loader.PluginLoader.Main(String[] args) > Examining the method in question, it appears that the "vendors" array is > being initialized to have 4 entries (line 189), and then the code attempts to > fill it with 5 entries if all 5 versions of the .Net Framework on the machine. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (NPANDAY-380) IndexOutOfRangeExcpetion in SettingsGeneratorMojo.GetVendorsFromMicrosoft
[ https://issues.apache.org/jira/browse/NPANDAY-380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Ocaba updated NPANDAY-380: -- Fix Version/s: 1.3.1-incubating > IndexOutOfRangeExcpetion in SettingsGeneratorMojo.GetVendorsFromMicrosoft > - > > Key: NPANDAY-380 > URL: https://issues.apache.org/jira/browse/NPANDAY-380 > Project: NPanday > Issue Type: Bug > Components: Maven Plugins >Affects Versions: 1.3-incubating > Environment: Windows 7 Pro, 32-bit. Visual Studio 2010. Maven 3.0.2, > JDK 1.6.0_22 >Reporter: Peter Johnson > Fix For: 1.3.1-incubating > > > I created a simple project using the maven-archetype-dotnet-simple archetype. > Without making any changes I attempted to build the project via "mvn > package". Got this error: > Exception occcurred: System.IndexOutOfRangeException: Index was outside the > bounds of the array. >at > NPanday.Plugin.Settings.SettingsGeneratorMojo.GetVendorsForMicrosoft(RegistryKey > microsoftRegistryKey) >at NPanday.Plugin.Settings.SettingsGeneratorMojo.Execute() >at NPanday.Plugin.AbstractMojo.Execute() >at NPanday.Plugin.Loader.PluginLoader.Main(String[] args) > Examining the method in question, it appears that the "vendors" array is > being initialized to have 4 entries (line 189), and then the code attempts to > fill it with 5 entries if all 5 versions of the .Net Framework on the machine. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (NPANDAY-383) update groupID to org.apache.npanday
[ https://issues.apache.org/jira/browse/NPANDAY-383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Ocaba updated NPANDAY-383: -- Fix Version/s: 1.3.1-incubating > 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 > Fix For: 1.3.1-incubating > > > 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] [Created] (NPANDAY-387) Improve the checking of the mirror repos in Reference.cs for artifact resync
Improve the checking of the mirror repos in Reference.cs for artifact resync
Key: NPANDAY-387
URL: https://issues.apache.org/jira/browse/NPANDAY-387
Project: NPanday
Issue Type: Improvement
Components: Project Importer
Affects Versions: 1.2.1
Reporter: Joe Ocaba
foreach (Mirror mirror in settings.mirrors)
{
string id = mirror.mirrorOf;
->>> if (id == "external:*")
id = "*";
// TODO: support '!' syntax
mirrors.Add(id, mirror.url);
}
change the condition to start of instead of exact match
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (NPANDAY-387) Improve the checking of the mirror repos in Reference.cs for artifact resync
[
https://issues.apache.org/jira/browse/NPANDAY-387?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joe Ocaba updated NPANDAY-387:
--
Fix Version/s: 1.3.1-incubating
> Improve the checking of the mirror repos in Reference.cs for artifact resync
>
>
> Key: NPANDAY-387
> URL: https://issues.apache.org/jira/browse/NPANDAY-387
> Project: NPanday
> Issue Type: Improvement
> Components: Project Importer
>Affects Versions: 1.2.1
>Reporter: Joe Ocaba
> Fix For: 1.3.1-incubating
>
>
> foreach (Mirror mirror in settings.mirrors)
> {
>string id = mirror.mirrorOf;
> ->>> if (id == "external:*")
> id = "*";
>// TODO: support '!' syntax
>mirrors.Add(id, mirror.url);
> }
> change the condition to start of instead of exact match
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (NPANDAY-390) Automated Builds, Testing and Deployment for Artifacts and trunk (Continuous Integration)
[ https://issues.apache.org/jira/browse/NPANDAY-390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joe Ocaba reassigned NPANDAY-390: - Assignee: Joe Ocaba > Automated Builds, Testing and Deployment for Artifacts and trunk (Continuous > Integration) > - > > Key: NPANDAY-390 > URL: https://issues.apache.org/jira/browse/NPANDAY-390 > Project: NPanday > Issue Type: Improvement > Components: Development Setup >Reporter: Lars Corneliussen >Assignee: Joe Ocaba > Labels: deployment, release > Fix For: 1.3.2-incubating > > > I think it is important to have CI back running again before we release the > first Apache Incubator version. > This includes deployment of documentation and artifacts to our > snapshot-repository. > Also build failures should be sent to the dev-list. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (NPANDAY-390) Automated Builds, Testing and Deployment for Artifacts and trunk (Continuous Integration)
[ https://issues.apache.org/jira/browse/NPANDAY-390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13019063#comment-13019063 ] Joe Ocaba commented on NPANDAY-390: --- Started on adding npanday in https://builds.apache.org/hudson/ We just need to agree on the configuration that NPanday will be running on: Maven version: (Maven 2.x or Maven 3.x) Java version: (1.6 above as is indicated in the documentation) Nunit version: (2.5.7 or greater) Wix version (3.0.5419.0) Visual Studios: (VS 2005, VS2008, VS2010) .Net Frameworks: 2.0, 3.5, 4.0 If there are other configurations that you think we should have our ci follow please post here. > Automated Builds, Testing and Deployment for Artifacts and trunk (Continuous > Integration) > - > > Key: NPANDAY-390 > URL: https://issues.apache.org/jira/browse/NPANDAY-390 > Project: NPanday > Issue Type: Improvement > Components: Development Setup >Reporter: Lars Corneliussen >Assignee: Joe Ocaba > Labels: deployment, release > Fix For: 1.3.2-incubating > > > I think it is important to have CI back running again before we release the > first Apache Incubator version. > This includes deployment of documentation and artifacts to our > snapshot-repository. > Also build failures should be sent to the dev-list. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (NPANDAY-399) UAC and PAB Removal Refactor
UAC and PAB Removal Refactor Key: NPANDAY-399 URL: https://issues.apache.org/jira/browse/NPANDAY-399 Project: NPanday Issue Type: Improvement Reporter: Joe Ocaba Assignee: Joe Ocaba Fix For: 1.3.2-incubating Refer to thread on dev mail: outstanding commit questions -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (NPANDAY-398) MojoGenerator can't generate .NET-Mojos referencing a newer NPanday.Plugin.dll
[
https://issues.apache.org/jira/browse/NPANDAY-398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joe Ocaba reassigned NPANDAY-398:
-
Assignee: Joe Ocaba
> MojoGenerator can't generate .NET-Mojos referencing a newer NPanday.Plugin.dll
> --
>
> Key: NPANDAY-398
> URL: https://issues.apache.org/jira/browse/NPANDAY-398
> Project: NPanday
> Issue Type: Bug
> Components: Maven Plugins
>Affects Versions: 1.3.1-incubating
>Reporter: Lars Corneliussen
>Assignee: Joe Ocaba
> Fix For: 1.3.1-incubating
>
>
> When building NPanday against a released version (e.g. trunk ->
> 1.3-incubating), there is a problem generating Mojos.
> The .NET-based Plugins we release should reference NPanday.Plugin.dll from
> the reactor using ${project.version} - in the current case
> 1.3.1-incubating-SNAPSHOT. But then the MojoGenerator is used from the
> bootstrap-version (1.3-incubating). This one also references (is compiled
> against) NPanday.Plugin of 1.3-incubating.
> Now, since NPanday.Plugin is strong-named the "old" MojoGenerator reflects on
> the "new" .NET-based Mojos and runs into a version conflict.
> In order to fix this, we have to relax the versioning in MojoGenerator by
> listening to AppDomain.AssemblyResolve event and help finding the right
> version.
> I'm not sure if we can "downgrade" the version for the Plugin reference, or
> if we need to load the newer NPanday.Plugin into the AppDomain and use that
> instead.
> {code}
> NPanday: Start Process = 12.04.2011 09:38:38
> "targetAssemblyFile=C:\Workbench\NPanday\svn-trunk\plugins\netplugins\NPanday.Plugin.Addin\target\NPanday.Plugin.Addin.dll"
>
> "outputDirectory=C:\Workbench\NPanday\svn-trunk\plugins\netplugins\NPanday.Plugin.Addin"
> "groupId=npanday.plugin" "artifactId=NPanday.Plugin.Addin"
> "artifactVersion=1.3.1-incubating-SNAPSHOT"
> "startProcessAssembly=C:\Workbench\NPanday\svn-trunk\target\NPanday.Plugin.MojoGenerator.exe"
> "pluginArtifactPath=C:\Workbench\NPanday\svn-trunk\target\NPanday.Plugin.dll"
> Creating Plugin Domain Manager
> Loading Generator:
> C:\Workbench\NPanday\svn-trunk\plugins\netplugins\NPanday.Plugin.Addin\target
> Creating Plugin Domain Manager
> Assembly :mscorlib
> Assembly :NPanday.Plugin
> Assembly :NPanday.Plugin.Addin
> [INFO]
> [INFO] Unhandled Exception: System.InvalidCastException: Unable to cast
> object of type 'NPanday.Plugin.FieldAttribute' to type
> 'NPanday.Plugin.FieldAttribute'.
> [INFO]at NPanday.Plugin.Generator.JavaClassUnmarshaller.convert(Type
> abstractMojoType, String groupId)
> [INFO]at
> NPanday.Plugin.Generator.JavaClassUnmarshaller.GetMojosFor(String
> assemblyName, String groupId)
> [INFO]at
> NPanday.Plugin.Generator.JavaClassUnmarshaller.GetMojosFor(String
> assemblyName, String groupId)
> [INFO]at
> NPanday.Plugin.MojoGenerator.Generator.BuildPluginProject(AppDomain
> applicationDomain, FileInfo pluginArtifact, FileInfo outputDirectory, String
> groupId, String artifactId, String version)
> [INFO]at NPanday.Plugin.MojoGenerator.Generator.Main(String[] args)
> NPanday: End Process = 12.04.2011 09:38:57; exit code = -532459699
> [INFO]
>
> [ERROR] BUILD ERROR
> [INFO]
>
> {code}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (NPANDAY-387) Improve the checking of the mirror repos in Reference.cs for artifact resync
[
https://issues.apache.org/jira/browse/NPANDAY-387?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joe Ocaba reassigned NPANDAY-387:
-
Assignee: Joe Ocaba
> Improve the checking of the mirror repos in Reference.cs for artifact resync
>
>
> Key: NPANDAY-387
> URL: https://issues.apache.org/jira/browse/NPANDAY-387
> Project: NPanday
> Issue Type: Improvement
> Components: Project Importer
>Affects Versions: 1.2.1
>Reporter: Joe Ocaba
>Assignee: Joe Ocaba
> Fix For: 1.3.1-incubating
>
>
> foreach (Mirror mirror in settings.mirrors)
> {
>string id = mirror.mirrorOf;
> ->>> if (id == "external:*")
> id = "*";
>// TODO: support '!' syntax
>mirrors.Add(id, mirror.url);
> }
> change the condition to start of instead of exact match
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (NPANDAY-387) Improve the checking of the mirror repos in Reference.cs for artifact resync
[
https://issues.apache.org/jira/browse/NPANDAY-387?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joe Ocaba updated NPANDAY-387:
--
Priority: Minor (was: Major)
> Improve the checking of the mirror repos in Reference.cs for artifact resync
>
>
> Key: NPANDAY-387
> URL: https://issues.apache.org/jira/browse/NPANDAY-387
> Project: NPanday
> Issue Type: Improvement
> Components: Project Importer
>Affects Versions: 1.2.1
>Reporter: Joe Ocaba
>Assignee: Joe Ocaba
>Priority: Minor
> Fix For: 1.3.1-incubating
>
>
> foreach (Mirror mirror in settings.mirrors)
> {
>string id = mirror.mirrorOf;
> ->>> if (id == "external:*")
> id = "*";
>// TODO: support '!' syntax
>mirrors.Add(id, mirror.url);
> }
> change the condition to start of instead of exact match
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
