July 2018 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-4696) Cannot install org.sonatype.tycho

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4696?page=com.atlassian.jira.plugin.... ] Nick Boldt reassigned JBDS-4696: -------------------------------- Assignee: Josef Kopriva (was: Nick Boldt) > Cannot install org.sonatype.tycho > --------------------------------- > > Key: JBDS-4696 > URL: https://issues.jboss.org/browse/JBDS-4696 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: target-platform > Affects Versions: 12.0.0.AM1 > Environment: Red Hat JBoss Developer Studio > Version: 12.0.0.AM1 > Build id: AM1-v20180502-0411-B2377 > Build date: 20180502-0411 > Reporter: Josef Kopriva > Assignee: Josef Kopriva > Priority: Critical > Labels: releasework > Fix For: 12.0.0.GA > > Attachments: 4696_01.png, 4696_02.png, 4696_03.png, 4696_03b.png > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4696) Cannot install org.sonatype.tycho

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4696?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-4696: ----------------------------- Attachment: 4696_02.png 4696_01.png > Cannot install org.sonatype.tycho > --------------------------------- > > Key: JBDS-4696 > URL: https://issues.jboss.org/browse/JBDS-4696 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: target-platform > Affects Versions: 12.0.0.AM1 > Environment: Red Hat JBoss Developer Studio > Version: 12.0.0.AM1 > Build id: AM1-v20180502-0411-B2377 > Build date: 20180502-0411 > Reporter: Josef Kopriva > Assignee: Nick Boldt > Priority: Critical > Labels: releasework > Fix For: 12.0.0.GA > > Attachments: 4696_01.png, 4696_02.png, 4696_03.png, 4696_03b.png > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4696) Cannot install org.sonatype.tycho

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4696?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-4696: ---------------------------------- With BYOE install of devstudio 12.0.0.v20180710-1916 into Photon.0 R JavaEE bundle, I'm not prompted to install tycho connector after doing a maven project import. Tried with two projects: !4696_01.png|thumbnail! !4696_02.png|thumbnail! But I can install *Tycho Project Configurators* +0.8.1.201704211436+ manually from Window > Preferences > Maven > Discovery > Open Catalog > type "tycho" > install. !4696_03.png|thumbnail! !4696_03b.png|thumbnail! ---- Noteworthy too, devstudio installed via installer (devstudio-12.0.0.GA-v20180710-1916-B2972-installer-standalone) has : * *m2e - Maven Integration for Eclipse* +1.9.1.20180704-1406+ But devstudio via BYOE install has: * *m2e - Maven Integration for Eclipse* +1.9.0.20180606-2036+ But the newer one can be discovered via Help > Check for updates, so we're good there. > Cannot install org.sonatype.tycho > --------------------------------- > > Key: JBDS-4696 > URL: https://issues.jboss.org/browse/JBDS-4696 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: target-platform > Affects Versions: 12.0.0.AM1 > Environment: Red Hat JBoss Developer Studio > Version: 12.0.0.AM1 > Build id: AM1-v20180502-0411-B2377 > Build date: 20180502-0411 > Reporter: Josef Kopriva > Assignee: Nick Boldt > Priority: Critical > Labels: releasework > Fix For: 12.0.0.GA > > Attachments: 4696_01.png, 4696_02.png, 4696_03.png, 4696_03b.png > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4696) Cannot install org.sonatype.tycho

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4696?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-4696: ----------------------------- Attachment: 4696_03.png > Cannot install org.sonatype.tycho > --------------------------------- > > Key: JBDS-4696 > URL: https://issues.jboss.org/browse/JBDS-4696 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: target-platform > Affects Versions: 12.0.0.AM1 > Environment: Red Hat JBoss Developer Studio > Version: 12.0.0.AM1 > Build id: AM1-v20180502-0411-B2377 > Build date: 20180502-0411 > Reporter: Josef Kopriva > Assignee: Nick Boldt > Priority: Critical > Labels: releasework > Fix For: 12.0.0.GA > > Attachments: 4696_03.png, 4696_03b.png > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4696) Cannot install org.sonatype.tycho

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4696?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-4696: ----------------------------- Attachment: 4696_03b.png > Cannot install org.sonatype.tycho > --------------------------------- > > Key: JBDS-4696 > URL: https://issues.jboss.org/browse/JBDS-4696 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: target-platform > Affects Versions: 12.0.0.AM1 > Environment: Red Hat JBoss Developer Studio > Version: 12.0.0.AM1 > Build id: AM1-v20180502-0411-B2377 > Build date: 20180502-0411 > Reporter: Josef Kopriva > Assignee: Nick Boldt > Priority: Critical > Labels: releasework > Fix For: 12.0.0.GA > > Attachments: 4696_03.png, 4696_03b.png > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3871) installer credentials misleading/incomplete information.

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3871?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-3871: ---------------------------------- [checkUnresolvedIssues.py] Slip to fixversion = *12.x* > installer credentials misleading/incomplete information. > -------------------------------------------------------- > > Key: JBDS-3871 > URL: https://issues.jboss.org/browse/JBDS-3871 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 9.1.0.Beta1 > Environment: Win 7/64 bit > Reporter: Robert Terzi > Assignee: Denis Golovin > Priority: Minor > Labels: ui > Fix For: 12.x > > Attachments: screenshot-1.png > > > There are several problems a with the information on the platform installer's login screen: > # "Your developers.redhat.com credentials" is misleading, Should probably be "Your Red Hat username" to be consistent with RHDeveloper registration process. > # The register link points to the login page, not the register page. > # Registering on RHDevelopers isn't sufficient. (A registered user gets " Terms and Conditions for CDK have not been signed." > # There should probably be a link to a page on RHDev with more info/FAQ about credentials, the registration process, and obtaining a (no-cost) subscription. > The platform installer description of the credentials to use are misleading. Currently it says " Try it now by providing your developers.redhat.com credentials to get access." > Users can log into RHDevelopers via other accounts (github, linkedin, stack overflow, etc. using OAUTH). They can not log into access.redhat.com (the customer portal) or other Red Hat sites with their developer.redhat.com "credentials". > During registration on RHDevelopers, a simple developers account is created. (Note: At this point, a Red Hat username hasn't been created yet. > Currently, when the user clicks a download link that goes through RHDev download manager, their account is "upgraded", which creates a Red Hat user than can be used to log into RHCP. Terms & conditions are presented. A no-cost RHEL Developer suite subscription is added to the user's Red Hat account. > Their Red Hat username and password which could be different from the RHDeveloper credentials. They will need their Red Hat username for the CDK box to attach to their subscription. Without it the CDK box won't start up correctly as it can't download software. > Some of this is covered for external users in the No-cost RHEL Dev. Suite FAQ. http://developers.redhat.com/articles/no-cost-rhel-faq/ We might need to do a version of that for CDK and JBDS platform installer.. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4673) Launch Installer e2e tests on Windows with a space in username

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4673?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-4673: ---------------------------------- [checkUnresolvedIssues.py] Slip to fixversion = *12.x* > Launch Installer e2e tests on Windows with a space in username > -------------------------------------------------------------- > > Key: JBDS-4673 > URL: https://issues.jboss.org/browse/JBDS-4673 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Task > Components: installer > Reporter: Aurélien Pupier > Assignee: Denis Golovin > Fix For: 12.x > > > there was several issues/regressions for this usecase. it would be nice to have the test launched in this configuration. > Nota: it might be good to test also with some UTF-8 special characters. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4553) Get ready for Java 9

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4553?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-4553: ----------------------------- Fix Version/s: 12.x (was: 12.0.0.GA) > Get ready for Java 9 > -------------------- > > Key: JBDS-4553 > URL: https://issues.jboss.org/browse/JBDS-4553 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Epic > Components: installer, platform-installer > Affects Versions: 11.1.0.AM2 > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Labels: installer, java9 > Fix For: 12.x > > > When 11.1 will be out, Java9 will also be out. The installer refuses to accept Java9 JVM when JBDS is installed. Shouldn't we accept them now ? -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4553) Get ready for Java 9

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4553?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-4553: ---------------------------------- [checkUnresolvedIssues.py] Slip to fixversion = *12.x* > Get ready for Java 9 > -------------------- > > Key: JBDS-4553 > URL: https://issues.jboss.org/browse/JBDS-4553 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Epic > Components: installer, platform-installer > Affects Versions: 11.1.0.AM2 > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Labels: installer, java9 > Fix For: 12.x > > > When 11.1 will be out, Java9 will also be out. The installer refuses to accept Java9 JVM when JBDS is installed. Shouldn't we accept them now ? -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3871) installer credentials misleading/incomplete information.

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3871?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-3871: ----------------------------- Fix Version/s: 12.x (was: 12.0.0.GA) > installer credentials misleading/incomplete information. > -------------------------------------------------------- > > Key: JBDS-3871 > URL: https://issues.jboss.org/browse/JBDS-3871 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 9.1.0.Beta1 > Environment: Win 7/64 bit > Reporter: Robert Terzi > Assignee: Denis Golovin > Priority: Minor > Labels: ui > Fix For: 12.x > > Attachments: screenshot-1.png > > > There are several problems a with the information on the platform installer's login screen: > # "Your developers.redhat.com credentials" is misleading, Should probably be "Your Red Hat username" to be consistent with RHDeveloper registration process. > # The register link points to the login page, not the register page. > # Registering on RHDevelopers isn't sufficient. (A registered user gets " Terms and Conditions for CDK have not been signed." > # There should probably be a link to a page on RHDev with more info/FAQ about credentials, the registration process, and obtaining a (no-cost) subscription. > The platform installer description of the credentials to use are misleading. Currently it says " Try it now by providing your developers.redhat.com credentials to get access." > Users can log into RHDevelopers via other accounts (github, linkedin, stack overflow, etc. using OAUTH). They can not log into access.redhat.com (the customer portal) or other Red Hat sites with their developer.redhat.com "credentials". > During registration on RHDevelopers, a simple developers account is created. (Note: At this point, a Red Hat username hasn't been created yet. > Currently, when the user clicks a download link that goes through RHDev download manager, their account is "upgraded", which creates a Red Hat user than can be used to log into RHCP. Terms & conditions are presented. A no-cost RHEL Developer suite subscription is added to the user's Red Hat account. > Their Red Hat username and password which could be different from the RHDeveloper credentials. They will need their Red Hat username for the CDK box to attach to their subscription. Without it the CDK box won't start up correctly as it can't download software. > Some of this is covered for external users in the No-cost RHEL Dev. Suite FAQ. http://developers.redhat.com/articles/no-cost-rhel-faq/ We might need to do a version of that for CDK and JBDS platform installer.. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues July 2018