March 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (TOOLSDOC-615) Start Developing Guide: Use and Evaluate Guide & Determine Format for JBDS 9.0

by Misha Ali (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-615?page=com.atlassian.jira.plug... ] Misha Ali updated TOOLSDOC-615: ------------------------------- Sprint: 2015/S8 (13-Apr > 26-Apr) 3 (was: 2015/S7 (30-Mar > 12-Apr) 2) > Start Developing Guide: Use and Evaluate Guide & Determine Format for JBDS 9.0 > ------------------------------------------------------------------------------ > > Key: TOOLSDOC-615 > URL: https://issues.jboss.org/browse/TOOLSDOC-615 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Enhancement > Components: Getting Started Guide > Affects Versions: 4.3.0.Final > Reporter: Misha Ali > Assignee: Misha Ali > > Requirements: > * Use the current Start Developing Guide to test content > * Review contents and determine if this would be better as a new series of articles rather than a document for 9.0 -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19494) Migrate Livereload to Jetty 9

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19494?page=com.atlassian.jira.plugi... ] Mickael Istria updated JBIDE-19494: ----------------------------------- Summary: Migrate Livereload to Jetty 9 (was: Migrate to Jetty 9) > Migrate Livereload to Jetty 9 > ----------------------------- > > Key: JBIDE-19494 > URL: https://issues.jboss.org/browse/JBIDE-19494 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: livereload > Reporter: Xavier Coulon > Assignee: Xavier Coulon > Fix For: 4.3.0.Alpha2 > > > Following JBIDE-18804 which migrates to Jetty 9, we should also do the move to have a single version of the Jetty bundles in our TP. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19497) Use Jetty 9 in TP

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19497?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-19497: ---------------------------------------- PR including Jetty 9 was merged. [~ibuziuk] & [~xcoulon] Please report there once your code is successfully migrated to Jetty 9 so we can get rid of Jetty 8 references in TP. > Use Jetty 9 in TP > ----------------- > > Key: JBIDE-19497 > URL: https://issues.jboss.org/browse/JBIDE-19497 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: target-platform > Affects Versions: 4.3.0.Alpha2 > Reporter: Mickael Istria > Assignee: Ilya Buziuk > > *Reason:* It seems like we are ready to move away from Jetty 8 and to use Jetty 9 in CordovaSim & LiveReload. We should update TP to include all Jetty 9 bundles > *Project page/sources:* https://www.eclipse.org/jetty/ > *Version:* 9.2.5.v20141112 > *License and owner:* Eclipse.org > *Original p2 repo:* http://download.eclipse.org/jetty/updates/jetty-bundles-9.x/9.2.5.v20141112/ > *JBoss mirror:* http://download.jboss.org/jbosstools/updates/requirements/jetty/9.2.5.v20... > *Include Sources:* Yes > *Affected projects:* Livereload, Cordovasim, BrowserSim > *Include in JBDS:* Yes > *Type of dependency:* distribution > *List of bundles added/removed:* > {code} > TODO: suggested diff on the .target files/p2diff > {code} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-621) Rework and Finalize Article about Generating a HTML5 Web App

by Misha Ali (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-621?page=com.atlassian.jira.plug... ] Misha Ali reassigned TOOLSDOC-621: ---------------------------------- Priority: Minor (was: Major) Assignee: Supriya Bharadwaj (was: Misha Ali) Estimated Difficulty: Medium Component/s: General documentation issues > Rework and Finalize Article about Generating a HTML5 Web App > ------------------------------------------------------------ > > Key: TOOLSDOC-621 > URL: https://issues.jboss.org/browse/TOOLSDOC-621 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Bug > Components: General documentation issues > Reporter: Misha Ali > Assignee: Supriya Bharadwaj > Priority: Minor > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-621) Rework and Finalize Article about Generating a HTML5 Web App

by Misha Ali (JIRA)

Misha Ali created TOOLSDOC-621: ---------------------------------- Summary: Rework and Finalize Article about Generating a HTML5 Web App Key: TOOLSDOC-621 URL: https://issues.jboss.org/browse/TOOLSDOC-621 Project: Documentation for JBoss Tools and Developer Studio Issue Type: Bug Reporter: Misha Ali Assignee: Misha Ali -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-620) How to work with remote server docs missing

by Misha Ali (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-620?page=com.atlassian.jira.plug... ] Misha Ali updated TOOLSDOC-620: ------------------------------- Sprint: 2015/S7 (30-Mar > 12-Apr) 2 (was: 2015/S6 (16-Mar > 29-Mar)) > How to work with remote server docs missing > ------------------------------------------- > > Key: TOOLSDOC-620 > URL: https://issues.jboss.org/browse/TOOLSDOC-620 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Bug > Components: General documentation issues > Affects Versions: 4.1.2 > Environment: JBoss Developer Studio 8.0.x > Reporter: Mustafa Musaji > Assignee: Misha Ali > > Our docs for JBDS 8.0.x don't cover how to add a remote server in JBDS: https://access.redhat.com/documentation/en-US/Red_Hat_JBoss_Developer_Stu... > For 7.x we had this so it would be good if we could get the same for 8.x releases on the Customer Portal. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-613) Document Using Maven

by Misha Ali (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-613?page=com.atlassian.jira.plug... ] Misha Ali updated TOOLSDOC-613: ------------------------------- Sprint: 2015/S7 (30-Mar > 12-Apr) 2 (was: 2015/S6 (16-Mar > 29-Mar)) > Document Using Maven > -------------------- > > Key: TOOLSDOC-613 > URL: https://issues.jboss.org/browse/TOOLSDOC-613 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Feature Request > Components: General documentation issues > Reporter: Misha Ali > Assignee: Misha Ali > Labels: maven > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19533) Missing schemas for WildFly configuration

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19533?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-19533: -------------------------------- Component/s: server > Missing schemas for WildFly configuration > ------------------------------------------ > > Key: JBIDE-19533 > URL: https://issues.jboss.org/browse/JBIDE-19533 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.2.Final > Reporter: Harald Wellmann > > The plugin specified entries in the Eclipse XML catalog are missing entries for the following namespaces used by WildFly 8.2.0.Final configuration files: > * urn:jboss:domain:2.2 > * urn:jboss:domain:undertow:1.2 > As a result, XML validation in Eclipse fails. > Workaround: Add user-defined catalog entries manually. > (Note: WildFly 9.0.0.Beta1 has further schema updates - I'm not sure if these are supposed to be covered by the stable release line of JBoss Tools.) -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19533) Missing schemas for WildFly configuration

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19533?page=com.atlassian.jira.plugi... ] Fred Bricon reassigned JBIDE-19533: ----------------------------------- Assignee: Rob Stryker > Missing schemas for WildFly configuration > ------------------------------------------ > > Key: JBIDE-19533 > URL: https://issues.jboss.org/browse/JBIDE-19533 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.2.Final > Reporter: Harald Wellmann > Assignee: Rob Stryker > > The plugin specified entries in the Eclipse XML catalog are missing entries for the following namespaces used by WildFly 8.2.0.Final configuration files: > * urn:jboss:domain:2.2 > * urn:jboss:domain:undertow:1.2 > As a result, XML validation in Eclipse fails. > Workaround: Add user-defined catalog entries manually. > (Note: WildFly 9.0.0.Beta1 has further schema updates - I'm not sure if these are supposed to be covered by the stable release line of JBoss Tools.) -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19521) Connection wizard: should show authentication form as soon as server type is selected

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19521?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-19521: ------------------------------------- Description: # ASSERT: make sure you have only v3 plugins installed (only v3 OpenShift has no default server so that the wizard comes up with an empty server url) # EXEC: launch connection wizard (in Explorer, hit "New Connection") # ASSERT: wizard comes up with "OpenShift v3" preselected in Server Type # ASSERT: wizard comes up with empty Server url Result: No authentication form is show, the pane is empty Expected result: We should have the authentication form for OpenShift v3 and be able to provide credentials. > Connection wizard: should show authentication form as soon as server type is selected > ------------------------------------------------------------------------------------- > > Key: JBIDE-19521 > URL: https://issues.jboss.org/browse/JBIDE-19521 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.0.Alpha2 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.3.0.Alpha2 > > > # ASSERT: make sure you have only v3 plugins installed (only v3 OpenShift has no default server so that the wizard comes up with an empty server url) > # EXEC: launch connection wizard (in Explorer, hit "New Connection") > # ASSERT: wizard comes up with "OpenShift v3" preselected in Server Type > # ASSERT: wizard comes up with empty Server url > Result: > No authentication form is show, the pane is empty > Expected result: > We should have the authentication form for OpenShift v3 and be able to provide credentials. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 11 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 March 2015