January 2020 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-19663) jst/jsf New and Noteworthy for 4.3.0.Alpha2

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19663?page=com.atlassian.jira.plugi... ] Alexey Kazakov reassigned JBIDE-19663: -------------------------------------- Assignee: Alexey Kazakov > jst/jsf New and Noteworthy for 4.3.0.Alpha2 > ------------------------------------------- > > Key: JBIDE-19663 > URL: https://issues.jboss.org/browse/JBIDE-19663 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: jsf, jsp/jsf/xml/html source editing > Reporter: Alexey Kazakov > Assignee: Alexey Kazakov > Priority: Critical > Fix For: 4.3.0.Alpha2 > > > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...]. > If jst/jsf is not listed here check if there are issues that should be added and add them. > Document the ones relevant for jst/jsf by adding to [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/doc...] and submit a pullrequest. > If no news for this component please reject and close this issue. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

16 hours, 7 minutes

2
1
0 / 0

[JBoss JIRA] (JBDS-3044) Align installation default path with installer filename

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3044?page=com.atlassian.jira.plugin.... ] Nick Boldt edited comment on JBDS-3044 at 5/28/14 10:36 AM: ------------------------------------------------------------ Martin did a quick test on OSX to see what the longest file paths are inside JBDS 8 Beta2: {quote} {code} find jbdevstudio-* |awk '{ print length($0) ; }'|sort|uniq|egrep "2.+" {code} shows 251 as the longest path on Mac so not really safe longest is ./studio/configuration/org.eclipse.osgi/949/data/c7ff8a0a591e0e90fe36069138e75f68/1012-1401176993555/org.springframework.ide.eclipse.core.java.ProjectClassLoaderCache$SourceAndOutputLocationResourceChangeListener$SourceAndOutputLocationResourceVisitor but that is spring and it's data {quote} So we're already pushing the limit here for long paths on Windows / NTFS... Related (with some LOLs): http://blog.codinghorror.com/filesystem-paths-how-long-is-too-long/ There are ways to achieve more-than-260-char paths, but do we want to? was (Author: nickboldt): Martin did a quick test on OSX to see what the longest file paths are inside JBDS 8 Beta2: {quote} {code} find jbdevstudio-* |awk '{ print length($0) ; }'|sort|uniq|egrep "2.+" {code} shows 251 as the longest path on Mac so not really safe longest is ./studio/configuration/org.eclipse.osgi/949/data/c7ff8a0a591e0e90fe36069138e75f68/1012-1401176993555/org.springframework.ide.eclipse.core.java.ProjectClassLoaderCache$SourceAndOutputLocationResourceChangeListener$SourceAndOutputLocationResourceVisitor but that is spring and it's data {quote} So we're already pushing the limit here for long paths on Windows / NTFS... > Align installation default path with installer filename > ------------------------------------------------------- > > Key: JBDS-3044 > URL: https://issues.jboss.org/browse/JBDS-3044 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: installer > Affects Versions: 8.0.0.Beta2 > Reporter: Martin Malina > Assignee: Denis Golovin > Priority: Blocker > Labels: discuss > Fix For: 8.0.0.Beta3 > > > Now that Nick changed the installer filenames to jboss-devstudio in JBIDE-16871 (was jbdevstudio), shouldn't the default install path be changed similarly? Because it just went out of sync. > This question is open for discussion. Nick pointed out some reasons against this suggestion: > {quote} > Martin Malina Re: changing the installation folder, I'll hold off on that change for the moment for a few reasons: > a) Max is AFK, and will want to vet/veto this idea > b) long paths for Windows users (80% of our user base) = bad news, especially considering how long some file paths can get already within Eclipse workspaces > c) short paths for Windows (c:\jbdevstudio) & long paths for everyone else ~/jboss-devstudio) would be ill-advised from a documentation and cross-platform user experience > So, either we stick w/ jbdevstudio, or we shorten to devstudio (losing the "jb" branding fragment). If we move to "jboss-devstudio" we increase the path by only 4 characters. > Max Rydahl Andersen WDYT? > {quote} -- This message was sent by Atlassian JIRA (v6.2.3#6260)

1 month

3
3
0 / 0

[JBoss JIRA] (JBDS-2719) Multiple Spring AOP problems when travel example is imported

by Joshua Wilson (JIRA)

[ https://issues.jboss.org/browse/JBDS-2719?page=com.atlassian.jira.plugin.... ] Joshua Wilson commented on JBDS-2719: ------------------------------------- [~nickboldt] I will need to test several different configurations to confirm my earlier guess. This is what I know so far. First I would ask that you test with the [Kitchensink-Spring Quickstarts|https://github.com/jboss-developer/jboss-wfk-quickstarts] as I am working to keep them up to date and error free as much as possible. This specific error can be seen in the [kitchensink-spring-matrixvariable|https://github.com/jboss-developer/jbos...] quickstart. The Travel and PetClinic will be kept as close to the original as possible (and I haven't had a chance to update them yet). With that in mind if I Build (with Eclipse/JBDS) [kitchensink-spring-matrixvariable|https://github.com/jboss-developer/jbos...] in JBDS 7.0.1 with Spring IDE 3.3 installed from JBoss Central, I get the aspectj error. However if I Build while in a standard Eclipse JEE install with JBDS and the stock Spring IDE/STS 3.4 installed, I do NOT get the aspectj error. In order to truly confirm that adding both "AspectJ Compiler" and "AspectJ Development Tools" will fix the error, I would need to test that on my JBDS 7.0.1/SpringIDE 3.3 set up. > Multiple Spring AOP problems when travel example is imported > ------------------------------------------------------------ > > Key: JBDS-2719 > URL: https://issues.jboss.org/browse/JBDS-2719 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: 3rd-party-certification, upstream > Affects Versions: 7.0.0.GA > Environment: JBDS 7.0.0.GA, L64, Spring IDE 3.3 installed from JBoss Central > Reporter: Jiri Peterka > Assignee: Nick Boldt > Fix For: 7.1.0.Beta1 > > > There are Multiple Spring AOP Errors after travel example is imported: > {code} > Build path is incomplete. Cannot find class file for org/aspectj/weaver/reflect/ReflectionWorld$ReflectionWorldException > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

4 months

2
2
0 / 0

[JBoss JIRA] Created: (JBIDE-5287) Block comment doesn't remove if code selected by 'Ctrl+A' for xhtml file.

by Svetlana Yasenovich (JIRA)

Block comment doesn't remove if code selected by 'Ctrl+A' for xhtml file. ------------------------------------------------------------------------- Key: JBIDE-5287 URL: https://jira.jboss.org/jira/browse/JBIDE-5287 Project: Tools (JBoss Tools) Issue Type: Bug Components: Visual Page Editor core Environment: JBoss Developer Studio Version: 3.0.0.M4 Build id: v200911180352M Reporter: Svetlana Yasenovich Priority: Minor 1. Open .xhtml file. 2. click 'Ctrl+A' -> all code selected 3. click 'Ctrl+Shift+/' (Source->Add Block Comment) ->all code commented 4. click 'Ctrl+A' 5. click 'Ctrl+Shift+\' (Source->Remove Block Comment) -> nothing happened Expected Result : Remove Block Comment for all code -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

6 months

3
7
0 / 0

[JBoss JIRA] (JBIDE-26480) Missing org.eclipse.epp.logging.aeri.ide plugin in devstudio

by Jeff MAURY (Jira)

[ https://issues.redhat.com/browse/JBIDE-26480?page=com.atlassian.jira.plug... ] Jeff MAURY commented on JBIDE-26480: ------------------------------------ I'm wondering if this helps as this bundle is part of our TP. > Missing org.eclipse.epp.logging.aeri.ide plugin in devstudio > ------------------------------------------------------------- > > Key: JBIDE-26480 > URL: https://issues.redhat.com/browse/JBIDE-26480 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: target-platform > Affects Versions: 4.10.0.AM1 > Reporter: Ondrej Dockal > Assignee: Jeff MAURY > Priority: Critical > Fix For: 4.14.0.Final > > > Moving TP from 4.9 to 4.10 caused missing org.eclipse.epp.logging.aeri.ide plugin. > One case how to reproduce this issue is to install RedDeer 2.4.0.M2 (Maybe even older 2.3.0.Final release) which requires aeri.core and aeri.ide plugins to be available. Restarting of devstudio after instalaltion or RD will shows in error log this: > {code} > Error > Tue Nov 20 10:11:03 CET 2018 > FrameworkEvent ERROR > org.osgi.framework.BundleException: Could not resolve module: org.eclipse.reddeer.eclipse.test [1196] > Unresolved requirement: Require-Bundle: org.eclipse.epp.logging.aeri.ide > -> Bundle-SymbolicName: org.eclipse.epp.logging.aeri.ide; bundle-version="2.0.7.v20180504-0806"; singleton:="true" > org.eclipse.epp.logging.aeri.ide [345] > Unresolved requirement: Import-Package: org.apache.lucene.document; version="[7.1.0,8.0.0)" > {code} > This is suggesting that it has something in common with lucene.core plugin. this might help identifying the root cause. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26480) Missing org.eclipse.epp.logging.aeri.ide plugin in devstudio

by Stephane Bouchet (Jira)

[ https://issues.redhat.com/browse/JBIDE-26480?page=com.atlassian.jira.plug... ] Stephane Bouchet commented on JBIDE-26480: ------------------------------------------ We can sync the aeri repository [1] to jboss requirement and use it for our targetplatform since it seems nobody at Eclipse did use it in the SimRel. [~jeffmaury] WDYT ? [1] https://download.eclipse.org/technology/epp/logging/head/ > Missing org.eclipse.epp.logging.aeri.ide plugin in devstudio > ------------------------------------------------------------- > > Key: JBIDE-26480 > URL: https://issues.redhat.com/browse/JBIDE-26480 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: target-platform > Affects Versions: 4.10.0.AM1 > Reporter: Ondrej Dockal > Assignee: Jeff MAURY > Priority: Critical > Fix For: 4.14.0.Final > > > Moving TP from 4.9 to 4.10 caused missing org.eclipse.epp.logging.aeri.ide plugin. > One case how to reproduce this issue is to install RedDeer 2.4.0.M2 (Maybe even older 2.3.0.Final release) which requires aeri.core and aeri.ide plugins to be available. Restarting of devstudio after instalaltion or RD will shows in error log this: > {code} > Error > Tue Nov 20 10:11:03 CET 2018 > FrameworkEvent ERROR > org.osgi.framework.BundleException: Could not resolve module: org.eclipse.reddeer.eclipse.test [1196] > Unresolved requirement: Require-Bundle: org.eclipse.epp.logging.aeri.ide > -> Bundle-SymbolicName: org.eclipse.epp.logging.aeri.ide; bundle-version="2.0.7.v20180504-0806"; singleton:="true" > org.eclipse.epp.logging.aeri.ide [345] > Unresolved requirement: Import-Package: org.apache.lucene.document; version="[7.1.0,8.0.0)" > {code} > This is suggesting that it has something in common with lucene.core plugin. this might help identifying the root cause. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-27026) Adjust Job DSL defined QE Jobs to be operational on RHEV Jenkins CSB Master

by Ondrej Dockal (Jira)

[ https://issues.redhat.com/browse/JBIDE-27026?page=com.atlassian.jira.plug... ] Ondrej Dockal updated JBIDE-27026: ---------------------------------- Description: Please, update Job DSL defined QE jobs to be aligned with Jenkins CSB Master on RHEV. Especially testing matrices of OSes, other configuration tools - Java axes, Groovy or maven, credentials IDs, etc. Your jobs defined in job dsl have to run on RHEV Jenkins. Seed job can be found on dev-platform-jenkins -> DSL Jobs seed -> cci-config-seed, once you are done adjusting your jobs, you can test locally using CCI-JD and then using seed to get it into Jenkins master. Be aware that: * former jenkins labels for OSes and jdks were different from labels defined jenkins using jcasc -> It should be fixed, but you still need to check * You need to sync your credentials IDs (hardcoded in RHEV Jenkins could differ from jcasc defined) * Matrix combination filter should be updated to something like: {code}(label =~ "mac") && !(jdk =~ "open") || !(label =~ "mac") && (jdk =~ "open"){code} * [~jkopriva] is updating and extracting matrices (axes function in job dsl language) to be general and you just use constants of arrays for each axes, ie. OS = ['rhel', 'win'], JDK = ['java11', 'jdk-39'] * After we have jobs running I will disable former QE jobs and these will be erased in next sprint was: Please, update Job DSL defined QE jobs to be aligned with Jenkins CSB Master on RHEV. Especially testing matrices of OSes, other configuration tools - Java axes, Groovy or maven, credentials IDs, etc. Your jobs defined in job dsl have to run on RHEV Jenkins. Seed job can be found on dev-platform-jenkins -> DSL Jobs seed -> cci-config-seed, once you are done adjusting your jobs, you can test locally using CCI-JD and then using seed to get it into Jenkins master. > Adjust Job DSL defined QE Jobs to be operational on RHEV Jenkins CSB Master > --------------------------------------------------------------------------- > > Key: JBIDE-27026 > URL: https://issues.redhat.com/browse/JBIDE-27026 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: integration-tests, qa > Affects Versions: 4.14.0.Final > Reporter: Ondrej Dockal > Assignee: Ondrej Dockal > Priority: Critical > Fix For: 4.14.0.Final > > > Please, update Job DSL defined QE jobs to be aligned with Jenkins CSB Master on RHEV. Especially testing matrices of OSes, other configuration tools - Java axes, Groovy or maven, credentials IDs, etc. > Your jobs defined in job dsl have to run on RHEV Jenkins. Seed job can be found on dev-platform-jenkins -> DSL Jobs seed -> cci-config-seed, once you are done adjusting your jobs, you can test locally using CCI-JD and then using seed to get it into Jenkins master. > Be aware that: > * former jenkins labels for OSes and jdks were different from labels defined jenkins using jcasc -> It should be fixed, but you still need to check > * You need to sync your credentials IDs (hardcoded in RHEV Jenkins could differ from jcasc defined) > * Matrix combination filter should be updated to something like: {code}(label =~ "mac") && !(jdk =~ "open") || !(label =~ "mac") && (jdk =~ "open"){code} > * [~jkopriva] is updating and extracting matrices (axes function in job dsl language) to be general and you just use constants of arrays for each axes, ie. OS = ['rhel', 'win'], JDK = ['java11', 'jdk-39'] > * After we have jobs running I will disable former QE jobs and these will be erased in next sprint -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26973) Update 4.14.0.Final Target Platform (Docker tooling, ...) for 2019-12.GA

by Stephane Bouchet (Jira)

[ https://issues.redhat.com/browse/JBIDE-26973?page=com.atlassian.jira.plug... ] Stephane Bouchet commented on JBIDE-26973: ------------------------------------------ [~jsteele] : after looking at the pom.xml of the windup repo, i think adding back the missing bundle into the base target platform should be easier. i'll update and let you know. > Update 4.14.0.Final Target Platform (Docker tooling, ...) for 2019-12.GA > ------------------------------------------------------------------------ > > Key: JBIDE-26973 > URL: https://issues.redhat.com/browse/JBIDE-26973 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: target-platform > Affects Versions: 4.14.0.AM1 > Reporter: Jeff MAURY > Assignee: Stephane Bouchet > Priority: Major > Fix For: 4.14.0.Final > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-27015) Add support for Widlfy 19

by Jeff MAURY (Jira)

[ https://issues.redhat.com/browse/JBIDE-27015?page=com.atlassian.jira.plug... ] Jeff MAURY updated JBIDE-27015: ------------------------------- Fix Version/s: 4.14.x > Add support for Widlfy 19 > ------------------------- > > Key: JBIDE-27015 > URL: https://issues.redhat.com/browse/JBIDE-27015 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: server > Affects Versions: 4.14.0.AM1 > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Priority: Major > Fix For: 4.14.x > > > WF 19 is scheduled Jan 30. But there may be a delay of a couple of weeks so in that case we won't be able to make it for 4.14.0.Final so it will be for 4.15.0.AM1 -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26973) Update 4.14.0.Final Target Platform (Docker tooling, ...) for 2019-12.GA

by John Steele (Jira)

[ https://issues.redhat.com/browse/JBIDE-26973?page=com.atlassian.jira.plug... ] John Steele edited comment on JBIDE-26973 at 1/30/20 1:23 PM: -------------------------------------------------------------- [~stephane.bouchet] How about for the maven build? What needs to be added so it can build? Do I need to add another repository location? was (Author: jsteele): [~stephane.bouchet] How about for the maven build? What needs to be added so it can build? > Update 4.14.0.Final Target Platform (Docker tooling, ...) for 2019-12.GA > ------------------------------------------------------------------------ > > Key: JBIDE-26973 > URL: https://issues.redhat.com/browse/JBIDE-26973 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: target-platform > Affects Versions: 4.14.0.AM1 > Reporter: Jeff MAURY > Assignee: Stephane Bouchet > Priority: Major > Fix For: 4.14.0.Final > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues January 2020