July 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-20288) v3 Application wizard: should prompt me to create a project if there's no project yet.

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20288?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-20288: ------------------------------------- Labels: application_wizard openshift_v3 (was: ) > v3 Application wizard: should prompt me to create a project if there's no project yet. > -------------------------------------------------------------------------------------- > > Key: JBIDE-20288 > URL: https://issues.jboss.org/browse/JBIDE-20288 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.0.Beta2 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: application_wizard, openshift_v3 > Fix For: 4.3.0.Beta2 > > > If there's no project yet and I launch the application wizard, I should get prompted to create a project. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20288) v3 Application wizard: should prompt me to create a project if there's no project yet.

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20288?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-20288: ------------------------------------------ merged and pushed to upstream/master > v3 Application wizard: should prompt me to create a project if there's no project yet. > -------------------------------------------------------------------------------------- > > Key: JBIDE-20288 > URL: https://issues.jboss.org/browse/JBIDE-20288 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.0.Beta2 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.3.0.Beta2 > > > If there's no project yet and I launch the application wizard, I should get prompted to create a project. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20266) v3 Application wizard: should be able to manage projects in application wizard

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20266?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-20266: ------------------------------------------ merged, pushed to upstream/master > v3 Application wizard: should be able to manage projects in application wizard > ------------------------------------------------------------------------------ > > Key: JBIDE-20266 > URL: https://issues.jboss.org/browse/JBIDE-20266 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.0.Beta2 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: application_wizard, openshift_v3 > Fix For: 4.3.0.Beta2 > > Attachments: manage-domains-link.png, manage-projects-link.png > > > In the v3 application wizard one has to select the project to create the application in. As a user I should be able to manage (create, delete, etc.) projects when in the application wizard. > In v2 this is done via a link "manage domains" next to the combo to select the domain for the application. > !manage-domains-link.png! -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20077) All the Quickstarts from JBoss Central should be available offline

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20077?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-20077: ------------------------------------- postponing to 4.3.0.CR1 due to unforeseen F2F event right before Beta2 code freeze > All the Quickstarts from JBoss Central should be available offline > ------------------------------------------------------------------ > > Key: JBIDE-20077 > URL: https://issues.jboss.org/browse/JBIDE-20077 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: project-examples > Affects Versions: 4.3.0.Beta1 > Reporter: Fred Bricon > Assignee: Fred Bricon > Fix For: 4.3.0.CR1 > > > The offline script doesn't currently support the examples returned in JBoss Central (~200+ projects). > It will most likely make the offline script execution time explode, but you gotta do what you gotta do ... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20077) All the Quickstarts from JBoss Central should be available offline

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20077?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-20077: -------------------------------- Fix Version/s: 4.3.0.CR1 (was: 4.3.0.Beta2) > All the Quickstarts from JBoss Central should be available offline > ------------------------------------------------------------------ > > Key: JBIDE-20077 > URL: https://issues.jboss.org/browse/JBIDE-20077 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: project-examples > Affects Versions: 4.3.0.Beta1 > Reporter: Fred Bricon > Assignee: Fred Bricon > Fix For: 4.3.0.CR1 > > > The offline script doesn't currently support the examples returned in JBoss Central (~200+ projects). > It will most likely make the offline script execution time explode, but you gotta do what you gotta do ... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20288) v3 Application wizard: should prompt me to create a project if there's no project yet.

by Andre Dietisheim (JIRA)

Andre Dietisheim created JBIDE-20288: ---------------------------------------- Summary: v3 Application wizard: should prompt me to create a project if there's no project yet. Key: JBIDE-20288 URL: https://issues.jboss.org/browse/JBIDE-20288 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: openshift Affects Versions: 4.3.0.Beta2 Reporter: Andre Dietisheim Assignee: Andre Dietisheim Fix For: 4.3.0.Beta2 If there's no project yet and I launch the application wizard, I should get prompted to create a project. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20284) For JBIDE 4.3.0.Beta2: Code Freeze + Branch [Arquillian]

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20284?page=com.atlassian.jira.plugi... ] Snjezana Peco closed JBIDE-20284. --------------------------------- Resolution: Done > For JBIDE 4.3.0.Beta2: Code Freeze + Branch [Arquillian] > -------------------------------------------------------- > > Key: JBIDE-20284 > URL: https://issues.jboss.org/browse/JBIDE-20284 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: arquillian > Reporter: Nick Boldt > Assignee: Snjezana Peco > Priority: Blocker > Labels: task > Fix For: 4.3.0.Beta2 > > > For JBIDE 4.3.0.Beta2 [Arquillian]: Please perform the following tasks: > 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.3.0.Beta2 > [Unresolved JIRAs with fixVersion = 4.3.0.Beta2, 9.0.0.Beta2|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%2...] > 1. Branch from your existing master branch into a new *{color:blue}jbosstools-4.3.0.Beta2x{color}* branch; > {code} > git checkout master > git pull origin master > git checkout -b jbosstools-4.3.0.Beta2x > git push origin jbosstools-4.3.0.Beta2x > {code} > 2. *NOW THAT YOU HAVE BRANCHED*, check out your *{color:orange}master branch{color}*. > {code} > git checkout master > git pull origin master > {code} > 3. Update your *{color:orange}master branch{color}* parent pom to use the latest version, *{color:orange}4.3.0.CR1-SNAPSHOT{color}*: > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.3.0.CR1-SNAPSHOT</version> > </parent> > {code} > Now, your root pom will use parent pom version: > * *{color:blue}4.3.0.Beta2-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.3.0.Beta2x{color}* branch, and > * *{color:orange}4.3.0.CR1-SNAPSHOT{color}* in your *{color:orange}master{color}* bran > 4. Close (do not resolve) this JIRA when done. > 5. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20in%20%28JBDS%2...] to do, please complete them next. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Arquillian task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20210) For JBIDE 4.3.0.CR1: Migrate to using license feature in JBT 4.3 / JBDS 9 [Webservices]

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20210?page=com.atlassian.jira.plugi... ] Denis Golovin updated JBIDE-20210: ---------------------------------- Fix Version/s: 4.3.0.Beta2 (was: 4.3.0.CR1) > For JBIDE 4.3.0.CR1: Migrate to using license feature in JBT 4.3 / JBDS 9 [Webservices] > --------------------------------------------------------------------------------------- > > Key: JBIDE-20210 > URL: https://issues.jboss.org/browse/JBIDE-20210 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: webservices > Reporter: Nick Boldt > Assignee: Denis Golovin > Priority: Blocker > Labels: task > Fix For: 4.3.0.Beta2 > > > For JBIDE 4.3.0.CR1 [Webservices]: Please perform the following tasks: > 1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.1.0 or 1.0.100. > 2. Switch to using the new o.j.t.foundation.license.feature. Instructions here: > https://github.com/jbosstools/jbosstools-devdoc/blob/master/source/how_to... > 2. Resolve this JIRA when done. QE can then verify and close it later. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Webservices task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18515) Cordova Plugin discovery wizard has broken layout

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18515?page=com.atlassian.jira.plugi... ] Gorkem Ercan updated JBIDE-18515: --------------------------------- Fix Version/s: 4.3.0.CR1 (was: 4.3.0.Beta2) > Cordova Plugin discovery wizard has broken layout > ------------------------------------------------- > > Key: JBIDE-18515 > URL: https://issues.jboss.org/browse/JBIDE-18515 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid > Affects Versions: 4.2.0.CR1 > Environment: JBT 4.2.0.CR2-v20141005-0541-B267 Fedora 19 KDE 64 bit Java Oracle 8 > Reporter: Vlado Pakan > Priority: Minor > Fix For: 4.3.0.CR1 > > Attachments: brokenlayoutdirectory.png, brokenlayoutgit.png > > > 1. Create Hybrid Mobile Project > 2. Open Cordova Configuration Editor > 3. Open dialog to add plugin from Git > !brokenlayoutgit.png! > 4. Open dialog to add plugin from Directory and select some directory > ERROR: Selected directory is not displayed in dialog > !brokenlayoutdirectory.png! > Once dialog is resized all looks correct in both cases. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19726) Error messages related to failures configuring Cordova version 4 engine are written to .log, and displayed in dialog for only a fraction of a second

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19726?page=com.atlassian.jira.plugi... ] Gorkem Ercan updated JBIDE-19726: --------------------------------- Fix Version/s: 4.3.0.CR1 (was: 4.3.0.Beta2) > Error messages related to failures configuring Cordova version 4 engine are written to .log, and displayed in dialog for only a fraction of a second > ---------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-19726 > URL: https://issues.jboss.org/browse/JBIDE-19726 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid > Affects Versions: 4.3.0.Alpha2 > Reporter: Len DiMaggio > Assignee: Gorkem Ercan > Fix For: 4.3.0.CR1 > > Attachments: IMG_2768.MOV > > > Attempts to configure Cordova version 4.0 fail - another case of changes in directory tree - the errors are written to the .log, and are not communicated to the user via the UI > !ENTRY org.eclipse.thym.android.core 2 0 2015-04-28 11:28:43.882 > !MESSAGE Missing Android engine file /home/ldimaggi/.cordova/lib/android/cordova/4.0.0/framework/cordova-4.0.0.jar > !ENTRY org.eclipse.thym.android.core 2 0 2015-04-28 11:28:43.882 > !MESSAGE Missing Android engine file /home/ldimaggi/.cordova/lib/android/cordova/4.0.0/framework/assets/www/cordova.js > !ENTRY org.eclipse.thym.ios.core 4 0 2015-04-28 11:28:43.882 > !MESSAGE Can not detect version. VERSION file /home/ldimaggi/.cordova/lib/android/cordova/4.0.0/CordovaLib/VERSION is missing -- 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 July 2015