May 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-14616) Remove <relativePath/> to parent pom

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14616?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-14616: ------------------------------------------ pushed to openshift-master in https://github.com/jbosstools/jbosstools-openshift/pull/154 > Remove <relativePath/> to parent pom > ------------------------------------ > > Key: JBIDE-14616 > URL: https://issues.jboss.org/browse/JBIDE-14616 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: Build/Releng > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 4.1.0.Beta2 > > > Having a relativePath to parent pom in each component makes that often, on development machine, build resolves parent pom to the relative one (which my not be correctly sync'd) instead of the one which is published on Nexus. > This introduce confusion and may result in different build output between CI and local. Therefore, we should remove the <relativePath/> from all components. -- 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

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14654) org.jboss.tools.openshift.egit.test: remove forked MockSytemReader

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14654?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-14654 at 5/31/13 11:50 AM: -------------------------------------------------------------------- re-added forked MockedSystemReader, built... {code} [INFO] Reactor Summary: [INFO] [INFO] openshift.all ..................................... SUCCESS [0.414s] [INFO] openshift.plugins ................................. SUCCESS [0.006s] [INFO] org.jboss.tools.openshift.egit.core ............... SUCCESS [2.198s] [INFO] org.jboss.tools.openshift.egit.ui ................. SUCCESS [0.445s] [INFO] org.jboss.tools.openshift.express.client .......... SUCCESS [0.183s] [INFO] org.jboss.tools.openshift.express.ui .............. SUCCESS [4.704s] [INFO] openshift.tests ................................... SUCCESS [0.008s] [INFO] org.jboss.tools.openshift.egit.test ............... SUCCESS [27.272s] [INFO] org.jboss.tools.openshift.express.test ............ SUCCESS [37.515s] [INFO] openshift.features ................................ SUCCESS [0.007s] [INFO] org.jboss.tools.openshift.egit.integration.feature SUCCESS [0.228s] [INFO] org.jboss.tools.openshift.express.feature ......... SUCCESS [0.251s] [INFO] org.jboss.tools.openshift.egit.integration.test.feature SUCCESS [0.112s] [INFO] org.jboss.tools.openshift.express.test.feature .... SUCCESS [0.141s] [INFO] openshift.site .................................... SUCCESS [7.603s] [INFO] ------------------------------------------------------------------------ [INFO] BUILD SUCCESS [INFO] ------------------------------------------------------------------------ [INFO] Total time: 1:55.416s [INFO] Finished at: Fri May 31 17:42:41 CEST 2013 [INFO] Final Memory: 69M/737M [INFO] ------------------------------------------------------------------------ {code} ...and pushed upstream. was (Author: adietish): re-added forked MockedSystemReader and pushed upstream. > org.jboss.tools.openshift.egit.test: remove forked MockSytemReader > ------------------------------------------------------------------ > > Key: JBIDE-14654 > URL: https://issues.jboss.org/browse/JBIDE-14654 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.1.0.Beta1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Priority: Minor > Fix For: 4.1.0.Beta2 > > > When testing egits operations (commit, push, etc.) we're using a MockSystemReader we forked from jgit. > The MockSystemReader in jgit is now perfectly suitable for us, we should kill our fork and switch to the one provided in jgit. -- 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

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14654) org.jboss.tools.openshift.egit.test: remove forked MockSytemReader

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14654?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-14654: ------------------------------------- Git Pull Request: https://github.com/jbosstools/jbosstools-openshift/pull/143, https://github.com/jbosstools/jbosstools-openshift/pull/153 (was: https://github.com/jbosstools/jbosstools-openshift/pull/143, https://github.com/jbosstools/jbosstools-openshift/pull/152) > org.jboss.tools.openshift.egit.test: remove forked MockSytemReader > ------------------------------------------------------------------ > > Key: JBIDE-14654 > URL: https://issues.jboss.org/browse/JBIDE-14654 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.1.0.Beta1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Priority: Minor > Fix For: 4.1.0.Beta2 > > > When testing egits operations (commit, push, etc.) we're using a MockSystemReader we forked from jgit. > The MockSystemReader in jgit is now perfectly suitable for us, we should kill our fork and switch to the one provided in jgit. -- 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

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14717) Add tooltip capabilities to field editors

by Viacheslav Kabanovich (JIRA)

Viacheslav Kabanovich created JBIDE-14717: --------------------------------------------- Summary: Add tooltip capabilities to field editors Key: JBIDE-14717 URL: https://issues.jboss.org/browse/JBIDE-14717 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: common/jst/core Reporter: Viacheslav Kabanovich Assignee: Viacheslav Kabanovich Fix For: 4.1.0.Beta2 Add methods creating field editors with descriptions rendered as tooltips to IFieldEditorFactory. -- 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

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14639) Add ability to prevent repository references from being included in repositories mirrored from a TP

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14639?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-14639: ---------------------------------------- Yes, it needs to be addressed upstream. However there are 2 workarounds: * Using the remove.references.xml Ant script linked by Nick * Using the generate-repository-facade mojo which trims existing references and allows to add some other ones: the remove.references.xml script is a way . See https://github.com/jbosstools/jbosstools-build-sites/blob/master/aggregat... and https://github.com/jbosstools/jbosstools-maven-plugins/blob/master/tycho-... ). > Add ability to prevent repository references from being included in repositories mirrored from a TP > --------------------------------------------------------------------------------------------------- > > Key: JBIDE-14639 > URL: https://issues.jboss.org/browse/JBIDE-14639 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: Build/Releng > Reporter: Rob Cernich > Assignee: Nick Boldt > > JBT-IS builds a repo of "extra" dependencies. When this repo is created, it contains repository references to the jboss.org requirements p2 mirrors, which prevent the mirrored repository from being used with jbds releases (which is what I assume the purpose of the mirrored repository is for). -- 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

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-89) target platform repo should not contain repository references

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBTIS-89?page=com.atlassian.jira.plugin.s... ] Mickael Istria commented on JBTIS-89: ------------------------------------- [~pleacu] [~rcernich]: the remove.references.xml script is a way to get rid of dependencies. The generate-repository-facade mojo also removes default references and is easier to integrate with Maven, and allows you to add some other references see https://github.com/jbosstools/jbosstools-build-sites/blob/master/aggregat... and https://github.com/jbosstools/jbosstools-maven-plugins/blob/master/tycho-... ). However, I don't understand why you get so many references on your site. It's probably caused by features defining reference to other sites, which is something deprecated as it does not provide enough control on final packaging. > target platform repo should not contain repository references > ------------------------------------------------------------- > > Key: JBTIS-89 > URL: https://issues.jboss.org/browse/JBTIS-89 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Rob Cernich > Assignee: Paul Leacu > Priority: Critical > > I don't see how this repo could be used in a jbds setting when it contains repository references to jbt repositories. My understanding was that this repo only contained the extra dependencies for jbt-is. By including these references, if this repo is used in jbds, all those linked repos will be available too, polluting the pool of available features/bundles. -- 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

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14654) org.jboss.tools.openshift.egit.test: remove forked MockSytemReader

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14654?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-14654: ------------------------------------------ re-added forked MockedSystemReader and pushed upstream. > org.jboss.tools.openshift.egit.test: remove forked MockSytemReader > ------------------------------------------------------------------ > > Key: JBIDE-14654 > URL: https://issues.jboss.org/browse/JBIDE-14654 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.1.0.Beta1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Priority: Minor > Fix For: 4.1.0.Beta2 > > > When testing egits operations (commit, push, etc.) we're using a MockSystemReader we forked from jgit. > The MockSystemReader in jgit is now perfectly suitable for us, we should kill our fork and switch to the one provided in jgit. -- 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

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14654) org.jboss.tools.openshift.egit.test: remove forked MockSytemReader

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14654?page=com.atlassian.jira.plugi... ] Andre Dietisheim resolved JBIDE-14654. -------------------------------------- Resolution: Rejected closing as REJECTED > org.jboss.tools.openshift.egit.test: remove forked MockSytemReader > ------------------------------------------------------------------ > > Key: JBIDE-14654 > URL: https://issues.jboss.org/browse/JBIDE-14654 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.1.0.Beta1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Priority: Minor > Fix For: 4.1.0.Beta2 > > > When testing egits operations (commit, push, etc.) we're using a MockSystemReader we forked from jgit. > The MockSystemReader in jgit is now perfectly suitable for us, we should kill our fork and switch to the one provided in jgit. -- 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

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14126) Weinre Inspector is showing no data within Elements tab

by Vlado Pakan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14126?page=com.atlassian.jira.plugi... ] Vlado Pakan commented on JBIDE-14126: ------------------------------------- Konstantin you are probably right I forgot to click on Target link. It's working with JBDS 7.0.0.Beta1b. So points 10., 11. can be ignored > Weinre Inspector is showing no data within Elements tab > ------------------------------------------------------- > > Key: JBIDE-14126 > URL: https://issues.jboss.org/browse/JBIDE-14126 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: browsersim > Affects Versions: 4.1.0.Alpha2 > Environment: Fedora 17 64bit, KDE, jbdevstudio-product-eap-universal-7.0.0.Alpha2-v20130421-0725-B198, Java Sun JDK 1.6.0_32 > Reporter: Vlado Pakan > Assignee: Konstantin Marmalyukov > Fix For: 4.1.0.Beta2 > > Attachments: localamazon.png, localbrowsersimhtml5.png, localhtml5.png, phonegapamazon.png > > > 1. Open www.amazon.com page in Browsersim > 2. Run Weinre Inspector via Browsersim context menu "Weinre" > ERROR: No elements shown on Elements tab > Client is connected: > !phonegapamazon.png! > 3. Run Weinre server locally. > 4. Set Browsersim to use local Weinre server > 5. Run Weinre Inspector as in step 2. > ERROR: No elements shown on Elements tab > Client is connected: > !localamazon.png! > 6. Create HTML5 project from JBoss Central > 7. Insert script tag allowing debugging via local Weinre server to index.html > 8. Run HTML5 project on Server > 9. Open HTML5 index.html in system borwser > ASSERT: Weinre debugging works > !localhtml5.png! > ERROR: Weinre debugging is not working from JBDS internal browser > 10. Open index.html of HTML5 project in Browsersim > 11. Open Weinre debug link in Browser > ERROR: No elements shown on Elements tab > Client is connected: > !localbrowsersimhtml5.png! -- 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

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14654) org.jboss.tools.openshift.egit.test: remove forked MockSytemReader

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14654?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-14654 at 5/31/13 11:33 AM: -------------------------------------------------------------------- reopening since this commit broke our build: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/JBossTools/view/JBo... org.eclipse.jgit.junit is apparently not present in the egit/jgit update sites but in staging sites only. Since I only use a single class of org.eclipse.jgit.junit I'll get back to the forked version. was (Author: adietish): reopening since this commit broke our build. org.eclipse.jgit.junit is apparently not present in the egit/jgit update sites but in staging sites only. Since I only use a single class of org.eclipse.jgit.junit I'll get back to the forked version. > org.jboss.tools.openshift.egit.test: remove forked MockSytemReader > ------------------------------------------------------------------ > > Key: JBIDE-14654 > URL: https://issues.jboss.org/browse/JBIDE-14654 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.1.0.Beta1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Priority: Minor > Fix For: 4.1.0.Beta2 > > > When testing egits operations (commit, push, etc.) we're using a MockSystemReader we forked from jgit. > The MockSystemReader in jgit is now perfectly suitable for us, we should kill our fork and switch to the one provided in jgit. -- 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

10 years, 11 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 May 2013