[JBoss JIRA] (JBDS-4847) devstudio.product_master job is failing on dependencies
by Josef Kopriva (Jira)
[ https://issues.redhat.com/browse/JBDS-4847?page=com.atlassian.jira.plugin... ]
Josef Kopriva closed JBDS-4847.
-------------------------------
Closing: build is back to green.
> devstudio.product_master job is failing on dependencies
> -------------------------------------------------------
>
> Key: JBDS-4847
> URL: https://issues.redhat.com/browse/JBDS-4847
> Project: Red Hat CodeReady Studio (devstudio)
> Issue Type: Bug
> Components: build
> Affects Versions: 12.16.0.AM1
> Reporter: Josef Kopriva
> Assignee: Stephane Bouchet
> Priority: Blocker
> Fix For: 12.16.0.AM1
>
>
> https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud...
> {code:java}
> 08:43:26 [ERROR] Cannot resolve project dependencies:
> 08:43:26 [ERROR] Software being installed: com.jboss.devstudio.core.feature.feature.group 12.16.0.qualifier
> 08:43:26 [ERROR] Missing requirement: com.jboss.devstudio.core.feature.feature.group 12.16.0.qualifier requires 'org.eclipse.equinox.p2.iu; org.eclipse.wst.jsdt.nodejs.feature.feature.group 0.0.0' but it could not be found
> 08:43:26 [ERROR]
> 08:43:26 [ERROR] See http://wiki.eclipse.org/Tycho/Dependency_Resolution_Troubleshooting for help.
> 08:43:26 [ERROR] Cannot resolve dependencies of MavenProject: com.jboss.devstudio.core.features:com.jboss.devstudio.core.feature:12.16.0-SNAPSHOT @ /mnt/hudson_workspace/workspace/devstudio.product_master/sources/product/features/com.jboss.devstudio.core.feature/pom.xml: See log for details -> [Help 1]
> 08:43:26 org.apache.maven.MavenExecutionException: Cannot resolve dependencies of MavenProject: com.jboss.devstudio.core.features:com.jboss.devstudio.core.feature:12.16.0-SNAPSHOT @ /mnt/hudson_workspace/workspace/devstudio.product_master/sources/product/features/com.jboss.devstudio.core.feature/pom.xml
> 08:43:26 at org.eclipse.tycho.core.maven.TychoMavenLifecycleParticipant.afterProjectsRead (TychoMavenLifecycleParticipant.java:100)
> 08:43:26 at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:267)
> 08:43:26 at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:194)
> 08:43:26 at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:107)
> 08:43:26 at org.apache.maven.cli.MavenCli.execute (MavenCli.java:955)
> 08:43:26 at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:290)
> 08:43:26 at org.apache.maven.cli.MavenCli.main (MavenCli.java:194)
> 08:43:26 at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
> 08:43:26 at sun.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:62)
> 08:43:26 at sun.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:43)
> 08:43:26 at java.lang.reflect.Method.invoke (Method.java:498)
> 08:43:26 at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced (Launcher.java:289)
> 08:43:26 at org.codehaus.plexus.classworlds.launcher.Launcher.launch (Launcher.java:229)
> 08:43:26 at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode (Launcher.java:415)
> 08:43:26 at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:356)
> 08:43:26 Caused by: org.eclipse.tycho.artifacts.DependencyResolutionException: Cannot resolve dependencies of MavenProject: com.jboss.devstudio.core.features:com.jboss.devstudio.core.feature:12.16.0-SNAPSHOT @ /mnt/hudson_workspace/workspace/devstudio.product_master/sources/product/features/com.jboss.devstudio.core.feature/pom.xml
> 08:43:26 at org.eclipse.tycho.p2.resolver.P2ResolverImpl.resolveDependencies (P2ResolverImpl.java:244)
> 08:43:26 at org.eclipse.tycho.p2.resolver.P2ResolverImpl.resolveTargetDependencies (P2ResolverImpl.java:124)
> 08:43:26 at org.eclipse.tycho.p2.resolver.P2DependencyResolver.doResolveDependencies (P2DependencyResolver.java:368)
> 08:43:26 at org.eclipse.tycho.p2.resolver.P2DependencyResolver.resolveDependencies (P2DependencyResolver.java:336)
> 08:43:26 at org.eclipse.tycho.core.resolver.DefaultTychoResolver.resolveProject (DefaultTychoResolver.java:134)
> 08:43:26 at org.eclipse.tycho.core.maven.TychoMavenLifecycleParticipant.afterProjectsRead (TychoMavenLifecycleParticipant.java:95)
> 08:43:26 at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:267)
> 08:43:26 at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:194)
> 08:43:26 at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:107)
> 08:43:26 at org.apache.maven.cli.MavenCli.execute (MavenCli.java:955)
> 08:43:26 at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:290)
> 08:43:26 at org.apache.maven.cli.MavenCli.main (MavenCli.java:194)
> 08:43:26 at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
> 08:43:26 at sun.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:62)
> 08:43:26 at sun.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:43)
> 08:43:26 at java.lang.reflect.Method.invoke (Method.java:498)
> 08:43:26 at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced (Launcher.java:289)
> 08:43:26 at org.codehaus.plexus.classworlds.launcher.Launcher.launch (Launcher.java:229)
> 08:43:26 at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode (Launcher.java:415)
> 08:43:26 at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:356)
> 08:43:26 Caused by: org.eclipse.tycho.p2.util.resolution.ResolverException: See log for details
> 08:43:26 at org.eclipse.tycho.p2.util.resolution.ProjectorResolutionStrategy.resolve (ProjectorResolutionStrategy.java:88)
> 08:43:26 at org.eclipse.tycho.p2.util.resolution.AbstractResolutionStrategy.resolve (AbstractResolutionStrategy.java:42)
> 08:43:26 at org.eclipse.tycho.p2.resolver.P2ResolverImpl.resolveDependencies (P2ResolverImpl.java:237)
> 08:43:26 at org.eclipse.tycho.p2.resolver.P2ResolverImpl.resolveTargetDependencies (P2ResolverImpl.java:124)
> 08:43:26 at org.eclipse.tycho.p2.resolver.P2DependencyResolver.doResolveDependencies (P2DependencyResolver.java:368)
> 08:43:26 at org.eclipse.tycho.p2.resolver.P2DependencyResolver.resolveDependencies (P2DependencyResolver.java:336)
> 08:43:26 at org.eclipse.tycho.core.resolver.DefaultTychoResolver.resolveProject (DefaultTychoResolver.java:134)
> 08:43:26 at org.eclipse.tycho.core.maven.TychoMavenLifecycleParticipant.afterProjectsRead (TychoMavenLifecycleParticipant.java:95)
> 08:43:26 at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:267)
> 08:43:26 at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:194)
> 08:43:26 at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:107)
> 08:43:26 at org.apache.maven.cli.MavenCli.execute (MavenCli.java:955)
> 08:43:26 at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:290)
> 08:43:26 at org.apache.maven.cli.MavenCli.main (MavenCli.java:194)
> 08:43:26 at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
> 08:43:26 at sun.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:62)
> 08:43:26 at sun.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:43)
> 08:43:26 at java.lang.reflect.Method.invoke (Method.java:498)
> 08:43:26 at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced (Launcher.java:289)
> 08:43:26 at org.codehaus.plexus.classworlds.launcher.Launcher.launch (Launcher.java:229)
> 08:43:26 at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode (Launcher.java:415)
> 08:43:26 at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:356)
> 08:43:26 [ERROR]
> 08:43:26 [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> 08:43:26 [ERROR]
> 08:43:26 [ERROR] For more information about the errors and possible solutions, please read the following articles:
> 08:43:26 [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MavenExecutionException
> 08:43:26 Build step 'Invoke top-level Maven targets' marked build as failure
> 08:43:27 [description-setter] Description set:
> 08:43:27 Sending e-mails to: jboss-devstudio-builds-list(a)redhat.com jmaury(a)redhat.com
> 08:43:33 Started calculate disk usage of build
> 08:43:33 Finished Calculation of disk usage of build in 0 seconds
> 08:43:33 Started calculate disk usage of workspace
> 08:43:33 Finished Calculation of disk usage of workspace in 0 seconds
> 08:43:33 Finished: FAILURE
> {code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 9 months
[JBoss JIRA] (JBIDE-27317) Deprecate Android Development Tools
by Stephane Bouchet (Jira)
[ https://issues.redhat.com/browse/JBIDE-27317?page=com.atlassian.jira.plug... ]
Stephane Bouchet commented on JBIDE-27317:
------------------------------------------
First, we'll mark it as deprecated in the central listing for 4.16.0.Final
Then we'll remove it on future versions totally.
see what we did for JST/VPE : JBIDE-26987
we should also add doc team to publish a note? CC: [~supriya.bharadwaj]
> Deprecate Android Development Tools
> -----------------------------------
>
> Key: JBIDE-27317
> URL: https://issues.redhat.com/browse/JBIDE-27317
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Affects Versions: 4.16.0.AM1
> Reporter: Josef Kopriva
> Assignee: Stephane Bouchet
> Priority: Major
> Fix For: 4.16.0.Final
>
>
> After discussion on slack, we should deprecate ADT:
> {code:java}
> @jmaury @sbouchet @psrna @bodavis Hi, I was looking at Android Develpment tools(we have it in CRS Central), but it seems to be it is not supported by Google for some time: https://android-developers.googleblog.com/2016/11/support-ended-for-eclip...
> Bob Davis 3:06 PM
> If it’s not supported/maintained, we should remove it, IMO
> Stéphane Bouchet 3:16 PM
> Currently it is listed on central, as tested, not deprecated.
> as we did for last codeready release, we should first deprecate it before removing it from central. (edited)
> Bob Davis 3:18 PM
> Agreed - if that’s the process, we should do that. It’s been deprecated by the upstream, so we should follow suit. Is there a replacement we can direct people to? (should we worry about that? I can try to see if we have any stats on usage)
> Stéphane Bouchet 3:19 PM
> Err, yes, the replacement is to use Android Studio, based on IDEA :smile:
> Bob Davis 3:20 PM
> Sigh…
> Stéphane Bouchet 3:22 PM
> yes, there was an alternative on eclipse, https://projects.eclipse.org/projects/tools.andmore, but no new release since 2017 :disappointed:
> 3:23
> @maxandersen is listed on the contributors. maybe he can add a note ?
> Bob Davis 3:36 PM
> Isn’t @maxandersen listed as a contributor on most anything a person would want to use?
> :joy:
> 1
> Max Rydahl Andersen 5:39 PM
> I only do useful stuff :)
> 5:40
> Andorid on eclipse is dead.
> {code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 9 months
[JBoss JIRA] (JBIDE-26970) Validator: The annotation @PathParam must define the attribute value
by Jeff MAURY (Jira)
[ https://issues.redhat.com/browse/JBIDE-26970?page=com.atlassian.jira.plug... ]
Jeff MAURY updated JBIDE-26970:
-------------------------------
Sprint: devex #186 July 2020
> Validator: The annotation @PathParam must define the attribute value
> --------------------------------------------------------------------
>
> Key: JBIDE-26970
> URL: https://issues.redhat.com/browse/JBIDE-26970
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: webservices
> Affects Versions: 4.13.0.Final
> Reporter: nimo stephan
> Assignee: Jeff MAURY
> Priority: Major
> Fix For: 4.16.0.AM1
>
> Attachments: jax-rs-validator.png
>
>
> According to https://developer.jboss.org/en/resteasy/blog/2018/05/29/new-blog, I can define a resource with
> {code:java}
> public String hello(@PathParam String name) {
> ..
> }
> {code}
> instead of
> {code:java}
> public String hello(@PathParam(value="name") String name) {
> ..
> }
> {code}
> when setting the following in pom.xml:
> {code:java}
> <maven.compiler.parameters>true</maven.compiler.parameters>
> {code}
> However, jboss tools validator complains about it as a validator error:
> {code:java}
> The annotation @PathParam must define the attribute value")
> {code}
> and compilation fails.
> So I tried to disable some validators according to JbossPath-Params (see attachement).
> However, the error is still shown in my editor by the validator.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 9 months
[JBoss JIRA] (JBIDE-27317) Deprecate Android Development Tools
by Jeff MAURY (Jira)
[ https://issues.redhat.com/browse/JBIDE-27317?page=com.atlassian.jira.plug... ]
Jeff MAURY updated JBIDE-27317:
-------------------------------
Sprint: devex #186 July 2020
> Deprecate Android Development Tools
> -----------------------------------
>
> Key: JBIDE-27317
> URL: https://issues.redhat.com/browse/JBIDE-27317
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Affects Versions: 4.16.0.AM1
> Reporter: Josef Kopriva
> Assignee: Stephane Bouchet
> Priority: Major
> Fix For: 4.16.0.Final
>
>
> After discussion on slack, we should deprecate ADT:
> {code:java}
> @jmaury @sbouchet @psrna @bodavis Hi, I was looking at Android Develpment tools(we have it in CRS Central), but it seems to be it is not supported by Google for some time: https://android-developers.googleblog.com/2016/11/support-ended-for-eclip...
> Bob Davis 3:06 PM
> If it’s not supported/maintained, we should remove it, IMO
> Stéphane Bouchet 3:16 PM
> Currently it is listed on central, as tested, not deprecated.
> as we did for last codeready release, we should first deprecate it before removing it from central. (edited)
> Bob Davis 3:18 PM
> Agreed - if that’s the process, we should do that. It’s been deprecated by the upstream, so we should follow suit. Is there a replacement we can direct people to? (should we worry about that? I can try to see if we have any stats on usage)
> Stéphane Bouchet 3:19 PM
> Err, yes, the replacement is to use Android Studio, based on IDEA :smile:
> Bob Davis 3:20 PM
> Sigh…
> Stéphane Bouchet 3:22 PM
> yes, there was an alternative on eclipse, https://projects.eclipse.org/projects/tools.andmore, but no new release since 2017 :disappointed:
> 3:23
> @maxandersen is listed on the contributors. maybe he can add a note ?
> Bob Davis 3:36 PM
> Isn’t @maxandersen listed as a contributor on most anything a person would want to use?
> :joy:
> 1
> Max Rydahl Andersen 5:39 PM
> I only do useful stuff :)
> 5:40
> Andorid on eclipse is dead.
> {code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 9 months
[JBoss JIRA] (JBIDE-27317) Deprecate Android Development Tools
by Stephane Bouchet (Jira)
[ https://issues.redhat.com/browse/JBIDE-27317?page=com.atlassian.jira.plug... ]
Stephane Bouchet updated JBIDE-27317:
-------------------------------------
Fix Version/s: 4.16.0.Final
> Deprecate Android Development Tools
> -----------------------------------
>
> Key: JBIDE-27317
> URL: https://issues.redhat.com/browse/JBIDE-27317
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Affects Versions: 4.16.0.AM1
> Reporter: Josef Kopriva
> Assignee: Stephane Bouchet
> Priority: Major
> Fix For: 4.16.0.Final
>
>
> After discussion on slack, we should deprecate ADT:
> {code:java}
> @jmaury @sbouchet @psrna @bodavis Hi, I was looking at Android Develpment tools(we have it in CRS Central), but it seems to be it is not supported by Google for some time: https://android-developers.googleblog.com/2016/11/support-ended-for-eclip...
> Bob Davis 3:06 PM
> If it’s not supported/maintained, we should remove it, IMO
> Stéphane Bouchet 3:16 PM
> Currently it is listed on central, as tested, not deprecated.
> as we did for last codeready release, we should first deprecate it before removing it from central. (edited)
> Bob Davis 3:18 PM
> Agreed - if that’s the process, we should do that. It’s been deprecated by the upstream, so we should follow suit. Is there a replacement we can direct people to? (should we worry about that? I can try to see if we have any stats on usage)
> Stéphane Bouchet 3:19 PM
> Err, yes, the replacement is to use Android Studio, based on IDEA :smile:
> Bob Davis 3:20 PM
> Sigh…
> Stéphane Bouchet 3:22 PM
> yes, there was an alternative on eclipse, https://projects.eclipse.org/projects/tools.andmore, but no new release since 2017 :disappointed:
> 3:23
> @maxandersen is listed on the contributors. maybe he can add a note ?
> Bob Davis 3:36 PM
> Isn’t @maxandersen listed as a contributor on most anything a person would want to use?
> :joy:
> 1
> Max Rydahl Andersen 5:39 PM
> I only do useful stuff :)
> 5:40
> Andorid on eclipse is dead.
> {code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 9 months
[JBoss JIRA] (JBIDE-27309) Job jbosstools-install-p2director.install-tests.matrix_master is failing
by Stephane Bouchet (Jira)
[ https://issues.redhat.com/browse/JBIDE-27309?page=com.atlassian.jira.plug... ]
Stephane Bouchet resolved JBIDE-27309.
--------------------------------------
Resolution: Done
build back to normal (green)
> Job jbosstools-install-p2director.install-tests.matrix_master is failing
> ------------------------------------------------------------------------
>
> Key: JBIDE-27309
> URL: https://issues.redhat.com/browse/JBIDE-27309
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Affects Versions: 4.16.0.AM1
> Reporter: Josef Kopriva
> Assignee: Stephane Bouchet
> Priority: Major
> Fix For: 4.16.0.AM1
>
>
> Job is failing for configuration:
> * [jbosstools,central,openjdk-1.8,rhel7-devstudio-releng|https://dev-platfor...]
> With error message in log:
> {code:java}
> 09:14:15 [ERROR] INSTALL FAILED
> 09:14:15
> 09:14:15 [p2.dir] Installing tern-server-nodejs-feature.feature.group 1.3.0.201803012316.
> 09:14:15 [p2.dir] Cannot complete the install because of a conflicting dependency.
> 09:14:15 [p2.dir] Software being installed: Eclipse PDE Plug-in Developer Resources 3.14.300.v20200305-0155 (org.eclipse.pde.source.feature.group 3.14.300.v20200305-0155)
> 09:14:15 [p2.dir] Software currently installed: Eclipse SDK 4.16.0.I20200427-1800 (org.eclipse.sdk.ide 4.16.0.I20200427-1800)
> 09:14:15 [p2.dir] Only one of the following can be installed at once:
> 09:14:15 [p2.dir] Eclipse PDE Plug-in Developer Resources 3.14.300.v20200305-0155 (org.eclipse.pde.source.feature.jar 3.14.300.v20200305-0155)
> 09:14:15 [p2.dir] Eclipse PDE Plug-in Developer Resources 3.14.400.v20200427-1800 (org.eclipse.pde.source.feature.jar 3.14.400.v20200427-1800)
> 09:14:15 --
> 09:14:15 [p2.dir] !ENTRY org.eclipse.equinox.p2.director 4 10054 2020-06-04 03:14:13.475
> 09:14:15 [p2.dir] !MESSAGE Cannot complete the install because of a conflicting dependency.
> 09:14:15 [p2.dir] !SUBENTRY 1 org.eclipse.equinox.p2.director 4 0 2020-06-04 03:14:13.475
> 09:14:15 [p2.dir] !MESSAGE Software being installed: Eclipse PDE Plug-in Developer Resources 3.14.300.v20200305-0155 (org.eclipse.pde.source.feature.group 3.14.300.v20200305-0155)
> 09:14:15 --
> 09:14:15 [p2.dir] !SUBENTRY 1 org.eclipse.equinox.p2.director 4 1 2020-06-04 03:14:13.475
> 09:14:15 [p2.dir] !MESSAGE Only one of the following can be installed at once:
> 09:14:15 [p2.dir] !SUBENTRY 2 org.eclipse.equinox.p2.director 4 0 2020-06-04 03:14:13.475
> 09:14:15 [p2.dir] !MESSAGE Eclipse PDE Plug-in Developer Resources 3.14.300.v20200305-0155 (org.eclipse.pde.source.feature.jar 3.14.300.v20200305-0155)
> 09:14:15 --
> 09:14:15 at org.eclipse.equinox.launcher.Main.main(Main.java:1420)
> 09:14:15 Caused by: /mnt/hudson_workspace/workspace/jbosstools-install-p2director.install-tests.matrix_master/92a2a6fc/director.xml:62: exec returned: 13
> 09:14:15 at org.apache.tools.ant.taskdefs.ExecTask.runExecute(ExecTask.java:645)
> 09:14:15 at org.apache.tools.ant.taskdefs.ExecTask.runExec(ExecTask.java:669)
> 09:14:15 --
> 09:14:15 Root exception:
> 09:14:15 /mnt/hudson_workspace/workspace/jbosstools-install-p2director.install-tests.matrix_master/92a2a6fc/director.xml:62: exec returned: 13
> 09:14:15 at org.apache.tools.ant.taskdefs.ExecTask.runExecute(ExecTask.java:645)
> 09:14:15 at org.apache.tools.ant.taskdefs.ExecTask.runExec(ExecTask.java:669)
> 09:14:15 --------------------------------
> {code}
> Full log: [https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/D...
>
>
>
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 9 months