June 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-24522) Incremental deployment for WF11/EAP7.1 - only redeploy if necessary

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24522?page=com.atlassian.jira.plugi... ] Rob Stryker resolved JBIDE-24522. --------------------------------- Resolution: Done Closing this. Please open any other more specific issues you find. I'm open to new solutions but I'd prefer focussed jiras on this topic rather than one large over-arching one. So let's take the broken situations one by one and see if we can get them fixed. > Incremental deployment for WF11/EAP7.1 - only redeploy if necessary > ------------------------------------------------------------------- > > Key: JBIDE-24522 > URL: https://issues.jboss.org/browse/JBIDE-24522 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Affects Versions: 4.5.0.AM1 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.5.0.AM1 > > > As discussed with Rob, JBIDE-23784 added support for incremental deployment over management API for WildFly 11 / EAP 7.1. But it does not actually deploy incrementally. It will still redeploy the whole module on the server. The improvement that was done in that JIRA is that now the whole project is not copied over to the server every time there is a change - now only the changes are being sent. But the whole module is still redeployed. > So I think it's worth looking into if it's possible to improve this further so that the module is not always redeployed on the server. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24522) Incremental deployment for WF11/EAP7.1 - only redeploy if necessary

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24522?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-24522: ------------------------------------- So I made a patch to fix this. It... works... a bit better than before. Changes to only an index.html will not initiate a redeployment. However, if the server is in debug mode, and you try to change a class file, and you have a breakpoint set there, it won't work properly, at all. I'll be pinging the EAP team to help me debug it asap. For now, a proper workaround is to change the "Application Reload Behavior" field in the server editor to something like "\.jar$|\.class$" AND disable the breakpoint, then refresh the webpage, then enable the breakpoint to debug it. This will force a redeploy to occur if any class files have changed. Why the normal remote debugger isn't working is very difficult to tell. Either way, this definitely improves the situation. It may make sense to change the default pattern to be "\.jar$|\.class$" all the time. But I'm hesitatn to do that until I know what effect it would have on other situations. > Incremental deployment for WF11/EAP7.1 - only redeploy if necessary > ------------------------------------------------------------------- > > Key: JBIDE-24522 > URL: https://issues.jboss.org/browse/JBIDE-24522 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Affects Versions: 4.5.0.AM1 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.5.0.AM1 > > > As discussed with Rob, JBIDE-23784 added support for incremental deployment over management API for WildFly 11 / EAP 7.1. But it does not actually deploy incrementally. It will still redeploy the whole module on the server. The improvement that was done in that JIRA is that now the whole project is not copied over to the server every time there is a change - now only the changes are being sent. But the whole module is still redeployed. > So I think it's worth looking into if it's possible to improve this further so that the module is not always redeployed on the server. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24080) release webtools site for Eclipse 4.5 Oxygen to so WTP 3.9 discovery upstream can find it

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24080?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-24080: ------------------------------------ However, EPP package doesn't have the updated wst.server.discovery plugin... so I've reopened https://bugs.eclipse.org/bugs/show_bug.cgi?id=513578 > release webtools site for Eclipse 4.5 Oxygen to so WTP 3.9 discovery upstream can find it > ----------------------------------------------------------------------------------------- > > Key: JBIDE-24080 > URL: https://issues.jboss.org/browse/JBIDE-24080 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server, updatesite, upstream > Affects Versions: 4.5.0.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.5.0.Final > > > Need a semi-working placeholder (even if it's a CI build) so that WTP can resolve a valid site for server adapters. > Content that needs to be copied is here: > http://download.jboss.org/jbosstools/oxygen/snapshots/updates/ > Once we release 4.5.0.Final, we can then update the symlink to point here: > http://download.jboss.org/jbosstools/oxygen/stable/updates/ > Upstream issue: > https://bugs.eclipse.org/513578 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[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/7/17 3:27 PM: ------------------------------------------------------------ I would suggest that if you want different defaults when running itests, that the itests root pom set that different default. For example: https://github.com/jbosstools/jbosstools-server/pull/516 Otherwise I don't see a way to have useUIThread = true AND false in the same parent pom property. Or, you could use the `mvn clean verify -P ITests` to enable the ITests profile in parent pom [1] which sets *useUIThread = false*, but that will also set the property false for unit tests too. [1] https://github.com/jbosstools/jbosstools-build/blob/master/parent/pom.xml... It's probably best to set the values you want at the itests/pom.xml level, so you override the default set for running unit tests. was (Author: nickboldt): I would suggest that if you want different defaults when running itests, that the itests root pom set that different default. For example: https://github.com/jbosstools/jbosstools-server/pull/516 Otherwise I don't see a way to have useUIThread = true AND false in the same parent pom property. Or, you could use the `mvn clean verify -P ITests` to enable the ITests profile in parent pom which sets *useUIThread = false*, but that will also set the property false for unit tests too. It's probably best to set the values you want at the itests/pom.xml level, so you override the default set for running unit tests. > 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, 10 months

1
0
0 / 0

[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: ------------------------------------ I would suggest that if you want different defaults when running itests, that the itests root pom set that different default. For example: https://github.com/jbosstools/jbosstools-server/pull/516 Otherwise I don't see a way to have useUIThread = true AND false in the same parent pom property. Or, you could use the `mvn clean verify -P ITests` to enable the ITests profile in parent pom which sets *useUIThread = false*, but that will also set the property false for unit tests too. It's probably best to set the values you want at the itests/pom.xml level, so you override the default set for running unit tests. > 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, 10 months

1
0
0 / 0

[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 updated JBIDE-24547: ------------------------------- Fix Version/s: 4.5.0.AM1 > 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, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24550) add Oxygen builds to tools.jboss.org

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24550?page=com.atlassian.jira.plugi... ] Paul Leacu commented on JBIDE-24550: ------------------------------------ +1 looks good! > add Oxygen builds to tools.jboss.org > ------------------------------------ > > Key: JBIDE-24550 > URL: https://issues.jboss.org/browse/JBIDE-24550 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: website > Affects Versions: 4.5.0.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.5.0.AM1 > > > Seems we forgot to add the Oxygen-based CI builds to the list of builds on http://tools.jboss.org/downloads/overview.html -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24550) add Oxygen builds to tools.jboss.org

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24550?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-24550: ------------------------------------ I've commented out all the pre-Final and pre-GA builds of devstudio, jbosstools, and integration stack to make the downloads overview page cleaner. Commits pushed to master [1] and production [2]. [1] http://tools.stage.jboss.org/downloads/overview.html [2] http://tools.jboss.org/downloads/overview.html cc: [~pleacu] [~jeffmaury] > add Oxygen builds to tools.jboss.org > ------------------------------------ > > Key: JBIDE-24550 > URL: https://issues.jboss.org/browse/JBIDE-24550 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: website > Affects Versions: 4.5.0.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.5.0.AM1 > > > Seems we forgot to add the Oxygen-based CI builds to the list of builds on http://tools.jboss.org/downloads/overview.html -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24458) Docker New and Noteworthy for 4.5.0.AM1

by Jeff Johnston (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24458?page=com.atlassian.jira.plugi... ] Jeff Johnston commented on JBIDE-24458: --------------------------------------- Create N&N for Docker 4.5.0.AM1 > Docker New and Noteworthy for 4.5.0.AM1 > --------------------------------------------------- > > Key: JBIDE-24458 > URL: https://issues.jboss.org/browse/JBIDE-24458 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: docker > Reporter: Jeff MAURY > Assignee: Jeff Johnston > Priority: Critical > Fix For: 4.5.0.AM1 > > > Jeff Johnston, > Search for your component's New and Noteworthy issues: > Queries: > * [Completed Docker JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] > * [All Completed JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] > * [N&N Task JIRAs for this milestone|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Not...] > * [All N&N Task JIRAs|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Notewor...] > If no N&N issues are found for Docker, check if there are issues that SHOULD have been labelled with *Labels =* _new_and_noteworthy_, and add them. > Document the ones relevant for Docker by submitting a pull request against: > * https://github.com/jbosstools/jbosstools-website/tree/master/documentatio... > If your PR's commit comment is of the form... {code}JBIDE-24455 #comment Create N&N for Docker 4.5.0.AM1 #close{code}... and your github user's email address is the same as your JIRA one, then this JIRA should be closed automatically when the PR is applied. > If there is nothing new or noteworthy for Docker for this milestone, please *reject* and *close* this issue. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24550) add Oxygen builds to tools.jboss.org

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-24550: ---------------------------------- Summary: add Oxygen builds to tools.jboss.org Key: JBIDE-24550 URL: https://issues.jboss.org/browse/JBIDE-24550 Project: Tools (JBoss Tools) Issue Type: Bug Components: website Affects Versions: 4.5.0.AM1 Reporter: Nick Boldt Seems we forgot to add the Oxygen-based CI builds to the list of builds on http://tools.jboss.org/downloads/overview.html -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues June 2017