December 2015 - jbosstools-issues

[JBoss JIRA] (JBIDE-21145) Composite install job does not reliably install all JBT IUs and so does not see changes between CI builds

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21145?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-21145: ------------------------------- Fix Version/s: (was: 4.3.1.Beta1) > Composite install job does not reliably install all JBT IUs and so does not see changes between CI builds > --------------------------------------------------------------------------------------------------------- > > Key: JBIDE-21145 > URL: https://issues.jboss.org/browse/JBIDE-21145 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.3.1.Beta1, 4.4.0.Alpha1 > Reporter: Pavol Srna > Assignee: Nick Boldt > Priority: Blocker > Fix For: 4.4.0.Alpha1 > > Attachments: jbide21145-conflict-between-tp-and-central.png > > > We have often seen old artifacts on nightly sites (mars and neon too). > It seems that the composite-install job [0], [1] is not reliable. So, the downstream JBT aggregate builds [2], [3] are not triggered automatically to pick up all new changes in the upstream JBT component site builds. > [0] http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-composite-... > [1] http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-composite-... > [2] http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-build-site... (latest build shows: "Nov 27, 2015 6:15 AM NOT PUBLISHED: UNCHANGED") > [3] http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-build-site... (latest build shows: "Nov 27, 2015 3:43 AM NOT PUBLISHED: UNCHANGED") > Please investigate. > Thanks! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21215) IUs missing from snapshot update site while site is being published / outdated metadata needs to be refreshed within Eclipse

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21215?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-21215: ------------------------------- Fix Version/s: 4.3.x (was: 4.3.1.Beta1) > IUs missing from snapshot update site while site is being published / outdated metadata needs to be refreshed within Eclipse > ---------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-21215 > URL: https://issues.jboss.org/browse/JBIDE-21215 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.3.1.Beta1 > Reporter: Max Rydahl Andersen > Assignee: Nick Boldt > Fix For: 4.3.x > > > running updates from: http://download.jboss.org/jbosstools/mars/snapshots/updates/ > I get this error: > {quote} > An error occurred while collecting items to be installed > session context was:(profile=_Users_max_products_eclipse_jee-mars3_Eclipse.app_Contents_Eclipse, phase=org.eclipse.equinox.internal.p2.engine.phases.Collect, operand=, action=). > No repository found containing: osgi.bundle,org.jboss.tools.common,3.7.1.Beta1-v20151204-0542-B55 > No repository found containing: osgi.bundle,org.jboss.tools.common.core,3.7.1.Beta1-v20151204-0542-B55 > No repository found containing: osgi.bundle,org.jboss.tools.common.el.core,3.7.1.Beta1-v20151204-0542-B55 > No repository found containing: osgi.bundle,org.jboss.tools.common.jdt.debug,3.7.1.Beta1-v20151204-0542-B55 > No repository found containing: osgi.bundle,org.jboss.tools.common.jdt.debug.ui,3.7.1.Beta1-v20151204-0542-B55 > No repository found containing: osgi.bundle,org.jboss.tools.common.resref.core,3.7.1.Beta1-v20151204-0542-B55 > No repository found containing: osgi.bundle,org.jboss.tools.common.text.xml,3.7.1.Beta1-v20151204-0542-B55 > No repository found containing: osgi.bundle,org.jboss.tools.common.ui,3.7.1.Beta1-v20151204-0542-B55 > No repository found containing: osgi.bundle,org.jboss.tools.common.validation,3.7.1.Beta1-v20151204-0542-B55 > No repository found containing: osgi.bundle,org.jboss.tools.foundation.checkup,1.2.1.Beta1-v20151204-0542-B55 > No repository found containing: osgi.bundle,org.jboss.tools.foundation.core,1.2.1.Beta1-v20151204-0542-B55 > No repository found containing: osgi.bundle,org.jboss.tools.foundation.ui,1.2.1.Beta1-v20151204-0542-B55 > No repository found containing: osgi.bundle,org.jboss.tools.openshift.cdk.server,3.1.0.Beta1-v20151205-0342-B106 > No repository found containing: osgi.bundle,org.jboss.tools.openshift.client,3.1.0.Beta1-v20151205-0342-B106 > No repository found containing: osgi.bundle,org.jboss.tools.openshift.common.core,3.1.0.Beta1-v20151205-0342-B106 > No repository found containing: osgi.bundle,org.jboss.tools.openshift.common.ui,3.1.0.Beta1-v20151205-0342-B106 > No repository found containing: osgi.bundle,org.jboss.tools.openshift.core,3.1.0.Beta1-v20151205-0342-B106 > No repository found containing: osgi.bundle,org.jboss.tools.openshift.egit.core,3.1.0.Beta1-v20151205-0342-B106 > No repository found containing: osgi.bundle,org.jboss.tools.openshift.egit.ui,3.1.0.Beta1-v20151205-0342-B106 > No repository found containing: osgi.bundle,org.jboss.tools.openshift.express.client,3.1.0.Beta1-v20151205-0342-B106 > No repository found containing: osgi.bundle,org.jboss.tools.openshift.express.core,3.1.0.Beta1-v20151205-0342-B106 > No repository found containing: osgi.bundle,org.jboss.tools.openshift.express.ui,3.1.0.Beta1-v20151205-0342-B106 > No repository found containing: osgi.bundle,org.jboss.tools.openshift.ui,3.1.0.Beta1-v20151205-0342-B106 > No repository found containing: osgi.bundle,org.jboss.tools.runtime.core,3.1.1.Beta1-v20151204-0542-B55 > No repository found containing: osgi.bundle,org.jboss.tools.runtime.ui,3.1.1.Beta1-v20151204-0542-B55 > No repository found containing: osgi.bundle,org.jboss.tools.stacks.core,1.2.1.Beta1-v20151204-0542-B55 > No repository found containing: osgi.bundle,org.jboss.tools.usage,2.1.1.Beta1-v20151204-0542-B55 > No repository found containing: org.eclipse.update.feature,org.jboss.tools.openshift.cdk.feature,3.1.0.Beta1-v20151205-0342-B106 > No repository found containing: org.eclipse.update.feature,org.jboss.tools.openshift.express.feature,3.1.0.Beta1-v20151205-0342-B106 > No repository found containing: org.eclipse.update.feature,org.jboss.tools.openshift.feature,3.1.0.Beta1-v20151205-0342-B106 > {quote} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3557) ReLicense JBDS Installer

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3557?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3557: -------------------------------- Fix Version/s: 9.1.0.Beta2 (was: 9.0.0.Beta2) > ReLicense JBDS Installer > ------------------------ > > Key: JBDS-3557 > URL: https://issues.jboss.org/browse/JBDS-3557 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Enhancement > Components: installer, legal > Reporter: Ken Finnigan > Assignee: Denis Golovin > Fix For: 9.1.0.Beta2 > > > For the Developer Platform to be able to bundle JBDS, it needs to be licensed as ASLv2 or EPL and not GPL -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21309) install tests should perform installs on minimum and maximum TPs, and report on which there are failures

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21309?page=com.atlassian.jira.plugi... ] Nick Boldt reassigned JBIDE-21309: ---------------------------------- Assignee: Nick Boldt > install tests should perform installs on minimum and maximum TPs, and report on which there are failures > -------------------------------------------------------------------------------------------------------- > > Key: JBIDE-21309 > URL: https://issues.jboss.org/browse/JBIDE-21309 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, target-platform > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.3.1.Beta2 > > > Currently, we run the install tests on the maximum TP using the latest Eclipse JEE or Platform Binary. > If we can't do an install against Mars.0 (only Mars.1) due to the fact that the Mars.0 install requires remediation, we should have those tests to show the failure, and log that in the N&N. > Also, if install-grinder can support p2 remediation, that would be awesome too as we could verify that use case too. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21309) install tests should perform installs on minimum and maximum TPs, and report on which there are failures

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21309?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-21309: ------------------------------- Fix Version/s: 4.3.1.Beta2 > install tests should perform installs on minimum and maximum TPs, and report on which there are failures > -------------------------------------------------------------------------------------------------------- > > Key: JBIDE-21309 > URL: https://issues.jboss.org/browse/JBIDE-21309 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, target-platform > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.3.1.Beta2 > > > Currently, we run the install tests on the maximum TP using the latest Eclipse JEE or Platform Binary. > If we can't do an install against Mars.0 (only Mars.1) due to the fact that the Mars.0 install requires remediation, we should have those tests to show the failure, and log that in the N&N. > Also, if install-grinder can support p2 remediation, that would be awesome too as we could verify that use case too. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21262) For JBIDE 4.3.1.Beta1: Code Freeze + Branch

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21262?page=com.atlassian.jira.plugi... ] Nick Boldt closed JBIDE-21262. ------------------------------ Resolution: Done > For JBIDE 4.3.1.Beta1: Code Freeze + Branch > ------------------------------------------- > > Key: JBIDE-21262 > URL: https://issues.jboss.org/browse/JBIDE-21262 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Labels: task > Fix For: 4.3.1.Beta1 > > > For JBIDE 4.3.1.Beta1: Please perform the following tasks: > 0. If nothing has changed in your component since the release of JBoss Tools 4.3.0.Final (eg., Portal, Freemarker?), *{color:red}Reject this JIRA{color}*. > Otherwise: > 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.3.1.Beta1 > [Unresolved JIRAs with fixVersion = 4.3.1.Beta1, 9.1.0.Beta1|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%2...] > 1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 4.3.0 to 4.3.1, 1.2.3 to 1.2.100, or 2.3.100 to 2.3.101 > *NOTE:* If you already did this earlier when we were preparing for Beta1 (after 4.3.0.Final was released), you do *not* need to do so again. > Please also ensure that the version of your code in the master branch is *greater* than your code in the 4.3.x branch. > {code} > mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.24.0:set-version -DnewVersion=4.3.1-SNAPSHOT > {code} > 2. Update your root pom to use parent pom version 4.3.1.Beta1-SNAPSHOT. > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.3.1.Beta1-SNAPSHOT</version> > </parent> > {code} > 3. Ensure you've built & run your plugin tests using the latest target platform version 4.50.2.Beta1 (or 4.50.2.Beta1-SNAPSHOT). > {code} > mvn clean verify -Dtpc.version=4.50.2.Beta1-SNAPSHOT # (if the TP is still a SNAPSHOT) > or > mvn clean verify -Dtpc.version=4.50.2.Beta1 # (if the TP is already released) > {code} > 4. Branch from your existing jbosstools-4.3.x branch into a new *{color:blue}jbosstools-4.3.1.Beta1x{color}* branch; > {code} > git checkout jbosstools-4.3.x > git pull origin jbosstools-4.3.x > git checkout -b jbosstools-4.3.1.Beta1x > git push origin jbosstools-4.3.1.Beta1x > {code} > 5. *NOW THAT YOU HAVE BRANCHED*, check out your *{color:orange}jbosstools-4.3.x branch{color}*. > {code} > git checkout jbosstools-4.3.x > git pull origin jbosstools-4.3.x > {code} > 6. Update your *{color:orange}jbosstools-4.3.x branch{color}* parent pom to use the latest version, *{color:orange}4.3.1.Beta2-SNAPSHOT{color}*: > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.3.1.Beta2-SNAPSHOT</version> > </parent> > {code} > Now, your root pom will use parent pom version: > * *{color:blue}4.3.1.Beta1-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.3.1.Beta1x{color}* branch, and > * *{color:orange}4.3.1.Beta2-SNAPSHOT{color}* in your *{color:orange}jbosstools-4.3.x{color}* branch. > 7. Close (do not resolve) this JIRA when done. > 8. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20in%20%28JBDS%2...] to do, please complete them next. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] > See also: JBDS-3572 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21309) install tests should perform installs on minimum and maximum TPs, and report on which there are failures

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-21309: ---------------------------------- Summary: install tests should perform installs on minimum and maximum TPs, and report on which there are failures Key: JBIDE-21309 URL: https://issues.jboss.org/browse/JBIDE-21309 Project: Tools (JBoss Tools) Issue Type: Bug Components: build, target-platform Reporter: Nick Boldt Currently, we run the install tests on the maximum TP using the latest Eclipse JEE or Platform Binary. If we can't do an install against Mars.0 (only Mars.1) due to the fact that the Mars.0 install requires remediation, we should have those tests to show the failure, and log that in the N&N. Also, if install-grinder can support p2 remediation, that would be awesome too as we could verify that use case too. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21038) Software/Update page is not working on Fedora 23 (Beta)

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21038?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-21038: --------------------------------------------- https://developer.jboss.org/message/947232?et=watches.email.thread#947232 with user having issues. would we make Fedora 23 users better of by moving software update tab to html5 too ? > Software/Update page is not working on Fedora 23 (Beta) > ------------------------------------------------------- > > Key: JBIDE-21038 > URL: https://issues.jboss.org/browse/JBIDE-21038 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.3.0.Final > Environment: JBDS 9.0.0.GA > Reporter: Radim Hopp > Assignee: Snjezana Peco > Priority: Critical > Fix For: 4.3.1.Beta2, 4.4.0.Alpha1 > > > Recently I upgraded my system to Fedora 23 (beta) and second page of Cetnral (Software/Update) is not working. It is rendered with "Refreshing..." text and carousel (which is not spinning as it should). One processor core goes 100%. > java version "1.8.0_65" > gtk3 version 3.18.2 > jstack: http://pastebin.com/a7U02yjt > Everything is fine with GTK2. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21299) EL Knowledge Base Problem with PrimeFaces functions

by Viacheslav Kabanovich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21299?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich edited comment on JBIDE-21299 at 12/11/15 6:18 PM: ------------------------------------------------------------------------- [~andrei.ivanov], if you have primefaces-5.3.jar in classpath of your project, do you see some function proposals when you type #{p: and Ctrl+Space? I can see 'component(String id)', 'widgetVar(String expression)', and 'widgetVarFromContext(String expression, UIComponent component)'. Other are missing, which looks like a bug. The problem with 'if*' methods in this case is that Java return type is primitive 'boolean' while facelet library declares for the function java.lang.Boolean. Since this works, then we fail to see that it is the same type. was (Author: scabanovich): [~andrei.ivanov], if you have primefaces-5.3.jar in classpath of your project, do you see some function proposals when you type #{p: and Ctrl+Space? I can see 'component(String id)', 'widgetVar(String expression)', and 'widgetVarFromContext(String expression, UIComponent component)'. Other are missing, which looks like a bug. > EL Knowledge Base Problem with PrimeFaces functions > --------------------------------------------------- > > Key: JBIDE-21299 > URL: https://issues.jboss.org/browse/JBIDE-21299 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: jsf > Affects Versions: 4.3.0.Final > Environment: Eclipse Mars.1 (4.5.1), Primefaces 5.x > Reporter: Andrei Ivanov > Assignee: Viacheslav Kabanovich > Priority: Minor > Fix For: 4.4.x > > > The PrimeFaces functions are not recognized: > {noformat} > "ifAnyGranted" cannot be resolved > "ifGranted" cannot be resolved > "remoteUser" cannot be resolved > {noformat} > These are defined in {{org.primefaces.util.SecurityUtils}} and {{primefaces-5.3.jar/META-INF/primefaces-p.taglib.xml}}. > {code:xml} > <html xmlns="http://www.w3.org/1999/xhtml" > xmlns:ui="http://xmlns.jcp.org/jsf/facelets" > xmlns:h="http://xmlns.jcp.org/jsf/html" > xmlns:f="http://xmlns.jcp.org/jsf/core" > xmlns:c="http://xmlns.jcp.org/jsp/jstl/core" > xmlns:p="http://primefaces.org/ui"> > #{p:ifAnyGranted('ROLE_USER, ROLE_ADMIN')} > #{p:ifGranted('ROLE_ADMIN')} > #{p:remoteUser()} > </html> > {code} > Similar to JBIDE-12317 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21305) Include Docker tooling 1.2.0.Final in TP

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21305?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-21305: ------------------------------------ Mirror pulled http://download.jboss.org/jbosstools/updates/requirements/docker/1.2.0.20... > Include Docker tooling 1.2.0.Final in TP > ---------------------------------------- > > Key: JBIDE-21305 > URL: https://issues.jboss.org/browse/JBIDE-21305 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: target-platform > Affects Versions: 4.3.0.Beta1 > Reporter: Xavier Coulon > Assignee: Nick Boldt > Fix For: 4.3.1.Beta1 > > > Please include the 1.2.0 (stable) release of Docker tooling in the target platform from http://download.eclipse.org/linuxtools/update-docker-1.2 (once it's available for download) > Affected: JBT and JBDS TPs from all three 4.50.x, 4.51.x and 4.60.x branches, as we did last time there was a docker update on Nov 17. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 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 December 2015