March 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-3270) Cordova App Icon Support

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-3270?page=com.atlassian.jira.plugin.... ] CDW Engine updated JBDS-3270: ----------------------------- CDW release: + (was: ?) > Cordova App Icon Support > ------------------------ > > Key: JBDS-3270 > URL: https://issues.jboss.org/browse/JBDS-3270 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: aerogear-hybrid, requirements > Reporter: Burr Sutter > Assignee: Gorkem Ercan > Fix For: 9.0.0.Alpha2 > > > As a HTML5-focused, Cordova mobile app developer, I need to change the icon associated with my mobile application. The icon on the end-user's home screen. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-19468) [ERROR] Non-resolvable import POM: Could not find artifact org.jboss.forge:forge-bom:pom:2.15.2.Final in redhat-techpreview-all-repository (http://maven.repository.redhat.com/techpreview/all/) @ line 16, column 19

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19468?page=com.atlassian.jira.plugi... ] Pavol Srna updated JBIDE-19468: ------------------------------- Attachment: forge-err.png > [ERROR] Non-resolvable import POM: Could not find artifact org.jboss.forge:forge-bom:pom:2.15.2.Final in redhat-techpreview-all-repository (http://maven.repository.redhat.com/techpreview/all/) @ line 16, column 19 > --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-19468 > URL: https://issues.jboss.org/browse/JBIDE-19468 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Affects Versions: 4.2.3.CR1 > Reporter: Pavol Srna > Fix For: 4.2.3.CR1 > > Attachments: forge-err.png > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-19468) [ERROR] Non-resolvable import POM: Could not find artifact org.jboss.forge:forge-bom:pom:2.15.2.Final in redhat-techpreview-all-repository (http://maven.repository.redhat.com/techpreview/all/) @ line 16, column 19

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19468?page=com.atlassian.jira.plugi... ] Pavol Srna updated JBIDE-19468: ------------------------------- Fix Version/s: 4.2.3.CR1 > [ERROR] Non-resolvable import POM: Could not find artifact org.jboss.forge:forge-bom:pom:2.15.2.Final in redhat-techpreview-all-repository (http://maven.repository.redhat.com/techpreview/all/) @ line 16, column 19 > --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-19468 > URL: https://issues.jboss.org/browse/JBIDE-19468 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Affects Versions: 4.2.3.CR1 > Reporter: Pavol Srna > Fix For: 4.2.3.CR1 > > Attachments: forge-err.png > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-19468) [ERROR] Non-resolvable import POM: Could not find artifact org.jboss.forge:forge-bom:pom:2.15.2.Final in redhat-techpreview-all-repository (http://maven.repository.redhat.com/techpreview/all/) @ line 16, column 19

by Pavol Srna (JIRA)

Pavol Srna created JBIDE-19468: ---------------------------------- Summary: [ERROR] Non-resolvable import POM: Could not find artifact org.jboss.forge:forge-bom:pom:2.15.2.Final in redhat-techpreview-all-repository (http://maven.repository.redhat.com/techpreview/all/) @ line 16, column 19 Key: JBIDE-19468 URL: https://issues.jboss.org/browse/JBIDE-19468 Project: Tools (JBoss Tools) Issue Type: Bug Components: forge Affects Versions: 4.2.3.CR1 Reporter: Pavol Srna -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-612) Generate Release Notes for JBDS-IS 7.1 GA

by Misha Ali (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-612?page=com.atlassian.jira.plug... ] Misha Ali commented on TOOLSDOC-612: ------------------------------------ >From mmakovy, who was asked to review the teiid part of the RN: Hi all, I think it is OK. Some JIRAs are not closed, but these are issues with eclipse Luna(JBDS 8) and JBDS-IS 8.x , these are not problems with Kepler(JBDS 7) and JBDS-IS 7.x . Matus Waiting for Andrej's sign off on the rest of the feedback and then we're good to publish. > Generate Release Notes for JBDS-IS 7.1 GA > ----------------------------------------- > > Key: TOOLSDOC-612 > URL: https://issues.jboss.org/browse/TOOLSDOC-612 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Task > Components: Release Notes > Reporter: Misha Ali > Assignee: Misha Ali > Labels: Notes, Release, Tooling > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-3251) Create screencasts for top features we like users to know more about from both JBoss Tools and base Eclipse

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBDS-3251?page=com.atlassian.jira.plugin.... ] Len DiMaggio updated JBDS-3251: ------------------------------- CDW qa_ack: + (was: ?) > Create screencasts for top features we like users to know more about from both JBoss Tools and base Eclipse > ----------------------------------------------------------------------------------------------------------- > > Key: JBDS-3251 > URL: https://issues.jboss.org/browse/JBDS-3251 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Epic > Components: documentation, requirements > Reporter: Max Rydahl Andersen > Assignee: Misha Ali > Fix For: 9.0.0.GA > > > suggestions from F2F: > |Maven Top 10 Use Cases| Import, multi-module, run on server, package vs install, update, adjust profiles, dependencies adds/removes| > |Java EE Top 10 Use Cases JPA, db reveng, JAX-RS (including testing), CDI, content assist, Servlets, JSF, etc > HTML5/Hybrid Mobile| > |OpenShift v3| start, stop, deploy apps > |eGit Top Use Cases| -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-3305) Support OpenShift v2

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBDS-3305?page=com.atlassian.jira.plugin.... ] Len DiMaggio updated JBDS-3305: ------------------------------- CDW qa_ack: + (was: ?) > Support OpenShift v2 > --------------------- > > Key: JBDS-3305 > URL: https://issues.jboss.org/browse/JBDS-3305 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Epic > Components: openshift, requirements > Reporter: Max Rydahl Andersen > Assignee: Andre Dietisheim > Fix For: 9.0.0.CR1 > > > OpenShift v2 is online and supported and needs to be maintained/updated. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-3298) Push changes to Existing OpenShift Project

by Burr Sutter (JIRA)

[ https://issues.jboss.org/browse/JBDS-3298?page=com.atlassian.jira.plugin.... ] Burr Sutter updated JBDS-3298: ------------------------------ CDW pm_ack: + (was: ?) > Push changes to Existing OpenShift Project > ------------------------------------------ > > Key: JBDS-3298 > URL: https://issues.jboss.org/browse/JBDS-3298 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: openshift, requirements > Affects Versions: 8.0.0.GA > Reporter: Burr Sutter > Assignee: Max Rydahl Andersen > Priority: Blocker > Fix For: 9.0.0.Beta1 > > > Use Case #2 Push changes to Existing OpenShift Project > a) assumes the steps in Use Case #1 JBDS-3297 > b) assumes the end-user has uploaded his SSH keys (to allow for git push) > c) Eclipse user will add, edit and delete files from the originally downloaded/imported set of files - leveraging Eclipse specialized editors, content-assist, etc > d) Eclipse user will run (deploy) Maven-based Java projects on a local EAP > e) Eclipse user will test (JUnit, Arquillian) > f) Eclipse user will debug with the local EAP (run on localhost or from Docker Image) > g) Eclipse user will git add and git commit as appropriate > h) Eclipse user will git push to the original URL provided in Use Case #1 > i) Eclipse user will await the automatic rebuild of a new image, deployment of the same > j) Eclipse user will then be provided a URL and the browser can be opened automatically > Note: > i) auto-build=true, auto-deploy=true > assumes the auto-build (.war and docker image) upon git push enabled in Use Case #1c (JBDS-3297). This step also assumes the auto-deploy upon build is enabled in 1c. > A future variation of #2 should allow for "auto-build=false" and "auto-deploy=true" with hot deployment of the binary .war or .ear. > If auto-build=false and auto-deploy=false then the Eclipse user will simply receive a message that his git push was successful, no URL, no browser opening. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-3298) Push changes to Existing OpenShift Project

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-3298?page=com.atlassian.jira.plugin.... ] CDW Engine updated JBDS-3298: ----------------------------- CDW docs_ack: ? CDW devel_ack: ? > Push changes to Existing OpenShift Project > ------------------------------------------ > > Key: JBDS-3298 > URL: https://issues.jboss.org/browse/JBDS-3298 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: openshift, requirements > Affects Versions: 8.0.0.GA > Reporter: Burr Sutter > Assignee: Max Rydahl Andersen > Priority: Blocker > Fix For: 9.0.0.Beta1 > > > Use Case #2 Push changes to Existing OpenShift Project > a) assumes the steps in Use Case #1 JBDS-3297 > b) assumes the end-user has uploaded his SSH keys (to allow for git push) > c) Eclipse user will add, edit and delete files from the originally downloaded/imported set of files - leveraging Eclipse specialized editors, content-assist, etc > d) Eclipse user will run (deploy) Maven-based Java projects on a local EAP > e) Eclipse user will test (JUnit, Arquillian) > f) Eclipse user will debug with the local EAP (run on localhost or from Docker Image) > g) Eclipse user will git add and git commit as appropriate > h) Eclipse user will git push to the original URL provided in Use Case #1 > i) Eclipse user will await the automatic rebuild of a new image, deployment of the same > j) Eclipse user will then be provided a URL and the browser can be opened automatically > Note: > i) auto-build=true, auto-deploy=true > assumes the auto-build (.war and docker image) upon git push enabled in Use Case #1c (JBDS-3297). This step also assumes the auto-deploy upon build is enabled in 1c. > A future variation of #2 should allow for "auto-build=false" and "auto-deploy=true" with hot deployment of the binary .war or .ear. > If auto-build=false and auto-deploy=false then the Eclipse user will simply receive a message that his git push was successful, no URL, no browser opening. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-3284) Ionic Palette - version selection, detection

by Burr Sutter (JIRA)

[ https://issues.jboss.org/browse/JBDS-3284?page=com.atlassian.jira.plugin.... ] Burr Sutter updated JBDS-3284: ------------------------------ CDW pm_ack: + (was: ?) > Ionic Palette - version selection, detection > -------------------------------------------- > > Key: JBDS-3284 > URL: https://issues.jboss.org/browse/JBDS-3284 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: jsp/jsf/xml/html source editing, requirements > Reporter: Burr Sutter > Assignee: Alexey Kazakov > Fix For: 9.0.0.Beta2 > > > As a Cordova-focused hybrid mobile app developer, I need to be able to import existing Ionic projects and modify the version of the Ionic framework, where the Palette is flexible enough to handle version changes, including addition/subtraction of specific widgets only available in particular versions. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 1 month

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