[JBoss JIRA] (JBTIS-27) migrate soa/brms tooling tests from jbosstools-integration-tests to new repo jbosstools-integration-stack-itests
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBTIS-27?page=com.atlassian.jira.plugin.s... ]
Nick Boldt updated JBTIS-27:
----------------------------
Description:
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)
http://download.jboss.org/jbosstools/updates/nightly/integration-stack-it...
was:
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/
> 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
> Affects Versions: 4.0.0
> Reporter: Nick Boldt
> 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)
> 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
13 years
[JBoss JIRA] (JBTIS-27) migrate soa/brms tooling tests from jbosstools-integration-tests to new repo jbosstools-integration-stack-itests
by Nick Boldt (JIRA)
Nick Boldt created JBTIS-27:
-------------------------------
Summary: 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
Affects Versions: 4.0.0
Reporter: Nick Boldt
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/
--
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
13 years
[JBoss JIRA] (JBIDE-13796) rename jbosstools-integration-tests to jbosstools-itests
by Nick Boldt (JIRA)
Nick Boldt created JBIDE-13796:
----------------------------------
Summary: rename jbosstools-integration-tests to jbosstools-itests
Key: JBIDE-13796
URL: https://issues.jboss.org/browse/JBIDE-13796
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: testing-tools, updatesite
Affects Versions: 4.1.0.Alpha1
Reporter: Nick Boldt
Assignee: Max Rydahl Andersen
Fix For: 4.1.0.Alpha2
To be consistent and more clear about purpose/content, I propose we rename the github project jbosstools-integration-tests to jbosstools-itests.
--
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
13 years
[JBoss JIRA] (JBIDE-11602) Provide first class support for client side development
by Victor Rubezhny (JIRA)
[ https://issues.jboss.org/browse/JBIDE-11602?page=com.atlassian.jira.plugi... ]
Victor Rubezhny commented on JBIDE-11602:
-----------------------------------------
Regarding the question on support for the latest jQuery library in VJet...
I found the issue in BugZilla on updating the VJet jQuery Type Libraries: [Bug 399447 - Update Jquery type library to 1.9 |https://bugs.eclipse.org/bugs/show_bug.cgi?id=399447]. The issue is new and not targeted yet, so jQuery 1.9.1 is not supported at the moment.
The other issue - [Bug 395742 - vjet initial contribution of type libraries |https://bugs.eclipse.org/bugs/show_bug.cgi?id=395742] (Resolved, fixed) states that the following versions are supported:
- jQuery 1.4
- jQuery Mobile 1.0 Alpha 4.1 (Requires JQuery Type lib)
More detail on Type Libraries and their versions included to the contribution see: [Bug 395742 - vjet initial contribution of type libraries |https://bugs.eclipse.org/bugs/show_bug.cgi?id=395742]
> Provide first class support for client side development
> -------------------------------------------------------
>
> Key: JBIDE-11602
> URL: https://issues.jboss.org/browse/JBIDE-11602
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: jsp/jsf/xml/html source editing
> Reporter: Sebastien Deleuze
> Assignee: Victor Rubezhny
> Labels: jsdt, vjet
> Fix For: 4.1.x
>
> Attachments: jbosstools-add-vjet-dependencies-patch.patch, jquery-1.5.1.min.js.jpg, jquery.tagcanvas.min.js.jpg, nexj-JS-Content-Assist-On-a-JS-in-ticket-monster-project-After-Insertion.jpg, nexj-JS-Content-Assist-On-a-JS-in-ticket-monster-project.jpg, nexj-JS-Content-Assist-On-an-HTML-1-in-ticket-monster-project-After-Insertion.jpg, nexj-JS-Content-Assist-On-an-HTML-1-in-ticket-monster-project.jpg, nexj-JS-Content-Assist-On-an-HTML-2-1-in-ticket-monster-project-After-Insertion.jpg, nexj-JS-Content-Assist-On-an-HTML-2-1-in-ticket-monster-project.jpg, nexj-JS-Content-Assist-On-an-HTML-2-2-in-ticket-monster-project-After-Insertion.jpg, nexj-JS-Content-Assist-On-an-HTML-2-2-in-ticket-monster-project.jpg, nexj-JS-Content-Assist-On-Any-JS-in-ticket-monster-project-After-Insertion.jpg, nexj-JS-Content-Assist-On-Any-JS-in-ticket-monster-project.jpg, nexj-JS-Content-Assist-On-Any-JS-in-ticket-monster-project.jpg, vjet-JS-Content-Assist-On-a-JS-in-ticket-monster-project-After-Insertion.jpg, vjet-JS-Content-Assist-On-a-JS-in-ticket-monster-project.jpg, vjet-JS-Content-Assist-On-Any-JS-in-ticket-monster-project-After-Insertion.jpg, vjet-JS-Content-Assist-On-Any-JS-in-ticket-monster-project.jpg, vjet-JS-Content-Assist-On-HTML-1-in-ticket-monster-project-After-Insertion.jpg, vjet-JS-Content-Assist-On-HTML-1-in-ticket-monster-project.jpg, vjet-JS-Content-Assist-On-HTML-2-1-in-ticket-monster-project-After-Insertion.jpg, vjet-JS-Content-Assist-On-HTML-2-1-in-ticket-monster-project.jpg, vjet-JS-Content-Assist-On-HTML-2-2-in-ticket-monster-project-After-Insertion.jpg, vjet-JS-Content-Assist-On-HTML-2-2-in-ticket-monster-project.jpg
>
>
> Web application development is currently moving in many projects from end to end server side technologies to HTML5 RIA developed with REST Webservices/ Webscoket on serverside + pure client side technologies GUI (Backbone.js for example).
> Eclipse has been always been quite bad in the field of advanced Javascript development. JSDT was a good start, but its development has been stopped for a few years, and in its current status, it is not really a good tool for real HTML5/JS dev. From what I know, there is no roadmap for strong move on this field in the WTP team. The only real Eclipse initiative for client side development is Orion (http://www.eclipse.org/orion/) outside of the IDE.
> The only other alternative is Aptana Studio 3, acquired last year by AppAccelerator.
> My question is : is there any plan to consider client side development as a first class citizen in JBoss Studio, even if this question apply to the whole Eclipse Ecosystem ? Other IDE like Netbeans or IntelliJ Idea have a strong support for these technologies, and my guess is this lack may be a significant blocking point in the following years.
> Thanks in advance for your feedback.
--
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
13 years
[JBoss JIRA] (JBDS-2499) Not able to resize the preferences window in JDBS 6
by Sande Gilda (JIRA)
[ https://issues.jboss.org/browse/JBDS-2499?page=com.atlassian.jira.plugin.... ]
Sande Gilda updated JBDS-2499:
------------------------------
Attachment: JDBS6-01.png
JDBS6-02.png
JDBS6-03.png
JDBS6-04.png
Screenshots taken through the process. The last shot shows how the Preferences window appears as a vertical bar.
> Not able to resize the preferences window in JDBS 6
> ---------------------------------------------------
>
> Key: JBDS-2499
> URL: https://issues.jboss.org/browse/JBDS-2499
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: ui/branding, Upstream
> Affects Versions: 6.0.0.GA
> Environment: Fedora 17
> jdbs 6.0.0.GA, build id: GA-v20121206-1855-B186, build date: 20121206-1855
> Reporter: Sande Gilda
> Attachments: JDBS6-01.png, JDBS6-02.png, JDBS6-03.png, JDBS6-04.png
>
>
> To recreate:
> Start JDBS.
> Choose menu: Window --> Preferences
> Grab a side edge to drag it wider, but it snaps down to a narrow vertical bar.
> When I hover over the edges, I get the arrow resize icon, but I can't resize it.
> At this point, I have to kill the 2 processes: one jbdevstudio and one java (for jbds and the popup window.
--
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
13 years
[JBoss JIRA] (JBDS-2499) Not able to resize the preferences window in JDBS 6
by Sande Gilda (JIRA)
Sande Gilda created JBDS-2499:
---------------------------------
Summary: Not able to resize the preferences window in JDBS 6
Key: JBDS-2499
URL: https://issues.jboss.org/browse/JBDS-2499
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: ui/branding, Upstream
Affects Versions: 6.0.0.GA
Environment: Fedora 17
jdbs 6.0.0.GA, build id: GA-v20121206-1855-B186, build date: 20121206-1855
Reporter: Sande Gilda
To recreate:
Start JDBS.
Choose menu: Window --> Preferences
Grab a side edge to drag it wider, but it snaps down to a narrow vertical bar.
When I hover over the edges, I get the arrow resize icon, but I can't resize it.
At this point, I have to kill the 2 processes: one jbdevstudio and one java (for jbds and the popup window.
--
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
13 years
[JBoss JIRA] (JBIDE-13561) Cannot embed cartridges
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13561?page=com.atlassian.jira.plugi... ]
RH Bugzilla Integration commented on JBIDE-13561:
-------------------------------------------------
Dan McPherson <dmcphers(a)redhat.com> changed the Status of [bug 911322|https://bugzilla.redhat.com/show_bug.cgi?id=911322] from VERIFIED to CLOSED
> Cannot embed cartridges
> -----------------------
>
> Key: JBIDE-13561
> URL: https://issues.jboss.org/browse/JBIDE-13561
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.0.0.Final
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Priority: Blocker
> Fix For: 4.1.0.Alpha1
>
> Attachments: apptype-is-embedded-cartridge.png, cartridge-type-not-embedded.png, jbds6-erroring-embedding-cartridge.png
>
>
> If you try to embed cartridges (or remove embedded cartridges) in 4.0.0 Final or JBDS6, then you wont be able to do it.
> This is an issue that shall help us track modifications on the OpenShift platform. There's nothing we can do about it, it's *OpenShift that has to hot-fix*.
--
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
13 years