[JBoss JIRA] (JBIDE-21801) Can't Download Runtimes for JBoss EAP and JBoss Fuse using git account signup
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21801?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-21801:
-------------------------------
Fix Version/s: 4.4.0.Alpha2
(was: 4.4.0.Alpha1)
> Can't Download Runtimes for JBoss EAP and JBoss Fuse using git account signup
> -----------------------------------------------------------------------------
>
> Key: JBIDE-21801
> URL: https://issues.jboss.org/browse/JBIDE-21801
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server, upstream
> Affects Versions: 4.3.1.Beta2
> Reporter: Aurélien Pupier
> Assignee: Rob Stryker
> Fix For: 4.3.2.Final, 4.4.0.Alpha2
>
> Attachments: 1-preferencepage.png, 2-selectRuntime.png, 3-clickDownLoadAndInstall.png, 4-selectEactVersion.png, 5-fillCredentials.png, 6-PleaseuseFollowingLink.png, 7-allInformationprovided.png
>
>
> first technical investigation:
> - the url used to retrieve information on the Terms and conditions page is (I put a breakpoint on DownloadmanagertermsAndConditionsFragment.getTCResponseString): https://developers.redhat.com/download-manager/rest/tc?downloadURL=https%...
> and it returns:
> {noformat}
> <?xml version="1.0" encoding="UTF-8"?>
> <result>
> <htmlText><![CDATA[It is no longer possible to accept terms and conditions in the wizard. Please, use <a href="https://developers.redhat.com/download-manager/file/jboss-fuse-6.2.1.GA-f...">following link</a> instead!]]></htmlText>
> <plainText><![CDATA[It is no longer possible to accept terms and conditions in the wizard. Please, use https://developers.redhat.com/download-manager/file/jboss-fuse-6.2.1.GA-f... instead!]]></plainText>
> <customParams>
> <param name="company" label="Company" />
> <param name="country" label="Country" >
> <options multiple="false">
> </options>
> </param>
> <param name="downloadURL" label="Downloaded file" >
> <options multiple="false">
> <option key="https://www.jboss.org/download-manager/content/origin/files/sha256/e5/e5b..."/>
> </options>
> </param>
> </customParams>
> </result>
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBIDE-22248) Some CI jobs fail at deploying to Nexus
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22248?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-22248:
-------------------------------
Fix Version/s: 4.4.0.Alpha2
(was: 4.4.0.Alpha1)
> Some CI jobs fail at deploying to Nexus
> ---------------------------------------
>
> Key: JBIDE-22248
> URL: https://issues.jboss.org/browse/JBIDE-22248
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Affects Versions: 4.4.0.Alpha1
> Reporter: Martin Malina
> Assignee: Nick Boldt
> Priority: Blocker
> Fix For: 4.4.0.Alpha2
>
>
> Nick, can you take a look why mvn deploy fails here?
> https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS...
> It worked for us in the past.
> It says:
> {code}
> [WARNING] Could not transfer metadata org.jboss.reddeer:jboss-reddeer-archetype/maven-metadata.xml from/to jboss-snapshots-repository (https://repository.jboss.org/nexus/content/repositories/snapshots/): Not authorized , ReasonPhrase:Unauthorized.
> [INFO] ------------------------------------------------------------------------
> [INFO] BUILD FAILURE
> [INFO] ------------------------------------------------------------------------
> [INFO] Total time: 04:49 min
> [INFO] Finished at: 2016-04-26T09:42:02-04:00
> [INFO] Final Memory: 19M/612M
> [INFO] ------------------------------------------------------------------------
> [ERROR] Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy (default-deploy) on project jboss-reddeer-archetype: Failed to retrieve remote metadata org.jboss.reddeer:jboss-reddeer-archetype/maven-metadata.xml: Could not transfer metadata org.jboss.reddeer:jboss-reddeer-archetype/maven-metadata.xml from/to jboss-snapshots-repository (https://repository.jboss.org/nexus/content/repositories/snapshots/): Not authorized , ReasonPhrase:Unauthorized. -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please read the following articles:
> [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
> {code}
> I'm not exactly sure how this works. Or is this something that is managed in jenkins config, so should I raise this with the jenkins team?
> Cc: [~rawagner]
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months