[JBoss JIRA] (JBIDE-24783) Update default registry url for cdk 3
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24783?page=com.atlassian.jira.plugi... ]
Martin Malina edited comment on JBIDE-24783 at 8/1/17 4:51 AM:
---------------------------------------------------------------
Once I deleted the VM and started cdk 3 again, the value was set to:
https://172.30.1.1:5000
And, as expected, the command works now:
{code}
$ ./minishift openshift registry
172.30.1.1:5000
{code}
was (Author: mmalina):
Once I deleted the VM and started cdk 3 again, the value was set to:
https://172.30.1.1:5000
> Update default registry url for cdk 3
> -------------------------------------
>
> Key: JBIDE-24783
> URL: https://issues.jboss.org/browse/JBIDE-24783
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: cdk, openshift
> Affects Versions: 4.5.0.AM2
> Reporter: Martin Malina
>
> Yesterday I started cdk 3 and it seemed to start ok, but was not really ok.
> The registry command didn't really work:
> {code}
> $ ./minishift openshift registry
> No information found for 'service/docker-registry'
> {code}
> The result is that the openshift connection details showed this under Image Registry URL:
> https://hub.openshift.rhel-cdk.10.1.2.2.xip.io
> This seems like the default value for cdk 3. I think we should update the default value for cdk 3. Or is this simply a default value for an openshift connection? In any case, this should use the cdk 3 value.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
6 years, 9 months
[JBoss JIRA] (JBIDE-24783) Update default registry url for cdk 3
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24783?page=com.atlassian.jira.plugi... ]
Martin Malina commented on JBIDE-24783:
---------------------------------------
Once I deleted the VM and started cdk 3 again, the value was set to:
https://172.30.1.1:5000
> Update default registry url for cdk 3
> -------------------------------------
>
> Key: JBIDE-24783
> URL: https://issues.jboss.org/browse/JBIDE-24783
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: cdk, openshift
> Affects Versions: 4.5.0.AM2
> Reporter: Martin Malina
>
> Yesterday I started cdk 3 and it seemed to start ok, but was not really ok.
> The registry command didn't really work:
> {code}
> $ ./minishift openshift registry
> No information found for 'service/docker-registry'
> {code}
> The result is that the openshift connection details showed this under Image Registry URL:
> https://hub.openshift.rhel-cdk.10.1.2.2.xip.io
> This seems like the default value for cdk 3. I think we should update the default value for cdk 3. Or is this simply a default value for an openshift connection? In any case, this should use the cdk 3 value.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
6 years, 9 months
[JBoss JIRA] (JBTIS-1087) Move all system properties to the variable 'systemProperties'
by Andrej Podhradsky (JIRA)
[ https://issues.jboss.org/browse/JBTIS-1087?page=com.atlassian.jira.plugin... ]
Andrej Podhradsky closed JBTIS-1087.
------------------------------------
Pushed to master
> Move all system properties to the variable 'systemProperties'
> -------------------------------------------------------------
>
> Key: JBTIS-1087
> URL: https://issues.jboss.org/browse/JBTIS-1087
> Project: JBoss Tools Integration Stack
> Issue Type: Task
> Components: Fuse IDE, QE
> Affects Versions: 4.4.3.Final
> Reporter: Andrej Podhradsky
> Assignee: Tomáš Sedmík
> Fix For: 4.5.0.Final
>
>
> The following system proeprties properties
> {code}
> <groupId>org.eclipse.tycho</groupId>
> <artifactId>tycho-surefire-plugin</artifactId>
> <configuration>
> ....
> <systemProperties>
> <logDebug>${enable.debug.log}</logDebug>
> <maven.settings>${project.build.directory}/requirements/emptysettings.xml</maven.settings>
> <maven.repository>${maven.repo}</maven.repository>
> <staging.repositories>${staging.repos}</staging.repositories>
> <rd.skipUnfixedIssues>${rd.skipUnfixedIssues}</rd.skipUnfixedIssues>
> </systemProperties>
> ....
> {code}
> should be moved to the variable 'systemProperties' or 'integrationTestsSystemProperties'.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
6 years, 9 months
[JBoss JIRA] (JBIDE-24783) Update default registry url for cdk 3
by Martin Malina (JIRA)
Martin Malina created JBIDE-24783:
-------------------------------------
Summary: Update default registry url for cdk 3
Key: JBIDE-24783
URL: https://issues.jboss.org/browse/JBIDE-24783
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: cdk, openshift
Affects Versions: 4.5.0.AM2
Reporter: Martin Malina
Yesterday I started cdk 3 and it seemed to start ok, but was not really ok.
The registry command didn't really work:
{code}
$ ./minishift openshift registry
No information found for 'service/docker-registry'
{code}
The result is that the openshift connection details showed this under Image Registry URL:
https://hub.openshift.rhel-cdk.10.1.2.2.xip.io
This seems like the default value for cdk 3. I think we should update the default value for cdk 3. Or is this simply a default value for an openshift connection? In any case, this should use the cdk 3 value.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
6 years, 9 months
[JBoss JIRA] (JBIDE-24534) Aeri connection problems on startup of devstudio / lucene issue?
by Lukáš Valach (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24534?page=com.atlassian.jira.plugi... ]
Lukáš Valach closed JBIDE-24534.
--------------------------------
I confirm that this error is not longer in the log. Tested with last stable Eclipse EE (eclipse-jee-oxygen-R-linux-gtk-x86_64) and last Devstudio snapshot (11.0.0.GA).
Closing.
> Aeri connection problems on startup of devstudio / lucene issue?
> ----------------------------------------------------------------
>
> Key: JBIDE-24534
> URL: https://issues.jboss.org/browse/JBIDE-24534
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: aeri, central-update
> Affects Versions: 4.5.0.AM1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.5.0.Final
>
>
> Having installed devstudio 11.0.0.AM1 into Oxygen.0.M7 JavaEE EPP bundle on Linux x64 (Fedora 24), I tried to install something from Central and instead got an AERI error:
> {code}
> !ENTRY org.eclipse.epp.logging.aeri.ide 2 17 2017-06-02 15:15:10.111
> !MESSAGE Server 'org.jboss.tools' failed with exception: Connect to tools.jboss.org:443 [tools.jboss.org/10.4.129.28] failed: connect timed out. ; version: 2.0.5.v20170531-0951
> !STACK 0
> org.apache.http.conn.ConnectTimeoutException: Connect to tools.jboss.org:443 [tools.jboss.org/10.4.129.28] failed: connect timed out
> at org.apache.http.impl.conn.DefaultHttpClientConnectionOperator.connect(DefaultHttpClientConnectionOperator.java:150)
> at org.apache.http.impl.conn.PoolingHttpClientConnectionManager.connect(PoolingHttpClientConnectionManager.java:353)
> at org.apache.http.impl.execchain.MainClientExec.establishRoute(MainClientExec.java:380)
> at org.apache.http.impl.execchain.MainClientExec.execute(MainClientExec.java:236)
> at org.apache.http.impl.execchain.ProtocolExec.execute(ProtocolExec.java:184)
> at org.apache.http.impl.execchain.RetryExec.execute(RetryExec.java:88)
> at org.apache.http.impl.execchain.RedirectExec.execute(RedirectExec.java:110)
> at org.apache.http.impl.client.InternalHttpClient.doExecute(InternalHttpClient.java:184)
> at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:82)
> at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:55)
> at org.apache.http.client.fluent.Request.internalExecute(Request.java:173)
> at org.apache.http.client.fluent.Executor.execute(Executor.java:262)
> at org.eclipse.epp.internal.logging.aeri.ide.server.mars.IO.request(IO.java:170)
> at org.eclipse.epp.internal.logging.aeri.ide.server.mars.IO.refreshConfiguration(IO.java:64)
> at org.eclipse.epp.internal.logging.aeri.ide.server.mars.ServerConnection.startUp(ServerConnection.java:124)
> at com.google.common.util.concurrent.AbstractIdleService$2$1.run(AbstractIdleService.java:54)
> at com.google.common.util.concurrent.Callables$3.run(Callables.java:93)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: java.net.SocketTimeoutException: connect timed out
> at java.net.PlainSocketImpl.socketConnect(Native Method)
> at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350)
> at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206)
> at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188)
> at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
> at java.net.Socket.connect(Socket.java:589)
> at org.apache.http.conn.ssl.SSLConnectionSocketFactory.connectSocket(SSLConnectionSocketFactory.java:337)
> at org.apache.http.impl.conn.DefaultHttpClientConnectionOperator.connect(DefaultHttpClientConnectionOperator.java:141)
> ... 17 more
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
6 years, 9 months
[JBoss JIRA] (JBDS-4176) Useless-provides detected by RPMlint
by Lukáš Valach (JIRA)
[ https://issues.jboss.org/browse/JBDS-4176?page=com.atlassian.jira.plugin.... ]
Lukáš Valach commented on JBDS-4176:
------------------------------------
That is a good point Nick, we can close this jira.
There is result of rpmlint test \[1\].
\[1\] https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud...
Log snippet:
{code}
rpmlint -f ./rpmlint.conf ./rh-eclipse47-devstudio-11.0-0.20170801.0458.el7.x86_64.rpm
00:06:52.975 1 packages and 0 specfiles checked; 0 errors, 0 warnings.
{code}
There is [^rpmlint.conf].
If you would like to see output without filters see \[2\].
\[2\] https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud...
These isn't any useless-provides, so I am closing this jira.
> Useless-provides detected by RPMlint
> ------------------------------------
>
> Key: JBDS-4176
> URL: https://issues.jboss.org/browse/JBDS-4176
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: rpm
> Affects Versions: 10.2.0.AM3
> Environment: RHEL7
> Reporter: Lukáš Valach
> Assignee: Lukáš Valach
> Priority: Optional
> Fix For: 11.0.0.GA
>
> Attachments: opt-rh-list.2.txt, opt-rh-list.2.txt.sh, opt-rh-list.txt, opt-rh-list.txt.sh, rpmlint.conf
>
>
> The rpmlint detects some problems in rpm package:
> {code}
> rpmlint -f ./rpmlint.conf ./rh-eclipse46-devstudio-10.2-0.20161111.1151.el7.x86_64.rpm
> rh-eclipse46-devstudio.x86_64: E: useless-provides rh-eclipse46-osgi(com.google.guava)
> rh-eclipse46-devstudio.x86_64: E: useless-provides rh-eclipse46-osgi(com.google.inject)
> rh-eclipse46-devstudio.x86_64: E: useless-provides rh-eclipse46-osgi(javax.wsdl)
> rh-eclipse46-devstudio.x86_64: E: useless-provides rh-eclipse46-osgi(org.apache.commons.collections)
> rh-eclipse46-devstudio.x86_64: E: useless-provides rh-eclipse46-osgi(org.apache.commons.io)
> rh-eclipse46-devstudio.x86_64: E: useless-provides rh-eclipse46-osgi(org.apache.commons.lang3)
> rh-eclipse46-devstudio.x86_64: E: useless-provides rh-eclipse46-osgi(org.apache.commons.logging)
> rh-eclipse46-devstudio.x86_64: E: useless-provides rh-eclipse46-osgi(org.eclipse.aether.api)
> rh-eclipse46-devstudio.x86_64: E: useless-provides rh-eclipse46-osgi(org.eclipse.aether.connector.basic)
> rh-eclipse46-devstudio.x86_64: E: useless-provides rh-eclipse46-osgi(org.eclipse.aether.impl)
> rh-eclipse46-devstudio.x86_64: E: useless-provides rh-eclipse46-osgi(org.eclipse.aether.spi)
> rh-eclipse46-devstudio.x86_64: E: useless-provides rh-eclipse46-osgi(org.eclipse.aether.util)
> rh-eclipse46-devstudio.x86_64: E: useless-provides rh-eclipse46-osgi(com.fasterxml.classmate)
> rh-eclipse46-devstudio.x86_64: E: useless-provides rh-eclipse46-osgi(org.jboss.logging.jboss-logging)
> rh-eclipse46-devstudio.x86_64: E: useless-provides rh-eclipse46-osgi(org.yaml.snakeyaml)
> rh-eclipse46-devstudio.x86_64: E: useless-provides rh-eclipse46-osgi(slf4j.api)
> rh-eclipse46-devstudio.x86_64: E: useless-provides rh-eclipse46-osgi(org.objectweb.asm)
> 1 packages and 0 specfiles checked; 17 errors, 0 warnings.
> {code}
> There are only important problems in the list above, another errors/warnings were suppressed according to discussion with [~vkadlcik].
> There is configuration of rpmlint filter (rpmlint.conf):
> {code}
> addFilter("W: ") # Warnings can be suppressed
> addFilter("E: dir-or-file-in-opt") # False positive
> addFilter("E: devel-dependency") # False positive
> addFilter("E: explicit-lib-dependency") # May be improved but is not important for now
> addFilter("E: non-executable-script") # 99% of these errors are false positive comming from upstream, there is a very small chance to get relevant error
> addFilter("E: wrong-script-interpreter") # The same as above
> addFilter("E: zero-length") # The same as above
> {code}
> [~vkadlcik] please correct me if I'm wrong.
> RPMlint test has been automated, you can find it in [jenkins|https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view...]
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
6 years, 9 months
[JBoss JIRA] (JBDS-4176) Useless-provides detected by RPMlint
by Lukáš Valach (JIRA)
[ https://issues.jboss.org/browse/JBDS-4176?page=com.atlassian.jira.plugin.... ]
Lukáš Valach closed JBDS-4176.
------------------------------
Resolution: Done
> Useless-provides detected by RPMlint
> ------------------------------------
>
> Key: JBDS-4176
> URL: https://issues.jboss.org/browse/JBDS-4176
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: rpm
> Affects Versions: 10.2.0.AM3
> Environment: RHEL7
> Reporter: Lukáš Valach
> Assignee: Lukáš Valach
> Priority: Optional
> Fix For: 11.0.0.GA
>
> Attachments: opt-rh-list.2.txt, opt-rh-list.2.txt.sh, opt-rh-list.txt, opt-rh-list.txt.sh, rpmlint.conf
>
>
> The rpmlint detects some problems in rpm package:
> {code}
> rpmlint -f ./rpmlint.conf ./rh-eclipse46-devstudio-10.2-0.20161111.1151.el7.x86_64.rpm
> rh-eclipse46-devstudio.x86_64: E: useless-provides rh-eclipse46-osgi(com.google.guava)
> rh-eclipse46-devstudio.x86_64: E: useless-provides rh-eclipse46-osgi(com.google.inject)
> rh-eclipse46-devstudio.x86_64: E: useless-provides rh-eclipse46-osgi(javax.wsdl)
> rh-eclipse46-devstudio.x86_64: E: useless-provides rh-eclipse46-osgi(org.apache.commons.collections)
> rh-eclipse46-devstudio.x86_64: E: useless-provides rh-eclipse46-osgi(org.apache.commons.io)
> rh-eclipse46-devstudio.x86_64: E: useless-provides rh-eclipse46-osgi(org.apache.commons.lang3)
> rh-eclipse46-devstudio.x86_64: E: useless-provides rh-eclipse46-osgi(org.apache.commons.logging)
> rh-eclipse46-devstudio.x86_64: E: useless-provides rh-eclipse46-osgi(org.eclipse.aether.api)
> rh-eclipse46-devstudio.x86_64: E: useless-provides rh-eclipse46-osgi(org.eclipse.aether.connector.basic)
> rh-eclipse46-devstudio.x86_64: E: useless-provides rh-eclipse46-osgi(org.eclipse.aether.impl)
> rh-eclipse46-devstudio.x86_64: E: useless-provides rh-eclipse46-osgi(org.eclipse.aether.spi)
> rh-eclipse46-devstudio.x86_64: E: useless-provides rh-eclipse46-osgi(org.eclipse.aether.util)
> rh-eclipse46-devstudio.x86_64: E: useless-provides rh-eclipse46-osgi(com.fasterxml.classmate)
> rh-eclipse46-devstudio.x86_64: E: useless-provides rh-eclipse46-osgi(org.jboss.logging.jboss-logging)
> rh-eclipse46-devstudio.x86_64: E: useless-provides rh-eclipse46-osgi(org.yaml.snakeyaml)
> rh-eclipse46-devstudio.x86_64: E: useless-provides rh-eclipse46-osgi(slf4j.api)
> rh-eclipse46-devstudio.x86_64: E: useless-provides rh-eclipse46-osgi(org.objectweb.asm)
> 1 packages and 0 specfiles checked; 17 errors, 0 warnings.
> {code}
> There are only important problems in the list above, another errors/warnings were suppressed according to discussion with [~vkadlcik].
> There is configuration of rpmlint filter (rpmlint.conf):
> {code}
> addFilter("W: ") # Warnings can be suppressed
> addFilter("E: dir-or-file-in-opt") # False positive
> addFilter("E: devel-dependency") # False positive
> addFilter("E: explicit-lib-dependency") # May be improved but is not important for now
> addFilter("E: non-executable-script") # 99% of these errors are false positive comming from upstream, there is a very small chance to get relevant error
> addFilter("E: wrong-script-interpreter") # The same as above
> addFilter("E: zero-length") # The same as above
> {code}
> [~vkadlcik] please correct me if I'm wrong.
> RPMlint test has been automated, you can find it in [jenkins|https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view...]
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
6 years, 9 months