You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@groovy.apache.org by "Paul King (Jira)" <ji...@apache.org> on 2022/06/29 00:49:00 UTC
[jira] [Commented] (GROOVY-10669) How to publish groovy distributions to my own repository?
|  |
[Paul King](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=paulk)
**commented** on [
GROOVY-10669](https://issues.apache.org/jira/browse/GROOVY-10669)
---|---
|
---
| [Re: How to publish groovy distributions to my own
repository?](https://issues.apache.org/jira/browse/GROOVY-10669)
---
|
That version of Groovy used the (legacy) maven plugin:
<https://docs.gradle.org/6.7.1/userguide/maven_plugin.html>
That doco link describes options for further configuration. We only
used it via publishing to an artifactory instance and the build is set
up for that case with various parameters. Typically you would do:
$ ./gradlew install dist artifactoryPublish
-PartifactoryContext=[https://your.artifactory.instance/potential_subdir/
-PartifactoryRepoKey=libs-release-local] -PartifactoryUser=someUser
-PartifactoryPassword=*****
Alternatively, the "install" task publishes to the local maven
repository and "installGroovy" publishes to a target/install directory
* you could publish the jar files in the lib folder manually.
Also, from your description, it wasn't clear if you were wanting to
fix the Groovy within Gradle. You may not be, but if you are, that
depends on how you are getting your gradle. If you are downloading a
zip, it will have groovy embedded in it and that would need to be
fixed separately if the issue you are having is when running gradle
itself or if you are using the "localGroovy()" dependency.
---
| | [ 
](https://issues.apache.org/jira/browse/GROOVY-10669#add-comment "Add
Comment") | [Add
Comment](https://issues.apache.org/jira/browse/GROOVY-10669#add-comment "Add
Comment")
---|---
| This message was sent by Atlassian Jira (v8.20.10#820010-sha1:ace47f9) | |
---