[JBoss JIRA] (JBTIS-914) Integration Stack features have incorrect versions
by Andrej Podhradsky (JIRA)
Andrej Podhradsky created JBTIS-914:
---------------------------------------
Summary: Integration Stack features have incorrect versions
Key: JBTIS-914
URL: https://issues.jboss.org/browse/JBTIS-914
Project: JBoss Tools Integration Stack
Issue Type: Bug
Components: distribution
Affects Versions: 9.0.2.CR1
Reporter: Andrej Podhradsky
Priority: Critical
|com.jboss.devstudio.integration-stack.bpr.feature|9.0.2.CR1|
|com.jboss.devstudio.integration-stack.ds.feature|9.0.2.CR1|
|com.jboss.devstudio.integration-stack.fuse.feature|9.0.2.CR1|
|com.jboss.devstudio.integration-stack.soa.feature|9.0.2.CR1|
The version should be something like *9.0.1.GA-v20160808-1454-B27*
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 6 months
[JBoss JIRA] (JBDS-4057) cdk fails, online install
by Jan Richter (JIRA)
[ https://issues.jboss.org/browse/JBDS-4057?page=com.atlassian.jira.plugin.... ]
Jan Richter commented on JBDS-4057:
-----------------------------------
[~mhusnain] this sounds a bit like JBDS-4033. Do you have Microsoft Visual C++ 2010 Redistributable Package (x86) [1] installed? If not, vagrant box add does not work.
[1] https://www.microsoft.com/en-us/download/details.aspx?id=5555
> cdk fails, online install
> -------------------------
>
> Key: JBDS-4057
> URL: https://issues.jboss.org/browse/JBDS-4057
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: platform-installer
> Affects Versions: 10.1.0.GA
> Reporter: Misha Ali
> Assignee: Denis Golovin
> Attachments: install (1).log, openjdk.log, vagrant.log, vbox.log
>
>
> I'm testing the online installer on a win 8 VM. The username is administrator, so we shouldn't face the space in the user name issue.
> I've run the online installer thrice now and every component has installed, but CDK fails with no useful error message or log. I don't know if this can be replicated, but I will add the VM I'm using in an internal comment for testing.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 6 months
[JBoss JIRA] (JBDS-4059) RPM errors: Installing rh-eclipse46-devstudio.10.1 into rh-eclipse46 beta.
by Václav Kadlčík (JIRA)
[ https://issues.jboss.org/browse/JBDS-4059?page=com.atlassian.jira.plugin.... ]
Václav Kadlčík commented on JBDS-4059:
--------------------------------------
(rh-eclipse46-eclipse-swt and its libjawt.so are a known false positive, there is some train of RPM deps which handles it.)
If I may comment on the question, the missing references come from rh-eclipse46-devstudio so the dependencies should be expressed there.
Note, however, that there's some error with libnotify: devstudio refers libnotify.so.1 which is not satisfiable on RHEL7 (only libnotify.so.4 is available). Maybe the reference comes from some dead part which could be cut out and there's no need for libnotify at all. If you actually need it, then the code should be rebuilt against libnotify.so.4; only then it would make sense to add the dependency on libnotify.
> RPM errors: Installing rh-eclipse46-devstudio.10.1 into rh-eclipse46 beta.
> --------------------------------------------------------------------------
>
> Key: JBDS-4059
> URL: https://issues.jboss.org/browse/JBDS-4059
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: build
> Reporter: Pavol Srna
> Assignee: Nick Boldt
>
> [~vkadlcik] has run some rpm sanity tests. The findings can be seen here: http://nest.test.redhat.com/mnt/qa/scratch/bkr-hv03-guest19/2016:24366/tp...
> [~nickboldt] can you please investigate? Thanks!
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 6 months
[JBoss JIRA] (JBDS-4057) cdk fails, online install
by Misha Ali (JIRA)
[ https://issues.jboss.org/browse/JBDS-4057?page=com.atlassian.jira.plugin.... ]
Misha Ali commented on JBDS-4057:
---------------------------------
Done, Alexey. Please let me know if there are any other logs you need.
> cdk fails, online install
> -------------------------
>
> Key: JBDS-4057
> URL: https://issues.jboss.org/browse/JBDS-4057
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: platform-installer
> Affects Versions: 10.1.0.GA
> Reporter: Misha Ali
> Assignee: Denis Golovin
> Attachments: install (1).log, openjdk.log, vagrant.log, vbox.log
>
>
> I'm testing the online installer on a win 8 VM. The username is administrator, so we shouldn't face the space in the user name issue.
> I've run the online installer thrice now and every component has installed, but CDK fails with no useful error message or log. I don't know if this can be replicated, but I will add the VM I'm using in an internal comment for testing.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 6 months
[JBoss JIRA] (JBDS-4057) cdk fails, online install
by Misha Ali (JIRA)
[ https://issues.jboss.org/browse/JBDS-4057?page=com.atlassian.jira.plugin.... ]
Misha Ali updated JBDS-4057:
----------------------------
Attachment: install (1).log
openjdk.log
vagrant.log
vbox.log
Generic install logs
> cdk fails, online install
> -------------------------
>
> Key: JBDS-4057
> URL: https://issues.jboss.org/browse/JBDS-4057
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: platform-installer
> Affects Versions: 10.1.0.GA
> Reporter: Misha Ali
> Assignee: Denis Golovin
> Attachments: install (1).log, openjdk.log, vagrant.log, vbox.log
>
>
> I'm testing the online installer on a win 8 VM. The username is administrator, so we shouldn't face the space in the user name issue.
> I've run the online installer thrice now and every component has installed, but CDK fails with no useful error message or log. I don't know if this can be replicated, but I will add the VM I'm using in an internal comment for testing.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 6 months
[JBoss JIRA] (JBDS-3834) Install fail - what next?
by Misha Ali (JIRA)
[ https://issues.jboss.org/browse/JBDS-3834?page=com.atlassian.jira.plugin.... ]
Misha Ali commented on JBDS-3834:
---------------------------------
Came across this frustrating issue again today. Would it be possible to have a retry button or a retry arrow to allow users to retry whatever part failed? At the moment if one component fails, the installation just halts and this is a really awkward user experience with no way to gracefully exit or retry.
> Install fail - what next?
> -------------------------
>
> Key: JBDS-3834
> URL: https://issues.jboss.org/browse/JBDS-3834
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Feature Request
> Components: platform-installer
> Affects Versions: 9.1.0.GA
> Reporter: Misha Ali
> Assignee: Denis Golovin
> Fix For: 10.2.0.AM1
>
> Attachments: error.PNG, fail_install.PNG
>
>
> Testing the Installer a bit more and I realize this is currently tech preview but when one (or more) components fail, there is no next step for users. There is no cancel or quit button to exit the failed install, nor is there a retry for the failed component, nor any error message at all. As a user, I'd be confused about what I should do next at this stage. I think this might be worth looking into with UX for the 9.1 GA++ release.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 6 months
[JBoss JIRA] (JBDS-3834) Install fail - what next?
by Misha Ali (JIRA)
[ https://issues.jboss.org/browse/JBDS-3834?page=com.atlassian.jira.plugin.... ]
Misha Ali updated JBDS-3834:
----------------------------
Priority: Major (was: Minor)
> Install fail - what next?
> -------------------------
>
> Key: JBDS-3834
> URL: https://issues.jboss.org/browse/JBDS-3834
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Feature Request
> Components: platform-installer
> Affects Versions: 9.1.0.GA
> Reporter: Misha Ali
> Assignee: Denis Golovin
> Fix For: 10.2.0.AM1
>
> Attachments: error.PNG, fail_install.PNG
>
>
> Testing the Installer a bit more and I realize this is currently tech preview but when one (or more) components fail, there is no next step for users. There is no cancel or quit button to exit the failed install, nor is there a retry for the failed component, nor any error message at all. As a user, I'd be confused about what I should do next at this stage. I think this might be worth looking into with UX for the 9.1 GA++ release.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 6 months