December 2016 - jbosstools-issues

[JBoss JIRA] (JBDS-4146) Updating the index from remote ‘https://aer.ctrlflow.com/downloads/redhat/problems.zip’ failed with exception: org.apache.lucene.index.IndexFormatTooOldException

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4146?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-4146: ----------------------------- Fix Version/s: 10.3.0.GA (was: 10.2.0.GA) > Updating the index from remote ‘https://aer.ctrlflow.com/downloads/redhat/problems.zip’ failed with exception: org.apache.lucene.index.IndexFormatTooOldException > ----------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBDS-4146 > URL: https://issues.jboss.org/browse/JBDS-4146 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: build, rpm, webservices > Affects Versions: 10.2.0.AM2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Minor > Fix For: 10.3.0.GA > > Attachments: aeri-bug-for-eclipse.org-and-jbosstools-reporting.png, eclipse-log-after-new-workspace.png, rh-eclipse46-devstudio10.2.log.20161102-1855.txt > > > As of the latest rpm build [1] I'm only getting this one error now: > {code}!ENTRY org.eclipse.epp.logging.aeri.ide 2 10 2016-10-28 14:32:25.075 > !MESSAGE Updating the index from remote ‘https://aer.ctrlflow.com/downloads/redhat/problems.zip’ failed with exception: org.apache.lucene.index.IndexFormatTooOldException: Format version is not supported (resource BufferedChecksumIndexInput(MMapIndexInput(path="/tmp/1477679545041-0/segments_1"))): -11 (needs to be between 1071082519 and 1071082519). This version of Lucene only supports indexes created with release 4.0 and later. ; version: 2.0.3.201610111629 > !STACK 0 > org.eclipse.epp.logging.aeri.core.util.Logs$LogTraceException > at org.eclipse.epp.logging.aeri.core.util.Logs$LogTraceException.newTrace(Logs.java:387) > at org.eclipse.epp.logging.aeri.core.util.Logs.log(Logs.java:134) > at org.eclipse.epp.internal.logging.aeri.ide.server.mars.ServerProblemsHistory$UpdateIndexJob.run(ServerProblemsHistory.java:322) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4152) On Windows, list of checkbox is unreadable if you try to select or unselect a line

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBDS-4152?page=com.atlassian.jira.plugin.... ] Paul Leacu commented on JBDS-4152: ---------------------------------- To try - see: http://download.jboss.org/jbosstools/neon/staging/updates/integration-sta... http://download.jboss.org/jbosstools/neon/staging/updates/integration-sta... ref: !inst1.png|thumbnail! > On Windows, list of checkbox is unreadable if you try to select or unselect a line > ---------------------------------------------------------------------------------- > > Key: JBDS-4152 > URL: https://issues.jboss.org/browse/JBDS-4152 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: installer > Affects Versions: 10.1.0.GA > Reporter: Aurélien Pupier > Assignee: Paul Leacu > Fix For: 10.3.0.AM1 > > Attachments: inst1.png, unreadable.png > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4152) On Windows, list of checkbox is unreadable if you try to select or unselect a line

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBDS-4152?page=com.atlassian.jira.plugin.... ] Paul Leacu updated JBDS-4152: ----------------------------- Attachment: inst1.png > On Windows, list of checkbox is unreadable if you try to select or unselect a line > ---------------------------------------------------------------------------------- > > Key: JBDS-4152 > URL: https://issues.jboss.org/browse/JBDS-4152 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: installer > Affects Versions: 10.1.0.GA > Reporter: Aurélien Pupier > Assignee: Paul Leacu > Fix For: 10.3.0.AM1 > > Attachments: inst1.png, unreadable.png > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23626) Preferences: link to download oc may lead me to try to use an incompatible oc binary for my origin/CDK

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23626?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23626: ------------------------------------- Description: oc 1.4, which is available from github is not compatible with the lastest CDK 2.3 (it's only compatible oc 1.3). Futhermore there are specific enterprise oc binaries which follow the OSE versioning scheme 3.2, 3.3 etc. making it hard for the user to know what oc he should use. Our preferences offer a link to the github releases but there's no info nor logic that makes sure that the user will use compatible combinations (oc 1.4 with CDK 2.3, oc 1.2 with CDK 2.3 etc.) was: oc 1.4, which is available from github is not compatible with the lastest CDK 2.3. Futhermore there are specific enterprise oc binaries which follow the OSE versioning scheme 3.2, 3.3 etc. making it hard for the user to know what oc he should use. Our preferences offer a link to the github releases but there's no info nor logic that makes sure that the user will use incompatible combinations (oc 1.4 with CDK 2.3, oc 1.2 with CDK 2.3 etc.) > Preferences: link to download oc may lead me to try to use an incompatible oc binary for my origin/CDK > ------------------------------------------------------------------------------------------------------ > > Key: JBIDE-23626 > URL: https://issues.jboss.org/browse/JBIDE-23626 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.2.AM3 > Reporter: Andre Dietisheim > Labels: oc_binary, preferences > Fix For: 4.4.3.AM1 > > > oc 1.4, which is available from github is not compatible with the lastest CDK 2.3 (it's only compatible oc 1.3). Futhermore there are specific enterprise oc binaries which follow the OSE versioning scheme 3.2, 3.3 etc. making it hard for the user to know what oc he should use. > Our preferences offer a link to the github releases but there's no info nor logic that makes sure that the user will use compatible combinations (oc 1.4 with CDK 2.3, oc 1.2 with CDK 2.3 etc.) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23626) Preferences: link to download oc may lead me to try to use an incompatible oc binary for my origin/CDK

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23626?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23626: ------------------------------------- Summary: Preferences: link to download oc may lead me to try to use an incompatible oc binary for my origin/CDK (was: Preferences: as a user I can easily end up using an incompatible oc binary for my origin/CDK) > Preferences: link to download oc may lead me to try to use an incompatible oc binary for my origin/CDK > ------------------------------------------------------------------------------------------------------ > > Key: JBIDE-23626 > URL: https://issues.jboss.org/browse/JBIDE-23626 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.2.AM3 > Reporter: Andre Dietisheim > Labels: oc_binary, preferences > Fix For: 4.4.3.AM1 > > > oc 1.4, which is available from github is not compatible with the lastest CDK 2.3. Futhermore there are specific enterprise oc binaries which follow the OSE versioning scheme 3.2, 3.3 etc. making it hard for the user to know what oc he should use. > Our preferences offer a link to the github releases but there's no info nor logic that makes sure that the user will use incompatible combinations (oc 1.4 with CDK 2.3, oc 1.2 with CDK 2.3 etc.) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23626) Preferences: as a user I can easily end up using an incompatible oc binary for my origin/CDK

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23626?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23626: ------------------------------------- Fix Version/s: 4.4.3.AM1 > Preferences: as a user I can easily end up using an incompatible oc binary for my origin/CDK > -------------------------------------------------------------------------------------------- > > Key: JBIDE-23626 > URL: https://issues.jboss.org/browse/JBIDE-23626 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.2.AM3 > Reporter: Andre Dietisheim > Labels: oc_binary, preferences > Fix For: 4.4.3.AM1 > > > oc 1.4, which is available from github is not compatible with the lastest CDK 2.3. Futhermore there are specific enterprise oc binaries which follow the OSE versioning scheme 3.2, 3.3 etc. making it hard for the user to know what oc he should use. > Our preferences offer a link to the github releases but there's no info nor logic that makes sure that the user will use incompatible combinations (oc 1.4 with CDK 2.3, oc 1.2 with CDK 2.3 etc.) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23626) Preferences: as a user I can easily end up using an incompatible oc binary for my origin/CDK

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23626?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23626: ------------------------------------- Labels: oc_binary preferences (was: ) > Preferences: as a user I can easily end up using an incompatible oc binary for my origin/CDK > -------------------------------------------------------------------------------------------- > > Key: JBIDE-23626 > URL: https://issues.jboss.org/browse/JBIDE-23626 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.2.AM3 > Reporter: Andre Dietisheim > Labels: oc_binary, preferences > Fix For: 4.4.3.AM1 > > > oc 1.4, which is available from github is not compatible with the lastest CDK 2.3. Futhermore there are specific enterprise oc binaries which follow the OSE versioning scheme 3.2, 3.3 etc. making it hard for the user to know what oc he should use. > Our preferences offer a link to the github releases but there's no info nor logic that makes sure that the user will use incompatible combinations (oc 1.4 with CDK 2.3, oc 1.2 with CDK 2.3 etc.) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23626) Preferences: as a user I can easily end up using an incompatible oc binary for my origin/CDK

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23626?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-23626: ------------------------------------------ CC [~rob.stryker] > Preferences: as a user I can easily end up using an incompatible oc binary for my origin/CDK > -------------------------------------------------------------------------------------------- > > Key: JBIDE-23626 > URL: https://issues.jboss.org/browse/JBIDE-23626 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.2.AM3 > Reporter: Andre Dietisheim > > oc 1.4, which is available from github is not compatible with the lastest CDK 2.3. Futhermore there are specific enterprise oc binaries which follow the OSE versioning scheme 3.2, 3.3 etc. making it hard for the user to know what oc he should use. > Our preferences offer a link to the github releases but there's no info nor logic that makes sure that the user will use incompatible combinations (oc 1.4 with CDK 2.3, oc 1.2 with CDK 2.3 etc.) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23626) Preferences: as a user I can easily end up using an incompatible oc binary for my origin/CDK

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23626?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23626: ------------------------------------- Summary: Preferences: as a user I can easily end up using an incompatible oc binary for my origin/CDK (was: Preferences: as a user I can easily end up using an incompatible oc binary) > Preferences: as a user I can easily end up using an incompatible oc binary for my origin/CDK > -------------------------------------------------------------------------------------------- > > Key: JBIDE-23626 > URL: https://issues.jboss.org/browse/JBIDE-23626 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.2.AM3 > Reporter: Andre Dietisheim > > oc 1.4, which is available from github is not compatible with the lastest CDK 2.3. Futhermore there are specific enterprise oc binaries which follow the OSE versioning scheme 3.2, 3.3 etc. making it hard for the user to know what oc he should use. > Our preferences offer a link to the github releases but there's no info nor logic that makes sure that the user will use incompatible combinations (oc 1.4 with CDK 2.3, oc 1.2 with CDK 2.3 etc.) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23626) Preferences: as a user I can easily end up using an incompatible oc binary

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23626?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23626: ------------------------------------- Description: oc 1.4, which is available from github is not compatible with the lastest CDK 2.3. Futhermore there are specific enterprise oc binaries which follow the OSE versioning scheme 3.2, 3.3 etc. making it hard for the user to know what oc he should use. Our preferences offer a link to the github releases but there's no info nor logic that makes sure that the user will use incompatible combinations (oc 1.4 with CDK 2.3, oc 1.2 with CDK 2.3 etc.) was: oc 1.4, which is available from github is not compatible with the lastest CDK 2.3. Futhermore there are specific enterprise oc binaries which follow the OSE versioning scheme 3.2, 3.3 etc. making it hard for the user to know what oc he should use. Our preferences offer a link to the github releases but there's no info nor logic that makes sure that the user will use incompatible combinations (oc 1.4 with CDK 2.3 etc.) > Preferences: as a user I can easily end up using an incompatible oc binary > -------------------------------------------------------------------------- > > Key: JBIDE-23626 > URL: https://issues.jboss.org/browse/JBIDE-23626 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.2.AM3 > Reporter: Andre Dietisheim > > oc 1.4, which is available from github is not compatible with the lastest CDK 2.3. Futhermore there are specific enterprise oc binaries which follow the OSE versioning scheme 3.2, 3.3 etc. making it hard for the user to know what oc he should use. > Our preferences offer a link to the github releases but there's no info nor logic that makes sure that the user will use incompatible combinations (oc 1.4 with CDK 2.3, oc 1.2 with CDK 2.3 etc.) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 10 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues December 2016