June 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-13189) Standalone BrowserSim should create .browsersim/config.cfg folder in user home directory

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13189?page=com.atlassian.jira.plugi... ] Denis Golovin updated JBIDE-13189: ---------------------------------- Fix Version/s: 4.1.0.Alpha2 (was: 4.1.x) > Standalone BrowserSim should create .browsersim/config.cfg folder in user home directory > ---------------------------------------------------------------------------------------- > > Key: JBIDE-13189 > URL: https://issues.jboss.org/browse/JBIDE-13189 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: browsersim > Reporter: Max Rydahl Andersen > Assignee: Konstantin Marmalyukov > Fix For: 4.1.0.Alpha2 > > > org.jboss.tools.vpe.browsersim/devices.cfg is created on every launch. > Couldn't this only be generated if actually did changes ? > and if i'm in standalone couldn't it be stored in like ~/.browsersim/devices.cfg or similar ? -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13189) Standalone BrowserSim should create .browsersim/config.cfg folder in user home directory

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13189?page=com.atlassian.jira.plugi... ] Denis Golovin closed JBIDE-13189. --------------------------------- Resolution: Done It was pushed in master before 4.1.0.Alpha2 codefreez > Standalone BrowserSim should create .browsersim/config.cfg folder in user home directory > ---------------------------------------------------------------------------------------- > > Key: JBIDE-13189 > URL: https://issues.jboss.org/browse/JBIDE-13189 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: browsersim > Reporter: Max Rydahl Andersen > Assignee: Konstantin Marmalyukov > Fix For: 4.1.0.Alpha2 > > > org.jboss.tools.vpe.browsersim/devices.cfg is created on every launch. > Couldn't this only be generated if actually did changes ? > and if i'm in standalone couldn't it be stored in like ~/.browsersim/devices.cfg or similar ? -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-11493) Create standalone BrowserSim application

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-11493?page=com.atlassian.jira.plugi... ] Denis Golovin closed JBIDE-11493. --------------------------------- Resolution: Done It was pushed into master only. > Create standalone BrowserSim application > ---------------------------------------- > > Key: JBIDE-11493 > URL: https://issues.jboss.org/browse/JBIDE-11493 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: browsersim > Affects Versions: 3.3.0.Beta3 > Reporter: Denis Golovin > Assignee: Konstantin Marmalyukov > Priority: Critical > Labels: new_and_noteworthy > Fix For: 4.1.0.Alpha1 > > > When I was looking for other Browser Simulator implementations I could not found anything downloadable for personal consumption :) would be good to provide standalone application for anyone to run. Because now to run it as standalone one need to know java and go with something like > {code} > java -cp /path/with/browsersim/jars;/path/to/platform/dependent/swt.jar org.jboss.tools.vpe.browsersim.ui.BrowserSim > {code} > In case of application it would need just a little: > # Download archive > # Unpack it > # Run browsersim(.exe) > *Update:* > pom.xml is already placed to jbosstools-vpe/browsersim-standalone. > To build BrowserSim standalone jar you need to execute: > {code} > git clone https://github.com/jbosstools/jbosstools-build.git > git clone https://github.com/jbosstools/jbosstools-vpe.git > cd jbosstools-vpe/browsersim-standalone > mvn clean install > {code} > After that browsersim.jar will be created in {{jbosstools-vpe/browsersim-standalone/application/target/application}} folder. > To run it execute: > * on Windows or Linux: > {code} > java -jar browsersim.jar > {code} > * on Mac OS: > {code} > java -XstartOnFirstThread -jar browsersim.jar > {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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-11493) Create standalone BrowserSim application

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-11493?page=com.atlassian.jira.plugi... ] Denis Golovin updated JBIDE-11493: ---------------------------------- Fix Version/s: (was: 4.0.x) > Create standalone BrowserSim application > ---------------------------------------- > > Key: JBIDE-11493 > URL: https://issues.jboss.org/browse/JBIDE-11493 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: browsersim > Affects Versions: 3.3.0.Beta3 > Reporter: Denis Golovin > Assignee: Konstantin Marmalyukov > Priority: Critical > Labels: new_and_noteworthy > Fix For: 4.1.0.Alpha1 > > > When I was looking for other Browser Simulator implementations I could not found anything downloadable for personal consumption :) would be good to provide standalone application for anyone to run. Because now to run it as standalone one need to know java and go with something like > {code} > java -cp /path/with/browsersim/jars;/path/to/platform/dependent/swt.jar org.jboss.tools.vpe.browsersim.ui.BrowserSim > {code} > In case of application it would need just a little: > # Download archive > # Unpack it > # Run browsersim(.exe) > *Update:* > pom.xml is already placed to jbosstools-vpe/browsersim-standalone. > To build BrowserSim standalone jar you need to execute: > {code} > git clone https://github.com/jbosstools/jbosstools-build.git > git clone https://github.com/jbosstools/jbosstools-vpe.git > cd jbosstools-vpe/browsersim-standalone > mvn clean install > {code} > After that browsersim.jar will be created in {{jbosstools-vpe/browsersim-standalone/application/target/application}} folder. > To run it execute: > * on Windows or Linux: > {code} > java -jar browsersim.jar > {code} > * on Mac OS: > {code} > java -XstartOnFirstThread -jar browsersim.jar > {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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-3628) Plugins should be .jar's not directories for efficiency sake

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-3628?page=com.atlassian.jira.plugin... ] Denis Golovin edited comment on JBIDE-3628 at 6/28/13 2:31 PM: --------------------------------------------------------------- {quote} eclipse knows how to handle jars inside jared plugins, it put all such jars into cache and then use them without unzipping constantly.{quote} The jars should be just referenced right way in Runtime section of manifest. was (Author: dgolovin): {quoye} eclipse knows how to handle jars inside jared plugins, it put all such jars into cache and then use them without unzipping constantly.{quote} The jars should be just referenced right way in Runtime section of manifest. > Plugins should be .jar's not directories for efficiency sake > ------------------------------------------------------------ > > Key: JBIDE-3628 > URL: https://issues.jboss.org/browse/JBIDE-3628 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: Build/Releng > Reporter: Max Rydahl Andersen > Assignee: Denis Golovin > Priority: Critical > Fix For: 4.2.0.Alpha1 > > Attachments: exception.log > > > 65 of our plugins are bundled exploded instead of a .jar > Some are probably just mistakes and can easily be packed others are because of legacy code assuming it can access the files directly and even store data in the plugins - that should be fixed. > What should be fixed: > 1. The way how plug-ins use images in plugin.xml, in java code and in .meta xmodel files > 2. Plug-ins that loads resources should be aware that they are in jar now (VPE should be able to load templates from plugin jar files) > 3. Some plug-ins contain resources registered in XML catalog > 4. common.projecttemplates contains resources that is used as template for new projects > 5. TBD -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15059) Server adapter: tells me that there are local commit that I can publish even though there are none

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15059?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-15059: ------------------------------------- Fix Version/s: 4.2.0.Alpha1 > Server adapter: tells me that there are local commit that I can publish even though there are none > -------------------------------------------------------------------------------------------------- > > Key: JBIDE-15059 > URL: https://issues.jboss.org/browse/JBIDE-15059 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.2.0.Alpha1 > > Attachments: already-up-to-date.png, committed-changes-to-publish.png > > > 1. EXEC: launch OpenShift Application wizard > 2. EXEC: create a new application and have it imported to your workspace > 3. EXEC: After the import the adapter will tell you that there are local commits that you may want to publish to OpenShift. Tell it to do so > !committed-changes-to-publish.png! > 4. EXEC: Pick your server adapter and tell it to publish to OpenShift > Result: > The adapter tells you that you that there are local commits that you may push. > !committed-changes-to-publish.png! > Expected: > We just pushed there cannot be local commits that were not pushed yet > 5. EXEC: Confirm the dialog and tell it to publish > Result: > It tells you that OpenShift is already up-to-date (which is true!) > !already-up-to-date.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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15059) Server adapter: tells me that there are local commit that I can publish even though there are none

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15059?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-15059: ------------------------------------- Affects Version/s: 4.1.0.CR1 > Server adapter: tells me that there are local commit that I can publish even though there are none > -------------------------------------------------------------------------------------------------- > > Key: JBIDE-15059 > URL: https://issues.jboss.org/browse/JBIDE-15059 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.1.0.CR1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.2.0.Alpha1 > > Attachments: already-up-to-date.png, committed-changes-to-publish.png > > > 1. EXEC: launch OpenShift Application wizard > 2. EXEC: create a new application and have it imported to your workspace > 3. EXEC: After the import the adapter will tell you that there are local commits that you may want to publish to OpenShift. Tell it to do so > !committed-changes-to-publish.png! > 4. EXEC: Pick your server adapter and tell it to publish to OpenShift > Result: > The adapter tells you that you that there are local commits that you may push. > !committed-changes-to-publish.png! > Expected: > We just pushed there cannot be local commits that were not pushed yet > 5. EXEC: Confirm the dialog and tell it to publish > Result: > It tells you that OpenShift is already up-to-date (which is true!) > !already-up-to-date.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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15059) Server adapter: tells me that there are local commit that I can publish even though there are none

by Andre Dietisheim (JIRA)

Andre Dietisheim created JBIDE-15059: ---------------------------------------- Summary: Server adapter: tells me that there are local commit that I can publish even though there are none Key: JBIDE-15059 URL: https://issues.jboss.org/browse/JBIDE-15059 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Reporter: Andre Dietisheim Assignee: Andre Dietisheim Attachments: already-up-to-date.png, committed-changes-to-publish.png 1. EXEC: launch OpenShift Application wizard 2. EXEC: create a new application and have it imported to your workspace 3. EXEC: After the import the adapter will tell you that there are local commits that you may want to publish to OpenShift. Tell it to do so !committed-changes-to-publish.png! 4. EXEC: Pick your server adapter and tell it to publish to OpenShift Result: The adapter tells you that you that there are local commits that you may push. !committed-changes-to-publish.png! Expected: We just pushed there cannot be local commits that were not pushed yet 5. EXEC: Confirm the dialog and tell it to publish Result: It tells you that OpenShift is already up-to-date (which is true!) !already-up-to-date.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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15059) Server adapter: tells me that there are local commit that I can publish even though there are none

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15059?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-15059: ------------------------------------- Attachment: committed-changes-to-publish.png already-up-to-date.png > Server adapter: tells me that there are local commit that I can publish even though there are none > -------------------------------------------------------------------------------------------------- > > Key: JBIDE-15059 > URL: https://issues.jboss.org/browse/JBIDE-15059 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Attachments: already-up-to-date.png, committed-changes-to-publish.png > > > 1. EXEC: launch OpenShift Application wizard > 2. EXEC: create a new application and have it imported to your workspace > 3. EXEC: After the import the adapter will tell you that there are local commits that you may want to publish to OpenShift. Tell it to do so > !committed-changes-to-publish.png! > 4. EXEC: Pick your server adapter and tell it to publish to OpenShift > Result: > The adapter tells you that you that there are local commits that you may push. > !committed-changes-to-publish.png! > Expected: > We just pushed there cannot be local commits that were not pushed yet > 5. EXEC: Confirm the dialog and tell it to publish > Result: > It tells you that OpenShift is already up-to-date (which is true!) > !already-up-to-date.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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-10541) If I add a file to my project, the OpenShift server adapter does not handle it well: should show EGit commit dialog

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-10541?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-10541: ------------------------------------- Attachment: committed-changes-to-publish.png > If I add a file to my project, the OpenShift server adapter does not handle it well: should show EGit commit dialog > ------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-10541 > URL: https://issues.jboss.org/browse/JBIDE-10541 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 3.3.0.M5 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.2.x > > Attachments: committed-changes-to-publish.png > > > Currently the dialog showing up when committing/pushing is confusing since it says there are no changes which is not correct if comparing to opehsfnit remote repo. > Should make a check against the fetched upstream and see what has changed since that is a fast local operation. -- 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, 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 June 2013