[JBoss JIRA] (JBTIS-647) Add test for Swagger
by Matus Makovy (JIRA)
Matus Makovy created JBTIS-647:
----------------------------------
Summary: Add test for Swagger
Key: JBTIS-647
URL: https://issues.jboss.org/browse/JBTIS-647
Project: JBoss Tools Integration Stack
Issue Type: Bug
Components: QE, teiid
Affects Versions: 4.3.0.Beta1
Reporter: Matus Makovy
Assignee: Matus Makovy
Fix For: 4.3.0.CR1
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBTIS-646) Do not include BPMN2 features in the JBoss Fuse category
by Andrej Podhradsky (JIRA)
Andrej Podhradsky created JBTIS-646:
---------------------------------------
Summary: Do not include BPMN2 features in the JBoss Fuse category
Key: JBTIS-646
URL: https://issues.jboss.org/browse/JBTIS-646
Project: JBoss Tools Integration Stack
Issue Type: Enhancement
Components: distribution
Environment: JBDS-IS 9.0.0.CR1a
Reporter: Andrej Podhradsky
The category JBoss Fuse Development should contain only the following features
- Fuse tooling
- SwitchYard tooling (+ BPEL/BPMN2 support)
All its dependencies such as BPMN2 should be included in the site without specifying in any category (they could be included in the target platform such as BPEL).
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBTIS-646) Do not include BPMN2 features in the JBoss Fuse category
by Andrej Podhradsky (JIRA)
[ https://issues.jboss.org/browse/JBTIS-646?page=com.atlassian.jira.plugin.... ]
Andrej Podhradsky updated JBTIS-646:
------------------------------------
Attachment: jbdsis_fuse_category.png
> Do not include BPMN2 features in the JBoss Fuse category
> --------------------------------------------------------
>
> Key: JBTIS-646
> URL: https://issues.jboss.org/browse/JBTIS-646
> Project: JBoss Tools Integration Stack
> Issue Type: Enhancement
> Components: distribution
> Environment: JBDS-IS 9.0.0.CR1a
> Reporter: Andrej Podhradsky
> Attachments: jbdsis_fuse_category.png
>
>
> The category JBoss Fuse Development should contain only the following features
> - Fuse tooling
> - SwitchYard tooling (+ BPEL/BPMN2 support)
> All its dependencies such as BPMN2 should be included in the site without specifying in any category (they could be included in the target platform such as BPEL).
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBTIS-640) Cannot install JBDS-IS EA in offline mode
by Andrej Podhradsky (JIRA)
[ https://issues.jboss.org/browse/JBTIS-640?page=com.atlassian.jira.plugin.... ]
Andrej Podhradsky commented on JBTIS-640:
-----------------------------------------
This is fixed in the snapshot build.
> Cannot install JBDS-IS EA in offline mode
> -----------------------------------------
>
> Key: JBTIS-640
> URL: https://issues.jboss.org/browse/JBTIS-640
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Components: distribution
> Affects Versions: 9.0.0.CR1
> Reporter: Andrej Podhradsky
> Assignee: Paul Leacu
> Priority: Blocker
>
> When installing JBDS-IS 9.0.0.CR1 EA from the zip file I'm getting the following
> {code}
> Cannot complete the install because one or more required items could not be found.
> Software being installed: JBoss Fuse Tooling Core Bundles 8.0.0.Beta2-v20160401-1305-B821 (org.fusesource.ide.core.feature.feature.group 8.0.0.Beta2-v20160401-1305-B821)
> Missing requirement: JBoss Fuse Tooling Core Bundles 8.0.0.Beta2-v20160401-1305-B821 (org.fusesource.ide.core.feature.feature.group 8.0.0.Beta2-v20160401-1305-B821) requires 'org.eclipse.zest.core 1.5.100' but it could not be found
> {code}
> EDIT: this can be resolved by adding JBDS-IS 9.0.0.CR1 zip file (the GA one)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBTIS-637) Cannot install JBoss Integration & SOA Dev
by Andrej Podhradsky (JIRA)
[ https://issues.jboss.org/browse/JBTIS-637?page=com.atlassian.jira.plugin.... ]
Andrej Podhradsky commented on JBTIS-637:
-----------------------------------------
This is fixed in the snapshot build. But we should consider removing this category, see JBTIS-644
> Cannot install JBoss Integration & SOA Dev
> ------------------------------------------
>
> Key: JBTIS-637
> URL: https://issues.jboss.org/browse/JBTIS-637
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Components: distribution
> Affects Versions: 9.0.0.CR1
> Reporter: Andrej Podhradsky
> Assignee: Paul Leacu
> Priority: Blocker
>
> The following error occurs if you try to install com.jboss.devstudio.integration-stack.soa.feature from
> https://devstudio.redhat.com/9.0/staging/updates/integration-stack/
> {code}
> Cannot complete the install because one or more required items could not be found.
> Software being installed: JBoss Integration and SOA Development 9.0.0.CR1 (com.jboss.devstudio.integration-stack.soa.feature.feature.group 9.0.0.CR1)
> Missing requirement: JBoss Integration and SOA Development 9.0.0.CR1 (com.jboss.devstudio.integration-stack.soa.feature.feature.group 9.0.0.CR1) requires 'org.fusesource.ide.camel.editor.feature.feature.group 0.0.0' but it could not be found
> {code}
> EDIT: Note that this will be a problem when installing JBDS-IS from Marketplace (I think the above feature is used in marketplace)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBTIS-645) Try to apply convention over configuration
by Jozef Marko (JIRA)
Jozef Marko created JBTIS-645:
---------------------------------
Summary: Try to apply convention over configuration
Key: JBTIS-645
URL: https://issues.jboss.org/browse/JBTIS-645
Project: JBoss Tools Integration Stack
Issue Type: Task
Components: BPMN2, QE
Reporter: Jozef Marko
Assignee: Jozef Marko
In bpm2 test is used annotation, which determines, which file to open, how to save given file, directory where manipulate with files. All these should be extracted from name of test class.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-22134) Sometimes docker image data are not shown in Deploy to OpenShift wizard
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22134?page=com.atlassian.jira.plugi... ]
Marián Labuda commented on JBIDE-22134:
---------------------------------------
Let's keep this opened, even though there is no known way to reproduce it all the time at the moment. If someone find a reliable way to reproduce, please fill in gaps in this JIRA. It is annoying because it makes deploying of docker image difficult, because if there are no exposes ports, user has to know what the port(s) is/are exposed or go through image documentation if exists.
> Sometimes docker image data are not shown in Deploy to OpenShift wizard
> -----------------------------------------------------------------------
>
> Key: JBIDE-22134
> URL: https://issues.jboss.org/browse/JBIDE-22134
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Marián Labuda
> Labels: docker, openshift_v3
>
> Sometimes docker image data are not shown/processed in Deploy to OpenShift wizard. Environment variables, exposed ports etc. Unfortunately I don't have a way to reproduce it 100 %, I am not sure at the moment what is causing it, but when deploying a local docker image (image already pulled) to OpenShift, environment variables and exposed ports are empty, even though when using an image which has not been pulled yet, I have not spotted this at all.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-22134) Sometimes docker image data are not shown in Deploy to OpenShift wizard
by Marián Labuda (JIRA)
Marián Labuda created JBIDE-22134:
-------------------------------------
Summary: Sometimes docker image data are not shown in Deploy to OpenShift wizard
Key: JBIDE-22134
URL: https://issues.jboss.org/browse/JBIDE-22134
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 4.3.1.CR1
Reporter: Marián Labuda
Sometimes docker image data are not shown/processed in Deploy to OpenShift wizard. Environment variables, exposed ports etc. Unfortunately I don't have a way to reproduce it 100 %, I am not sure at the moment what is causing it, but when deploying a local docker image (image already pulled) to OpenShift, environment variables and exposed ports are empty, even though when using an image which has not been pulled yet, I have not spotted this at all.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-22134) Sometimes docker image data are not shown in Deploy to OpenShift wizard
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22134?page=com.atlassian.jira.plugi... ]
Marián Labuda updated JBIDE-22134:
----------------------------------
Labels: docker openshift_v3 (was: )
> Sometimes docker image data are not shown in Deploy to OpenShift wizard
> -----------------------------------------------------------------------
>
> Key: JBIDE-22134
> URL: https://issues.jboss.org/browse/JBIDE-22134
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Marián Labuda
> Labels: docker, openshift_v3
>
> Sometimes docker image data are not shown/processed in Deploy to OpenShift wizard. Environment variables, exposed ports etc. Unfortunately I don't have a way to reproduce it 100 %, I am not sure at the moment what is causing it, but when deploying a local docker image (image already pulled) to OpenShift, environment variables and exposed ports are empty, even though when using an image which has not been pulled yet, I have not spotted this at all.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years