[JBoss JIRA] (JBDS-4179) DevStudio installer uses console installation instead of wizard
by Lukáš Valach (JIRA)
[ https://issues.jboss.org/browse/JBDS-4179?page=com.atlassian.jira.plugin.... ]
Lukáš Valach edited comment on JBDS-4179 at 12/8/16 8:54 AM:
-------------------------------------------------------------
Reproduced on Fedora 25 64bit and openjdk 1.8.0_111. I tried to run installer using clean image for VirtualBox which I downloaded from http://www.osboxes.org/fedora/. I hope it helps to reproduce this issue.
GraphicsEnvironment.isHeadless() also returning true.
was (Author: lvalach):
Reproduced on Fedora 25 64bit and openjdk 1.8.0_111. I tried to run installer using clean image for VirtualBox which I downloaded from http://www.osboxes.org/fedora/. I hope it helps to reproduce this issue.
> DevStudio installer uses console installation instead of wizard
> ---------------------------------------------------------------
>
> Key: JBDS-4179
> URL: https://issues.jboss.org/browse/JBDS-4179
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: documentation, installer, upstream
> Affects Versions: 10.2.0.GA
> Environment: openjdk version "1.8.0_102"
> OpenJDK Runtime Environment (build 1.8.0_102-b14)
> Reporter: Marián Labuda
> Assignee: Denis Golovin
> Fix For: 10.x
>
>
> I tried to install latest DevStudio (devstudio-10.2.0.GA-v20161116-0039-B6472-installer-standalone.jar) but when I run installation as usual, I get console installation - at first whole license text and prompt to 1) Accept, 2) Reject, 3) Redisplay. After that installation unpack files to home and I am not able to select destination.
> This happens with older version of openjdk8. With latest available openjdk for fedora (1.8.0_111) it works.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBDS-4214) use a less confusing path segment for the devstudio update & build folders
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4214?page=com.atlassian.jira.plugin.... ]
Nick Boldt commented on JBDS-4214:
----------------------------------
OK, so when we start on the oxygen.m4-based CI builds some time after Dec 15, we'll use /11/ for devstudio and /oxygen/ for jbosstools.
I would also have accepted /spinal-tap/ or /stranger-things/ had anyone suggested it, but it's too late now. :D
> use a less confusing path segment for the devstudio update & build folders
> --------------------------------------------------------------------------
>
> Key: JBDS-4214
> URL: https://issues.jboss.org/browse/JBDS-4214
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: build, rpm, updatesite
> Affects Versions: 10.2.0.GA
> Reporter: Nick Boldt
> Assignee: Alexey Kazakov
> Fix For: 11.0.0.AM1
>
>
> Alexey and Tim think that using https://devstudio.jboss.com/10.0/stable/updates/ for the update site that contains 10.0, 10.1, 10.2, 10.3 updates... is confusing.
> So, for devstudio 11, we could use:
> * /11/
> * /11.x/
> * /oxygen/ (because this is based on Eclipse Oxygen)
> * /e47/ (because this is based on Eclipse 4.7)
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBDS-4179) DevStudio installer uses console installation instead of wizard
by Lukáš Valach (JIRA)
[ https://issues.jboss.org/browse/JBDS-4179?page=com.atlassian.jira.plugin.... ]
Lukáš Valach commented on JBDS-4179:
------------------------------------
Reproduced on Fedora 25 64bit and openjdk 1.8.0_111. I tried to run installer using clean image for VirtualBox which I downloaded from http://www.osboxes.org/fedora/. I hope it helps to reproduce this issue.
> DevStudio installer uses console installation instead of wizard
> ---------------------------------------------------------------
>
> Key: JBDS-4179
> URL: https://issues.jboss.org/browse/JBDS-4179
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: documentation, installer, upstream
> Affects Versions: 10.2.0.GA
> Environment: openjdk version "1.8.0_102"
> OpenJDK Runtime Environment (build 1.8.0_102-b14)
> Reporter: Marián Labuda
> Assignee: Denis Golovin
> Fix For: 10.x
>
>
> I tried to install latest DevStudio (devstudio-10.2.0.GA-v20161116-0039-B6472-installer-standalone.jar) but when I run installation as usual, I get console installation - at first whole license text and prompt to 1) Accept, 2) Reject, 3) Redisplay. After that installation unpack files to home and I am not able to select destination.
> This happens with older version of openjdk8. With latest available openjdk for fedora (1.8.0_111) it works.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBDS-4214) use a less confusing path segment for the devstudio update & build folders
by Todd Mancini (JIRA)
[ https://issues.jboss.org/browse/JBDS-4214?page=com.atlassian.jira.plugin.... ]
Todd Mancini commented on JBDS-4214:
------------------------------------
I like 11 the most -- mainly because it's devstudio 11, not devstudio oxygen. I totally appreciate the fact that it is based upon oxygen, but I think the more natural association is with 11. Besides, in the future, it's much easier to remember /10, /11, /12 then /oxygen, /neon, etc.
I also prefer /11 over /11.x. I think the most natural usage is to go off of the major revision #, with the assumption that, in doing so, I'm looking at the latest minor revision of that major release.
> use a less confusing path segment for the devstudio update & build folders
> --------------------------------------------------------------------------
>
> Key: JBDS-4214
> URL: https://issues.jboss.org/browse/JBDS-4214
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: build, rpm, updatesite
> Affects Versions: 10.2.0.GA
> Reporter: Nick Boldt
> Assignee: Alexey Kazakov
> Fix For: 11.0.0.AM1
>
>
> Alexey and Tim think that using https://devstudio.jboss.com/10.0/stable/updates/ for the update site that contains 10.0, 10.1, 10.2, 10.3 updates... is confusing.
> So, for devstudio 11, we could use:
> * /11/
> * /11.x/
> * /oxygen/ (because this is based on Eclipse Oxygen)
> * /e47/ (because this is based on Eclipse 4.7)
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBIDE-23632) Fehler bei Installation in Eclipse - Artifact not found
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23632?page=com.atlassian.jira.plugi... ]
Jeff MAURY reassigned JBIDE-23632:
----------------------------------
Component/s: build
Assignee: Nick Boldt
> Fehler bei Installation in Eclipse - Artifact not found
> -------------------------------------------------------
>
> Key: JBIDE-23632
> URL: https://issues.jboss.org/browse/JBIDE-23632
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Affects Versions: 4.4.0.Final
> Environment: Win7 (tried three different mashines, two virtual ones, on physical)
> Eclipse Neon x64 or Eclipse Neon 1a x64
> Reporter: Heinz Erhard
> Assignee: Nick Boldt
> Labels: eclipse, jboss_tools
>
> Hello,
> I downloaded Eclipse from its homepage (NEON and NEON1a, also tried MARS).
> Tried installing JBOSS Tools:
> http://tools.jboss.org/downloads/jbosstools/neon/4.4.0.Final.html#update_...
> and also tried:
> http://tools.jboss.org/downloads/jbosstools/neon/4.4.1.Final.html
> Always, after selecting all componentes and agreeing licens, its download some sources but after some minutes I am always getting this error:
> An error occurred while collecting items to be installed
> session context was:(profile=epp.package.jee, phase=org.eclipse.equinox.internal.p2.engine.phases.Collect, operand=, action=).
> Artifact not found: http://download.jboss.org/jbosstools/static/neon/stable/updates/core/4.4.....
> http://download.jboss.org/jbosstools/static/neon/stable/updates/core/4.4....
> Artifact not found: http://download.jboss.org/jbosstools/static/neon/stable/updates/core/4.4.....
> http://download.jboss.org/jbosstools/static/neon/stable/updates/core/4.4....
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months