January 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-23737) Integration test: if symlink to oc exists, but target isnt, OpenShiftCommandLineToolsRequirement is failing

by Andre Dietisheim (JIRA)

Andre Dietisheim created JBIDE-23737: ---------------------------------------- Summary: Integration test: if symlink to oc exists, but target isnt, OpenShiftCommandLineToolsRequirement is failing Key: JBIDE-23737 URL: https://issues.jboss.org/browse/JBIDE-23737 Project: Tools (JBoss Tools) Issue Type: Bug Components: integration-tests, openshift Affects Versions: 4.4.3.AM1 Reporter: Andre Dietisheim Assignee: Andre Dietisheim Fix For: 4.4.3.AM2 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4204) Red Hat JBoss Developer Studio and dialogs do not size correctly under Fedora 25 w/ Wayland

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4204?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-4204: ----------------------------- Fix Version/s: 10.3.0.AM2 (was: 10.3.0.AM1) > Red Hat JBoss Developer Studio and dialogs do not size correctly under Fedora 25 w/ Wayland > ------------------------------------------------------------------------------------------- > > Key: JBDS-4204 > URL: https://issues.jboss.org/browse/JBDS-4204 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: upstream > Affects Versions: 10.1.0.GA > Environment: FC25, wayland > Reporter: cube 00 > Assignee: Supriya Bharadwaj > Labels: upstream > Fix For: 10.3.0.AM2 > > Attachments: jboss1.png, jboss2.png, jboss3.PnG, jbosstools-diagnostics-20161129110614.zip > > > The window either cuts the top off, bottom off or overdraws into space near the window. Dialogs have their OK/Cancel buttons hidden and resizing does not make them appear either. > Appears to be related to Wayland as I [disabled it|https://fedoraproject.org/wiki/Changes/WaylandByDefault] and things are back to normal. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4130) Environment variables are duplicated after several installations

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4130?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-4130: ----------------------------- Fix Version/s: 10.3.0.AM2 (was: 10.3.0.AM1) > Environment variables are duplicated after several installations > ---------------------------------------------------------------- > > Key: JBDS-4130 > URL: https://issues.jboss.org/browse/JBDS-4130 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 10.1.0.GA > Environment: Windows > Reporter: Aurélien Pupier > Assignee: Denis Golovin > Fix For: 10.3.0.AM2 > > Attachments: screenshot-1.png > > > Installer does not perform any checks at the moment before setting PATH environment variable. This issue affects only windows installer. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3866) vagrant up failed due to rsync error, eclipse tooling confused about state of cdk server

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3866?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-3866: ----------------------------- Fix Version/s: 10.3.0.AM2 (was: 10.3.0.AM1) > vagrant up failed due to rsync error, eclipse tooling confused about state of cdk server > ---------------------------------------------------------------------------------------- > > Key: JBDS-3866 > URL: https://issues.jboss.org/browse/JBDS-3866 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: cdk > Affects Versions: 9.1.0.Beta1 > Environment: Windows 7/64 bit. > (previous installs of CDK and dependencies) > Reporter: Robert Terzi > Assignee: Rob Stryker > Fix For: 10.3.0.AM2 > > > vagrant up through the CDK server tooling failed because of an rsync problem. The tooling lost track of the state of the vagrant box. The vagrant box couldn't be stopped from inside of Eclipse. > The vagrant up failed because of an error with rsync. Something was confused about the user's home directory. It was trying to write to /home/username/.ssh, however, $HOME isn't /home/username, it's /cygdrive/c/Users/username, so /home/username/ doesn't exist. > The CDK server was shown as 'Started, Sychronized'. > The error message appeared in the server console tab. However the stop button wouldn't work. Provisioning had never finished so the OpenShift connection wasn't working either. > Synchronized seems misleading here, since no files had been sync'd yet. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2356) JEE project example generates warnings

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2356?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-2356: ----------------------------- Fix Version/s: 10.3.0.AM2 (was: 10.3.0.AM1) > JEE project example generates warnings > -------------------------------------- > > Key: JBDS-2356 > URL: https://issues.jboss.org/browse/JBDS-2356 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: central > Affects Versions: 6.0.0.Alpha2 > Environment: Version: 6.0.0.Alpha2 > Build id: Alpha2-v20121004-2330-B40 > Build date: 20121004-2330 > Reporter: Len DiMaggio > Assignee: Fred Bricon > Labels: examplewarnings > Fix For: 10.3.0.AM2 > > > The JEE project example generates these warnings: > jboss-javaee6-multi-ejb > No connection specified for project. No database-specific validation will be performed. > The import javax.persistence.PersistenceContext is never used > WebResources.java > /jboss-javaee6-multi-web/src/main/java/org/jboss/tools/example/util > line 10 > The import javax.enterprise.event.Event is never used > MemberController.java > /jboss-javaee6-multi-web/src/main/java/org/jboss/tools/example/controller > line 6 > The import javax.persistence.EntityManager is never used > WebResources.java > /jboss-javaee6-multi-web/src/main/java/org/jboss/tools/example/util > line 9 > The import java.util.logging.Logger is never used > MemberController.java > /jboss-javaee6-multi-web/src/main/java/org/jboss/tools/example/controller > line 3 > The import javax.enterprise.inject.spi.InjectionPoint is never used > WebResources.java > /jboss-javaee6-multi-web/src/main/java/org/jboss/tools/example/util > line 7 > The import java.util.logging.Logger is never used > WebResources.java > /jboss-javaee6-multi-web/src/main/java/org/jboss/tools/example/util > line 3 > Unnecessary @SuppressWarnings("unused") Resources.java > /jboss-javaee6-multi-ejb/src/main/java/org/jboss/tools/example/util > line 24 > No connection specified for project. No database-specific validation will be performed. > jboss-javaee6-multi-ejb > The import javax.persistence.EntityManager is never used > MemberController.java > /jboss-javaee6-multi-web/src/main/java/org/jboss/tools/example/controller -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2355) JEE web project example generates warnings

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2355?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-2355: ----------------------------- Fix Version/s: 10.3.0.AM2 (was: 10.3.0.AM1) > JEE web project example generates warnings > ------------------------------------------ > > Key: JBDS-2355 > URL: https://issues.jboss.org/browse/JBDS-2355 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: central > Affects Versions: 6.0.0.Alpha2 > Environment: Version: 6.0.0.Alpha2 > Build id: Alpha2-v20121004-2330-B40 > Build date: 20121004-2330 > Reporter: Len DiMaggio > Assignee: Fred Bricon > Labels: examplewarnings > Fix For: 10.3.0.AM2 > > > The JEE web project example generates these warnings: > The import java.util.logging.Logger is never used > MemberController.java > /jboss-javaee6-webapp/src/main/java/org/jboss/tools/examples/controller > line 3 > No connection specified for project. No database-specific validation will be performed. > jboss-javaee6-webapp > Unnecessary @SuppressWarnings("unused") Resources.java > /jboss-javaee6-webapp/src/main/java/org/jboss/tools/examples/util > line 26 > The import javax.persistence.EntityManager is never used > MemberController.java > /jboss-javaee6-webapp/src/main/java/org/jboss/tools/examples/controller > line 14 > The import javax.enterprise.event.Event is never used > MemberController.java > /jboss-javaee6-webapp/src/main/java/org/jboss/tools/examples/controller > line 7 > The import javax.ejb.Stateful is never used > MemberController.java > /jboss-javaee6-webapp/src/main/java/org/jboss/tools/examples/controller > line 6 > The import org.jboss.tools.examples.controller.MemberController is never used > MemberRegistrationTest.java > /jboss-javaee6-webapp/src/test/java/org/jboss/tools/examples/test -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22305) automate process for fetching latest target platform mirrors

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22305?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-22305: ------------------------------- Fix Version/s: 4.4.3.AM2 (was: 4.4.3.AM1) > automate process for fetching latest target platform mirrors > ------------------------------------------------------------ > > Key: JBIDE-22305 > URL: https://issues.jboss.org/browse/JBIDE-22305 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: target-platform, updatesite, upstream > Affects Versions: 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Labels: releasework > Fix For: 4.4.3.AM2 > > Attachments: git.diff.txt > > > Rather than manually pulling requirements, it would be hella sweet if there was a job config into which we could just list all the URLs to mirror and their matching project names. > Then this job would scrape the *.target files for the current list of URLs used, grep out the /requirements/<reqname>/<version>, fetch a new mirror for each new version*, and dump an updated copy of the .target file into the job's workspace. > Thus for webtools we might simply define: > webtools,S-3.8.0M7-20160503010110,http://download.eclipse.org/webtools/do... > and we'd end up with: > http://download.jboss.org/jbosstools/updates/requirements/webtools/S-3.8.... > * Since we already have a http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt... job we can just pass parameters to that to invoke the mirroring steps. Would be even better if we could run multiple calls in parallel as neon and wtp can take >2hr > 1. matrix job. each config is a trio of reqname/version/URL which is passed to a process akin to that of the jbosstools-requirements job to perform the mirror; process is now scripted here: https://github.com/jbosstools/jbosstools-build-ci/blob/jbosstools-4.4.x/p... > 2. when all children are done, a downstream job can runs TP update & validation against new .target files > * fetch http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstoolstargetplatf... > * parse that into a list of URLs > * each URL contains REQ_NAME/VERSION, which can then be matched up with similar lines in .target files > * run p2diff between old/new URLs in .target to generate list of changes and verify new site contains all the same IUs > * resulting edited .target files will remain in the workspace, and we can then run > * https://github.com/jbosstools/jbosstools-build-ci/blob/jbosstools-4.4.x/u... > * when done if success: > * ideally, generate a PR and attach link in email to jbosstools-dev@ > * if can't generate PR, then attach patch in email to nickboldt & mistria to apply locally in jbosstools-target-platforms to create a PR > * email should includes boilerplate text to send mail to list announcing new change for review -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23569) Integration tests global refactoring: org.jboss.tools.aerogear.ui.bot.test

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23569?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-23569: ------------------------------- Fix Version/s: 4.4.3.AM2 (was: 4.4.3.AM1) > Integration tests global refactoring: org.jboss.tools.aerogear.ui.bot.test > -------------------------------------------------------------------------- > > Key: JBIDE-23569 > URL: https://issues.jboss.org/browse/JBIDE-23569 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: aerogear-hybrid > Affects Versions: 4.4.2.Final > Reporter: Jeff MAURY > Labels: aerogear, integration, integration-test > Fix For: 4.4.3.AM2 > > > Maven command: > {code} > mvn clean verify -Dtest.module=org.jboss.tools.aerogear.ui.bot.test -DskipTests=false > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23570) Integration tests global refactoring: org.jboss.tools.archives.ui.bot.test

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23570?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-23570: ------------------------------- Fix Version/s: 4.4.3.AM2 (was: 4.4.3.AM1) > Integration tests global refactoring: org.jboss.tools.archives.ui.bot.test > -------------------------------------------------------------------------- > > Key: JBIDE-23570 > URL: https://issues.jboss.org/browse/JBIDE-23570 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: archives > Affects Versions: 4.4.2.Final > Reporter: Jeff MAURY > Assignee: Rob Stryker > Labels: archives, integration, integration-test > Fix For: 4.4.3.AM2 > > > Maven command: > {code} > mvn clean verify -Dtest.module=org.jboss.tools.archives.ui.bot.test -DskipTests=false > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23503) Target platform PR check fails to use p2diff correctly, so build fails

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23503?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-23503: ------------------------------- Fix Version/s: 4.4.3.AM2 (was: 4.4.3.AM1) > Target platform PR check fails to use p2diff correctly, so build fails > ---------------------------------------------------------------------- > > Key: JBIDE-23503 > URL: https://issues.jboss.org/browse/JBIDE-23503 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build, target-platform > Affects Versions: 4.4.2.AM3 > Reporter: Nick Boldt > Assignee: Mickael Istria > Fix For: 4.4.3.AM2 > > Attachments: dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com.log.txt > > > Recently, it was noticed that the TP PR checks are failing. And have been for a long time. > So, I'm opening this to track the work needed to make them work again. > There are two different TP PR jobs: > * https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/jbosstoo... (which seems to have never worked) > * https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/jbos... (which has been blue in the past) > Recent failure: > {code} > [INFO] Command line: > [/qa/tools/opt/x86_64/jdk1.8.0_101/jre/bin/java, -jar, /mnt/hudson_workspace/workspace/jbosstools-target-platform-Pull-Request/.repository/p2/osgi/bundle/org.eclipse.equinox.launcher/1.3.100.v20150511-1540/org.eclipse.equinox.launcher-1.3.100.v20150511-1540.jar, -install, /mnt/hudson_workspace/workspace/jbosstools-target-platform-Pull-Request/jbosstools/multiple/target/eclipserun-work, -configuration, /mnt/hudson_workspace/workspace/jbosstools-target-platform-Pull-Request/jbosstools/multiple/target/eclipserun-work/configuration, -application, org.eclipse.equinox.p2.example.p2diff.application, -outputFile=/mnt/hudson_workspace/workspace/jbosstools-target-platform-Pull-Request/jbosstools/multiple/target/jbosstools-multiple-ignoreVersions.p2diff, -mode=ignoreVersions, file:/mnt/hudson_workspace/workspace/jbosstools-target-platform-Pull-Request/jbosstools/multiple/target/jbosstools-multiple.target.repo, http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.6...] > An error has occurred. See the log file > /mnt/hudson_workspace/workspace/jbosstools-target-platform-Pull-Request/jbosstools/multiple/target/eclipserun-work/configuration/1479683354475.log.{code} > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/jbosstoo... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 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 January 2017