[JBoss JIRA] (JBDS-4362) Eliminate devstudio EAP installer bundle; move EAP installation functionality into devsuite installer
by Lukáš Valach (JIRA)
[ https://issues.jboss.org/browse/JBDS-4362?page=com.atlassian.jira.plugin.... ]
Lukáš Valach closed JBDS-4362.
------------------------------
Verified, closing.
> Eliminate devstudio EAP installer bundle; move EAP installation functionality into devsuite installer
> -----------------------------------------------------------------------------------------------------
>
> Key: JBDS-4362
> URL: https://issues.jboss.org/browse/JBDS-4362
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: installer, integration-platform
> Affects Versions: 10.4.0.AM3
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 11.0.0.AM1
>
> Attachments: devstudio-install-add-servers-01.png, devstudio-install-add-servers-02.png, devstudio-install-add-servers-03.png, devstudio-install-add-servers-04.png, devstudio-install-add-servers-05.png
>
>
> For devstudio 11, we might want to eliminate the devstudio EAP installer.
> If we could do so, we would no longer require an internal-facing server (eg., www.qa or wonka.mw) since everything in devstudio would be completely open source and free.
> This would also make releases simpler and faster as I wouldn't have to push bits to BOTH the internal and external staging servers - we could stage 100% on the public devstudio.redhat.com server.
> Since EAP releases don't align very well with devstudio releases, maybe it's time to decouple entirely?
> That way only the devSUITE installer would include EAP.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 9 months
[JBoss JIRA] (JBIDE-24548) Server adapter: Automatic syncing of code with the pod doesn't work with Wildfly
by Dmitrii Bocharov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24548?page=com.atlassian.jira.plugi... ]
Dmitrii Bocharov commented on JBIDE-24548:
------------------------------------------
[~v_m] could you, please, provide the application you're working with? The best option would be if you provide an openshift json template
> Server adapter: Automatic syncing of code with the pod doesn't work with Wildfly
> --------------------------------------------------------------------------------
>
> Key: JBIDE-24548
> URL: https://issues.jboss.org/browse/JBIDE-24548
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.3.Final
> Environment: Running on Mac 10.12.4
> JBDS
> Version: 10.3.0.GA
> Build id: GA-v20170218-1636-B94
> Build date: 20170218-1636
> Installed minishift v1.0.1
> Reporter: Veer Muchandi
> Assignee: Dmitrii Bocharov
> Priority: Critical
> Labels: openshift_v3, server_adapter
> Fix For: 4.5.0.AM2
>
>
> * Created a Wildfly application on openshift web-ui
> * Setup a server adapter
> * Imported application to JBDS
> * Made code changes and saved.
> Result:
> While the data seems to be exchanged, the changes are not synced with the pod and the application is not updated.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 9 months
[JBoss JIRA] (JBIDE-24547) Refactor ITests settings in parent pom
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24547?page=com.atlassian.jira.plugi... ]
Nick Boldt edited comment on JBIDE-24547 at 6/16/17 9:44 AM:
-------------------------------------------------------------
Given the choice, I prefer ITests to NOT RUN by default. +1 for PR #255, -1 for PR #256. That way we build & run UNIT tests by default, and ITests are an optional additional profile.
was (Author: nickboldt):
Given the choice, I prefer ITests to NOT RUN by default. +1 for PR #255. That way we build & run UNIT tests by default, and ITests are an optional additional profile.
> Refactor ITests settings in parent pom
> --------------------------------------
>
> Key: JBIDE-24547
> URL: https://issues.jboss.org/browse/JBIDE-24547
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, integration-tests
> Reporter: Pavol Srna
> Assignee: Pavol Srna
> Fix For: 4.5.0.AM1
>
>
> It is desired that single 'mvn clean verify' command will run *unit tests* and *integration tests* in a single run. Parent pom should hold all shared settings across jbosstools repositories (e.g pluginCustomization, useUIThread etc ).
> The problem is that unit tests require useUIThread=true, but integration tests the opposite. We need to come with a solution where we share the settings in parent pom.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 9 months
[JBoss JIRA] (JBIDE-24547) Refactor ITests settings in parent pom
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24547?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-24547:
------------------------------------
Given the choice, I prefer ITests to NOT RUN by default. +1 for PR #255. That way we build & run UNIT tests by default, and ITests are an optional additional profile.
> Refactor ITests settings in parent pom
> --------------------------------------
>
> Key: JBIDE-24547
> URL: https://issues.jboss.org/browse/JBIDE-24547
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, integration-tests
> Reporter: Pavol Srna
> Assignee: Pavol Srna
> Fix For: 4.5.0.AM1
>
>
> It is desired that single 'mvn clean verify' command will run *unit tests* and *integration tests* in a single run. Parent pom should hold all shared settings across jbosstools repositories (e.g pluginCustomization, useUIThread etc ).
> The problem is that unit tests require useUIThread=true, but integration tests the opposite. We need to come with a solution where we share the settings in parent pom.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 9 months
[JBoss JIRA] (JBTIS-1011) Create UI test for language / dataformats properties
by Andrej Podhradsky (JIRA)
[ https://issues.jboss.org/browse/JBTIS-1011?page=com.atlassian.jira.plugin... ]
Andrej Podhradsky updated JBTIS-1011:
-------------------------------------
Fix Version/s: 11.0.0.AM1
(was: 10.3.0.GA)
> Create UI test for language / dataformats properties
> ----------------------------------------------------
>
> Key: JBTIS-1011
> URL: https://issues.jboss.org/browse/JBTIS-1011
> Project: JBoss Tools Integration Stack
> Issue Type: Task
> Components: Fuse IDE, QE
> Affects Versions: 10.0.0.GA
> Reporter: Lars Heinemann
> Assignee: Andrej Podhradsky
> Priority: Blocker
> Fix For: 11.0.0.AM1
>
>
> If you select a "transform" endpoint in the diagram and set a new expression language the pom.xml should be updated to contain the dependency of the new language if not yet there.
> Same applies to dataformats (for instance "marshal" endpoints). Whenever you change the dataformat in the properties view to some other data format the dependency for that data format should be added to the pom.xml if its not yet there.
> Please find more information on this issue in FUSETOOLS-2186.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 9 months
[JBoss JIRA] (JBTIS-1011) Create UI test for language / dataformats properties
by Andrej Podhradsky (JIRA)
[ https://issues.jboss.org/browse/JBTIS-1011?page=com.atlassian.jira.plugin... ]
Andrej Podhradsky updated JBTIS-1011:
-------------------------------------
Priority: Blocker (was: Critical)
> Create UI test for language / dataformats properties
> ----------------------------------------------------
>
> Key: JBTIS-1011
> URL: https://issues.jboss.org/browse/JBTIS-1011
> Project: JBoss Tools Integration Stack
> Issue Type: Task
> Components: Fuse IDE, QE
> Affects Versions: 10.0.0.GA
> Reporter: Lars Heinemann
> Assignee: Andrej Podhradsky
> Priority: Blocker
> Fix For: 10.3.0.GA
>
>
> If you select a "transform" endpoint in the diagram and set a new expression language the pom.xml should be updated to contain the dependency of the new language if not yet there.
> Same applies to dataformats (for instance "marshal" endpoints). Whenever you change the dataformat in the properties view to some other data format the dependency for that data format should be added to the pom.xml if its not yet there.
> Please find more information on this issue in FUSETOOLS-2186.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 9 months
[JBoss JIRA] (JBTIS-1011) Create UI test for language / dataformats properties
by Andrej Podhradsky (JIRA)
[ https://issues.jboss.org/browse/JBTIS-1011?page=com.atlassian.jira.plugin... ]
Andrej Podhradsky updated JBTIS-1011:
-------------------------------------
Priority: Critical (was: Major)
> Create UI test for language / dataformats properties
> ----------------------------------------------------
>
> Key: JBTIS-1011
> URL: https://issues.jboss.org/browse/JBTIS-1011
> Project: JBoss Tools Integration Stack
> Issue Type: Task
> Components: Fuse IDE, QE
> Affects Versions: 10.0.0.GA
> Reporter: Lars Heinemann
> Assignee: Andrej Podhradsky
> Priority: Critical
> Fix For: 10.3.0.GA
>
>
> If you select a "transform" endpoint in the diagram and set a new expression language the pom.xml should be updated to contain the dependency of the new language if not yet there.
> Same applies to dataformats (for instance "marshal" endpoints). Whenever you change the dataformat in the properties view to some other data format the dependency for that data format should be added to the pom.xml if its not yet there.
> Please find more information on this issue in FUSETOOLS-2186.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 9 months
[JBoss JIRA] (JBIDE-24547) Refactor ITests settings in parent pom
by Pavol Srna (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24547?page=com.atlassian.jira.plugi... ]
Pavol Srna commented on JBIDE-24547:
------------------------------------
I investigated and found out that we cannot use maven lifecycle to have separate settings for unit tests, UI tests and itests. All are run by tycho surefire and in the same 'integration-test' phase. So I'm coming with 2 other options:
1) run itests by default. Disadvantage is that we need copy/paste itests settings into given folder-of-tests and there will be many. which makes the maintenance harder. PR is here: https://github.com/jbosstools/jbosstools-build/pull/256
2) disable itests by default, and keep itests configuration in ITests profile. Advantage is that the build won't take ages by default (itests disabled), itests configuration is stored in ITests profile (don't need to copy everything to all folders-of-tests). To run the build with itests you need to call: `mvn verify -PITests` PR is here: https://github.com/jbosstools/jbosstools-build/pull/255
[~nickboldt], [~jeffmaury]. Please look at the PRs, review, comment and pick one preferred option.
Thanks!
> Refactor ITests settings in parent pom
> --------------------------------------
>
> Key: JBIDE-24547
> URL: https://issues.jboss.org/browse/JBIDE-24547
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, integration-tests
> Reporter: Pavol Srna
> Assignee: Pavol Srna
> Fix For: 4.5.0.AM1
>
>
> It is desired that single 'mvn clean verify' command will run *unit tests* and *integration tests* in a single run. Parent pom should hold all shared settings across jbosstools repositories (e.g pluginCustomization, useUIThread etc ).
> The problem is that unit tests require useUIThread=true, but integration tests the opposite. We need to come with a solution where we share the settings in parent pom.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 9 months