December 2014 - jbosstools-issues

[JBoss JIRA] (JBTIS-376) Update IS site category definitions to include separate Fuse selection.

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-376?page=com.atlassian.jira.plugin.... ] Paul Leacu resolved JBTIS-376. ------------------------------ Fix Version/s: 8.0.0.GA 4.2.0.Final Resolution: Done https://github.com/jbosstools/jbosstools-integration-stack/commit/bd3cacd... > Update IS site category definitions to include separate Fuse selection. > ----------------------------------------------------------------------- > > Key: JBTIS-376 > URL: https://issues.jboss.org/browse/JBTIS-376 > Project: JBoss Tools Integration Stack > Issue Type: Feature Request > Components: distribution > Affects Versions: 8.0.0.Beta2, 4.2.0.Alpha2 > Reporter: Paul Leacu > Assignee: Paul Leacu > Fix For: 8.0.0.GA, 4.2.0.Final > > > JBoss Central and (soon) Eclipse MarketPlace will have a separate selectable Fuse tooling category. Update the p2 site category defintion as well. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18678) Make dependencies to org.jboss.tools.usage optional

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18678?page=com.atlassian.jira.plugi... ] Ilya Buziuk commented on JBIDE-18678: ------------------------------------- BrowserSim / CordovaSim work fine against this PR + 1 to apply > Make dependencies to org.jboss.tools.usage optional > --------------------------------------------------- > > Key: JBIDE-18678 > URL: https://issues.jboss.org/browse/JBIDE-18678 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: browsersim, usage > Affects Versions: 4.2.0.CR1 > Reporter: Kaloyan Raev > Assignee: Alexey Kazakov > Fix For: 4.3.x > > > I am interested in adopting the CordovaSim feature in our product. However, most of the browsersim bundles have a strong dependency to org.jboss.tools.usage bundle, which force a Usage Reporting popup on startup. I want to avoid this and have the org.jboss.tools.usage excluded from my build. > Is it possible to make the dependencies to org.jboss.tools.usage optional? -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18924) Cordovasim: Url parameter for the start page disappears after refresh / device changing for JavaFx web-engine Oracle JDK 8

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18924?page=com.atlassian.jira.plugi... ] Ilya Buziuk commented on JBIDE-18924: ------------------------------------- [~gercan] shell we create a duplicate for 4.2.x ? > Cordovasim: Url parameter for the start page disappears after refresh / device changing for JavaFx web-engine Oracle JDK 8 > -------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-18924 > URL: https://issues.jboss.org/browse/JBIDE-18924 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cordovasim > Affects Versions: 4.2.0.Final > Reporter: Ilya Buziuk > Assignee: Ilya Buziuk > Fix For: 4.3.0.Alpha1 > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3295) Product update fails on windows if installation folder and user home are on different devices

by Anthony Hebig (JIRA)

[ https://issues.jboss.org/browse/JBDS-3295?page=com.atlassian.jira.plugin.... ] Anthony Hebig commented on JBDS-3295: ------------------------------------- Thanks Moneim Emad ! Simple and smart workaround ! > Product update fails on windows if installation folder and user home are on different devices > --------------------------------------------------------------------------------------------- > > Key: JBDS-3295 > URL: https://issues.jboss.org/browse/JBDS-3295 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: p2-product > Affects Versions: 8.0.1.GA > Environment: Windows > Reporter: Denis Golovin > Assignee: Denis Golovin > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18986) Insert Tag dialog has wrong text highlighting for Add References JS/CSS Tool

by Denis Golovin (JIRA)

Denis Golovin created JBIDE-18986: ------------------------------------- Summary: Insert Tag dialog has wrong text highlighting for Add References JS/CSS Tool Key: JBIDE-18986 URL: https://issues.jboss.org/browse/JBIDE-18986 Project: Tools (JBoss Tools) Issue Type: Bug Components: jsp/jsf/xml/html source editing Affects Versions: 4.3.0.Alpha1 Environment: Ubuntu Linux X86_64 OpenJDK 7 Reporter: Denis Golovin Priority: Minor Attachments: insert-ionic-links.png !insert-ionic-links.png! -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18986) Insert Tag dialog has wrong text highlighting for Add References JS/CSS Tool

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18986?page=com.atlassian.jira.plugi... ] Denis Golovin updated JBIDE-18986: ---------------------------------- Attachment: insert-ionic-links.png > Insert Tag dialog has wrong text highlighting for Add References JS/CSS Tool > ---------------------------------------------------------------------------- > > Key: JBIDE-18986 > URL: https://issues.jboss.org/browse/JBIDE-18986 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsp/jsf/xml/html source editing > Affects Versions: 4.3.0.Alpha1 > Environment: Ubuntu Linux X86_64 > OpenJDK 7 > Reporter: Denis Golovin > Priority: Minor > Attachments: insert-ionic-links.png > > > !insert-ionic-links.png! -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18948) Include new jbosstools-javaee/batch component into aggregated update site

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18948?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-18948: ------------------------------------ How should the new org.jboss.tools.batch.feature be categorized? Choices are listed here: https://github.com/jbosstools/jbosstools-build-sites/blob/master/aggregat... Should this also be included in the JBDS update site as an optional feature users can choose to install? Or should it be in the Central Early Access site? Should it be preinstalled as part of the JBDS installer? > Include new jbosstools-javaee/batch component into aggregated update site > ------------------------------------------------------------------------- > > Key: JBIDE-18948 > URL: https://issues.jboss.org/browse/JBIDE-18948 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build > Reporter: Alexey Kazakov > Assignee: Nick Boldt > Priority: Critical > Fix For: 4.3.0.Alpha1 > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18948) Include new jbosstools-javaee/batch component into aggregated update site

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18948?page=com.atlassian.jira.plugi... ] Nick Boldt reassigned JBIDE-18948: ---------------------------------- Assignee: Alexey Kazakov (was: Nick Boldt) > Include new jbosstools-javaee/batch component into aggregated update site > ------------------------------------------------------------------------- > > Key: JBIDE-18948 > URL: https://issues.jboss.org/browse/JBIDE-18948 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build > Reporter: Alexey Kazakov > Assignee: Alexey Kazakov > Priority: Critical > Fix For: 4.3.0.Alpha1 > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18985) provide tool to audit BUILD_ALIAS in aggregate builds

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-18985: ---------------------------------- Summary: provide tool to audit BUILD_ALIAS in aggregate builds Key: JBIDE-18985 URL: https://issues.jboss.org/browse/JBIDE-18985 Project: Tools (JBoss Tools) Issue Type: Bug Components: build, updatesite Affects Versions: 4.3.0.Alpha1 Reporter: Nick Boldt Based on discussion {quote}Do you have a test for "expected BUILD_ALIAS value in feature qualifiers" ?{quote} Some tests we can run (forgive this pseudocode): {code} // for builds up to a x.y.0 release if ((BUILD_ALIAS in (Alpha*, Beta*, CR*) and jbosstools.version endsWith(".0")) { // make sure all features end in the same BUILD_ALIAS, or Final // if anything doesn't match WARN (want a build to be yellow, not red) } {code} {code} // for GA builds and followup maintenance if ((BUILD_ALIAS in (Final, GA)) { // make sure all com.* features end in GA, and all others end in Final // if anything doesn't match FAIL (want a build to be red) } {code} Once we have that coded, perhaps into a maven enforcer plugin?, we can fine tune it for cases like where Freemarker does an update in Alpha and then does nothing for 4 months, waiting for CR/GA. Should they have to keep updating their root pom just so the BUILD_ALIAS matches and they're building against the correct target platform? Or, should their code remain dormant, but their job's config.xml be updated to override the BUILD_ALIAS & TARGET_PLATFORM values to the correct versions? -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18985) provide tool to audit BUILD_ALIAS in feature qualifiers when aggregated

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18985?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-18985: ------------------------------- Summary: provide tool to audit BUILD_ALIAS in feature qualifiers when aggregated (was: provide tool to audit BUILD_ALIAS in aggregate builds) > provide tool to audit BUILD_ALIAS in feature qualifiers when aggregated > ----------------------------------------------------------------------- > > Key: JBIDE-18985 > URL: https://issues.jboss.org/browse/JBIDE-18985 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, updatesite > Affects Versions: 4.3.0.Alpha1 > Reporter: Nick Boldt > > Based on discussion {quote}Do you have a test for "expected BUILD_ALIAS value in feature qualifiers" ?{quote} > Some tests we can run (forgive this pseudocode): > {code} > // for builds up to a x.y.0 release > if ((BUILD_ALIAS in (Alpha*, Beta*, CR*) and jbosstools.version endsWith(".0")) { > // make sure all features end in the same BUILD_ALIAS, or Final > // if anything doesn't match WARN (want a build to be yellow, not red) > } > {code} > {code} > // for GA builds and followup maintenance > if ((BUILD_ALIAS in (Final, GA)) { > // make sure all com.* features end in GA, and all others end in Final > // if anything doesn't match FAIL (want a build to be red) > } > {code} > Once we have that coded, perhaps into a maven enforcer plugin?, we can fine tune it for cases like where Freemarker does an update in Alpha and then does nothing for 4 months, waiting for CR/GA. > Should they have to keep updating their root pom just so the BUILD_ALIAS matches and they're building against the correct target platform? > Or, should their code remain dormant, but their job's config.xml be updated to override the BUILD_ALIAS & TARGET_PLATFORM values to the correct versions? -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 10 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues December 2014