[JBoss JIRA] (JBIDE-23212) move to tycho 1.0 (was 0.27.0) :: mvn clean verify checks old features versions against baseline
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23212?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-23212:
-------------------------------
Fix Version/s: 4.4.3.Final
(was: 4.4.3.AM2)
> move to tycho 1.0 (was 0.27.0) :: mvn clean verify checks old features versions against baseline
> ------------------------------------------------------------------------------------------------
>
> Key: JBIDE-23212
> URL: https://issues.jboss.org/browse/JBIDE-23212
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Affects Versions: 4.4.1.Final
> Reporter: Jeff MAURY
> Assignee: Nick Boldt
> Labels: build, tycho
> Fix For: 4.4.3.Final
>
>
> The check with baseline seems broken to me as it does not seem to work with features. When feature.source is checked, the baseline artifact (feature.source.jar) is compared to the wrong artifact (feature.jar).
> I reproduced the problem by updating jbosstool-central root POM (only the parent POM version has been changed) and the mvn verify build failed on org.jboss.tools.maven.feature. The output can be seen in one of the PR check
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (JBDS-4257) rh-eclipse46-devstudio provides packages that are dependencies of rh-eclipse46
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4257?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-4257:
-----------------------------
Fix Version/s: 10.3.0.GA
> rh-eclipse46-devstudio provides packages that are dependencies of rh-eclipse46
> ------------------------------------------------------------------------------
>
> Key: JBDS-4257
> URL: https://issues.jboss.org/browse/JBDS-4257
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: build, rpm
> Affects Versions: 10.3.0.AM2
> Environment: RHEL7
> Reporter: Lukáš Valach
> Assignee: Nick Boldt
> Priority: Minor
> Fix For: 10.3.0.GA
>
> Attachments: rh-eclipse46-devstudio_provides.txt, rh-eclipse46_provides.txt, yum_install_rh-eclipse46.png
>
>
> I noticed rh-eclipse46-devstudio is installed as dependenci when installing rh-eclipse46.
> !yum_install_rh-eclipse46.png|thumbnail!
> [~vkadlcik] said that it is because rh-eclipse46-devstudio offers some package which rh-eclipse46 needs, so yum decides to use devstudio as library.
> He said that the best practice for end-user application like rh-eclipse46-devstudio is to have less amount of stuff in "rpm -q --provides". Rh-eclipse46 provides 4 packages, devstudio provides 539 packages.
> [^rh-eclipse46_provides.txt]
> [^rh-eclipse46-devstudio_provides.txt]
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (JBDS-4257) rh-eclipse46-devstudio provides packages that are dependencies of rh-eclipse46
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4257?page=com.atlassian.jira.plugin.... ]
Nick Boldt edited comment on JBDS-4257 at 1/30/17 4:32 PM:
-----------------------------------------------------------
[~vkadlcik] Currently the RPM only installs two features:
* com.jboss.devstudio.core.rpm.feature
* com.jboss.devstudio.core.capabilities.feature
But these drag in all the dependencies they need to complete the installation, including com.google.guava.
I tried to remove/blacklist that plugin, but seemed that org.eclipse.m2e needed it (JBDS-4131); however, now that we depend on the org.eclipse.m2e RPM instead of the stuff in the devstudio update site, perhaps we can remove this too. https://github.com/jbdevstudio/jbdevstudio-product/pull/443
I've moved some more p2 deps out of the rpm (as they're now provided by RPM deps):
https://github.com/jbdevstudio/jbdevstudio-product/commit/1d53969a727011d... (order of listed IUs fixed to be in alpha order so the diff looks larger than it might otherwise be)
was (Author: nickboldt):
[~vkadlcik] Currently the RPM only installs two features:
* com.jboss.devstudio.core.rpm.feature
* com.jboss.devstudio.core.capabilities.feature
But these drag in all the dependencies they need to complete the installation, including com.google.guava.
I tried to remove/blacklist that plugin, but seemed that org.eclipse.m2e needed it (JBDS-4131); however, now that we depend on the org.eclipse.m2e RPM instead of the stuff in the devstudio update site, perhaps we can remove this too. https://github.com/jbdevstudio/jbdevstudio-product/pull/443
How can I easily determine which requirements for devstudio have already been met by installed rpms? Or migrate p2 dependencies to rpm dependencies?
> rh-eclipse46-devstudio provides packages that are dependencies of rh-eclipse46
> ------------------------------------------------------------------------------
>
> Key: JBDS-4257
> URL: https://issues.jboss.org/browse/JBDS-4257
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: build, rpm
> Affects Versions: 10.3.0.AM2
> Environment: RHEL7
> Reporter: Lukáš Valach
> Assignee: Nick Boldt
> Priority: Minor
> Fix For: 10.3.0.GA
>
> Attachments: rh-eclipse46-devstudio_provides.txt, rh-eclipse46_provides.txt, yum_install_rh-eclipse46.png
>
>
> I noticed rh-eclipse46-devstudio is installed as dependenci when installing rh-eclipse46.
> !yum_install_rh-eclipse46.png|thumbnail!
> [~vkadlcik] said that it is because rh-eclipse46-devstudio offers some package which rh-eclipse46 needs, so yum decides to use devstudio as library.
> He said that the best practice for end-user application like rh-eclipse46-devstudio is to have less amount of stuff in "rpm -q --provides". Rh-eclipse46 provides 4 packages, devstudio provides 539 packages.
> [^rh-eclipse46_provides.txt]
> [^rh-eclipse46-devstudio_provides.txt]
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (JBDS-4257) rh-eclipse46-devstudio provides packages that are dependencies of rh-eclipse46
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4257?page=com.atlassian.jira.plugin.... ]
Nick Boldt commented on JBDS-4257:
----------------------------------
[~vkadlcik] Currently the RPM only installs two features:
* com.jboss.devstudio.core.rpm.feature
* com.jboss.devstudio.core.capabilities.feature
But these drag in all the dependencies they need to complete the installation, including com.google.guava.
I tried to remove/blacklist that plugin, but seemed that org.eclipse.m2e needed it (JBDS-4131); however, now that we depend on the org.eclipse.m2e RPM instead of the stuff in the devstudio update site, perhaps we can remove this too. https://github.com/jbdevstudio/jbdevstudio-product/pull/443
How can I easily determine which requirements for devstudio have already been met by installed rpms? Or migrate p2 dependencies to rpm dependencies?
> rh-eclipse46-devstudio provides packages that are dependencies of rh-eclipse46
> ------------------------------------------------------------------------------
>
> Key: JBDS-4257
> URL: https://issues.jboss.org/browse/JBDS-4257
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: build, rpm
> Affects Versions: 10.3.0.AM2
> Environment: RHEL7
> Reporter: Lukáš Valach
> Assignee: Nick Boldt
> Priority: Minor
> Attachments: rh-eclipse46-devstudio_provides.txt, rh-eclipse46_provides.txt, yum_install_rh-eclipse46.png
>
>
> I noticed rh-eclipse46-devstudio is installed as dependenci when installing rh-eclipse46.
> !yum_install_rh-eclipse46.png|thumbnail!
> [~vkadlcik] said that it is because rh-eclipse46-devstudio offers some package which rh-eclipse46 needs, so yum decides to use devstudio as library.
> He said that the best practice for end-user application like rh-eclipse46-devstudio is to have less amount of stuff in "rpm -q --provides". Rh-eclipse46 provides 4 packages, devstudio provides 539 packages.
> [^rh-eclipse46_provides.txt]
> [^rh-eclipse46-devstudio_provides.txt]
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (JBDS-4175) NPE/broken functionality/cannot start after install from Red Hat Central into rh-eclipse46-devstudio
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4175?page=com.atlassian.jira.plugin.... ]
Nick Boldt commented on JBDS-4175:
----------------------------------
With the latest CI build, I can no longer reproduce the javax.annotation problem. javax.servlet problem CAN be reproduced.
Explanation:
in https://devstudio.redhat.com/targetplatforms/jbdevstudiotarget/4.62.0.AM1... -> content.xml, we have:
{code}
<unit id='org.eclipse.wst.server.preview' version='1.1.400.v201606081655'>
<update id='org.eclipse.wst.server.preview' range='[0.0.0,1.1.400.v201606081655)' severity='0'/>
...
<requires size='9'>
...
<required namespace='osgi.bundle' name='javax.servlet' range='[2.6.0,4.0.0)'/>{code}
So, we need to get this fixed in upstream wtp: https://bugs.eclipse.org/bugs/show_bug.cgi?id=464221 -> http://git.eclipse.org/c/servertools/webtools.servertools.git/tree/plugin...
> NPE/broken functionality/cannot start after install from Red Hat Central into rh-eclipse46-devstudio
> ----------------------------------------------------------------------------------------------------
>
> Key: JBDS-4175
> URL: https://issues.jboss.org/browse/JBDS-4175
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: central-update, rpm
> Environment: RHEL 7.2 with RHSCL repositories available:
> * RHSCL 2.3 RC (http://download-node-02.eng.bos.redhat.com/rel-eng/RHSCL-2.3-RHEL-7-RC-1....)
> * update for RHBZ#1392095 (http://nest.test.redhat.com/mnt/qa/scratch/vkadlcik/eclipse/repos/rhscl23...)
> Reporter: Václav Kadlčík
> Assignee: Nick Boldt
> Fix For: 10.3.0.AM2
>
> Attachments: JBDS-4175_logs_first_half.tar.gz, devstudio-is-major-feature-groups-to-test.png, install-all-the-categorized-features.png, install-integration-stack-441cr1.png, install-springide383-correctly.png, install-springide383-create-mvc-project-done.png, install-springide383-create-mvc-project.png, integration-stack-install-everything-some-deps-are-old-neon.1-versions.png, integration-stack-install-everything-some-deps-are-old-neon.1-versions_option2.png, rh-eclipse46-devstudio10.2.log.20161115-0953.txt, rh-eclipse46-devstudio10.2.log.20161118-1112_strict.txt, slf4j-error.txt, spring-ide-fail-aop.png, spring-ide-fail-list.png, spring-ide-fail-npe.png, spring-ide-fail-project-explorer-broken-package-explorer-OK.png, spring-ide-fail.png, spring-ide-view-fail.png, springide382.png, sw_to_install.txt, workspace.log, wst.xsd.core_diff.png
>
>
> I installed rh-eclipse46-devstudio-10.2-0.20161111.0219.el7.x86_64.rpm and followed Nick's scenario [1]. In Red Hat Central, I clicked "Select All" (it found 36 items), then "Install/Update", did all the confirmations, including a restart. After the restart, Eclipse died on java.lang.NullPointerException. I'm attaching the workspace log (aside from the NPE, it's full of "Could not resolve module").
> I reproduced the problem several times on two different machines. The update for RHBZ#1392095 (rh-eclipse46-eclipse-4.6.1-2.4.el7) isn't necessary, it just makes the reproduction much faster.
> Not sure how related it is, but rh-eclipse46 disallows updating packages installed from RPM [2]. But in the list of software to be installed/updated, I saw, among others, EGit and Mylyn, which are definitely included in rh-eclipse46-base. In any case, I'm attaching the list, too.
> [1] https://bugzilla.redhat.com/show_bug.cgi?id=1392095#c6
> [2] https://bugzilla.redhat.com/show_bug.cgi?id=1173024
> (copied from comment below to make it sticky)
> Results of installing first half of the items in Central:
> ||Item||Result||Description or Errors||
> |Android_Development_Tools|(/)||
> |JBoss_Hybrid_Mobile_Tools|(/)||
> |AngularJS_for_Web_Tools|(x)|IllegalStateException: BundleContext, NullPointerException|
> |JBoss_Arquillian_Tools|(/)||
> |JBoss_Forge_Tools|(/)||
> |JBoss_OpenShift_2_Tools|(x)|BundleException|
> |JBoss_OpenShift_3_Tools|(x)|BundleException|
> |JBoss_Portlet_Tools|(x)|BundleException, NullPointerException, eclipse didn't start|
> |JBoss_Seam_Tools|(x)|BundleException, NullPointerException, eclipse didn't start|
> |JBoss_Tools_LiveReload|(x)|BundleException|
> |JST_Server|(x)|BundleException|
> |Spring_IDE|(x)|BundleException, NullPointerException, eclipse didn't start|
> |Atlassian_Connector|(x)|BundleException, loader constraint violation|
> |Eclipse_EGit_Mylyn_Support|(x)|BundleException|
> |Subclipse_SVNKit|(/)|First attempt failed due to SocketTimeoutException but second passed|
> |Subclipse_SVNKit_Mylyn_Support|(x)|BundleException|
> |Eclipse_Checkstyle|(x)|NullPointerException|
> All logs [^JBDS-4175_logs_first_half.tar.gz].
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (JBTIS-1031) Fuse - Fix 'DeploymentTest'
by Tomáš Sedmík (JIRA)
Tomáš Sedmík created JBTIS-1031:
-----------------------------------
Summary: Fuse - Fix 'DeploymentTest'
Key: JBTIS-1031
URL: https://issues.jboss.org/browse/JBTIS-1031
Project: JBoss Tools Integration Stack
Issue Type: Task
Components: Fuse IDE, QE
Environment: DevStudio-IS 10.1.0.CR1
Reporter: Tomáš Sedmík
Assignee: Tomáš Sedmík
Priority: Critical
Attachments: prompt.png
Add handle for the prompt in the attachment (it appears if you want to remove a bundle from a server)
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (JBIDE-23422) Server Adapter: Node.js debug session is terminated after ~1 minute and browser shows 502 error
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23422?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-23422:
------------------------------------------
[~ibuziuk] looking at the debugging code that we have it's not all obvious to me how the connection is built. Is it possible for us to get a hold of the connection and use it to send keepalives?
> Server Adapter: Node.js debug session is terminated after ~1 minute and browser shows 502 error
> -----------------------------------------------------------------------------------------------
>
> Key: JBIDE-23422
> URL: https://issues.jboss.org/browse/JBIDE-23422
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: javascript, openshift
> Affects Versions: 4.4.2.AM2
> Environment: windows 10
> Fedora 24
> Reporter: Ilya Buziuk
> Assignee: Jeff MAURY
> Priority: Critical
> Labels: nodejs, openshift_v3, server_adapter
> Fix For: 4.4.3.Final
>
>
> We've found, that when one is debugging (the code is stopeed at breakpoint, stepping through code, inspecting variables, ...) longer than ~1 minute, browser displays error code 502 and the debug session gets terminated. This makes this feature not very useful, because all debugging must be quicker than that timeout.
> The behavior is captured in this screencast: https://youtu.be/BJf7wcPqNmM (note how at the time 0:42 the page is finally loaded (502 error) and the debug session is terminated (in debug view)).
> We were able to reproduce this issue on F24 and Win10 (using CDK and console.engint.openshift.com)
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months