June 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-19785) CordovaSim does not work with cordova-android-4.0.0

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19785?page=com.atlassian.jira.plugi... ] Ilya Buziuk updated JBIDE-19785: -------------------------------- Fix Version/s: 4.3.0.Beta2 (was: 4.3.0.Beta1) > CordovaSim does not work with cordova-android-4.0.0 > --------------------------------------------------- > > Key: JBIDE-19785 > URL: https://issues.jboss.org/browse/JBIDE-19785 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cordovasim > Affects Versions: 4.3.0.Alpha2 > Reporter: Ilya Buziuk > Assignee: Ilya Buziuk > Priority: Critical > Labels: upstream > Fix For: 4.3.0.Beta2 > > > The upstream issues: > - https://issues.apache.org/jira/browse/RIPPLE-82 > - https://issues.apache.org/jira/browse/CB-8971 > Basically, need to wait for republication of all affected platforms (this release would be broken for both Ripple and CordovaSim) -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19899) Add usage tracking of which browser name and version is used

by Konstantin Marmalyukov (JIRA)

Konstantin Marmalyukov created JBIDE-19899: ---------------------------------------------- Summary: Add usage tracking of which browser name and version is used Key: JBIDE-19899 URL: https://issues.jboss.org/browse/JBIDE-19899 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: central, usage Affects Versions: 4.3.0.Beta1 Reporter: Konstantin Marmalyukov Assignee: Konstantin Marmalyukov Fix For: 4.3.0.Beta1 There will be good to know which browser our users have. Central is the best place for that: it will be opened at least at the first start and already has an API which detects browser name and version. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19845) Project context menu: Creating a new OpenShift application via Configure always uses first connection from OpenShift Explorer view

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19845?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-19845: ------------------------------------------ merged and pushed to upstream/master > Project context menu: Creating a new OpenShift application via Configure always uses first connection from OpenShift Explorer view > ---------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-19845 > URL: https://issues.jboss.org/browse/JBIDE-19845 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Beta1 > Reporter: Marián Labuda > Assignee: Andre Dietisheim > Priority: Critical > Labels: application_wizard > Fix For: 4.3.0.Beta1 > > > If user wants to create a new OpenShift application via context menu of a project, it is possible to do it via context menu "Configure - New/Import OpenShift application". Previously this selection prompted user to choose desired connection where to create a new application. Nowadays the first existing connection in OpenShift explorer view is selected and it is not possible to change connection. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19604) Save Password in New Openshift Application Wizard is annoying

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19604?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-19604: ------------------------------------------ postponing since not critical enough to require fix in 4.3.0.Beta1 > Save Password in New Openshift Application Wizard is annoying > ------------------------------------------------------------- > > Key: JBIDE-19604 > URL: https://issues.jboss.org/browse/JBIDE-19604 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Alpha2 > Environment: Linux, x86_64, Open JDK 7 > Reporter: Denis Golovin > Assignee: Andre Dietisheim > Fix For: 4.3.0.Beta2 > > Attachments: openshif-save-password.mp4 > > > Selected "Save Password" option in wizard triggers secure storage login that cannot be canceled in on click. This dialog keeps coming back after Cancel is pressed (three or more times). After reopening wizard first Security Storage Login pops up that I have to Cancel it several times (see attached video). -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19604) Save Password in New Openshift Application Wizard is annoying

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19604?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-19604: ------------------------------------- Fix Version/s: 4.3.0.Beta2 (was: 4.3.0.Beta1) > Save Password in New Openshift Application Wizard is annoying > ------------------------------------------------------------- > > Key: JBIDE-19604 > URL: https://issues.jboss.org/browse/JBIDE-19604 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Alpha2 > Environment: Linux, x86_64, Open JDK 7 > Reporter: Denis Golovin > Assignee: Andre Dietisheim > Fix For: 4.3.0.Beta2 > > Attachments: openshif-save-password.mp4 > > > Selected "Save Password" option in wizard triggers secure storage login that cannot be canceled in on click. This dialog keeps coming back after Cancel is pressed (three or more times). After reopening wizard first Security Storage Login pops up that I have to Cancel it several times (see attached video). -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13835) Improve publish script (split? Move to maven?)

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13835?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-13835: ---------------------------------------- [~nickboldt] I believe we've made sufficient progress on the publish script itself, so that next steps are more about its adoption (JBIDE-18772). Should we mark this jira as resolved? > Improve publish script (split? Move to maven?) > ---------------------------------------------- > > Key: JBIDE-13835 > URL: https://issues.jboss.org/browse/JBIDE-13835 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Reporter: Mickael Istria > Assignee: Nick Boldt > Fix For: 4.3.0.Beta1 > > > Publish script deals with a lot of different and not-always-related things. It makes it difficult to maintain it. We should think about some improvements such as > * different conventions from different stream > * components vs aggregate > * devstudio vs jbosstools. > Or, > * Make publishing part of a "mvn deploy" step. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18772) Include publish steps in pom files

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18772?page=com.atlassian.jira.plugi... ] Mickael Istria edited comment on JBIDE-18772 at 6/2/15 4:47 AM: ---------------------------------------------------------------- Needs changes: * devstudio.product : requires more specific steps, so pom has to be changed * jbosstools-browsersim-standalone : doesn't match the generic deployment procedure, so its pom requires some customization * jbosstools-discovery : requires more specific steps, as generic process isn't covering this case * jbosstools-integration-stack-tests.aggregate : Needs additional configuration to publish also to snapshot location. See https://github.com/jbosstools/jbosstools-build-sites/commit/38e4126546c55... as example. cc [~mmalina] * jbosstools-integration-tests.aggregate : Needs additional configuration to publish also to snapshot location. See https://github.com/jbosstools/jbosstools-build-sites/commit/38e4126546c55... as example. cc [~mmalina] * RedDeer_master : Does NOT use JBoss Tools parent, so configuration of the deploy-to-jboss profile from JBT parent pom has to be duplicated to Red Deer before updating the job. cc [~mmalina] Nothing to change: * jbosstools-locus.site : Latest version only seems to be published and consumed only through Nexus (in all .target definition I've checked), so it's just a regular "mvn deploy", without any other publish step necessary (more like JBIDE-16128 ). Nothing to change on the job. was (Author: mickael_istria): * devstudio.product : requires more specific steps, so pom has to be changed * jbosstools-browsersim-standalone : doesn't match the generic deployment procedure, so its pom requires some customization * jbosstools-discovery : requires more specific steps, as generic process isn't covering this case * jbosstools-integration-stack-tests.aggregate : Needs additional configuration to publish also to snapshot location. See https://github.com/jbosstools/jbosstools-build-sites/commit/38e4126546c55... as example. cc [~mmalina] * jbosstools-integration-tests.aggregate : Needs additional configuration to publish also to snapshot location. See https://github.com/jbosstools/jbosstools-build-sites/commit/38e4126546c55... as example. cc [~mmalina] * jbosstools-locus.site : Latest version only seems to be published and consumed only through Nexus (in all .target definition I've checked), so it's just a regular "mvn deploy", without any other publish step necessary (more like JBIDE-16128 ). Nothing to change on the job. * RedDeer_master : Does NOT use JBoss Tools parent, so configuration of the deploy-to-jboss profile from JBT parent pom has to be duplicated to Red Deer before updating the job. cc [~mmalina] > Include publish steps in pom files > ---------------------------------- > > Key: JBIDE-18772 > URL: https://issues.jboss.org/browse/JBIDE-18772 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Reporter: Max Rydahl Andersen > Assignee: Mickael Istria > Priority: Critical > Fix For: 4.3.0.Beta1 > > Attachments: jbds-publish-to-snapshots.png > > > instead of relying to publish.sh being on master, we should use a versioned publish.sh (or maybe even mojo) that the build then uses. > suggestion: > publish.sh (or mojo) gets released to our maven repo, use it in the pom.xml to perform publishing. > What this helps with is: > a) can do changes to publish mechanism without affecting every past builds. > b) more movable build system > c) isolated testing possible > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18772) Include publish steps in pom files

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18772?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-18772: ---------------------------------------- * devstudio.product : requires more specific steps, so pom has to be changed * jbosstools-browsersim-standalone : doesn't match the generic deployment procedure, so its pom requires some customization * jbosstools-discovery : requires more specific steps, as generic process isn't covering this case * jbosstools-integration-stack-tests.aggregate : Needs additional configuration to publish also to snapshot location. See https://github.com/jbosstools/jbosstools-build-sites/commit/38e4126546c55... as example. cc [~mmalina] * jbosstools-integration-tests.aggregate : Needs additional configuration to publish also to snapshot location. See https://github.com/jbosstools/jbosstools-build-sites/commit/38e4126546c55... as example. cc [~mmalina] * jbosstools-locus.site : Latest version only seems to be published and consumed only through Nexus (in all .target definition I've checked), so it's just a regular "mvn deploy", without any other publish step necessary (more like JBIDE-16128 ). Nothing to change on the job. * RedDeer_master : Does NOT use JBoss Tools parent, so configuration of the deploy-to-jboss profile from JBT parent pom has to be duplicated to Red Deer before updating the job. cc [~mmalina] > Include publish steps in pom files > ---------------------------------- > > Key: JBIDE-18772 > URL: https://issues.jboss.org/browse/JBIDE-18772 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Reporter: Max Rydahl Andersen > Assignee: Mickael Istria > Priority: Critical > Fix For: 4.3.0.Beta1 > > Attachments: jbds-publish-to-snapshots.png > > > instead of relying to publish.sh being on master, we should use a versioned publish.sh (or maybe even mojo) that the build then uses. > suggestion: > publish.sh (or mojo) gets released to our maven repo, use it in the pom.xml to perform publishing. > What this helps with is: > a) can do changes to publish mechanism without affecting every past builds. > b) more movable build system > c) isolated testing possible > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3449) Add Windows 10 to the support matrix for JBDS 9

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-3449?page=com.atlassian.jira.plugin.... ] CDW Engine updated JBDS-3449: ----------------------------- CDW pm_ack: ? > Add Windows 10 to the support matrix for JBDS 9 > ----------------------------------------------- > > Key: JBDS-3449 > URL: https://issues.jboss.org/browse/JBDS-3449 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: requirements > Affects Versions: 9.0.0.Beta1 > Reporter: Martin Malina > > JBDS 9 GA is currently scheduled for Tue 2015-10-06. > Microsoft announced recently that Windows 10 will come out on July 29. > We should try and support Windows 10 with JBDS 9. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3449) Add Windows 10 to the support matrix for JBDS 9

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBDS-3449?page=com.atlassian.jira.plugin.... ] Martin Malina updated JBDS-3449: -------------------------------- CDW release: ? Status: New (was: New) Target Release: 9.0.0.GA > Add Windows 10 to the support matrix for JBDS 9 > ----------------------------------------------- > > Key: JBDS-3449 > URL: https://issues.jboss.org/browse/JBDS-3449 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: requirements > Affects Versions: 9.0.0.Beta1 > Reporter: Martin Malina > > JBDS 9 GA is currently scheduled for Tue 2015-10-06. > Microsoft announced recently that Windows 10 will come out on July 29. > We should try and support Windows 10 with JBDS 9. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 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 June 2015