This is an automated email from the ASF dual-hosted git repository.

nightowl888 pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/lucenenet.git


The following commit(s) were added to refs/heads/master by this push:
     new c8b826db4 Lucene.Net.Analysis.OpenNLP/overview.md: Corrected errors 
(transitive instead of transient) in the docs (#994)
c8b826db4 is described below

commit c8b826db4b28ca70cc0ab859927a5b18ba1e1ad7
Author: Shad Storhaug <[email protected]>
AuthorDate: Thu Oct 24 08:00:48 2024 +0700

    Lucene.Net.Analysis.OpenNLP/overview.md: Corrected errors (transitive 
instead of transient) in the docs (#994)
---
 src/Lucene.Net.Analysis.OpenNLP/overview.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/Lucene.Net.Analysis.OpenNLP/overview.md 
b/src/Lucene.Net.Analysis.OpenNLP/overview.md
index 05aa4ca15..60706c773 100644
--- a/src/Lucene.Net.Analysis.OpenNLP/overview.md
+++ b/src/Lucene.Net.Analysis.OpenNLP/overview.md
@@ -42,7 +42,7 @@ Named Entity Recognition is also supported by OpenNLP, but 
there is no OpenNLPNE
 
 ## MavenReference Primer
 
-When a `<PackageReference>` is included for this NuGet package in your 
SDK-style MSBuild project, it will automatically include transient dependencies 
to [`opennlp-tools` on 
maven.org](https://search.maven.org/artifact/org.apache.opennlp/opennlp-tools/1.9.4/bundle).
 The transient dependency will automatically include a `<MavenReference>` in 
your MSBuild project.
+When a `<PackageReference>` is included for this NuGet package in your 
SDK-style MSBuild project, it will automatically include transitive 
dependencies to [`opennlp-tools` on 
maven.org](https://search.maven.org/artifact/org.apache.opennlp/opennlp-tools/1.9.4/bundle).
 The transitive dependency will automatically include a `<MavenReference>` in 
your MSBuild project.
 
 The `<MavenReference>` item group operates similar to a dependency in Maven. 
All transitive dependencies are collected and resolved, and then the final 
output is produced. However, unlike `PackageReference`s, `MavenReference`s are 
collected by the final output project, and reassessed. That is, each dependent 
Project within your .NET SDK-style solution contributes its `MavenReference`s 
to project(s) which include it, and each project makes its own dependency 
graph. Projects do not contrib [...]
 

Reply via email to