Release Notes - NMaven (Retired) - Version 0.14 (Unreleased) - HTML format

Bug

  • [NMAVEN-11] - Can't generate resources for an executable that contains an exe.config file
  • [NMAVEN-28] - -SNAPSHOT suffixed version in generated AssemblyInfo for library snapshot version
  • [NMAVEN-38] - "NUnit" group ID hardwired into TesterMojo.java(142) - doesn't match site documentation.
  • [NMAVEN-56] - Cannot run NUnit tests independen
  • [NMAVEN-59] - IDE Output Pane Only Displays the Maven Java Output
  • [NMAVEN-63] - Signing of assemblies not supported for VB and Java on Framework Version 1.1
  • [NMAVEN-76] - NMaven attempts to download direct GAC Dependencies
  • [NMAVEN-79] - With <vendor>MICROSOFT</vendor> still failing with "NMAVEN-9011-007: Mono installation could not be found."
  • [NMAVEN-85] - Install plugin fails when parent project is not in parent directory
  • [NMAVEN-94] - Archetypes packaging changed to 'jar'
  • [NMAVEN-95] - artifacts in the GAC should be deployed to the repository with their public token key id
  • [NMAVEN-96] - repository builder fails to create missing directories in the local repository
  • [NMAVEN-97] - remove the alternative deploy plugin and change the lifecycle to use the standard one
  • [NMAVEN-103] - CSharpClassCompiler will invoke csc even if there are no files in the source path; this causes a build failure
  • [NMAVEN-111] - the visual studio installer plugin doesn't work on an empty local repository
  • [NMAVEN-112] - Unable to generate solution file from test project
  • [NMAVEN-113] - Remove dependencies using VS NMaven Plugin
  • [NMAVEN-115] - Using the systemPath element in a dependecy doesn't work
  • [NMAVEN-117] - The project generated by the NMaven netexecutable archetype defaults to version 0.14-incubating-SNAPSHOT when it should be 1.0-SNAPSHOT
  • [NMAVEN-118] - Errors from .NET plugins are not recognized
  • [NMAVEN-124] - NMaven crashes when generating solution files
  • [NMAVEN-125] - NUnit dependency should be in test scope
  • [NMAVEN-126] - Unable to retrieve and use timestamped snapshots of plugins
  • [NMAVEN-129] - Deploy plugin documentation doesn't match behavior: -Dversion vs. -DartifactVersion
  • [NMAVEN-130] - NPE when deploying to remote repo
  • [NMAVEN-132] - VS Addin 'Configure Maven Repository' breaks command line builds
  • [NMAVEN-133] - VS Addin 'Configure Maven Repository' does not work if nmaven.id is not in the first profile
  • [NMAVEN-134] - VS Addin 'Configure Maven Repository' does not remember checkbox values
  • [NMAVEN-135] - VS Addin 'Add Maven Artifact' does not respect mirrors in settings.xml
  • [NMAVEN-137] - Reference listing in VS remains after removing a NMaven artifact
  • [NMAVEN-138] - Code Signature not viewable from within Visual Studio
  • [NMAVEN-143] - NMaven-generated poms have unnecessary version and groupId elements
  • [NMAVEN-144] - NMaven is unable to build project with groupId and version inherited from parent
  • [NMAVEN-145] - NMaven.Plugins:NMaven.Plugin.Solution.JavaBinding:Solution got errors on multi-module project or pom
  • [NMAVEN-149] - Project Importer adds system-scoped System.* dependencies to poms
  • [NMAVEN-150] - Add back the dot net dependencies for VS2005 profile in VSInstsller plugin
  • [NMAVEN-153] - Intermittent error when starting the Visual Studio Add-in
  • [NMAVEN-154] - Unable to build a project that uses a parent pom
  • [NMAVEN-155] - NMaven is unable to build VB project with Visual Studio project structure
  • [NMAVEN-157] - Can't add a dependency w/Add NMaven Artifact
  • [NMAVEN-160] - VS will crash when adding a NMaven Artifact that was already added as part of the Import Project
  • [NMAVEN-161] - Tests do not execute with dll built with NMaven
  • [NMAVEN-162] - A dependency can be added to the pom multiple times through Add NMaven Artifact.
  • [NMAVEN-163] - Support for Visual Studio nested (project-within-project) structure
  • [NMAVEN-164] - For VB projects; deleting a reference with DEL key does not remove reference from the pom
  • [NMAVEN-165] - Support for Windows Application type projects
  • [NMAVEN-169] - Dependencies added through the Import Project have their <name> converted to lower case
  • [NMAVEN-171] - NMaven should support Imported Namespaces for VB projects
  • [NMAVEN-173] - Project Import error with Assembly information is missing from project.
  • [NMAVEN-175] - Project Importer does not add dependency elements for intra-project references
  • [NMAVEN-176] - Installing vsinstaller addin with "My Documents" targeted to another directory doesn't work
  • [NMAVEN-177] - When performing an NMaven build, user can still build the same project/solution using the Build menu option.
  • [NMAVEN-178] - Build events scripts does not execute when performing an NMaven build
  • [NMAVEN-180] - Visual Studio crashes when you add maven a artifact and the project you're about to add into has a reference to a project that has the same name as the artifact to be added.
  • [NMAVEN-181] - Project Importer failing to produce pom
  • [NMAVEN-182] - NMaven Project-Importer support for adding <define> tag for compile plugin configuration, for compile switch /define support
  • [NMAVEN-183] - Missing method implementation in Connect.cs is causing compilation error
  • [NMAVEN-185] - Unable to start NMaven Addin
  • [NMAVEN-188] - NMaven menu options are available even after stopping NMaven Build System from Tools -> Addin Manager
  • [NMAVEN-191] - If source project is in VB.net then mvn install does not support c# test project.
  • [NMAVEN-194] - Unable to build (compile) without installing
  • [NMAVEN-196] - NMaven should ignore "<sourceDirectory>\bin\Debug" directory during process-sources phase
  • [NMAVEN-197] - Building NMaven Project Using Visual Studio sometimes does not output some remaining logs
  • [NMAVEN-202] - NMaven downloads .pom and .dll files every build execution
  • [NMAVEN-204] - simple-archetype project after project import will not build successfully in VS
  • [NMAVEN-207] - Project Importer utility produces the project POM file in a different folder than the folder where project file or solution resides
  • [NMAVEN-210] - Fix maven-resgen-plugin to read the resource files under resources folder
  • [NMAVEN-211] - WSDL generation fails if output dir does not exist
  • [NMAVEN-212] - TestSourceProcessorMojo must must not copy the non-source code files to "target\build-test-sources" folder
  • [NMAVEN-218] - Adding dependencies with the same artifact ID but with different version is added in pom
  • [NMAVEN-219] - Artifacts are duplicated in "Add Maven Artifact" form.
  • [NMAVEN-221] - Consecutively installing web applications will give an error
  • [NMAVEN-222] - Build Error installing web applications with vb project after project importing

Improvement

  • [NMAVEN-71] - Replace various hard-coded paths with environment-aware versions
  • [NMAVEN-86] - Code sketch for NMaven.Model.Settings support, as well as a non-trivial application thereof in the visual studio addin connect method.
  • [NMAVEN-89] - Update documentation for Visual Studio
  • [NMAVEN-98] - Dotnet simple archetype does not include unit tests
  • [NMAVEN-106] - NMaven Service Embedder vs Simple Call of mvn.bat using dotnet System.Diagnostics.Process
  • [NMAVEN-114] - Jetty is pulled out by plugins, even if it isn't needed
  • [NMAVEN-123] - Remove maven 2.1 snapshot dependencies, embedder dependencies, war dependency in favor for System.Diagnostics.Process when running maven commands in VS
  • [NMAVEN-127] - Simple C# Archetype is missing a name
  • [NMAVEN-128] - Document packaging and built-in lifecycle bindings
  • [NMAVEN-140] - Make add remote artifact feature of Nmaven more robust, improve parsing of remote artifacts
  • [NMAVEN-152] - VS Addin should allow configuration of the test source directory to exclude from packaging
  • [NMAVEN-158] - Support signed assemblies via NMaven for versioned releases
  • [NMAVEN-159] - Support for signed .NET assemblies in the release process
  • [NMAVEN-167] - Make error messages more descriptive
  • [NMAVEN-172] - Project Importer should append Parent rather than -parent to artifactId of parent pom
  • [NMAVEN-174] - Need the ability to specify the test module during project Import
  • [NMAVEN-179] - Reasons for failed unit tests not displayed in Output window, it just says Build Error
  • [NMAVEN-189] - NMaven Execution Output should be cleared when closing the project solution.
  • [NMAVEN-190] - Improve NUnit test result message in console
  • [NMAVEN-193] - Recognise NUnit artifact conventions used in trunk
  • [NMAVEN-203] - Building a project without pom.xml file must only prompt once
  • [NMAVEN-205] - Auto inject log into CommandExecutor
  • [NMAVEN-209] - Alter Pom Generator to use GAC instead of systemPath when referencing .Net framework libraries
  • [NMAVEN-217] - Improve messages when VS Addin starts and stops
  • [NMAVEN-220] - Make Artifacts selectable by double-click in Add Maven Artifact Form

New Feature

  • [NMAVEN-16] - Add NUnit Support to Visual Studio
  • [NMAVEN-18] - Archetype Plugins
  • [NMAVEN-21] - Support for Ruby .NET Compiler
  • [NMAVEN-39] - Browse Maven Repository and Add/Delete Dependencies through the IDE
  • [NMAVEN-41] - Configuration of Remote Services through the IDE
  • [NMAVEN-82] - Support for IoC Container
  • [NMAVEN-99] - Need a VB .NET quickstart archetype
  • [NMAVEN-110] - Ability to generate .vbproj files
  • [NMAVEN-116] - Add feature for Solution.JavaBinding plugin to pickup resource file in the source directory
  • [NMAVEN-119] - Ability to generate pom.xml file from an existing Visual Studio solution file
  • [NMAVEN-121] - Have a configurable root namespace for VB assembly
  • [NMAVEN-122] - JavaBinding (solution generation) plugin needs a Clean goal
  • [NMAVEN-131] - Deploy plugin should generate a minimal pom if one is not supplied
  • [NMAVEN-136] - References added using Visual Studio controls (Add Reference) do not update the pom
  • [NMAVEN-170] - Ability to configure the location of settings.xml file
  • [NMAVEN-184] - Support for web app projects
  • [NMAVEN-195] - Ability to generate a project from an archetype within Visual Studio
  • [NMAVEN-199] - Create an aspx-compiler-mojo for precompilation of ASP .NET pages
  • [NMAVEN-200] - Create a ASP .NET packaging
  • [NMAVEN-201] - Visual Studio Addin needs to recognize web and webservices projects during import
  • [NMAVEN-206] - Add missing compiler options for CSC and VBC in nmaven-compile-plugin
  • [NMAVEN-208] - Add paramater for Pom Generator to specify .Net framework version used
  • [NMAVEN-223] - Support for File protocol in "Configure Maven Repository".

Edit/Copy Release Notes

The text area below allows the project release notes to be edited and copied to another document.