[JBoss JIRA] (JBIDE-2032) Help button works not in all wizards.
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-2032?page=com.atlassian.jira.plugin... ]
Denis Golovin updated JBIDE-2032:
---------------------------------
Attachment: Resource - Eclipse Platform _028.png
Screenshot added for PR
[^Resource - Eclipse Platform _028.png]
> Help button works not in all wizards.
> -------------------------------------
>
> Key: JBIDE-2032
> URL: https://issues.jboss.org/browse/JBIDE-2032
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: help
> Affects Versions: 2.1.0.beta1
> Reporter: Anton Klimkovich
> Assignee: Denis Golovin
> Priority: Minor
> Fix For: 4.2.x
>
> Attachments: CreateJSFLibrary.PNG, DriverDefinitions.PNG, EditDriverDefinitions.PNG, InstallNewServerAdapter.PNG, JSFImplementationLibrary.PNG, NewConnectionProfile.PNG, NewDriverDefinitions.PNG, NewSeamRuntime.PNG, NewServer.PNG, Resource - Eclipse Platform _028.png
>
>
> Wizards with non-working help button attached.
--
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-16393) Fix/recover for bad usage of submodules in VPE
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16393?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-16393:
---------------------------------------------
B - its referencing to a commit SHA to a repo with zero tags or branches. Sure we point to a sha1 but zero idea what changes since then are relevant for the branch we are pulling in from.
C /D - lets just wait do this before we are sure submodules are proper here
There is also F - with submodules you can't fork easily. Its just painful
I want to know where these git repos are forked from. Show original repos please.
If they are not forked from something that the commits can easily be merged back into or from then it is pointless to have them as submodules.
If they are clean repos that can be used to easily consume from and contribute to upstream then it makes sense - but then why are these not just done as proper maven projects we can depend on and integrate without using git submodules ?
> Fix/recover for bad usage of submodules in VPE
> ----------------------------------------------
>
> Key: JBIDE-16393
> URL: https://issues.jboss.org/browse/JBIDE-16393
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: browsersim, visual-page-editor-core
> Affects Versions: 4.1.1.Final, 4.2.0.Alpha1
> Reporter: Max Rydahl Andersen
> Assignee: Ilya Buziuk
> Priority: Critical
> Fix For: 4.1.2.Final, 4.2.0.Alpha2
>
>
> both master and branch of vpe is using submodules
> https://github.com/jbosstools/jbosstools-vpe/blob/master/.gitmodules
> https://github.com/jbosstools/jbosstools-vpe/blob/jbosstools-4.1.x/.gitmo...
> Things wrong:
> A) These are pointing to personal repos
> B) No tags used
> C) readme.adoc not documenting it
> D) not announced anywhere
> E) git clone no longer sufficient
> We need to get this fixed/cleaned up in both branch and master.
> *jbosstools-4.1.1.Final* - e498c091f79c140 ( JBIDE-15814 CordovaSim: Adding navigator.app.backHistory support )
--
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] (JBDS-2635) Installation sometimes fail with bundle was not found on Windows
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-2635?page=com.atlassian.jira.plugin.... ]
Denis Golovin commented on JBDS-2635:
-------------------------------------
One more option is RCP application. Eclipse has everything to create an installer and this p2 implementation could be good starting point http://git.eclipse.org/c/equinox/rt.equinox.p2.git/tree/bundles/org.eclip....
> Installation sometimes fail with bundle was not found on Windows
> ----------------------------------------------------------------
>
> Key: JBDS-2635
> URL: https://issues.jboss.org/browse/JBDS-2635
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: installer
> Affects Versions: 7.0.0.Beta1
> Environment: JBDS 7.0.0.Beta1, W8_64, Java 1.7.0_07
> Reporter: Jiri Peterka
> Assignee: Denis Golovin
> Fix For: 8.0.0.Alpha2
>
> Attachments: 1369261136479.log, 1372203584223.log, 1372203590931.bak_0.log, 1372203590931.bak_1.log, 1372203590931.bak_2.log, 1372203590931.log, 1372355790692.log
>
>
> For the first time JBDS 7.0.0.Beta1 failed on windows8:
> {code}
> An error occurred while installing the items
> session context was:(profile=jbds, phase=org.eclipse.equinox.internal.p2.engine.phases.Install, operand=null --> [R]org.eclipse.jst.common.frameworks 1.1.601.v201208160700, action=org.eclipse.equinox.internal.p2.touchpoint.eclipse.actions.InstallBundleAction).
> The artifact file for osgi.bundle,org.eclipse.jst.common.frameworks,1.1.601.v201208160700 was not found.
> Application failed, log file location: C:\vw\jbds-7.0.0-beta1\studio\p2\director\configuration\1369261136579.log
> {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] (JBDS-2880) com.jboss.jbds.product.EclipseGenerator application failure in isntaller
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-2880?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-2880:
--------------------------------
Fix Version/s: 8.0.0.Alpha2
> com.jboss.jbds.product.EclipseGenerator application failure in isntaller
> ------------------------------------------------------------------------
>
> Key: JBDS-2880
> URL: https://issues.jboss.org/browse/JBDS-2880
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: installer
> Affects Versions: 7.1.0.GA
> Reporter: Denis Golovin
> Assignee: Denis Golovin
> Fix For: 8.0.0.Alpha2
>
>
> {code}!SESSION 2014-01-16 16:34:55.784 -----------------------------------------------
> eclipse.buildId=unknown
> java.version=1.7.0_51
> java.vendor=Oracle Corporation
> BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US
> Framework arguments: -application com.jboss.jbds.product.EclipseGenerator
> Command-line arguments: -application com.jboss.jbds.product.EclipseGenerator -clean
> !ENTRY org.eclipse.osgi 4 0 2014-01-16 16:34:57.716
> !MESSAGE Application error
> !STACK 1
> java.lang.RuntimeException: Application "com.jboss.jbds.product.EclipseGenerator" could not be found in the registry. The applications available are: com.jboss.jbds.p2.director, org.eclipse.equinox.app.error, org.eclipse.equinox.p2.director, org.eclipse.equinox.p2.garbagecollector.application, org.eclipse.equinox.p2.publisher.InstallPublisher, org.eclipse.equinox.p2.publisher.EclipseGenerator, org.eclipse.equinox.p2.publisher.ProductPublisher, org.eclipse.equinox.p2.publisher.FeaturesAndBundlesPublisher, org.eclipse.equinox.p2.repository.repo2runnable, org.eclipse.equinox.p2.repository.metadataverifier, org.eclipse.equinox.p2.artifact.repository.mirrorApplication, org.eclipse.equinox.p2.metadata.repository.mirrorApplication.
> at org.eclipse.equinox.internal.app.EclipseAppContainer.startDefaultApp(EclipseAppContainer.java:248)
> at org.eclipse.equinox.internal.app.MainApplicationLauncher.run(MainApplicationLauncher.java:29)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:354)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:181)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:636)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:591)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1450)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1426){code}
> Installer could not run this application becasue it is trying to start it inside p2 director, just installed product should be used instead.
--
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-3937) Create Stress JUnit Test Suite withch is included all available JUnit tests from all components
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-3937?page=com.atlassian.jira.plugin... ]
Denis Golovin commented on JBIDE-3937:
--------------------------------------
{quote}What do you mean by "Stress test", do you mean "performance tests"?{quote}
Idea was to detect performance issues related to memory leaks, number of projects created in workspace (some tests do not clean up after themselves), integration problems when all JBT components are in the same bucket. It also about detection memory or resource leaks that leads to problems in long eclipse sessions.
{quote}If so, it would make more sense to create a real usage scenario and execute it on a static environment and look at execution time trends to see how this evolves.{quote}
That was the Idea, but I just wanted to use current tests instead of real scenarios.
{quote}What would be the goal of such a "master" test suite?{quote}
To see if all installed JBoss Tools modules can live in one bucked for a long session (it is sure gonna be long running test suite)
{quote}Who would be in charge of it?{quote}
I hope QA could manage it to see if JBT is good enough to be released.
{quote}Is it about unit tests or integration tests ?{quote}
We don't have unit tests for now, what we have is integration tests.
> Create Stress JUnit Test Suite withch is included all available JUnit tests from all components
> -----------------------------------------------------------------------------------------------
>
> Key: JBIDE-3937
> URL: https://issues.jboss.org/browse/JBIDE-3937
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: build, qa
> Affects Versions: 3.0.0.GA
> Reporter: Denis Golovin
> Assignee: Denis Golovin
> Fix For: 4.2.x
>
>
> Why we need this?
> The Idea is in emulation a long development session. Now all tests suites are ran one by one each in its own session on clean workspace. A longest test suite takes around 15-20 minutes. Such test suite would emulate an about one hour long development session which can help to find memory leaks or other integration problems.
> It should be able to start on selected JBT build. It should download last or selected version of JBT form download site and start Stress Test Suite.
--
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-16220) create an all-in-one build for JBT projects, using submodules
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16220?page=com.atlassian.jira.plugi... ]
Denis Golovin commented on JBIDE-16220:
---------------------------------------
This approach could be actually good way to do integration builds once a week or every change in this composite git repo. It would be similar to tag files in eclipse. Not every commit to actual module would trigger it. If module lead wants integration build he/she should go an update submodule in composite repo.
It also would let us do:
- branches in this composite repo for different streams
- tagging in one place for everything like:
{code}git foreach 'git tag 4.1.0.GA -m "JBoss Tools 4.1.0.GA"{code}
The name for repo would be jbosstools-releng (similar to what they have in eclipse) or jbosstools-submodules or jbosstools-aggregated or jbosstools-product or e.t.c ... your suggestions are welcome.
> create an all-in-one build for JBT projects, using submodules
> -------------------------------------------------------------
>
> Key: JBIDE-16220
> URL: https://issues.jboss.org/browse/JBIDE-16220
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Affects Versions: 4.2.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.2.x
>
> Attachments: buildlog_maven311.txt
>
>
> Git 1.8.2 includes an option to have submodules track a branch tip, rather than specific commit IDs.
> {code:title=https://github.com/git/git/blob/master/Documentation/RelNotes/1.8.2.txt#L186-L188}
> "git submodule" started learning a new mode to integrate with the
> tip of the remote branch (as opposed to integrating with the commit
> recorded in the superproject's gitlink).
> {code}
> Therefore, while the solution [~dgolovin] has for his https://github.com/dgolovin/jbosstools-submodules project is a decent option, it requires updating to stay current with branch tips. It's therefore only really as useful as it stays current.
> If we can get Git 1.8.2 or newer installed on the Jenkins slaves, we could do a submodule build against whatever branch we wanted - master, 4.2.0.Alpha1x, etc.
--
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-16389) Query parameters are not allowed in the runtime configuration for CordovaSim
by Gorkem Ercan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16389?page=com.atlassian.jira.plugi... ]
Gorkem Ercan updated JBIDE-16389:
---------------------------------
Original Estimate: 0 minutes
Remaining Estimate: 0 minutes
Component/s: browsersim
> Query parameters are not allowed in the runtime configuration for CordovaSim
> ----------------------------------------------------------------------------
>
> Key: JBIDE-16389
> URL: https://issues.jboss.org/browse/JBIDE-16389
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: aerogear-hybrid, browsersim
> Affects Versions: 4.1.1.Final
> Reporter: Vineet Reynolds
> Original Estimate: 0 minutes
> Remaining Estimate: 0 minutes
>
> Related to JBIDE-16388, I'm creating a page: {{mobileapp.html}} that employs a query parameter ({{?target=cordova}}) to trigger the condition relevant to hybrid applications. The Hybrid Mobile application uses the REST APIs hosted on OpenShift via absolute URLs instead of relative URLs. The logic makes use of the presence/absence of the query parameter to use absolute (cloud) URLs instead of relative URLs.
> When I create a runtime configuration to bypass JBIDE-16388 (to specify {{mobileapp.html}} as the start page), I cannot specify '?' in the path : http://www.screencast.com/t/ZYVMPtUWjq2
> This fails only in CordovaSim, and the app works when run in emulators/devices.
--
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-16389) Query parameters are not allowed in the runtime configuration for CordovaSim
by Gorkem Ercan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16389?page=com.atlassian.jira.plugi... ]
Gorkem Ercan commented on JBIDE-16389:
--------------------------------------
CordovaSim launch config's start page validation seems to be more strict then the rest of the tools
> Query parameters are not allowed in the runtime configuration for CordovaSim
> ----------------------------------------------------------------------------
>
> Key: JBIDE-16389
> URL: https://issues.jboss.org/browse/JBIDE-16389
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: aerogear-hybrid, browsersim
> Affects Versions: 4.1.1.Final
> Reporter: Vineet Reynolds
> Original Estimate: 0 minutes
> Remaining Estimate: 0 minutes
>
> Related to JBIDE-16388, I'm creating a page: {{mobileapp.html}} that employs a query parameter ({{?target=cordova}}) to trigger the condition relevant to hybrid applications. The Hybrid Mobile application uses the REST APIs hosted on OpenShift via absolute URLs instead of relative URLs. The logic makes use of the presence/absence of the query parameter to use absolute (cloud) URLs instead of relative URLs.
> When I create a runtime configuration to bypass JBIDE-16388 (to specify {{mobileapp.html}} as the start page), I cannot specify '?' in the path : http://www.screencast.com/t/ZYVMPtUWjq2
> This fails only in CordovaSim, and the app works when run in emulators/devices.
--
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-16388) Cordovasim does not use the Hybrid Mobile project's start page
by Gorkem Ercan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16388?page=com.atlassian.jira.plugi... ]
Gorkem Ercan updated JBIDE-16388:
---------------------------------
Original Estimate: 0 minutes
Remaining Estimate: 0 minutes
Component/s: browsersim
> Cordovasim does not use the Hybrid Mobile project's start page
> --------------------------------------------------------------
>
> Key: JBIDE-16388
> URL: https://issues.jboss.org/browse/JBIDE-16388
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: aerogear-hybrid, browsersim
> Affects Versions: 4.1.1.Final
> Reporter: Vineet Reynolds
> Original Estimate: 0 minutes
> Remaining Estimate: 0 minutes
>
> When I run a Hybrid Mobile project under CordovaSim, it does not use the start page defined in {{config.xml}}.
> If the application were to use a different application start page, say {{mobileapp.html}} in {{config.xml}}, CordovaSim reports the following error: http://www.screencast.com/t/8odNCS5FWK
> I'm forced to create a new runtime configuration that explicitly defines the start page again. This is not necessary for running under the Android emulator or device, and is a problem only under CordovaSim.
--
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