kwin commented on code in PR #620:
URL: https://github.com/apache/maven-parent/pull/620#discussion_r4370607413


##########
pom.xml:
##########
@@ -1642,5 +1655,30 @@ under the License.</licenseText>
         </dependencies>
       </dependencyManagement>
     </profile>
+    <profile>
+      <!-- prepare a njord bundle archive that contains output for Maven 
Central,
+           and upload to ATR for ATR to stage content during vote and publish 
to Maven Central if vote successful -->
+      <id>push-to-atr-njord</id>
+      <distributionManagement>
+        <repository>
+          <id>njord</id>
+          <url>njord:release</url>
+        </repository>
+        <snapshotRepository>
+          <id>njord</id>
+          <url>njord:snapshot</url>
+        </snapshotRepository>
+      </distributionManagement>
+      <!-- after running: mvn -Papache-release,push-to-atr-njord clean deploy
+        run: mvn njord:list
+        to get store id (maven-parent-00001 on first run)
+        then: mvn njord:export -Dnjord.path=target 
-Dnjord.store=maven-parent-00001
+        to get the zip as target/maven-parent-00001.ntb
+        this is the file to upload to ATR later...
+       -->
+      <!-- we probably need to write a njord publisher that creates that file 
and uses atr-maven-plugin to push to ATR

Review Comment:
   I think the most interesting aspect is how to tag ATR uploads targeting 3rd 
party repo uploads vs svn dist relevant (potentially even both).



##########
pom.xml:
##########
@@ -1642,5 +1655,30 @@ under the License.</licenseText>
         </dependencies>
       </dependencyManagement>
     </profile>
+    <profile>
+      <!-- prepare a njord bundle archive that contains output for Maven 
Central,
+           and upload to ATR for ATR to stage content during vote and publish 
to Maven Central if vote successful -->
+      <id>push-to-atr-njord</id>

Review Comment:
   for me this id is confusing as long as it merely only creates a njord bundle.



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to