[JBoss JIRA] (JBIDE-17498) Can't run default hybrid project on device
by Vlado Pakan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17498?page=com.atlassian.jira.plugi... ]
Vlado Pakan closed JBIDE-17498.
-------------------------------
> Can't run default hybrid project on device
> ------------------------------------------
>
> Key: JBIDE-17498
> URL: https://issues.jboss.org/browse/JBIDE-17498
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: aerogear-hybrid
> Affects Versions: 4.2.0.Beta1
> Environment: windows
> Reporter: Ilya Buziuk
> Assignee: Gorkem Ercan
> Fix For: 4.2.0.CR1
>
> Attachments: BUILD SUCCESSFUL.png, Launching.png
>
>
> After choosing *Run As.. -> Run on Android Device* getting exception:
> {code}
> !ENTRY org.eclipse.ant.launching 4 0 2014-06-02 13:03:42.618
> !MESSAGE Ant Build Failed
> !STACK 1
> org.eclipse.core.runtime.CoreException: E:\AllEclipses\Installations\ADT\adt-bundle-windows-x86-20140321\sdk\tools\ant\build.xml:397: Problem: failed to create task or type checkenv
> Cause: The name is undefined.
> Action: Check the spelling.
> Action: Check that any custom tasks/types have been declared.
> Action: Check that any <presetdef>/<macrodef> declarations have taken place.
> at org.eclipse.ant.core.AntRunner.handleInvocationTargetException(AntRunner.java:448)
> at org.eclipse.ant.core.AntRunner.run(AntRunner.java:380)
> at org.eclipse.ant.internal.launching.launchConfigurations.AntLaunchDelegate.runInSameVM(AntLaunchDelegate.java:265)
> at org.eclipse.ant.internal.launching.launchConfigurations.AntLaunchDelegate.launch(AntLaunchDelegate.java:224)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:884)
> at org.jboss.tools.aerogear.hybrid.android.core.adt.BuildDelegate.doBuildProject(BuildDelegate.java:97)
> at org.jboss.tools.aerogear.hybrid.android.core.adt.BuildDelegate.buildProject(BuildDelegate.java:58)
> at org.jboss.tools.aerogear.hybrid.android.core.adt.BuildDelegate.buildNow(BuildDelegate.java:53)
> at org.jboss.tools.aerogear.hybrid.android.core.adt.AndroidLaunchDelegate.buildForLaunch(AndroidLaunchDelegate.java:77)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:852)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739)
> at org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:1039)
> at org.eclipse.debug.internal.ui.DebugUIPlugin$8.run(DebugUIPlugin.java:1256)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
> Caused by: E:\AllEclipses\Installations\ADT\adt-bundle-windows-x86-20140321\sdk\tools\ant\build.xml:397: Problem: failed to create task or type checkenv
> Cause: The name is undefined.
> Action: Check the spelling.
> Action: Check that any custom tasks/types have been declared.
> Action: Check that any <presetdef>/<macrodef> declarations have taken place.
> at org.apache.tools.ant.UnknownElement.getNotFoundException(UnknownElement.java:499)
> at org.apache.tools.ant.UnknownElement.makeObject(UnknownElement.java:431)
> at org.apache.tools.ant.UnknownElement.maybeConfigure(UnknownElement.java:163)
> at org.apache.tools.ant.Task.perform(Task.java:347)
> at org.apache.tools.ant.Target.execute(Target.java:435)
> at org.apache.tools.ant.Target.performTasks(Target.java:456)
> at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1393)
> at org.apache.tools.ant.Project.executeTarget(Project.java:1364)
> at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41)
> at org.eclipse.ant.internal.core.ant.EclipseDefaultExecutor.executeTargets(EclipseDefaultExecutor.java:36)
> at org.apache.tools.ant.Project.executeTargets(Project.java:1248)
> at org.eclipse.ant.internal.core.ant.InternalAntRunner.run(InternalAntRunner.java:703)
> at org.eclipse.ant.internal.core.ant.InternalAntRunner.run(InternalAntRunner.java:525)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:483)
> at org.eclipse.ant.core.AntRunner.run(AntRunner.java:371)
> ... 12 more
> !SUBENTRY 1 org.eclipse.ant.core 4 1 2014-06-02 13:03:42.618
> !MESSAGE E:\AllEclipses\Installations\ADT\adt-bundle-windows-x86-20140321\sdk\tools\ant\build.xml:397: Problem: failed to create task or type checkenv
> Cause: The name is undefined.
> Action: Check the spelling.
> Action: Check that any custom tasks/types have been declared.
> Action: Check that any <presetdef>/<macrodef> declarations have taken place.
> !STACK 0
> E:\AllEclipses\Installations\ADT\adt-bundle-windows-x86-20140321\sdk\tools\ant\build.xml:397: Problem: failed to create task or type checkenv
> Cause: The name is undefined.
> Action: Check the spelling.
> Action: Check that any custom tasks/types have been declared.
> Action: Check that any <presetdef>/<macrodef> declarations have taken place.
> at org.apache.tools.ant.UnknownElement.getNotFoundException(UnknownElement.java:499)
> at org.apache.tools.ant.UnknownElement.makeObject(UnknownElement.java:431)
> at org.apache.tools.ant.UnknownElement.maybeConfigure(UnknownElement.java:163)
> at org.apache.tools.ant.Task.perform(Task.java:347)
> at org.apache.tools.ant.Target.execute(Target.java:435)
> at org.apache.tools.ant.Target.performTasks(Target.java:456)
> at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1393)
> at org.apache.tools.ant.Project.executeTarget(Project.java:1364)
> at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41)
> at org.eclipse.ant.internal.core.ant.EclipseDefaultExecutor.executeTargets(EclipseDefaultExecutor.java:36)
> at org.apache.tools.ant.Project.executeTargets(Project.java:1248)
> at org.eclipse.ant.internal.core.ant.InternalAntRunner.run(InternalAntRunner.java:703)
> at org.eclipse.ant.internal.core.ant.InternalAntRunner.run(InternalAntRunner.java:525)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:483)
> at org.eclipse.ant.core.AntRunner.run(AntRunner.java:371)
> at org.eclipse.ant.internal.launching.launchConfigurations.AntLaunchDelegate.runInSameVM(AntLaunchDelegate.java:265)
> at org.eclipse.ant.internal.launching.launchConfigurations.AntLaunchDelegate.launch(AntLaunchDelegate.java:224)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:884)
> at org.jboss.tools.aerogear.hybrid.android.core.adt.BuildDelegate.doBuildProject(BuildDelegate.java:97)
> at org.jboss.tools.aerogear.hybrid.android.core.adt.BuildDelegate.buildProject(BuildDelegate.java:58)
> at org.jboss.tools.aerogear.hybrid.android.core.adt.BuildDelegate.buildNow(BuildDelegate.java:53)
> at org.jboss.tools.aerogear.hybrid.android.core.adt.AndroidLaunchDelegate.buildForLaunch(AndroidLaunchDelegate.java:77)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:852)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739)
> at org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:1039)
> at org.eclipse.debug.internal.ui.DebugUIPlugin$8.run(DebugUIPlugin.java:1256)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
> !ENTRY org.jboss.tools.aerogear.hybrid.android.core 4 0 2014-06-02 13:03:42.620
> !MESSAGE Build failed... Build artifact does not exist
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBIDE-17854) ArrayStoreException while opening database in Hibernate Console
by Jiri Peterka (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17854?page=com.atlassian.jira.plugi... ]
Jiri Peterka edited comment on JBIDE-17854 at 9/1/14 6:05 AM:
--------------------------------------------------------------
Same scenario another error so it's not fully fixed. It complains that hibernate.cfg.xml is not found, but configuration is configured as [ JPA Project Configured Connection ] and should use connection from Project JPA Settings and not to look for hibernate.cfg.xml
{code}
org.hibernate.HibernateException: /hibernate.cfg.xml not found
at org.hibernate.internal.util.ConfigHelper.getResourceAsStream(ConfigHelper.java:173)
at org.hibernate.cfg.Configuration.getConfigurationInputStream(Configuration.java:1940)
at org.hibernate.cfg.Configuration.configure(Configuration.java:1921)
at org.hibernate.cfg.Configuration.configure(Configuration.java:1901)
at org.jboss.tools.hibernate.proxy.ConfigurationProxy.buildServiceRegistry(ConfigurationProxy.java:253)
at org.jboss.tools.hibernate.proxy.ConfigurationProxy.buildSettings(ConfigurationProxy.java:125)
at org.hibernate.console.ConsoleConfiguration$6.execute(ConsoleConfiguration.java:438)
at org.hibernate.console.execution.DefaultExecutionContext.execute(DefaultExecutionContext.java:63)
at org.hibernate.console.ConsoleConfiguration.execute(ConsoleConfiguration.java:108)
at org.hibernate.console.ConsoleConfiguration.getSettings(ConsoleConfiguration.java:436)
at org.hibernate.eclipse.console.workbench.LazyDatabaseSchemaWorkbenchAdapter$2.execute(LazyDatabaseSchemaWorkbenchAdapter.java:129)
at org.hibernate.console.execution.DefaultExecutionContext.execute(DefaultExecutionContext.java:63)
at org.hibernate.console.ConsoleConfiguration.execute(ConsoleConfiguration.java:108)
at org.hibernate.eclipse.console.workbench.LazyDatabaseSchemaWorkbenchAdapter.readDatabaseSchema(LazyDatabaseSchemaWorkbenchAdapter.java:125)
at org.hibernate.eclipse.console.workbench.LazyDatabaseSchemaWorkbenchAdapter.getChildren(LazyDatabaseSchemaWorkbenchAdapter.java:65)
at org.hibernate.eclipse.console.workbench.BasicWorkbenchAdapter.fetchDeferredChildren(BasicWorkbenchAdapter.java:104)
at org.eclipse.ui.progress.DeferredTreeContentManager$1.run(DeferredTreeContentManager.java:238)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
{code}
was (Author: jpeterka):
Same scenario another error so it's not fully fixed. It complains that hibernate.cfg.xml is not found, but configuration is configured as [ JPA Project Configured Connection ] and should use connection from Project JPA Settings and not look for hibernate.cfg.xml and not look for hibernate.cfg.xml
{code}
org.hibernate.HibernateException: /hibernate.cfg.xml not found
at org.hibernate.internal.util.ConfigHelper.getResourceAsStream(ConfigHelper.java:173)
at org.hibernate.cfg.Configuration.getConfigurationInputStream(Configuration.java:1940)
at org.hibernate.cfg.Configuration.configure(Configuration.java:1921)
at org.hibernate.cfg.Configuration.configure(Configuration.java:1901)
at org.jboss.tools.hibernate.proxy.ConfigurationProxy.buildServiceRegistry(ConfigurationProxy.java:253)
at org.jboss.tools.hibernate.proxy.ConfigurationProxy.buildSettings(ConfigurationProxy.java:125)
at org.hibernate.console.ConsoleConfiguration$6.execute(ConsoleConfiguration.java:438)
at org.hibernate.console.execution.DefaultExecutionContext.execute(DefaultExecutionContext.java:63)
at org.hibernate.console.ConsoleConfiguration.execute(ConsoleConfiguration.java:108)
at org.hibernate.console.ConsoleConfiguration.getSettings(ConsoleConfiguration.java:436)
at org.hibernate.eclipse.console.workbench.LazyDatabaseSchemaWorkbenchAdapter$2.execute(LazyDatabaseSchemaWorkbenchAdapter.java:129)
at org.hibernate.console.execution.DefaultExecutionContext.execute(DefaultExecutionContext.java:63)
at org.hibernate.console.ConsoleConfiguration.execute(ConsoleConfiguration.java:108)
at org.hibernate.eclipse.console.workbench.LazyDatabaseSchemaWorkbenchAdapter.readDatabaseSchema(LazyDatabaseSchemaWorkbenchAdapter.java:125)
at org.hibernate.eclipse.console.workbench.LazyDatabaseSchemaWorkbenchAdapter.getChildren(LazyDatabaseSchemaWorkbenchAdapter.java:65)
at org.hibernate.eclipse.console.workbench.BasicWorkbenchAdapter.fetchDeferredChildren(BasicWorkbenchAdapter.java:104)
at org.eclipse.ui.progress.DeferredTreeContentManager$1.run(DeferredTreeContentManager.java:238)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
{code}
> ArrayStoreException while opening database in Hibernate Console
> ---------------------------------------------------------------
>
> Key: JBIDE-17854
> URL: https://issues.jboss.org/browse/JBIDE-17854
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: hibernate
> Affects Versions: 4.2.0.Beta3
> Environment: JBDS 8.0.0.
> Reporter: Jiri Peterka
> Assignee: Koen Aers
> Priority: Blocker
> Labels: respin-a
> Fix For: 4.2.0.CR1
>
>
> An internal error has occurred.
> java.lang.ArrayStoreException
> Used pom file
> {code}
> <project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
> <modelVersion>4.0.0</modelVersion>
> <groupId>testjpa</groupId>
> <artifactId>testjpa</artifactId>
> <version>0.0.1-SNAPSHOT</version>
> <dependencies>
> <dependency>
> <groupId>org.hibernate</groupId>
> <artifactId>hibernate-core</artifactId>
> <version>4.0.0.Final</version>
> </dependency>
> <dependency>
> <groupId>org.hibernate</groupId>
> <artifactId>hibernate-entitymanager</artifactId>
> <version>4.0.0.Final</version>
> </dependency>
> <dependency>
> <groupId>org.hibernate.javax.persistence</groupId>
> <artifactId>hibernate-jpa-2.0-api</artifactId>
> <version>1.0.0.Final</version>
> </dependency>
> <dependency>
> <groupId>com.h2database</groupId>
> <artifactId>h2</artifactId>
> <version>1.3.161</version>
> </dependency>
> </dependencies>
> <build>
> <sourceDirectory>src</sourceDirectory>
> <resources>
> <resource>
> <directory>src</directory>
> <excludes>
> <exclude>**/*.java</exclude>
> </excludes>
> </resource>
> </resources>
> <plugins>
> <plugin>
> <artifactId>maven-compiler-plugin</artifactId>
> <version>3.1</version>
> <configuration>
> <source>1.8</source>
> <target>1.8</target>
> </configuration>
> </plugin>
> </plugins>
> </build>
> </project>
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBDS-3130) [RFE] Add tooling to manage openshift databases
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBDS-3130?page=com.atlassian.jira.plugin.... ]
Andre Dietisheim updated JBDS-3130:
-----------------------------------
Fix Version/s: 8.0.x
> [RFE] Add tooling to manage openshift databases
> -----------------------------------------------
>
> Key: JBDS-3130
> URL: https://issues.jboss.org/browse/JBDS-3130
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Components: openshift
> Affects Versions: 7.1.1.GA
> Environment: All
> Reporter: Tim Williams
> Assignee: Max Rydahl Andersen
> Priority: Minor
> Fix For: 8.0.x
>
>
> In OpenShift, a scaled application will have numerous 'gears', each running a copy of the developer's code. If the developer is running a database, there will be only one gear containing this database.
> To export/import/backup/restore the database, a user must ssh to the specific gear that holds the database cartridge. The only current way to do this in JBDS is to print all the environment variables and look for the following:
> $OPENSHIFT_MYSQL_DB_GEAR_UUID
> $OPENSHIFT_MYSQL_DB_GEAR_DNS
> You can then use these values in a terminal to ssh to the database gear:
> $ ssh $OPENSHIFT_MYSQL_DB_GEAR_UUID@$OPENSHIFT_MYSQL_DB_GEAR_DNS
> It would be helpful to have some kind of tooling to either ssh into this gear directly through JBDS, or at least print the ssh command (above) using the environment variables from the gear.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBIDE-17854) ArrayStoreException while opening database in Hibernate Console
by Jiri Peterka (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17854?page=com.atlassian.jira.plugi... ]
Jiri Peterka updated JBIDE-17854:
---------------------------------
Labels: respin-a (was: )
> ArrayStoreException while opening database in Hibernate Console
> ---------------------------------------------------------------
>
> Key: JBIDE-17854
> URL: https://issues.jboss.org/browse/JBIDE-17854
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: hibernate
> Affects Versions: 4.2.0.Beta3
> Environment: JBDS 8.0.0.
> Reporter: Jiri Peterka
> Assignee: Koen Aers
> Priority: Blocker
> Labels: respin-a
> Fix For: 4.2.0.CR1
>
>
> An internal error has occurred.
> java.lang.ArrayStoreException
> Used pom file
> {code}
> <project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
> <modelVersion>4.0.0</modelVersion>
> <groupId>testjpa</groupId>
> <artifactId>testjpa</artifactId>
> <version>0.0.1-SNAPSHOT</version>
> <dependencies>
> <dependency>
> <groupId>org.hibernate</groupId>
> <artifactId>hibernate-core</artifactId>
> <version>4.0.0.Final</version>
> </dependency>
> <dependency>
> <groupId>org.hibernate</groupId>
> <artifactId>hibernate-entitymanager</artifactId>
> <version>4.0.0.Final</version>
> </dependency>
> <dependency>
> <groupId>org.hibernate.javax.persistence</groupId>
> <artifactId>hibernate-jpa-2.0-api</artifactId>
> <version>1.0.0.Final</version>
> </dependency>
> <dependency>
> <groupId>com.h2database</groupId>
> <artifactId>h2</artifactId>
> <version>1.3.161</version>
> </dependency>
> </dependencies>
> <build>
> <sourceDirectory>src</sourceDirectory>
> <resources>
> <resource>
> <directory>src</directory>
> <excludes>
> <exclude>**/*.java</exclude>
> </excludes>
> </resource>
> </resources>
> <plugins>
> <plugin>
> <artifactId>maven-compiler-plugin</artifactId>
> <version>3.1</version>
> <configuration>
> <source>1.8</source>
> <target>1.8</target>
> </configuration>
> </plugin>
> </plugins>
> </build>
> </project>
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBIDE-17841) Unable to import cordova Hello project created by cordova CLI
by Vlado Pakan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17841?page=com.atlassian.jira.plugi... ]
Vlado Pakan closed JBIDE-17841.
-------------------------------
Verified with JBDS CR1-v20140831-0335-B201
> Unable to import cordova Hello project created by cordova CLI
> -------------------------------------------------------------
>
> Key: JBIDE-17841
> URL: https://issues.jboss.org/browse/JBIDE-17841
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: aerogear-hybrid
> Affects Versions: 4.2.0.CR1
> Environment: JBDS 8.0.0.Beta3-v20140706-0939-B172
> Linux
> Cordova v. 3.5.0-0.2.6
> Reporter: Vlado Pakan
> Assignee: Gorkem Ercan
> Priority: Critical
> Fix For: 4.2.0.CR1
>
>
> 1. Create default cordova app via command
> {noformat}
> cordova create hello com.example.hello HelloWorld
> {noformat}
> 2. Open Import > Mobile > Import Cordova Project
> 3. Select Hello directory of created project
> ASSERT: Project is listed in Project list
> ERROR: Unable to check project to be imported and therefore Finish buttons is disabled and project can't be imported
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBIDE-18100) Application wizard, server adapter: New->File->OpenShift App is using "existing application" from selected server adapter. Should not
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18100?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-18100:
-------------------------------------
Summary: Application wizard, server adapter: New->File->OpenShift App is using "existing application" from selected server adapter. Should not (was: Application wizard, server adapter: Wizard choose existing application from server adapter selection)
> Application wizard, server adapter: New->File->OpenShift App is using "existing application" from selected server adapter. Should not
> -------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-18100
> URL: https://issues.jboss.org/browse/JBIDE-18100
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.2.0.CR1
> Reporter: Marián Labuda
> Assignee: Andre Dietisheim
> Priority: Minor
> Labels: application_wizard
> Fix For: 4.2.0.CR1
>
> Attachments: out-1.ogv, selected-server-adapter.png, used-existing-project.png
>
>
> This is happening only in wizard opened via shell menu (File - New - OpenShift Application). Opening New application wizard via Central and OpenShift explorer works fine (probably because of view focus).
> Issue is preselected existing application in New application wizard although I had no intentions to do it. If I have selected a server adapter and then I opened New application wizard via shell menu and go via wizard to the third wizard page, where the field for using an existing project is placed, there is used project from existing selected server adapter. For better and more obvious explanation see attached video: [^out-1.ogv]
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBIDE-12851) Server Adapter wizard: link should point to creation wizard in case user don't have app/domain
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-12851?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-12851:
-------------------------------------
Affects: Documentation (Ref Guide, User Guide, etc.),Interactive Demo/Tutorial,User Experience
> Server Adapter wizard: link should point to creation wizard in case user don't have app/domain
> ----------------------------------------------------------------------------------------------
>
> Key: JBIDE-12851
> URL: https://issues.jboss.org/browse/JBIDE-12851
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift, server
> Affects Versions: 4.0.0.Beta1
> Reporter: Stefan Bunciak
> Assignee: Andre Dietisheim
> Priority: Minor
> Labels: server_adapter_wizard
> Fix For: 4.2.0.CR1
>
> Attachments: CreateNewApplicationLink.png, newappserver.png
>
>
> In case the user doesn't have an application on openshift (or domain) link should point to Create OpenShift Application wizard not to the Import OpenShift Application wizard. Also the link could be named more appropriately in this case - user will be creating application, not importing.
> !newappserver.png|thumbnail!
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBIDE-16987) Unable to download Mobile Engine v. 3.4.1 for Android
by Vlado Pakan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16987?page=com.atlassian.jira.plugi... ]
Vlado Pakan closed JBIDE-16987.
-------------------------------
Verified with JBDS CR1-v20140831-0335-B201
> Unable to download Mobile Engine v. 3.4.1 for Android
> -----------------------------------------------------
>
> Key: JBIDE-16987
> URL: https://issues.jboss.org/browse/JBIDE-16987
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: aerogear-hybrid
> Affects Versions: 4.2.0.Beta1
> Environment: JBDS 8.0.0.Beta1-v20140402-0037-B82
> Reporter: Vlado Pakan
> Assignee: Gorkem Ercan
> Priority: Critical
> Fix For: 4.2.0.CR1
>
>
> 1. Open Window > Preferences > Hybrid Mobile > Engines
> 2. Click Download...
> 3. Select 3.4.1 version and click OK
> ERROR: No Engine is dowloaded. Dialog stayed opened. No error in displayed to error log
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBIDE-17881) Publishing jobs are hanging in Progress view and in bottom right corner.
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17881?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-17881:
-------------------------------------
Labels: server_adapter (was: )
> Publishing jobs are hanging in Progress view and in bottom right corner.
> ------------------------------------------------------------------------
>
> Key: JBIDE-17881
> URL: https://issues.jboss.org/browse/JBIDE-17881
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.2.0.Beta3
> Reporter: Marián Labuda
> Assignee: Andre Dietisheim
> Priority: Critical
> Labels: server_adapter
> Fix For: 4.2.0.CR1
>
> Attachments: finished_job.png, hanging_finished_job.png
>
>
> Publishing jobs are shown in Progress view. In previous versions they were removed from this view after finishing the job. Now they are still hanging there with status "Finished" and after removal and reopen Progress view they are still here. Instead of reopen view also Remove all Finished Jobs (double gray crosses in view) works fine too.
> !finished_job.png!
> Running job is also shown in bottom right corner. After finishing it is still hanging there.
> !hanging_finished_job.png!
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months