org.eobjects.build:dotnet-maven-parent

Sonatype helps open source projects to set up Maven repositories on https://oss.sonatype.org/

License	The Apache Software License, Version 2.0
Categories	Maven Build Tools Net
GroupId	org.eobjects.build
ArtifactId	dotnet-maven-parent
Last Version	0.24
Release Date	Apr 8, 2019
Type	pom
Description	Sonatype helps open source projects to set up Maven repositories on https://oss.sonatype.org/
Source Code Management	https://github.com/kaspersorensen/dotnet-maven-plugin

Download dotnet-maven-parent

Filename	Size
dotnet-maven-parent-0.24.pom	2 KB

How to add to project

Apache Maven

<!-- https://jarcasting.com/artifacts/org.eobjects.build/dotnet-maven-parent/ -->
<dependency>
    <groupId>org.eobjects.build</groupId>
    <artifactId>dotnet-maven-parent</artifactId>
    <version>0.24</version>
    <type>pom</type>
</dependency>

Gradle Groovy

// https://jarcasting.com/artifacts/org.eobjects.build/dotnet-maven-parent/
implementation 'org.eobjects.build:dotnet-maven-parent:0.24'

Gradle Kotlin

// https://jarcasting.com/artifacts/org.eobjects.build/dotnet-maven-parent/
implementation ("org.eobjects.build:dotnet-maven-parent:0.24")

Apache Buildr

'org.eobjects.build:dotnet-maven-parent:pom:0.24'

Apache Ivy

<dependency org="org.eobjects.build" name="dotnet-maven-parent" rev="0.24">
  <artifact name="dotnet-maven-parent" type="pom" />
</dependency>

Groovy Grape

@Grapes(
@Grab(group='org.eobjects.build', module='dotnet-maven-parent', version='0.24')
)

Scala SBT

libraryDependencies += "org.eobjects.build" % "dotnet-maven-parent" % "0.24"

Leiningen

[org.eobjects.build/dotnet-maven-parent "0.24"]

Dependencies

There are no dependencies for this project. It is a standalone project that does not depend on any other jars.

Project Modules

• plugin

dotnet-maven-plugin

A Maven plugin for building dotnet projects based on .csproj or project.json files.

This plugin lets you use the power of Maven to drive .NET core builds.

Features

• Drives the invocation of dotnet and nuget command line tools for build, test, deploy of .NET core projects.
• Runs unittests via dotnet test on projects that have a defined Test Runner.
• Offers a mvn clean option which arguably is currently missing from the dotnet CLI tools.
• Propagates versioning scheme from Maven parent to the .csproj or project.json files of the modules.
• Supports two project layouts: A pom-per-dotnet-module or a single-pom-for-all-dotnet-modules approach. See example projects.
• The plugin has Maven extensions, allowing it to be idiomatically bound to standard Maven phases by declaring certain packging types:
• <packaging>dotnet</packaging> will bind relevant Maven phases for dotnet component and application projects, including dotnet pack, dotnet publish and dotnet nuget add.
  • If a <repository> element is defined in the projects configuration, dotnet nuget push is also bound to the mvn deploy phase.
• <packaging>dotnet-library</packaging> will bind relevant Maven phases for dotnet class libraries, i.e. excluding dotnet publish.
• <packaging>dotnet-test</packaging> will bind relevant Maven phases for dotnet test-only projects, including dotnet test.
• <packaging>dotnet-integration-test</packaging> will bind Maven phase integration-test to dotnet test and Maven phase to verify to the gathering/evaluation of those results, allowing for post-integration-test clean-up tasks to take place exiting on test failures.
• All above packaging types also have clean, restore, build bindings

Installing

The plugin leverages the dotnet (required) and nuget (optional) command line tools, which have to be installed prior to usage of the plugin.

The simples use-case it to simply define your project with the packaging type, dotnet and enabled it with a plugin in pom.xml like this:

<project>
  [...]
  <packaging>dotnet</packaging>

  [...]
  <build>
    <plugins>
      <plugin>
        <groupId>org.eobjects.build</groupId>
        <artifactId>dotnet-maven-plugin</artifactId>
        <version>0.24</version>
        <extensions>true</extensions>
      </plugin>
    </plugins>
  </build>
  [...]
</project>

Configuration

Should you want to, you can configure many aspects of the dotnet and nuget invocations. The following should provide a handy overview by example:

<plugin>
  <groupId>org.eobjects.build</groupId>
  <artifactId>dotnet-maven-plugin</artifactId>
  <version>0.23</version>
  <extensions>true</extensions>
  <configuration>
    <buildConfiguration>Release</buildConfiguration>
    <buildEnabled>true</buildEnabled>
    <cleanEnabled>true</cleanEnabled>
    <environment>
      <MY_ENVVAR_1>hello</MY_ENVVAR_1>
      <MY_ENVVAR_2>world</MY_ENVVAR_2>
    </environment>
    <integrationTestRunEnabled>true</integrationTestRunEnabled>
    <integrationTestVerifyEnabled>true</integrationTestVerifyEnabled>
    <nugetAddEnabled>true</nugetAddEnabled>
    <nugetAddSource>~/.nuget/Packages</nugetAddSource>
    <nugetPushEnabled>true</nugetPushEnabled>
    <packEnabled>true</packEnabled>
    <packOutput>bin</packOutput>
    <publishEnabled>true</publishEnabled>
    <publishOutput>bin/my-publish-output</publishOutput>
    <repository>https://path/to/repository</repository>
    <restoreEnabled>true</restoreEnabled>
    <testEnabled>true</testEnabled>
  </configuration>
</plugin>

Take a look at the Example projects for more inspiration.

Versions

Version
0.24 Apr 8, 2019
0.23 Feb 14, 2018
0.22 Dec 24, 2017
0.21 Feb 14, 2018
0.20 Aug 26, 2017
0.19 Jul 22, 2017
0.18 Jul 10, 2017
0.17 Jun 15, 2017
0.16 May 15, 2017
0.15 May 12, 2017
0.14 Apr 4, 2017
0.13 Mar 13, 2017
0.12 Feb 15, 2017
0.11 Dec 24, 2016
0.10 Nov 2, 2016
0.9 Oct 24, 2016
0.8 Oct 18, 2016
0.7 Oct 6, 2016
0.6 Oct 6, 2016
0.5 Oct 6, 2016
0.4 Oct 5, 2016
0.3 Sep 12, 2016