September 2013 - jbosstools-issues

[JBoss JIRA] (JBIDE-15457) CordovaSim and Hybrid tools interaction/source code sharing

by Yahor Radtsevich (JIRA)

Yahor Radtsevich created JBIDE-15457: ---------------------------------------- Summary: CordovaSim and Hybrid tools interaction/source code sharing Key: JBIDE-15457 URL: https://issues.jboss.org/browse/JBIDE-15457 Project: Tools (JBoss Tools) Issue Type: Task Components: aerogear-hybrid, browsersim Reporter: Yahor Radtsevich Assignee: Yahor Radtsevich Fix For: 4.2.x Currently CordovaSim application consists of two parts: a Jetty-based server, and a BrowserSim-based client. The server part generates some content on the fly. For instance, the server may response with generated {{cordova_plugins.js}} content when it is requested by the client. Both parts of CordovaSim are executed in their own JVM, which means they do not have access to the Eclipse API. Hybrid tools do very similar things, but in static way. For instance, while creating Android executables, they create {{cordova_plugins.js}} file on disk. Hybrid tools is a set of Eclipse plugins, so they have access to the Eclipse API. Obviously CordovaSim and Hybrid tools have some code in their sources that could be shared. For the example above, both of them need a method to generate content of {{cordova_plugins.js}}. There are several approaches to implement it: 1. Create two different implementations for CordovaSim and Hybrid tools and synchronize them when needed (currently we do this). This approach creates code duplication problems. 2. Create an Eclipse API-independent plugin, so both CordovaSim and Hybrid tools could set it as a dependency. This approach imposes some restriction on the independent plugin (useful Eclipse API and libs cannot be used). 3. Move the server part of CordovaSim to the Eclipse JVM, so it could use Eclipse API and any Hybrid tools API. With this approach we loose the ability to create standalone CordovaSim in the future. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2734) Forge 2 in JBDS

by Lincoln Baxter III (JIRA)

[ https://issues.jboss.org/browse/JBDS-2734?page=com.atlassian.jira.plugin.... ] Lincoln Baxter III edited comment on JBDS-2734 at 9/5/13 12:30 PM: ------------------------------------------------------------------- Hey Michelle, That sounds good. Here is what we are planning to provide from a functionality point-of-view: * Edit Addons -- Install Addons -- Remove Addons -- Build and Install an Addon * Create a new project with Forge 2 wizard. -- Maven Java -- Maven Resources -- Maven Forge Addon * Java EE -- Setup CDI -- Setup REST -- Setup EJB -- Setup JSF -- Setup Servlet -- Setup JPA * New Entity * New Field * Reverse Engineer Database -- Creates JPA entities in existing Project or Folder * Scaffold -- Setup -- From JPA Entities *** Our BHAG is a Multi-step Wizard that will Step the User through creating a new project, reverse engineering a database, setting up necessary EE specs, and generating scaffolding. However, this does not address how users will/should interact with Forge1 and Forge2. Here is what I would like, and what I believe you suggested in your comments: CTRL+4 should default to Forge 2 out-of-box. The user may then utilize the Eclipse standard "Keys preferences" page to change that setting to Forge1. Via this same mechanism, they may also configure the key to allow them to select Forge1 or Forge2 each time it is pressed. Max can confirm, but I believe this is standard Eclipse config and should not require much implementation on our part. We should not need to change the Forge preferences pane in this release AFAIK. was (Author: lincolnthree): Hey Michelle, That sounds good. Here is what we are planning to provide from a functionality point-of-view: * Edit Addons -- Install Addons -- Remove Addons -- Build and Install an Addon * Create a new project with Forge 2 wizard. -- Maven Java -- Maven Resources -- Maven Forge Addon * Java EE -- Setup CDI -- Setup REST -- Setup JPA * New Entity * New Field -- Setup EJB -- Setup JSF -- Setup Servlet * Reverse Engineer Database -- Creates JPA entities in existing Project or Folder * Scaffold -- Setup -- From JPA Entities *** Our BHAG is a Multi-step Wizard that will Step the User through creating a new project, reverse engineering a database, setting up necessary EE specs, and generating scaffolding. However, this does not address how users will/should interact with Forge1 and Forge2. Here is what I would like, and what I believe you suggested in your comments: CTRL+4 should default to Forge 2 out-of-box. The user may then utilize the Eclipse standard "Keys preferences" page to change that setting to Forge1. Via this same mechanism, they may also configure the key to allow them to select Forge1 or Forge2 each time it is pressed. Max can confirm, but I believe this is standard Eclipse config and should not require much implementation on our part. We should not need to change the Forge preferences pane in this release AFAIK. > Forge 2 in JBDS > --------------- > > Key: JBDS-2734 > URL: https://issues.jboss.org/browse/JBDS-2734 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: forge > Reporter: Burr Sutter > > Is Forge 2 ready to be included in JBDS ? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15433) mvn/tycho does not bump version in site/category.xml

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15433?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen resolved JBIDE-15433. ----------------------------------------- Resolution: Rejected expected behavior, minor now fixed glitch in categoery.xml of livereload thus ersolving this specific issue as rejected. > mvn/tycho does not bump version in site/category.xml > ---------------------------------------------------- > > Key: JBIDE-15433 > URL: https://issues.jboss.org/browse/JBIDE-15433 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build > Reporter: Xavier Coulon > > After running the following command on the livereload component: > {code} > mvn org.eclipse.tycho:tycho-versions-plugin:set-version -DnewVersion=1.2.0-SNAPSHOT > {code} > I could see that all pom.xml, feature.xml and MANIFEST.xml were updated, but not the site/category.xml which I had to edit myself (mvn clean verify failed) > {code} > <site> > <feature url="features/org.jboss.tools.livereload.feature_1.2.0.qualifier.jar" id="org.jboss.tools.livereload.feature" version="1.2.0.qualifier"/> > <feature url="features/org.jboss.tools.livereload.feature.source_1.2.0.qualifier.jar" id="org.jboss.tools.livereload.feature.source" version="1.2.0.qualifier"/> > </site> > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14797) weird question/dialog with missing info when project from archetype/quickstart already exists

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14797?page=com.atlassian.jira.plugi... ] Snjezana Peco reassigned JBIDE-14797: ------------------------------------- Assignee: Fred Bricon (was: Snjezana Peco) > weird question/dialog with missing info when project from archetype/quickstart already exists > --------------------------------------------------------------------------------------------- > > Key: JBIDE-14797 > URL: https://issues.jboss.org/browse/JBIDE-14797 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Reporter: Max Rydahl Andersen > Assignee: Fred Bricon > Fix For: 4.1.1.Alpha1, 4.2.0.Alpha1 > > > Install a quickstart twice and you get this > http://screencast.com/t/Ptqsqevoe > Title: "Overwrite" > "There is the '<name>' project on the destination path: > Would you like to overwrite it ?" > Should this dialog actually have a Warning icon or similar and be worded a bit more assertive and not have blank fields - like: > Title: "Warning: Directory already exists" > "The project '<name>' already exist at '<actual path>'. > Do you wish to overwrite this directory ? > This cannot be undone" > This is assuming it is actually a project and not a directory. > btw. is the directory actually overwrittten or actually just copied on top ? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14797) weird question/dialog with missing info when project from archetype/quickstart already exists

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14797?page=com.atlassian.jira.plugi... ] Snjezana Peco updated JBIDE-14797: ---------------------------------- Fix Version/s: 4.1.1.Alpha1 4.2.0.Alpha1 (was: 4.1.1.Final) > weird question/dialog with missing info when project from archetype/quickstart already exists > --------------------------------------------------------------------------------------------- > > Key: JBIDE-14797 > URL: https://issues.jboss.org/browse/JBIDE-14797 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Reporter: Max Rydahl Andersen > Assignee: Snjezana Peco > Fix For: 4.1.1.Alpha1, 4.2.0.Alpha1 > > > Install a quickstart twice and you get this > http://screencast.com/t/Ptqsqevoe > Title: "Overwrite" > "There is the '<name>' project on the destination path: > Would you like to overwrite it ?" > Should this dialog actually have a Warning icon or similar and be worded a bit more assertive and not have blank fields - like: > Title: "Warning: Directory already exists" > "The project '<name>' already exist at '<actual path>'. > Do you wish to overwrite this directory ? > This cannot be undone" > This is assuming it is actually a project and not a directory. > btw. is the directory actually overwrittten or actually just copied on top ? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15456) For JBIDE 4.1.1.Alpha1: Code Freeze + Branch [LiveReload]

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-15456: ---------------------------------- Summary: For JBIDE 4.1.1.Alpha1: Code Freeze + Branch [LiveReload] Key: JBIDE-15456 URL: https://issues.jboss.org/browse/JBIDE-15456 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: livereload Reporter: Nick Boldt Priority: Blocker For JBIDE 4.1.1.Alpha1: Please perform the following tasks: 0. If nothing has changed in your component since the least GA release on this branch, *Reject this JIRA*. Otherwise: 1. Update your root pom to use parent pom version 4.1.1.Alpha1-SNAPSHOT; 2. Ensure you've built & run your plugin tests using the latest target platform version 4.31.0.Alpha1; 3. Branch from your existing jbosstools-4.1.x branch into a new jbosstools-4.1.1.Alpha1x branch; 4. Close (not resolve) this JIRA when done. [LiveReload] [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for LiveReload task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15452) For JBIDE 4.1.1.Alpha1: Code Freeze + Branch [Arquillian]

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-15452: ---------------------------------- Summary: For JBIDE 4.1.1.Alpha1: Code Freeze + Branch [Arquillian] Key: JBIDE-15452 URL: https://issues.jboss.org/browse/JBIDE-15452 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: testing-tools Reporter: Nick Boldt Priority: Blocker For JBIDE 4.1.1.Alpha1: Please perform the following tasks: 0. If nothing has changed in your component since the least GA release on this branch, *Reject this JIRA*. Otherwise: 1. Update your root pom to use parent pom version 4.1.1.Alpha1-SNAPSHOT; 2. Ensure you've built & run your plugin tests using the latest target platform version 4.31.0.Alpha1; 3. Branch from your existing jbosstools-4.1.x branch into a new jbosstools-4.1.1.Alpha1x branch; 4. Close (not resolve) this JIRA when done. [Arquillian] [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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15453) For JBIDE 4.1.1.Alpha1: Code Freeze + Branch [Central]

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-15453: ---------------------------------- Summary: For JBIDE 4.1.1.Alpha1: Code Freeze + Branch [Central] Key: JBIDE-15453 URL: https://issues.jboss.org/browse/JBIDE-15453 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: central, maven, project-examples Reporter: Nick Boldt Priority: Blocker For JBIDE 4.1.1.Alpha1: Please perform the following tasks: 0. If nothing has changed in your component since the least GA release on this branch, *Reject this JIRA*. Otherwise: 1. Update your root pom to use parent pom version 4.1.1.Alpha1-SNAPSHOT; 2. Ensure you've built & run your plugin tests using the latest target platform version 4.31.0.Alpha1; 3. Branch from your existing jbosstools-4.1.x branch into a new jbosstools-4.1.1.Alpha1x branch; 4. Close (not resolve) this JIRA when done. [Central] [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Central task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15454) For JBIDE 4.1.1.Alpha1: Code Freeze + Branch [Portlet]

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-15454: ---------------------------------- Summary: For JBIDE 4.1.1.Alpha1: Code Freeze + Branch [Portlet] Key: JBIDE-15454 URL: https://issues.jboss.org/browse/JBIDE-15454 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: portal-gatein Reporter: Nick Boldt Priority: Blocker For JBIDE 4.1.1.Alpha1: Please perform the following tasks: 0. If nothing has changed in your component since the least GA release on this branch, *Reject this JIRA*. Otherwise: 1. Update your root pom to use parent pom version 4.1.1.Alpha1-SNAPSHOT; 2. Ensure you've built & run your plugin tests using the latest target platform version 4.31.0.Alpha1; 3. Branch from your existing jbosstools-4.1.x branch into a new jbosstools-4.1.1.Alpha1x branch; 4. Close (not resolve) this JIRA when done. [Portlet] [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Portlet task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15455) For JBIDE 4.1.1.Alpha1: Code Freeze + Branch [Freemarker]

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-15455: ---------------------------------- Summary: For JBIDE 4.1.1.Alpha1: Code Freeze + Branch [Freemarker] Key: JBIDE-15455 URL: https://issues.jboss.org/browse/JBIDE-15455 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: freemarker Reporter: Nick Boldt Priority: Blocker For JBIDE 4.1.1.Alpha1: Please perform the following tasks: 0. If nothing has changed in your component since the least GA release on this branch, *Reject this JIRA*. Otherwise: 1. Update your root pom to use parent pom version 4.1.1.Alpha1-SNAPSHOT; 2. Ensure you've built & run your plugin tests using the latest target platform version 4.31.0.Alpha1; 3. Branch from your existing jbosstools-4.1.x branch into a new jbosstools-4.1.1.Alpha1x branch; 4. Close (not resolve) this JIRA when done. [Freemarker] [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Freemarker task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 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 September 2013