April 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-13646) Support for Apache Cordova config.xml

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13646?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-13646: ---------------------------------------- Fix Version/s: 4.1.0.Beta1 Set version to 4.1.0.Beta1 for all non-fix-version issues since more true than "no fix version". Adjust the fix version to match actual aerogear plan. > Support for Apache Cordova config.xml > ------------------------------------- > > Key: JBIDE-13646 > URL: https://issues.jboss.org/browse/JBIDE-13646 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: aerogear-hybrid > Reporter: Gorkem Ercan > Assignee: Gorkem Ercan > Fix For: 4.1.0.Beta1 > > Original Estimate: 0 minutes > Remaining Estimate: 0 minutes > > Tools needs to generate a model out of config.xml to use with various tasks. Also a multipage editor is needed to make it easier for the develoers to modify the config.xml. The model should also provide listeners for changes -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13805) Validation for config.xml editor

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13805?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-13805: ---------------------------------------- Fix Version/s: 4.1.0.Beta1 Set version to 4.1.0.Beta1 for all non-fix-version issues since more true than "no fix version". Adjust the fix version to match actual aerogear plan. > Validation for config.xml editor > -------------------------------- > > Key: JBIDE-13805 > URL: https://issues.jboss.org/browse/JBIDE-13805 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: aerogear-hybrid > Reporter: Gorkem Ercan > Assignee: Gorkem Ercan > Fix For: 4.1.0.Beta1 > > > config.xml editor needs validators for data entry. Editor itself is using jface databinding therefore jface validators should be able to help. Valid values depends on whether Phonegap or pure cordova values are supported. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13648) Support for Android

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13648?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-13648: ---------------------------------------- Fix Version/s: 4.1.0.Beta1 Set version to 4.1.0.Beta1 for all non-fix-version issues since more true than "no fix version". Adjust the fix version to match actual aerogear plan. > Support for Android > ------------------- > > Key: JBIDE-13648 > URL: https://issues.jboss.org/browse/JBIDE-13648 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: aerogear-hybrid > Reporter: Gorkem Ercan > Assignee: Gorkem Ercan > Fix For: 4.1.0.Beta1 > > > Support the building, native project generation and launching on Emulator/device of Cordova projects on Android devices. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13645) Run on iOS simulator

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13645?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-13645: ---------------------------------------- Fix Version/s: 4.1.0.Beta1 Set version to 4.1.0.Beta1 for all non-fix-version issues since more true than "no fix version". Adjust the fix version to match actual aerogear plan. > Run on iOS simulator > -------------------- > > Key: JBIDE-13645 > URL: https://issues.jboss.org/browse/JBIDE-13645 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: aerogear-hybrid > Reporter: Gorkem Ercan > Assignee: Gorkem Ercan > Fix For: 4.1.0.Beta1 > > Original Estimate: 0 minutes > Remaining Estimate: 0 minutes > > This is needed to provide "Run on iOS Simulator" functionality. Ideally the solution should be able to change the different types of iOS devices that are started through a Launch Configuration dialog. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13776) Implement proper logging for BrowserSim

by Yahor Radtsevich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13776?page=com.atlassian.jira.plugi... ] Yahor Radtsevich commented on JBIDE-13776: ------------------------------------------ >From [IRC|http://transcripts.jboss.org/meeting/irc.freenode.org/jbosstools-tria...]: {quote} [~yradtsevich]: I would show BrowserSim errors in Eclipse. But this requires a way to serialize BrowserSim exceprions to eclipse via System.out and showing them via Eclipse UI. I consider this as a fearture, but we have no time to implement it before beta1. So for 4.1.x, because of the feature freeze? [~maxandersen]: okey - not sure if that is worth serializing back to eclipse, what about the running standalone case? [~yradtsevich]: I assume, in the standalone case it will still print exceptions to the System.out. Do you think this is wrong? [~maxandersen]: As long as it is not just raw exceptions but also give some context i'm fine with that. but could maybe at least using Java util logging and then later move to something more unified (i.e. jboss logging). {quote} > Implement proper logging for BrowserSim > --------------------------------------- > > Key: JBIDE-13776 > URL: https://issues.jboss.org/browse/JBIDE-13776 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: browsersim > Affects Versions: 4.1.0.Alpha1 > Reporter: Denis Golovin > Assignee: Yahor Radtsevich > > Current implementation is just printing stack trace to standard output. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14341) Add support for creating OpenShift Cartridges using JBoss Tools/Eclipse

by Joe Fernandes (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14341?page=com.atlassian.jira.plugi... ] Joe Fernandes commented on JBIDE-14341: --------------------------------------- A basic "cartridge" project would be great as a starting point. Using Forge isn't a requirement for the OpenShift team. I am not very familiar with Forge and what it adds here, so if there is some benefit over what you could just add through JBoss Tools let us know. In terms of what the plugin would do, creating the cartridge project layout and making it easy for cartridge developers to see what's editable would be great. We probably need to meet with folks from the OpenShift side who have more experience with v2 cartridge creation - Bill DeCoste, Jon Honce, etc. - to get more specific requirements. I will start a thread on libra-devel. The output of this is an actual OpenShift Cartridge. To test it out, users should be able to run the cartridge in user space on OpenShift Online from any machine or in their own private OpenShift Origin PaaS platform instance which yes does only run on RHEL. > Add support for creating OpenShift Cartridges using JBoss Tools/Eclipse > ----------------------------------------------------------------------- > > Key: JBIDE-14341 > URL: https://issues.jboss.org/browse/JBIDE-14341 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Reporter: Joe Fernandes > Priority: Optional > > OpenShift is introducing a new v2 cartridge format to make it easier for users to create cartridges to add support for different languages, frameworks or runtimes to the OpenShift PaaS. > This enhancement request is to create an Eclipse/JBoss Tools plugin to enable users to create these cartridges directly from their IDE. This plugin would have knowledge of the new v2 cartridge format and make it easier for users to create cartridges that they could use in OpenShift Origin community project, OpenShift Online Public PaaS or OpenShift Enterprise Private PaaS offerings. > Some key information on the new OpenShift v2 cartridge format: > -Currently planned for June OpenShift Online commercial launch and OpenShift Enterprise 1.2 release (~June). All current cartridges are being migrated to the new v2 cartridge format. > -One of the core changes is allowing cartridges to run in userspace, so you don't need to be an admin to install them. That means that you can write and host a cartridge on GitHub/S3, etc and users can consume it from that URL. That is really the core feature of being able to start a cartridge ecosystem. > -Modelled the v2 cartridge format around the DIY cartridges which have been pretty popular. Main goal there was to try and simplify, cleanup and better document the process. H > -Here are some of the docs: > Technical docs: > https://github.com/openshift/origin-server/blob/master/node/README.writin... > https://github.com/openshift/origin-server/blob/master/node/README.node_m... > https://github.com/openshift/origin-server/blob/master/node/README.writin... > Getting Started: > https://www.openshift.com/blogs/new-openshift-cartridge-format-part-1 > https://www.openshift.com/blogs/new-openshift-cartridge-format-part-2 > If you are interested in tinkering, you can stand up an OpenShift Origin instance for local development (https://www.openshift.com/wiki/installing-openshift-origin-using-vagrant-...) or we will happily give anyone access to our Amazon development infrastructure as well - just let us know. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14341) Add support for creating OpenShift Cartridges using JBoss Tools/Eclipse

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14341?page=com.atlassian.jira.plugi... ] George Gastaldi commented on JBIDE-14341: ----------------------------------------- I don't understand why developing using Forge seems overkill. Besides rendering as an Eclipse Wizard, Forge 2 allows you to run into other IDEs as well (Support for IntelliJ IDEA coming soon). Forge 1 (which is already part of JBT) makes it easy to create a new-project using the shell prompt and manipulation of the cartridge configuration is as easy as creating a new method with an @Option. Since Forge 2 is in Alpha and Experimental state, developing a Forge 1 plugin seems the most stable choice so far, at least until we release Forge 2 Final (which should happen in November AFAIK). > Add support for creating OpenShift Cartridges using JBoss Tools/Eclipse > ----------------------------------------------------------------------- > > Key: JBIDE-14341 > URL: https://issues.jboss.org/browse/JBIDE-14341 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Reporter: Joe Fernandes > Priority: Optional > > OpenShift is introducing a new v2 cartridge format to make it easier for users to create cartridges to add support for different languages, frameworks or runtimes to the OpenShift PaaS. > This enhancement request is to create an Eclipse/JBoss Tools plugin to enable users to create these cartridges directly from their IDE. This plugin would have knowledge of the new v2 cartridge format and make it easier for users to create cartridges that they could use in OpenShift Origin community project, OpenShift Online Public PaaS or OpenShift Enterprise Private PaaS offerings. > Some key information on the new OpenShift v2 cartridge format: > -Currently planned for June OpenShift Online commercial launch and OpenShift Enterprise 1.2 release (~June). All current cartridges are being migrated to the new v2 cartridge format. > -One of the core changes is allowing cartridges to run in userspace, so you don't need to be an admin to install them. That means that you can write and host a cartridge on GitHub/S3, etc and users can consume it from that URL. That is really the core feature of being able to start a cartridge ecosystem. > -Modelled the v2 cartridge format around the DIY cartridges which have been pretty popular. Main goal there was to try and simplify, cleanup and better document the process. H > -Here are some of the docs: > Technical docs: > https://github.com/openshift/origin-server/blob/master/node/README.writin... > https://github.com/openshift/origin-server/blob/master/node/README.node_m... > https://github.com/openshift/origin-server/blob/master/node/README.writin... > Getting Started: > https://www.openshift.com/blogs/new-openshift-cartridge-format-part-1 > https://www.openshift.com/blogs/new-openshift-cartridge-format-part-2 > If you are interested in tinkering, you can stand up an OpenShift Origin instance for local development (https://www.openshift.com/wiki/installing-openshift-origin-using-vagrant-...) or we will happily give anyone access to our Amazon development infrastructure as well - just let us know. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14305) Error popup when runing schema ddl with Hibernate Configurations

by labdoui labdoui (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14305?page=com.atlassian.jira.plugi... ] labdoui labdoui commented on JBIDE-14305: ----------------------------------------- Using only hibernate 4.0.1 in (project and Hibernate configuration). To reproduce the probleme, juste explore the database from hibernate console or try to run schema ddl. Thx. > Error popup when runing schema ddl with Hibernate Configurations > ----------------------------------------------------------------- > > Key: JBIDE-14305 > URL: https://issues.jboss.org/browse/JBIDE-14305 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: hibernate > Affects Versions: 4.1.0.Final > Reporter: labdoui labdoui > Fix For: 4.1.0.Beta1 > > > Using Hibernate 4, and slf4j 1.7.2, I can't runing my ddl schema > to reproduce the problem just explore the database from hibernate console > java.lang.NoSuchMethodError: org.slf4j.spi.LocationAwareLogger.log(Lorg/slf4j/Marker;Ljava/lang/String;ILjava/lang/String;[Ljava/lang/Object;Ljava/lang/Throwable;)V > at org.apache.commons.logging.impl.SLF4JLocationAwareLog.debug(SLF4JLocationAwareLog.java:133) > at org.hibernate.cfg.reveng.dialect.JDBCMetaDataDialect.getTables(JDBCMetaDataDialect.java:26) > at org.hibernate.cfg.reveng.JDBCReader.processTables(JDBCReader.java:476) > at org.hibernate.cfg.reveng.JDBCReader.readDatabaseSchema(JDBCReader.java:74) > at org.hibernate.eclipse.console.workbench.LazyDatabaseSchemaWorkbenchAdapter$2.execute(LazyDatabaseSchemaWorkbenchAdapter.java:116) > at org.hibernate.console.execution.DefaultExecutionContext.execute(DefaultExecutionContext.java:63) > at org.hibernate.eclipse.console.workbench.LazyDatabaseSchemaWorkbenchAdapter.readDatabaseSchema(LazyDatabaseSchemaWorkbenchAdapter.java:107) > at org.hibernate.eclipse.console.workbench.LazyDatabaseSchemaWorkbenchAdapter.getChildren(LazyDatabaseSchemaWorkbenchAdapter.java:63) > at org.hibernate.eclipse.console.workbench.BasicWorkbenchAdapter.fetchDeferredChildren(BasicWorkbenchAdapter.java:106) > at org.eclipse.ui.progress.DeferredTreeContentManager$1.run(DeferredTreeContentManager.java:235) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14337) Portal Quickstarts are not displayed after changing target runtime to portal

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14337?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-14337: --------------------------------------------- EAP 6.1 does not support running old Portal examples thus I think this is expected. But new examples are not supposed to target/require portal so something must either be wrong in matching or the example. > Portal Quickstarts are not displayed after changing target runtime to portal > ---------------------------------------------------------------------------- > > Key: JBIDE-14337 > URL: https://issues.jboss.org/browse/JBIDE-14337 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: Portal/GateIn > Affects Versions: 4.1.0.Beta1 > Environment: gatein-master (3.6.0.Beta02-SNAPSHOT) - eap 6.1 bundle > Eclipse 4.3 M6 Kepler + JBT 4.1.0.Beta1 > Reporter: Filip Kiss > Labels: JPP61-Test-dev > Fix For: 4.1.0.Beta1 > > -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14337) Portal Quickstarts are not displayed after changing target runtime to portal

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14337?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-14337: ---------------------------------------- Fix Version/s: 4.1.0.Beta1 > Portal Quickstarts are not displayed after changing target runtime to portal > ---------------------------------------------------------------------------- > > Key: JBIDE-14337 > URL: https://issues.jboss.org/browse/JBIDE-14337 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: Portal/GateIn > Affects Versions: 4.1.0.Beta1 > Environment: gatein-master (3.6.0.Beta02-SNAPSHOT) - eap 6.1 bundle > Eclipse 4.3 M6 Kepler + JBT 4.1.0.Beta1 > Reporter: Filip Kiss > Labels: JPP61-Test-dev > Fix For: 4.1.0.Beta1 > > -- 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, 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 April 2013