May 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-14400) create p2 remediation UI icons

by Vlado Pakan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14400?page=com.atlassian.jira.plugi... ] Vlado Pakan commented on JBIDE-14400: ------------------------------------- Could you please provide steps to verify this Jira or verify and close it? > create p2 remediation UI icons > ------------------------------ > > Key: JBIDE-14400 > URL: https://issues.jboss.org/browse/JBIDE-14400 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: upstream > Reporter: Max Rydahl Andersen > Assignee: Max Rydahl Andersen > Fix For: 4.1.0.Beta1 > > Attachments: down1.png, down2.png, down3.png, screen1.jpg, screen2.jpg, screen3.jpg, Screen_Shot_2013-05-06_at_9.59.35_AM.png, up1.png, up2.png, up3.png > > > Pascal from p2 on eclipse side is working on p2 remediation UI and have asked if we got two icons for < and > (bigger than and less than). > See the screenshot for where they would be used (basically in the tree to indicate which are being down or upgraded. > Daniel could you make such that can be shown nicely in a treeviewer ? > I think having a v and ^ to show up and down might be better. -- 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

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2640) Make sure jbds product has p2 property to avoid it being uninstalled

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBDS-2640?page=com.atlassian.jira.plugin.... ] Mickael Istria resolved JBDS-2640. ---------------------------------- Assignee: Mickael Istria Resolution: Done After installation, file jbdevstudio/studio/configuration/config.ini reads {code} eclipse.product=com.jboss.jbds.product.product {code} > Make sure jbds product has p2 property to avoid it being uninstalled > -------------------------------------------------------------------- > > Key: JBDS-2640 > URL: https://issues.jboss.org/browse/JBDS-2640 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Max Rydahl Andersen > Assignee: Mickael Istria > Priority: Critical > Fix For: 7.0.0.Beta2 > > > see discussion at https://bugs.eclipse.org/bugs/show_bug.cgi?id=406985 for eclipse EPP > we should be sure we have the same for jbds product. -- 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

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13379) BrowserSim: implement support of the LiveReload protocol

by Yahor Radtsevich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13379?page=com.atlassian.jira.plugi... ] Yahor Radtsevich resolved JBIDE-13379. -------------------------------------- Fix Version/s: 4.1.0.Beta1 (was: 4.1.0.Beta2) Resolution: Done *Resolved* as the feature is already working. Subtask JBIDE-14361 will be resolved later. > BrowserSim: implement support of the LiveReload protocol > -------------------------------------------------------- > > Key: JBIDE-13379 > URL: https://issues.jboss.org/browse/JBIDE-13379 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: browsersim > Reporter: Yahor Radtsevich > Assignee: Ilya Buziuk > Labels: new_and_noteworthy > Fix For: 4.1.0.Beta1 > > > There is https://github.com/livereload/livereload-js which could help. -- 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

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14663) Source lookup dialog shown twice on maven projects

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14663?page=com.atlassian.jira.plugi... ] Snjezana Peco commented on JBIDE-14663: --------------------------------------- {quote} if we remove the popup dialog we are adding machine specific paths that is bad (m2e doing it and not telling users are just as bad). {quote} In that case, the only thing we can do is to create a bug against m2e. > Source lookup dialog shown twice on maven projects > -------------------------------------------------- > > Key: JBIDE-14663 > URL: https://issues.jboss.org/browse/JBIDE-14663 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: maven > Affects Versions: 4.1.0.Beta1 > Reporter: Fred Bricon > Assignee: Fred Bricon > Labels: respin-b > Fix For: 4.1.0.Beta1 > > > Source lookup dialog is shown twice on maven projects : http://screencast.com/t/3yESat96FIw > I think our source lookup should ignore projects with the maven nature, since a m2e's source lookup mechanism is already running in the background. > If maven nature is enabled AND source is set but missing THEN, it'd be ok to show our own stuff -- 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

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14663) Source lookup dialog shown twice on maven projects

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14663?page=com.atlassian.jira.plugi... ] Snjezana Peco resolved JBIDE-14663. ----------------------------------- Resolution: Done > Source lookup dialog shown twice on maven projects > -------------------------------------------------- > > Key: JBIDE-14663 > URL: https://issues.jboss.org/browse/JBIDE-14663 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: maven > Affects Versions: 4.1.0.Beta1 > Reporter: Fred Bricon > Assignee: Fred Bricon > Labels: respin-b > Fix For: 4.1.0.Beta1 > > > Source lookup dialog is shown twice on maven projects : http://screencast.com/t/3yESat96FIw > I think our source lookup should ignore projects with the maven nature, since a m2e's source lookup mechanism is already running in the background. > If maven nature is enabled AND source is set but missing THEN, it'd be ok to show our own stuff -- 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

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14697) User library fileset cannot be modified

by Jaroslav Jankovič (JIRA)

Jaroslav Jankovič created JBIDE-14697: ----------------------------------------- Summary: User library fileset cannot be modified Key: JBIDE-14697 URL: https://issues.jboss.org/browse/JBIDE-14697 Project: Tools (JBoss Tools) Issue Type: Bug Components: archives Affects Versions: 4.1.0.Beta1 Reporter: Jaroslav Jankovič Fix For: 4.1.0.Beta2 STEP: prepare two library filesets, lets say myLib1, myLib2 via preferences (Java -> Build Path -> User Libraries) STEP: create project with archives support in it STEP: create some archive STEP: add new user library fileset in the archive (myLib1) STEP: select myLib1 in archives explorer, invoke its context menu and select Edit fileset STEP: in "User Library Fileset Wizard" dialog select myLib2, confirm it FAIL: there is still myLib in archives explorer, not myLib2 as it should be -- 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

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14697) User library fileset cannot be modified

by Jaroslav Jankovič (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14697?page=com.atlassian.jira.plugi... ] Jaroslav Jankovič updated JBIDE-14697: -------------------------------------- Description: STEP: prepare two library filesets, lets say myLib1, myLib2 via preferences (Java -> Build Path -> User Libraries) STEP: create project with archives support STEP: create some archive in the project STEP: add new user library fileset in the archive (myLib1) STEP: select myLib1 in archives explorer, invoke its context menu and select Edit fileset STEP: in "User Library Fileset Wizard" dialog select myLib2, confirm it FAIL: there is still myLib in archives explorer, not myLib2 as it should be was: STEP: prepare two library filesets, lets say myLib1, myLib2 via preferences (Java -> Build Path -> User Libraries) STEP: create project with archives support in it STEP: create some archive STEP: add new user library fileset in the archive (myLib1) STEP: select myLib1 in archives explorer, invoke its context menu and select Edit fileset STEP: in "User Library Fileset Wizard" dialog select myLib2, confirm it FAIL: there is still myLib in archives explorer, not myLib2 as it should be > User library fileset cannot be modified > --------------------------------------- > > Key: JBIDE-14697 > URL: https://issues.jboss.org/browse/JBIDE-14697 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: archives > Affects Versions: 4.1.0.Beta1 > Reporter: Jaroslav Jankovič > Fix For: 4.1.0.Beta2 > > > STEP: prepare two library filesets, lets say myLib1, myLib2 via preferences (Java -> Build Path -> User Libraries) > STEP: create project with archives support > STEP: create some archive in the project > STEP: add new user library fileset in the archive (myLib1) > STEP: select myLib1 in archives explorer, invoke its context menu and select Edit fileset > STEP: in "User Library Fileset Wizard" dialog select myLib2, confirm it > FAIL: there is still myLib in archives explorer, not myLib2 as it should be -- 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

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14696) VPE context menu has missing menu items

by Vlado Pakan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14696?page=com.atlassian.jira.plugi... ] Vlado Pakan updated JBIDE-14696: -------------------------------- Attachment: brokenvpecontextmenu.png correctvpecontextmenu.png > VPE context menu has missing menu items > --------------------------------------- > > Key: JBIDE-14696 > URL: https://issues.jboss.org/browse/JBIDE-14696 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: Visual Page Editor core > Affects Versions: 4.1.0.Beta1 > Environment: JBDS 7.0.0.Beta1-v20130529-0631-B257 Linux 32bit > Reporter: Vlado Pakan > Priority: Critical > Fix For: 4.1.0.Beta2 > > Attachments: brokenvpecontextmenu.png, correctvpecontextmenu.png > > > 1. Import HTML5 froject from Central > 2. Open index.html file from this project in VPE > 3. Right-click on some graphical element within visual part of VPE > ERROR: Context Menu has missing menu items. Two empty spaces displayed between three spacers. Probably it broke between 7.0.0.Beta1 build and 7.0.0.Beta1a build when target platform was updated: > !brokenvpecontextmenu.png! > Menu should looks like this one from JBDS 7.0.0.Alpha2: > !correctvpecontextmenu.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

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14696) VPE context menu has missing menu items

by Vlado Pakan (JIRA)

Vlado Pakan created JBIDE-14696: ----------------------------------- Summary: VPE context menu has missing menu items Key: JBIDE-14696 URL: https://issues.jboss.org/browse/JBIDE-14696 Project: Tools (JBoss Tools) Issue Type: Bug Components: Visual Page Editor core Affects Versions: 4.1.0.Beta1 Environment: JBDS 7.0.0.Beta1-v20130529-0631-B257 Linux 32bit Reporter: Vlado Pakan Priority: Critical Fix For: 4.1.0.Beta2 1. Import HTML5 froject from Central 2. Open index.html file from this project in VPE 3. Right-click on some graphical element within visual part of VPE ERROR: Context Menu has missing menu items. Two empty spaces displayed between three spacers. Probably it broke between 7.0.0.Beta1 build and 7.0.0.Beta1a build when target platform was updated: !brokenvpecontextmenu.png! Menu should looks like this one from JBDS 7.0.0.Alpha2: !correctvpecontextmenu.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

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14695) no version set for org.codehaus.mojo:exec-maven-plugin in parent pom on line 733

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-14695: ---------------------------------- Summary: no version set for org.codehaus.mojo:exec-maven-plugin in parent pom on line 733 Key: JBIDE-14695 URL: https://issues.jboss.org/browse/JBIDE-14695 Project: Tools (JBoss Tools) Issue Type: Bug Components: Build/Releng Affects Versions: 4.1.0.Beta2 Reporter: Nick Boldt Assignee: Nick Boldt {code} [WARNING] 'build.plugins.plugin.version' for org.codehaus.mojo:exec-maven-plugin is missing. @ org.jboss.tools:parent:4.1.0.Beta2-SNAPSHOT, /mnt/hudson_workspace/workspace/devstudio.signed.product_trunk/.repository/org/jboss/tools/parent/4.1.0.Beta2-SNAPSHOT/parent-4.1.0.Beta2-SNAPSHOT.pom, line 733, column 19{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

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