[JBoss JIRA] (JBDS-4259) Could not resolve module: org.eclipse.recommenders
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4259?page=com.atlassian.jira.plugin.... ]
Nick Boldt commented on JBDS-4259:
----------------------------------
I removed guava because it appeared to not be needed anymore. But it does, so I've added it back.
https://github.com/jbdevstudio/jbdevstudio-product/commit/5f52ee8d03d2d78...
> Could not resolve module: org.eclipse.recommenders
> --------------------------------------------------
>
> Key: JBDS-4259
> URL: https://issues.jboss.org/browse/JBDS-4259
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: build, rpm
> Affects Versions: 10.3.0.GA
> Environment: RHEL7, RHSCL 2.4 alpha 1.0
> Reporter: Lukáš Valach
> Assignee: Nick Boldt
> Fix For: 10.3.0.GA
>
> Attachments: rh-eclipse46-devstudio10.3.log.20170131-1103.txt
>
>
> I got errors during start of Devstudio 10.3-0.20170131.0115.el7. There are errors like this:
> {code}
> org.osgi.framework.BundleException: Could not resolve module: org.eclipse.recommenders.apidocs.rcp [1085]
> Unresolved requirement: Import-Package: com.google.common.annotations; version="[15.0.0,16.0.0)"
> {code}
> Log: [^rh-eclipse46-devstudio10.3.log.20170131-1103.txt]
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (JBIDE-23816) Cannot run server itest module separately
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23816?page=com.atlassian.jira.plugi... ]
Martin Malina updated JBIDE-23816:
----------------------------------
Fix Version/s: 4.4.3.Final
> Cannot run server itest module separately
> -----------------------------------------
>
> Key: JBIDE-23816
> URL: https://issues.jboss.org/browse/JBIDE-23816
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, server
> Affects Versions: 4.4.3.AM2
> Reporter: Martin Malina
> Assignee: Martin Malina
> Fix For: 4.4.3.Final
>
>
> Now that the server tools bot tests have been moved from jbosstools-integration-tests github repo to jbosstools-server, I would like to find a way to run a specific test in the simplest way possible.
> The test bundle I want to run is this:
> as/itests/org.jboss.tools.as.ui.bot.itests [1]
> This is the kind of command that I would expect to work from the root directory of the git repo:
> {code}$ mvn clean verify -pl as/itests/org.jboss.tools.as.ui.bot.itests -am -Djbosstools.test.jboss-eap-7.x.md5=4973998216a8eb5b2f5a6fc00d84705c -Dswtbot.test.skip=false -Djbosstools.test.jboss-eap-7.x.home='${requirementsDirectory}/jboss-eap-7.1' -DskipRequirements=false -Djbosstools.test.jboss-eap-7.x.url=$EAP_URL -Dtest.profile=eap7x-compatibility -Dusage_reporting_enabled=false -U -DskipTests=false -PITests{code}
> This will fail:
> {code}
> [ERROR] Cannot resolve project dependencies:
> [ERROR] Software being installed: org.jboss.tools.as.ui.bot.itests 3.2.3.qualifier
> [ERROR] Missing requirement: org.jboss.tools.as.ui.bot.itests 3.2.3.qualifier requires 'bundle org.jboss.ide.eclipse.as.reddeer
> {code}
> I was under the impression that using "-pl -am" with maven will ensure that all the deps from the maven project are added to the build, but it seems this does not work for dependencies defined in Manifest.MF file of the bundle?
> What options do we have here? The simplest solution is to first build the whole repo and install it in the local maven repo, but I'd like to avoid that. Another option would be to add the whole jbosstools repo to the ITests profile in parent pom, but I'm guessing that not everybody would like that.
> Is there some other way?
> [1] https://github.com/jbosstools/jbosstools-server/tree/master/as/itests/org...
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (JBIDE-23816) Cannot run server itest module separately
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23816?page=com.atlassian.jira.plugi... ]
Martin Malina reassigned JBIDE-23816:
-------------------------------------
Assignee: Nick Boldt (was: Martin Malina)
[~nickboldt], any ideas?
> Cannot run server itest module separately
> -----------------------------------------
>
> Key: JBIDE-23816
> URL: https://issues.jboss.org/browse/JBIDE-23816
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, server
> Affects Versions: 4.4.3.AM2
> Reporter: Martin Malina
> Assignee: Nick Boldt
> Fix For: 4.4.3.Final
>
>
> Now that the server tools bot tests have been moved from jbosstools-integration-tests github repo to jbosstools-server, I would like to find a way to run a specific test in the simplest way possible.
> The test bundle I want to run is this:
> as/itests/org.jboss.tools.as.ui.bot.itests [1]
> This is the kind of command that I would expect to work from the root directory of the git repo:
> {code}$ mvn clean verify -pl as/itests/org.jboss.tools.as.ui.bot.itests -am -Djbosstools.test.jboss-eap-7.x.md5=4973998216a8eb5b2f5a6fc00d84705c -Dswtbot.test.skip=false -Djbosstools.test.jboss-eap-7.x.home='${requirementsDirectory}/jboss-eap-7.1' -DskipRequirements=false -Djbosstools.test.jboss-eap-7.x.url=$EAP_URL -Dtest.profile=eap7x-compatibility -Dusage_reporting_enabled=false -U -DskipTests=false -PITests{code}
> This will fail:
> {code}
> [ERROR] Cannot resolve project dependencies:
> [ERROR] Software being installed: org.jboss.tools.as.ui.bot.itests 3.2.3.qualifier
> [ERROR] Missing requirement: org.jboss.tools.as.ui.bot.itests 3.2.3.qualifier requires 'bundle org.jboss.ide.eclipse.as.reddeer
> {code}
> I was under the impression that using "-pl -am" with maven will ensure that all the deps from the maven project are added to the build, but it seems this does not work for dependencies defined in Manifest.MF file of the bundle?
> What options do we have here? The simplest solution is to first build the whole repo and install it in the local maven repo, but I'd like to avoid that. Another option would be to add the whole jbosstools repo to the ITests profile in parent pom, but I'm guessing that not everybody would like that.
> Is there some other way?
> [1] https://github.com/jbosstools/jbosstools-server/tree/master/as/itests/org...
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (JBIDE-23816) Cannot run server itest module separately
by Martin Malina (JIRA)
Martin Malina created JBIDE-23816:
-------------------------------------
Summary: Cannot run server itest module separately
Key: JBIDE-23816
URL: https://issues.jboss.org/browse/JBIDE-23816
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: build, server
Affects Versions: 4.4.3.AM2
Reporter: Martin Malina
Assignee: Martin Malina
Now that the server tools bot tests have been moved from jbosstools-integration-tests github repo to jbosstools-server, I would like to find a way to run a specific test in the simplest way possible.
The test bundle I want to run is this:
as/itests/org.jboss.tools.as.ui.bot.itests [1]
This is the kind of command that I would expect to work from the root directory of the git repo:
{code}$ mvn clean verify -pl as/itests/org.jboss.tools.as.ui.bot.itests -am -Djbosstools.test.jboss-eap-7.x.md5=4973998216a8eb5b2f5a6fc00d84705c -Dswtbot.test.skip=false -Djbosstools.test.jboss-eap-7.x.home='${requirementsDirectory}/jboss-eap-7.1' -DskipRequirements=false -Djbosstools.test.jboss-eap-7.x.url=$EAP_URL -Dtest.profile=eap7x-compatibility -Dusage_reporting_enabled=false -U -DskipTests=false -PITests{code}
This will fail:
{code}
[ERROR] Cannot resolve project dependencies:
[ERROR] Software being installed: org.jboss.tools.as.ui.bot.itests 3.2.3.qualifier
[ERROR] Missing requirement: org.jboss.tools.as.ui.bot.itests 3.2.3.qualifier requires 'bundle org.jboss.ide.eclipse.as.reddeer
{code}
I was under the impression that using "-pl -am" with maven will ensure that all the deps from the maven project are added to the build, but it seems this does not work for dependencies defined in Manifest.MF file of the bundle?
What options do we have here? The simplest solution is to first build the whole repo and install it in the local maven repo, but I'd like to avoid that. Another option would be to add the whole jbosstools repo to the ITests profile in parent pom, but I'm guessing that not everybody would like that.
Is there some other way?
[1] https://github.com/jbosstools/jbosstools-server/tree/master/as/itests/org...
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (JBIDE-23733) Merge .smoke and .nightly integration jobs into a single job and run them weekly
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23733?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-23733:
------------------------------------
Two questions re: DEVSTUDIO_VERSION variable.
a) Do you want the x.y.z version, qualified version, or fully-qualified version? 10.3.0, 10.3.0.GA, or 10.3.0.GA-20170221-1419-B79 ?
b) where in a job such as https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... are you actually USING this variable? Is it to replace the version in the URL in INSTALLER_URL, eg., http://www.qa.jboss.com/binaries/devstudio/10.0/snapshots/builds/devstudi... ?
c) depending on your answer for (a), can I suggest a different variable name? I've already been using variables for the devstudio version in my staging/promotion scripts/jobs and in other places, and I'd like to be consistent w/ what's used there and in the parent pom, too.
d) Why are you using a 10.2.0 build for these smoke tests? Why not use the 10.3.0 CI builds? here's the latest: http://www.qa.jboss.com/binaries/devstudio/10.0/snapshots/builds/devstudi...
> Merge .smoke and .nightly integration jobs into a single job and run them weekly
> --------------------------------------------------------------------------------
>
> Key: JBIDE-23733
> URL: https://issues.jboss.org/browse/JBIDE-23733
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, integration-tests
> Affects Versions: 4.4.3.AM1
> Reporter: Nick Boldt
> Assignee: Rastislav Wagner
> Fix For: 4.4.3.Final
>
>
> Purpose:
> a) easier maintenance of jobs / tests
> b) run fewer nightly jobs so that we don't block slaves from being available for other builds / tests
> c) more frequent full integration runs (rather than once per sprint, once per week)
> Tests to merge are in this view:
> https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud...
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (JBIDE-23733) Merge .smoke and .nightly integration jobs into a single job and run them weekly
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23733?page=com.atlassian.jira.plugi... ]
Nick Boldt edited comment on JBIDE-23733 at 1/31/17 10:24 AM:
--------------------------------------------------------------
Four questions re: DEVSTUDIO_VERSION variable.
a) Do you want the x.y.z version, qualified version, or fully-qualified version? 10.3.0, 10.3.0.GA, or 10.3.0.GA-20170221-1419-B79 ?
b) where in a job such as https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... are you actually USING this variable? Is it to replace the version in the URL in INSTALLER_URL, eg., http://www.qa.jboss.com/binaries/devstudio/10.0/snapshots/builds/devstudi... ?
c) depending on your answer for (a), can I suggest a different variable name? I've already been using variables for the devstudio version in my staging/promotion scripts/jobs and in other places, and I'd like to be consistent w/ what's used there and in the parent pom, too.
d) Why are you using a 10.2.0 build for these smoke tests? Why not use the 10.3.0 CI builds? here's the latest: http://www.qa.jboss.com/binaries/devstudio/10.0/snapshots/builds/devstudi...
was (Author: nickboldt):
Two questions re: DEVSTUDIO_VERSION variable.
a) Do you want the x.y.z version, qualified version, or fully-qualified version? 10.3.0, 10.3.0.GA, or 10.3.0.GA-20170221-1419-B79 ?
b) where in a job such as https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... are you actually USING this variable? Is it to replace the version in the URL in INSTALLER_URL, eg., http://www.qa.jboss.com/binaries/devstudio/10.0/snapshots/builds/devstudi... ?
c) depending on your answer for (a), can I suggest a different variable name? I've already been using variables for the devstudio version in my staging/promotion scripts/jobs and in other places, and I'd like to be consistent w/ what's used there and in the parent pom, too.
d) Why are you using a 10.2.0 build for these smoke tests? Why not use the 10.3.0 CI builds? here's the latest: http://www.qa.jboss.com/binaries/devstudio/10.0/snapshots/builds/devstudi...
> Merge .smoke and .nightly integration jobs into a single job and run them weekly
> --------------------------------------------------------------------------------
>
> Key: JBIDE-23733
> URL: https://issues.jboss.org/browse/JBIDE-23733
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, integration-tests
> Affects Versions: 4.4.3.AM1
> Reporter: Nick Boldt
> Assignee: Rastislav Wagner
> Fix For: 4.4.3.Final
>
>
> Purpose:
> a) easier maintenance of jobs / tests
> b) run fewer nightly jobs so that we don't block slaves from being available for other builds / tests
> c) more frequent full integration runs (rather than once per sprint, once per week)
> Tests to merge are in this view:
> https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud...
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (JBIDE-23761) ensure that latest x.y.3 AS, archives, & runtime test-framework plugins/features are added to the coretests site
by Lukáš Valach (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23761?page=com.atlassian.jira.plugi... ]
Lukáš Valach closed JBIDE-23761.
--------------------------------
Verified, closing.
> ensure that latest x.y.3 AS, archives, & runtime test-framework plugins/features are added to the coretests site
> ----------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-23761
> URL: https://issues.jboss.org/browse/JBIDE-23761
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, server, updatesite
> Affects Versions: 4.4.3.AM1
> Reporter: Nick Boldt
> Assignee: Rob Stryker
> Priority: Blocker
> Fix For: 4.4.3.AM2
>
>
> [7:30 AM] Pavol Srna: @RobStryker hi Rob, got a minute?
> [7:31 AM] Pavol Srna: @RobStryker wondering if the (as, runtime) test-framework can be made available e.g. here: http://download.jboss.org/jbosstools/neon/snapshots/updates/coretests/mas...
> [7:31 AM] Pavol Srna: what do you think?
> [7:34 AM] Pavol Srna: I don't see it in the org.jboss.ide.eclipse.as.test.feature on site, maybe needs a rebuild?
> [12:49 PM] Nick Boldt: if you want more test plugins/features in the coretests site... make sure they're part of the server site [1] and then PR me to add them to the coretests site [2].
> [1] http://download.jboss.org/jbosstools/neon/snapshots/builds/jbosstools-ser...
> [2] http://download.jboss.org/jbosstools/neon/snapshots/builds/jbosstools-bui...
> Submit PR against this:
> https://github.com/jbosstools/jbosstools-build-sites/blob/master/aggregat...
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (JBIDE-23389) OpenShift 3.4 support
by Radim Hopp (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23389?page=com.atlassian.jira.plugi... ]
Radim Hopp closed JBIDE-23389.
------------------------------
ITests are running fine with Devstudio 10.3.0.AM2 against openshift 3.4. Closing.
> OpenShift 3.4 support
> ---------------------
>
> Key: JBIDE-23389
> URL: https://issues.jboss.org/browse/JBIDE-23389
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Reporter: Alexey Kazakov
> Assignee: Jeff MAURY
> Priority: Critical
> Labels: new_and_noteworthy
> Fix For: 4.4.3.AM2
>
>
> OpenShift 3.4 is currently in progress but we need to start testing it now to see if we need adjust anything in our tools to support it.
> cc: [~adietish]
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months