September 2015 - jbosstools-issues

[JBoss JIRA] (JBIDE-18820) define how to handle ide.properties and avoid parent pom to always change

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18820?page=com.atlassian.jira.plugi... ] Nick Boldt reassigned JBIDE-18820: ---------------------------------- Assignee: Max Rydahl Andersen (was: Nick Boldt) > define how to handle ide.properties and avoid parent pom to always change > ------------------------------------------------------------------------- > > Key: JBIDE-18820 > URL: https://issues.jboss.org/browse/JBIDE-18820 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build > Reporter: Max Rydahl Andersen > Assignee: Max Rydahl Andersen > Fix For: 4.3.0.CR1 > > > As illustrated in JBIDE-18806 our current setup of how ide.properties and project versioning are not working or at least we seem to not get it updated right. > Current workaround applied is that parent pom now again defines the global version even though this is not reliable at all since not all plugins will be rebuilt. (see JBIDE-13452 for earlier attempts on this) > Opening this jira to make sure we walkthrough and write down which values should be in ide.properties and what level (4.2.0.CR1, 4.2.0 or 4.2. etc), when they get updated (hopefully rarely) and how to avoid parent pom from always having to respin because of a maintanence release. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18820) define how to handle ide.properties and avoid parent pom to always change

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18820?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-18820: ------------------------------------ Do you mean these properties? {code} jboss.discovery.directory.url|jbosstools|4.3=http://download.jboss.org/jb... jboss.discovery.site.url|jbosstools|4.3=http://download.jboss.org/jbossto... jboss.discovery.earlyaccess.site.url|jbosstools|4.3=http://download.jboss... # 4.3.mars version of jbosstools-earlyaccess.properties should be edited here, so the discovery job can fetch it: http://download.jboss.org/jbosstools/mars/snapshots/updates/earlyaccess.p... jboss.discovery.earlyaccess.list.url|jbosstools|4.3=http://download.jboss... jboss.discovery.site.integration-stack.url|jbosstools|4.3=http://download... jboss.discovery.site.integration-stack-sap.url|jbosstools|4.3= jboss.discovery.site.integration-stack-sap.feature=org.fusesource.ide.sap.feature.feature.group {code} Or do you mean stuff that's only in the parent pom right now? https://github.com/jbosstools/jbosstools-build/blob/master/parent/pom.xml#L7 https://github.com/jbosstools/jbosstools-build/blob/master/parent/pom.xml... https://github.com/jbosstools/jbosstools-build/blob/master/parent/pom.xml... https://github.com/jbosstools/jbosstools-build/blob/master/parent/pom.xml... {code} <version>4.3.0.CR1-SNAPSHOT</version> <!-- changes once per milestone until Final <BUILD_ALIAS>CR1</BUILD_ALIAS> <!-- changes once per milestone until Final <targetEclipseVersion>4.5 (Mars)</targetEclipseVersion> <!-- changes once per year <tychoVersion>0.23.1</tychoVersion> <!-- changes as new releases happen <tychoExtrasVersion>${tychoVersion}</tychoExtrasVersion> <jbossTychoPluginsVersion>0.23.1-SNAPSHOT</jbossTychoPluginsVersion> <!-- changes as new releases happen <jbosstoolsRelengPublishVersion>4.3.0.CR1-SNAPSHOT</jbosstoolsRelengPublishVersion> <!-- changes as new releases happen <TARGET_PLATFORM_VERSION>4.50.0.CR1-SNAPSHOT</TARGET_PLATFORM_VERSION> <!-- changes once per milestone until Final (Mars.0) <TARGET_PLATFORM_VERSION_MAXIMUM>4.50.0.CR1-SNAPSHOT</TARGET_PLATFORM_VERSION_MAXIMUM> <!-- changes once per milestone until end of Mars (Mars.2) {code} None of these are set in ide-config.properties, but all, being Maven properties, can be overwritten in Jenkins configs. > define how to handle ide.properties and avoid parent pom to always change > ------------------------------------------------------------------------- > > Key: JBIDE-18820 > URL: https://issues.jboss.org/browse/JBIDE-18820 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build > Reporter: Max Rydahl Andersen > Assignee: Nick Boldt > Fix For: 4.3.0.CR1 > > > As illustrated in JBIDE-18806 our current setup of how ide.properties and project versioning are not working or at least we seem to not get it updated right. > Current workaround applied is that parent pom now again defines the global version even though this is not reliable at all since not all plugins will be rebuilt. (see JBIDE-13452 for earlier attempts on this) > Opening this jira to make sure we walkthrough and write down which values should be in ide.properties and what level (4.2.0.CR1, 4.2.0 or 4.2. etc), when they get updated (hopefully rarely) and how to avoid parent pom from always having to respin because of a maintanence release. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20194) For JBIDE 4.3.0.CR1: Migrate to using license feature in JBT 4.3 / JBDS 9

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20194?page=com.atlassian.jira.plugi... ] Nick Boldt closed JBIDE-20194. ------------------------------ Resolution: Done > For JBIDE 4.3.0.CR1: Migrate to using license feature in JBT 4.3 / JBDS 9 > ------------------------------------------------------------------------- > > Key: JBIDE-20194 > URL: https://issues.jboss.org/browse/JBIDE-20194 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Labels: task > Fix For: 4.3.0.CR1 > > Attachments: jbide20194-portlet-not-updated.png > > > For JBIDE 4.3.0.CR1: Please perform the following tasks: > 1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.1.0 or 1.0.100. > 2. Switch to using the new o.j.t.foundation.license.feature. Instructions here: > https://github.com/jbosstools/jbosstools-devdoc/blob/master/source/how_to... > 2. Resolve this JIRA when done. QE can then verify and close it later. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] > See also: JBDS-3481 > STEPS TO VERIFY THAT IT WORKED: > https://github.com/jbosstools/jbosstools-devdoc/blob/master/source/how_to... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3494) JBDS 9.0.0.beta2 - is preconfigured without an update site

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-3494?page=com.atlassian.jira.plugin.... ] CDW Engine updated JBDS-3494: ----------------------------- CDW release: + (was: ?) > JBDS 9.0.0.beta2 - is preconfigured without an update site > ----------------------------------------------------------- > > Key: JBDS-3494 > URL: https://issues.jboss.org/browse/JBDS-3494 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: updatesite > Affects Versions: 9.0.0.Beta2 > Reporter: Len DiMaggio > Assignee: Nick Boldt > Priority: Blocker > Fix For: 9.0.0.CR1 > > Attachments: jbds3494.png, JBDS_update.png > > > Seeing this in JBDS 9.0.0.beta2.respin-b: > There are no update sites configured - see attached screenshot. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3494) JBDS 9.0.0.beta2 - is preconfigured without an update site

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-3494?page=com.atlassian.jira.plugin.... ] CDW Engine reassigned JBDS-3494: -------------------------------- > JBDS 9.0.0.beta2 - is preconfigured without an update site > ----------------------------------------------------------- > > Key: JBDS-3494 > URL: https://issues.jboss.org/browse/JBDS-3494 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: updatesite > Affects Versions: 9.0.0.Beta2 > Reporter: Len DiMaggio > Assignee: Nick Boldt > Priority: Blocker > Fix For: 9.0.0.CR1 > > Attachments: jbds3494.png, JBDS_update.png > > > Seeing this in JBDS 9.0.0.beta2.respin-b: > There are no update sites configured - see attached screenshot. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3494) JBDS 9.0.0.beta2 - is preconfigured without an update site

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3494?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-3494: ----------------------------- CDW qa_ack: + (was: ?) > JBDS 9.0.0.beta2 - is preconfigured without an update site > ----------------------------------------------------------- > > Key: JBDS-3494 > URL: https://issues.jboss.org/browse/JBDS-3494 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: updatesite > Affects Versions: 9.0.0.Beta2 > Reporter: Len DiMaggio > Assignee: Nick Boldt > Priority: Blocker > Fix For: 9.0.0.CR1 > > Attachments: jbds3494.png, JBDS_update.png > > > Seeing this in JBDS 9.0.0.beta2.respin-b: > There are no update sites configured - see attached screenshot. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3494) JBDS 9.0.0.beta2 - is preconfigured without an update site

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3494?page=com.atlassian.jira.plugin.... ] Nick Boldt resolved JBDS-3494. ------------------------------ Resolution: Done > JBDS 9.0.0.beta2 - is preconfigured without an update site > ----------------------------------------------------------- > > Key: JBDS-3494 > URL: https://issues.jboss.org/browse/JBDS-3494 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: updatesite > Affects Versions: 9.0.0.Beta2 > Reporter: Len DiMaggio > Assignee: Nick Boldt > Priority: Blocker > Fix For: 9.0.0.CR1 > > Attachments: jbds3494.png, JBDS_update.png > > > Seeing this in JBDS 9.0.0.beta2.respin-b: > There are no update sites configured - see attached screenshot. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20558) org.jboss.tools.common.validation.JBTValidationException at org.jboss.tools.common.validation.AsYouTypeValidatorManager.

by The Alchemist (JIRA)

The Alchemist created JBIDE-20558: ------------------------------------- Summary: org.jboss.tools.common.validation.JBTValidationException at org.jboss.tools.common.validation.AsYouTypeValidatorManager. Key: JBIDE-20558 URL: https://issues.jboss.org/browse/JBIDE-20558 Project: Tools (JBoss Tools) Issue Type: Bug Affects Versions: 4.3.0.Beta2 Reporter: The Alchemist Priority: Minor {noformat} org.jboss.tools.common.validation.JBTValidationException at org.jboss.tools.common.validation.AsYouTypeValidatorManager.validate(AsYouTypeValidatorManager.java:187) at org.jboss.tools.common.validation.AsYouTypeValidatorManager.validateJavaElement(AsYouTypeValidatorManager.java:222) at org.jboss.tools.common.validation.AsYouTypeValidatorManager.validateJavaElement(AsYouTypeValidatorManager.java:217) at org.jboss.tools.common.validation.java.JavaDirtyRegionProcessor.endProcessing(JavaDirtyRegionProcessor.java:507) at org.eclipse.wst.sse.ui.internal.reconcile.DirtyRegionProcessor$BackgroundThread.run(DirtyRegionProcessor.java:697) Caused by: java.lang.NullPointerException at org.jboss.tools.cdi.core.CDIUtil.collectAdditionalInterceptorBindingDeclaratios(CDIUtil.java:1114) at org.jboss.tools.cdi.core.CDIUtil.collectAdditionalInterceptorBindingDeclaratios(CDIUtil.java:1118) at org.jboss.tools.cdi.core.CDIUtil.getAllInterceptorBindingDeclaratios(CDIUtil.java:1110) at org.jboss.tools.cdi.internal.core.validation.CDICoreValidator.hasConflictedInterceptorBindings(CDICoreValidator.java:984) at org.jboss.tools.cdi.internal.core.validation.CDICoreValidator.validateInterceptorBindings(CDICoreValidator.java:970) at org.jboss.tools.cdi.internal.core.validation.CDICoreValidator.validateClassBean(CDICoreValidator.java:952) at org.jboss.tools.cdi.internal.core.validation.CDICoreValidator.validateBean(CDICoreValidator.java:792) at org.jboss.tools.cdi.internal.core.validation.CDICoreValidator.validateResource(CDICoreValidator.java:641) at org.jboss.tools.cdi.internal.core.validation.CDICoreValidator.validate(CDICoreValidator.java:574) at org.jboss.tools.common.validation.AsYouTypeValidatorManager.validate(AsYouTypeValidatorManager.java:183) ... 4 more {noformat} I wish I could see which class is causing this error... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20559) org.jboss.tools.common.validation.JBTValidationException at org.jboss.tools.common.validation.AsYouTypeValidatorManager.

by The Alchemist (JIRA)

The Alchemist created JBIDE-20559: ------------------------------------- Summary: org.jboss.tools.common.validation.JBTValidationException at org.jboss.tools.common.validation.AsYouTypeValidatorManager. Key: JBIDE-20559 URL: https://issues.jboss.org/browse/JBIDE-20559 Project: Tools (JBoss Tools) Issue Type: Bug Affects Versions: 4.3.0.Beta2 Reporter: The Alchemist Priority: Minor {noformat} org.jboss.tools.common.validation.JBTValidationException at org.jboss.tools.common.validation.AsYouTypeValidatorManager.validate(AsYouTypeValidatorManager.java:187) at org.jboss.tools.common.validation.AsYouTypeValidatorManager.validateJavaElement(AsYouTypeValidatorManager.java:222) at org.jboss.tools.common.validation.AsYouTypeValidatorManager.validateJavaElement(AsYouTypeValidatorManager.java:217) at org.jboss.tools.common.validation.java.JavaDirtyRegionProcessor.endProcessing(JavaDirtyRegionProcessor.java:507) at org.eclipse.wst.sse.ui.internal.reconcile.DirtyRegionProcessor$BackgroundThread.run(DirtyRegionProcessor.java:697) Caused by: java.lang.NullPointerException at org.jboss.tools.cdi.core.CDIUtil.collectAdditionalInterceptorBindingDeclaratios(CDIUtil.java:1114) at org.jboss.tools.cdi.core.CDIUtil.collectAdditionalInterceptorBindingDeclaratios(CDIUtil.java:1118) at org.jboss.tools.cdi.core.CDIUtil.getAllInterceptorBindingDeclaratios(CDIUtil.java:1110) at org.jboss.tools.cdi.internal.core.validation.CDICoreValidator.hasConflictedInterceptorBindings(CDICoreValidator.java:984) at org.jboss.tools.cdi.internal.core.validation.CDICoreValidator.validateInterceptorBindings(CDICoreValidator.java:970) at org.jboss.tools.cdi.internal.core.validation.CDICoreValidator.validateClassBean(CDICoreValidator.java:952) at org.jboss.tools.cdi.internal.core.validation.CDICoreValidator.validateBean(CDICoreValidator.java:792) at org.jboss.tools.cdi.internal.core.validation.CDICoreValidator.validateResource(CDICoreValidator.java:641) at org.jboss.tools.cdi.internal.core.validation.CDICoreValidator.validate(CDICoreValidator.java:574) at org.jboss.tools.common.validation.AsYouTypeValidatorManager.validate(AsYouTypeValidatorManager.java:183) ... 4 more {noformat} I wish I could see which class is causing this error... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20557) V3: Finish button is enabled without specified openshift server url

by Rastislav Wagner (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20557?page=com.atlassian.jira.plugi... ] Rastislav Wagner updated JBIDE-20557: ------------------------------------- Steps to Reproduce: 1. Open Openshift explorer view 2. right click -> new -> connection 3. set OPv3, leave server URL blank 4. type in any username/password (basic auth) or any token string (OAuth) FAIL: Finish button gets enabled was: 1. Open Openshift explorer view 2. right click -> new -> connection 3. set OPv3, leave server URL blank 4. type in any username/password (basic auth) or any token strink (OAuth) FAIL: Finish button gets enabled > V3: Finish button is enabled without specified openshift server url > ------------------------------------------------------------------- > > Key: JBIDE-20557 > URL: https://issues.jboss.org/browse/JBIDE-20557 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Beta2 > Reporter: Rastislav Wagner > Fix For: 4.3.0.CR1 > > > Finish button is enabled without defined OSv3 server URL. You can find this message in error log: > {code} > com.openshift.restclient.OpenShiftException: Malformed URL 'null' > at com.openshift.restclient.ClientFactory.create(ClientFactory.java:38) > at org.jboss.tools.openshift.core.connection.ConnectionFactory.create(ConnectionFactory.java:57) > at org.jboss.tools.openshift.core.connection.ConnectionFactory.create(ConnectionFactory.java:50) > at org.jboss.tools.openshift.core.connection.ConnectionFactory.create(ConnectionFactory.java:1) > at org.jboss.tools.openshift.internal.common.ui.connection.ConnectionWizardPageModel.createConnection(ConnectionWizardPageModel.java:331) > at org.jboss.tools.openshift.internal.common.ui.connection.ConnectionWizardPageModel.connect(ConnectionWizardPageModel.java:306) > at org.jboss.tools.openshift.internal.common.ui.connection.ConnectionWizardPage$ConnectJob.doRun(ConnectionWizardPage.java:411) > at org.jboss.tools.openshift.internal.common.core.job.AbstractDelegatingMonitorJob.run(AbstractDelegatingMonitorJob.java:36) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > Caused by: java.net.MalformedURLException > at java.net.URL.<init>(URL.java:620) > at java.net.URL.<init>(URL.java:483) > at java.net.URL.<init>(URL.java:432) > at com.openshift.restclient.ClientFactory.create(ClientFactory.java:36) > ... 8 more > Caused by: java.lang.NullPointerException > at java.net.URL.<init>(URL.java:525) > ... 11 more > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

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