December 2014 - jbosstools-issues

[JBoss JIRA] (JBIDE-18177) Request at first start what is more important JSF or HTML5 support and enable/disable XULRunner

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18177?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-18177: ----------------------------------- Attachment: restart.jpg {quote} The problem is that I don't know how to inform user here that restart will be required if browser engine should be switched. Do you have any idea? {quote} Something similar to the following message (used by Eclipse after updating) could be used: !restart.jpg! > Request at first start what is more important JSF or HTML5 support and enable/disable XULRunner > ----------------------------------------------------------------------------------------------- > > Key: JBIDE-18177 > URL: https://issues.jboss.org/browse/JBIDE-18177 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: visual-page-editor-core, xulrunner > Affects Versions: 4.2.0.CR1 > Reporter: Denis Golovin > Assignee: Konstantin Marmalyukov > Priority: Critical > Labels: f2f2014 > Fix For: 4.2.2.Final, 4.3.0.Alpha1 > > Attachments: restart.jpg > > > Imagine that one first clean workspace startup on opening vpe on systems where xulrunner / webkit can't run at the same time we will ask if he prefers to have good JSF support (use xulrunner) or HTML5 support (disable xulrunner) > if he says okey - we set a flag somewhere to not start xulrunner. > user restart - user is happy. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18866) allow URL in the form "from-code=git@github.com" for custom app source code and downloadable cartridges

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18866?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-18866: ------------------------------------- Git Pull Request: https://github.com/jbosstools/jbosstools-openshift/pull/512 (was: https://github.com/jbosstools/jbosstools-openshift/pull/511) > allow URL in the form "from-code=git(a)github.com" for custom app source code and downloadable cartridges > ------------------------------------------------------------------------------------------------------- > > Key: JBIDE-18866 > URL: https://issues.jboss.org/browse/JBIDE-18866 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.2.0.Final > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.3.0.Alpha1 > > > We should be able to use urls that refer to github repositories when using custom application source code and downloadable cartridges -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18177) Request at first start what is more important JSF or HTML5 support and enable/disable XULRunner

by Konstantin Marmalyukov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18177?page=com.atlassian.jira.plugi... ] Konstantin Marmalyukov commented on JBIDE-18177: ------------------------------------------------ As we decide with [~akazakov], this feature should be pushed in master, but tested with nightly before it ([~vpakan] - please do it), and if everything is ok - should be applied in 4.2.2 [~maxandersen], [~burrsutter] I need your help with dialog message. My first idea is bq. Do you prefer to have good JSF support (use xulrunner) or HTML5 support (use webkit)? and two buttons: stay with/switch to JSF and switch to/stay with HTML5. The problem is that I don't know how to inform user here that restart will be required if browser engine should be switched. Do you have any idea? > Request at first start what is more important JSF or HTML5 support and enable/disable XULRunner > ----------------------------------------------------------------------------------------------- > > Key: JBIDE-18177 > URL: https://issues.jboss.org/browse/JBIDE-18177 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: visual-page-editor-core, xulrunner > Affects Versions: 4.2.0.CR1 > Reporter: Denis Golovin > Assignee: Konstantin Marmalyukov > Priority: Critical > Labels: f2f2014 > Fix For: 4.2.2.Final, 4.3.0.Alpha1 > > > Imagine that one first clean workspace startup on opening vpe on systems where xulrunner / webkit can't run at the same time we will ask if he prefers to have good JSF support (use xulrunner) or HTML5 support (disable xulrunner) > if he says okey - we set a flag somewhere to not start xulrunner. > user restart - user is happy. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18177) Request at first start what is more important JSF or HTML5 support and enable/disable XULRunner

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18177?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-18177: ----------------------------------- Labels: f2f2014 (was: f2f2014 respin-a) > Request at first start what is more important JSF or HTML5 support and enable/disable XULRunner > ----------------------------------------------------------------------------------------------- > > Key: JBIDE-18177 > URL: https://issues.jboss.org/browse/JBIDE-18177 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: visual-page-editor-core, xulrunner > Affects Versions: 4.2.0.CR1 > Reporter: Denis Golovin > Assignee: Konstantin Marmalyukov > Priority: Critical > Labels: f2f2014 > Fix For: 4.2.2.Final, 4.3.0.Alpha1 > > > Imagine that one first clean workspace startup on opening vpe on systems where xulrunner / webkit can't run at the same time we will ask if he prefers to have good JSF support (use xulrunner) or HTML5 support (disable xulrunner) > if he says okey - we set a flag somewhere to not start xulrunner. > user restart - user is happy. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18177) Request at first start what is more important JSF or HTML5 support and enable/disable XULRunner

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18177?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-18177: ----------------------------------- Fix Version/s: 4.2.2.Final (was: 4.2.1.CR1) > Request at first start what is more important JSF or HTML5 support and enable/disable XULRunner > ----------------------------------------------------------------------------------------------- > > Key: JBIDE-18177 > URL: https://issues.jboss.org/browse/JBIDE-18177 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: visual-page-editor-core, xulrunner > Affects Versions: 4.2.0.CR1 > Reporter: Denis Golovin > Assignee: Konstantin Marmalyukov > Priority: Critical > Labels: f2f2014, respin-a > Fix For: 4.2.2.Final, 4.3.0.Alpha1 > > > Imagine that one first clean workspace startup on opening vpe on systems where xulrunner / webkit can't run at the same time we will ask if he prefers to have good JSF support (use xulrunner) or HTML5 support (disable xulrunner) > if he says okey - we set a flag somewhere to not start xulrunner. > user restart - user is happy. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18177) Request at first start what is more important JSF or HTML5 support and enable/disable XULRunner

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18177?page=com.atlassian.jira.plugi... ] Alexey Kazakov commented on JBIDE-18177: ---------------------------------------- I added a few comments in github - https://github.com/jbosstools/jbosstools-vpe/pull/295 But I think we are not ready to push this PR to 4.2.1. We have one day for development and a week for testing before 4.2.1.Final. What I'm suggesting: 1. Finish review of the PR ([~maxandersen], [~dgolovin], [~fbricon], any input?), fix all found issues/questions) 2. Merge it to master 3. Ask [~vpakan] to test it in the next nightly build (Vlado, please speak up if you have any problems with this) 4. If everything is OK then push it to 4.2.2 stream. So, I'm moving the issue to 4.2.2.Final. [~maxandersen], guys, WDYT? > Request at first start what is more important JSF or HTML5 support and enable/disable XULRunner > ----------------------------------------------------------------------------------------------- > > Key: JBIDE-18177 > URL: https://issues.jboss.org/browse/JBIDE-18177 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: visual-page-editor-core, xulrunner > Affects Versions: 4.2.0.CR1 > Reporter: Denis Golovin > Assignee: Konstantin Marmalyukov > Priority: Critical > Labels: f2f2014, respin-a > Fix For: 4.2.2.Final, 4.3.0.Alpha1 > > > Imagine that one first clean workspace startup on opening vpe on systems where xulrunner / webkit can't run at the same time we will ask if he prefers to have good JSF support (use xulrunner) or HTML5 support (disable xulrunner) > if he says okey - we set a flag somewhere to not start xulrunner. > user restart - user is happy. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3208) reorg/refactor directories for consistency across JBT/JBDS

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3208?page=com.atlassian.jira.plugin.... ] Denis Golovin commented on JBDS-3208: ------------------------------------- That is exactly what I mean :) > reorg/refactor directories for consistency across JBT/JBDS > ---------------------------------------------------------- > > Key: JBDS-3208 > URL: https://issues.jboss.org/browse/JBDS-3208 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: build > Affects Versions: 9.0.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 9.0.0.Alpha1 > > > Be it resolved - we should reorg directories for consistency across JBT/JBDS: > {code} > download.jboss.org > <earlyaccess,updates,discovery>/mars > /snapshots [replace nightly] > /staging [rename content for QE, moves to development when approved] > /development > /stable (updates/mars/stable is a pointer back into updates/mars) > drop /integration (not used) > builds/<jobname>/<buildid> > builds/<jobname>/composite*.xml for last 2 builds > targetplatforms/<type>/<version> > {code} > and > {code} > devstudio.redhat.com > <earlyaccess,updates,discovery>/9.0 > /snapshots > /staging > /development > /stable (updates/9.0/stable is a pointer back into updates/9.0) > builds/<jobname>/<buildid> > builds/<jobname>/composite*.xml for last 2 builds > targetplatforms/<type>/<version> > {code} > Further discussion in http://ether-man.rhcloud.com/p/build.next.20141112 > This would remove the idea of the composite staging site [1] and the composite install job [2], today used to determine when it's time to run the aggregate builds, in favour of a new p2diff mechanism for determining if aggregates should be published. See JBIDE-18742 and JBIDE-16970. > [1] http://download.jboss.org/jbosstools/builds/staging/_composite_/core/4.2.... > [2] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18876) Improve TP publishing so changes released to git or deployed to nexus would not break developer local builds

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18876?page=com.atlassian.jira.plugi... ] Denis Golovin updated JBIDE-18876: ---------------------------------- Workaround Description: 1. Rollback to previous revision and release to local maven repository 2. Sometimes it is possible to use multiple target platform with -Dtpc.targetKind=multiple Workaround: Workaround Exists > Improve TP publishing so changes released to git or deployed to nexus would not break developer local builds > ------------------------------------------------------------------------------------------------------------ > > Key: JBIDE-18876 > URL: https://issues.jboss.org/browse/JBIDE-18876 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.3.0.Alpha1 > Reporter: Denis Golovin > > Latest Thym update is 'good' example for this problem. I was in the middle of testing some changes in parent/pom.xml and suddenly build start to fail with Thym resolution problem. IMO what happened is TP .target files were published to nexus before actual p2-repos appeared online. Building from latest revision didn't help ether because of the same problem. I had to revert to previous revision to continue my task. > So it would be good if TP builds publish binaries first and then release TP sources to git and deploy to nexus. > Please note, that when sftp/rsync for unified TP binaries is finished it doesn't mean p2-repos are available from download.jboss.org right away. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18876) Improve TP publishing so changes released to git or deployed to nexus would not break developer local builds

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18876?page=com.atlassian.jira.plugi... ] Denis Golovin updated JBIDE-18876: ---------------------------------- Issue Type: Bug (was: Task) > Improve TP publishing so changes released to git or deployed to nexus would not break developer local builds > ------------------------------------------------------------------------------------------------------------ > > Key: JBIDE-18876 > URL: https://issues.jboss.org/browse/JBIDE-18876 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.3.0.Alpha1 > Reporter: Denis Golovin > > Latest Thym update is 'good' example for this problem. I was in the middle of testing some changes in parent/pom.xml and suddenly build start to fail with Thym resolution problem. IMO what happened is TP .target files were published to nexus before actual p2-repos appeared online. Building from latest revision didn't help ether because of the same problem. I had to revert to previous revision to continue my task. > So it would be good if TP builds publish binaries first and then release TP sources to git and deploy to nexus. > Please note, that when sftp/rsync for unified TP binaries is finished it doesn't mean p2-repos are available from download.jboss.org right away. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18876) Improve TP publishing so changes released to git or deployed to nexus would not break developer local builds

by Denis Golovin (JIRA)

Denis Golovin created JBIDE-18876: ------------------------------------- Summary: Improve TP publishing so changes released to git or deployed to nexus would not break developer local builds Key: JBIDE-18876 URL: https://issues.jboss.org/browse/JBIDE-18876 Project: Tools (JBoss Tools) Issue Type: Task Components: build Affects Versions: 4.3.0.Alpha1 Reporter: Denis Golovin Latest Thym update is 'good' example for this problem. I was in the middle of testing some changes in parent/pom.xml and suddenly build start to fail with Thym resolution problem. IMO what happened is TP .target files were published to nexus before actual p2-repos appeared online. Building from latest revision didn't help ether because of the same problem. I had to revert to previous revision to continue my task. So it would be good if TP builds publish binaries first and then release TP sources to git and deploy to nexus. Please note, that when sftp/rsync for unified TP binaries is finished it doesn't mean p2-repos are available from download.jboss.org right away. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 4 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 December 2014