Where to keep maven publish related sections of Gradle build file?
I do publish an open source library to Maven Central. In order to do that the gradle.build file contains variable references to a gradle.properties file which contains secret information like usernames and passwords.
Of course the build.gradle needs to be published to the public git repository, the gradle.properties should not be published, due to containing all the personal information but without the properties file the build.gradle is not valid.
How are open source projects handling those sensitive data?
gradle maven-publish
asked Nov 27 '18 at 7:21
HannesHannes
1,62151732
add a comment |
I do publish an open source library to Maven Central. In order to do that the gradle.build file contains variable references to a gradle.properties file which contains secret information like usernames and passwords.
Of course the build.gradle needs to be published to the public git repository, the gradle.properties should not be published, due to containing all the personal information but without the properties file the build.gradle is not valid.
How are open source projects handling those sensitive data?
gradle maven-publish
asked Nov 27 '18 at 7:21
HannesHannes
1,62151732
I think this answer should help you : stackoverflow.com/a/12751665/6899896 : you should extract all personal information out of the projectgradle.propertiesfile, and keep these personal data in your Usergradle.properties( or inject these credentials as environment variable when executing your build script)
– M.Ricciuti
Nov 27 '18 at 8:18
@M.Ricciuti Thanks for the reference to another answer, but the problem with the most voted-up answer is, that thegradle.buildas you check it out from the repository will fail due to missing values. I am not sure if this is acceptable.
– Hannes
Nov 27 '18 at 21:32
@M.Ricciuti Thanks a lot for this - works perfectly for me :-)
– Hannes
Nov 28 '18 at 5:58
add a comment |
I do publish an open source library to Maven Central. In order to do that the gradle.build file contains variable references to a gradle.properties file which contains secret information like usernames and passwords.
Of course the build.gradle needs to be published to the public git repository, the gradle.properties should not be published, due to containing all the personal information but without the properties file the build.gradle is not valid.
How are open source projects handling those sensitive data?
gradle maven-publish
asked Nov 27 '18 at 7:21
HannesHannes
1,62151732
I do publish an open source library to Maven Central. In order to do that the gradle.build file contains variable references to a gradle.properties file which contains secret information like usernames and passwords.
Of course the build.gradle needs to be published to the public git repository, the gradle.properties should not be published, due to containing all the personal information but without the properties file the build.gradle is not valid.
How are open source projects handling those sensitive data?
gradle maven-publish
gradle maven-publish
asked Nov 27 '18 at 7:21
HannesHannes
1,62151732
asked Nov 27 '18 at 7:21
HannesHannes
1,62151732
asked Nov 27 '18 at 7:21
HannesHannes
1,62151732
asked Nov 27 '18 at 7:21
HannesHannes
1,62151732
asked Nov 27 '18 at 7:21
HannesHannes
1,62151732
1,62151732
I think this answer should help you : stackoverflow.com/a/12751665/6899896 : you should extract all personal information out of the projectgradle.propertiesfile, and keep these personal data in your Usergradle.properties( or inject these credentials as environment variable when executing your build script)
– M.Ricciuti
Nov 27 '18 at 8:18
@M.Ricciuti Thanks for the reference to another answer, but the problem with the most voted-up answer is, that thegradle.buildas you check it out from the repository will fail due to missing values. I am not sure if this is acceptable.
– Hannes
Nov 27 '18 at 21:32
@M.Ricciuti Thanks a lot for this - works perfectly for me :-)
– Hannes
Nov 28 '18 at 5:58
add a comment |
I think this answer should help you : stackoverflow.com/a/12751665/6899896 : you should extract all personal information out of the projectgradle.propertiesfile, and keep these personal data in your Usergradle.properties( or inject these credentials as environment variable when executing your build script)
– M.Ricciuti
Nov 27 '18 at 8:18
@M.Ricciuti Thanks for the reference to another answer, but the problem with the most voted-up answer is, that thegradle.buildas you check it out from the repository will fail due to missing values. I am not sure if this is acceptable.
– Hannes
Nov 27 '18 at 21:32
@M.Ricciuti Thanks a lot for this - works perfectly for me :-)
– Hannes
Nov 28 '18 at 5:58
I think this answer should help you : stackoverflow.com/a/12751665/6899896 : you should extract all personal information out of the project
gradle.properties file, and keep these personal data in your User gradle.properties ( or inject these credentials as environment variable when executing your build script)– M.Ricciuti
Nov 27 '18 at 8:18
I think this answer should help you : stackoverflow.com/a/12751665/6899896 : you should extract all personal information out of the project
gradle.properties file, and keep these personal data in your User gradle.properties ( or inject these credentials as environment variable when executing your build script)– M.Ricciuti
Nov 27 '18 at 8:18
@M.Ricciuti Thanks for the reference to another answer, but the problem with the most voted-up answer is, that the
gradle.build as you check it out from the repository will fail due to missing values. I am not sure if this is acceptable.– Hannes
Nov 27 '18 at 21:32
@M.Ricciuti Thanks for the reference to another answer, but the problem with the most voted-up answer is, that the
gradle.build as you check it out from the repository will fail due to missing values. I am not sure if this is acceptable.– Hannes
Nov 27 '18 at 21:32
@M.Ricciuti Thanks a lot for this - works perfectly for me :-)
– Hannes
Nov 28 '18 at 5:58
@M.Ricciuti Thanks a lot for this - works perfectly for me :-)
– Hannes
Nov 28 '18 at 5:58
add a comment |
1 Answer
1
active
oldest
votes
Here is a solution based on this answer, with the use of findProperty method to allow users to build your project without providing the publishing credentials (issue you mentioned in your comment above)
- move credentials outside the project's
gradle.propertiesand put them to your local user/.gradle/gradle.propertiesconfiguration file
in your publish task definition, use:
authentication(userName: findProperty('mavenUser'), password: findProperty('mavenPassword'))
answered Nov 28 '18 at 19:29
M.RicciutiM.Ricciuti
3,5502419
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53494588%2fwhere-to-keep-maven-publish-related-sections-of-gradle-build-file%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Here is a solution based on this answer, with the use of findProperty method to allow users to build your project without providing the publishing credentials (issue you mentioned in your comment above)
- move credentials outside the project's
gradle.propertiesand put them to your local user/.gradle/gradle.propertiesconfiguration file
in your publish task definition, use:
authentication(userName: findProperty('mavenUser'), password: findProperty('mavenPassword'))
answered Nov 28 '18 at 19:29
M.RicciutiM.Ricciuti
3,5502419
add a comment |
Here is a solution based on this answer, with the use of findProperty method to allow users to build your project without providing the publishing credentials (issue you mentioned in your comment above)
- move credentials outside the project's
gradle.propertiesand put them to your local user/.gradle/gradle.propertiesconfiguration file
in your publish task definition, use:
authentication(userName: findProperty('mavenUser'), password: findProperty('mavenPassword'))
answered Nov 28 '18 at 19:29
M.RicciutiM.Ricciuti
3,5502419
add a comment |
Here is a solution based on this answer, with the use of findProperty method to allow users to build your project without providing the publishing credentials (issue you mentioned in your comment above)
- move credentials outside the project's
gradle.propertiesand put them to your local user/.gradle/gradle.propertiesconfiguration file
in your publish task definition, use:
authentication(userName: findProperty('mavenUser'), password: findProperty('mavenPassword'))
answered Nov 28 '18 at 19:29
M.RicciutiM.Ricciuti
3,5502419
Here is a solution based on this answer, with the use of findProperty method to allow users to build your project without providing the publishing credentials (issue you mentioned in your comment above)
- move credentials outside the project's
gradle.propertiesand put them to your local user/.gradle/gradle.propertiesconfiguration file
in your publish task definition, use:
authentication(userName: findProperty('mavenUser'), password: findProperty('mavenPassword'))
answered Nov 28 '18 at 19:29
M.RicciutiM.Ricciuti
3,5502419
answered Nov 28 '18 at 19:29
M.RicciutiM.Ricciuti
3,5502419
answered Nov 28 '18 at 19:29
M.RicciutiM.Ricciuti
3,5502419
answered Nov 28 '18 at 19:29
M.RicciutiM.Ricciuti
3,5502419
3,5502419
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53494588%2fwhere-to-keep-maven-publish-related-sections-of-gradle-build-file%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
I think this answer should help you : stackoverflow.com/a/12751665/6899896 : you should extract all personal information out of the project
gradle.propertiesfile, and keep these personal data in your Usergradle.properties( or inject these credentials as environment variable when executing your build script)– M.Ricciuti
Nov 27 '18 at 8:18
@M.Ricciuti Thanks for the reference to another answer, but the problem with the most voted-up answer is, that the
gradle.buildas you check it out from the repository will fail due to missing values. I am not sure if this is acceptable.– Hannes
Nov 27 '18 at 21:32
@M.Ricciuti Thanks a lot for this - works perfectly for me :-)
– Hannes
Nov 28 '18 at 5:58