This is an automated email from the ASF dual-hosted git repository. Cole-Greer pushed a commit to branch remove-mono in repository https://gitbox.apache.org/repos/asf/tinkerpop.git
commit 308adfd2c82d3dd701137bb0f71ba2699e4428b7 Author: Cole Greer <[email protected]> AuthorDate: Wed Jul 22 12:12:49 2026 -0700 simplify docs --- docs/src/dev/developer/development-environment.asciidoc | 12 +++--------- gremlin-dotnet/src/pom.xml | 15 ++------------- 2 files changed, 5 insertions(+), 22 deletions(-) diff --git a/docs/src/dev/developer/development-environment.asciidoc b/docs/src/dev/developer/development-environment.asciidoc index 6d61443761..0735c90063 100644 --- a/docs/src/dev/developer/development-environment.asciidoc +++ b/docs/src/dev/developer/development-environment.asciidoc @@ -250,8 +250,7 @@ and `test` directories of the `gremlin-dotnet` module which will signify to Mave The `.glv` file need not have any contents and is ignored by Git. A standard `mvn clean install` will then build `gremlin-dotnet` in full. -Packing the Gremlin.Net.Template project uses `dotnet pack` directly — no additional tooling beyond the .NET SDK is -required. To pack the template, the `nuget` property has to be set: +To pack the Gremlin.Net.Template, the `nuget` property has to be set: [source,text] mvn clean install -Dnuget @@ -375,13 +374,10 @@ link:https://pypi.org/manage/account/token/[account settings] and then the usern and the password to the token value. Please see link:https://pypi.org/help/#apitoken[PyPI documentation] for more details. -For .NET releases, the .NET SDK (already required for building) provides all necessary tooling — no additional -Mono or `nuget.exe` installation is needed. To get an environment ready to deploy to NuGet, it is necessary to have a -NuGet API key. First, create an account with +For .NET releases, it is necessary to have a NuGet API key. First, create an account with link:https://www.nuget.org[nuget] and request that a PMC member add your account to the Gremlin.Net and the Gremlin.Net.Template package in nuget so that you can deploy. Next, generate an API key for your account on the -nuget website. The old `mono nuget.exe setApiKey` approach stored the key encrypted (via Windows DPAPI) in -`NuGet.Config`, which the `dotnet` CLI cannot decrypt on Linux/macOS. Instead, supply the key with the `nuget.apiKey` +nuget website. During deployments, supply the key with the `nuget.apiKey` Maven property when running `mvn deploy`, which the build passes explicitly to `dotnet nuget push --api-key`: [source,text] @@ -389,8 +385,6 @@ Maven property when running `mvn deploy`, which the build passes explicitly to ` mvn deploy -pl :gremlin-dotnet-source -Dnuget -Dnuget.apiKey=[your-api-key] ---- -If `nuget.apiKey` is not supplied, the build will fail fast with a message explaining how to set it. - To deploy JavaScript / TypeScript artifacts on the link:https://www.npmjs.com[npm registry], the release manager must set the authentication information on the ~/.npmrc file. The easiest way to do that is to use the `npm adduser` command. This must be done only once, as the auth token doesn't have an expiration date and it's stored on your file diff --git a/gremlin-dotnet/src/pom.xml b/gremlin-dotnet/src/pom.xml index 76e52e2df5..6a9c080a5b 100644 --- a/gremlin-dotnet/src/pom.xml +++ b/gremlin-dotnet/src/pom.xml @@ -229,11 +229,6 @@ limitations under the License. </properties> <build> <plugins> - <!-- - not seeing much point to making this OS agnostic really. as far as it is known, no one who does - deployments will do so from a windows machine. the dotnet CLI handles packing and pushing - natively - no additional tooling required beyond the .NET SDK. - --> <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-antrun-plugin</artifactId> @@ -263,16 +258,10 @@ limitations under the License. <!-- the NuGet API key is passed explicitly via the "api-key" option, sourced from the "nuget.apiKey" Maven property, which the release manager must set - with "-Dnuget.apiKey=..." when running "mvn deploy -Dnuget". NuGet 7.6+ - (bundled with .NET SDK 10.0.300+) can read a NUGET_API_KEY environment - variable automatically instead, but this build currently targets .NET SDK - 8.0, whose bundled NuGet CLI predates that feature. The old - "nuget.exe setApiKey" config file approach is not viable here either: it - encrypts the key with Windows DPAPI, which the dotnet CLI cannot decrypt on - Linux/macOS release hosts. + with "-Dnuget.apiKey=..." when running "mvn deploy -Dnuget". --> <fail unless="nuget.apiKey"> -Deploying to NuGet requires an API key. Please supply one with "-Dnuget.apiKey=[your-api-key]" when running "mvn deploy -Dnuget". + Deploying to NuGet requires an API key. Please supply one with "-Dnuget.apiKey=[your-api-key]" when running "mvn deploy -Dnuget". </fail> <exec executable="dotnet" failonerror="true"> <arg line="nuget push Gremlin.Net/bin/Gremlin.Net.${project.version}.nupkg --source https://api.nuget.org/v3/index.json --api-key ${nuget.apiKey}"/>
