[JBoss JIRA] (JBTIS-27) migrate soa/brms tooling tests from jbosstools-integration-tests to new repo jbosstools-integration-stack-itests
by Paul Leacu (JIRA)
[ https://issues.jboss.org/browse/JBTIS-27?page=com.atlassian.jira.plugin.s... ]
Paul Leacu updated JBTIS-27:
----------------------------
Assignee: Andrej Podhradsky
Component/s: testing
Moved from unassigned.
> migrate soa/brms tooling tests from jbosstools-integration-tests to new repo jbosstools-integration-stack-itests
> ----------------------------------------------------------------------------------------------------------------
>
> Key: JBTIS-27
> URL: https://issues.jboss.org/browse/JBTIS-27
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: distribution, testing
> Affects Versions: 4.0.0
> Reporter: Nick Boldt
> Assignee: Andrej Podhradsky
> Fix For: 4.0.0
>
>
> Currently, we have 3 update sites being built which include tests, from various repos.
> The most notable of these is jbosstools-integration-tests, which includes UI and integration tests (and framework code) for both the core and (JBT) the SOA/BRMS (JBTIS) projects. Additionally, the individual JBT and JBTIS project also publish test features/plugins to their respective update sites.
> These test features are then composited, then aggregated into these sites:
> http://download.jboss.org/jbosstools/updates/nightly/coretests/
> http://download.jboss.org/jbosstools/updates/nightly/soatests/
> http://download.jboss.org/jbosstools/updates/nightly/integrationtests/
> Unfortunately, because of conflicting dependencies and version levels (soa is still on Juno, whereas core is on Kepler) not all tests can run against a single target platform/stack.
> Therefore, I propose we move the SOA/BRMS (JBTIS) tests into a new github repo:
> *jbosstools-integration-stack-itests*
> This would allow those tests to be build/run/published against the upstream JBTIS target platform and projects' test code, as well as incorporating shared code from the upstream core projects' tests (and framework code) published here:
> http://download.jboss.org/jbosstools/updates/nightly/coretests/4.0.juno/
> New update sites would presumably be here:
> http://download.jboss.org/jbosstools/updates/nightly/integration-stack/ (need to migrate the build code and refactor the destination folder - see JBTIS-28)
> http://download.jboss.org/jbosstools/updates/nightly/integration-stack-it...
--
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 Vlado Pakan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15904?page=com.atlassian.jira.plugi... ]
Vlado Pakan edited comment on JBIDE-15904 at 11/8/13 9:15 AM:
--------------------------------------------------------------
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. Already running Android Emulator instance is used no new Android Emulator is started
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
was (Author: vpakan):
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
[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 commented on JBIDE-15904:
---------------------------------------
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] (JBTIS-28) produce a JBTIS unit tests update site (aggregate or composite)
by Paul Leacu (JIRA)
[ https://issues.jboss.org/browse/JBTIS-28?page=com.atlassian.jira.plugin.s... ]
Paul Leacu updated JBTIS-28:
----------------------------
Assignee: Andrej Podhradsky
Component/s: testing
Assigned to Andrej since it was unassigned.
> produce a JBTIS unit tests update site (aggregate or composite)
> ---------------------------------------------------------------
>
> Key: JBTIS-28
> URL: https://issues.jboss.org/browse/JBTIS-28
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: distribution, ESB, releng, target-platform, testing
> Affects Versions: 4.0.0
> Reporter: Nick Boldt
> Assignee: Andrej Podhradsky
> Fix For: 4.0.0
>
>
> JBTIS-27 asks that the core and JBTIS integration tests (itests) be split into a new repo.
> However, some of those itests depend on upstream tests unit tests (utests)... ESB, for example.
> So, either you
> * need to publish a site from which these can be resolved [1]
> ** :: more jobs to maintain, but will make downstream builds resolve p2 deps faster, and facilitate doing headless automated test plugin installation w/ install-grinder or p2.director
> * or you need to ensure that when building/running the itests, you point at the composite JBTIS site [2].
> ** :: requires that you produce a folder somewhere on download.jboss.org, like this one [3], and maintain that composite site... since you can't link to a folder on raw.github.com [4]
> [1] http://download.jboss.org/jbosstools/updates/nightly/soatests/
> [2] https://raw.github.com/jbosstools/jbosstools-integration-stack/master/jbo...
> [3] http://download.jboss.org/jbosstools/updates/integration/juno/integration...
> [4] https://raw.github.com/jbosstools/jbosstools-integration-stack/master/jbo... is 404'd
> Both options would work... but I suggest that building a new aggregate might be better.
> If you agree, you'll want to therefore migrate the code in
> https://github.com/jbosstools/jbosstools-build-sites/tree/master/aggregat...
> to a folder under
> https://github.com/jbosstools/jbosstools-integration-stack/tree/master/jb...
--
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 Vlado Pakan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15904?page=com.atlassian.jira.plugi... ]
Vlado Pakan edited comment on JBIDE-15904 at 11/8/13 8:29 AM:
--------------------------------------------------------------
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
was (Author: vpakan):
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
[JBoss JIRA] (JBIDE-15907) Adds source plugins into JBT's Target-platforms update site
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15907?page=com.atlassian.jira.plugi... ]
Mickael Istria commented on JBIDE-15907:
----------------------------------------
Suggested implementation after discussion on IRC:
* Run 2 invocations of the TargetToRepo mojo: one without "includeSources", one with includeSources=true. The output will be 2 sites.
* Make TP publisher able to publish the site with sources at a different URL
Then Teiid or other JBTIS component TP will be able to reference the site which include sources in their target platform.
> Adds source plugins into JBT's Target-platforms update site
> -----------------------------------------------------------
>
> Key: JBIDE-15907
> URL: https://issues.jboss.org/browse/JBIDE-15907
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: integration-platform, target-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
