May 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-22460) Test classes should be in the same package as the class(es) under test

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22460?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-22460: ------------------------------------- I'm all for it, if only to be able to use [moreunit|http://moreunit.sourceforge.net/], However the big caveat is testing package protected methods doesn't work with OSGi projects, for some reason. Unless I missed something. It might work when using fragments, but I'm not sure. > Test classes should be in the same package as the class(es) under test > ----------------------------------------------------------------------- > > Key: JBIDE-22460 > URL: https://issues.jboss.org/browse/JBIDE-22460 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.0.Alpha2 > Reporter: Jeff MAURY > Priority: Minor > Labels: test > Fix For: 4.4.x > > > Test classes should be in the same package as the class(es) under test as it is a generally admitted pattern and as it allows to use package protected classes/methods -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22459) Figure out impact of adding EAP 7 to DCP and what changes DCP has that might affect Central

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22459?page=com.atlassian.jira.plugi... ] Fred Bricon edited comment on JBIDE-22459 at 5/30/16 9:38 AM: -------------------------------------------------------------- [~lkrzyzanek] the sys_type parameter we can change without any issue, as long as it yields the same results. I honestly don't remember how I came up with the hack version (either I was told, saw it used elsewhere or figured it out myself). The output format is definitely, absolutely not the same as in v1, as most fields are returned as arrays instead of simple values, this definitely breaks our parsing in JBDS 9 (and 10 currently). If the output could be the exact same as v1, then we could switch over to v2 without sweating. We'd only lose the help search feature eventually. As for the result limit set to 500, this is to allow us to perform only 1 query, do the appropriate processing on the results and present them to the user. Filtering in Central doesn't do any round trips to the server. The search is cached for offline use. Search is performed every time Central is opened (which is *usually* once every time you open Eclipse). We can add more identifying parameters to the search query if you need, to help you log usage. was (Author: fbricon): [~lkrzyzanek] the sys_type parameter we can change without any issue, as long as it yields the same results. I honestly don't remember how I came up with the hack version (either I was told, saw it used elsewhere or figured it out myself). The output format is definitely, absolutely not the same as in v1, as most fields are returned as arrays instead of simple values, this definitely breaks our parsing in JBDS 9 (and 10 currently). If the output could be the exact same as v1, then we could switch over to v2 without sweating. We'd only loose the help search feature eventually. As for the result limit set to 500, this is to allow us to perform only 1 query, do the appropriate processing on the results and present them to the user. Filtering in Central doesn't do any round trips to the server. The search is cached for offline use. Search is performed every time Central is opened (which is *usually* once every time you open Eclipse). We can add more identifying parameters to the search query if you need, to help you log usage. > Figure out impact of adding EAP 7 to DCP and what changes DCP has that might affect Central > ------------------------------------------------------------------------------------------- > > Key: JBIDE-22459 > URL: https://issues.jboss.org/browse/JBIDE-22459 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: central > Reporter: Max Rydahl Andersen > Assignee: Fred Bricon > Priority: Blocker > > ~1 year ago we made Central use DCP for querying the quickstart list to let users start easily with the examples/quickstrats. > In the context of EAP 7 coming out there are new quickstarts. > In a perfect world the following have happend: > EAP 7 Quickstarts added to DCP > Central in both devstudio 9 and 10 can see both EAP 6 and EAP 7 quickstarts > What seem to have happened instead is: > if EAP 7 quickstarts are added to DCP EAP 6 quickstarts are no longer available > DCP has changed its format/approach and not sure what the impact of this is > (can devstudio 9 still work ? must devstudio 10 change ? will we ever have multiple version support ?) > This bug is to gather the facts and figure out what we do about them. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22459) Figure out impact of adding EAP 7 to DCP and what changes DCP has that might affect Central

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22459?page=com.atlassian.jira.plugi... ] Fred Bricon edited comment on JBIDE-22459 at 5/30/16 9:36 AM: -------------------------------------------------------------- [~lkrzyzanek] the sys_type parameter we can change without any issue, as long as it yields the same results. I honestly don't remember how I came up with the hack version (either I was told, saw it used elsewhere or figured it out myself). The output format is definitely, absolutely not the same as in v1, as most fields are returned as arrays instead of simple values, this definitely breaks our parsing in JBDS 9 (and 10 currently). If the output could be the exact same as v1, then we could switch over to v2 without sweating. We'd only loose the help search feature eventually. As for the result limit set to 500, this is to allow us to perform only 1 query, do the appropriate processing on the results and present them to the user. Filtering in Central doesn't do any round trips to the server. The search is cached for offline use. Search is performed every time Central is opened (which is *usually* once every time you open Eclipse). We can add more identifying parameters to the search query if you need, to help you log usage. was (Author: fbricon): [~lkrzyzanek] the sys_type parameter we can change without any issue, as long as it yields the same results. I honestly don't remember how I came up with the hack version (either I was told, saw it used elsewhere or figured it out myself). The output format is definitely, absolutely not the same as in v1, as most fields are returned as arrays instead of simple values, this definitely breaks our parsing in JBDS 9 (and 10 currently). If the output could be the exact same as v1, then we could switch over to v2 without sweating. We'd only use the help search feature eventually. As for the result limit set to 500, this is to allow us to perform only 1 query, do the appropriate processing on the results and present them to the user. Filtering in Central doesn't do any round trips to the server. The search is cached for offline use. Search is performed every time Central is opened (which is *usually* once every time you open Eclipse). We can add more identifying parameters to the search query if you need, to help you log usage. > Figure out impact of adding EAP 7 to DCP and what changes DCP has that might affect Central > ------------------------------------------------------------------------------------------- > > Key: JBIDE-22459 > URL: https://issues.jboss.org/browse/JBIDE-22459 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: central > Reporter: Max Rydahl Andersen > Assignee: Fred Bricon > Priority: Blocker > > ~1 year ago we made Central use DCP for querying the quickstart list to let users start easily with the examples/quickstrats. > In the context of EAP 7 coming out there are new quickstarts. > In a perfect world the following have happend: > EAP 7 Quickstarts added to DCP > Central in both devstudio 9 and 10 can see both EAP 6 and EAP 7 quickstarts > What seem to have happened instead is: > if EAP 7 quickstarts are added to DCP EAP 6 quickstarts are no longer available > DCP has changed its format/approach and not sure what the impact of this is > (can devstudio 9 still work ? must devstudio 10 change ? will we ever have multiple version support ?) > This bug is to gather the facts and figure out what we do about them. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22411) update TPs to latest Docker/Vagrant tooling

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22411?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-22411: ---------------------------------------- [~xcoulon] Is there a jbosstools component that depend on Docker Tools, or is it "just" included in JBT site and Developer Studio? > update TPs to latest Docker/Vagrant tooling > ------------------------------------------- > > Key: JBIDE-22411 > URL: https://issues.jboss.org/browse/JBIDE-22411 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: docker > Affects Versions: 4.4.0.Alpha2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.0.Alpha3 > > > Latest Docker tooling from Linux Tools can be found at: http://download.eclipse.org/linuxtools/update-neon-docker-rc2 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22459) Figure out impact of adding EAP 7 to DCP and what changes DCP has that might affect Central

by Libor Krzyžanek (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22459?page=com.atlassian.jira.plugi... ] Libor Krzyžanek commented on JBIDE-22459: ----------------------------------------- I guess you used the hack way because you saw that. I remember that someone on jboss.org website started using it and others copied. Result - sorry I totally forgot about that. You're right about arrays vs. simple strings. That's breaking. I guess the quick workaround is to push quickstarts to DCP1. Right ? Limit - yep it sounds good to me know. > Figure out impact of adding EAP 7 to DCP and what changes DCP has that might affect Central > ------------------------------------------------------------------------------------------- > > Key: JBIDE-22459 > URL: https://issues.jboss.org/browse/JBIDE-22459 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: central > Reporter: Max Rydahl Andersen > Assignee: Fred Bricon > Priority: Blocker > > ~1 year ago we made Central use DCP for querying the quickstart list to let users start easily with the examples/quickstrats. > In the context of EAP 7 coming out there are new quickstarts. > In a perfect world the following have happend: > EAP 7 Quickstarts added to DCP > Central in both devstudio 9 and 10 can see both EAP 6 and EAP 7 quickstarts > What seem to have happened instead is: > if EAP 7 quickstarts are added to DCP EAP 6 quickstarts are no longer available > DCP has changed its format/approach and not sure what the impact of this is > (can devstudio 9 still work ? must devstudio 10 change ? will we ever have multiple version support ?) > This bug is to gather the facts and figure out what we do about them. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22459) Figure out impact of adding EAP 7 to DCP and what changes DCP has that might affect Central

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22459?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-22459: ------------------------------------- [~lkrzyzanek] the sys_type parameter we can change without any issue, as long as it yields the same results. I honestly don't remember how I came up with the hack version (either I was told, saw it used elsewhere or figured it out myself). The output format is definitely, absolutely not the same as in v1, as most fields are returned as arrays instead of simple values, this definitely breaks our parsing in JBDS 9 (and 10 currently). If the output could be the exact same as v1, then we could switch over to v2 without sweating. We'd only use the help search feature eventually. As for the result limit set to 500, this is to allow us to perform only 1 query, do the appropriate processing on the results and present them to the user. Filtering in Central doesn't do any round trips to the server. The search is cached for offline use. Search is performed every time Central is opened (which is *usually* once every time you open Eclipse). We can add more identifying parameters to the search query if you need, to help you log usage. > Figure out impact of adding EAP 7 to DCP and what changes DCP has that might affect Central > ------------------------------------------------------------------------------------------- > > Key: JBIDE-22459 > URL: https://issues.jboss.org/browse/JBIDE-22459 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: central > Reporter: Max Rydahl Andersen > Assignee: Fred Bricon > Priority: Blocker > > ~1 year ago we made Central use DCP for querying the quickstart list to let users start easily with the examples/quickstrats. > In the context of EAP 7 coming out there are new quickstarts. > In a perfect world the following have happend: > EAP 7 Quickstarts added to DCP > Central in both devstudio 9 and 10 can see both EAP 6 and EAP 7 quickstarts > What seem to have happened instead is: > if EAP 7 quickstarts are added to DCP EAP 6 quickstarts are no longer available > DCP has changed its format/approach and not sure what the impact of this is > (can devstudio 9 still work ? must devstudio 10 change ? will we ever have multiple version support ?) > This bug is to gather the facts and figure out what we do about them. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22461) JPA Generate Entities does not generate entities

by George Gastaldi (JIRA)

George Gastaldi created JBIDE-22461: --------------------------------------- Summary: JPA Generate Entities does not generate entities Key: JBIDE-22461 URL: https://issues.jboss.org/browse/JBIDE-22461 Project: Tools (JBoss Tools) Issue Type: Bug Components: forge Affects Versions: 4.4.0.Alpha2 Reporter: Pavol Srna Assignee: George Gastaldi Priority: Critical Fix For: 4.4.x There is no exception in error log. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22411) update TPs to latest Docker/Vagrant tooling

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22411?page=com.atlassian.jira.plugi... ] Xavier Coulon commented on JBIDE-22411: --------------------------------------- [~mickael_istria] this looks good to me. > update TPs to latest Docker/Vagrant tooling > ------------------------------------------- > > Key: JBIDE-22411 > URL: https://issues.jboss.org/browse/JBIDE-22411 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: docker > Affects Versions: 4.4.0.Alpha2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.0.Alpha3 > > > Latest Docker tooling from Linux Tools can be found at: http://download.eclipse.org/linuxtools/update-neon-docker-rc2 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22415) Target Platform PR build should produce both ignoreVerions and "honorVersion" p2diff

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22415?page=com.atlassian.jira.plugi... ] Mickael Istria resolved JBIDE-22415. ------------------------------------ Resolution: Done Done with https://github.com/jbosstools/jbosstools-target-platforms/commit/0c6098ca... > Target Platform PR build should produce both ignoreVerions and "honorVersion" p2diff > ------------------------------------------------------------------------------------ > > Key: JBIDE-22415 > URL: https://issues.jboss.org/browse/JBIDE-22415 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: target-platform > Affects Versions: 4.4.0.Alpha2 > Reporter: Nick Boldt > Assignee: Mickael Istria > Fix For: 4.4.0.Alpha3 > > Attachments: _view_.txt, _view_2.txt > > > When rolling back a change [1], the build [2] produced two empty p2diff files. > [1] https://github.com/jbosstools/jbosstools-target-platforms/commit/935dcedc... > [2] http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22428) Create Central-CI Jenkins job for JSDT Integration Tests

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22428?page=com.atlassian.jira.plugi... ] Pavol Srna reassigned JBIDE-22428: ---------------------------------- Assignee: Pavol Srna > Create Central-CI Jenkins job for JSDT Integration Tests > -------------------------------------------------------- > > Key: JBIDE-22428 > URL: https://issues.jboss.org/browse/JBIDE-22428 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: javascript > Reporter: Pavol Srna > Assignee: Pavol Srna > Fix For: 4.4.0.Alpha3 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 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 May 2016