[JBoss JIRA] (JBIDE-14388) Running "run in Android emulator" a second time fails
by Vlado Pakan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14388?page=com.atlassian.jira.plugi... ]
Vlado Pakan commented on JBIDE-14388:
-------------------------------------
But because now it's not possible to run application on Android Emulator it cannot be verified
> Running "run in Android emulator" a second time fails
> -----------------------------------------------------
>
> Key: JBIDE-14388
> URL: https://issues.jboss.org/browse/JBIDE-14388
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: aerogear-hybrid
> Reporter: Sebastien Blanc
> Assignee: Gorkem Ercan
> Labels: respin-a
> Fix For: 4.1.1.Beta1
>
> Original Estimate: 0 minutes
> Remaining Estimate: 0 minutes
>
> If a Android emulator is already running and that we run again from the project "run on Android Emulator" a second Emulator attempts to start and fails because some data is already in use.
> I'm not sure but when running again the project on the emulator, the plugin should check if there is already an instance of the emulator running and redeploy on this one instead of trying to start a new 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
[JBoss JIRA] (JBIDE-15885) CAnnot run cordova project when android sdk version is <13
by Gorkem Ercan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15885?page=com.atlassian.jira.plugi... ]
Gorkem Ercan updated JBIDE-15885:
---------------------------------
Description:
if user has old (api level<13) android target defined the project fails to build for running on android.
See JBIDE-14544 for details.
was:
if user has old (<19) android sdk installed you cannot run the project on android device.
See JBIDE-14544 for details.
> CAnnot run cordova project when android sdk version is <13
> ----------------------------------------------------------
>
> Key: JBIDE-15885
> URL: https://issues.jboss.org/browse/JBIDE-15885
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: aerogear-hybrid
> Affects Versions: 4.1.1.Beta1
> Reporter: Max Rydahl Andersen
> Priority: Critical
> Fix For: 4.1.1.CR1
>
>
> if user has old (api level<13) android target defined the project fails to build for running on android.
> See JBIDE-14544 for details.
--
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-14388) Running "run in Android emulator" a second time fails
by Gorkem Ercan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14388?page=com.atlassian.jira.plugi... ]
Gorkem Ercan commented on JBIDE-14388:
--------------------------------------
1. Create a Hybrid Mobile Project
2. Select Run on Android Emulator
ASSERT: Application start on the emulator
3. Close the app
4. Select Run On Android Emulator again
ASSERT: observe that a second emulator is not started and application runs again on the emulator
> Running "run in Android emulator" a second time fails
> -----------------------------------------------------
>
> Key: JBIDE-14388
> URL: https://issues.jboss.org/browse/JBIDE-14388
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: aerogear-hybrid
> Reporter: Sebastien Blanc
> Assignee: Gorkem Ercan
> Labels: respin-a
> Fix For: 4.1.1.Beta1
>
> Original Estimate: 0 minutes
> Remaining Estimate: 0 minutes
>
> If a Android emulator is already running and that we run again from the project "run on Android Emulator" a second Emulator attempts to start and fails because some data is already in use.
> I'm not sure but when running again the project on the emulator, the plugin should check if there is already an instance of the emulator running and redeploy on this one instead of trying to start a new 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
[JBoss JIRA] (JBIDE-13869) Find a way to run testsuite against existing builds but with different TP without requiring publishing
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13869?page=com.atlassian.jira.plugi... ]
Mickael Istria commented on JBIDE-13869:
----------------------------------------
[~jpeterka] [~vpakan] [~psrna] [~rhopp] [~rawagner]... Guys, this change is for you. Can you please review the PR and give a try on your favourite use-case?
You'll need to:
* Fetch code from PR
* "mvn install" parent pom
* Use a version of JBDS that matches the stream of the test module (JBDS 8.0.0.Alpha1 for master, JBDS 7.1.0.Beta1 for 4.1.1 branch).
and run the command as described above. You can also run it on an Eclipse instance (instead of JBDS), but you'll need to override the "tycho.surefire.profileName" property to match the right profile.
> Find a way to run testsuite against existing builds but with different TP without requiring publishing
> ------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-13869
> URL: https://issues.jboss.org/browse/JBIDE-13869
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Reporter: Max Rydahl Andersen
> Assignee: Mickael Istria
> Priority: Critical
> Fix For: 4.1.1.Final, 4.2.0.Alpha1
>
>
> Case for 4.0.1 was TP change was done late, how do we run tests without having to rebuild everything again.
> Possible options:
> 1) Create new testsuite that depends on all other testsuites and run them in surefire test.
> 2) use something else than surefire to run the already built testsuites.
--
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