[JBoss JIRA] (JBIDE-23039) Need an interactive terminal that fits specific requirements
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23039?page=com.atlassian.jira.plugi... ]
Alexey Kazakov reassigned JBIDE-23039:
--------------------------------------
Assignee: Rob Stryker
> Need an interactive terminal that fits specific requirements
> ------------------------------------------------------------
>
> Key: JBIDE-23039
> URL: https://issues.jboss.org/browse/JBIDE-23039
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: server
> Affects Versions: 4.4.1.AM2
> Reporter: Rob Stryker
> Assignee: Rob Stryker
>
> CDK Tools requires a terminal that allows interactivity of i/o. The full set of requirements is a bit difficult to find a solution for.
> 1) I must be able to get a Process or IProcess object when a command is run
> 2) I must be able to get an event or know when the process terminates
> 3) The terminal or console must be interactive and allow user input when prompted.
> 4) It must behave as in 3) for 'vagrant' commands and any and all associated plugins.
> These three requirements thus far seem impossible to solve. Solutions that have been attempted are:
> 1) Creating a java Process by myself via Runtime.exec. The interactive prompts never arrive and there is no API for Process to know when it is waiting for input.
> 2) Using the external-tools launch configuration. When running a command like mvn, the console that pops up seems to allow input from the user, and functions as expected. However, when running a command such as vagrant, such prompts are not provided. In our usecase, the following behavior is observed:
> a) During vagrant-registration prompts, the console indicates it is not a TTY terminal and cannot allow input
> b) During a landrush prompt for superuser status, no prompt is made, no TTY message is listed, and the process appears to have frozen
> 3) Launching / Opening a tm.terminal view. This solution fails requirements 1 and 2. We are not able to get a Process or an IProcess when a command is launched in a proper interactive terminal. This means we can have no way to know when the process has completed.
> Other options have been explored but ended up at dead ends and not worth mentioning. The real question is why interactive behavior is visible when using external-tools launch config for maven, but is not visible when running vagrant.
> Is this a function of the way the vagrant commands display or prompt for input? Why does vagrant-registration require a TTY terminal, but maven does not? Is this something that can be fixed upstream?
> No other obvious solutions have presented themselves in the past year.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBIDE-23031) OpenShift can't push Docker Images with latest Docker Neon.1 bits
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23031?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-23031:
-----------------------------------
Issue Type: Bug (was: Feature Request)
> OpenShift can't push Docker Images with latest Docker Neon.1 bits
> -----------------------------------------------------------------
>
> Key: JBIDE-23031
> URL: https://issues.jboss.org/browse/JBIDE-23031
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: docker, openshift
> Environment: DevStudio 10.1.0.AM3
> Docker Tooling 2.1.0.201608221023
> Reporter: Fred Bricon
> Assignee: Jeff MAURY
> Priority: Blocker
> Fix For: 4.4.1.Final
>
>
> After installing Docker Tooling 2.1.0.201608221023 on top of Devstudio 10.1.0.AM3, when I try to push a docker image to openshift, I get this error:
> {noformat}
> java.lang.NoClassDefFoundError: org/eclipse/linuxtools/internal/docker/ui/views/ImagePushProgressHandler
> at org.jboss.tools.openshift.internal.ui.dockerutils.PushImageToRegistryJob.doRun(PushImageToRegistryJob.java:66)
> at org.jboss.tools.openshift.internal.common.core.job.AbstractDelegatingMonitorJob.run(AbstractDelegatingMonitorJob.java:37)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> Caused by: java.lang.ClassNotFoundException: org.eclipse.linuxtools.internal.docker.ui.views.ImagePushProgressHandler cannot be found by org.jboss.tools.openshift.ui_3.3.0.v20160812-0126
> at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:448)
> at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:361)
> at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:353)
> at org.eclipse.osgi.internal.loader.ModuleClassLoader.loadClass(ModuleClassLoader.java:161)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> ... 3 more
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBIDE-23039) Need an interactive terminal that fits specific requirements
by Rob Stryker (JIRA)
Rob Stryker created JBIDE-23039:
-----------------------------------
Summary: Need an interactive terminal that fits specific requirements
Key: JBIDE-23039
URL: https://issues.jboss.org/browse/JBIDE-23039
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: server
Affects Versions: 4.4.1.AM2
Reporter: Rob Stryker
CDK Tools requires a terminal that allows interactivity of i/o. The full set of requirements is a bit difficult to find a solution for.
1) I must be able to get a Process or IProcess object when a command is run
2) I must be able to get an event or know when the process terminates
3) The terminal or console must be interactive and allow user input when prompted.
4) It must behave as in 3) for 'vagrant' commands and any and all associated plugins.
These three requirements thus far seem impossible to solve. Solutions that have been attempted are:
1) Creating a java Process by myself via Runtime.exec. The interactive prompts never arrive and there is no API for Process to know when it is waiting for input.
2) Using the external-tools launch configuration. When running a command like mvn, the console that pops up seems to allow input from the user, and functions as expected. However, when running a command such as vagrant, such prompts are not provided. In our usecase, the following behavior is observed:
a) During vagrant-registration prompts, the console indicates it is not a TTY terminal and cannot allow input
b) During a landrush prompt for superuser status, no prompt is made, no TTY message is listed, and the process appears to have frozen
3) Launching / Opening a tm.terminal view. This solution fails requirements 1 and 2. We are not able to get a Process or an IProcess when a command is launched in a proper interactive terminal. This means we can have no way to know when the process has completed.
Other options have been explored but ended up at dead ends and not worth mentioning. The real question is why interactive behavior is visible when using external-tools launch config for maven, but is not visible when running vagrant.
Is this a function of the way the vagrant commands display or prompt for input? Why does vagrant-registration require a TTY terminal, but maven does not? Is this something that can be fixed upstream?
No other obvious solutions have presented themselves in the past year.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBDS-3981) Build a new feature that omits features available from RPM install
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3981?page=com.atlassian.jira.plugin.... ]
Nick Boldt edited comment on JBDS-3981 at 8/24/16 4:28 PM:
-----------------------------------------------------------
To know what's actually included in the RPM (after this PR is applied): {code}
rpm -e rh-eclipse46-devstudio
rpm -i rh-eclipse46-devstudio-1.0-1.el7.noarch.rpm
rpm -q --provides rh-eclipse46-devstudio | tee /tmp/rh-eclipse46-devstudio.provides.list.01
{code} --> [^rh-eclipse46-devstudio.provides.list.01]
Unfortunately even with this change, the RPM is only down to 447M from 460M.
This is because p2 resolves dependencies transitively in the update site mirror used for the RPM, and if devstduio includes org.jboss.tools.openshift.egit.integration.feature, it will depend on egit, and thus pull in that feature to the mirror.
So... we need a way to make the mirror less greedy.
was (Author: nickboldt):
To know what's actually included in the RPM (after this PR is applied): {code}
rpm -e rh-eclipse46-devstudio
rpm -i rh-eclipse46-devstudio-1.0-1.el7.noarch.rpm
rpm -q --provides rh-eclipse46-devstudio | tee /tmp/rh-eclipse46-devstudio.provides.list.01
{code} --> [^rh-eclipse46-devstudio.provides.list.01]
Unfortunately even with this change, the RPM is only down to 447M from 460M.
> Build a new feature that omits features available from RPM install
> ------------------------------------------------------------------
>
> Key: JBDS-3981
> URL: https://issues.jboss.org/browse/JBDS-3981
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: build, updatesite
> Affects Versions: 10.1.0.AM2
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 10.1.0.GA
>
> Attachments: IUs-removed-from-rh-eclipse46-devstudio.rpm.txt, rh-eclipse46-devstudio.provides.list.01, simpler_install_foorprint_rh-eclipse46-devstudio.rpm.png, simpler_install_foorprint_rh-eclipse46-devstudio.rpm_2.png, simpler_install_foorprint_rh-eclipse46-devstudio.rpm_3.png
>
>
> What we DO need is a feature with fewer dependencies than com.jboss.devstudio.core.feature (eg., which omits pde, emf, xsd, egit...)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBDS-3981) Build a new feature that omits features available from RPM install
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3981?page=com.atlassian.jira.plugin.... ]
Nick Boldt edited comment on JBDS-3981 at 8/24/16 4:23 PM:
-----------------------------------------------------------
To know what's actually included in the RPM (after this PR is applied): {code}
rpm -e rh-eclipse46-devstudio
rpm -i rh-eclipse46-devstudio-1.0-1.el7.noarch.rpm
rpm -q --provides rh-eclipse46-devstudio | tee /tmp/rh-eclipse46-devstudio.provides.list.01
{code} --> [^rh-eclipse46-devstudio.provides.list.01]
Unfortunately even with this change, the RPM is only down to 447M from 460M.
was (Author: nickboldt):
To know what's actually included in the RPM (after this PR is applied): {code}
rpm -e rh-eclipse46-devstudio
rpm -i rh-eclipse46-devstudio-1.0-1.el7.noarch.rpm
rpm -q --provides rh-eclipse46-devstudio | tee /tmp/rh-eclipse46-devstudio.provides.list.01
{code} --> rh-eclipse46-devstudio.provides.list.01
> Build a new feature that omits features available from RPM install
> ------------------------------------------------------------------
>
> Key: JBDS-3981
> URL: https://issues.jboss.org/browse/JBDS-3981
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: build, updatesite
> Affects Versions: 10.1.0.AM2
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 10.1.0.GA
>
> Attachments: IUs-removed-from-rh-eclipse46-devstudio.rpm.txt, rh-eclipse46-devstudio.provides.list.01, simpler_install_foorprint_rh-eclipse46-devstudio.rpm.png, simpler_install_foorprint_rh-eclipse46-devstudio.rpm_2.png, simpler_install_foorprint_rh-eclipse46-devstudio.rpm_3.png
>
>
> What we DO need is a feature with fewer dependencies than com.jboss.devstudio.core.feature (eg., which omits pde, emf, xsd, egit...)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBDS-3981) Build a new feature that omits features available from RPM install
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3981?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-3981:
-----------------------------
Attachment: rh-eclipse46-devstudio.provides.list.01
To know what's actually included in the RPM (after this PR is applied): {code}
rpm -e rh-eclipse46-devstudio
rpm -i rh-eclipse46-devstudio-1.0-1.el7.noarch.rpm
rpm -q --provides rh-eclipse46-devstudio | tee /tmp/rh-eclipse46-devstudio.provides.list.01
{code} --> rh-eclipse46-devstudio.provides.list.01
> Build a new feature that omits features available from RPM install
> ------------------------------------------------------------------
>
> Key: JBDS-3981
> URL: https://issues.jboss.org/browse/JBDS-3981
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: build, updatesite
> Affects Versions: 10.1.0.AM2
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 10.1.0.GA
>
> Attachments: IUs-removed-from-rh-eclipse46-devstudio.rpm.txt, rh-eclipse46-devstudio.provides.list.01, simpler_install_foorprint_rh-eclipse46-devstudio.rpm.png, simpler_install_foorprint_rh-eclipse46-devstudio.rpm_2.png, simpler_install_foorprint_rh-eclipse46-devstudio.rpm_3.png
>
>
> What we DO need is a feature with fewer dependencies than com.jboss.devstudio.core.feature (eg., which omits pde, emf, xsd, egit...)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBDS-3981) Build a new feature that omits features available from RPM install
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3981?page=com.atlassian.jira.plugin.... ]
Nick Boldt edited comment on JBDS-3981 at 8/24/16 4:14 PM:
-----------------------------------------------------------
With the PR applied, many IUs are removed from the rpm installation: [^IUs-removed-from-rh-eclipse46-devstudio.rpm.txt]
Here's how I deduced which IUs could be removed from the RPM:
{code}
# to remove requirements which are available in an rpm, do this:
for iu in $(cat ../com.jboss.devstudio.core.rpm.feature/feature.xml | grep import \
| sed "s#<import \(feature\|plugin\)=\"\([^\"]\+\)\".\+#\2#"); do
rpm -q \-\-provides $(rpm -q \-\-requires rh-eclipse46-base | grep -v rpmlib | sed "s#\(rh-[^=]\+\).*#\1#") \
| sort | uniq | grep osgi | grep $iu; done
# if nothing reported, no dupes!
# if output, move those features to the rpmdeps.feature.{code}
was (Author: nickboldt):
With the PR applied, many IUs are removed from the rpm installation: [^IUs-removed-from-rh-eclipse46-devstudio.rpm.txt]
> Build a new feature that omits features available from RPM install
> ------------------------------------------------------------------
>
> Key: JBDS-3981
> URL: https://issues.jboss.org/browse/JBDS-3981
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: build, updatesite
> Affects Versions: 10.1.0.AM2
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 10.1.0.GA
>
> Attachments: IUs-removed-from-rh-eclipse46-devstudio.rpm.txt, simpler_install_foorprint_rh-eclipse46-devstudio.rpm.png, simpler_install_foorprint_rh-eclipse46-devstudio.rpm_2.png, simpler_install_foorprint_rh-eclipse46-devstudio.rpm_3.png
>
>
> What we DO need is a feature with fewer dependencies than com.jboss.devstudio.core.feature (eg., which omits pde, emf, xsd, egit...)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBDS-3981) Build a new feature that omits features available from RPM install
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3981?page=com.atlassian.jira.plugin.... ]
Nick Boldt edited comment on JBDS-3981 at 8/24/16 4:14 PM:
-----------------------------------------------------------
With the PR applied, many IUs are removed from the rpm installation: [^IUs-removed-from-rh-eclipse46-devstudio.rpm.txt]
Here's how I deduced which IUs could be removed from the RPM:
{code}
# to remove requirements which are available in an rpm, do this:
for iu in $(cat ../com.jboss.devstudio.core.rpm.feature/feature.xml | grep import \
| sed "s#<import \(feature\|plugin\)=\"\([^\"]\+\)\".\+#\2#"); do
rpm -q \-\-provides $(rpm -q \-\-requires rh-eclipse46-base | grep -v rpmlib | sed "s#\(rh-[^=]\+\).*#\1#") \
| sort | uniq | grep osgi | grep $iu; done
# if nothing reported, no dupes!
# if output, move those features to the rpmdeps.feature.{code}
was (Author: nickboldt):
With the PR applied, many IUs are removed from the rpm installation: [^IUs-removed-from-rh-eclipse46-devstudio.rpm.txt]
Here's how I deduced which IUs could be removed from the RPM:
{code}
# to remove requirements which are available in an rpm, do this:
for iu in $(cat ../com.jboss.devstudio.core.rpm.feature/feature.xml | grep import \
| sed "s#<import \(feature\|plugin\)=\"\([^\"]\+\)\".\+#\2#"); do
rpm -q \-\-provides $(rpm -q \-\-requires rh-eclipse46-base | grep -v rpmlib | sed "s#\(rh-[^=]\+\).*#\1#") \
| sort | uniq | grep osgi | grep $iu; done
# if nothing reported, no dupes!
# if output, move those features to the rpmdeps.feature.{code}
> Build a new feature that omits features available from RPM install
> ------------------------------------------------------------------
>
> Key: JBDS-3981
> URL: https://issues.jboss.org/browse/JBDS-3981
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: build, updatesite
> Affects Versions: 10.1.0.AM2
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 10.1.0.GA
>
> Attachments: IUs-removed-from-rh-eclipse46-devstudio.rpm.txt, simpler_install_foorprint_rh-eclipse46-devstudio.rpm.png, simpler_install_foorprint_rh-eclipse46-devstudio.rpm_2.png, simpler_install_foorprint_rh-eclipse46-devstudio.rpm_3.png
>
>
> What we DO need is a feature with fewer dependencies than com.jboss.devstudio.core.feature (eg., which omits pde, emf, xsd, egit...)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months