[jira] [Created] (NPANDAY-607) Re-sync artifacts in addin can create unnecessary entries in the local repository
Brett Porter created NPANDAY-607: Summary: Re-sync artifacts in addin can create unnecessary entries in the local repository Key: NPANDAY-607 URL: https://issues.apache.org/jira/browse/NPANDAY-607 Project: NPanday Issue Type: Bug Components: Visual Studio Add-in Affects Versions: 1.5.0-incubating Reporter: Brett Porter I've noticed that there is a harmless bug where resyncing copies files into the local repository in the wrong location in addition to the right one (e.g. System.Net.Http/System.Net.Http4.0.0.0-.dll instead of System.Net.Http/4.0.0.0/System.Net.Http-4.0.0.0.dll) -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Created] (NPANDAY-606) Addin caches available artifacts in local repository, but does not detect subsequent changes
Brett Porter created NPANDAY-606: Summary: Addin caches available artifacts in local repository, but does not detect subsequent changes Key: NPANDAY-606 URL: https://issues.apache.org/jira/browse/NPANDAY-606 Project: NPanday Issue Type: Bug Components: Visual Studio Add-in Affects Versions: 1.4-incubating Reporter: Brett Porter The cache that gets constructed should do a quick file check before each request to determine whether it needs to be updated if an artifact has been deleted. Detecting additions is more difficult, but it would be worth periodically refreshing the cache by re-scanning. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (NPANDAY-604) When a solution contains more than one version of an assembly, only one version is used in POMs
[
https://issues.apache.org/jira/browse/NPANDAY-604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13768013#comment-13768013
]
Brett Porter commented on NPANDAY-604:
--
Fixed in r1523534
> When a solution contains more than one version of an assembly, only one
> version is used in POMs
> ---
>
> Key: NPANDAY-604
> URL: https://issues.apache.org/jira/browse/NPANDAY-604
> Project: NPanday
> Issue Type: Bug
> Components: Project Importer
>Affects Versions: 1.4-incubating
>Reporter: Brett Porter
>Assignee: Brett Porter
> Fix For: 1.5.0-incubating
>
>
> When the project importer reviews references, it uses
> {{AppDomain.CurrentDomain.ReflectionOnlyAssemblies()}} to look at existing
> loaded assemblies and tries to match the assembly by short name. If not found
> it loads the DLL for reflection. This means once one version of an assembly
> is loaded, not different versions will later be loaded.
> Reflection loading in this case is unnecessary as
> {{AssemblyName.GetAssemblyName()}} contains all the information needed to
> construct the reference information without loading the assembly.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (NPANDAY-604) When a solution contains more than one version of an assembly, only one version is used in POMs
[
https://issues.apache.org/jira/browse/NPANDAY-604?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brett Porter resolved NPANDAY-604.
--
Resolution: Fixed
> When a solution contains more than one version of an assembly, only one
> version is used in POMs
> ---
>
> Key: NPANDAY-604
> URL: https://issues.apache.org/jira/browse/NPANDAY-604
> Project: NPanday
> Issue Type: Bug
> Components: Project Importer
>Affects Versions: 1.4-incubating
>Reporter: Brett Porter
>Assignee: Brett Porter
> Fix For: 1.5.0-incubating
>
>
> When the project importer reviews references, it uses
> {{AppDomain.CurrentDomain.ReflectionOnlyAssemblies()}} to look at existing
> loaded assemblies and tries to match the assembly by short name. If not found
> it loads the DLL for reflection. This means once one version of an assembly
> is loaded, not different versions will later be loaded.
> Reflection loading in this case is unnecessary as
> {{AssemblyName.GetAssemblyName()}} contains all the information needed to
> construct the reference information without loading the assembly.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Work started] (NPANDAY-604) When a solution contains more than one version of an assembly, only one version is used in POMs
[
https://issues.apache.org/jira/browse/NPANDAY-604?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on NPANDAY-604 started by Brett Porter.
> When a solution contains more than one version of an assembly, only one
> version is used in POMs
> ---
>
> Key: NPANDAY-604
> URL: https://issues.apache.org/jira/browse/NPANDAY-604
> Project: NPanday
> Issue Type: Bug
> Components: Project Importer
>Affects Versions: 1.4-incubating
>Reporter: Brett Porter
>Assignee: Brett Porter
> Fix For: 1.5.0-incubating
>
>
> When the project importer reviews references, it uses
> {{AppDomain.CurrentDomain.ReflectionOnlyAssemblies()}} to look at existing
> loaded assemblies and tries to match the assembly by short name. If not found
> it loads the DLL for reflection. This means once one version of an assembly
> is loaded, not different versions will later be loaded.
> Reflection loading in this case is unnecessary as
> {{AssemblyName.GetAssemblyName()}} contains all the information needed to
> construct the reference information without loading the assembly.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (NPANDAY-604) When a solution contains more than one version of an assembly, only one version is used in POMs
Brett Porter created NPANDAY-604:
Summary: When a solution contains more than one version of an
assembly, only one version is used in POMs
Key: NPANDAY-604
URL: https://issues.apache.org/jira/browse/NPANDAY-604
Project: NPanday
Issue Type: Bug
Components: Project Importer
Affects Versions: 1.4-incubating
Reporter: Brett Porter
Assignee: Brett Porter
Fix For: 1.5.0-incubating
When the project importer reviews references, it uses
{{AppDomain.CurrentDomain.ReflectionOnlyAssemblies()}} to look at existing
loaded assemblies and tries to match the assembly by short name. If not found
it loads the DLL for reflection. This means once one version of an assembly is
loaded, not different versions will later be loaded.
Reflection loading in this case is unnecessary as
{{AssemblyName.GetAssemblyName()}} contains all the information needed to
construct the reference information without loading the assembly.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (NPANDAY-603) Hi ,In my project i have done NPanday build .But in that ,There is some issue .I have created MSDeploy.zip but in that some folders are missing
[ https://issues.apache.org/jira/browse/NPANDAY-603?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter resolved NPANDAY-603. -- Resolution: Incomplete Hi, thanks for contacting us. Unfortunately we will need more details to assist with the issue - please consider emailing npanday-us...@incubator.apache.org with information on what you have tried and how it failed. This tracker is intended for identified bugs and feature requests in the software. > Hi ,In my project i have done NPanday build .But in that ,There is some issue > .I have created MSDeploy.zip but in that some folders are missing > --- > > Key: NPANDAY-603 > URL: https://issues.apache.org/jira/browse/NPANDAY-603 > Project: NPanday > Issue Type: Bug >Reporter: sai chetan siddavatam > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Deleted] (NPANDAY-602) Hi all,
[ https://issues.apache.org/jira/browse/NPANDAY-602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter deleted NPANDAY-602: - > Hi all, > --- > > Key: NPANDAY-602 > URL: https://issues.apache.org/jira/browse/NPANDAY-602 > Project: NPanday > Issue Type: Bug >Reporter: sai chetan siddavatam > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (NPANDAY-601) Support /platform argument to the compile plugin
[ https://issues.apache.org/jira/browse/NPANDAY-601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter resolved NPANDAY-601. -- Resolution: Fixed Assignee: Brett Porter Added on trunk > Support /platform argument to the compile plugin > > > Key: NPANDAY-601 > URL: https://issues.apache.org/jira/browse/NPANDAY-601 > Project: NPanday > Issue Type: Bug >Reporter: Brett Porter >Assignee: Brett Porter > Fix For: 1.5.0-incubating > > > The compile plugin currently has a platform and testPlatform argument, but > they are marked as unsupported, and not passed on. These should be enabled, > if they are specified. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (NPANDAY-505) Move vendor detection to Java code (hence remove NPanday.Plugin.Settings)
[
https://issues.apache.org/jira/browse/NPANDAY-505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13742172#comment-13742172
]
Brett Porter commented on NPANDAY-505:
--
Couple more things to keep an eye on - there seemed to be an issue on Server
2008 R2 if I wasn't using administrative mode - it couldn't use the WinRegistry
class. We might need to confirm if that affects this.
Also, we should keep an eye on whether 64-bit OS get the merged registry, not
just the 64-bit portion (since the .NET framework entries sit under the Wow6432
section)
> Move vendor detection to Java code (hence remove NPanday.Plugin.Settings)
> -
>
> Key: NPANDAY-505
> URL: https://issues.apache.org/jira/browse/NPANDAY-505
> Project: NPanday
> Issue Type: Improvement
> Components: Development Setup, Maven Plugins
>Affects Versions: 1.4-incubating
>Reporter: Lars Corneliussen
>Assignee: Brett Porter
> Fix For: 1.5.0-incubating
>
>
> Currently NPanday "sometimes" generates a {{npanday-settings.xml}}-file;
> preferably in {{~/.m2}}. Currently this is done by
> NPanday.Plugin.Settings:generate-settings. The problem is, that the file is
> needed to compile the plugin that generates it. That makes it hard to
> bootstrap without a path.
> h2. New Approach
> We create a master "superset" configuration {{npanday-settings.xml}} (or
> better {{supported-vendors.xml}}?? that contains all frameworks and vendors
> NPanday supports. Then based on various rules, NPanday checks which
> combinations of vendor, vendorVersion and frameworkVersion(s) are available
> on the current platform (registry and path lookup, as currently done in
> generate-settings).
> h2. Example
> Currently this code:
> {code:title=plugins\netplugins\NPanday.Plugin.Settings\src\main\csharp\DotnetSdkLocator.cs}
> ..
> RegistryKey Microsoft_NETFramework =
> Registry.LocalMachine.OpenSubKey(@"SOFTWARE\Microsoft\.NETFramework");
> RegistryKey Microsoft_SDKs_NETFramework =
> Registry.LocalMachine.OpenSubKey(@"SOFTWARE\Microsoft\SDKs\.NETFramework");
> ..
> return PathUtil.FirstExisting(
> registryFind(Microsoft_NETFramework, "sdkInstallRootv2.0"),
> registryFind(Microsoft_SDKs_NETFramework, "v2.0",
> "InstallationFolder"),
> ProgramFilesX86(@"Microsoft.NET\SDK\v2.0"),
> ProgramFilesX86(@"Microsoft.NET\SDK\v2.0 64bit"),
> ProgramFilesX86(@"Microsoft SDKs\Windows\v6.0A\bin"),
> ProgramFiles(@"Microsoft SDKs\Windows\v6.0A\bin")
> );
> {code}
> Generates this:
> {code:title=~\.m2\npanday-settings.xml}
> ...
>
> MICROSOFT
> 3.0
>
>
> 3.0
> C:\Windows\Microsoft.NET\Framework64\v3.0
> C:\Program Files\Microsoft.NET\SDK\v2.0
> 64bit\
>
>
> C:\Windows\Microsoft.NET\Framework64\v2.0.50727
> C:\Program Files\Microsoft.NET\SDK\v2.0
> 64bit\bin
>
>
>
>
> ...
> {code}
> {code:title=components\dotnet-core\src\main\resources\META-INF\npanday\npanday-settings.xml}
> ...
>
> ...
>
> MICROSOFT
> 3.0
>
>
>
> AMD64
> 3.0
>
>
>
> ${env.WINDIR}\Microsoft.NET\Framework64\v3.0
>
>
>
>
> ${HKLM\Software\Microsoft\.NETFramework@sdkInstallRootv2.0"}
> ${HKLM\SOFTWARE\Microsoft\Microsoft
> SDKs\.NETFramework\v2.0@InstallationFolder}
>
> ${env.ProgramFiles}\Microsoft.NET\SDK\v2.0
> ${env.ProgramFiles}\Microsoft
> SDKs\Windows\v6.0A\bin
> ${env.ProgramFilesX86}(@"Microsoft
> SDKs\Windows\v6.0A\bin"}
>
>
>
>
> ${env.WINDIR}\Microsoft.NET\Framework64\v2.0.50727
>
>
>
>
>
>
>
> ...
>
> ...
> {code}
> Both registry access with ${HKLM*}, ${HKCU*}, ${HKEY_LOCAL_MACHINE*},
> ${HKEY_CURRENT_USER*} and ${env.*} should work. I'd suggest to let
> ${env.ProgramFilesX86} fall back to ${env.ProgramFiles} for non-64-bit - (add
> an item to the properties in {{ContextAwareModelInterpolator}})
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (NPANDAY-369) Explicit 64bit-Support (NPanday now doesn't distinguish)
[ https://issues.apache.org/jira/browse/NPANDAY-369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13742062#comment-13742062 ] Brett Porter commented on NPANDAY-369: -- I've filed NPANDAY-601 to support the /platform argument to the compiler, as a starting point. We should work through the tool locations as part of NPANDAY-505. I'm not sure I understand the comment about the architecture that NPanday itself should run under - AnyCPU seems the most appropriate for the AddIn? > Explicit 64bit-Support (NPanday now doesn't distinguish) > > > Key: NPANDAY-369 > URL: https://issues.apache.org/jira/browse/NPANDAY-369 > Project: NPanday > Issue Type: Bug > Components: Development Setup >Affects Versions: 1.4-incubating > Environment: Win 7, x64, VS 2010 only >Reporter: Lars Corneliussen >Assignee: Lars Corneliussen > Labels: build, nunit, test, x64, x86 > Fix For: 2.0 > > > Building NPanday from source (including tests) on 64bit windows fails. > The problem is, that all resources are built with the 64-bit version of the > .NET Framework tools. Also then, the nunit-console runs everything (including > MSBUILD) in 64 bit. > NPanday itself should allways be built using x86. It should furthermore have > strong support for building both 32bit and 64bit apps on 64bit systems. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (NPANDAY-601) Support /platform argument to the compile plugin
Brett Porter created NPANDAY-601: Summary: Support /platform argument to the compile plugin Key: NPANDAY-601 URL: https://issues.apache.org/jira/browse/NPANDAY-601 Project: NPanday Issue Type: Bug Reporter: Brett Porter Fix For: 1.5.0-incubating The compile plugin currently has a platform and testPlatform argument, but they are marked as unsupported, and not passed on. These should be enabled, if they are specified. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (NPANDAY-597) Disable transitivity for pdb-artifacts
[
https://issues.apache.org/jira/browse/NPANDAY-597?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13738125#comment-13738125
]
Brett Porter commented on NPANDAY-597:
--
I think you want {{includesDependencies}} to be true when it is declared as an
artifact type. We already have some supporting code to construct that in
{{./components/dotnet-core/src/main/groovy/npanday/lifecycle/LifecycleConfigurationGenerator.groovy}},
but I don't think there's a {{pdb}} definition yet.
> Disable transitivity for pdb-artifacts
> --
>
> Key: NPANDAY-597
> URL: https://issues.apache.org/jira/browse/NPANDAY-597
> Project: NPanday
> Issue Type: Sub-task
> Components: Maven Plugins
>Reporter: Lars Corneliussen
> Fix For: 1.5.0-incubating
>
>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (NPANDAY-594) Only resolve PDBs from the same repo the dll was resolved from
[ https://issues.apache.org/jira/browse/NPANDAY-594?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13738111#comment-13738111 ] Brett Porter commented on NPANDAY-594: -- I agree, I don't think there's significant value in trying to constrain the source repository. > Only resolve PDBs from the same repo the dll was resolved from > -- > > Key: NPANDAY-594 > URL: https://issues.apache.org/jira/browse/NPANDAY-594 > Project: NPanday > Issue Type: Sub-task > Components: Maven Plugins >Reporter: Lars Corneliussen > Fix For: 1.5.0-incubating > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (NPANDAY-505) Move vendor detection to Java code (hence remove NPanday.Plugin.Settings)
[
https://issues.apache.org/jira/browse/NPANDAY-505?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13727460#comment-13727460
]
Brett Porter commented on NPANDAY-505:
--
Looking closer at the code for this, it seems that the SDK locators are too
broad in the first place, and there is some confusion between .NET SDK and
Windows SDK references. We would be better specifying the expected path of the
specific commands needed:
* csc, etc. in the framework tools path
* xsd, gacutil in the framework NETFX path
That way it should just be one path rather than a search.
I note that there are the following to help now, which reference the specific
Windows SDK:
{{HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSBuild\ToolsVersions\2.0@MSBuildToolsPath}}
and from 4.0 also:
{{HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSBuild\ToolsVersions\4.0@FrameworkSDKRoot}}
{{HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSBuild\ToolsVersions\4.0@SDK40ToolsPath}}
> Move vendor detection to Java code (hence remove NPanday.Plugin.Settings)
> -
>
> Key: NPANDAY-505
> URL: https://issues.apache.org/jira/browse/NPANDAY-505
> Project: NPanday
> Issue Type: Improvement
> Components: Development Setup, Maven Plugins
>Affects Versions: 1.4-incubating
>Reporter: Lars Corneliussen
>Assignee: Brett Porter
> Fix For: 1.5.0-incubating
>
>
> Currently NPanday "sometimes" generates a {{npanday-settings.xml}}-file;
> preferably in {{~/.m2}}. Currently this is done by
> NPanday.Plugin.Settings:generate-settings. The problem is, that the file is
> needed to compile the plugin that generates it. That makes it hard to
> bootstrap without a path.
> h2. New Approach
> We create a master "superset" configuration {{npanday-settings.xml}} (or
> better {{supported-vendors.xml}}?? that contains all frameworks and vendors
> NPanday supports. Then based on various rules, NPanday checks which
> combinations of vendor, vendorVersion and frameworkVersion(s) are available
> on the current platform (registry and path lookup, as currently done in
> generate-settings).
> h2. Example
> Currently this code:
> {code:title=plugins\netplugins\NPanday.Plugin.Settings\src\main\csharp\DotnetSdkLocator.cs}
> ..
> RegistryKey Microsoft_NETFramework =
> Registry.LocalMachine.OpenSubKey(@"SOFTWARE\Microsoft\.NETFramework");
> RegistryKey Microsoft_SDKs_NETFramework =
> Registry.LocalMachine.OpenSubKey(@"SOFTWARE\Microsoft\SDKs\.NETFramework");
> ..
> return PathUtil.FirstExisting(
> registryFind(Microsoft_NETFramework, "sdkInstallRootv2.0"),
> registryFind(Microsoft_SDKs_NETFramework, "v2.0",
> "InstallationFolder"),
> ProgramFilesX86(@"Microsoft.NET\SDK\v2.0"),
> ProgramFilesX86(@"Microsoft.NET\SDK\v2.0 64bit"),
> ProgramFilesX86(@"Microsoft SDKs\Windows\v6.0A\bin"),
> ProgramFiles(@"Microsoft SDKs\Windows\v6.0A\bin")
> );
> {code}
> Generates this:
> {code:title=~\.m2\npanday-settings.xml}
> ...
>
> MICROSOFT
> 3.0
>
>
> 3.0
> C:\Windows\Microsoft.NET\Framework64\v3.0
> C:\Program Files\Microsoft.NET\SDK\v2.0
> 64bit\
>
>
> C:\Windows\Microsoft.NET\Framework64\v2.0.50727
> C:\Program Files\Microsoft.NET\SDK\v2.0
> 64bit\bin
>
>
>
>
> ...
> {code}
> {code:title=components\dotnet-core\src\main\resources\META-INF\npanday\npanday-settings.xml}
> ...
>
> ...
>
> MICROSOFT
> 3.0
>
>
>
> AMD64
> 3.0
>
>
>
> ${env.WINDIR}\Microsoft.NET\Framework64\v3.0
>
>
>
>
> ${HKLM\Software\Microsoft\.NETFramework@sdkInstallRootv2.0"}
> ${HKLM\SOFTWARE\Microsoft\Microsoft
> SDKs\.NETFramework\v2.0@InstallationFolder}
>
> ${env.ProgramFiles}\Microsoft.NET\SDK\v2.0
> ${env.ProgramFiles}\Microsoft
> SDKs\Windows\v6.0A\bin
> ${env.ProgramFilesX86}(@"Microsoft
> SDKs\Windows\v6.0A\bin"}
>
>
>
>
> ${env.WINDIR}\Microsoft.NET\Framework64\v2.0.50727
>
>
>
>
>
>
>
> ...
>
> ...
> {code}
> Both registry access with ${HKLM*}, ${HKCU*}, ${HKEY_LOCAL_MACHINE*},
> ${HKEY_CURRENT_USER*} and ${env.*} should work. I'd suggest to let
> ${env.ProgramFilesX86} fall back to ${env.ProgramFiles} for non-64-bit - (add
> an item to the properties in {{ContextAwareModelInterpolator}})
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, plea
[jira] [Updated] (NPANDAY-591) Correct project importer issues with VisualStudioVersion 11.0 and Azure projects
[ https://issues.apache.org/jira/browse/NPANDAY-591?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter updated NPANDAY-591: - Fix Version/s: 1.5.0-incubating > Correct project importer issues with VisualStudioVersion 11.0 and Azure > projects > > > Key: NPANDAY-591 > URL: https://issues.apache.org/jira/browse/NPANDAY-591 > Project: NPanday > Issue Type: Sub-task > Components: Visual Studio Add-in >Reporter: Brett Porter >Assignee: Brett Porter > Fix For: 1.5.0-incubating > > > This is just an issue for the tests that are hardcoded to Azure 1.7 + the > latest visual studio installed. If the latest visual studio was installed > after Azure 1.7, it won't have the tools in the right place. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (NPANDAY-582) Default value of testAssemblyPath does not work on linux/mono
[ https://issues.apache.org/jira/browse/NPANDAY-582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter updated NPANDAY-582: - Fix Version/s: 1.5.0-incubating > Default value of testAssemblyPath does not work on linux/mono > - > > Key: NPANDAY-582 > URL: https://issues.apache.org/jira/browse/NPANDAY-582 > Project: NPanday > Issue Type: Bug > Components: Maven Plugins >Affects Versions: 1.5.0-incubating > Environment: Debian >Reporter: Mickaël Remars >Assignee: Brett Porter > Labels: linux, mono, patch > Fix For: 1.5.0-incubating > > Attachments: NPANDAY-582.patch > > > This default value contains a backslash which linux does not like. This > should be replaced with a slash to work on both windows and linux. > Patch is attached. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (NPANDAY-582) Default value of testAssemblyPath does not work on linux/mono
[ https://issues.apache.org/jira/browse/NPANDAY-582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter resolved NPANDAY-582. -- Resolution: Fixed Assignee: Brett Porter Applied, sorry for missing it earlier! > Default value of testAssemblyPath does not work on linux/mono > - > > Key: NPANDAY-582 > URL: https://issues.apache.org/jira/browse/NPANDAY-582 > Project: NPanday > Issue Type: Bug > Components: Maven Plugins >Affects Versions: 1.5.0-incubating > Environment: Debian >Reporter: Mickaël Remars >Assignee: Brett Porter > Labels: linux, mono, patch > Attachments: NPANDAY-582.patch > > > This default value contains a backslash which linux does not like. This > should be replaced with a slash to work on both windows and linux. > Patch is attached. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (NPANDAY-358) ResGen Maven Plugin: Failed to find resources in multi module project
[ https://issues.apache.org/jira/browse/NPANDAY-358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter resolved NPANDAY-358. -- Resolution: Fixed Assignee: Brett Porter (was: Lars Corneliussen) Applied patch > ResGen Maven Plugin: Failed to find resources in multi module project > - > > Key: NPANDAY-358 > URL: https://issues.apache.org/jira/browse/NPANDAY-358 > Project: NPanday > Issue Type: Bug > Components: Maven Plugins >Affects Versions: 1.2.1, 1.4-incubating >Reporter: Simon Brending >Assignee: Brett Porter >Priority: Blocker > Fix For: 1.5.0-incubating > > Attachments: NPANDAY-358-PATCH, ResourceTest.zip > > > The ResGen Maven Plugin fails in a multi module project. It can not find the > resources, because it does not resolve the paths correctly. > The path will be resolved correctly with the command line option > "/usesourcepath". -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (NPANDAY-586) Support for Visual Studio 2012
[ https://issues.apache.org/jira/browse/NPANDAY-586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter resolved NPANDAY-586. -- Resolution: Fixed Fix Version/s: 1.5.0-incubating > Support for Visual Studio 2012 > -- > > Key: NPANDAY-586 > URL: https://issues.apache.org/jira/browse/NPANDAY-586 > Project: NPanday > Issue Type: Improvement > Components: Visual Studio Add-in >Reporter: Brett Porter >Assignee: Brett Porter > Fix For: 1.5.0-incubating > > > VS 2012 has been out for a while - it would be good to verify that the Addin > works, and that the integration tests pass. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (NPANDAY-592) Test project generation of major project types and that they correctly build
[ https://issues.apache.org/jira/browse/NPANDAY-592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter resolved NPANDAY-592. -- Resolution: Fixed Fix Version/s: 1.5.0-incubating Assignee: Brett Porter Passing the ITs and other ad-hoc testing seems fine. > Test project generation of major project types and that they correctly build > > > Key: NPANDAY-592 > URL: https://issues.apache.org/jira/browse/NPANDAY-592 > Project: NPanday > Issue Type: Sub-task > Components: Visual Studio Add-in >Reporter: Brett Porter >Assignee: Brett Porter > Fix For: 1.5.0-incubating > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (NPANDAY-589) Update settings mojo to generate appropriate vendor information for framework 4.5
[ https://issues.apache.org/jira/browse/NPANDAY-589?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter resolved NPANDAY-589. -- Resolution: Fixed Fix Version/s: 1.5.0-incubating Assignee: Brett Porter > Update settings mojo to generate appropriate vendor information for framework > 4.5 > - > > Key: NPANDAY-589 > URL: https://issues.apache.org/jira/browse/NPANDAY-589 > Project: NPanday > Issue Type: Sub-task > Components: Maven Plugins >Reporter: Brett Porter >Assignee: Brett Porter > Fix For: 1.5.0-incubating > > > Should refer to the 4.0 installRoot (in place upgrade), but use the > appropriate Windows SDK for the newer tools. > This might be the appropriate time to review the settings file as recorded in > other issues, to make sure the right paths are used in the right place. There > are several more appropriate locations and techniques for locating them than > are currently used. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (NPANDAY-588) Add support for framework 4.5 to vendor information for compiler and other plugins
[ https://issues.apache.org/jira/browse/NPANDAY-588?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter resolved NPANDAY-588. -- Resolution: Fixed Fix Version/s: 1.5.0-incubating Assignee: Brett Porter > Add support for framework 4.5 to vendor information for compiler and other > plugins > -- > > Key: NPANDAY-588 > URL: https://issues.apache.org/jira/browse/NPANDAY-588 > Project: NPanday > Issue Type: Sub-task > Components: Maven Plugins >Reporter: Brett Porter >Assignee: Brett Porter > Fix For: 1.5.0-incubating > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (NPANDAY-587) Support for .NET Framework 4.5
[ https://issues.apache.org/jira/browse/NPANDAY-587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter resolved NPANDAY-587. -- Resolution: Fixed Fix Version/s: 1.5.0-incubating > Support for .NET Framework 4.5 > -- > > Key: NPANDAY-587 > URL: https://issues.apache.org/jira/browse/NPANDAY-587 > Project: NPanday > Issue Type: Improvement > Components: Maven Plugins >Reporter: Brett Porter >Assignee: Brett Porter > Fix For: 1.5.0-incubating > > > Along with NPANDAY-586, check that projects using the new version of the > framework build successfully. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (NPANDAY-591) Correct project importer issues with VisualStudioVersion 11.0 and Azure projects
[ https://issues.apache.org/jira/browse/NPANDAY-591?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13671990#comment-13671990 ] Brett Porter commented on NPANDAY-591: -- Oops, was already fixed - was testing a slightly older version. > Correct project importer issues with VisualStudioVersion 11.0 and Azure > projects > > > Key: NPANDAY-591 > URL: https://issues.apache.org/jira/browse/NPANDAY-591 > Project: NPanday > Issue Type: Sub-task > Components: Visual Studio Add-in >Reporter: Brett Porter >Assignee: Brett Porter > > This is just an issue for the tests that are hardcoded to Azure 1.7 + the > latest visual studio installed. If the latest visual studio was installed > after Azure 1.7, it won't have the tools in the right place. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (NPANDAY-591) Correct project importer issues with VisualStudioVersion 11.0 and Azure projects
[ https://issues.apache.org/jira/browse/NPANDAY-591?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter updated NPANDAY-591: - Fix Version/s: (was: 1.5.0-incubating) > Correct project importer issues with VisualStudioVersion 11.0 and Azure > projects > > > Key: NPANDAY-591 > URL: https://issues.apache.org/jira/browse/NPANDAY-591 > Project: NPanday > Issue Type: Sub-task > Components: Visual Studio Add-in >Reporter: Brett Porter >Assignee: Brett Porter > > This is just an issue for the tests that are hardcoded to Azure 1.7 + the > latest visual studio installed. If the latest visual studio was installed > after Azure 1.7, it won't have the tools in the right place. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (NPANDAY-591) Correct project importer issues with VisualStudioVersion 11.0 and Azure projects
[ https://issues.apache.org/jira/browse/NPANDAY-591?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter resolved NPANDAY-591. -- Resolution: Fixed Fix Version/s: 1.5.0-incubating Assignee: Brett Porter Commenting out the import in the test project, as it doesn't impact the result. > Correct project importer issues with VisualStudioVersion 11.0 and Azure > projects > > > Key: NPANDAY-591 > URL: https://issues.apache.org/jira/browse/NPANDAY-591 > Project: NPanday > Issue Type: Sub-task > Components: Visual Studio Add-in >Reporter: Brett Porter >Assignee: Brett Porter > Fix For: 1.5.0-incubating > > > This is just an issue for the tests that are hardcoded to Azure 1.7 + the > latest visual studio installed. If the latest visual studio was installed > after Azure 1.7, it won't have the tools in the right place. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (NPANDAY-591) Correct project importer issues with VisualStudioVersion 11.0 and Azure projects
[ https://issues.apache.org/jira/browse/NPANDAY-591?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter updated NPANDAY-591: - Description: This is just an issue for the tests that are hardcoded to Azure 1.7 + the latest visual studio installed. If the latest visual studio was installed after Azure 1.7, it won't have the tools in the right place. > Correct project importer issues with VisualStudioVersion 11.0 and Azure > projects > > > Key: NPANDAY-591 > URL: https://issues.apache.org/jira/browse/NPANDAY-591 > Project: NPanday > Issue Type: Sub-task > Components: Visual Studio Add-in >Reporter: Brett Porter > > This is just an issue for the tests that are hardcoded to Azure 1.7 + the > latest visual studio installed. If the latest visual studio was installed > after Azure 1.7, it won't have the tools in the right place. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (NPANDAY-592) Test project generation of major project types and that they correctly build
Brett Porter created NPANDAY-592: Summary: Test project generation of major project types and that they correctly build Key: NPANDAY-592 URL: https://issues.apache.org/jira/browse/NPANDAY-592 Project: NPanday Issue Type: Sub-task Reporter: Brett Porter -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (NPANDAY-590) Allow the addin to run in VS 2012
[ https://issues.apache.org/jira/browse/NPANDAY-590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter resolved NPANDAY-590. -- Resolution: Fixed Fix Version/s: 1.5.0-incubating Assignee: Brett Porter > Allow the addin to run in VS 2012 > - > > Key: NPANDAY-590 > URL: https://issues.apache.org/jira/browse/NPANDAY-590 > Project: NPanday > Issue Type: Sub-task > Components: Visual Studio Add-in >Reporter: Brett Porter >Assignee: Brett Porter > Fix For: 1.5.0-incubating > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (NPANDAY-589) Update settings mojo to generate appropriate vendor information for framework 4.5
Brett Porter created NPANDAY-589: Summary: Update settings mojo to generate appropriate vendor information for framework 4.5 Key: NPANDAY-589 URL: https://issues.apache.org/jira/browse/NPANDAY-589 Project: NPanday Issue Type: Sub-task Reporter: Brett Porter Should refer to the 4.0 installRoot (in place upgrade), but use the appropriate Windows SDK for the newer tools. This might be the appropriate time to review the settings file as recorded in other issues, to make sure the right paths are used in the right place. There are several more appropriate locations and techniques for locating them than are currently used. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (NPANDAY-588) Add support for framework 4.5 to vendor information for compiler and other plugins
Brett Porter created NPANDAY-588: Summary: Add support for framework 4.5 to vendor information for compiler and other plugins Key: NPANDAY-588 URL: https://issues.apache.org/jira/browse/NPANDAY-588 Project: NPanday Issue Type: Sub-task Reporter: Brett Porter -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (NPANDAY-590) Allow the addin to run in VS 2012
Brett Porter created NPANDAY-590: Summary: Allow the addin to run in VS 2012 Key: NPANDAY-590 URL: https://issues.apache.org/jira/browse/NPANDAY-590 Project: NPanday Issue Type: Sub-task Reporter: Brett Porter -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (NPANDAY-591) Correct project importer issues with VisualStudioVersion 11.0 and Azure projects
Brett Porter created NPANDAY-591: Summary: Correct project importer issues with VisualStudioVersion 11.0 and Azure projects Key: NPANDAY-591 URL: https://issues.apache.org/jira/browse/NPANDAY-591 Project: NPanday Issue Type: Sub-task Reporter: Brett Porter -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (NPANDAY-586) Support for Visual Studio 2012
[ https://issues.apache.org/jira/browse/NPANDAY-586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13667516#comment-13667516 ] Brett Porter commented on NPANDAY-586: -- There's an issue with the project importer tests that fail whenever VisualStudioVersion is 11.0 that will need to be addressed, but they otherwise pass. > Support for Visual Studio 2012 > -- > > Key: NPANDAY-586 > URL: https://issues.apache.org/jira/browse/NPANDAY-586 > Project: NPanday > Issue Type: Improvement > Components: Visual Studio Add-in >Reporter: Brett Porter >Assignee: Brett Porter > > VS 2012 has been out for a while - it would be good to verify that the Addin > works, and that the integration tests pass. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Issue Comment Deleted] (NPANDAY-586) Support for Visual Studio 2012
[
https://issues.apache.org/jira/browse/NPANDAY-586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brett Porter updated NPANDAY-586:
-
Comment: was deleted
(was: Got this when running in debug mode:
{code}
System.InvalidOperationException was unhandled
Message=DragDrop registration did not succeed.
Source=System.Windows.Forms
StackTrace:
at System.Windows.Forms.Control.SetAcceptDrops(Boolean accept)
at System.Windows.Forms.Control.OnHandleCreated(EventArgs e)
at System.Windows.Forms.ListBox.OnHandleCreated(EventArgs e)
at System.Windows.Forms.Control.WmCreate(Message& m)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ListBox.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.DebuggableCallback(IntPtr hWnd,
Int32 msg, IntPtr wparam, IntPtr lparam)
at System.Windows.Forms.UnsafeNativeMethods.IntCreateWindowEx(Int32
dwExStyle, String lpszClassName, String lpszWindowName, Int32 style, Int32 x,
Int32 y, Int32 width, Int32 height, HandleRef hWndParent, HandleRef hMenu,
HandleRef hInst, Object pvParam)
at System.Windows.Forms.UnsafeNativeMethods.CreateWindowEx(Int32
dwExStyle, String lpszClassName, String lpszWindowName, Int32 style, Int32 x,
Int32 y, Int32 width, Int32 height, HandleRef hWndParent, HandleRef hMenu,
HandleRef hInst, Object pvParam)
at System.Windows.Forms.NativeWindow.CreateHandle(CreateParams cp)
at System.Windows.Forms.Control.CreateHandle()
at System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible)
at System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible)
at System.Windows.Forms.Control.CreateControl()
at System.Windows.Forms.Control.WmShowWindow(Message& m)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ScrollableControl.WndProc(Message& m)
at System.Windows.Forms.ContainerControl.WndProc(Message& m)
at System.Windows.Forms.Form.WmShowWindow(Message& m)
at System.Windows.Forms.Form.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.DebuggableCallback(IntPtr hWnd,
Int32 msg, IntPtr wparam, IntPtr lparam)
at System.Windows.Forms.SafeNativeMethods.ShowWindow(HandleRef hWnd,
Int32 nCmdShow)
at System.Windows.Forms.Control.SetVisibleCore(Boolean value)
at System.Windows.Forms.Form.SetVisibleCore(Boolean value)
at System.Windows.Forms.Control.set_Visible(Boolean value)
at
System.Windows.Forms.Application.ThreadContext.RunMessageLoopInner(Int32
reason, ApplicationContext context)
at System.Windows.Forms.Application.ThreadContext.RunMessageLoop(Int32
reason, ApplicationContext context)
at System.Windows.Forms.Application.Run(Form mainForm)
at WindowsApplication2.Program.Main() in
C:\Users\brett\scm\maestrodev\npanday\dotnet\assemblies\NPanday.VisualStudio.ProjectWizard\src\main\csharp\Program.cs:line
38
at System.AppDomain._nExecuteAssembly(Assembly assembly, String[] args)
at System.AppDomain.ExecuteAssembly(String assemblyFile, Evidence
assemblySecurity, String[] args)
at Microsoft.VisualStudio.HostingProcess.HostProc.RunUsersAssembly()
at System.Threading.ThreadHelper.ThreadStart_Context(Object state)
at System.Threading.ExecutionContext.Run(ExecutionContext
executionContext, ContextCallback callback, Object state)
at System.Threading.ThreadHelper.ThreadStart()
InnerException: System.Threading.ThreadStateException
Message=Current thread must be set to single thread apartment (STA) mode
before OLE calls can be made. Ensure that your Main function has
STAThreadAttribute marked on it.
Source=System.Windows.Forms
StackTrace:
at System.Windows.Forms.Control.SetAcceptDrops(Boolean accept)
InnerException:
{code}
This code hasn't been used and can probably be removed.)
> Support for Visual Studio 2012
> --
>
> Key: NPANDAY-586
> URL: https://issues.apache.org/jira/browse/NPANDAY-586
> Project: NPanday
> Issue Type: Improvement
> Components: Visual Studio Add-in
>Reporter: Brett Porter
>Assignee: Brett Porter
>
> VS 2012 has been out for a while - it would be good to verify that the Addin
> works, and that the integration tests pass.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.a
[jira] [Commented] (NPANDAY-586) Support for Visual Studio 2012
[
https://issues.apache.org/jira/browse/NPANDAY-586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13667498#comment-13667498
]
Brett Porter commented on NPANDAY-586:
--
Got this when running in debug mode:
{code}
System.InvalidOperationException was unhandled
Message=DragDrop registration did not succeed.
Source=System.Windows.Forms
StackTrace:
at System.Windows.Forms.Control.SetAcceptDrops(Boolean accept)
at System.Windows.Forms.Control.OnHandleCreated(EventArgs e)
at System.Windows.Forms.ListBox.OnHandleCreated(EventArgs e)
at System.Windows.Forms.Control.WmCreate(Message& m)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ListBox.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.DebuggableCallback(IntPtr hWnd,
Int32 msg, IntPtr wparam, IntPtr lparam)
at System.Windows.Forms.UnsafeNativeMethods.IntCreateWindowEx(Int32
dwExStyle, String lpszClassName, String lpszWindowName, Int32 style, Int32 x,
Int32 y, Int32 width, Int32 height, HandleRef hWndParent, HandleRef hMenu,
HandleRef hInst, Object pvParam)
at System.Windows.Forms.UnsafeNativeMethods.CreateWindowEx(Int32
dwExStyle, String lpszClassName, String lpszWindowName, Int32 style, Int32 x,
Int32 y, Int32 width, Int32 height, HandleRef hWndParent, HandleRef hMenu,
HandleRef hInst, Object pvParam)
at System.Windows.Forms.NativeWindow.CreateHandle(CreateParams cp)
at System.Windows.Forms.Control.CreateHandle()
at System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible)
at System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible)
at System.Windows.Forms.Control.CreateControl()
at System.Windows.Forms.Control.WmShowWindow(Message& m)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ScrollableControl.WndProc(Message& m)
at System.Windows.Forms.ContainerControl.WndProc(Message& m)
at System.Windows.Forms.Form.WmShowWindow(Message& m)
at System.Windows.Forms.Form.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.DebuggableCallback(IntPtr hWnd,
Int32 msg, IntPtr wparam, IntPtr lparam)
at System.Windows.Forms.SafeNativeMethods.ShowWindow(HandleRef hWnd,
Int32 nCmdShow)
at System.Windows.Forms.Control.SetVisibleCore(Boolean value)
at System.Windows.Forms.Form.SetVisibleCore(Boolean value)
at System.Windows.Forms.Control.set_Visible(Boolean value)
at
System.Windows.Forms.Application.ThreadContext.RunMessageLoopInner(Int32
reason, ApplicationContext context)
at System.Windows.Forms.Application.ThreadContext.RunMessageLoop(Int32
reason, ApplicationContext context)
at System.Windows.Forms.Application.Run(Form mainForm)
at WindowsApplication2.Program.Main() in
C:\Users\brett\scm\maestrodev\npanday\dotnet\assemblies\NPanday.VisualStudio.ProjectWizard\src\main\csharp\Program.cs:line
38
at System.AppDomain._nExecuteAssembly(Assembly assembly, String[] args)
at System.AppDomain.ExecuteAssembly(String assemblyFile, Evidence
assemblySecurity, String[] args)
at Microsoft.VisualStudio.HostingProcess.HostProc.RunUsersAssembly()
at System.Threading.ThreadHelper.ThreadStart_Context(Object state)
at System.Threading.ExecutionContext.Run(ExecutionContext
executionContext, ContextCallback callback, Object state)
at System.Threading.ThreadHelper.ThreadStart()
InnerException: System.Threading.ThreadStateException
Message=Current thread must be set to single thread apartment (STA) mode
before OLE calls can be made. Ensure that your Main function has
STAThreadAttribute marked on it.
Source=System.Windows.Forms
StackTrace:
at System.Windows.Forms.Control.SetAcceptDrops(Boolean accept)
InnerException:
{code}
This code hasn't been used and can probably be removed.
> Support for Visual Studio 2012
> --
>
> Key: NPANDAY-586
> URL: https://issues.apache.org/jira/browse/NPANDAY-586
> Project: NPanday
> Issue Type: Improvement
> Components: Visual Studio Add-in
>Reporter: Brett Porter
>Assignee: Brett Porter
>
> VS 2012 has been out for a while - it would be good to verify that the Addin
> works, and that the integration tests pass.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more in
[jira] [Commented] (NPANDAY-587) Support for .NET Framework 4.5
[ https://issues.apache.org/jira/browse/NPANDAY-587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13667497#comment-13667497 ] Brett Porter commented on NPANDAY-587: -- New vendor information needs to be aded > Support for .NET Framework 4.5 > -- > > Key: NPANDAY-587 > URL: https://issues.apache.org/jira/browse/NPANDAY-587 > Project: NPanday > Issue Type: Improvement > Components: Maven Plugins >Reporter: Brett Porter >Assignee: Brett Porter > > Along with NPANDAY-586, check that projects using the new version of the > framework build successfully. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (NPANDAY-586) Support for Visual Studio 2012
[ https://issues.apache.org/jira/browse/NPANDAY-586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13667496#comment-13667496 ] Brett Porter commented on NPANDAY-586: -- Addin seems to start fine and perform normal operations with the new HostApplication added. > Support for Visual Studio 2012 > -- > > Key: NPANDAY-586 > URL: https://issues.apache.org/jira/browse/NPANDAY-586 > Project: NPanday > Issue Type: Improvement > Components: Visual Studio Add-in >Reporter: Brett Porter >Assignee: Brett Porter > > VS 2012 has been out for a while - it would be good to verify that the Addin > works, and that the integration tests pass. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (NPANDAY-586) Support for Visual Studio 2012
Brett Porter created NPANDAY-586: Summary: Support for Visual Studio 2012 Key: NPANDAY-586 URL: https://issues.apache.org/jira/browse/NPANDAY-586 Project: NPanday Issue Type: Improvement Components: Visual Studio Add-in Reporter: Brett Porter Assignee: Brett Porter VS 2012 has been out for a while - it would be good to verify that the Addin works, and that the integration tests pass. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Work started] (NPANDAY-586) Support for Visual Studio 2012
[ https://issues.apache.org/jira/browse/NPANDAY-586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on NPANDAY-586 started by Brett Porter. > Support for Visual Studio 2012 > -- > > Key: NPANDAY-586 > URL: https://issues.apache.org/jira/browse/NPANDAY-586 > Project: NPanday > Issue Type: Improvement > Components: Visual Studio Add-in >Reporter: Brett Porter >Assignee: Brett Porter > > VS 2012 has been out for a while - it would be good to verify that the Addin > works, and that the integration tests pass. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (NPANDAY-587) Support for .NET Framework 4.5
Brett Porter created NPANDAY-587: Summary: Support for .NET Framework 4.5 Key: NPANDAY-587 URL: https://issues.apache.org/jira/browse/NPANDAY-587 Project: NPanday Issue Type: Improvement Components: Maven Plugins Reporter: Brett Porter Assignee: Brett Porter Along with NPANDAY-586, check that projects using the new version of the framework build successfully. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (NPANDAY-585) Support future versions of Azure by making CSPACK selection use an expression
Brett Porter created NPANDAY-585: Summary: Support future versions of Azure by making CSPACK selection use an expression Key: NPANDAY-585 URL: https://issues.apache.org/jira/browse/NPANDAY-585 Project: NPanday Issue Type: Improvement Components: Maven Plugins Affects Versions: 1.5.0-incubating Reporter: Brett Porter See the comment on NPANDAY-571 - currently the supported versions are hardcoded, but there is an opportunity to use an expression if that can be supported -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (NPANDAY-571) Support Azure SDK 1.7 (June 2012)
[
https://issues.apache.org/jira/browse/NPANDAY-571?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brett Porter resolved NPANDAY-571.
--
Resolution: Fixed
Assignee: Brett Porter
Splitting the issue up
> Support Azure SDK 1.7 (June 2012)
> -
>
> Key: NPANDAY-571
> URL: https://issues.apache.org/jira/browse/NPANDAY-571
> Project: NPanday
> Issue Type: New Feature
>Reporter: Brett Porter
>Assignee: Brett Porter
>
> Currently, the Azure plugin only supports 1.6 (November 2011):
> http://incubator.apache.org/npanday/docs/1.5.0-incubating-SNAPSHOT/plugins/azure-maven-plugin/azure-sdk-versions.html
> We need to be able to run CSPACK from 1.7, which resides in: {{C:\Program
> Files\Microsoft SDKs\Windows Azure\.NET SDK\2012-06}}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (NPANDAY-571) Support Azure SDK 1.7 (June 2012)
[
https://issues.apache.org/jira/browse/NPANDAY-571?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brett Porter updated NPANDAY-571:
-
Fix Version/s: 1.5.0-incubating
> Support Azure SDK 1.7 (June 2012)
> -
>
> Key: NPANDAY-571
> URL: https://issues.apache.org/jira/browse/NPANDAY-571
> Project: NPanday
> Issue Type: New Feature
>Reporter: Brett Porter
>Assignee: Brett Porter
> Fix For: 1.5.0-incubating
>
>
> Currently, the Azure plugin only supports 1.6 (November 2011):
> http://incubator.apache.org/npanday/docs/1.5.0-incubating-SNAPSHOT/plugins/azure-maven-plugin/azure-sdk-versions.html
> We need to be able to run CSPACK from 1.7, which resides in: {{C:\Program
> Files\Microsoft SDKs\Windows Azure\.NET SDK\2012-06}}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (NPANDAY-584) Use relative paths to resources in response file
[ https://issues.apache.org/jira/browse/NPANDAY-584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter resolved NPANDAY-584. -- Resolution: Fixed > Use relative paths to resources in response file > > > Key: NPANDAY-584 > URL: https://issues.apache.org/jira/browse/NPANDAY-584 > Project: NPanday > Issue Type: Improvement >Reporter: Brett Porter >Assignee: Brett Porter > Fix For: 1.5.0-incubating > > > When using embedded resources - particularly with cultures - the list is > quite long. With the absolute path rendered into the repsonse file, the > command line can exceed 32K characters and crash the command line tools. > These should be made relative to the execution directory as a short term fix > until some improvements like NPANDAY-227 are considered. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (NPANDAY-584) Use relative paths to resources in response file
Brett Porter created NPANDAY-584: Summary: Use relative paths to resources in response file Key: NPANDAY-584 URL: https://issues.apache.org/jira/browse/NPANDAY-584 Project: NPanday Issue Type: Improvement Reporter: Brett Porter Assignee: Brett Porter Fix For: 1.5.0-incubating When using embedded resources - particularly with cultures - the list is quite long. With the absolute path rendered into the repsonse file, the command line can exceed 32K characters and crash the command line tools. These should be made relative to the execution directory as a short term fix until some improvements like NPANDAY-227 are considered. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (NPANDAY-583) Allow additional arguments to be passed to the MSBuild plugin
[
https://issues.apache.org/jira/browse/NPANDAY-583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13666049#comment-13666049
]
Brett Porter commented on NPANDAY-583:
--
added {{}} (or {{-Dmsbuild.extraArguments=...}}
> Allow additional arguments to be passed to the MSBuild plugin
> -
>
> Key: NPANDAY-583
> URL: https://issues.apache.org/jira/browse/NPANDAY-583
> Project: NPanday
> Issue Type: Improvement
>Reporter: Brett Porter
>Assignee: Brett Porter
> Fix For: 1.5.0-incubating
>
>
> It is useful to be able to pass additional arguments (or override the default
> ones) by appending them to the end of the command line.
> (e.g. {{/v:d}})
> This would help with the general case, though when the plugin is remodelled
> in the other issue, it would be good to cover the most specific ones with
> dedicated fields like , linking debug level to the plugin log level,
> etc.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Comment Edited] (NPANDAY-583) Allow additional arguments to be passed to the MSBuild plugin
[
https://issues.apache.org/jira/browse/NPANDAY-583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13666049#comment-13666049
]
Brett Porter edited comment on NPANDAY-583 at 5/24/13 7:21 AM:
---
added {{}} (or {{-Dmsbuild.extraArguments=...}})
was (Author: brettporter):
added {{}} (or {{-Dmsbuild.extraArguments=...}}
> Allow additional arguments to be passed to the MSBuild plugin
> -
>
> Key: NPANDAY-583
> URL: https://issues.apache.org/jira/browse/NPANDAY-583
> Project: NPanday
> Issue Type: Improvement
>Reporter: Brett Porter
>Assignee: Brett Porter
> Fix For: 1.5.0-incubating
>
>
> It is useful to be able to pass additional arguments (or override the default
> ones) by appending them to the end of the command line.
> (e.g. {{/v:d}})
> This would help with the general case, though when the plugin is remodelled
> in the other issue, it would be good to cover the most specific ones with
> dedicated fields like , linking debug level to the plugin log level,
> etc.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (NPANDAY-583) Allow additional arguments to be passed to the MSBuild plugin
[
https://issues.apache.org/jira/browse/NPANDAY-583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brett Porter resolved NPANDAY-583.
--
Resolution: Fixed
Fix Version/s: 1.5.0-incubating
> Allow additional arguments to be passed to the MSBuild plugin
> -
>
> Key: NPANDAY-583
> URL: https://issues.apache.org/jira/browse/NPANDAY-583
> Project: NPanday
> Issue Type: Improvement
>Reporter: Brett Porter
>Assignee: Brett Porter
> Fix For: 1.5.0-incubating
>
>
> It is useful to be able to pass additional arguments (or override the default
> ones) by appending them to the end of the command line.
> (e.g. {{/v:d}})
> This would help with the general case, though when the plugin is remodelled
> in the other issue, it would be good to cover the most specific ones with
> dedicated fields like , linking debug level to the plugin log level,
> etc.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (NPANDAY-583) Allow additional arguments to be passed to the MSBuild plugin
Brett Porter created NPANDAY-583:
Summary: Allow additional arguments to be passed to the MSBuild
plugin
Key: NPANDAY-583
URL: https://issues.apache.org/jira/browse/NPANDAY-583
Project: NPanday
Issue Type: Improvement
Reporter: Brett Porter
Assignee: Brett Porter
It is useful to be able to pass additional arguments (or override the default
ones) by appending them to the end of the command line.
(e.g. {{/v:d}})
This would help with the general case, though when the plugin is remodelled in
the other issue, it would be good to cover the most specific ones with
dedicated fields like , linking debug level to the plugin log level, etc.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (NPANDAY-244) Projects the build using the MSBuild plugin should use it entirely
[ https://issues.apache.org/jira/browse/NPANDAY-244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter updated NPANDAY-244: - Fix Version/s: (was: Backlog) > Projects the build using the MSBuild plugin should use it entirely > -- > > Key: NPANDAY-244 > URL: https://issues.apache.org/jira/browse/NPANDAY-244 > Project: NPanday > Issue Type: Bug > Components: Maven Plugins >Reporter: Brett Porter >Priority: Minor > > Currently, the workflow for MSBuild-built projects is this: > 1) run msbuild > 2) rebuild using standard lifecycle, including some generated results from > the previous build > 3) delete the bin directory to avoid confusion > It would be better if the lifecycle could be replaced when using the msbuild > plugin, perhaps through new plugin types, so that it takes on the role that > the compile plugin currently does. Alternatively, the compile plugin could be > taught to use msbuild by configuration instead of having a separate plugin -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (NPANDAY-411) Transitive dependency resolution requires explicit version in a dependent child pom
[
https://issues.apache.org/jira/browse/NPANDAY-411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brett Porter updated NPANDAY-411:
-
Fix Version/s: (was: 2.0)
> Transitive dependency resolution requires explicit version in a dependent
> child pom
> ---
>
> Key: NPANDAY-411
> URL: https://issues.apache.org/jira/browse/NPANDAY-411
> Project: NPanday
> Issue Type: Bug
> Components: Maven Plugins
>Affects Versions: 1.4-incubating
> Environment: $ mvn -v
> Apache Maven 2.2.1 (rdebian-4)
> Java version: 1.6.0_24
> Java home: /usr/lib/jvm/java-6-sun-1.6.0.24/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "linux" version: "2.6.35-28-generic" arch: "amd64" Family: "unix"
>Reporter: John R. Fallows
>Assignee: Lars Corneliussen
> Fix For: 1.5.0-incubating
>
>
> In the past, NPanday required the version of a dependency in pom.xml to be
> explicit, whereas now that has been fixed so that a parent pom.xml can
> specify the version in the dependencyManagement section instead.
> Suppose we have 3 projects called Parent, Library and Executable. The Parent
> pom refers to both Library and Executable projects as modules, and also acts
> as the super pom for both Library and Executable projects. The Executable
> project depends on the Library project. The Parent project defaults the
> version of another dotnet-library (let's say ThirdParty) used by the Library
> project in the Parent's dependencyManagement section.
> The Library project builds successfully. However, when attempting to build
> the Executable project, it complains during dependency resolution that the
> version is missing from ThirdParty and the build fails. Now, while the
> version is physically missing from the Library pom.xml file, it is not
> missing from the effective pom for the Library and should therefore not give
> any error, just as no error is given when the Library project builds.
> {code}
> WARNING: NPANDAY-180-003: Project Version is missing: Group Id = NUnit,
> Artifact Id = NUnit.Framework
> [INFO]
>
> [ERROR] FATAL ERROR
> [INFO]
>
> [INFO] null
> [INFO]
>
> [INFO] Trace
> java.lang.NullPointerException
> at npanday.dao.Project.hashCode(Project.java:329)
> at java.util.HashMap.put(HashMap.java:372)
> at java.util.HashSet.add(HashSet.java:200)
> at npanday.dao.Project.addProjectDependency(Project.java:204)
> at npanday.dao.ProjectFactory.createProjectFrom(ProjectFactory.java:147)
> at
> npanday.dao.impl.ProjectDaoImpl.storeProjectAndResolveDependencies(ProjectDaoImpl.java:866)
> at
> npanday.dao.impl.ProjectDaoImpl.storeProjectAndResolveDependencies(ProjectDaoImpl.java:414)
> at
> npanday.artifact.impl.AssemblyResolverImpl.resolveTransitivelyFor(AssemblyResolverImpl.java:131)
> at
> npanday.plugin.compile.ComponentInitializerMojo.execute(ComponentInitializerMojo.java:86)
> at
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348)
> at
> 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:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
> at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
> at org.codehaus.classworlds.Launcher.main
[jira] [Resolved] (NPANDAY-581) [Regression to NPANDAY-238] switches starting by "/" fails on Linux/Mono
[ https://issues.apache.org/jira/browse/NPANDAY-581?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter resolved NPANDAY-581. -- Resolution: Fixed Assignee: Brett Porter Thanks, I've applied the patch. I believe this would already be exercised by the integration tests if we could get that to the point of running. Have you worked through any of the other current issues on Linux/Mono in your environment? > [Regression to NPANDAY-238] switches starting by "/" fails on Linux/Mono > > > Key: NPANDAY-581 > URL: https://issues.apache.org/jira/browse/NPANDAY-581 > Project: NPanday > Issue Type: Bug > Components: Maven Plugins >Affects Versions: 1.5.0-incubating > Environment: Debian/Mono >Reporter: Mickaël Remars >Assignee: Brett Porter > Labels: linux, mono, patch > Fix For: 1.5.0-incubating > > Attachments: NPANDAY-581.patch > > > The regression seems to appear during NPANDAY-499. > A simple fix may be to always use "-" instead of "/": nunit-console accepts > it on Windows and on Linux. > Patch is attached. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (NPANDAY-581) [Regression to NPANDAY-238] switches starting by "/" fails on Linux/Mono
[ https://issues.apache.org/jira/browse/NPANDAY-581?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13649569#comment-13649569 ] Brett Porter commented on NPANDAY-581: -- thanks for the report - we'll have a look into it > [Regression to NPANDAY-238] switches starting by "/" fails on Linux/Mono > > > Key: NPANDAY-581 > URL: https://issues.apache.org/jira/browse/NPANDAY-581 > Project: NPanday > Issue Type: Bug > Components: Maven Plugins >Affects Versions: 1.5.0-incubating > Environment: Debian/Mono >Reporter: Mickaël Remars > Labels: linux, mono, patch > > The regression seems to appear during NPANDAY-499. > A simple fix may be to always use "-" instead of "/": nunit-console accepts > it on Windows and on Linux. > --- > a/plugins/maven-test-plugin/src/main/java/npanday/plugin/test/TesterMojo.java > +++ > b/plugins/maven-test-plugin/src/main/java/npanday/plugin/test/TesterMojo.java > @@ -168,7 +168,7 @@ public class TesterMojo > > commands.add( testAssemblyPath + File.separator + getTestFileName() > ); > > -String switchChar = "/"; > +String switchChar = "-"; > commands.add( switchChar + "xml:" + > nUnitXmlFilePath.getAbsolutePath() ); > > commands.add( switchChar + "output:" + > nUnitResultOutputPath.getAbsolutePath() ); > -- -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (NPANDAY-581) [Regression to NPANDAY-238] switches starting by "/" fails on Linux/Mono
[ https://issues.apache.org/jira/browse/NPANDAY-581?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter updated NPANDAY-581: - Fix Version/s: 1.5.0-incubating > [Regression to NPANDAY-238] switches starting by "/" fails on Linux/Mono > > > Key: NPANDAY-581 > URL: https://issues.apache.org/jira/browse/NPANDAY-581 > Project: NPanday > Issue Type: Bug > Components: Maven Plugins >Affects Versions: 1.5.0-incubating > Environment: Debian/Mono >Reporter: Mickaël Remars > Labels: linux, mono, patch > Fix For: 1.5.0-incubating > > > The regression seems to appear during NPANDAY-499. > A simple fix may be to always use "-" instead of "/": nunit-console accepts > it on Windows and on Linux. > --- > a/plugins/maven-test-plugin/src/main/java/npanday/plugin/test/TesterMojo.java > +++ > b/plugins/maven-test-plugin/src/main/java/npanday/plugin/test/TesterMojo.java > @@ -168,7 +168,7 @@ public class TesterMojo > > commands.add( testAssemblyPath + File.separator + getTestFileName() > ); > > -String switchChar = "/"; > +String switchChar = "-"; > commands.add( switchChar + "xml:" + > nUnitXmlFilePath.getAbsolutePath() ); > > commands.add( switchChar + "output:" + > nUnitResultOutputPath.getAbsolutePath() ); > -- -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (NPANDAY-525) Make sure UnifiedShellCommandExecutor works with BourneShell
[ https://issues.apache.org/jira/browse/NPANDAY-525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13625636#comment-13625636 ] Brett Porter commented on NPANDAY-525: -- Tests are currently failing on this, so we need to bring it up to speed for the release. > Make sure UnifiedShellCommandExecutor works with BourneShell > > > Key: NPANDAY-525 > URL: https://issues.apache.org/jira/browse/NPANDAY-525 > Project: NPanday > Issue Type: Improvement > Components: Maven Plugins >Reporter: Lars Corneliussen > Fix For: 1.5.0-incubating > > > As Part of NPANDAY-509 the execution engine for executing shell commands was > replaced. We have to make sure, that quoting++ still works as expected on > !Windows. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (NPANDAY-572) When settings.xml already has a profiles section, configuring the remote repository from the AddIn creates an invalid settings file
[
https://issues.apache.org/jira/browse/NPANDAY-572?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brett Porter resolved NPANDAY-572.
--
Resolution: Fixed
Fix Version/s: 1.5.0-incubating
Assignee: Brett Porter
Fixed, also made it set the mirror setting.
> When settings.xml already has a profiles section, configuring the remote
> repository from the AddIn creates an invalid settings file
> ---
>
> Key: NPANDAY-572
> URL: https://issues.apache.org/jira/browse/NPANDAY-572
> Project: NPanday
> Issue Type: Bug
> Components: Visual Studio Add-in
>Reporter: Brett Porter
>Assignee: Brett Porter
> Fix For: 1.5.0-incubating
>
>
> # Create a {{settings.xml}} file with a {{}} section
> # Open an NPanday project in VS
> # Select "Add Maven Artifact..." from the context menu on the project
> # Go to the "Configure Repository" tab
> # Type in {{http://repo.maven.apache.org/maven2/}} and press "Update"
> The resulting {{settings.xml}} file has two {{}} sections, one
> before {{}} and one after.
> A better alternative may be to use this field to set the mirror instead.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (NPANDAY-580) WPF XBAP applications do not get attached to the build process
[ https://issues.apache.org/jira/browse/NPANDAY-580?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter resolved NPANDAY-580. -- Resolution: Fixed Fix Version/s: 1.5.0-incubating > WPF XBAP applications do not get attached to the build process > -- > > Key: NPANDAY-580 > URL: https://issues.apache.org/jira/browse/NPANDAY-580 > Project: NPanday > Issue Type: Bug >Affects Versions: 1.5.0-incubating >Reporter: Brett Porter >Assignee: Brett Porter > Fix For: 1.5.0-incubating > > > If a WPF project has set, it generates an XBAP file by virtue > of the included call to MSBuild. These artifacts should be installed into the > local/remote repository along with the generated .exe file. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (NPANDAY-580) WPF XBAP applications do not get attached to the build process
Brett Porter created NPANDAY-580: Summary: WPF XBAP applications do not get attached to the build process Key: NPANDAY-580 URL: https://issues.apache.org/jira/browse/NPANDAY-580 Project: NPanday Issue Type: Bug Affects Versions: 1.5.0-incubating Reporter: Brett Porter Assignee: Brett Porter If a WPF project has set, it generates an XBAP file by virtue of the included call to MSBuild. These artifacts should be installed into the local/remote repository along with the generated .exe file. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (NPANDAY-558) Library importer requires nuget and manifest info on the path
[ https://issues.apache.org/jira/browse/NPANDAY-558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13591385#comment-13591385 ] Brett Porter commented on NPANDAY-558: -- Note: there's a profile to remove in plugins/library-importer-maven-plugin/pom.xml when this is done to re-enable that test > Library importer requires nuget and manifest info on the path > - > > Key: NPANDAY-558 > URL: https://issues.apache.org/jira/browse/NPANDAY-558 > Project: NPanday > Issue Type: Bug > Components: Library Importer >Affects Versions: 1.5.0-incubating >Reporter: Lars Corneliussen > Labels: nuget, path > Fix For: 1.5.0-incubating > > > They should be resolved from the repo instead - and be redeployed to npandays > 3rdparty repository. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (NPANDAY-579) Ability to copy artifacts into the local repository as part of the import process
[ https://issues.apache.org/jira/browse/NPANDAY-579?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter resolved NPANDAY-579. -- Resolution: Fixed Fix Version/s: 1.5.0-incubating Assignee: Brett Porter > Ability to copy artifacts into the local repository as part of the import > process > - > > Key: NPANDAY-579 > URL: https://issues.apache.org/jira/browse/NPANDAY-579 > Project: NPanday > Issue Type: New Feature >Reporter: Brett Porter >Assignee: Brett Porter > Fix For: 1.5.0-incubating > > > It is quite common for Visual Studio projects to result in a number of > references to the GAC, or to system paths, which make for non-portable > projects. It would be useful for the import to have an option to copy > artifacts to the local repository, and then use normal Maven repository > references. In combination with NPANDAY-578 this gives you all the artifacts > arranged in a way that can be loaded into a remote repository. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (NPANDAY-578) Project importer should use assembly search paths ahead of GAC
[
https://issues.apache.org/jira/browse/NPANDAY-578?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brett Porter resolved NPANDAY-578.
--
Resolution: Fixed
Fix Version/s: 1.5.0-incubating
Assignee: Brett Porter
> Project importer should use assembly search paths ahead of GAC
> --
>
> Key: NPANDAY-578
> URL: https://issues.apache.org/jira/browse/NPANDAY-578
> Project: NPanday
> Issue Type: Improvement
> Components: Project Importer
>Reporter: Brett Porter
>Assignee: Brett Porter
> Fix For: 1.5.0-incubating
>
>
> From {{Microsoft.Common.targets}}:
> {code}
>
> {code}
> Not all of these steps are suitable for NPanday, and it always includes the
> Maven repository as the first location it searches. Currently, only (3) and
> (7) from the above are implemented.
> When a dependency hasn't yet been loaded it is often located in the GAC, but
> these frequently differ in version from the reference assemblies distributed
> with most SDKs.
> Adding (4) and (5) would make this more reliable, and give users a clearer
> path to load into their artifact repository.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (NPANDAY-579) Ability to copy artifacts into the local repository as part of the import process
Brett Porter created NPANDAY-579: Summary: Ability to copy artifacts into the local repository as part of the import process Key: NPANDAY-579 URL: https://issues.apache.org/jira/browse/NPANDAY-579 Project: NPanday Issue Type: New Feature Reporter: Brett Porter It is quite common for Visual Studio projects to result in a number of references to the GAC, or to system paths, which make for non-portable projects. It would be useful for the import to have an option to copy artifacts to the local repository, and then use normal Maven repository references. In combination with NPANDAY-578 this gives you all the artifacts arranged in a way that can be loaded into a remote repository. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (NPANDAY-578) Project importer should use assembly search paths ahead of GAC
[
https://issues.apache.org/jira/browse/NPANDAY-578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13590288#comment-13590288
]
Brett Porter commented on NPANDAY-578:
--
I've done this, but made them both optional, since many users will wish to
avoid the hardcoded paths and rather ensure that the artifacts have been loaded
into a repository.
> Project importer should use assembly search paths ahead of GAC
> --
>
> Key: NPANDAY-578
> URL: https://issues.apache.org/jira/browse/NPANDAY-578
> Project: NPanday
> Issue Type: Improvement
> Components: Project Importer
>Reporter: Brett Porter
>
> From {{Microsoft.Common.targets}}:
> {code}
>
> {code}
> Not all of these steps are suitable for NPanday, and it always includes the
> Maven repository as the first location it searches. Currently, only (3) and
> (7) from the above are implemented.
> When a dependency hasn't yet been loaded it is often located in the GAC, but
> these frequently differ in version from the reference assemblies distributed
> with most SDKs.
> Adding (4) and (5) would make this more reliable, and give users a clearer
> path to load into their artifact repository.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (NPANDAY-578) Project importer should use assembly search paths ahead of GAC
Brett Porter created NPANDAY-578:
Summary: Project importer should use assembly search paths ahead
of GAC
Key: NPANDAY-578
URL: https://issues.apache.org/jira/browse/NPANDAY-578
Project: NPanday
Issue Type: Improvement
Components: Project Importer
Reporter: Brett Porter
>From {{Microsoft.Common.targets}}:
{code}
{code}
Not all of these steps are suitable for NPanday, and it always includes the
Maven repository as the first location it searches. Currently, only (3) and (7)
from the above are implemented.
When a dependency hasn't yet been loaded it is often located in the GAC, but
these frequently differ in version from the reference assemblies distributed
with most SDKs.
Adding (4) and (5) would make this more reliable, and give users a clearer path
to load into their artifact repository.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (NPANDAY-566) Custom NPanday-aware copy-dependencies / list-dependencies plugin
[ https://issues.apache.org/jira/browse/NPANDAY-566?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter updated NPANDAY-566: - Fix Version/s: 1.5.0-incubating Saw some work on trunk for this too - what needs to be done to finish? > Custom NPanday-aware copy-dependencies / list-dependencies plugin > - > > Key: NPANDAY-566 > URL: https://issues.apache.org/jira/browse/NPANDAY-566 > Project: NPanday > Issue Type: New Feature > Components: Maven Plugins >Affects Versions: 1.5.0-incubating >Reporter: Lars Corneliussen >Assignee: Lars Corneliussen > Fix For: 1.5.0-incubating > > > When copying dependencies we have to run our own resolver, and we'd also like > to copy along pdb+xml+... as soon as we have those... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (NPANDAY-567) Copy along app.config (and transform with app.test.config) for test runs
[ https://issues.apache.org/jira/browse/NPANDAY-567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter updated NPANDAY-567: - Fix Version/s: 1.5.0-incubating I see there's some work in trunk for this already - what needs to be done to finish? > Copy along app.config (and transform with app.test.config) for test runs > > > Key: NPANDAY-567 > URL: https://issues.apache.org/jira/browse/NPANDAY-567 > Project: NPanday > Issue Type: Improvement > Components: Maven Plugins >Reporter: Lars Corneliussen >Assignee: Lars Corneliussen > Fix For: 1.5.0-incubating > > > Currently there is no way to configure tests... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (NPANDAY-210) Deprecate includeSources in favor of include/exclude patterns
[ https://issues.apache.org/jira/browse/NPANDAY-210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter updated NPANDAY-210: - Is this still in progress? What else needs to be done? > Deprecate includeSources in favor of include/exclude patterns > - > > Key: NPANDAY-210 > URL: https://issues.apache.org/jira/browse/NPANDAY-210 > Project: NPanday > Issue Type: Bug > Components: Maven Plugins >Reporter: Brett Porter >Assignee: Lars Corneliussen >Priority: Minor > Fix For: 1.5.0-incubating > > > This configuration was added to support certain types of Visual Studio > project nesting that we have concluded not to support. It currently slows the > build due to the extra copying and makes the POM harder to maintain. We > should remove it in favour of something closer to the Maven compiler plugin's > configuration, with and , but defaulting to including > all relevant files. > That is, > - by default, csc is given all *.cs files in the source directory and > subdirectories; and vbc is given all *.vb files in the source directory and > subdirectories. No other files need be compiled. > - files in target, bin, obj are excluded by default > - files that are not a part of the csproj/vbproj (by being excluded or never > added) are excluded from compile by setting an > ... configuration on the plugin. The addin > would be responsible for maintaining this - basically a reverse of the > current functionality, but much cleaner in its implementation and appearance, > and more robust against sync issues in the IDE. > To implement the last point, the addin will need to be able to scan for the > available files in the same way as the compile plugin would, then add exclude > items for all that are not present in the csproj/vbproj, as excluded items > are not accessible from the project instances. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (NPANDAY-418) Automatically exclude test sources from main sources in compile-plugin
[
https://issues.apache.org/jira/browse/NPANDAY-418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13585258#comment-13585258
]
Brett Porter commented on NPANDAY-418:
--
What needs to be done to finish this off?
> Automatically exclude test sources from main sources in compile-plugin
> --
>
> Key: NPANDAY-418
> URL: https://issues.apache.org/jira/browse/NPANDAY-418
> Project: NPanday
> Issue Type: Improvement
> Components: Maven Plugins
>Affects Versions: 1.4-incubating
>Reporter: Lars Corneliussen
>Assignee: Lars Corneliussen
> Labels: compile, test
> Fix For: 1.5.0-incubating
>
>
> I'd like to run a configuration, where all test sources are automatically
> excluded from the main compilation.
> Usually in .NET-Projects, Tests are in a separate assembly. NPanday supports
> having tests within the same Project, but then they have to be in a separate
> folder.
> I'd like support for these two layouts:
> {code:title=Layout one}
> MyProj
> - Some.cs
> - More
> - Here.cs
> Test
> - SomeTest.cs
> - More
> - HereTest.cs
> {code}
> {code:title=Layout two}
> MyProj
> - Some.cs
> - SomeTest.cs
> - More
> - Here.cs
> - HereTest.cs
> {code}
> In both cases it should be sufficient to tell NPanday how to find test
> fixtures. Then it can figure out that those are not to be included in the
> main artifact.
> What do you think?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (NPANDAY-563) Generic MSDeploy synchronization mojo
[ https://issues.apache.org/jira/browse/NPANDAY-563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13585255#comment-13585255 ] Brett Porter commented on NPANDAY-563: -- Is this still in progress, or can we move to next release? > Generic MSDeploy synchronization mojo > - > > Key: NPANDAY-563 > URL: https://issues.apache.org/jira/browse/NPANDAY-563 > Project: NPanday > Issue Type: New Feature > Components: Maven Plugins >Reporter: Lars Corneliussen >Assignee: Lars Corneliussen > Fix For: 1.5.0-incubating > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (NPANDAY-556) Importer for Nuget Packages
[
https://issues.apache.org/jira/browse/NPANDAY-556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13585256#comment-13585256
]
Brett Porter commented on NPANDAY-556:
--
What's left to do on this? I note that the plugin exists.
> Importer for Nuget Packages
> ---
>
> Key: NPANDAY-556
> URL: https://issues.apache.org/jira/browse/NPANDAY-556
> Project: NPanday
> Issue Type: New Feature
> Components: Development Setup, Maven Plugins
>Affects Versions: 1.5.0-incubating
>Reporter: Lars Corneliussen
>Assignee: Lars Corneliussen
> Labels: nuget
> Fix For: 1.5.0-incubating
>
>
> Nuget Packages are much broader than Maven Artifacts. Our first thought was
> to implement a repository layout that would enable for resolving nuget
> packages directly (see NPANDAY-372).
> But those packages come in various shapes and are not as easily converted to
> {{dotnet-library}} artifacts as first thought.
> h3. Library Importer
> Instead we will create a plugin, that helps importing nuget packages (and
> soon also plain DLL-libs) into maven artifacts. As a general rule, each DLL
> contained in a single {{nupkg}} will result in a separate maven artifact.
> Some of the challenges we see:
> h4. Versions
> Nuget packages (and dlls) have four version numbers while maven only has
> three. In most cases those are not used in nuget, but if, there has to be
> some manual mapping.
> h4. Multi-targeted packages
> Nuget packages may contain libraries for different target frameworks (net20,
> 35, wp, sl, ...); something that we'd like to support in NPanday too
> (NPANDAY-405)
> As a first approach, you'll have to specify which of the versions to import.
> We could also support a mapping from framework versions to maven version
> qualifiers, as for example {{1.2-net20}}
> h4. Dependencies
> Since there is no easy mapping from package to artifact, it is not that easy
> to convert the dependencies either. For each import it will be necessary to
> specify how the reps are mapped.
> h4. Prerelease versions
> Nuget >= 1.6 does also support prerelease versions. These should be mapped to
> SNAPSHOT, if possible.
> h4. What more?
> Please comment or edit, if you see more challenges that I haven't seen yet.
> h2. Technical approach
> A plugin with it's own lifecycle will 'compile' import declarations and then
> perform the import on 'compile'; then install and deploy the imported
> packages on the corresponding maven life cycles 'install' and 'deploy'.
> {code:title=example import declaration}
> http://npanday.apache.org/library-import/1.0.0";>
>
> NUnit
>
>
>
> net40
>
>
>
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (NPANDAY-568) When removing the last test, npanday still runs the previously compiled tests
[ https://issues.apache.org/jira/browse/NPANDAY-568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter updated NPANDAY-568: - Fix Version/s: (was: 1.5.0-incubating) > When removing the last test, npanday still runs the previously compiled tests > - > > Key: NPANDAY-568 > URL: https://issues.apache.org/jira/browse/NPANDAY-568 > Project: NPanday > Issue Type: Bug > Components: Maven Plugins >Affects Versions: 1.5.0-incubating >Reporter: Lars Corneliussen > > We have to remove the test-dll if it exists and no tests are found... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (NPANDAY-567) Copy along app.config (and transform with app.test.config) for test runs
[ https://issues.apache.org/jira/browse/NPANDAY-567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter updated NPANDAY-567: - Fix Version/s: (was: 1.5.0-incubating) > Copy along app.config (and transform with app.test.config) for test runs > > > Key: NPANDAY-567 > URL: https://issues.apache.org/jira/browse/NPANDAY-567 > Project: NPanday > Issue Type: Improvement > Components: Maven Plugins >Reporter: Lars Corneliussen >Assignee: Lars Corneliussen > > Currently there is no way to configure tests... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (NPANDAY-566) Custom NPanday-aware copy-dependencies / list-dependencies plugin
[ https://issues.apache.org/jira/browse/NPANDAY-566?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter updated NPANDAY-566: - Fix Version/s: (was: 1.5.0-incubating) > Custom NPanday-aware copy-dependencies / list-dependencies plugin > - > > Key: NPANDAY-566 > URL: https://issues.apache.org/jira/browse/NPANDAY-566 > Project: NPanday > Issue Type: New Feature > Components: Maven Plugins >Affects Versions: 1.5.0-incubating >Reporter: Lars Corneliussen >Assignee: Lars Corneliussen > > When copying dependencies we have to run our own resolver, and we'd also like > to copy along pdb+xml+... as soon as we have those... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (NPANDAY-577) Plugins other than the compile plugin don't support framework v3.0
Brett Porter created NPANDAY-577: Summary: Plugins other than the compile plugin don't support framework v3.0 Key: NPANDAY-577 URL: https://issues.apache.org/jira/browse/NPANDAY-577 Project: NPanday Issue Type: Bug Components: Maven Plugins Affects Versions: 1.4-incubating Reporter: Brett Porter Fix For: 1.5.0-incubating Most plugins list v3.5 as a valid framework, but not v3.0 - only the compile plugin includes that. That means that projects that use resgen, for example, will fail on that target framework. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (NPANDAY-577) Plugins other than the compile plugin don't support framework v3.0
[ https://issues.apache.org/jira/browse/NPANDAY-577?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter resolved NPANDAY-577. -- Resolution: Fixed Assignee: Brett Porter > Plugins other than the compile plugin don't support framework v3.0 > -- > > Key: NPANDAY-577 > URL: https://issues.apache.org/jira/browse/NPANDAY-577 > Project: NPanday > Issue Type: Bug > Components: Maven Plugins >Affects Versions: 1.4-incubating >Reporter: Brett Porter >Assignee: Brett Porter > Fix For: 1.5.0-incubating > > > Most plugins list v3.5 as a valid framework, but not v3.0 - only the compile > plugin includes that. That means that projects that use resgen, for example, > will fail on that target framework. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (NPANDAY-569) local dependency and Npanday
[
https://issues.apache.org/jira/browse/NPANDAY-569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13571042#comment-13571042
]
Brett Porter commented on NPANDAY-569:
--
Sorry for overlooking this issue. Are you saying that you are referencing a
dependency that does not have a POM in the local repository? Can you clarify
how the DLL was added to ~/.m2?
> local dependency and Npanday
>
>
> Key: NPANDAY-569
> URL: https://issues.apache.org/jira/browse/NPANDAY-569
> Project: NPanday
> Issue Type: Bug
>Reporter: François
>
> When adding the following a dll from a local .m2, NPanday tries to build the
> pom in the dependency repo. This leads to an error because it the
> configuration does not fit anymore. In the .m2 folder there is the
> corresponding dll. Here is the error, which is generate from the console
> …
> [INFO] --- maven-compile-plugin:1.4.0-incubating:initialize
> (default-initialize) @ ServiceTestConsole ---
> Jul 04, 2012 11:45:29 PM npanday.dao.impl.ProjectDaoImpl
> storeProjectAndResolveDependencies
> WARNING: NPANDAY-180-018: Not found in local repository, now retrieving
> artifact from
> wagon:org.openengsb.loom.csharp.common.bridge:ExampleDomainEventsInterfaces:dotnet-library:1.0.0-SNAPSHOT,
> Failed Path Check =
> C:\Users\User\Projekts\Example\target\ExampleDomainEventsInterfaces.dll
> Jul 04, 2012 11:45:29 PM
> npanday.dao.impl.ProjectDaoImplstoreProjectAndResolveDependencies
> WARNING: NPANDAY-180-018: Not found in local repository, now retrieving
> artifact from
> wagon:org.openengsb.loom.csharp.common.bridge:ExampleDomainInterfaces:dotnet-library:1.0.0-SNAPSHOT,
> Failed Path Check =
> C:\Users\User\Projekts\Example\target\ExampleDomainInterfaces.dll
> Jul 04, 2012 11:45:29 PM npanday.dao.impl.ProjectDaoImpl
> storeProjectAndResolveDependencies
> WARNING: NPANDAY-180-018: Not found in local repository, now retrieving
> artifact from
> wagon:org.openengsb.loom.csharp.common.bridge:Implementation:dotnet-library:1.0.0-SNAPSHOT,
> Failed Path Check = C:\Users\User\Projekts\Example\target\Implementation.dll
> Jul 04, 2012 11:45:29 PM npanday.dao.impl.ProjectDaoImpl
> storeProjectAndResolveDependencies
> WARNING: NPANDAY-180-018: Not found in local repository, now retrieving
> artifact from
> wagon:org.openengsb.loom.csharp.common.bridge:Interface:dotnet-library:1.0.0-SNAPSHOT,
> Failed Path Check = C:\Users\User\Projekts\Example\target\Interface.dll
> Jul 04, 2012 11:45:29 PM npanday.PathUtil getDotNetArtifact
> WARNING:
> NPANDAY-1005-0001: Error copying dependency
> org.openengsb.domain:org.openengsb.domain.example:wsdl:ExampleDomainEvents:3.0.0-SNAPSHOT:compile
> File
> C:\Users\User\.m2\repository\org\openengsb\domain\org.openengsb.domain.example\3.0.0-SNAPSHOT\org.openengsb.domain.example
> -3.0.0-SNAPSHOT-ExampleDomainEvents.jar does not exist
> Jul 04, 2012 11:45:29 PM npanday.PathUtil getDotNetArtifact
> WARNING:
> NPANDAY-1005-0001: Error copying dependency
> org.openengsb.domain:org.openengsb.domain.example:wsdl:ExampleDomainEvents:3.0.0-SNAPSHOT:compile
> File
> C:\Users\User\.m2\repository\org\openengsb\domain\org.openengsb.domain.example\3.0.0-SNAPSHOT\org.openengsb.domain.example
> -3.0.0-SNAPSHOT-ExampleDomainEvents.jar does not exist
> Jul 04, 2012 11:45:29 PM npanday.dao.impl.ProjectDaoImpl
> storeProjectAndResolveDependencies
> WARNING: NPANDAY-180-018: Not found in local repository, now retrieving
> artifact from
> wagon:org.openengsb.domain:org.openengsb.domain.example:wsdl:ExampleDomainEvents:3.0.0-SNAPSHOT,
> Failed Path Check =
> C:\Users\User\Projekts\Example\target\org.openengsb.domain.example.wsdl
> Jul 04, 2012 11:45:29 PM npanday.dao.ProjectFactory
> logAndVerifyProjectParameters
> WARNING: NPANDAY-180-003: Project Version is missing: Group Id =
> org.openengsb.labs.delegation, Artifact Id =
> org.openengsb.labs.delegation.service
> …
> The pom in the .m2 repo looks like the following:
> …
>
>
>
> org.apache.maven.plugins
> maven-dependency-plugin
>
>
> copy
> compile
>
> copy
>
>
>
>
> org.openengsb.domain
> org.openengsb.domain.example
> ExampleDomainEvents
> wsdl
> false
>
> ${project.build.directory}
> ExampleDomainEvents.wsdl
>
>
>
>
>
>
>
> org.openengsb.loom.csharp.common
> wsdltodll-maven-plugin
>
>
> ${project.build.directory}\ExampleDomainEvents.wsdl
> ExampleDomainEvents
>
>
>
>
[jira] [Updated] (NPANDAY-570) Unable to build NPanday due to missing npanday-settings.xml
[ https://issues.apache.org/jira/browse/NPANDAY-570?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter updated NPANDAY-570: - Fix Version/s: 1.5.0-incubating Will need to take a closer look how this might have occurred with the latest. FYI, we've fixed the problems with the repository. > Unable to build NPanday due to missing npanday-settings.xml > --- > > Key: NPANDAY-570 > URL: https://issues.apache.org/jira/browse/NPANDAY-570 > Project: NPanday > Issue Type: Bug > Components: Development Setup >Affects Versions: 1.5.0-incubating > Environment: Windows 7 Professional x64, Java 1.7 (x86), Maven 3.0.4, > Windows SDK 7.1 >Reporter: Julian Cromarty > Labels: build > Fix For: 1.5.0-incubating > > > Possibly related to NPANDAY-413 > Having been unsuccessful in getting NPanday to work from the msi installer > (it doesn't seem to install the NPanday plugins anywhere and repo.npanday.org > doesn't exist anymore) I figured I'd try building it from source. I followed > the instructions on the site, i.e. running "mvn clean install" from the > directory where I checked out the source and it fails when trying to build > NPanday.Model.Pom with the following error: > [INFO] > > [INFO] Building NPanday :: .NET Model :: POM 1.5.0-incubating-SNAPSHOT > [INFO] > > [INFO] > [INFO] --- maven-compile-plugin:1.5.0-incubating-SNAPSHOT:initialize > (default-initialize) @ NPanday.Model.Pom --- > [WARNING] Invalid POM for NUnit:NUnit.Framework:dotnet-library:2.2.8.0, > transitive dependencies (if any) will not be available, enable debug logging > for more details > [INFO] > [INFO] --- > NPanday.Plugin.Settings.JavaBinding:1.5.0-incubating-SNAPSHOT:generate-settings > (default-generate-settings) @ NPanday.Model.Pom --- > [INFO] NPANDAY-119-000: Excecution of generate-settings has been skipped. > [INFO] > [INFO] --- > maven-compile-plugin:1.5.0-incubating-SNAPSHOT:generate-assembly-info > (default-generate-assembly-info) @ NPanday.Model.Pom --- > [INFO] > > [INFO] Reactor Summary: > [INFO] > [INFO] NPanday :: .NET Model :: POM .. FAILURE [0.747s] > [INFO] NPanday :: .NET Model :: Settings . SKIPPED > [INFO] NPanday :: .NET Model :: AutomationExtensibility .. SKIPPED > [INFO] NPanday :: .NET Utils . SKIPPED > [INFO] NPanday :: .NET Artifact .. SKIPPED > [INFO] NPanday :: .NET Plugin SKIPPED > [INFO] NPanday :: .NET Plugin MojoGenerator .. SKIPPED > [INFO] NPanday :: .NET Plugin Loader . SKIPPED > [INFO] NPanday :: .NET Plugin Runner . SKIPPED > [INFO] NPanday :: Project Importer ... SKIPPED > [INFO] NPanday :: Project Importer :: Engine . SKIPPED > [INFO] NPanday :: Project Importer :: Console SKIPPED > [INFO] NPanday :: VisualStudio Addin . SKIPPED > [INFO] NPanday :: VisualStudio Project Wizard SKIPPED > [INFO] NPanday :: .NET Plugins ... SKIPPED > [INFO] NPanday :: Addin Plugin ... SKIPPED > [INFO] NPanday :: Devenv Plugin .. SKIPPED > [INFO] NPanday :: ResX Plugin SKIPPED > [INFO] NPanday :: Settings Plugin SKIPPED > [INFO] NPanday :: SysRef Plugin .. SKIPPED > [INFO] NPanday :: Msbuild Plugin . SKIPPED > [INFO] > > [INFO] BUILD FAILURE > [INFO] > > [INFO] Total time: 2.131s > [INFO] Finished at: Fri Aug 31 09:58:01 BST 2012 > [INFO] Final Memory: 18M/44M > [INFO] > > [ERROR] Failed to execute goal > org.apache.npanday.plugins:maven-compile-plugin:1.5.0-incubating-SNAPSHOT:generate-assembly-info > (default-generate-assembly-info) on project NPanday.Model.Pom: > NPANDAY-108-005: > nfigured settings file does not exist: > C:\Users\jooles\.m2\npanday-settings.xml -> [Help 1] > org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute > goal > org.apache.npanday.plugins:maven-compile-plugin:1.5.0-incubating-SNAPSHOT:generate-assembly-info > (default-generate-assembly-info) > n project NPanday.Model.Pom: NPANDAY-108-005: Configured settings file does > not exist: C:\Users\jooles\.m2\npanday-set
[jira] [Updated] (NPANDAY-576) Add capability to add pdb artifact for .net project
[ https://issues.apache.org/jira/browse/NPANDAY-576?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter updated NPANDAY-576: - Fix Version/s: 1.5.0-incubating > Add capability to add pdb artifact for .net project > --- > > Key: NPANDAY-576 > URL: https://issues.apache.org/jira/browse/NPANDAY-576 > Project: NPanday > Issue Type: New Feature > Components: Maven Plugins >Affects Versions: 1.5.0-incubating >Reporter: Victor Stefoglo > Fix For: 1.5.0-incubating > > Attachments: maven-plugins.patch > > > Attach PDB artifacts for .net project it's useful for Integration test > projects and coverage tools. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (NPANDAY-571) Support Azure SDK 1.7 (June 2012)
[
https://issues.apache.org/jira/browse/NPANDAY-571?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13463739#comment-13463739
]
Brett Porter commented on NPANDAY-571:
--
Added the registry key for 1.7 explicitly to show that it works - will try and
make that generic by replacing with ${executableVersion} in a subsequent commit
> Support Azure SDK 1.7 (June 2012)
> -
>
> Key: NPANDAY-571
> URL: https://issues.apache.org/jira/browse/NPANDAY-571
> Project: NPanday
> Issue Type: New Feature
>Reporter: Brett Porter
>
> Currently, the Azure plugin only supports 1.6 (November 2011):
> http://incubator.apache.org/npanday/docs/1.5.0-incubating-SNAPSHOT/plugins/azure-maven-plugin/azure-sdk-versions.html
> We need to be able to run CSPACK from 1.7, which resides in: {{C:\Program
> Files\Microsoft SDKs\Windows Azure\.NET SDK\2012-06}}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (NPANDAY-573) remove maven-vsinstaller-plugin
[ https://issues.apache.org/jira/browse/NPANDAY-573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13463508#comment-13463508 ] Brett Porter commented on NPANDAY-573: -- removed integration test that was failing. Will come back to the plugin and documentation at a later time. > remove maven-vsinstaller-plugin > --- > > Key: NPANDAY-573 > URL: https://issues.apache.org/jira/browse/NPANDAY-573 > Project: NPanday > Issue Type: Task >Reporter: Brett Porter >Priority: Blocker > Fix For: 1.5.0-incubating > > > NPANDAY-231 has broken the vsinstaller plugin. Rather than fix it, we should > push our effort towards using the MSI instead. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (NPANDAY-573) remove maven-vsinstaller-plugin
Brett Porter created NPANDAY-573: Summary: remove maven-vsinstaller-plugin Key: NPANDAY-573 URL: https://issues.apache.org/jira/browse/NPANDAY-573 Project: NPanday Issue Type: Task Reporter: Brett Porter Priority: Blocker Fix For: 1.5.0-incubating NPANDAY-231 has broken the vsinstaller plugin. Rather than fix it, we should push our effort towards using the MSI instead. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (NPANDAY-571) Support Azure SDK 1.7 (June 2012)
[
https://issues.apache.org/jira/browse/NPANDAY-571?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13461765#comment-13461765
]
Brett Porter commented on NPANDAY-571:
--
Yep, confirmed that the same registry key can be used if the version is
substituted. I think we should look into subbing executableVersion into the
file rather than specifying an extra definition of CSPACK.
> Support Azure SDK 1.7 (June 2012)
> -
>
> Key: NPANDAY-571
> URL: https://issues.apache.org/jira/browse/NPANDAY-571
> Project: NPanday
> Issue Type: New Feature
>Reporter: Brett Porter
>
> Currently, the Azure plugin only supports 1.6 (November 2011):
> http://incubator.apache.org/npanday/docs/1.5.0-incubating-SNAPSHOT/plugins/azure-maven-plugin/azure-sdk-versions.html
> We need to be able to run CSPACK from 1.7, which resides in: {{C:\Program
> Files\Microsoft SDKs\Windows Azure\.NET SDK\2012-06}}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (NPANDAY-572) When settings.xml already has a profiles section, configuring the remote repository from the AddIn creates an invalid settings file
Brett Porter created NPANDAY-572:
Summary: When settings.xml already has a profiles section,
configuring the remote repository from the AddIn creates an invalid settings
file
Key: NPANDAY-572
URL: https://issues.apache.org/jira/browse/NPANDAY-572
Project: NPanday
Issue Type: Bug
Components: Visual Studio Add-in
Reporter: Brett Porter
# Create a {{settings.xml}} file with a {{}} section
# Open an NPanday project in VS
# Select "Add Maven Artifact..." from the context menu on the project
# Go to the "Configure Repository" tab
# Type in {{http://repo.maven.apache.org/maven2/}} and press "Update"
The resulting {{settings.xml}} file has two {{}} sections, one before
{{}} and one after.
A better alternative may be to use this field to set the mirror instead.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (NPANDAY-571) Support Azure SDK 1.7 (June 2012)
Brett Porter created NPANDAY-571:
Summary: Support Azure SDK 1.7 (June 2012)
Key: NPANDAY-571
URL: https://issues.apache.org/jira/browse/NPANDAY-571
Project: NPanday
Issue Type: New Feature
Reporter: Brett Porter
Currently, the Azure plugin only supports 1.6 (November 2011):
http://incubator.apache.org/npanday/docs/1.5.0-incubating-SNAPSHOT/plugins/azure-maven-plugin/azure-sdk-versions.html
We need to be able to run CSPACK from 1.7, which resides in: {{C:\Program
Files\Microsoft SDKs\Windows Azure\.NET SDK\2012-06}}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Reopened] (NPANDAY-537) Add dotnet-windows-executable packaging
[ https://issues.apache.org/jira/browse/NPANDAY-537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter reopened NPANDAY-537: -- I'll revisit the solution > Add dotnet-windows-executable packaging > --- > > Key: NPANDAY-537 > URL: https://issues.apache.org/jira/browse/NPANDAY-537 > Project: NPanday > Issue Type: Bug >Reporter: Brett Porter >Assignee: Brett Porter > Fix For: 1.5.0-incubating > > > In an earlier release, "winexe" was deprecated in favour of a unified > "dotnet-executable" (along with "exe"). However, there is still a valid use > case for a separate packaging that triggers the alternate /target parameter > to CSC that will generate a windows executable (with no console window > attached, for example). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (NPANDAY-247) exe.config handling is hardcoded and will not deploy to the repository
Brett Porter assigned NPANDAY-247 to Unassigned exe.config handling is hardcoded and will not deploy to the repository Change By: Brett Porter (15/May/12 11:18) Assignee: Brett Porter This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (NPANDAY-210) Deprecate includeSources in favor of include/exclude patterns
[ https://issues.apache.org/jira/browse/NPANDAY-210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13269772#comment-13269772 ] Brett Porter commented on NPANDAY-210: -- Deprecate sounds better. > Deprecate includeSources in favor of include/exclude patterns > - > > Key: NPANDAY-210 > URL: https://issues.apache.org/jira/browse/NPANDAY-210 > Project: NPanday > Issue Type: Bug > Components: Maven Plugins >Reporter: Brett Porter >Assignee: Lars Corneliussen >Priority: Minor > Fix For: 1.5.0-incubating > > > This configuration was added to support certain types of Visual Studio > project nesting that we have concluded not to support. It currently slows the > build due to the extra copying and makes the POM harder to maintain. We > should remove it in favour of something closer to the Maven compiler plugin's > configuration, with and , but defaulting to including > all relevant files. > That is, > - by default, csc is given all *.cs files in the source directory and > subdirectories; and vbc is given all *.vb files in the source directory and > subdirectories. No other files need be compiled. > - files in target, bin, obj are excluded by default > - files that are not a part of the csproj/vbproj (by being excluded or never > added) are excluded from compile by setting an > ... configuration on the plugin. The addin > would be responsible for maintaining this - basically a reverse of the > current functionality, but much cleaner in its implementation and appearance, > and more robust against sync issues in the IDE. > To implement the last point, the addin will need to be able to scan for the > available files in the same way as the compile plugin would, then add exclude > items for all that are not present in the csproj/vbproj, as excluded items > are not accessible from the project instances. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (NPANDAY-457) Nothing happens when you click on browse button in dialog "Change Maven settings.xml" if M2_HOME doesn't exist
[ https://issues.apache.org/jira/browse/NPANDAY-457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter updated NPANDAY-457: - Fix Version/s: (was: 1.5.0-incubating) Backlog > Nothing happens when you click on browse button in dialog "Change Maven > settings.xml" if M2_HOME doesn't exist > -- > > Key: NPANDAY-457 > URL: https://issues.apache.org/jira/browse/NPANDAY-457 > Project: NPanday > Issue Type: Bug > Components: Visual Studio Add-in >Affects Versions: 1.4-incubating > Environment: OS : Windows 7 SP1 64bits > Visual Studio 2005 SP1 >Reporter: Kevin Lecouvey >Priority: Minor > Fix For: Backlog > > > In dialog "Change Maven settings.xml", if M2_HOME environment variable > doesn't exist and you click on 'Browse...' button nothing happens. > There is an unmanaged exception in > getInitialDirectory():ChangeMavenSettingsXmlForm.cs. > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (NPANDAY-299) Visual Studio Addin should have a feature to set the version of NPanday to use in the POM
[ https://issues.apache.org/jira/browse/NPANDAY-299?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter updated NPANDAY-299: - Fix Version/s: (was: 1.5.0-incubating) Backlog > Visual Studio Addin should have a feature to set the version of NPanday to > use in the POM > - > > Key: NPANDAY-299 > URL: https://issues.apache.org/jira/browse/NPANDAY-299 > Project: NPanday > Issue Type: Bug > Components: Visual Studio Add-in >Reporter: Brett Porter >Priority: Minor > Fix For: Backlog > > > see user story in issue #13600 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (NPANDAY-543) Resync References doesn´t update dependencies from remote repositories with LDAP verification
[
https://issues.apache.org/jira/browse/NPANDAY-543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brett Porter updated NPANDAY-543:
-
Fix Version/s: 1.5.0-incubating
Assignee: Brett Porter
I'll check this, I think it's been fixed already
> Resync References doesn´t update dependencies from remote repositories with
> LDAP verification
> -
>
> Key: NPANDAY-543
> URL: https://issues.apache.org/jira/browse/NPANDAY-543
> Project: NPanday
> Issue Type: Bug
> Components: Visual Studio Add-in
>Affects Versions: 1.4-incubating
> Environment: Archiva 1.3.5.,
> NPanday 1.4-incubating,
> Visual studion 2010
> Maven 3.0.3
>Reporter: Jiri Pergl
>Assignee: Brett Porter
>Priority: Blocker
> Fix For: 1.5.0-incubating
>
>
> Steps:
> 1. Add references using "Add Maven Artifact" from the menu(VS) or direct in
> the project pom.
> 2. Update the configuration in the settings.xml.
>- I insert to the configuration in the setting.xml this snippet:
> ...
>
> npanday.repo.0
> {LDAP user name}
> {encrypted password}
>
> ...
> 3. Refresh references using "Resync References" from the menu(VS).
> After action I see message "Download Failed The remote server returned an
> error: (401) Unauthorized."
> I found out that Archiva is contacted without LDAP parameters in the
> communication between Archiva and local machine. If I try the goal "deploy"
> on the simple project, the communication is ok.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (NPANDAY-544) Missing(?) NUnit pluggin, general complexity of first use.
[
https://issues.apache.org/jira/browse/NPANDAY-544?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brett Porter resolved NPANDAY-544.
--
Resolution: Not A Problem
Hi, Sorry for missing this. It's probably best worked through on the users list
in future.
The repository containing NUnit is back up, and we're working to remove the
openrdf dependency and making it easier to select other versions of libraries.
> Missing(?) NUnit pluggin, general complexity of first use.
> --
>
> Key: NPANDAY-544
> URL: https://issues.apache.org/jira/browse/NPANDAY-544
> Project: NPanday
> Issue Type: Improvement
> Components: Development Setup, Maven Plugins, Repository
>Affects Versions: 1.4-incubating
> Environment: Apache Maven 2.2.1 (r801777; 2009-08-06 15:16:01-0400)
> Java version: 1.6.0_31
> Java home: C:\Program Files\Java\jdk1.6.0_31\jre
> Default locale: en_AU, platform encoding: Cp1252
> OS name: "windows 7" version: "6.1" arch: "amd64" Family: "windows"
> Visual Studio 10, 9, 8 installed (10 is active using vcvars)
> JDK 1.4, 1.5, 1.6 installed
>Reporter: Greg Domjan
> Labels: documentation, newbie
>
> Feel free to "take with a grain of salt", fairly new to all this.
> Installing NPanday from Maven central, it was not obvious (to me) that this
> relied on http://repository.aduna-software.org/maven2/ when it raised issue
> with openrdf pluggin. Will these dependencies also be on Maven central in
> future? this was kind of painful.
> Link "NPanday Release and Dependencies Repository Group" on
> http://incubator.apache.org/npanday/docs/1.4.0-incubating/guide/installation/index.html
> is broken.
> Having sorted out proxy for aduna and having it seems (almost) all the
> plugins, the compile step is still failing on NUnit pluggin
> - why is 'compile' using NUnit? Shouldn't that be in compile-test unless
> specified for the release artifact?
> - where do you get the plugin? or is there some issue where you have to load
> the installed NUnit file to the local repo?
> [INFO] Scanning for projects...
> [INFO]
>
> [INFO] Building Unnamed - com.groupid:MyApp:library:1.0-SNAPSHOT
> [INFO]task-segment: [compile]
> [INFO]
>
> [INFO] [compile:initialize {execution: default-initialize}]
> SLF4J: Class path contains multiple SLF4J bindings.
> SLF4J: Found binding in
> [jar:file:/C:/path/.m2/repository/org/sonatype/gossip/gossip/1.0/gossip-1.0.jar!/org/slf4j/impl/StaticLoggerBinder.class]
> SLF4J: Found binding in
> [jar:file:/C:/path/.m2/repository/org/slf4j/slf4j-jdk14/1.5.11/slf4j-jdk14-1.5.11.jar!/org/slf4j/impl/StaticLoggerBinder.class]
> SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an
> explanation.
> 27/02/2012 6:25:14 PM npanday.PathUtil getDotNetArtifact
> WARNING:
> NPANDAY-1005-0001: Error copying dependency
> NUnit:NUnit.Framework:library:2.2.8.0:compile File
> C:\path\.m2\repository\NUnit\NUnit.Framework\2.2.8.0\NUnit.Framework-2.2.8.0.dll
> does not exist
> Downloading:
> http://nexus:8081/nexus/content/groups/public/NUnit/NUnit.Framework/2.2.8.0/NUnit.Framework-2.2.8.0.dll
> [INFO] Unable to find resource 'NUnit:NUnit.Framework:library:2.2.8.0' in
> repository sm.nexus
> (http://nexus.esecurity.net:8081/nexus/content/groups/public)
> Downloading:
> http://nexus8081/nexus/content/groups/public/NUnit/NUnit.Framework/2.2.8.0/NUnit.Framework-2.2.8.0.dll
> [INFO] Unable to find resource 'NUnit:NUnit.Framework:library:2.2.8.0' in
> repository central (http://repo1.maven.org/maven2)
> 27/02/2012 6:25:15 PM npanday.dao.impl.ProjectDaoImpl
> storeProjectAndResolveDependencies
> WARNING: NPANDAY-181-121: Problem in resolving assembly:
> NUnit:NUnit.Framework:library:2.2.8.0:compile, Message = 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=NUnit -DartifactId=NUnit.Framework
> -Dversion=2.2.8.0 -Dpackaging=library -Dfile=/path/to/file
> Alternatively, if you host your own repository you can deploy the file there:
> mvn deploy:deploy-file -DgroupId=NUnit -DartifactId=NUnit.Framework
> -Dversion=2.2.8.0 -Dpackaging=library -Dfile=/path/to/file -Durl=[url]
> -DrepositoryId=[id]
> ... [snip]
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (NPANDAY-547) Add support for unmanaged C++ projects
[ https://issues.apache.org/jira/browse/NPANDAY-547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13266347#comment-13266347 ] Brett Porter commented on NPANDAY-547: -- This isn't in our current plans, but happy to discuss it with you. Have you already tried the general native maven plugins to see if they address your needs? > Add support for unmanaged C++ projects > -- > > Key: NPANDAY-547 > URL: https://issues.apache.org/jira/browse/NPANDAY-547 > Project: NPanday > Issue Type: Improvement > Components: Development Setup, Project Importer, Visual Studio Add-in >Reporter: Theodore Sheckler > Original Estimate: 0h > Remaining Estimate: 0h > > NPanday project importer does not recognize unmanaged C++ projects > (.vcproj/.vcxproj), nor does there exist native plugin to compile such > projects. > (Disclaimer: I am new to NPanday, so I am not sure if there are plans to > include unmanaged code as a feature of the software). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (NPANDAY-546) Azure plugin doesn't add the correct entry point to web roles
[
https://issues.apache.org/jira/browse/NPANDAY-546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brett Porter resolved NPANDAY-546.
--
Resolution: Fixed
> Azure plugin doesn't add the correct entry point to web roles
> -
>
> Key: NPANDAY-546
> URL: https://issues.apache.org/jira/browse/NPANDAY-546
> Project: NPanday
> Issue Type: Bug
> Components: Maven Plugins
>Affects Versions: 1.5.0-incubating
>Reporter: Brett Porter
>Assignee: Brett Porter
> Fix For: 1.5.0-incubating
>
>
> When calling cspack, it looks for the entrypoint in {{./artifactId.dll}} of
> the role package, but that is only relevant for a worker role. For a web
> role, it is in {{./bin/artifactId.dll}}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (NPANDAY-203) MSBuild should be called from Java / remove .NET-MSBuild-Plugin
[ https://issues.apache.org/jira/browse/NPANDAY-203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13262657#comment-13262657 ] Brett Porter commented on NPANDAY-203: -- hasn't really been partially done - there is some code in the javabinding and some in the C#. Agree, should use the executable stuff (and I think the msbuild tool you put together) in a new plugin. > MSBuild should be called from Java / remove .NET-MSBuild-Plugin > --- > > Key: NPANDAY-203 > URL: https://issues.apache.org/jira/browse/NPANDAY-203 > Project: NPanday > Issue Type: Bug >Reporter: Brett Porter >Assignee: Lars Corneliussen >Priority: Minor > Fix For: 1.5.0-incubating > > > Currently this is doing nothing more than reading the parameters and forking > msbuild - this can be done in a Java mojo, removing one of the Process.Start > calls. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (NPANDAY-469) Error copying dependency if local repository is not default
[
https://issues.apache.org/jira/browse/NPANDAY-469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brett Porter updated NPANDAY-469:
-
Fix Version/s: 1.4.1-incubating
> Error copying dependency if local repository is not default
> ---
>
> Key: NPANDAY-469
> URL: https://issues.apache.org/jira/browse/NPANDAY-469
> Project: NPanday
> Issue Type: Bug
>Affects Versions: 1.4-incubating
>Reporter: Marcus Burton
> Fix For: 1.4.1-incubating
>
>
> When trying to build a WPF library I get "NPANDAY-190-005: An error occurred
> while retrieving projects." during mvn install.
> It looks like a hard coded reference to the local repo in
> RepositoryConverterForArtifactMojo.java (Line 72)
> localRepository = new File( System.getProperty( "user.home" ),
> ".m2/repository" );
> https://svn.apache.org/repos/asf/incubator/npanday/trunk/plugins/maven-repository-plugin/src/main/java/npanday/plugin/repository/RepositoryConverterForArtifactMojo.java
> Partial debug log
> [DEBUG] Configuring mojo
> 'org.apache.npanday.plugins:maven-repository-plugin:1.4.0-incubating:convert-artifact'
> -->
> [DEBUG] (f) localRepository = C:\Working\dev\m2_repo
> [DEBUG] (f) project = MavenProject: asdf:1.0-SNAPSHOT @
> C:\Working\dev\asdf\pom.xml
> [DEBUG] -- end configuration --
> [INFO] [repository:convert-artifact {execution: default-convert-artifact}]
> 06-Sep-2011 10:18:16 info.aduna.lang.service.ServiceRegistry
> INFO: Registered service class
> org.openrdf.query.parser.serql.SeRQLParserFactory
> 06-Sep-2011 10:18:16 info.aduna.lang.service.ServiceRegistry
> INFO: Registered service class
> org.openrdf.query.parser.sparql.SPARQLParserFactory
> 06-Sep-2011 10:18:16 npanday.PathUtil getDotNetArtifact
> WARNING:
> NPANDAY-1005-0001: Error copying dependency
> asdf:dotnet-library:1.0-SNAPSHOT:compile File
> H:\...\.m2\repository\asdf\1.0-SNAPSHOT\asdf-SNAPSHOT.dll does not exist
> [INFO]
>
> [ERROR] BUILD ERROR
> [INFO]
>
> [INFO] NPANDAY-190-005: An error occurred while retrieving projects.
> [INFO]
>
> [DEBUG] Trace
> org.apache.maven.lifecycle.LifecycleExecutionException: NPANDAY-190-005: An
> error occurred while retrieving projects.
> 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:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> 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-190-005:
> An error occurred while retrieving projects.
> at
> npanday.plugin.repository.RepositoryConverterForArtifactMojo.execute(RepositoryConverterForArtifactMojo.java:100)
> at
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694)
> ... 17 more
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[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 ] Brett Porter updated NPANDAY-284: - Fix Version/s: (was: 2.0) 1.4.1-incubating > 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: 1.4.1-incubating > > > 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. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (NPANDAY-468) npanday does not respect scope
[ https://issues.apache.org/jira/browse/NPANDAY-468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13095896#comment-13095896 ] Brett Porter commented on NPANDAY-468: -- the build tasks issue has already been fixed in trunk > npanday does not respect scope > -- > > Key: NPANDAY-468 > URL: https://issues.apache.org/jira/browse/NPANDAY-468 > Project: NPanday > Issue Type: Question > Components: Maven Plugins >Affects Versions: 1.4-incubating > Environment: windows 7, maven 2.2.1 >Reporter: sergio rupena > > When you add a dependency with scope 'runtime', npanday will pass that > dependency to the compiler. > Example: > > Foo > MyAssembly.dll > 1.0-SNAPSHOT > dotnet-library > runtime > > This will trigger the following command option for the compiler: > /reference:D:\Temp\project\target\MyAssembly.dll > The scope "runtime" means that this assembly is not needed at compile time so > I would not expect npanday to add a reference to it. > Also I wonder why npanday uses by default references like > Microsoft.Build.Tasks.v3.5.dll to compile my assemblies. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (NPANDAY-465) need more options for ASPX packaging plugin
[
https://issues.apache.org/jira/browse/NPANDAY-465?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brett Porter updated NPANDAY-465:
-
Priority: Minor (was: Major)
Fix Version/s: Backlog
> need more options for ASPX packaging plugin
> ---
>
> Key: NPANDAY-465
> URL: https://issues.apache.org/jira/browse/NPANDAY-465
> Project: NPanday
> Issue Type: Task
> Components: Maven Plugins
>Affects Versions: 1.4.1-incubating
>Reporter: Brett Porter
>Priority: Minor
> Fix For: Backlog
>
>
> currently, if you create a project that uses the aspx plugin, you are forced
> to precompile the web application, and to adhere to the output of the
> aspnet_compiler application. This can do things like compile some resources
> but leave others uncompiled so that they can be locally edited - where you
> may want them all precompiled (omit {{-u}}), or none (don't precompile, or
> copy anyway).
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
