[JBoss JIRA] (JBTIS-1051) Return CDI features to JBTIS TP for use by SwitchYard/Fuse Tooling
by Paul Leacu (JIRA)
Paul Leacu created JBTIS-1051:
---------------------------------
Summary: Return CDI features to JBTIS TP for use by SwitchYard/Fuse Tooling
Key: JBTIS-1051
URL: https://issues.jboss.org/browse/JBTIS-1051
Project: JBoss Tools Integration Stack
Issue Type: Bug
Components: target-platform
Affects Versions: 10.2.0.CR1, 4.4.2.CR1
Reporter: Paul Leacu
Assignee: Paul Leacu
Priority: Blocker
The effort to remove unneeded JBT core requirements removed CDI which is needed by SwitchYard. Return:
org.jboss.tools.cdi.deltaspike.feature.feature.group
org.jboss.tools.cdi.feature.feature.group
org.jboss.tools.cdi.seam.feature.feature.group
ref:
Fuse Tooling there are 3 git repos:
- Fuse Tooling itself
- SAP Tooling, because it contains proprietary dependencies
- SwitchYard Tooling because historically a different project and it enters in maintenance mode so we don't make an effort to merge it with Fuse Tooling git repository
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (JBTIS-1050) Move MWAE Jenkins jobs to Central CI
by Paul Leacu (JIRA)
Paul Leacu created JBTIS-1050:
---------------------------------
Summary: Move MWAE Jenkins jobs to Central CI
Key: JBTIS-1050
URL: https://issues.jboss.org/browse/JBTIS-1050
Project: JBoss Tools Integration Stack
Issue Type: Task
Components: distribution
Affects Versions: 10.0.0.GA
Reporter: Paul Leacu
Assignee: Paul Leacu
The middleware Jenkins jobs need to be mograted to Central CI
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (JBDS-4263) Problems after install from Red Hat Central into rh-eclipse46-devstudio
by Lukáš Valach (JIRA)
[ https://issues.jboss.org/browse/JBDS-4263?page=com.atlassian.jira.plugin.... ]
Lukáš Valach edited comment on JBDS-4263 at 2/27/17 9:23 AM:
-------------------------------------------------------------
I reran test against recommended update sites.
[#37|https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstudio/view/devstudio_rpm_tests/job/rpm_rh_central_test.weekly/37/]
Devstudio: 10.4-0.20170227.0853.el7
Update site: https://devstudio.redhat.com/10.0/snapshots/builds/jbosstools-discovery.e...
Failed tests:
* [PMD|https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Dev...]
** There is different problem than in #31 and #32, nothing about log4j.
** [^rh-eclipse46-devstudio-10.4-0.20170227.0853.el7_20170227-0512_install_PMD.txt]
{code}
Caused by: java.lang.ClassNotFoundException: net.sourceforge.pmd.RuleSetNotFoundException cannot be found by net.sourceforge.pmd.eclipse.plugin_4.0.11.v20160626-1057
{code}
[#38|https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstudio/view/devstudio_rpm_tests/job/rpm_rh_central_test.weekly/38/]
Devstudio: 10.4-0.20170227.0853.el7
Update site: https://devstudio.redhat.com/10.0/staging/updates/discovery.earlyaccess/1...
Failed tests:
* JBoss_Business_Process_and_Rules_Development (Installation failed. The installable unit org.jboss.tools.bpel.feature.feature.group has not been found.)
* JBoss_Data_Virtualization_Development (Installation failed)
* JBoss_Developer_Studio_Integration_Stack_Early_Access_Components (Installation failed)
* JBoss_Fuse_Development (Installation failed)
* JBoss_Integration_and_SOA_Development (Installation failed)
* PMD (similar error like in #37)
I have to look why the installation failed.
----
I created second job that runs against the Integration Stack [rpm_rh_central_IS_test.weekly|https://dev-platform-jenkins.rhev-ci-vms.en...].
Which update site should I use for testing against IS? [Snapshots|https://devstudio.redhat.com/10.0/snapshots/updates/integration...] or [stable|https://devstudio.redhat.com/10.0/staging/updates/integration-stac...
{quote}
3. Rather than testing w/ snapshots, why not try the latest 10.3.0.GA staging \[2\] and stable \[3\] sites?
{quote}
Sure, I can do that, but just to be clear... Why do you want me to test Devstudio RPM 10.4 against stable/staged 10.3 version which is older than last snapshot? Do you want me to use staging URL as default or only use it one times?
was (Author: lvalach):
I reran test against recommended update sites.
[#37|https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstudio/view/devstudio_rpm_tests/job/rpm_rh_central_test.weekly/37/]
Devstudio: 10.4-0.20170227.0853.el7
Update site: https://devstudio.redhat.com/10.0/snapshots/builds/jbosstools-discovery.e...
Failed tests:
* [PMD|https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Dev...]
** There is different problem than in #31 and #32, nothing about log4j.
** [^rh-eclipse46-devstudio-10.4-0.20170227.0853.el7_20170227-0512_install_PMD.txt]
{code}
Caused by: java.lang.ClassNotFoundException: net.sourceforge.pmd.RuleSetNotFoundException cannot be found by net.sourceforge.pmd.eclipse.plugin_4.0.11.v20160626-1057
{code}
[#38|https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstudio/view/devstudio_rpm_tests/job/rpm_rh_central_test.weekly/38/]
Devstudio: 10.4-0.20170227.0853.el7
Update site: https://devstudio.redhat.com/10.0/staging/updates/discovery.earlyaccess/1...
Failed tests:
* JBoss_Business_Process_and_Rules_Development (Installation failed. The installable unit org.jboss.tools.bpel.feature.feature.group has not been found.)
* JBoss_Data_Virtualization_Development (Installation failed)
* JBoss_Developer_Studio_Integration_Stack_Early_Access_Components (Installation failed)
* JBoss_Fuse_Development (Installation failed)
* JBoss_Integration_and_SOA_Development (Installation failed)
* PMD (similar error like in #37)
I have to look why the installation failed.
----
I created second job that runs against the Integration Stack [rpm_rh_central_IS_test.weekly|https://dev-platform-jenkins.rhev-ci-vms.en...].
Which update site should I use for testing against IS? [Snapshots|https://devstudio.redhat.com/10.0/snapshots/updates/integration...] or [stable|https://devstudio.redhat.com/10.0/staging/updates/integration-stac...
{quote}
3. Rather than testing w/ snapshots, why not try the latest 10.3.0.GA staging \[2\] and stable \[3\] sites?
{quote}
Sure, I can do that, but just to be clear... Why do you want me to test Devstudio RPM 10.4 against stable/staged 10.3 version which is older than last snapshot? Do you want me to use staging URL as default or only use it one times?
Why there isn't 10.3.0.GA folder? https://devstudio.redhat.com/10.0/stable/updates/discovery.earlyaccess/
> Problems after install from Red Hat Central into rh-eclipse46-devstudio
> -----------------------------------------------------------------------
>
> Key: JBDS-4263
> URL: https://issues.jboss.org/browse/JBDS-4263
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: rpm
> Affects Versions: 10.3.0.AM2
> Reporter: Nick Boldt
> Assignee: Lukáš Valach
> Fix For: 10.4.0.AM1
>
> Attachments: build_31_eclipse_log.zip, build_32_eclipse_log.zip, build_33_eclipse_log.zip, home_eclipse.txt, opt_rh.txt, rh-eclipse46-devstudio-10.4-0.20170227.0853.el7_20170227-0512_install_PMD.txt, rh-eclipse46-devstudio10.3-0.20170206.0203.el7.log.Jboss_Data_Virtualization_Developement_form_IS_repo_strict.txt
>
>
> The installation of software from Red Hat Central causes errors in the log. Some functionality may be broken. We have to test installation of all the stuff from the central and fix the problems.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (JBDS-4289) Update site page not updated to 10.3
by Lukáš Valach (JIRA)
[ https://issues.jboss.org/browse/JBDS-4289?page=com.atlassian.jira.plugin.... ]
Lukáš Valach updated JBDS-4289:
-------------------------------
Description:
Stable update site (1) seems to be not updated to 10.3. They contain text "Latest Build: 10.2.0.GA" and links to Update site zip, Target platform zip, etc. are pointing to 10.2.
(1) https://devstudio.redhat.com/10.0/stable/updates/
!Stable_update_site_2017-02-27_10-14-35.png|thumbnail!
Problem is probably only in html page, because when I try to install BYOE from (1) then I see that update site contains 10.3.
!Stable_update_site_2017-02-27_09-43-17.png|thumbnail!
The central and early access folders for 10.3.0.GA are missing in \[1\] and \[2\].
\[1\] https://devstudio.redhat.com/10.0/stable/updates/discovery.central/
\[2\] https://devstudio.redhat.com/10.0/stable/updates/discovery.earlyaccess/
was:
Stable update site (1) seems to be not updated to 10.3. They contain text "Latest Build: 10.2.0.GA" and links to Update site zip, Target platform zip, etc. are pointing to 10.2.
(1) https://devstudio.redhat.com/10.0/stable/updates/
!Stable_update_site_2017-02-27_10-14-35.png|thumbnail!
Problem is probably only in html page, because when I try to install BYOE from (1) then I see that update site contains 10.3.
!Stable_update_site_2017-02-27_09-43-17.png|thumbnail!
> Update site page not updated to 10.3
> ------------------------------------
>
> Key: JBDS-4289
> URL: https://issues.jboss.org/browse/JBDS-4289
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: updatesite
> Affects Versions: 10.3.0.GA
> Reporter: Lukáš Valach
> Assignee: Nick Boldt
> Fix For: 10.4.0.AM1
>
> Attachments: Stable_update_site_2017-02-27_09-43-17.png, Stable_update_site_2017-02-27_10-14-35.png
>
>
> Stable update site (1) seems to be not updated to 10.3. They contain text "Latest Build: 10.2.0.GA" and links to Update site zip, Target platform zip, etc. are pointing to 10.2.
> (1) https://devstudio.redhat.com/10.0/stable/updates/
> !Stable_update_site_2017-02-27_10-14-35.png|thumbnail!
> Problem is probably only in html page, because when I try to install BYOE from (1) then I see that update site contains 10.3.
> !Stable_update_site_2017-02-27_09-43-17.png|thumbnail!
> The central and early access folders for 10.3.0.GA are missing in \[1\] and \[2\].
> \[1\] https://devstudio.redhat.com/10.0/stable/updates/discovery.central/
> \[2\] https://devstudio.redhat.com/10.0/stable/updates/discovery.earlyaccess/
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (JBDS-4263) Problems after install from Red Hat Central into rh-eclipse46-devstudio
by Lukáš Valach (JIRA)
[ https://issues.jboss.org/browse/JBDS-4263?page=com.atlassian.jira.plugin.... ]
Lukáš Valach commented on JBDS-4263:
------------------------------------
I reran test against recommended update sites.
[#37|https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstudio/view/devstudio_rpm_tests/job/rpm_rh_central_test.weekly/37/]
Devstudio: 10.4-0.20170227.0853.el7
Update site: https://devstudio.redhat.com/10.0/snapshots/builds/jbosstools-discovery.e...
Failed tests:
* [PMD|https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Dev...]
** There is different problem than in #31 and #32, nothing about log4j.
** [^rh-eclipse46-devstudio-10.4-0.20170227.0853.el7_20170227-0512_install_PMD.txt]
{code}
Caused by: java.lang.ClassNotFoundException: net.sourceforge.pmd.RuleSetNotFoundException cannot be found by net.sourceforge.pmd.eclipse.plugin_4.0.11.v20160626-1057
{code}
[#38|https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstudio/view/devstudio_rpm_tests/job/rpm_rh_central_test.weekly/38/]
Devstudio: 10.4-0.20170227.0853.el7
Update site: https://devstudio.redhat.com/10.0/staging/updates/discovery.earlyaccess/1...
Failed tests:
* JBoss_Business_Process_and_Rules_Development (Installation failed. The installable unit org.jboss.tools.bpel.feature.feature.group has not been found.)
* JBoss_Data_Virtualization_Development (Installation failed)
* JBoss_Developer_Studio_Integration_Stack_Early_Access_Components (Installation failed)
* JBoss_Fuse_Development (Installation failed)
* JBoss_Integration_and_SOA_Development (Installation failed)
* PMD (similar error like in #37)
I have to look why the installation failed.
----
I created second job that runs against the Integration Stack [rpm_rh_central_IS_test.weekly|https://dev-platform-jenkins.rhev-ci-vms.en...].
Which update site should I use for testing against IS? [Snapshots|https://devstudio.redhat.com/10.0/snapshots/updates/integration...] or [stable|https://devstudio.redhat.com/10.0/staging/updates/integration-stac...
{quote}
3. Rather than testing w/ snapshots, why not try the latest 10.3.0.GA staging \[2\] and stable \[3\] sites?
{quote}
Sure, I can do that, but just to be clear... Why do you want me to test Devstudio RPM 10.4 against stable/staged 10.3 version which is older than last snapshot? Do you want me to use staging URL as default or only use it one times?
Why there isn't 10.3.0.GA folder? https://devstudio.redhat.com/10.0/stable/updates/discovery.earlyaccess/
> Problems after install from Red Hat Central into rh-eclipse46-devstudio
> -----------------------------------------------------------------------
>
> Key: JBDS-4263
> URL: https://issues.jboss.org/browse/JBDS-4263
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: rpm
> Affects Versions: 10.3.0.AM2
> Reporter: Nick Boldt
> Assignee: Lukáš Valach
> Fix For: 10.4.0.AM1
>
> Attachments: build_31_eclipse_log.zip, build_32_eclipse_log.zip, build_33_eclipse_log.zip, home_eclipse.txt, opt_rh.txt, rh-eclipse46-devstudio-10.4-0.20170227.0853.el7_20170227-0512_install_PMD.txt, rh-eclipse46-devstudio10.3-0.20170206.0203.el7.log.Jboss_Data_Virtualization_Developement_form_IS_repo_strict.txt
>
>
> The installation of software from Red Hat Central causes errors in the log. Some functionality may be broken. We have to test installation of all the stuff from the central and fix the problems.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (JBDS-4263) Problems after install from Red Hat Central into rh-eclipse46-devstudio
by Lukáš Valach (JIRA)
[ https://issues.jboss.org/browse/JBDS-4263?page=com.atlassian.jira.plugin.... ]
Lukáš Valach updated JBDS-4263:
-------------------------------
Attachment: rh-eclipse46-devstudio-10.4-0.20170227.0853.el7_20170227-0512_install_PMD.txt
> Problems after install from Red Hat Central into rh-eclipse46-devstudio
> -----------------------------------------------------------------------
>
> Key: JBDS-4263
> URL: https://issues.jboss.org/browse/JBDS-4263
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: rpm
> Affects Versions: 10.3.0.AM2
> Reporter: Nick Boldt
> Assignee: Lukáš Valach
> Fix For: 10.4.0.AM1
>
> Attachments: build_31_eclipse_log.zip, build_32_eclipse_log.zip, build_33_eclipse_log.zip, home_eclipse.txt, opt_rh.txt, rh-eclipse46-devstudio-10.4-0.20170227.0853.el7_20170227-0512_install_PMD.txt, rh-eclipse46-devstudio10.3-0.20170206.0203.el7.log.Jboss_Data_Virtualization_Developement_form_IS_repo_strict.txt
>
>
> The installation of software from Red Hat Central causes errors in the log. Some functionality may be broken. We have to test installation of all the stuff from the central and fix the problems.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (JBDS-4263) Problems after install from Red Hat Central into rh-eclipse46-devstudio
by Mat Booth (JIRA)
[ https://issues.jboss.org/browse/JBDS-4263?page=com.atlassian.jira.plugin.... ]
Mat Booth commented on JBDS-4263:
---------------------------------
PMD problem sounds similar to JBIDE-23834
> Problems after install from Red Hat Central into rh-eclipse46-devstudio
> -----------------------------------------------------------------------
>
> Key: JBDS-4263
> URL: https://issues.jboss.org/browse/JBDS-4263
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: rpm
> Affects Versions: 10.3.0.AM2
> Reporter: Nick Boldt
> Assignee: Lukáš Valach
> Fix For: 10.4.0.AM1
>
> Attachments: build_31_eclipse_log.zip, build_32_eclipse_log.zip, build_33_eclipse_log.zip, home_eclipse.txt, opt_rh.txt, rh-eclipse46-devstudio10.3-0.20170206.0203.el7.log.Jboss_Data_Virtualization_Developement_form_IS_repo_strict.txt
>
>
> The installation of software from Red Hat Central causes errors in the log. Some functionality may be broken. We have to test installation of all the stuff from the central and fix the problems.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (JBIDE-24012) org.jboss.tools.cordovasim: Version has not incremented in 4.4.x and master branches
by Ilya Buziuk (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24012?page=com.atlassian.jira.plugi... ]
Ilya Buziuk commented on JBIDE-24012:
-------------------------------------
browsersim / cordovasime / aerogear plugins have been properly upversioned in master, so there should not be problems with building Oxygen TP.
> org.jboss.tools.cordovasim: Version has not incremented in 4.4.x and master branches
> ------------------------------------------------------------------------------------
>
> Key: JBIDE-24012
> URL: https://issues.jboss.org/browse/JBIDE-24012
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: aerogear-hybrid
> Affects Versions: 4.5.0.AM1
> Reporter: Nick Boldt
> Assignee: Ilya Buziuk
> Priority: Blocker
> Fix For: 4.5.0.AM1
>
>
> {code}
> [ERROR] Failed to execute goal org.eclipse.tycho.extras:tycho-p2-extras-plugin:1.0.0:compare-version-with-baselines
> (default) on project org.jboss.tools.cordovasim: Only qualifier changed for (org.jboss.tools.cordovasim/3.8.3.v20170222-0934).
> Expected to have bigger x.y.z than what is available in baseline (3.8.3.v20161201-1914) {code} -- https://jenkins.hosts.mwqe.eng.bos.redhat.com/hudson/view/DevStudio/view/...
> Solution: upversion your plugin(s)/feature(s) to a new version in 4.4.x and master branches.
> Perhaps you want 3.8.4 in 4.4.x branch, and 3.8.100 in the master branch?
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years