[JBoss JIRA] (JBDS-4018) Integrate m2e-wtp 1.2.2 version in Mars Target Platform
by Aurélien Pupier (JIRA)
Aurélien Pupier created JBDS-4018:
-------------------------------------
Summary: Integrate m2e-wtp 1.2.2 version in Mars Target Platform
Key: JBDS-4018
URL: https://issues.jboss.org/browse/JBDS-4018
Project: Red Hat JBoss Developer Studio (devstudio)
Issue Type: Feature Request
Reporter: Aurélien Pupier
I create the gerrit change with the fix
[~fbricon] will merge and create the release at the end of the week or at the beginning of the next one.
Please notice that it is for the Mars TP (not the Neon one)
--
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/25/16 12:45 PM:
------------------------------------------------------------
Build successful on wonka, after some fancy footwork to get eclipse installed.
http://wonka.mw.lab.eng.bos.redhat.com/RHDS/10.0/snapshots/builds/2016082...
Note that this version is 460M and includes lots of extra IUs, as it was built from a different version of the git sources. You can use it to compare with the 301M version and verify that the removal of those 160M of duplicate IUs is safe.
was (Author: nickboldt):
Build successful on wonka, after some fancy footwork to get eclipse installed.
http://wonka.mw.lab.eng.bos.redhat.com/RHDS/10.0/snapshots/builds/2016082...
Note that this version is 460M and includes lots of extra IUs, as it was built from a different version of the git sources.
> 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, IUs-removed-from-rh-eclipse46-devstudio.rpm_more.txt, rh-eclipse46-devstudio.provides.list.01, rh-eclipse46-devstudio.provides.list.02, 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/25/16 12:45 PM:
------------------------------------------------------------
Further removed IUs: [^IUs-removed-from-rh-eclipse46-devstudio.rpm_more.txt]
Result is an even smaller list of provided IUs: [^rh-eclipse46-devstudio.provides.list.02]
And now the mirror is only 480M, with the rpm compressed down to 301M.
Seems good enough to start doing more install/usage testing.
So, here's a taste of what the RPM looks like:
http://www.qa.jboss.com/binaries/RHDS/10.0/snapshots/builds/devstudio.rpm...
Now I need a place to build it other than my own machine :D
was (Author: nickboldt):
Further removed IUs: [^IUs-removed-from-rh-eclipse46-devstudio.rpm_more.txt]
Result is an even smaller list of provided IUs: [^rh-eclipse46-devstudio.provides.list.02]
And now the mirror is only 480M, with the rpm compressed down to 302M.
Seems good enough to start doing more install/usage testing.
So, here's a taste of what the RPM looks like:
http://www.qa.jboss.com/binaries/RHDS/10.0/snapshots/builds/devstudio.rpm...
Now I need a place to build it other than my own machine :D
> 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, IUs-removed-from-rh-eclipse46-devstudio.rpm_more.txt, rh-eclipse46-devstudio.provides.list.01, rh-eclipse46-devstudio.provides.list.02, 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/25/16 12:44 PM:
------------------------------------------------------------
Build successful on wonka, after some fancy footwork to get eclipse installed.
http://wonka.mw.lab.eng.bos.redhat.com/RHDS/10.0/snapshots/builds/2016082...
Note that this version is 460M and includes lots of extra IUs, as it was built from a different version of the git sources.
was (Author: nickboldt):
Build successful on wonka, after some fancy footwork to get eclipse installed.
http://wonka.mw.lab.eng.bos.redhat.com/RHDS/10.0/snapshots/builds/2016082...
> 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, IUs-removed-from-rh-eclipse46-devstudio.rpm_more.txt, rh-eclipse46-devstudio.provides.list.01, rh-eclipse46-devstudio.provides.list.02, 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] (JBIDE-23039) Need an interactive terminal that fits specific requirements
by Roland Grunberg (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23039?page=com.atlassian.jira.plugi... ]
Roland Grunberg edited comment on JBIDE-23039 at 8/25/16 12:40 PM:
-------------------------------------------------------------------
Am I right in assuming that for the terminal.tm viewer, you are using a "org.eclipse.tm.terminal.connector.process.launcher.process". This would be the one where you're providing the path of the command along with arguments through the properties. In this case, yes I don't immediately see a way of getting the Process.
However, you could try using a "org.eclipse.tm.terminal.connector.streams.launcher.streams" delegate. This is what the Eclipse Docker Tooling does. In our case we don't want to launch some command, we just want to take care of that ourselves, and just pass a input/output streams to the terminal service.
So you would :
1) Launch the process however you like (eg. Runtime.getRuntime().exec(..), which gives you (1), access to the IProcess/Process, and (2), a way to check when it has terminated.
2) Pass the output/input streams from the Process as properties to the "org.eclipse.tm.terminal.connector.streams.launcher.streams" delegate. I believe they are ITerminalsConnectorConstants.PROP_STREAMS_STDIN, and ITerminalsConnectorConstants.PROP_STREAMS_STDOUT. Have a look at http://git.eclipse.org/c/linuxtools/org.eclipse.linuxtools.git/tree/conta... .
was (Author: rgrunber):
Am I right in assuming that for the terminal.tm viewer, you are using a "org.eclipse.tm.terminal.connector.process.launcher.process". This would be the one where you're providing the path of the command along with arguments through the properties. In this case, yes I don't immediately see a way of getting the Process.
However, you could try using a "org.eclipse.tm.terminal.connector.streams.launcher.streams" delegate. This is what the Eclipse Docker Tooling does. In our case we don't want to launch some command, we just want to take care of that ourselves, and just pass a input/output streams to the terminal service.
So you would :
1) Launch the process however you like (eg. Runtime.getRuntime().exec(..), which gives you (1), access to the IProcess/Process, and (2), a way to check when it has terminated.
2) Pass the output/input streams from the Process as properties to the "org.eclipse.tm.terminal.connector.streams.launcher.streams" delegate as properties. I believe they are ITerminalsConnectorConstants.PROP_STREAMS_STDIN, and ITerminalsConnectorConstants.PROP_STREAMS_STDOUT. Have a look at http://git.eclipse.org/c/linuxtools/org.eclipse.linuxtools.git/tree/conta... .
> 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-23039) Need an interactive terminal that fits specific requirements
by Roland Grunberg (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23039?page=com.atlassian.jira.plugi... ]
Roland Grunberg commented on JBIDE-23039:
-----------------------------------------
Am I right in assuming that for the terminal.tm viewer, you are using a "org.eclipse.tm.terminal.connector.process.launcher.process". This would be the one where you're providing the path of the command along with arguments through the properties. In this case, yes I don't immediately see a way of getting the Process.
However, you could try using a "org.eclipse.tm.terminal.connector.streams.launcher.streams" delegate. This is what the Eclipse Docker Tooling does. In our case we don't want to launch some command, we just want to take care of that ourselves, and just pass a input/output streams to the terminal service.
So you would :
1) Launch the process however you like (eg. Runtime.getRuntime().exec(..), which gives you (1), access to the IProcess/Process, and (2), a way to check when it has terminated.
2) Pass the output/input streams from the Process as properties to the "org.eclipse.tm.terminal.connector.streams.launcher.streams" delegate as properties. I believe they are ITerminalsConnectorConstants.PROP_STREAMS_STDIN, and ITerminalsConnectorConstants.PROP_STREAMS_STDOUT. Have a look at http://git.eclipse.org/c/linuxtools/org.eclipse.linuxtools.git/tree/conta... .
> 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-23043) Not working connection to CDK Docker deamon
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23043?page=com.atlassian.jira.plugi... ]
Nick Boldt reassigned JBIDE-23043:
----------------------------------
Assignee: Jeff Johnston (was: Nick Boldt)
> Not working connection to CDK Docker deamon
> -------------------------------------------
>
> Key: JBIDE-23043
> URL: https://issues.jboss.org/browse/JBIDE-23043
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk, docker, target-platform
> Affects Versions: 4.4.1.Final
> Environment: F24,
> Devstudio:
> Version: 10.1.0.GA
> Build id: GA-v20160825-0621-B5857
> Build date: 20160825-0621
> Docker Tooling:
> 2.1.0.20160825102
> Reporter: Josef Kopriva
> Assignee: Jeff Johnston
> Priority: Blocker
> Fix For: 4.4.1.Final
>
> Attachments: RC1vs0825N.txt, RC1vs0825N_sorted.txt
>
>
> After upgrading Docker Tooling to latest nightly, I cannot create connection to the Docker CDK deamon through TCP connection with certificates.
> Stacktrace:
> {code:java}
> An internal error occurred during: "Opening connection...".
> java.lang.NoClassDefFoundError: org/bouncycastle/openssl/PEMParser
> at com.spotify.docker.client.DockerCertificates.<init>(DockerCertificates.java:80)
> at com.spotify.docker.client.DockerCertificates.<init>(DockerCertificates.java:64)
> at org.eclipse.linuxtools.internal.docker.core.DockerClientFactory.getClient(DockerClientFactory.java:83)
> at org.eclipse.linuxtools.internal.docker.core.DockerClientFactory.getClient(DockerClientFactory.java:47)
> at org.eclipse.linuxtools.internal.docker.core.DockerConnection.open(DockerConnection.java:252)
> at org.eclipse.linuxtools.internal.docker.ui.views.DockerExplorerContentProvider$1.run(DockerExplorerContentProvider.java:179)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBIDE-23043) Not working connection to CDK Docker deamon
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23043?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-23043:
-------------------------------
Attachment: RC1vs0825N_sorted.txt
RC1vs0825N.txt
Change is obvious if you use p2diff [0] to check the sites.
{code}p2diff http://download.eclipse.org/linuxtools/update-neon-1-docker-rc1/ http://download.eclipse.org/linuxtools/updates-docker-nightly/ | tee RC1vs0825N.txt{code} -- [^RC1vs0825N.txt]
{code}
cat RC1vs0825N.txt | egrep "^(<|>) " | sed -e "s/\(<\|>\) \(.\+\)/\2\1/" | sort | sed -e "s/\(.\+\) \(<\|>\)/\2 \1/" | egrep "^(<|>)" | tee RC1vs0825N_sorted.txt
{code} -- [^RC1vs0825N_sorted.txt]
[0] https://github.com/irbull/p2diff
> Not working connection to CDK Docker deamon
> -------------------------------------------
>
> Key: JBIDE-23043
> URL: https://issues.jboss.org/browse/JBIDE-23043
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk, docker, target-platform
> Affects Versions: 4.4.1.Final
> Environment: F24,
> Devstudio:
> Version: 10.1.0.GA
> Build id: GA-v20160825-0621-B5857
> Build date: 20160825-0621
> Docker Tooling:
> 2.1.0.20160825102
> Reporter: Josef Kopriva
> Assignee: Nick Boldt
> Priority: Blocker
> Fix For: 4.4.1.Final
>
> Attachments: RC1vs0825N.txt, RC1vs0825N_sorted.txt
>
>
> After upgrading Docker Tooling to latest nightly, I cannot create connection to the Docker CDK deamon through TCP connection with certificates.
> Stacktrace:
> {code:java}
> An internal error occurred during: "Opening connection...".
> java.lang.NoClassDefFoundError: org/bouncycastle/openssl/PEMParser
> at com.spotify.docker.client.DockerCertificates.<init>(DockerCertificates.java:80)
> at com.spotify.docker.client.DockerCertificates.<init>(DockerCertificates.java:64)
> at org.eclipse.linuxtools.internal.docker.core.DockerClientFactory.getClient(DockerClientFactory.java:83)
> at org.eclipse.linuxtools.internal.docker.core.DockerClientFactory.getClient(DockerClientFactory.java:47)
> at org.eclipse.linuxtools.internal.docker.core.DockerConnection.open(DockerConnection.java:252)
> at org.eclipse.linuxtools.internal.docker.ui.views.DockerExplorerContentProvider$1.run(DockerExplorerContentProvider.java:179)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months