[JBoss JIRA] (JBIDE-14544) Cannot run Cordova project on Android Emulator/Device
by Len DiMaggio (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14544?page=com.atlassian.jira.plugi... ]
Len DiMaggio edited comment on JBIDE-14544 at 5/31/13 10:06 AM:
----------------------------------------------------------------
Suggestion from Max:
go and find org.jboss.tools.aerogear.hybrid.core-*.jar file,
do unzip -d org.jboss.tools.aerogear.hybrid.core-<exactsameasonthejar> org.jboss.tools.aerogear.hybrid.core-*.jar
then remove the .jar, start eclipse with -clean and try this usecase again
(./plugins/org.jboss.tools.aerogear.hybrid.core_1.0.0.Beta1-v20130523-2211-B7.jar)
was (Author: ldimaggio):
Suggestion from Max:
go and find org.jboss.tools.aerogear.hybrid.core-*.jar file,
do unzip -d org.jboss.tools.aerogear.hybrid.core-<exactsameasonthejar> org.jboss.tools.aerogear.hybrid.core-*.jar
then remove the .jar, start eclipse with -clean and try this usecase again
> 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
> Priority: Blocker
> Labels: respin-a
> Fix For: 4.1.0.Beta1
>
> 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, 10 months
[JBoss JIRA] (JBIDE-12815) Create a JBoss Tools Orbit
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-12815?page=com.atlassian.jira.plugi... ]
Mickael Istria commented on JBIDE-12815:
----------------------------------------
pomDepedencies consider won't help much IMO and it appears difficult to use.
However, I'd rather see those dependencies defined in a target platform to ensure we don't have "leaks" of unexpected bundles.
> Create a JBoss Tools Orbit
> --------------------------
>
> Key: JBIDE-12815
> URL: https://issues.jboss.org/browse/JBIDE-12815
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: Build/Releng, locus
> Reporter: Mickael Istria
> Assignee: Max Rydahl Andersen
> Fix For: 4.1.0.Beta2
>
> Attachments: pom.xml
>
>
> Since all JBoss Eclipse-based project probably share some needs for usual libraries, we should create a JBoss Tools Orbit project in which one we would provide those 3rd-party dependencies packaged as OSGi Bundle in a p2 repository.
> In a first time, we could simply create some OSGi "wrappers" around those jars.
--
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, 10 months
[JBoss JIRA] (JBIDE-14706) openshift-java-client: add support for initial git url when creating a new application
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14706?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-14706:
------------------------------------------
In the integration tests I currently install the spring-eap6-quickstart which failes here and there when jboss fails to start up.
Talking about it with bill deCoste my impression is that I should deploy a simplistic demo-app which I then try to access instead.
> openshift-java-client: add support for initial git url when creating a new application
> --------------------------------------------------------------------------------------
>
> Key: JBIDE-14706
> URL: https://issues.jboss.org/browse/JBIDE-14706
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.1.0.Beta1
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Fix For: 4.1.0.Beta2
>
>
> In order to fullfill JBIDE-14588 we need to add the ability to the openshift-java-client to tell it create a new application with a given initial git url that the initial application code and configuration will get cloned from.
--
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, 10 months
[JBoss JIRA] (JBIDE-14544) Cannot run Cordova project on Android Emulator/Device
by Len DiMaggio (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14544?page=com.atlassian.jira.plugi... ]
Len DiMaggio commented on JBIDE-14544:
--------------------------------------
Suggestion from Max:
go and find org.jboss.tools.aerogear.hybrid.core-*.jar file,
do unzip -d org.jboss.tools.aerogear.hybrid.core-<exactsameasonthejar> org.jboss.tools.aerogear.hybrid.core-*.jar
then remove the .jar, start eclipse with -clean and try this usecase again
> 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
> Priority: Blocker
> Labels: respin-a
> Fix For: 4.1.0.Beta1
>
> 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, 10 months
[JBoss JIRA] (JBIDE-12815) Create a JBoss Tools Orbit
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-12815?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-12815:
------------------------------------
Turns out as usual I documented why I needed these IN THE CODE.
{code:title=https://github.com/nickboldt/jbosstools-locus/blob/master/pom.xml#L265}
<!-- needed to resolve org.junit and org.apache.ant, org.eclipse.osgi, etc. -->
<repository>
<id>JBoss Tools Target Platform Site</id>
<url>http://download.jboss.org/jbosstools/updates/juno/</url>
<layout>p2</layout>
<snapshots>
<enabled>true</enabled>
</snapshots>
<releases>
<enabled>true</enabled>
</releases>
</repository>
<!-- needed to resolve org.apache.commons.beanutils -->
<repository>
<id>Orbit Update Site</id>
<url>http://download.jboss.org/jbosstools/updates/requirements/orbit/S20130427...</url>
<layout>p2</layout>
<snapshots>
<enabled>true</enabled>
</snapshots>
<releases>
<enabled>true</enabled>
</releases>
</repository>
{code}
I suppose we could include some of these deps as m2 deps instead of p2 deps if we enable pomDependencies=consider.
{code:title=http://wiki.eclipse.org/Tycho/How_Tos/Dependency_on_pom-first_artifacts#What_happens_under_the_hood}
<plugin>
<groupId>org.eclipse.tycho</groupId>
<artifactId>target-platform-configuration</artifactId>
<version>${tycho-version}</version>
<configuration>
<pomDependencies>consider</pomDependencies>
</configuration>
</plugin>{code}
> Create a JBoss Tools Orbit
> --------------------------
>
> Key: JBIDE-12815
> URL: https://issues.jboss.org/browse/JBIDE-12815
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: Build/Releng, locus
> Reporter: Mickael Istria
> Assignee: Max Rydahl Andersen
> Fix For: 4.1.0.Beta2
>
> Attachments: pom.xml
>
>
> Since all JBoss Eclipse-based project probably share some needs for usual libraries, we should create a JBoss Tools Orbit project in which one we would provide those 3rd-party dependencies packaged as OSGi Bundle in a p2 repository.
> In a first time, we could simply create some OSGi "wrappers" around those jars.
--
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, 10 months
[JBoss JIRA] (JBIDE-14126) Weinre Inspector is showing no data within Elements tab
by Vlado Pakan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14126?page=com.atlassian.jira.plugi... ]
Vlado Pakan commented on JBIDE-14126:
-------------------------------------
HTML5 in system browser + local Weinre Server works.
HTML5 in JBDS internal browser + local Weinre Server doesn't works.
I think I did click on Target link and it didn't work. I have added screenshot just to show that Target is connected. I will check it with JBDS 7.0.0.Beta1b build.
> Weinre Inspector is showing no data within Elements tab
> -------------------------------------------------------
>
> Key: JBIDE-14126
> URL: https://issues.jboss.org/browse/JBIDE-14126
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: browsersim
> Affects Versions: 4.1.0.Alpha2
> Environment: Fedora 17 64bit, KDE, jbdevstudio-product-eap-universal-7.0.0.Alpha2-v20130421-0725-B198, Java Sun JDK 1.6.0_32
> Reporter: Vlado Pakan
> Assignee: Konstantin Marmalyukov
> Fix For: 4.1.0.Beta2
>
> Attachments: localamazon.png, localbrowsersimhtml5.png, localhtml5.png, phonegapamazon.png
>
>
> 1. Open www.amazon.com page in Browsersim
> 2. Run Weinre Inspector via Browsersim context menu "Weinre"
> ERROR: No elements shown on Elements tab
> Client is connected:
> !phonegapamazon.png!
> 3. Run Weinre server locally.
> 4. Set Browsersim to use local Weinre server
> 5. Run Weinre Inspector as in step 2.
> ERROR: No elements shown on Elements tab
> Client is connected:
> !localamazon.png!
> 6. Create HTML5 project from JBoss Central
> 7. Insert script tag allowing debugging via local Weinre server to index.html
> 8. Run HTML5 project on Server
> 9. Open HTML5 index.html in system borwser
> ASSERT: Weinre debugging works
> !localhtml5.png!
> ERROR: Weinre debugging is not working from JBDS internal browser
> 10. Open index.html of HTML5 project in Browsersim
> 11. Open Weinre debug link in Browser
> ERROR: No elements shown on Elements tab
> Client is connected:
> !localbrowsersimhtml5.png!
--
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, 10 months
[JBoss JIRA] (JBIDE-14126) Weinre Inspector is showing no data within Elements tab
by Konstantin Marmalyukov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14126?page=com.atlassian.jira.plugi... ]
Konstantin Marmalyukov commented on JBIDE-14126:
------------------------------------------------
1. amazon.com with default server: one of possible reasons is that weinre works not very fast, it need some time to build DOM tree.
2. amazon.com via local server: reproduces for me. Page reload helps me to to make everything work fine.
3. HTML5 in system browser: Cannot understand when weinre works and when not. Vlado. please, update description.
4. HTML5 in BrowserSim: due to your screenshot I understand that you does not click on target. Select it and everything will be fine.
Actyally we can do nothinng with weinre unstable working. So I think this ticked could be rosolved with "Wont fix" resolution.
> Weinre Inspector is showing no data within Elements tab
> -------------------------------------------------------
>
> Key: JBIDE-14126
> URL: https://issues.jboss.org/browse/JBIDE-14126
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: browsersim
> Affects Versions: 4.1.0.Alpha2
> Environment: Fedora 17 64bit, KDE, jbdevstudio-product-eap-universal-7.0.0.Alpha2-v20130421-0725-B198, Java Sun JDK 1.6.0_32
> Reporter: Vlado Pakan
> Assignee: Konstantin Marmalyukov
> Fix For: 4.1.0.Beta2
>
> Attachments: localamazon.png, localbrowsersimhtml5.png, localhtml5.png, phonegapamazon.png
>
>
> 1. Open www.amazon.com page in Browsersim
> 2. Run Weinre Inspector via Browsersim context menu "Weinre"
> ERROR: No elements shown on Elements tab
> Client is connected:
> !phonegapamazon.png!
> 3. Run Weinre server locally.
> 4. Set Browsersim to use local Weinre server
> 5. Run Weinre Inspector as in step 2.
> ERROR: No elements shown on Elements tab
> Client is connected:
> !localamazon.png!
> 6. Create HTML5 project from JBoss Central
> 7. Insert script tag allowing debugging via local Weinre server to index.html
> 8. Run HTML5 project on Server
> 9. Open HTML5 index.html in system borwser
> ASSERT: Weinre debugging works
> !localhtml5.png!
> ERROR: Weinre debugging is not working from JBDS internal browser
> 10. Open index.html of HTML5 project in Browsersim
> 11. Open Weinre debug link in Browser
> ERROR: No elements shown on Elements tab
> Client is connected:
> !localbrowsersimhtml5.png!
--
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, 10 months