July 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBTIS-804) Complete REST test

by stanislav kaleta (JIRA)

stanislav kaleta created JBTIS-804: -------------------------------------- Summary: Complete REST test Key: JBTIS-804 URL: https://issues.jboss.org/browse/JBTIS-804 Project: JBoss Tools Integration Stack Issue Type: Enhancement Components: QE, teiid Affects Versions: 4.3.0.Final Reporter: stanislav kaleta Assignee: stanislav kaleta Fix For: 4.3.1.Final -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22726) Associate jbosstools & devstudio marketplace entries by fileextension to file types opened in Eclipse

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22726?page=com.atlassian.jira.plugi... ] Alexey Kazakov commented on JBIDE-22726: ---------------------------------------- ftl,ftlx,ftlh for Freemarker The rest of our editors is probably associated with .xml extension... Can it be associated with a file extension only? Another question, if we associate some extension with our entry then will user be asked to install the entire devstudio/jbt but not particular feature? > Associate jbosstools & devstudio marketplace entries by fileextension to file types opened in Eclipse > ----------------------------------------------------------------------------------------------------- > > Key: JBIDE-22726 > URL: https://issues.jboss.org/browse/JBIDE-22726 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: marketplace > Affects Versions: 4.4.0.Final > Reporter: Nick Boldt > Assignee: Alexey Kazakov > > I need a list of file extensions we want associated with JBT/devstudio. > Then I can add those to the list of tags on the marketplace entries: > https://marketplace.eclipse.org/content/jboss-tools > https://marketplace.eclipse.org/content/red-hat-jboss-developer-studio > eg., for freemarker, we want to add tag = *fileExtension_ftl* [1] > ref: https://www.eclipse.org/eclipse/news/4.6/platform.php#text-editor-selecti... > ref: https://www.eclipse.org/community/eclipse_newsletter/2016/june/article1.php (see #5) > [1] https://marketplace.eclipse.org/content/freemarker-ide-jboss-tools > related: https://bugs.eclipse.org/bugs/show_bug.cgi?id=480176 > related: https://bugs.eclipse.org/bugs/show_bug.cgi?id=494050 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22728) Script the process for jbosstools projects to move up to the latest parent pom in their root pom & all-tests pom; verify that changes are valid & push to origin

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22728?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-22728: ------------------------------------ Projects to include here are: * jbosstools-aerogear * jbosstools-base * jbosstools-forge * jbosstools-server * jbosstools-webservices * jbosstools-hibernate * jbosstools-vpe * jbosstools-browsersim * jbosstools-jst * jbosstools-javaee * jbosstools-central * jbosstools-arquillian * jbosstools-livereload * jbosstools-openshift * jbosstools-freemarker and * jbosstools-build-sites [needs a new PR builder job?] * jbosstools-integration-tests [needs a new PR builder job?] Projects which are more complicated to move via script: * jbosstools-discovery * jbosstools-build * jbosstools-build-ci, maven-plugins, versionwatch * jbosstools-target-platforms > Script the process for jbosstools projects to move up to the latest parent pom in their root pom & all-tests pom; verify that changes are valid & push to origin > ---------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-22728 > URL: https://issues.jboss.org/browse/JBIDE-22728 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.4.1.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.1.AM2 > > > Current process for moving all the JBT projects to the latest parent pom involves generating 15+ JIRAs assigned to the various project leads, so they can all adopt the latest parent pom, verify their build works, and push the change. > With the advent of PR build jobs, we can now streamline this a little: > instead of creating Task JIRAs, create PRs & let them run automatically. > if they pass, push them in automatically (via script that Alexey or Denis would run) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22728) Script the process for jbosstools projects to move up to the latest parent pom in their root pom & all-tests pom; verify that changes are valid & push to origin

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22728?page=com.atlassian.jira.plugi... ] Nick Boldt reassigned JBIDE-22728: ---------------------------------- Assignee: Nick Boldt > Script the process for jbosstools projects to move up to the latest parent pom in their root pom & all-tests pom; verify that changes are valid & push to origin > ---------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-22728 > URL: https://issues.jboss.org/browse/JBIDE-22728 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.4.1.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.1.AM2 > > > Current process for moving all the JBT projects to the latest parent pom involves generating 15+ JIRAs assigned to the various project leads, so they can all adopt the latest parent pom, verify their build works, and push the change. > With the advent of PR build jobs, we can now streamline this a little: > instead of creating Task JIRAs, create PRs & let them run automatically. > if they pass, push them in automatically (via script that Alexey or Denis would run) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22728) Script the process for jbosstools projects to move up to the latest parent pom in their root pom & all-tests pom; verify that changes are valid & push to origin

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22728?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-22728: ------------------------------- Fix Version/s: 4.4.1.AM2 > Script the process for jbosstools projects to move up to the latest parent pom in their root pom & all-tests pom; verify that changes are valid & push to origin > ---------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-22728 > URL: https://issues.jboss.org/browse/JBIDE-22728 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.4.1.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.1.AM2 > > > Current process for moving all the JBT projects to the latest parent pom involves generating 15+ JIRAs assigned to the various project leads, so they can all adopt the latest parent pom, verify their build works, and push the change. > With the advent of PR build jobs, we can now streamline this a little: > instead of creating Task JIRAs, create PRs & let them run automatically. > if they pass, push them in automatically (via script that Alexey or Denis would run) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22728) Script the process for jbosstools projects to move up to the latest parent pom in their root pom & all-tests pom; verify that changes are valid & push to origin

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-22728: ---------------------------------- Summary: Script the process for jbosstools projects to move up to the latest parent pom in their root pom & all-tests pom; verify that changes are valid & push to origin Key: JBIDE-22728 URL: https://issues.jboss.org/browse/JBIDE-22728 Project: Tools (JBoss Tools) Issue Type: Bug Components: build Affects Versions: 4.4.1.AM1 Reporter: Nick Boldt Current process for moving all the JBT projects to the latest parent pom involves generating 15+ JIRAs assigned to the various project leads, so they can all adopt the latest parent pom, verify their build works, and push the change. With the advent of PR build jobs, we can now streamline this a little: instead of creating Task JIRAs, create PRs & let them run automatically. if they pass, push them in automatically (via script that Alexey or Denis would run) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22727) Openshift resources managed by explorer and watcher are declared in both place leading to inconsistency

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22727?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-22727: ------------------------------- Labels: explorer openshift openshift_v3 (was: ) > Openshift resources managed by explorer and watcher are declared in both place leading to inconsistency > ------------------------------------------------------------------------------------------------------- > > Key: JBIDE-22727 > URL: https://issues.jboss.org/browse/JBIDE-22727 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.1.AM1 > Reporter: Jeff MAURY > Labels: explorer, openshift, openshift_v3 > Fix For: 4.4.1.AM2 > > > The kind of Openshift resources are declated in 2 different places: WatchManager and ConnectionWrapper. This increases the technical debt and may lead to resources displayed by the explorer but not refreshed by the watcher. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22727) Openshift resources managed by explorer and watcher are declared in both place leading to inconsistency

by Jeff MAURY (JIRA)

Jeff MAURY created JBIDE-22727: ---------------------------------- Summary: Openshift resources managed by explorer and watcher are declared in both place leading to inconsistency Key: JBIDE-22727 URL: https://issues.jboss.org/browse/JBIDE-22727 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.4.1.AM1 Reporter: Jeff MAURY Fix For: 4.4.1.AM2 The kind of Openshift resources are declated in 2 different places: WatchManager and ConnectionWrapper. This increases the technical debt and may lead to resources displayed by the explorer but not refreshed by the watcher. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ERT-341) Need to add Chromium / Chrome Runtime for front-end Debugging [EBZ#497765]

by Friendly Jira Robot (JIRA)

Friendly Jira Robot created ERT-341: --------------------------------------- Summary: Need to add Chromium / Chrome Runtime for front-end Debugging [EBZ#497765] Key: ERT-341 URL: https://issues.jboss.org/browse/ERT-341 Project: Eclipse Release Train Issue Type: Task Components: JSDT Reporter: Friendly Jira Robot As part of Neon release mechanism to register different JS Runtime has been implemented (Bug 359436 - Investigate defining browsers / runtimes to use for debugging). The main idea behind this is that is possible to provide different JavaScript runtimes through runtime providers. All of the runtime providers must be associated to a runtime type (previously defined through another extension point), and all those contributions are managed and accessed through a JavaScript runtime manager. Need to add `Chrome / Chromium Runtime` that will be used for front-end debugging. Chromium Runtime will be launched with parameter like --remote-debugging-port=9222 (debug port) / 'www.example.com' (start page). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22726) Associate jbosstools & devstudio marketplace entries by fileextension to file types opened in Eclipse

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-22726: ---------------------------------- Summary: Associate jbosstools & devstudio marketplace entries by fileextension to file types opened in Eclipse Key: JBIDE-22726 URL: https://issues.jboss.org/browse/JBIDE-22726 Project: Tools (JBoss Tools) Issue Type: Bug Components: marketplace Affects Versions: 4.4.0.Final Reporter: Nick Boldt I need a list of file extensions we want associated with JBT/devstudio. Then I can add those to the list of tags on the marketplace entries: https://marketplace.eclipse.org/content/jboss-tools https://marketplace.eclipse.org/content/red-hat-jboss-developer-studio eg., for freemarker, we want to add tag = *fileExtension_ftl* [1] ref: https://www.eclipse.org/eclipse/news/4.6/platform.php#text-editor-selecti... ref: https://www.eclipse.org/community/eclipse_newsletter/2016/june/article1.php (see #5) [1] https://marketplace.eclipse.org/content/freemarker-ide-jboss-tools related: https://bugs.eclipse.org/bugs/show_bug.cgi?id=480176 related: https://bugs.eclipse.org/bugs/show_bug.cgi?id=494050 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 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 July 2016