I’m having an issue deploying my Spring Boot JARs to the company’s internal libs-release-local repository. When I run the mvn deploy:deploy-file command with the appropriate arguments, it deploys successfully from my workstation: The above repositoryId is defined in my home directory’s settings.xml. When I run the same command in GitLab CI, I get the following: Both myself and our service
Tag: artifactory
Artifactory + Custom Gradle Plugin Programmatically (2022)
I’m trying to create a custom gradle plugin (100% java) which will automatically configure Artifactory, avoiding the need of the following DSL: I’m trying to re-create @agrosner own solution (from https://stackoverflow.com/a/25669431/1880280) but I’m missing “ArtifactoryAction”. I can’t find it anywhere. The nonworking version posted by @agrosner is the following code: Can anyone help with an updated 100% java version of
gradle publishing project-version-PLAIN.war file instead of project-version.war
When I run “gradle build”, it generates a build/libs/project-version.war file which is able to run by itself with “java -jar” command. But when I run “gradle artifactoryPublish”, it saves on the artifactory repository a “project-version-plain-war” file which does not have tomcat embedded. I am following this instruccions https://www.jfrog.com/confluence/display/JFROG/Gradle+Artifactory+Plugin The lines added to the gradle.build are something like this: help is
Artifactory publish with multi-module gradle
Hope all doing well. Today I was working on multi-module gradle project, and trying to publish one of it’s dependency to artifactory as well. my project structure are: build.gradle (main) build.gradle (api) and the task artifactoryPublish produces: Now the issue is that, the modules, like admin-api builds with the name admin-api-0.0.2-RC3-plain.jar, and the resolution of dependency fails in another project,