[JBoss JIRA] (JBDS-4432) Test optimization and enhancements
by Jan Richter (JIRA)
Jan Richter created JBDS-4432:
---------------------------------
Summary: Test optimization and enhancements
Key: JBDS-4432
URL: https://issues.jboss.org/browse/JBDS-4432
Project: Red Hat JBoss Developer Studio (devstudio)
Issue Type: Task
Components: platform-installer
Affects Versions: 11.0.0.AM1
Reporter: Jan Richter
Assignee: Jan Richter
Fix For: 11.0.0.AM1
See subtasks for details
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (ERT-513) App does not run in iOS simulator with ios cordova 4.3.1 [EBZ#517918]
by Friendly Jira Robot (JIRA)
Friendly Jira Robot created ERT-513:
---------------------------------------
Summary: App does not run in iOS simulator with ios cordova 4.3.1 [EBZ#517918]
Key: ERT-513
URL: https://issues.jboss.org/browse/ERT-513
Project: Eclipse Release Train
Issue Type: Task
Components: Thym
Reporter: Friendly Jira Robot
Priority: Critical
Fix For: Neon (4.6)
Created attachment 268781
simulator_system_log.txt
1) Create hybrid application with ios cordova 4.3.1 engine.
2) Run As -> Run on iOS Simulator
The app opens and quits/crashes immediately.
This scenario works fine with lower cordova versions e.g (4.2.0, 4.1.1)
If I open xcodeproject in XCode and run from there it works.
iOS Simulator system log is attached.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (JBIDE-24438) Server adapter: JMX connection is not working for OpenShift instance
by Aurélien Pupier (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24438?page=com.atlassian.jira.plugi... ]
Aurélien Pupier commented on JBIDE-24438:
-----------------------------------------
The open.paas.redhat.com instance is working today...
I provided 2 screencasts:
- one is showing that using the JMX connection from the server adapter is not working
- the other one is showing that just by shrinking off the arbitrary port it is working from a manually defined JMX connection
the default examples inside Fuse Tooling is used in the screencast, see https://www.youtube.com/watch?v=Ko4mNaQsCvI&t=8s&list=PLU-T8l-XOWOPh0z14I... to know how to create and deploy the project
> Server adapter: JMX connection is not working for OpenShift instance
> ---------------------------------------------------------------------
>
> Key: JBIDE-24438
> URL: https://issues.jboss.org/browse/JBIDE-24438
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.4.Final
> Reporter: Aurélien Pupier
> Assignee: Rob Stryker
> Labels: jmx, jolokia, openshift_v3, server_adapter
> Fix For: 4.5.0.AM1
>
> Attachments: JMXForOpenSHiftWithoutPortNotWorking.mp4, ManualJMXConnectionWithoutPortWorking.mp4
>
>
> such as open.paas.redhat.com
> {noformat}
> java.io.IOException: org.jolokia.client.exception.J4pTimeoutException: Read timeout while request https://open.paas.redhat.com:8443/api/v1/namespaces/fis-test/pods/https:c...: Connect to open.paas.redhat.com:8443 [open.paas.redhat.com/10.29.67.214, open.paas.redhat.com/10.29.67.200, open.paas.redhat.com/10.29.67.238] failed: connect timed out
> at org.jboss.tools.jmx.jolokia.JolokiaConnectionWrapper.verifyServerReachable(JolokiaConnectionWrapper.java:324)
> at org.jboss.tools.jmx.jolokia.JolokiaConnectionWrapper.connect(JolokiaConnectionWrapper.java:113)
> at org.jboss.tools.jmx.core.ConnectJob.run(ConnectJob.java:29)
> at org.jboss.tools.jmx.ui.internal.actions.DoubleClickAction$1.run(DoubleClickAction.java:71)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> Caused by: org.jolokia.client.exception.J4pTimeoutException: Read timeout while request https://open.paas.redhat.com:8443/api/v1/namespaces/fis-test/pods/https:c...: Connect to open.paas.redhat.com:8443 [open.paas.redhat.com/10.29.67.214, open.paas.redhat.com/10.29.67.200, open.paas.redhat.com/10.29.67.238] failed: connect timed out
> at org.jolokia.client.J4pClient.mapException(J4pClient.java:330)
> at org.jolokia.client.J4pClient.execute(J4pClient.java:198)
> at org.jolokia.client.J4pClient.execute(J4pClient.java:168)
> at org.jolokia.client.J4pClient.execute(J4pClient.java:117)
> at org.jboss.tools.jmx.jolokia.JolokiaConnectionWrapper.verifyServerReachable(JolokiaConnectionWrapper.java:311)
> ... 4 more
> Caused by: org.apache.http.conn.ConnectTimeoutException: Connect to open.paas.redhat.com:8443 [open.paas.redhat.com/10.29.67.214, open.paas.redhat.com/10.29.67.200, open.paas.redhat.com/10.29.67.238] 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:107)
> at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:55)
> at org.jolokia.client.J4pClient.execute(J4pClient.java:190)
> ... 7 more
> Caused by: java.net.SocketTimeoutException: connect timed out
> at java.net.DualStackPlainSocketImpl.waitForConnect(Native Method)
> at java.net.DualStackPlainSocketImpl.socketConnect(Unknown Source)
> at java.net.AbstractPlainSocketImpl.doConnect(Unknown Source)
> at java.net.AbstractPlainSocketImpl.connectToAddress(Unknown Source)
> at java.net.AbstractPlainSocketImpl.connect(Unknown Source)
> at java.net.PlainSocketImpl.connect(Unknown Source)
> at java.net.SocksSocketImpl.connect(Unknown Source)
> at java.net.Socket.connect(Unknown Source)
> at sun.security.ssl.SSLSocketImpl.connect(Unknown Source)
> at org.apache.http.conn.ssl.SSLConnectionSocketFactory.connectSocket(SSLConnectionSocketFactory.java:337)
> at org.apache.http.impl.conn.DefaultHttpClientConnectionOperator.connect(DefaultHttpClientConnectionOperator.java:141)
> ... 18 more
> {noformat}
> we can notice that the url used is https://open.paas.redhat.com:8443/api/v1/namespaces/fis-test/pods/https:c...
> It should not contain the port 8443
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (JBIDE-24438) Server adapter: JMX connection is not working for OpenShift instance
by Aurélien Pupier (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24438?page=com.atlassian.jira.plugi... ]
Aurélien Pupier updated JBIDE-24438:
------------------------------------
Attachment: ManualJMXConnectionWithoutPortWorking.mp4
JMXForOpenSHiftWithoutPortNotWorking.mp4
> Server adapter: JMX connection is not working for OpenShift instance
> ---------------------------------------------------------------------
>
> Key: JBIDE-24438
> URL: https://issues.jboss.org/browse/JBIDE-24438
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.4.Final
> Reporter: Aurélien Pupier
> Assignee: Rob Stryker
> Labels: jmx, jolokia, openshift_v3, server_adapter
> Fix For: 4.5.0.AM1
>
> Attachments: JMXForOpenSHiftWithoutPortNotWorking.mp4, ManualJMXConnectionWithoutPortWorking.mp4
>
>
> such as open.paas.redhat.com
> {noformat}
> java.io.IOException: org.jolokia.client.exception.J4pTimeoutException: Read timeout while request https://open.paas.redhat.com:8443/api/v1/namespaces/fis-test/pods/https:c...: Connect to open.paas.redhat.com:8443 [open.paas.redhat.com/10.29.67.214, open.paas.redhat.com/10.29.67.200, open.paas.redhat.com/10.29.67.238] failed: connect timed out
> at org.jboss.tools.jmx.jolokia.JolokiaConnectionWrapper.verifyServerReachable(JolokiaConnectionWrapper.java:324)
> at org.jboss.tools.jmx.jolokia.JolokiaConnectionWrapper.connect(JolokiaConnectionWrapper.java:113)
> at org.jboss.tools.jmx.core.ConnectJob.run(ConnectJob.java:29)
> at org.jboss.tools.jmx.ui.internal.actions.DoubleClickAction$1.run(DoubleClickAction.java:71)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> Caused by: org.jolokia.client.exception.J4pTimeoutException: Read timeout while request https://open.paas.redhat.com:8443/api/v1/namespaces/fis-test/pods/https:c...: Connect to open.paas.redhat.com:8443 [open.paas.redhat.com/10.29.67.214, open.paas.redhat.com/10.29.67.200, open.paas.redhat.com/10.29.67.238] failed: connect timed out
> at org.jolokia.client.J4pClient.mapException(J4pClient.java:330)
> at org.jolokia.client.J4pClient.execute(J4pClient.java:198)
> at org.jolokia.client.J4pClient.execute(J4pClient.java:168)
> at org.jolokia.client.J4pClient.execute(J4pClient.java:117)
> at org.jboss.tools.jmx.jolokia.JolokiaConnectionWrapper.verifyServerReachable(JolokiaConnectionWrapper.java:311)
> ... 4 more
> Caused by: org.apache.http.conn.ConnectTimeoutException: Connect to open.paas.redhat.com:8443 [open.paas.redhat.com/10.29.67.214, open.paas.redhat.com/10.29.67.200, open.paas.redhat.com/10.29.67.238] 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:107)
> at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:55)
> at org.jolokia.client.J4pClient.execute(J4pClient.java:190)
> ... 7 more
> Caused by: java.net.SocketTimeoutException: connect timed out
> at java.net.DualStackPlainSocketImpl.waitForConnect(Native Method)
> at java.net.DualStackPlainSocketImpl.socketConnect(Unknown Source)
> at java.net.AbstractPlainSocketImpl.doConnect(Unknown Source)
> at java.net.AbstractPlainSocketImpl.connectToAddress(Unknown Source)
> at java.net.AbstractPlainSocketImpl.connect(Unknown Source)
> at java.net.PlainSocketImpl.connect(Unknown Source)
> at java.net.SocksSocketImpl.connect(Unknown Source)
> at java.net.Socket.connect(Unknown Source)
> at sun.security.ssl.SSLSocketImpl.connect(Unknown Source)
> at org.apache.http.conn.ssl.SSLConnectionSocketFactory.connectSocket(SSLConnectionSocketFactory.java:337)
> at org.apache.http.impl.conn.DefaultHttpClientConnectionOperator.connect(DefaultHttpClientConnectionOperator.java:141)
> ... 18 more
> {noformat}
> we can notice that the url used is https://open.paas.redhat.com:8443/api/v1/namespaces/fis-test/pods/https:c...
> It should not contain the port 8443
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (JBDS-4417) Bundle org.eclipse.wst.jsdt.nashorn.extension not found
by Ilya Buziuk (JIRA)
[ https://issues.jboss.org/browse/JBDS-4417?page=com.atlassian.jira.plugin.... ]
Ilya Buziuk commented on JBDS-4417:
-----------------------------------
[~vrubezhny] As I recall nashorn has been removed from Oxygen in favour of Closure, so I think we should remove the following line from devstudio.ini:
{code}
-Dosgi.framework.extensions=org.eclipse.wst.jsdt.nashorn.extension
{code}
Is this correct ?
> Bundle org.eclipse.wst.jsdt.nashorn.extension not found
> -------------------------------------------------------
>
> Key: JBDS-4417
> URL: https://issues.jboss.org/browse/JBDS-4417
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: build
> Affects Versions: 11.0.0.AM1
> Environment: Devstudio installed form devstudio-11.0.0.AM1-v20170531-1042-B189-installer-standalone.jar
> Reporter: Lukáš Valach
> Assignee: Nick Boldt
> Priority: Minor
> Fix For: 11.0.0.AM1
>
>
> I have this error message in eclipse log:
> {code}
> !SESSION Wed May 31 14:13:11 CEST 2017 -----------------------------------------
> !ENTRY org.eclipse.equinox.launcher 4 0 2017-05-31 14:13:11.062
> !MESSAGE Could not find extension: org.eclipse.wst.jsdt.nashorn.extension
> !SESSION 2017-05-31 14:13:11.038 -----------------------------------------------
> eclipse.buildId=11.0.0.AM1-v20170531-1042-B189
> java.version=1.8.0_131
> java.vendor=Oracle Corporation
> BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_GB
> Framework arguments: -product com.jboss.devstudio.core.product
> Command-line arguments: -os linux -ws gtk -arch x86_64 -product com.jboss.devstudio.core.product
> !ENTRY org.eclipse.osgi 4 0 2017-05-31 14:13:11.805
> !MESSAGE Bundle org.eclipse.wst.jsdt.nashorn.extension not found.
> {code}
> I see that plugin org.eclipse.wst.jsdt.nashorn.extension isn't installed in .../Devstudio/studio/plugins/ folder.
> Possibly we have to remove this line from devstudio.ini?
> {code}
> -Dosgi.framework.extensions=org.eclipse.wst.jsdt.nashorn.extension
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (JBIDE-24526) eap 7.1 missing runtime wizard fragment
by Ondrej Dockal (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24526?page=com.atlassian.jira.plugi... ]
Ondrej Dockal commented on JBIDE-24526:
---------------------------------------
I encounter this issue while creating new EAP 7.1 server via Servers -> New -> Server. There was missing JBoss Runtime page in the wizard (while create new runtime option was selected). Hope that your PR will solve this too.
> eap 7.1 missing runtime wizard fragment
> ----------------------------------------
>
> Key: JBIDE-24526
> URL: https://issues.jboss.org/browse/JBIDE-24526
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.5.0.AM1
> Reporter: Rob Stryker
> Assignee: Rob Stryker
> Fix For: 4.5.0.AM1
>
>
> The eap 7.1 runtime fragment is missing when accessed / created via properties -> runtime -> new (the wtp runtime wizard, not jbt's runtime detection)
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (JBDS-4293) Merge requirements-*.json files into one
by Jan Richter (JIRA)
[ https://issues.jboss.org/browse/JBDS-4293?page=com.atlassian.jira.plugin.... ]
Jan Richter closed JBDS-4293.
-----------------------------
Don't know why this issue ended up in fix version 11.0.0, but it was done for 10.4, so closing.
> Merge requirements-*.json files into one
> ----------------------------------------
>
> Key: JBDS-4293
> URL: https://issues.jboss.org/browse/JBDS-4293
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Task
> Components: platform-installer
> Affects Versions: 10.4.0.AM1
> Reporter: Denis Golovin
> Assignee: Sudhir Verma
> Labels: New_and_noteworthy
> Fix For: 10.4.0.GA
>
>
> Current implementation is looking for requirements-${process.platform}.json. There are three supported platforms and therefore three configuration file with duplicated information for some components.
> New implementation should merge configuration in one file and introduce platform attribute for component configuration's. Only components that has platform specific binaries are affected.
> For example for CDK configuration instead of having it defined in three files like this:
> {code:title=requirements-win32.json|borderStyle=solid}
> {
> "cdk": {
> "name": "Red Hat Container Development Kit",
> "description": "Developer Tools for Creating, Testing, and Distributing Red Hat Container-Based Applications",
> "bundle": "yes",
> "version": "3.0.0.GA",
> "dmUrl": "http://cdk-builds.usersys.redhat.com/builds/nightly/11-Feb-2017/windows-a...",
> "url": "http://cdk-builds.usersys.redhat.com/builds/nightly/11-Feb-2017/windows-a...",
> "filename": "minishift.exe",
> "sha256sum": "984318638a5c0d67ae4483bb508f6b90b99f885153dc525660bfff07fa883c94",
> "vendor": "Red Hat, Inc."
> }
> }
> {code}
> {code:title=requirements-darwin.json|borderStyle=solid}
> {
> "cdk": {
> "name": "Red Hat Container Development Kit",
> "description": "Developer Tools for Creating, Testing, and Distributing Red Hat Container-Based Applications",
> "bundle": "yes",
> "version": "3.0.0.GA",
> "dmUrl": "http://cdk-builds.usersys.redhat.com/builds/nightly/11-Feb-2017/darwin-am...",
> "url": "http://cdk-builds.usersys.redhat.com/builds/nightly/11-Feb-2017/darwin-am...",
> "filename": "minishift",
> "sha256sum": "1e7472175e25d9d197149a3ed2192440a1f581f1884cf2b2c77d97674ee73e5e",
> "vendor": "Red Hat, Inc."
> }
> }
> {code}
> {code:title=requirements-linux.json|borderStyle=solid}
> {
> "cdk": {
> "name": "Red Hat Container Development Kit",
> "description": "Developer Tools for Creating, Testing, and Distributing Red Hat Container-Based Applications",
> "bundle": "yes",
> "version": "3.0.0.GA",
> "dmUrl": "http://cdk-builds.usersys.redhat.com/builds/nightly/11-Feb-2017/linux-amd...",
> "url": "http://cdk-builds.usersys.redhat.com/builds/weekly/25-Jan-2017.3.0_alpha....",
> "filename": "linux-amd64.tar.gz",
> "sha256sum": "76da07d4065eb387093af1316371a19c11982b4b9270eff14bca84db69e2bb32",
> "vendor": "Red Hat, Inc."
> }
> }
> {code}
> It would be defined only once like this
> {code:title=requirements.json|borderStyle=solid}
> {
> "cdk": {
> "name": "Red Hat Container Development Kit",
> "description": "Developer Tools for Creating, Testing, and Distributing Red Hat Container-Based Applications",
> "bundle": "yes",
> "version": "3.0.0.GA",
> "vendor": "Red Hat, Inc."
> platform: {
> win32: {
> "dmUrl": "http://cdk-builds.usersys.redhat.com/builds/nightly/11-Feb-2017/windows-a...",
> "url": "http://cdk-builds.usersys.redhat.com/builds/nightly/11-Feb-2017/windows-a...",
> "filename": "minishift.exe",
> "sha256sum": "984318638a5c0d67ae4483bb508f6b90b99f885153dc525660bfff07fa883c94"
> },
> darwin: {
> "dmUrl": "http://cdk-builds.usersys.redhat.com/builds/nightly/11-Feb-2017/darwin-am...",
> "url": "http://cdk-builds.usersys.redhat.com/builds/nightly/11-Feb-2017/darwin-am...",
> "filename": "minishift",
> "sha256sum": "1e7472175e25d9d197149a3ed2192440a1f581f1884cf2b2c77d97674ee73e5e"
> },
> linux: {
> "dmUrl": "http://cdk-builds.usersys.redhat.com/builds/nightly/11-Feb-2017/linux-amd...",
> "url": "http://cdk-builds.usersys.redhat.com/builds/weekly/25-Jan-2017.3.0_alpha....",
> "filename": "linux-amd64.tar.gz",
> "sha256sum": "76da07d4065eb387093af1316371a19c11982b4b9270eff14bca84db69e2bb32"
> }
> }
> }
> }
> {code}
> Note that requirements files used as is in tests, they also transformed during the build and final file is landed in 'transpiled' folder.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (JBDS-4293) Merge requirements-*.json files into one
by Jan Richter (JIRA)
[ https://issues.jboss.org/browse/JBDS-4293?page=com.atlassian.jira.plugin.... ]
Jan Richter updated JBDS-4293:
------------------------------
Fix Version/s: 10.4.0.GA
(was: 11.0.0.AM1)
> Merge requirements-*.json files into one
> ----------------------------------------
>
> Key: JBDS-4293
> URL: https://issues.jboss.org/browse/JBDS-4293
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Task
> Components: platform-installer
> Affects Versions: 10.4.0.AM1
> Reporter: Denis Golovin
> Assignee: Sudhir Verma
> Labels: New_and_noteworthy
> Fix For: 10.4.0.GA
>
>
> Current implementation is looking for requirements-${process.platform}.json. There are three supported platforms and therefore three configuration file with duplicated information for some components.
> New implementation should merge configuration in one file and introduce platform attribute for component configuration's. Only components that has platform specific binaries are affected.
> For example for CDK configuration instead of having it defined in three files like this:
> {code:title=requirements-win32.json|borderStyle=solid}
> {
> "cdk": {
> "name": "Red Hat Container Development Kit",
> "description": "Developer Tools for Creating, Testing, and Distributing Red Hat Container-Based Applications",
> "bundle": "yes",
> "version": "3.0.0.GA",
> "dmUrl": "http://cdk-builds.usersys.redhat.com/builds/nightly/11-Feb-2017/windows-a...",
> "url": "http://cdk-builds.usersys.redhat.com/builds/nightly/11-Feb-2017/windows-a...",
> "filename": "minishift.exe",
> "sha256sum": "984318638a5c0d67ae4483bb508f6b90b99f885153dc525660bfff07fa883c94",
> "vendor": "Red Hat, Inc."
> }
> }
> {code}
> {code:title=requirements-darwin.json|borderStyle=solid}
> {
> "cdk": {
> "name": "Red Hat Container Development Kit",
> "description": "Developer Tools for Creating, Testing, and Distributing Red Hat Container-Based Applications",
> "bundle": "yes",
> "version": "3.0.0.GA",
> "dmUrl": "http://cdk-builds.usersys.redhat.com/builds/nightly/11-Feb-2017/darwin-am...",
> "url": "http://cdk-builds.usersys.redhat.com/builds/nightly/11-Feb-2017/darwin-am...",
> "filename": "minishift",
> "sha256sum": "1e7472175e25d9d197149a3ed2192440a1f581f1884cf2b2c77d97674ee73e5e",
> "vendor": "Red Hat, Inc."
> }
> }
> {code}
> {code:title=requirements-linux.json|borderStyle=solid}
> {
> "cdk": {
> "name": "Red Hat Container Development Kit",
> "description": "Developer Tools for Creating, Testing, and Distributing Red Hat Container-Based Applications",
> "bundle": "yes",
> "version": "3.0.0.GA",
> "dmUrl": "http://cdk-builds.usersys.redhat.com/builds/nightly/11-Feb-2017/linux-amd...",
> "url": "http://cdk-builds.usersys.redhat.com/builds/weekly/25-Jan-2017.3.0_alpha....",
> "filename": "linux-amd64.tar.gz",
> "sha256sum": "76da07d4065eb387093af1316371a19c11982b4b9270eff14bca84db69e2bb32",
> "vendor": "Red Hat, Inc."
> }
> }
> {code}
> It would be defined only once like this
> {code:title=requirements.json|borderStyle=solid}
> {
> "cdk": {
> "name": "Red Hat Container Development Kit",
> "description": "Developer Tools for Creating, Testing, and Distributing Red Hat Container-Based Applications",
> "bundle": "yes",
> "version": "3.0.0.GA",
> "vendor": "Red Hat, Inc."
> platform: {
> win32: {
> "dmUrl": "http://cdk-builds.usersys.redhat.com/builds/nightly/11-Feb-2017/windows-a...",
> "url": "http://cdk-builds.usersys.redhat.com/builds/nightly/11-Feb-2017/windows-a...",
> "filename": "minishift.exe",
> "sha256sum": "984318638a5c0d67ae4483bb508f6b90b99f885153dc525660bfff07fa883c94"
> },
> darwin: {
> "dmUrl": "http://cdk-builds.usersys.redhat.com/builds/nightly/11-Feb-2017/darwin-am...",
> "url": "http://cdk-builds.usersys.redhat.com/builds/nightly/11-Feb-2017/darwin-am...",
> "filename": "minishift",
> "sha256sum": "1e7472175e25d9d197149a3ed2192440a1f581f1884cf2b2c77d97674ee73e5e"
> },
> linux: {
> "dmUrl": "http://cdk-builds.usersys.redhat.com/builds/nightly/11-Feb-2017/linux-amd...",
> "url": "http://cdk-builds.usersys.redhat.com/builds/weekly/25-Jan-2017.3.0_alpha....",
> "filename": "linux-amd64.tar.gz",
> "sha256sum": "76da07d4065eb387093af1316371a19c11982b4b9270eff14bca84db69e2bb32"
> }
> }
> }
> }
> {code}
> Note that requirements files used as is in tests, they also transformed during the build and final file is landed in 'transpiled' folder.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months