Hi All,
We are planning to release NPanday-1.3.1-incubating within this month. The issues included for this release are as follows: * NPANDAY-69 - NPanday needs to be more synchronized and automated * NPANDAY-83 - do not hide originating exceptions * NPANDAY-186 - Remove the uac and pab directories * NPANDAY-239 - VS Add-In messes up settings.xml * NPANDAY-277 - NPanday.Plugin.Runner and Loader not installed to UAC * NPANDAY-288 - Support for VS 2010 and .NET Framework 4.0 * NPANDAY-290 - Improve console output for integration tests * NPANDAY-314 - Adding a Maven artifact from VS plugin generates NPANDAY-180-017 error * NPANDAY-316 - Trying to import WPF-project on a 64-bit system (VS 2008) throws FileLoadException * NPANDAY-325 - Additional parameters for wix-maven-plugin * NPANDAY-326 - misc. improvements * NPANDAY-328 - Support for VS2010 WPF Project * NPANDAY-329 - Support for VS2010 WCF Project * NPANDAY-330 - Support for VS2010 MVC Project * NPANDAY-333 - Dependency of type 'gac' is not resolved correctly * NPANDAY-334 - Upgrade Integration Tests in relation with the UAC & PAB removal enhancements * NPANDAY-335 - NPanday on Visual Studio only starts on Debug Mode * NPANDAY-336 - Add Integration Tests for VS 2010 supported projects (WPF, WCF and MVC) * NPANDAY-337 - NPanday unusable under linux * NPANDAY-339 - Npanday.Plugin size 0 in repo * NPANDAY-341 - command execution fails if paths with space * NPANDAY-342 - deploy sources artifacts to npanday asset repo * NPANDAY-343 - Can't successfully build projects (VS 2005 and VS 2008) - Builder Error due to Access is denied * NPANDAY-347 - compile fails on unix if sources in subfolder * NPANDAY-348 - Import Error when importing WPF projects in VS 2010 on a 64-bit system * NPANDAY-349 - NPanday not building resource files correctly * NPANDAY-351 - NPanday does not respect the configured repository in the pom * NPANDAY-354 - Addin 'resync references' feature fails if using remote repositories but there is no "mirrors" section in Settings.xml file * NPANDAY-355 - Addin 'resync references' feature hard-wires " http://repo1.maven.org/maven2" as remote repository causing network security violations * NPANDAY-356 - Addin 'resync references' feature fails to download the latest SNAPSHOT from remote repo if older snapshot file already exists locally * NPANDAY-357 - Add 'deploy' option to 'Current NPanday Project' menu options * NPANDAY-360 - Local Repository not displaying correct artifacts from the local repository * NPANDAY-361 - Configurable .M2 Folder and npanday-settings.xml lookup * NPANDAY-362 - npanday-settings.xml in local repository is not overwritten on a new install of npanday. * NPANDAY-363 - Service Reference is not deleted from pom when removing it in the project * NPANDAY-367 - Building a project that contains a maven artifact from a remote repository generates a new .m2groupId folder * NPANDAY-373 - Custom Lifecycle Plugin does not bind the produced artifact * NPANDAY-376 - Intermittent error caused by updating npanday-settings.xml * NPANDAY-378 - malformed npanday-settings.xml should fail the build * NPANDAY-379 - Exception not caught properly when default path for npanday-settings.xml is used * NPANDAY-380 - IndexOutOfRangeException in SettingsGeneratorMojo.GetVendorsFromMicrosoft * NPANDAY-381 - Missing SVN EOL properties There are 4 opened/unresolved issues and they are as follows: * NPANDAY-377 - released registry-config.xml contains a hardcoded path * NPANDAY-383 - update groupID to org.apache.npanday * NPANDAY-386 - Support Maven 3 and enable bootstrapping NPanday using itself (within the same reactor) * NPANDAY-123 - PATH should not have to be set for both Visual Studio Addin or mvn command-line to function If you have anything to add, please feel free to reply on this thread. We also need to make sure that the LICENSES are updated. Thanks! -- liit