[JBoss JIRA] (TOOLSDOC-426) Add info about JBDS Central TP zip
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/TOOLSDOC-426?page=com.atlassian.jira.plug... ]
Nick Boldt commented on TOOLSDOC-426:
-------------------------------------
1. Download the zip manually, as you would the update site zip. There's no one-click integration within Eclipse or JBDS to do so, but you could open the internal browser in Eclipse/JBDS and browse to the site w/ the zip on it).
2. Help > Install New Software... > Add... > Archive... browse for the zip on your filesystem > select feature(s). Install.
> Add info about JBDS Central TP zip
> ----------------------------------
>
> Key: TOOLSDOC-426
> URL: https://issues.jboss.org/browse/TOOLSDOC-426
> Project: Documentation for JBoss Tools and Developer Studio
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: User Guide - JBoss Central & JBoss Perspective
> Affects Versions: 4.1.1
> Reporter: Michelle Murray
> Assignee: Michelle Murray
> Fix For: 4.1.1
>
> Original Estimate: 2 hours
> Remaining Estimate: 2 hours
>
> JBDS Central TP (3rd party) zip enables user to install 3rd party plug-ins while offline.
> How is this implemented?
> * Do users initiate the install download of Central TP from within IDE (like JBoss Central examples offline)?
> * Or do users download the zip from access.redhat (+ other sites) like the update zip?
> * And once users have zip how do they install bits of it? Window > Install New Software and point to zip on system (link install from update zip)?
> Will require a new section in User Guide, Central chapter, probably in customization section.
--
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-15892) Weird code in JBT installation script: install.sh
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15892?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-15892:
------------------------------------
Valid point. Would you want a different README for bash scripts vs. cmd scripts? or one big README w/ both?
> Weird code in JBT installation script: install.sh
> --------------------------------------------------
>
> Key: JBIDE-15892
> URL: https://issues.jboss.org/browse/JBIDE-15892
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Affects Versions: 4.1.1.Beta1
> Reporter: Pavol Srna
> Assignee: Nick Boldt
> Priority: Critical
> Fix For: 4.1.1.CR1
>
> Attachments: JBIDE15892.png
>
>
> install.sh contains some weird hardcoded stuff. you can download the script from offcial pages: http://www.jboss.org/tools/download/installation/update_4_1.html#fromscript
> [~nickboldt] can you explain how is it meant to be used?
> I don't think it is very straight forward for the user.
> {code}
> #!/bin/bash
> # install all of JBT into Eclipse Standard bundle
> target=${HOME}/eclipse/eclipse43; cd ${target}; rm -fr ${target}/eclipse
> tar xzf /tmp/eclipse-standard-kepler-R-linux-gtk-x86_64.tar.gz
> ${target}/eclipse/eclipse -consolelog -nosplash -data /tmp -application org.eclipse.ant.core.antRunner -f \
> install.xml \
> -DsourceZip=/tmp/jbosstools-Update-4.1.0.Final_2013-07-19_19-47-52-B380.zip \
> -DotherRepos=http://download.jboss.org/jbosstools/updates/stable/kepler/central/core/ \
> -DtargetDir=${target}/eclipse/
> # [p2.dir] Installing org.hibernate.eclipse.feature.source.feature.group 3.7.0.Final-v20130717-0715-B84.
> # ...
> # [p2.dir] Installing org.mozilla.xulrunner.feature.feature.group 1.9.218.Final-v20121126-2356-B155.
> # [p2.dir] Operation completed in 212518 ms.
> # install JBT Central, including Subclipse w/ SVNKit into Eclipse JEE bundle
> target=${HOME}/eclipse/eclipse43; cd ${target}; rm -fr ${target}/eclipse
> tar xzf /tmp/eclipse-jee-kepler-R-linux-gtk-x86_64.tar.gz
> ${target}/eclipse/eclipse -consolelog -nosplash -data /tmp -application org.eclipse.ant.core.antRunner -f \
> install.xml \
> -DsourceZip=/tmp/jbosstools-Update-4.1.0.Final_2013-07-19_19-47-52-B380.zip \
> -DotherRepos=http://download.jboss.org/jbosstools/updates/stable/kepler/central/core/ \
> -DtargetDir=${target}/eclipse/
> -Dinstall="org.jboss.tools.community.central.feature.feature.group,\
> org.tigris.subversion.subclipse.feature.group,\
> org.tigris.subversion.clientadapter.svnkit.feature.feature.group,\
> com.collabnet.subversion.merge.feature.feature.group,\
> net.java.dev.jna.feature.group,\
> org.tigris.subversion.clientadapter.feature.feature.group,\
> org.tigris.subversion.subclipse.graph.feature.feature.group,\
> org.tmatesoft.svnkit.feature.group"
> # [p2.dir] Installing org.jboss.tools.community.central.feature.feature.group 1.2.0.Final-v20130719-2050-B70.
> # [p2.dir] Installing org.tigris.subversion.subclipse.feature.group 1.8.20.
> # [p2.dir] Installing org.tigris.subversion.clientadapter.svnkit.feature.feature.group 1.7.9.1.
> # ...
> # [p2.dir] Operation completed in 55635 ms.
> {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-15806) Migrate jbosstools-4.1.x and master branches to use Tycho 0.19.0
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15806?page=com.atlassian.jira.plugi... ]
Mickael Istria updated JBIDE-15806:
-----------------------------------
Fix Version/s: 4.1.1.CR1
4.2.0.Alpha1
Affects Version/s: (was: 4.2.0.Alpha1)
(was: 4.1.1.CR1)
> Migrate jbosstools-4.1.x and master branches to use Tycho 0.19.0
> ----------------------------------------------------------------
>
> Key: JBIDE-15806
> URL: https://issues.jboss.org/browse/JBIDE-15806
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Reporter: Nick Boldt
> Assignee: Mickael Istria
> Fix For: 4.1.1.CR1, 4.2.0.Alpha1
>
>
> With the release of Tycho 0.19, we should explore moving up to that in our parent pom, Locus, and TP builds.
> {quote}
> Tycho milestone 0.19.0 has been released and is available from maven central.
> See the release notes [1] for details of enhancements and bug fixes in this release.
> Thanks to Mickael Istria, Nepomuk Seiler, Roland Grunberg, and Thanh Ha who contributed patches for this release.
> And thanks and to everyone who helped us with testing the staged version.
> Regards,
> Tycho team
> [1] http://wiki.eclipse.org/Tycho/Release_Notes/0.19
> {quote}
--
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-15806) Migrate jbosstools-4.1.x and master branches to use Tycho 0.19.0
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15806?page=com.atlassian.jira.plugi... ]
Mickael Istria resolved JBIDE-15806.
------------------------------------
Resolution: Done
This was fixed on master, no issues and CI, and then applied on branch as well.
> Migrate jbosstools-4.1.x and master branches to use Tycho 0.19.0
> ----------------------------------------------------------------
>
> Key: JBIDE-15806
> URL: https://issues.jboss.org/browse/JBIDE-15806
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Reporter: Nick Boldt
> Assignee: Mickael Istria
> Fix For: 4.1.1.CR1, 4.2.0.Alpha1
>
>
> With the release of Tycho 0.19, we should explore moving up to that in our parent pom, Locus, and TP builds.
> {quote}
> Tycho milestone 0.19.0 has been released and is available from maven central.
> See the release notes [1] for details of enhancements and bug fixes in this release.
> Thanks to Mickael Istria, Nepomuk Seiler, Roland Grunberg, and Thanh Ha who contributed patches for this release.
> And thanks and to everyone who helped us with testing the staged version.
> Regards,
> Tycho team
> [1] http://wiki.eclipse.org/Tycho/Release_Notes/0.19
> {quote}
--
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-15904) Test Cordova combinations
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15904?page=com.atlassian.jira.plugi... ]
Martin Malina edited comment on JBIDE-15904 at 11/8/13 9:35 AM:
----------------------------------------------------------------
On OS X Mavericks, first attempt to run the cordova app on a virtual android device failed (I followed Vlado's instructions and this was test case 1).
I got these errors:
https://www.dropbox.com/s/kywu3nhf8tfyvnn/Screenshot%202013-11-08%2014.49...
https://www.dropbox.com/s/rxhr1jh7d4ny0a1/Screenshot%202013-11-08%2014.50...
Maybe the Virtual Device wasn't ready yet, I'm not sure
On second attempt it worked
When I edited index.html and ran Run on Android Emulator again, a second instance of the virtual device was launched, but the app was run on the first one and the second one stayed blank.
So to try again, I closed both emulators and did Run on Android Emulator again. A build was kicked off, android emulator was started, but at the end I got:
APK installation did not succeed
https://www.dropbox.com/s/pzpvy5b3yiiakto/Screenshot%202013-11-08%2015.34...
And the app was not launched :(
was (Author: mmalina):
On OS X Mavericks, first attempt to run the cordova app on a virtual android device failed (I followed Vlado's instructions and this was test case 1).
I got these errors:
https://www.dropbox.com/s/kywu3nhf8tfyvnn/Screenshot%202013-11-08%2014.49...
https://www.dropbox.com/s/rxhr1jh7d4ny0a1/Screenshot%202013-11-08%2014.50...
Maybe the Virtual Device wasn't ready yet, I'm not sure
On second attempt it worked
When I edited index.html and ran Run on Android Emulator again, a second instance of the virtual device was launched, but the app was run on the first one and the second one stayed blank.
> Test Cordova combinations
> -------------------------
>
> Key: JBIDE-15904
> URL: https://issues.jboss.org/browse/JBIDE-15904
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Affects Versions: 4.1.1.Beta1
> Reporter: Max Rydahl Andersen
> Assignee: Vlado Pakan
> Priority: Blocker
> Fix For: 4.1.1.CR1
>
>
> Use this jira to collect results from testing:
> 1)
> Run On Android Emulator. On windows, Linux and Mac (in that prio order).
>
> Run On Android Device: On windows, Linux and Mac (in that prio order)
>
> The more SDK version we cover the better with the above two. I do not think
> we can cover all so we should start with latest and make our way down.
>
> 2)
> Changes on the Run configurations for Run on Android...
>
> 3)
> Install Cordova Plugin:
>
> Offline, windows, Linux, Mac
>
> 4)
> Share project via git. Import existing project.
>
> 5)
> Export native platform project
>
> 6)
> Export Mobile Application
> windows, linux, mac
--
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-15904) Test Cordova combinations
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15904?page=com.atlassian.jira.plugi... ]
Martin Malina edited comment on JBIDE-15904 at 11/8/13 9:28 AM:
----------------------------------------------------------------
On OS X Mavericks, first attempt to run the cordova app on a virtual android device failed (I followed Vlado's instructions and this was test case 1).
I got these errors:
https://www.dropbox.com/s/kywu3nhf8tfyvnn/Screenshot%202013-11-08%2014.49...
https://www.dropbox.com/s/rxhr1jh7d4ny0a1/Screenshot%202013-11-08%2014.50...
Maybe the Virtual Device wasn't ready yet, I'm not sure
On second attempt it worked
When I edited index.html and ran Run on Android Emulator again, a second instance of the virtual device was launched, but the app was run on the first one and the second one stayed blank.
was (Author: mmalina):
On OS X Mavericks, first attempt to run the cordova app on a virtual android device failed (I followed Vlado's instructions and this was test case 1).
I got these errors:
https://www.dropbox.com/s/kywu3nhf8tfyvnn/Screenshot%202013-11-08%2014.49...
https://www.dropbox.com/s/rxhr1jh7d4ny0a1/Screenshot%202013-11-08%2014.50...
Maybe the Virtual Device wasn't ready yet, I'm not sure
On second attempt it worked
> Test Cordova combinations
> -------------------------
>
> Key: JBIDE-15904
> URL: https://issues.jboss.org/browse/JBIDE-15904
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Affects Versions: 4.1.1.Beta1
> Reporter: Max Rydahl Andersen
> Assignee: Vlado Pakan
> Priority: Blocker
> Fix For: 4.1.1.CR1
>
>
> Use this jira to collect results from testing:
> 1)
> Run On Android Emulator. On windows, Linux and Mac (in that prio order).
>
> Run On Android Device: On windows, Linux and Mac (in that prio order)
>
> The more SDK version we cover the better with the above two. I do not think
> we can cover all so we should start with latest and make our way down.
>
> 2)
> Changes on the Run configurations for Run on Android...
>
> 3)
> Install Cordova Plugin:
>
> Offline, windows, Linux, Mac
>
> 4)
> Share project via git. Import existing project.
>
> 5)
> Export native platform project
>
> 6)
> Export Mobile Application
> windows, linux, mac
--
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:
----------------------------------------
Yes another update. Command is now
{code}
$ cd tests/my.test.bundle
$ mvn clean verify -Dtest.installPath=/home/me/jbdevstudio-8.0.0.Alpha1-SNAPSHOT/studio
{code}
[~psrna] Do you still like it?
> 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
