[JBoss JIRA] (JBIDE-23380) MOJO that fails or logs errors for build if manifest in .core plugin has .ui dependency
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23380?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-23380:
------------------------------------
Works in Jenkins [1] and in fact caught a core-ui dependency, which I've opened as JBIDE-23410.
[1] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/Inst...
So... try rebuilding your parent pom locally. Or purge the .metadata and .cache folders in ~/.m2/repository/ to clean out stale information, if -U isn't working.
> MOJO that fails or logs errors for build if manifest in .core plugin has .ui dependency
> ---------------------------------------------------------------------------------------
>
> Key: JBIDE-23380
> URL: https://issues.jboss.org/browse/JBIDE-23380
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: build
> Reporter: Rob Stryker
> Assignee: Nick Boldt
> Fix For: 4.4.2.AM3
>
>
> At a minimum, the mojo should:
> foreach plugin, if plugin ends in .core, check plugin/META-INF/MANIFEST for Dependencies manifest header, and verify .ui is not included in the dependencies at all.
> However, this minimum goal would not have solved the issue we are experiencing with foundation.checkup. The foundation.checkup plugin does not end in .core and so would be skipped by this simple algorithm.
> So... we may wish to check transitive dependencies *only in the same repo*. For example, foundation.core depends on foundation.checker, and foundation.checker is in the same repo, so foundation.checker should also be checked for ui deps or fail.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 5 months
[JBoss JIRA] (JBIDE-23410) For JBIDE 4.4.2.AM3: UI dependencies from Core plugins [integration-tests]
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23410?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-23410:
-------------------------------
Description:
For JBIDE 4.4.2.AM3 [integation-tests]: The following core plugins depend on UI plugins directly or indirectly.
{code}
[INFO] --- maven-enforcer-plugin:1.4.1:enforce (core-has-ui-deps) @ org.jboss.tools.perf.test.core ---
[WARNING] Rule 0: org.jboss.tools.releng.CoreUIDependency failed with message:
[CoreUIDependency] org.jboss.tools.perf.test.core is a Core plugin, but depends on these UI plugins directly or transitively:
> org.eclipse.ui
> org.jboss.tools.common.model.ui
> org.eclipse.ui.editors
> org.eclipse.ui.workbench
> org.eclipse.ui.ide
> org.jboss.tools.ui.bot.ext
> org.eclipse.ui.forms
> org.eclipse.ui.views.properties.tabbed
{code}
[Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for integration-tests task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
was:
For JBIDE 4.4.2.AM3 [central]: The following core plugins depend on UI plugins directly or indirectly. {code}[CoreUIDependency] org.jboss.tools.discovery.core is a Core plugin, but depends on these UI plugins directly or transitively:
> org.eclipse.ui.workbench
> org.eclipse.equinox.p2.ui
> org.eclipse.mylyn.discovery.ui
--
[CoreUIDependency] org.jboss.tools.maven.core is a Core plugin, but depends on these UI plugins directly or transitively:
> org.eclipse.jdt.ui
> org.eclipse.ui.workbench
> org.eclipse.m2e.core.ui
--
[CoreUIDependency] org.jboss.tools.maven.sourcelookup.core is a Core plugin, but depends on these UI plugins directly or transitively:
> org.eclipse.ui
> org.eclipse.jdt.ui
> org.eclipse.ui.workbench
> org.eclipse.m2e.core.ui{code}
[Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for central task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
> For JBIDE 4.4.2.AM3: UI dependencies from Core plugins [integration-tests]
> --------------------------------------------------------------------------
>
> Key: JBIDE-23410
> URL: https://issues.jboss.org/browse/JBIDE-23410
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: central
> Reporter: Nick Boldt
> Assignee: Fred Bricon
> Priority: Minor
> Labels: task
> Fix For: 4.4.x
>
>
> For JBIDE 4.4.2.AM3 [integation-tests]: The following core plugins depend on UI plugins directly or indirectly.
> {code}
> [INFO] --- maven-enforcer-plugin:1.4.1:enforce (core-has-ui-deps) @ org.jboss.tools.perf.test.core ---
> [WARNING] Rule 0: org.jboss.tools.releng.CoreUIDependency failed with message:
> [CoreUIDependency] org.jboss.tools.perf.test.core is a Core plugin, but depends on these UI plugins directly or transitively:
> > org.eclipse.ui
> > org.jboss.tools.common.model.ui
> > org.eclipse.ui.editors
> > org.eclipse.ui.workbench
> > org.eclipse.ui.ide
> > org.jboss.tools.ui.bot.ext
> > org.eclipse.ui.forms
> > org.eclipse.ui.views.properties.tabbed
> {code}
> [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for integration-tests task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 5 months
[JBoss JIRA] (JBIDE-23410) For JBIDE 4.4.2.AM3: UI dependencies from Core plugins [integration-tests]
by Nick Boldt (JIRA)
Nick Boldt created JBIDE-23410:
----------------------------------
Summary: For JBIDE 4.4.2.AM3: UI dependencies from Core plugins [integration-tests]
Key: JBIDE-23410
URL: https://issues.jboss.org/browse/JBIDE-23410
Project: Tools (JBoss Tools)
Issue Type: Task
Components: central
Reporter: Nick Boldt
Assignee: Fred Bricon
Priority: Minor
Fix For: 4.4.x
For JBIDE 4.4.2.AM3 [central]: The following core plugins depend on UI plugins directly or indirectly. {code}[CoreUIDependency] org.jboss.tools.discovery.core is a Core plugin, but depends on these UI plugins directly or transitively:
> org.eclipse.ui.workbench
> org.eclipse.equinox.p2.ui
> org.eclipse.mylyn.discovery.ui
--
[CoreUIDependency] org.jboss.tools.maven.core is a Core plugin, but depends on these UI plugins directly or transitively:
> org.eclipse.jdt.ui
> org.eclipse.ui.workbench
> org.eclipse.m2e.core.ui
--
[CoreUIDependency] org.jboss.tools.maven.sourcelookup.core is a Core plugin, but depends on these UI plugins directly or transitively:
> org.eclipse.ui
> org.eclipse.jdt.ui
> org.eclipse.ui.workbench
> org.eclipse.m2e.core.ui{code}
[Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for central task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 5 months
[JBoss JIRA] (JBIDE-22362) Server Adapter: Static changes done to nodejs application are not visible
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22362?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-22362:
------------------------------------------
[~ibuziuk] if I remember right, https://github.com/jbosstools/jbosstools-openshift/pull/1340/files#diff-a... (JBIDE-22225) is preventing publishing from happening in Debug. Changes will thus not be visible any more if I restart the server in debug mode, changes wont get published any more, once this patch is applied. Correct?
> Server Adapter: Static changes done to nodejs application are not visible
> -------------------------------------------------------------------------
>
> Key: JBIDE-22362
> URL: https://issues.jboss.org/browse/JBIDE-22362
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: javascript, openshift
> Affects Versions: 4.4.0.Alpha2
> Reporter: Marián Labuda
> Assignee: Ilya Buziuk
> Priority: Critical
> Labels: openshift_v3, server_adapter
> Fix For: 4.4.2.AM3
>
>
> I am having an OpenShift application based either on nodejs-example or nodejs-mongodb-example template. Once application is up and running I create a new server adapter and perform changes in index.html. These changes are static and should be (?) immediately visible on OpenShift server, but they are not. I have checked whether changes were published, but rsync in console shows expected output also changes done manually on the server side to index.html are not visible in browser (even when cache overwritten is triggered - so there is no caching problem in browser). This seems to be upstream issues, but requires investigating.
> So far I have tried it on CDK OpenShift. It would be nice to test it on other OpenShift instances, also on templates using different base docker image.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 5 months
[JBoss JIRA] (JBIDE-3937) Create Stress JUnit Test Suite withch is included all available JUnit tests from all components
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-3937?page=com.atlassian.jira.plugin... ]
Martin Malina commented on JBIDE-3937:
--------------------------------------
On on my radar and definitely not Vlado's - he's no longer in the devstudio team.
[~rawagner] was working on some performance tests, perhaps he can comment if those are being used?
> Create Stress JUnit Test Suite withch is included all available JUnit tests from all components
> -----------------------------------------------------------------------------------------------
>
> Key: JBIDE-3937
> URL: https://issues.jboss.org/browse/JBIDE-3937
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: build, qa
> Affects Versions: 3.0.0.GA
> Reporter: Denis Golovin
> Assignee: Denis Golovin
> Fix For: 4.3.x
>
>
> Why we need this?
> The Idea is in emulation a long development session. Now all tests suites are ran one by one each in its own session on clean workspace. A longest test suite takes around 15-20 minutes. Such test suite would emulate an about one hour long development session which can help to find memory leaks or other integration problems.
> It should be able to start on selected JBT build. It should download last or selected version of JBT form download site and start Stress Test Suite.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 5 months
[JBoss JIRA] (JBIDE-22362) Server Adapter: Static changes done to nodejs application are not visible
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22362?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-22362:
------------------------------------------
[~ibuziuk] I dont see what doesnt work with https://github.com/ibuziuk/jbosstools-openshift/commit/d419c9d3da26ad4cc5...
# ASSERT: have a nodejs app running in OpenShift and the project imported to the Eclipse workspace
# EXEC: Open nodejs in context menu of the "nodejs-example" server adapter Show In > Web Browser
# EXEC: Restart nodejs-example in debug mode via context menu of the server adapter "Restart in Debug"
# EXEC: modify workspace project "nodejs-ex/views/index.html": change title "<h1>Welcome....</h1>"
# EXEC: refresh browser
# ASSERT: change must be visible in browser
And I saw the change. What's wrong?
> Server Adapter: Static changes done to nodejs application are not visible
> -------------------------------------------------------------------------
>
> Key: JBIDE-22362
> URL: https://issues.jboss.org/browse/JBIDE-22362
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: javascript, openshift
> Affects Versions: 4.4.0.Alpha2
> Reporter: Marián Labuda
> Assignee: Ilya Buziuk
> Priority: Critical
> Labels: openshift_v3, server_adapter
> Fix For: 4.4.2.AM3
>
>
> I am having an OpenShift application based either on nodejs-example or nodejs-mongodb-example template. Once application is up and running I create a new server adapter and perform changes in index.html. These changes are static and should be (?) immediately visible on OpenShift server, but they are not. I have checked whether changes were published, but rsync in console shows expected output also changes done manually on the server side to index.html are not visible in browser (even when cache overwritten is triggered - so there is no caching problem in browser). This seems to be upstream issues, but requires investigating.
> So far I have tried it on CDK OpenShift. It would be nice to test it on other OpenShift instances, also on templates using different base docker image.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 5 months
[JBoss JIRA] (JBIDE-22362) Server Adapter: Static changes done to nodejs application are not visible
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22362?page=com.atlassian.jira.plugi... ]
Andre Dietisheim edited comment on JBIDE-22362 at 10/24/16 11:22 AM:
---------------------------------------------------------------------
[~ibuziuk] I dont see what doesnt work with https://github.com/ibuziuk/jbosstools-openshift/commit/d419c9d3da26ad4cc5...
# ASSERT: have a nodejs app running in OpenShift and the project imported to the Eclipse workspace
# EXEC: Open nodejs in context menu of the "nodejs-example" server adapter Show In > Web Browser
# EXEC: Restart nodejs-example in debug mode via context menu of the server adapter "Restart in Debug"
# EXEC: modify workspace project "nodejs-ex/views/index.html": change title "<h1>Welcome....</h1>"
# EXEC: refresh browser
# ASSERT: change must be visible in browser
And I saw the change. What's wrong? What am I missing?
was (Author: adietish):
[~ibuziuk] I dont see what doesnt work with https://github.com/ibuziuk/jbosstools-openshift/commit/d419c9d3da26ad4cc5...
# ASSERT: have a nodejs app running in OpenShift and the project imported to the Eclipse workspace
# EXEC: Open nodejs in context menu of the "nodejs-example" server adapter Show In > Web Browser
# EXEC: Restart nodejs-example in debug mode via context menu of the server adapter "Restart in Debug"
# EXEC: modify workspace project "nodejs-ex/views/index.html": change title "<h1>Welcome....</h1>"
# EXEC: refresh browser
# ASSERT: change must be visible in browser
And I saw the change. What's wrong?
> Server Adapter: Static changes done to nodejs application are not visible
> -------------------------------------------------------------------------
>
> Key: JBIDE-22362
> URL: https://issues.jboss.org/browse/JBIDE-22362
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: javascript, openshift
> Affects Versions: 4.4.0.Alpha2
> Reporter: Marián Labuda
> Assignee: Ilya Buziuk
> Priority: Critical
> Labels: openshift_v3, server_adapter
> Fix For: 4.4.2.AM3
>
>
> I am having an OpenShift application based either on nodejs-example or nodejs-mongodb-example template. Once application is up and running I create a new server adapter and perform changes in index.html. These changes are static and should be (?) immediately visible on OpenShift server, but they are not. I have checked whether changes were published, but rsync in console shows expected output also changes done manually on the server side to index.html are not visible in browser (even when cache overwritten is triggered - so there is no caching problem in browser). This seems to be upstream issues, but requires investigating.
> So far I have tried it on CDK OpenShift. It would be nice to test it on other OpenShift instances, also on templates using different base docker image.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 5 months
[JBoss JIRA] (JBIDE-23016) When starting CDK 2.2 with landrush for the first time, user will be prompted for sudo password
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23016?page=com.atlassian.jira.plugi... ]
Martin Malina closed JBIDE-23016.
---------------------------------
I can confirm that this works as expected. But the future of our use of landrush is still uncertain. Currently the landrush plugin is included in the cdk builds, but it's not actually used.
> When starting CDK 2.2 with landrush for the first time, user will be prompted for sudo password
> -----------------------------------------------------------------------------------------------
>
> Key: JBIDE-23016
> URL: https://issues.jboss.org/browse/JBIDE-23016
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk
> Affects Versions: 4.4.1.AM3
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Priority: Critical
> Fix For: 4.4.2.AM2
>
>
> The problem is that the first time you do vagrant up with cdk that has landrush set up, you will be asked to provide your sudo password so that landrush can be set up (unless you used it elsewhere already).
> This is definitely true on Mac, most likely on Linux also. On Windows, I expect that you will probably just be shown the system prompt for agreeing that the process uses admin rights.
> When I did this yesterday (while testing cdk 2.2 rc1), I actually started it from terminal first, so I could enter my password in the console. But I'm pretty sure this wouldn't work in Eclipse. So we need to figure out how to handle this scenario and also test what happens on Windows after installing devsuite and then starting cdk from devstudio - that is our most important use case.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 5 months