October 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-23380) MOJO that fails or logs errors for build if manifest in .core plugin has .ui dependency

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23380?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-23380: --------------------------------------- OK, I removed .cache and .meta and now I'm downloading the internet again. It's been 30 mins or so and still running. I have to go, so will update this JIRA tomorrow. > 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

1
0
0 / 0

[JBoss JIRA] (JBTIS-947) Installer with runtime doesn't automatically set the appropriated server

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-947?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky updated JBTIS-947: ------------------------------------ Component/s: distribution (was: 10.0.0.GA) > Installer with runtime doesn't automatically set the appropriated server > ------------------------------------------------------------------------ > > Key: JBTIS-947 > URL: https://issues.jboss.org/browse/JBTIS-947 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 10.0.0.CR1 > Environment: devstudio-integration-stack-rt-10.0.0.CR1-standalone-installer.jar > Reporter: Andrej Podhradsky > Priority: Minor > Attachments: search_for_runtimes.png > > > Installer with runtime doesn't automatically set the appropriated server. Instead of that there is a dialog 'Search for runtimes' when you start the IDE for the first time. > !search_for_runtimes.png|thumbnail! > Note that this is a different behavior as it is in Devstudio installer with EAP -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-947) Installer with runtime doesn't automatically set the appropriated server

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-947?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky updated JBTIS-947: ------------------------------------ Affects Version/s: 10.0.0.CR1 > Installer with runtime doesn't automatically set the appropriated server > ------------------------------------------------------------------------ > > Key: JBTIS-947 > URL: https://issues.jboss.org/browse/JBTIS-947 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 10.0.0.CR1 > Environment: devstudio-integration-stack-rt-10.0.0.CR1-standalone-installer.jar > Reporter: Andrej Podhradsky > Priority: Minor > Attachments: search_for_runtimes.png > > > Installer with runtime doesn't automatically set the appropriated server. Instead of that there is a dialog 'Search for runtimes' when you start the IDE for the first time. > !search_for_runtimes.png|thumbnail! > Note that this is a different behavior as it is in Devstudio installer with EAP -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-948) Runtime is not detected if the Devstudio was installed using the InstallConfigRecord.xml

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-948?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky updated JBTIS-948: ------------------------------------ Affects Version/s: 10.0.0.CR1 (was: 10.0.0.GA) > Runtime is not detected if the Devstudio was installed using the InstallConfigRecord.xml > ---------------------------------------------------------------------------------------- > > Key: JBTIS-948 > URL: https://issues.jboss.org/browse/JBTIS-948 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 10.0.0.CR1 > Environment: devstudio-integration-stack-rt-10.0.0.CR1-standalone-installer.jar > Reporter: Andrej Podhradsky > > Runtime is not detected if the Devstudio was installed using the InstallConfigRecord.xml. It seems that the folder for runtime detection is set to {{<user>/jboss-runtimes}}. > The above folder can be found at Preferences > JBoss Tools > JBoss Runtime Detection -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-950) Cannot connect to fuse runtime after installing by the installer

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-950?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky updated JBTIS-950: ------------------------------------ Affects Version/s: 10.0.0.CR1 (was: 10.0.0.GA) > Cannot connect to fuse runtime after installing by the installer > ---------------------------------------------------------------- > > Key: JBTIS-950 > URL: https://issues.jboss.org/browse/JBTIS-950 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 10.0.0.CR1 > Environment: devstudio-integration-stack-rt-10.0.0.CR1-standalone-installer.jar > Reporter: Andrej Podhradsky > Priority: Critical > > Cannot connect to fuse runtime after installing by the installer. The problem is that the runtime doesn't specify any user by default. This is important if you need to execute a command in the terminal (Terminal view). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-949) Rename the name of the installer with runtime

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-949?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky updated JBTIS-949: ------------------------------------ Affects Version/s: 10.0.0.CR1 (was: 10.0.0.GA) > Rename the name of the installer with runtime > --------------------------------------------- > > Key: JBTIS-949 > URL: https://issues.jboss.org/browse/JBTIS-949 > Project: JBoss Tools Integration Stack > Issue Type: Enhancement > Components: distribution > Affects Versions: 10.0.0.CR1 > Environment: devstudio-integration-stack-rt-10.0.0.CR1-standalone-installer.jar > Reporter: Andrej Podhradsky > Priority: Minor > > Rename the name of the installer with runtime. I suggest > {code} > devstudio-integration-stack-10.0.0.CR1-runtime-installer.jar > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-945) Missing MD5 files for Devstutio-IS 10.0.0.CR1 installers

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-945?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky updated JBTIS-945: ------------------------------------ Affects Version/s: 10.0.0.CR1 > Missing MD5 files for Devstutio-IS 10.0.0.CR1 installers > -------------------------------------------------------- > > Key: JBTIS-945 > URL: https://issues.jboss.org/browse/JBTIS-945 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Affects Versions: 10.0.0.CR1 > Reporter: Andrej Podhradsky > Priority: Critical > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-945) Missing MD5 files for Devstutio-IS 10.0.0.CR1 installers

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-945?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky updated JBTIS-945: ------------------------------------ Component/s: distribution > Missing MD5 files for Devstutio-IS 10.0.0.CR1 installers > -------------------------------------------------------- > > Key: JBTIS-945 > URL: https://issues.jboss.org/browse/JBTIS-945 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 10.0.0.CR1 > Reporter: Andrej Podhradsky > Priority: Critical > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4077) Cannot run integration tests against Devstudio with latest target platform

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4077?page=com.atlassian.jira.plugin.... ] Nick Boldt edited comment on JBDS-4077 at 10/24/16 12:08 PM: ------------------------------------------------------------- So comparing the screenshots above I see that in the broken case (devstudio 10.2.AM2) the window title, icon, toolbar items, and even a perspective icon missing. Good vs. bad: https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Develop... vs. https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Develop... This to me suggests that either the bad one is just Eclipse (but then we'd see "data -- JavaEE -- Eclipse" as the product name in the window title instead of "data -- JavaEE -- ") or else it's devstudio but a ton of plugins haven't been enabled/activated. Could be because if an invalid install, or because of missing OS-level deps (like GTK2? GTK3? SWT?) or maybe it's launching with a JDK lower than 1.8 so JDK8-dependent stuff isn't loading. Point is ... we need to figure out what's broken in the AM2 devstudio install on that slave. Can we start devstudio with {code} -debug -console -consolelog{code} to get more details about what's (not) happening? Or, can someone run these tests locally and debug them in Eclipse? http://maven.apache.org/surefire/maven-surefire-plugin/examples/debugging... was (Author: nickboldt): So comparing the screenshots above I see that in the broken case (devstudio 10.2.AM2) the window title, icon, toolbar items, and even a perspective icon missing. Good vs. bad: !https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Developer%20Studio%20Integration%20Tests/job/deltaspike.102AM1/2/jdk=jdk1.8,label=rhel7/artifact/jbosstools-integration-tests/tests/org.jboss.tools.deltaspike.ui.bot.test/target/screenshots/wildfly-10.xml/org.jboss.tools.deltaspike.ui.bot.test.ConfigPropertyAnnotationTest.testInjectUnsupportedConfigProperty.png|thumbnail! !https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Developer%20Studio%20Integration%20Tests/job/deltaspike.102AM2/1/jdk=jdk1.8,label=rhel7/artifact/jbosstools-integration-tests/tests/org.jboss.tools.deltaspike.ui.bot.test/target/screenshots/wildfly-10.xml/org.jboss.tools.deltaspike.ui.bot.test.ExceptionHandlerAnnotationTest@ServerRequirement.png|thumbnail! This to me suggests that either the bad one is just Eclipse (but then we'd see "data -- JavaEE -- Eclipse" as the product name in the window title instead of "data -- JavaEE -- ") or else it's devstudio but a ton of plugins haven't been enabled/activated. Could be because if an invalid install, or because of missing OS-level deps (like GTK2? GTK3? SWT?) or maybe it's launching with a JDK lower than 1.8 so JDK8-dependent stuff isn't loading. Point is ... we need to figure out what's broken in the AM2 devstudio install on that slave. Can we start devstudio with {code} -debug -console -consolelog{code} to get more details about what's (not) happening? Or, can someone run these tests locally and debug them in Eclipse? http://maven.apache.org/surefire/maven-surefire-plugin/examples/debugging... > Cannot run integration tests against Devstudio with latest target platform > -------------------------------------------------------------------------- > > Key: JBDS-4077 > URL: https://issues.jboss.org/browse/JBDS-4077 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: build, target-platform > Affects Versions: 10.2.0.AM1 > Reporter: Jan Richter > Assignee: Nick Boldt > Priority: Blocker > Fix For: 10.2.0.AM3 > > Attachments: .log, jbosstools-integration-tests.log.txt.zip, no_devstudio.jpg, no_devstudio.png, org.jboss.tools.deltaspike.ui.bot.test.DeltaspikeAllBotTests.txt, org.jboss.tools.deltaspike.ui.bot.test.log.txt, org.jboss.tools.deltaspike.ui.bot.test.log_0.txt, Screenshot_2016-10-05_10-00-03.png, Screenshot_2016-10-05_10-00-21.png, Screenshot_2016-10-05_10-00-28.png, Screenshot_2016-10-05_10-00-57.png, Screenshot_2016-10-05_10-01-14.png, Screenshot_2016-10-05_10-01-32.png, shell.png, TEST-org.jboss.tools.deltaspike.ui.bot.test.DeltaspikeAllBotTests.xml, tpfail.png > > > Integration tests run from maven against Devstudio, which was built using the latest target platform (4.61.0.AM1-SNAPSHOT), cannot properly launch all the plugins and fail afterwards. > A full devstudio should open when the tests are run. Instead it looks like this: > !tpfail.png|thumbnail! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[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 updated JBIDE-22362: ------------------------------------- Attachment: enabling-dev-mode-has-encountered-an-error.png > 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 > > Attachments: enabling-dev-mode-has-encountered-an-error.png > > > 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

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 October 2016