Hi, just say that I use what Chris suggest in other maven environments.
El lun, 23 nov 2020 a las 13:29, Christofer Dutz (<christofer.d...@c-ware.de>) escribió: > Hi Harbs, > > does this answer your question? > > https://stackoverflow.com/questions/31251259/how-to-pass-maven-settings-via-environmental-vars > > In short you would create the settings.xml file the same way, but use > environment variables as source: > > <servers> > <server> > <id>deploymentRepo</id> > <username>${server.username}</username> > <password>${server.password}</password> > </server> > </servers> > > But I am not sure about how this would possibly be logged somewhere in > Jenkins or on the System itself. > > Chris > > > > Am 23.11.20, 12:48 schrieb "Harbs" <harbs.li...@gmail.com>: > > Is there a way to pull the maven credentials from an env var? > > That might make it more practical to use a CI server for this. > > > On Sep 25, 2020, at 12:13 AM, Christofer Dutz < > christofer.d...@c-ware.de> wrote: > > > > Hi all, > > > > The error you got @harbs was that when deploying the artifact in the > release:perform step you probably didn't have your apache credentials setup > in your settings.xml to the server declined the deployment. > > > > I described what has to be done here: > > https://plc4x.apache.org/developers/release/release.html > > Especially the part "Preparing your system for being able to > release" is what you should have a look at. > > Even if I wrote the documentation for PLC4X, this part identically > applies for this case. > > > > Hope that helps. > > > > Chris > > > > Am 24.09.20, 18:16 schrieb "Yishay Weiss" <yishayj...@hotmail.com>: > > > > Is this the same step where you got stuck before? From what I > remember you were missing a way to specify your SVN credentials on dist and > I added param in the form for that. Can you trace the old thread on dev and > verify? > > > > From: Harbs<mailto:harbs.li...@gmail.com> > > Sent: Thursday, September 24, 2020 11:31 AM > > To: Apache Royale Development<mailto:dev@royale.apache.org> > > Subject: Re: [royale-compiler] branch develop updated: > [maven-release-plugin] prepare for next development iteration > > > > I’m trying to work on the release of the compiler build tools, > but I really don’t understand what I’m doing. > > > > Step 2 was successful here: > https://github.com/apache/royale-asjs/wiki/Task-List-For-Royale-Releases < > https://github.com/apache/royale-asjs/wiki/Task-List-For-Royale-Releases> > but step three failed with the following error: > > > > [INFO] [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy (default-deploy) > on project compiler-build-tools: Failed to deploy artifacts: Could not > transfer artifact org.apache.royale.compiler:compiler-build-tools:jar:1.2.1 > from/to apache.releases.https ( > https://repository.apache.org/service/local/staging/deploy/maven2): > Transfer failed for > https://repository.apache.org/service/local/staging/deploy/maven2/org/apache/royale/compiler/compiler-build-tools/1.2.1/compiler-build-tools-1.2.1.jar > 401 Unauthorized -> [Help 1] > > [INFO] [ERROR] > > [INFO] [ERROR] To see the full stack trace of the errors, re-run > Maven with the -e switch. > > [INFO] [ERROR] Re-run Maven using the -X switch to enable full > debug logging. > > [INFO] [ERROR] > > [INFO] [ERROR] For more information about the errors and possible > solutions, please read the following articles: > > [INFO] [ERROR] [Help 1] > http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException > > [INFO] > ------------------------------------------------------------------------ > > [INFO] BUILD FAILURE > > [INFO] > ------------------------------------------------------------------------ > > [INFO] Total time: 08:39 min > > [INFO] Finished at: 2020-09-24T11:27:29+03:00 > > [INFO] > ------------------------------------------------------------------------ > > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-release-plugin:3.0.0-M1:perform > (default-cli) on project compiler-build-tools: Maven execution failed, exit > code: '1' -> [Help 1] > > > > I have no idea how the deployment of artifacts work and what > could be causing a 401. > > > > Suggestions? > > Harbs > > > >> On Sep 24, 2020, at 11:17 AM, ha...@apache.org wrote: > >> > >> This is an automated email from the ASF dual-hosted git repository. > >> > >> harbs pushed a commit to branch develop > >> in repository > https://gitbox.apache.org/repos/asf/royale-compiler.git > >> > >> > >> The following commit(s) were added to refs/heads/develop by this > push: > >> new fd62e36 [maven-release-plugin] prepare for next development > iteration > >> fd62e36 is described below > >> > >> commit fd62e368b3ab98f4560c7874360cc10a80b4ef11 > >> Author: Harbs <ha...@in-tools.com> > >> AuthorDate: Thu Sep 24 11:17:21 2020 +0300 > >> > >> [maven-release-plugin] prepare for next development iteration > >> --- > >> compiler-build-tools/pom.xml | 2 +- > >> 1 file changed, 1 insertion(+), 1 deletion(-) > >> > >> diff --git a/compiler-build-tools/pom.xml > b/compiler-build-tools/pom.xml > >> index bebc59f..a88f994 100644 > >> --- a/compiler-build-tools/pom.xml > >> +++ b/compiler-build-tools/pom.xml > >> @@ -28,7 +28,7 @@ > >> > >> <groupId>org.apache.royale.compiler</groupId> > >> <artifactId>compiler-build-tools</artifactId> > >> - <version>1.2.1</version> > >> + <version>1.2.2-SNAPSHOT</version> > >> <packaging>maven-plugin</packaging> > >> > >> <name>Apache Royale: Build Tools</name> > >> > > > > > > > -- Carlos Rovira Apache Member & Apache Royale PMC *Apache Software Foundation* http://about.me/carlosrovira
