[JBoss JIRA] (JBIDE-14544) Cannot run Cordova project on Android Emulator/Device
by Vlado Pakan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14544?page=com.atlassian.jira.plugi... ]
Vlado Pakan commented on JBIDE-14544:
-------------------------------------
Sorry I misunderstand your question. I put an exact copy of error message to Jira comment.
And I also have checked emulator serial number via adb devices commant and serial number is properly set.
> Cannot run Cordova project on Android Emulator/Device
> -----------------------------------------------------
>
> Key: JBIDE-14544
> URL: https://issues.jboss.org/browse/JBIDE-14544
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: aerogear-hybrid
> Affects Versions: 4.1.0.Beta1
> Environment: Fedora 17 32bit
> Android 4.1.2
> Reporter: Stefan Bunciak
> Assignee: Gorkem Ercan
> Labels: respin-a
> Fix For: 4.1.x, 4.2.x
>
> Attachments: runasandroidemulatorwin7_32.png, Screen Shot 2013-06-03 at 10.50.52 AM.png
>
> Original Estimate: 0 minutes
> Remaining Estimate: 0 minutes
>
> {code}
> java.io.IOException: No such file or directory
> at java.io.UnixFileSystem.createFileExclusively(Native Method)
> at java.io.File.createNewFile(File.java:883)
> at org.jboss.tools.aerogear.hybrid.core.util.FileUtils.fileCopy(FileUtils.java:105)
> at org.jboss.tools.aerogear.hybrid.android.core.adt.AndroidProjectGenerator.generateNativeFiles(AndroidProjectGenerator.java:99)
> at org.jboss.tools.aerogear.hybrid.core.platform.AbstractPlatformProjectGenerator.generateNow(AbstractPlatformProjectGenerator.java:68)
> at org.jboss.tools.aerogear.hybrid.android.core.adt.AndroidLaunchDelegate.buildForLaunch(AndroidLaunchDelegate.java:68)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:825)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:706)
> at org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:1018)
> at org.eclipse.debug.internal.ui.DebugUIPlugin$8.run(DebugUIPlugin.java:1222)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)
> {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, 5 months
[JBoss JIRA] (JBIDE-15766) openshift-java-client: don't refresh env variables on each addition/removal
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15766?page=com.atlassian.jira.plugi... ]
Denis Golovin updated JBIDE-15766:
----------------------------------
Summary: openshift-java-client: don't refresh env variables on each addition/removal (was: openshift-java-client: dont refresh env variables on each addition/removal)
> openshift-java-client: don't refresh env variables on each addition/removal
> ---------------------------------------------------------------------------
>
> Key: JBIDE-15766
> URL: https://issues.jboss.org/browse/JBIDE-15766
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.1.1.Beta1, 4.2.0.Alpha1
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Fix For: 4.1.1.Beta1, 4.2.0.Alpha1
>
>
> When adding/removing environment variables, the openshift-java-client would always request the backend for the full list. This should not be required and avoided
> {code:title=ApplicationResource#addEnvironmentVariable}
> EnvironmentVariableResourceDTO environmentVariableResourceDTO =
> new AddEnvironmentVariableRequest().execute(name, value);
> IEnvironmentVariable environmentVariable = new EnvironmentVariableResource(environmentVariableResourceDTO, this);
> updateEnvironmentVariables();
> return environmentVariable;
> {code}
> {code:title=ApplicationResource#updateEnvironmentVariables}
> protected void updateEnvironmentVariables() throws OpenShiftException {
> if (environmentVariableByName == null) {
> environmentVariableByName = loadEnvironmentVariables();
> } else {
> environmentVariableByName.clear();
> environmentVariableByName.putAll(loadEnvironmentVariables());
> }
> }
> {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, 5 months
[JBoss JIRA] (JBIDE-14544) Cannot run Cordova project on Android Emulator/Device
by Gorkem Ercan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14544?page=com.atlassian.jira.plugi... ]
Gorkem Ercan commented on JBIDE-14544:
--------------------------------------
I mean was the error actually did not list a real serial number but just question marks?
> Cannot run Cordova project on Android Emulator/Device
> -----------------------------------------------------
>
> Key: JBIDE-14544
> URL: https://issues.jboss.org/browse/JBIDE-14544
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: aerogear-hybrid
> Affects Versions: 4.1.0.Beta1
> Environment: Fedora 17 32bit
> Android 4.1.2
> Reporter: Stefan Bunciak
> Assignee: Gorkem Ercan
> Labels: respin-a
> Fix For: 4.1.x, 4.2.x
>
> Attachments: runasandroidemulatorwin7_32.png, Screen Shot 2013-06-03 at 10.50.52 AM.png
>
> Original Estimate: 0 minutes
> Remaining Estimate: 0 minutes
>
> {code}
> java.io.IOException: No such file or directory
> at java.io.UnixFileSystem.createFileExclusively(Native Method)
> at java.io.File.createNewFile(File.java:883)
> at org.jboss.tools.aerogear.hybrid.core.util.FileUtils.fileCopy(FileUtils.java:105)
> at org.jboss.tools.aerogear.hybrid.android.core.adt.AndroidProjectGenerator.generateNativeFiles(AndroidProjectGenerator.java:99)
> at org.jboss.tools.aerogear.hybrid.core.platform.AbstractPlatformProjectGenerator.generateNow(AbstractPlatformProjectGenerator.java:68)
> at org.jboss.tools.aerogear.hybrid.android.core.adt.AndroidLaunchDelegate.buildForLaunch(AndroidLaunchDelegate.java:68)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:825)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:706)
> at org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:1018)
> at org.eclipse.debug.internal.ui.DebugUIPlugin$8.run(DebugUIPlugin.java:1222)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)
> {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, 5 months
[JBoss JIRA] (JBIDE-14544) Cannot run Cordova project on Android Emulator/Device
by Vlado Pakan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14544?page=com.atlassian.jira.plugi... ]
Vlado Pakan commented on JBIDE-14544:
-------------------------------------
Where it can be found?
> Cannot run Cordova project on Android Emulator/Device
> -----------------------------------------------------
>
> Key: JBIDE-14544
> URL: https://issues.jboss.org/browse/JBIDE-14544
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: aerogear-hybrid
> Affects Versions: 4.1.0.Beta1
> Environment: Fedora 17 32bit
> Android 4.1.2
> Reporter: Stefan Bunciak
> Assignee: Gorkem Ercan
> Labels: respin-a
> Fix For: 4.1.x, 4.2.x
>
> Attachments: runasandroidemulatorwin7_32.png, Screen Shot 2013-06-03 at 10.50.52 AM.png
>
> Original Estimate: 0 minutes
> Remaining Estimate: 0 minutes
>
> {code}
> java.io.IOException: No such file or directory
> at java.io.UnixFileSystem.createFileExclusively(Native Method)
> at java.io.File.createNewFile(File.java:883)
> at org.jboss.tools.aerogear.hybrid.core.util.FileUtils.fileCopy(FileUtils.java:105)
> at org.jboss.tools.aerogear.hybrid.android.core.adt.AndroidProjectGenerator.generateNativeFiles(AndroidProjectGenerator.java:99)
> at org.jboss.tools.aerogear.hybrid.core.platform.AbstractPlatformProjectGenerator.generateNow(AbstractPlatformProjectGenerator.java:68)
> at org.jboss.tools.aerogear.hybrid.android.core.adt.AndroidLaunchDelegate.buildForLaunch(AndroidLaunchDelegate.java:68)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:825)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:706)
> at org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:1018)
> at org.eclipse.debug.internal.ui.DebugUIPlugin$8.run(DebugUIPlugin.java:1222)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)
> {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, 5 months
[JBoss JIRA] (JBIDE-15789) Renaming HTML file doesn't change editor title
by Vlado Pakan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15789?page=com.atlassian.jira.plugi... ]
Vlado Pakan commented on JBIDE-15789:
-------------------------------------
Unfortunately no errors in error.log
java -version
{noformat}
java version "1.6.0_32"
Java(TM) SE Runtime Environment (build 1.6.0_32-b05)
Java HotSpot(TM) 64-Bit Server VM (build 20.7-b02, mixed mode)
{noformat}
> Renaming HTML file doesn't change editor title
> ----------------------------------------------
>
> Key: JBIDE-15789
> URL: https://issues.jboss.org/browse/JBIDE-15789
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jsp/jsf/xml/html source editing
> Affects Versions: 4.1.1.Beta1
> Environment: JBT 4.1.1 Beta1-v20131020-0207-B454 Linux KDE
> Reporter: Vlado Pakan
> Assignee: Victor Rubezhny
> Fix For: 4.2.x
>
>
> 1. Create project with HTML file
> 2. Open HTML file in VPE
> 3. Rename HTML file in Package Explorer
> ASSERT: File is renamed in Package Explorer
> ERROR: Editor title of opened HTML file is not changed
--
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, 5 months
[JBoss JIRA] (JBTIS-199) Update category names for installer.
by Paul Leacu (JIRA)
[ https://issues.jboss.org/browse/JBTIS-199?page=com.atlassian.jira.plugin.... ]
Paul Leacu commented on JBTIS-199:
----------------------------------
A modified option B is the winner:
> JBoss Business Process and Rules Development
> JBoss Data Virtualization Development
> JBoss Integration and SOA Development
> JBoss SOA 5.x Development
> Update category names for installer.
> ------------------------------------
>
> Key: JBTIS-199
> URL: https://issues.jboss.org/browse/JBTIS-199
> Project: JBoss Tools Integration Stack
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Affects Versions: 4.1.3
> Reporter: Paul Leacu
> Assignee: Paul Leacu
> Fix For: 4.1.3.Beta5
>
>
> I've received two potentially contradictory BZs ([1], [2]) and there's been recent discussion
> involving the JBDSIS 7.0.0.Beta4 category names. This would affect both equinox/p2 and JBoss
> Central mylyn/discovery labelling. The issue is the following - currently the p2 installer presents
> the user with this:
> > JBoss Business Process and Rules development
> > JBoss Data Virtualization development
> > JBoss Fuse development
> > JBoss SOA 5.x development
> > JBoss SOA development
> The site category name definitions are inconsistent because there's a mixture of product names and
> abstract concept labelling. The idea was to have FuseSource users and legacy 5.x SOA users have
> an easy time finding what they needed to install and a general user could figure out what they wanted
> by the abstract concept label. These are expandable categories - if the user wants to know what their
> getting they can expand the category.
> BZ [1] suggests changing the following:
> Option [A]:
> > JBoss Business Process and Rules development
> > JBoss Data Virtualization development
> > JBoss Fuse development
> > JBoss SOA 5.x development
> > JBoss Fuse Service Works
> That clearly leaves us with 2 "Fuse" categories, one of which doesn't contain the Fuse features, and
> expands on the product name based category labelling. If you're installing 'Fuse Service Works' it
> could be argued that you'd expect to find that as a choice.
> Alan made an interesting suggestion to combine SOA and Fuse, keeping the abstract labelling and
> resulting in the following:
> Option [B]:
> > JBoss Business Process and Rules development
> > JBoss Data Virtualization development
> > JBoss Integration development
> > JBoss SOA 5.x development
> That leaves the 'SOA 5.x' category as an outlier. Acceptable? Would something like this be better?
> Option [C]:
> > JBoss Business Process and Rules development
> > JBoss Data Virtualization development
> > JBoss Integration development
> > JBoss Legacy Integration development
>
> Applying the combine Fuse algorithm to [A] you could also have this:
>
> Option [D]:
> > JBoss Business Process and Rules development
> > JBoss Data Virtualization development
> > JBoss Fuse Service Works
> > JBoss SOA 5.x development
> So - we're post-beta and I'm happy to accommodate the consensus - WDYT?
> Thanks,
> --paull
> [1] https://bugzilla.redhat.com/show_bug.cgi?id=1021282
> [2] https://bugzilla.redhat.com/show_bug.cgi?id=1021283
--
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, 5 months
[JBoss JIRA] (JBIDE-14544) Cannot run Cordova project on Android Emulator/Device
by Gorkem Ercan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14544?page=com.atlassian.jira.plugi... ]
Gorkem Ercan commented on JBIDE-14544:
--------------------------------------
Is ???????????? the actual serial number?
> Cannot run Cordova project on Android Emulator/Device
> -----------------------------------------------------
>
> Key: JBIDE-14544
> URL: https://issues.jboss.org/browse/JBIDE-14544
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: aerogear-hybrid
> Affects Versions: 4.1.0.Beta1
> Environment: Fedora 17 32bit
> Android 4.1.2
> Reporter: Stefan Bunciak
> Assignee: Gorkem Ercan
> Labels: respin-a
> Fix For: 4.1.x, 4.2.x
>
> Attachments: runasandroidemulatorwin7_32.png, Screen Shot 2013-06-03 at 10.50.52 AM.png
>
> Original Estimate: 0 minutes
> Remaining Estimate: 0 minutes
>
> {code}
> java.io.IOException: No such file or directory
> at java.io.UnixFileSystem.createFileExclusively(Native Method)
> at java.io.File.createNewFile(File.java:883)
> at org.jboss.tools.aerogear.hybrid.core.util.FileUtils.fileCopy(FileUtils.java:105)
> at org.jboss.tools.aerogear.hybrid.android.core.adt.AndroidProjectGenerator.generateNativeFiles(AndroidProjectGenerator.java:99)
> at org.jboss.tools.aerogear.hybrid.core.platform.AbstractPlatformProjectGenerator.generateNow(AbstractPlatformProjectGenerator.java:68)
> at org.jboss.tools.aerogear.hybrid.android.core.adt.AndroidLaunchDelegate.buildForLaunch(AndroidLaunchDelegate.java:68)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:825)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:706)
> at org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:1018)
> at org.eclipse.debug.internal.ui.DebugUIPlugin$8.run(DebugUIPlugin.java:1222)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)
> {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, 5 months
[JBoss JIRA] (JBDS-2803) Mobile Hybrid or Hybrid Mobile?
by Vlado Pakan (JIRA)
[ https://issues.jboss.org/browse/JBDS-2803?page=com.atlassian.jira.plugin.... ]
Vlado Pakan closed JBDS-2803.
-----------------------------
Verified with JBDS 7.1.0.Beta1a Beta1-v20131026-0928-B470
> Mobile Hybrid or Hybrid Mobile?
> -------------------------------
>
> Key: JBDS-2803
> URL: https://issues.jboss.org/browse/JBDS-2803
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: aerogear-hybrid, central
> Affects Versions: 7.1.0.Alpha2
> Reporter: Michelle Murray
> Assignee: Gorkem Ercan
> Labels: respin-a
> Fix For: 7.1.0.Beta1
>
> Attachments: mobile_hybrid_feature.png, mobile_hybrid_plugins.png
>
>
> How are we referring to it: Mobile Hybrid or Hybrid Mobile?
> Both are being used. For examples,
> * Update tab in JBoss Central uses "Mobile Hybrid ..."
> * New Project uses "Hybrid Mobile ...."
>
> A consensus needs to be reached and just one wording order used. Which one?
--
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, 5 months