November 2013 - jbosstools-issues

[JBoss JIRA] (JBIDE-13869) Find a way to run testsuite against existing builds but with different TP without requiring publishing

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13869?page=com.atlassian.jira.plugi... ] Pavol Srna commented on JBIDE-13869: ------------------------------------ +1 > 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

1
0
0 / 0

[JBoss JIRA] (JBIDE-15907) Adds source plugins into JBT's update site

by Paul Richardson (JIRA)

Paul Richardson created JBIDE-15907: --------------------------------------- Summary: Adds source plugins into JBT's update site Key: JBIDE-15907 URL: https://issues.jboss.org/browse/JBIDE-15907 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: integration-platform Reporter: Paul Richardson The integration-stack target uses http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.3... to provide the base eclipse dependencies, eg. org.eclipse.jface. This update site does not include source plugins. For higher level projects, like Teiid Designer, that use the IS as its target platform, this means that eclipse classes do not find nor display their source. This makes debugging UI elements a lot harder. Thus, can source plugins be included in the integration-stack base.target via the above dependent update site? -- 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

1
0
0 / 0

[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: ---------------------------------------- I've updated the PR so one can use only -Dtycho.surefire.runtimePath=... (without -Prun-on-installed-application to run tests against a given installation. Command is now: {code} $ cd tests/my.test.bundle $ mvn clean verify -Dtycho.surefire.runtimePath=/home/me/jbdevstudio-8.0.0.Alpha1-SNAPSHOT/studio {code} If everyone is ok with that change, I'll merge it and then apply it also on 4.1.1 branch for immediate usage by QE. > 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

1
0
0 / 0

[JBoss JIRA] (JBIDE-7515) Add (optional) start/stop script to the Deploy only server

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-7515?page=com.atlassian.jira.plugin... ] Rob Stryker updated JBIDE-7515: ------------------------------- Fix Version/s: 4.2.0.Alpha1 (was: 4.1.x) > Add (optional) start/stop script to the Deploy only server > ---------------------------------------------------------- > > Key: JBIDE-7515 > URL: https://issues.jboss.org/browse/JBIDE-7515 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Reporter: Max Rydahl Andersen > Assignee: Rob Stryker > Fix For: 4.2.0.Alpha1 > > > Currently the "Deploy only" server can just "deploy" - I suggest we add support for running a start (and optional) a stop script to let users start/stop what they want. > This would be a nice stop-gap feature for things like AS 7 or other runtimes out in the world until "native" integration is possible. -- 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

1
0
0 / 0

[JBoss JIRA] (JBIDE-15170) Quickstart (helloworld-jms) added as part of JBIDE-14940 includes readme file with broken wiki links

by Sande Gilda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15170?page=com.atlassian.jira.plugi... ] Sande Gilda commented on JBIDE-15170: ------------------------------------- [~ldimaggio]: Please clarify which links you mean. If this bug is referring to the links to sections in the parent readme file, [~rafabene] fixed it with this commit: https://github.com/jboss-jdf/jdf-site/commit/7c108c8f6 > Quickstart (helloworld-jms) added as part of JBIDE-14940 includes readme file with broken wiki links > ---------------------------------------------------------------------------------------------------- > > Key: JBIDE-15170 > URL: https://issues.jboss.org/browse/JBIDE-15170 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.1.0.CR1 > Reporter: Len DiMaggio > Assignee: Fred Bricon > Fix For: 4.1.1.Final > > > The Readme.md file for the new "backend" helloworld-jms quickstart includes the same content as: http://www.jboss.org/jdf/quickstarts/jboss-as-quickstart/helloworld-jms/ > The wiki links in the readme do not work. -- 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

1
0
0 / 0

[JBoss JIRA] (JBIDE-15905) allow users to set openshift-java-client specific timeout in JBoss Tools

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15905?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-15905: ------------------------------------- Description: In JBIDE-15880 we provide a system property that allow JBoss Tools to set a timeout that affects only the http connections that the openshift-java-client is using. We We should allow users to set this value in JBoss tools via Eclipse preferences (was: In JBIDE-15880 we provide a system property that allow JBoss Tools to set a timeout that affects only the http connections that the openshift-java-client is using. We should use this specific timeout in JBoss Tools and eventually provide a UI for the Eclipse preferences ) > allow users to set openshift-java-client specific timeout in JBoss Tools > ------------------------------------------------------------------------ > > Key: JBIDE-15905 > URL: https://issues.jboss.org/browse/JBIDE-15905 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.1.1.Beta1, 4.2.0.Alpha1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.1.1.CR1, 4.2.0.Alpha1 > > > In JBIDE-15880 we provide a system property that allow JBoss Tools to set a timeout that affects only the http connections that the openshift-java-client is using. We We should allow users to set this value in JBoss tools via Eclipse preferences -- 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

1
0
0 / 0

[JBoss JIRA] (JBIDE-15905) allow users to set openshift-java-client specific timeout in JBoss Tools

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15905?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-15905: ------------------------------------- Summary: allow users to set openshift-java-client specific timeout in JBoss Tools (was: use openshift-java-client specific timeout in JBoss Tools) > allow users to set openshift-java-client specific timeout in JBoss Tools > ------------------------------------------------------------------------ > > Key: JBIDE-15905 > URL: https://issues.jboss.org/browse/JBIDE-15905 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.1.1.Beta1, 4.2.0.Alpha1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.1.1.CR1, 4.2.0.Alpha1 > > > In JBIDE-15880 we provide a system property that allow JBoss Tools to set a timeout that affects only the http connections that the openshift-java-client is using. We should use this specific timeout in JBoss Tools and eventually provide a UI for the Eclipse preferences -- 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

1
0
0 / 0

[JBoss JIRA] (JBIDE-13869) Find a way to run testsuite against existing builds but with different TP without requiring publishing

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13869?page=com.atlassian.jira.plugi... ] Pavol Srna commented on JBIDE-13869: ------------------------------------ Thanks Mickael for your help. I did mvn clean install parent pom, but unfortunately had a bad parent pom version in integration-tests pom. I can report that it works. This is a huge improvement for QE. Can I ask you to apply the PR also on 4.1.1 branch? I'm convinced we can benefit from it before 4.1.1.Final. > 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

1
0
0 / 0

[JBoss JIRA] (JBIDE-15904) Test Cordova combinations

by Vlado Pakan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15904?page=com.atlassian.jira.plugi... ] Vlado Pakan commented on JBIDE-15904: ------------------------------------- 1. Install Android tooling from JBoss Central 2. After required restart JBT dialog asking to install new Android SDK should appear. Install latest available Android API. 3. Open Java Perspective 4. Open Window > Android SDK Manager and install Android SDK Build Tools 19, ARM EABI v7a System Image 19, Android Support Library 19 5. Restart Eclipse 6. Open Window > ADROID Virtual Device Manager and add some device (Nexus 7, Android 4.4 - API Level 19, ARM) 7. Try to start added device to see if it works Java JDK has to available 8. Create default Hybrid Mobile applicatio. Menu New > Other > Mobile > Hybrid Mobile (Cordova) Application. Specify Project name, Application and ID. ID has to have form ???.???.???... e.g. org.jboss.tool.cordova Test case 1: 1. connect android device enabled for development 2. right click on created project and Menu Run As > Run on Android Device. ASSERT: Application is deployed and started on device. 3. right click on created project and Menu Run As > Run on Android Emulator. ASSERT: Application is deployed and started on Android Emulator. 4. change index.html file of created project save and run project again on Android Device and Android Emulator. ASSERT: Chagnes are deployed. It could be needed to unlock screen on Device/Emulator Test case 2: 1. Add another Android Virtual Device 2. Open Run As configuration of <cordova-project> run on Adnroid Emulator 3. Select newly added AVD as Virtual Device 4. Choose Apply and Run ASSERT: <cordova-project> runs on newly created Virtual Device Test modification of Run As configuration of <cordova-project> run on Adnroid. I'm not able to provide more details on this one because I do not have available any Android device today. Will update description later Test case 3: 1. Open <cordova-project>/www/config.xml file with Cordova Configuration Editor 2. Select second tab Platform Properties and choose Add... to add Feature 3. Select org.appache.cordova.device-motion plugin in opened Cordova Plugin Discovery dialog and choose finish ASSERT: Feature Acceleroimeter was added to config.xml Features on 2nd. tab and also to config.xml source ASSERT: org.appache.cordova.device-motion plugin was added to <cordova-project>/plugins directory and it has not empty content Test case 4: ASSERT: project https://github.com/vpakan/cordovatestprojects/tree/master/cordova-acceler... can be imported and runs properly. Try to click oon Accelerometer link within cordova application to see if accelerometer data are read. Test it with CordovaSim, Android Device and Android Emulator ASSERT: Open new clean workspace and import <cordova-project> from previously used workspace. Follow checks written above Test case 5: Try to use accelerator application to be able to check if Cordova API works 1. Select <cordova-project> 2 Right click on it and choose Export > Mobile > Export Native Platform Project 3. Export to all available platforms ASSERT: No errors occured during export For Android only: 4. <android-sdks>/tools/android avd 5. Run Android Emulator 6. Build application ant -f <exported-cordova-project>/android/build.xml debug 7. Install .apk file to running emulator <android-sdks>/platform-tools/adb install <exported-cordova-project>/android/bin/<appname>-debug.apk 8. Verify application running on emulator Test case 6: Try to use accelerator application to be able to check if Cordova API works 1. Select <cordova-project> 2 Right click on it and choose Export > Mobile > Export Mobile Application 3. Export to all available platforms For Android only: 4. <android-sdks>/tools/android avd 5. Run Android Emulator 6. Install .apk file to running emulator <android-sdks>/platform-tools/adb install <exported-cordova-project>/android/bin/<appname>-debug.apk 7. Verify application running on emulator > 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

1
0
0 / 0

[JBoss JIRA] (JBIDE-15495) OpenShift server adapter: publish locks the whole workspace

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15495?page=com.atlassian.jira.plugi... ] Rob Stryker reassigned JBIDE-15495: ----------------------------------- Assignee: Andre Dietisheim (was: Rob Stryker) > OpenShift server adapter: publish locks the whole workspace > ----------------------------------------------------------- > > Key: JBIDE-15495 > URL: https://issues.jboss.org/browse/JBIDE-15495 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift, server > Affects Versions: 4.1.0.Final > Reporter: Xavier Coulon > Assignee: Andre Dietisheim > Labels: openshift_server_adapter > Fix For: LATER > > Attachments: Screen Shot 2013-09-17 at 10.42.43 AM.png > > > Have 2 projects in a workspace, one of them is an OpenShift application > Deploy some changes on OpenShift, and while the publication is performed (git push, then OS restarts the server), go to the second (unrelated) project and try to move a file from a package to another package in the same project. > The 'Publish' operation locked the whoel workspace, which means that the move operation needs to wait. -- 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

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues November 2013