December 2019 - jbosstools-issues

[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)

3 weeks, 5 days

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-26987) Deprecate vpe/forge/jst components

by Jeff MAURY (Jira)

[ https://issues.redhat.com/browse/JBIDE-26987?page=com.atlassian.jira.plug... ] Jeff MAURY commented on JBIDE-26987: ------------------------------------ I would vote for the second option, it is important to state that it is not supported again. > Deprecate vpe/forge/jst components > ---------------------------------- > > Key: JBIDE-26987 > URL: https://issues.redhat.com/browse/JBIDE-26987 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: central, forge, jst, visual-page-editor-core > Affects Versions: 4.13.0.Final > Reporter: Stephane Bouchet > Assignee: Jeff MAURY > Priority: Major > Fix For: 4.14.0.Final > > Attachments: Capture d’écran de 2019-12-19 10-55-02.png, Capture d’écran de 2019-12-19 10-55-16.png > > > Mark following components as not fully tested anymore : > - VPE > - Forge > - JST > The task is to communicate theses components are not yet removed from JBossTools/Studio, but are not anymore fully tested. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26987) Deprecate vpe/forge/jst components

by Supriya Takkhi (Jira)

[ https://issues.redhat.com/browse/JBIDE-26987?page=com.atlassian.jira.plug... ] Supriya Takkhi commented on JBIDE-26987: ---------------------------------------- Hello [~stephane.bouchet] and [~jeffmaury]. Here is what I have right now: "Although the Forge tooling is a part of the current release of Red Hat CodeReady Studio, it is not tested anymore." To me, this is vague. Should we not tell the user about it not being supported anymore. Better still, sate: Although the Forge tooling is a part of the current release of Red Hat CodeReady Studio, it is not tested and is not supported starting with version <studio-version>." Please let me know what you both think about this. Thanks! > Deprecate vpe/forge/jst components > ---------------------------------- > > Key: JBIDE-26987 > URL: https://issues.redhat.com/browse/JBIDE-26987 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: central, forge, jst, visual-page-editor-core > Affects Versions: 4.13.0.Final > Reporter: Stephane Bouchet > Assignee: Jeff MAURY > Priority: Major > Fix For: 4.14.0.Final > > Attachments: Capture d’écran de 2019-12-19 10-55-02.png, Capture d’écran de 2019-12-19 10-55-16.png > > > Mark following components as not fully tested anymore : > - VPE > - Forge > - JST > The task is to communicate theses components are not yet removed from JBossTools/Studio, but are not anymore fully tested. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26989) pre select default extensions

by Jeff MAURY (Jira)

Jeff MAURY created JBIDE-26989: ---------------------------------- Summary: pre select default extensions Key: JBIDE-26989 URL: https://issues.redhat.com/browse/JBIDE-26989 Project: Tools (JBoss Tools) Issue Type: Bug Components: quarkus Affects Versions: 4.14.0.AM1 Reporter: Jeff MAURY Assignee: Jeff MAURY Fix For: 4.14.0.AM1 The extensions model has the notion of default extensions. Such extensions should be pre selected when launching the wizard -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26791) Migration of QE Infra provisioning jobs under dev-platform/cci-config

by Ondrej Dockal (Jira)

[ https://issues.redhat.com/browse/JBIDE-26791?page=com.atlassian.jira.plug... ] Ondrej Dockal updated JBIDE-26791: ---------------------------------- Fix Version/s: 4.14.x (was: 4.14.0.AM1) > Migration of QE Infra provisioning jobs under dev-platform/cci-config > --------------------------------------------------------------------- > > Key: JBIDE-26791 > URL: https://issues.redhat.com/browse/JBIDE-26791 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: qa > Affects Versions: 4.13.0.AM1 > Reporter: Ondrej Dockal > Assignee: Ondrej Dockal > Priority: Major > Fix For: 4.14.x > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26760) Migrate QE integration tests jobs into job DSL under dev-platform/cci-config repo

by Ondrej Dockal (Jira)

[ https://issues.redhat.com/browse/JBIDE-26760?page=com.atlassian.jira.plug... ] Ondrej Dockal resolved JBIDE-26760. ----------------------------------- Resolution: Done > Migrate QE integration tests jobs into job DSL under dev-platform/cci-config repo > --------------------------------------------------------------------------------- > > Key: JBIDE-26760 > URL: https://issues.redhat.com/browse/JBIDE-26760 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: integration-tests, qa > Affects Versions: 4.13.0.Final > Reporter: Ondrej Dockal > Assignee: Ondrej Dockal > Priority: Critical > Labels: integration_tests, jenkins, jenkins_pipeline > Fix For: 4.14.0.AM1 > > > As a part of QE - CI initiative and its out coming best practices, we need to move our QE and Infra jobs into job DSL. New repository that will be used to store jobs as a code ( job DSL) is here [1]. Migrate according to the QE - CI initiative best practices. > *Job migration workflow:* > * Check on best practices and migrate job according to them, use existing examples of already migrated jobs > * Verify that migration is successful by running it locally using jcasc [2]. And share the test results in your sub-tasks jira. > * Create a PR and notify your component backup to get +1 on the PR. > *Best Practices* > * [Authentication & Credentials|https://docs.engineering.redhat.com/pages/viewpage.action?pag...] > * [Execution Scripts|https://docs.engineering.redhat.com/display/QEARCH/Execution+Scripts] > * [Jenkins Job generation|https://docs.engineering.redhat.com/display/QEARCH/Jenkins+Job...] > * [Jenkins Job Types|https://docs.engineering.redhat.com/display/QEARCH/Jenkins+Job+Types] > * [Job Triggers|https://docs.engineering.redhat.com/display/QEARCH/Job+Triggers] > * [Resource Ready|https://docs.engineering.redhat.com/display/QEARCH/Resource+Ready] > * [SCM|https://docs.engineering.redhat.com/display/QEARCH/SCM] > Some other are still in doing: > * [Provisioning|https://docs.google.com/document/d/1p-MJB6vP1oZXXFr2qscopkEo...] > * [Job Parameters|https://docs.engineering.redhat.com/display/QEARCH/Job+Parameters] > * [Data Usage and Retention|https://docs.engineering.redhat.com/display/QEARCH/Data+Usage+a...] > [1]: https://gitlab.mw.lab.eng.bos.redhat.com/dev-platform/cci-config > [2]: https://gitlab.mw.lab.eng.bos.redhat.com/jbossqe-jenkins/jcasc -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26988) Mark old EAP runtimes not fully supported anymore

by Supriya Takkhi (Jira)

[ https://issues.redhat.com/browse/JBIDE-26988?page=com.atlassian.jira.plug... ] Supriya Takkhi commented on JBIDE-26988: ---------------------------------------- Thanks for letting me know about this, [~jkopriva]! I have created an RHDEVDOCS JIRA for this and have added it to a future sprint. Shall get this done for the 12.14 CRS release. > Mark old EAP runtimes not fully supported anymore > ------------------------------------------------- > > Key: JBIDE-26988 > URL: https://issues.redhat.com/browse/JBIDE-26988 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: server > Affects Versions: 4.14.0.AM1 > Reporter: Stephane Bouchet > Assignee: Jeff MAURY > Priority: Major > Fix For: 4.14.0.Final > > > EAP 5.x and 6.x are out of Maintenance support as of today, we should mark them as not fully tested anymore, but not remove them off. > see https://access.redhat.com/support/policy/updates/jboss_notes for dates. > also this article should be updated : https://access.redhat.com/articles/113373 -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26988) Mark old EAP runtimes not fully supported anymore

by Supriya Takkhi (Jira)

[ https://issues.redhat.com/browse/JBIDE-26988?page=com.atlassian.jira.plug... ] Supriya Takkhi edited comment on JBIDE-26988 at 12/20/19 5:09 AM: ------------------------------------------------------------------ Thanks for letting me know about this, [~jkopriva]! I have created an RHDEVDOCS JIRA (https://issues.redhat.com/browse/RHDEVDOCS-1541) for this and have added it to a future sprint. Shall get this done for the 12.14 CRS release. was (Author: supriya.bharadwaj): Thanks for letting me know about this, [~jkopriva]! I have created an RHDEVDOCS JIRA for this and have added it to a future sprint. Shall get this done for the 12.14 CRS release. > Mark old EAP runtimes not fully supported anymore > ------------------------------------------------- > > Key: JBIDE-26988 > URL: https://issues.redhat.com/browse/JBIDE-26988 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: server > Affects Versions: 4.14.0.AM1 > Reporter: Stephane Bouchet > Assignee: Jeff MAURY > Priority: Major > Fix For: 4.14.0.Final > > > EAP 5.x and 6.x are out of Maintenance support as of today, we should mark them as not fully tested anymore, but not remove them off. > see https://access.redhat.com/support/policy/updates/jboss_notes for dates. > also this article should be updated : https://access.redhat.com/articles/113373 -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 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 December 2019