[JBoss JIRA] (JBDS-4775) In Camel project errors thrown exposing Swagger API documentation.
by Jeff MAURY (Jira)
[ https://issues.jboss.org/browse/JBDS-4775?page=com.atlassian.jira.plugin.... ]
Jeff MAURY updated JBDS-4775:
-----------------------------
Fix Version/s: 12.x
> In Camel project errors thrown exposing Swagger API documentation.
> ------------------------------------------------------------------
>
> Key: JBDS-4775
> URL: https://issues.jboss.org/browse/JBDS-4775
> Project: Red Hat CodeReady Studio (devstudio)
> Issue Type: Bug
> Affects Versions: 12.11.0.GA
> Environment: Assuming this occurs in all environments.
> Reporter: Bruno Meseguer
> Priority: Major
> Fix For: 12.x
>
>
> ui experience:
> > user has little guidance on UI
> > no documentation available on how to expose Swagger info
> > misleading/not-functional options in UI (i.e. enableCORS checkbox)
> > textbox "port" (in Mac) user input goes backwards (yes, backwards!)
> > textbox "contextPath" (in Mac) user input goes backwards (yes, backwards!)
> result:
> > not possible from UI to expose Swagger info
> expected:
> > options available on UI to expose API definitions
> workaround:
> > manually add all necessary parameters:
> - add: contextPath="camel"
> - add: port="8080"
> - add: apiContextPath="api-docs"
> - add: <apiProperty key="cors" value="true"/>
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 9 months
[JBoss JIRA] (JBDS-4775) In Camel project errors thrown exposing Swagger API documentation.
by Jeff MAURY (Jira)
[ https://issues.jboss.org/browse/JBDS-4775?page=com.atlassian.jira.plugin.... ]
Jeff MAURY updated JBDS-4775:
-----------------------------
Component/s: fusetools
> In Camel project errors thrown exposing Swagger API documentation.
> ------------------------------------------------------------------
>
> Key: JBDS-4775
> URL: https://issues.jboss.org/browse/JBDS-4775
> Project: Red Hat CodeReady Studio (devstudio)
> Issue Type: Bug
> Components: fusetools
> Affects Versions: 12.11.0.GA
> Environment: Assuming this occurs in all environments.
> Reporter: Bruno Meseguer
> Priority: Major
> Fix For: 12.x
>
>
> ui experience:
> > user has little guidance on UI
> > no documentation available on how to expose Swagger info
> > misleading/not-functional options in UI (i.e. enableCORS checkbox)
> > textbox "port" (in Mac) user input goes backwards (yes, backwards!)
> > textbox "contextPath" (in Mac) user input goes backwards (yes, backwards!)
> result:
> > not possible from UI to expose Swagger info
> expected:
> > options available on UI to expose API definitions
> workaround:
> > manually add all necessary parameters:
> - add: contextPath="camel"
> - add: port="8080"
> - add: apiContextPath="api-docs"
> - add: <apiProperty key="cors" value="true"/>
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 9 months
[JBoss JIRA] (JBDS-4775) In Camel project errors thrown exposing Swagger API documentation.
by Jeff MAURY (Jira)
[ https://issues.jboss.org/browse/JBDS-4775?page=com.atlassian.jira.plugin.... ]
Jeff MAURY reassigned JBDS-4775:
--------------------------------
Assignee: Aurélien Pupier
> In Camel project errors thrown exposing Swagger API documentation.
> ------------------------------------------------------------------
>
> Key: JBDS-4775
> URL: https://issues.jboss.org/browse/JBDS-4775
> Project: Red Hat CodeReady Studio (devstudio)
> Issue Type: Bug
> Components: fusetools
> Affects Versions: 12.11.0.GA
> Environment: Assuming this occurs in all environments.
> Reporter: Bruno Meseguer
> Assignee: Aurélien Pupier
> Priority: Major
> Fix For: 12.x
>
>
> ui experience:
> > user has little guidance on UI
> > no documentation available on how to expose Swagger info
> > misleading/not-functional options in UI (i.e. enableCORS checkbox)
> > textbox "port" (in Mac) user input goes backwards (yes, backwards!)
> > textbox "contextPath" (in Mac) user input goes backwards (yes, backwards!)
> result:
> > not possible from UI to expose Swagger info
> expected:
> > options available on UI to expose API definitions
> workaround:
> > manually add all necessary parameters:
> - add: contextPath="camel"
> - add: port="8080"
> - add: apiContextPath="api-docs"
> - add: <apiProperty key="cors" value="true"/>
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 9 months
[JBoss JIRA] (JBIDE-26600) Cannot remove JSF capabilities from JSF project
by Ondrej Dockal (Jira)
[ https://issues.jboss.org/browse/JBIDE-26600?page=com.atlassian.jira.plugi... ]
Ondrej Dockal commented on JBIDE-26600:
---------------------------------------
[~jeffmaury] The issue is still there. Happens for EAP 7.1 (with execution env. java 1.8) and 7.2 runtimes (with java 11).
> Cannot remove JSF capabilities from JSF project
> -----------------------------------------------
>
> Key: JBIDE-26600
> URL: https://issues.jboss.org/browse/JBIDE-26600
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jsf
> Affects Versions: 4.11.0.Final
> Environment: Fedora 29, Java 11.0.2
> Reporter: Ondrej Dockal
> Assignee: Jeff MAURY
> Priority: Critical
> Fix For: 4.12.0.AM1
>
>
> Removing JSF capabilities introduces Command 'org.jboss.tools.jsf.ui.project.configure.disable' failed error.
> {code}
> eclipse.buildId=12.11.0.GA-v20190321-1925-B4244
> java.version=11.0.2
> java.vendor=Oracle Corporation
> BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US
> Framework arguments: -product com.jboss.devstudio.core.product
> Command-line arguments: -data file:/home/odockal/workspace_12110Ga-Staging/ -os linux -ws gtk -arch x86_64 -product com.jboss.devstudio.core.product
> org.eclipse.e4.ui.workbench
> Error
> Wed Mar 27 14:32:09 CET 2019
> Command 'org.jboss.tools.jsf.ui.project.configure.disable' failed
> org.eclipse.core.commands.ExecutionException: Error executing 'org.jboss.tools.jsf.ui.project.configure.disable': java.lang.NullPointerException
> at org.eclipse.e4.core.commands.internal.HandlerServiceHandler.execute(HandlerServiceHandler.java:170)
> at org.eclipse.core.commands.Command.executeWithChecks(Command.java:497)
> at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:490)
> at org.eclipse.e4.core.commands.internal.HandlerServiceImpl.executeHandler(HandlerServiceImpl.java:213)
> at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.executeItem(HandledContributionItem.java:438)
> at org.eclipse.e4.ui.workbench.renderers.swt.AbstractContributionItem.handleWidgetSelection(AbstractContributionItem.java:449)
> at org.eclipse.e4.ui.workbench.renderers.swt.AbstractContributionItem.lambda$2(AbstractContributionItem.java:475)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:89)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:5783)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1411)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:5051)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:4579)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$5.run(PartRenderingEngine.java:1173)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:338)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1062)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:155)
> at org.eclipse.ui.internal.Workbench.lambda$3(Workbench.java:644)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:338)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:566)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:155)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:203)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:137)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:107)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:400)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:255)
> at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflect.Method.invoke(Method.java:566)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:661)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:597)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1476)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1449)
> Caused by: org.eclipse.e4.core.di.InjectionException: java.lang.NullPointerException
> at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:68)
> at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:320)
> at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:254)
> at org.eclipse.e4.core.contexts.ContextInjectionFactory.invoke(ContextInjectionFactory.java:173)
> at org.eclipse.e4.core.commands.internal.HandlerServiceHandler.execute(HandlerServiceHandler.java:156)
> ... 33 more
> Caused by: java.lang.NullPointerException
> at org.jboss.tools.jsf.model.handlers.RemoveJSFNatureContribution.execute(RemoveJSFNatureContribution.java:40)
> at org.jboss.tools.common.model.handlers.RemoveModelNatureHandler.executeHandler(RemoveModelNatureHandler.java:99)
> at org.jboss.tools.common.meta.action.impl.XActionImpl.executeHandler(XActionImpl.java:65)
> at org.jboss.tools.common.model.ui.action.XModelObjectAction.actionPerformed(XModelObjectAction.java:96)
> at org.jboss.tools.common.model.ui.action.XModelObjectActionInvoker.execute(XModelObjectActionInvoker.java:36)
> at org.jboss.tools.common.meta.action.XActionInvoker.invoke(XActionInvoker.java:53)
> at org.jboss.tools.common.meta.action.XActionInvoker.invoke(XActionInvoker.java:40)
> at org.jboss.tools.common.model.ui.internal.handlers.ModelResourceHandler.doRun(ModelResourceHandler.java:94)
> at org.jboss.tools.common.model.ui.internal.handlers.ModelResourceHandler.execute(ModelResourceHandler.java:74)
> at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:294)
> at org.eclipse.ui.internal.handlers.E4HandlerProxy.execute(E4HandlerProxy.java:96)
> at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflect.Method.invoke(Method.java:566)
> at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:58)
> ... 37 more
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 9 months
[JBoss JIRA] (JBIDE-26663) Error occured while running bean post processors after import Spring Starter Project
by Josef Kopriva (Jira)
Josef Kopriva created JBIDE-26663:
-------------------------------------
Summary: Error occured while running bean post processors after import Spring Starter Project
Key: JBIDE-26663
URL: https://issues.jboss.org/browse/JBIDE-26663
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: central
Affects Versions: 4.12.0.AM1
Reporter: Josef Kopriva
After import there is an error in error log:
{code:java}
null
org.springframework.ide.eclipse.beans.core
Warning
Mon Jun 10 09:00:00 CEST 2019
Error occured while running bean post processors
java.lang.IllegalStateException: Error processing condition on org.springframework.boot.autoconfigure.cache.CacheAutoConfiguration
at org.springframework.boot.autoconfigure.condition.SpringBootCondition.matches(SpringBootCondition.java:64)
at org.springframework.context.annotation.ConditionEvaluator.shouldSkip(ConditionEvaluator.java:102)
at org.springframework.context.annotation.ConfigurationClassBeanDefinitionReader$TrackedConditionEvaluator.shouldSkip(ConfigurationClassBeanDefinitionReader.java:444)
at org.springframework.context.annotation.ConfigurationClassBeanDefinitionReader$TrackedConditionEvaluator.shouldSkip(ConfigurationClassBeanDefinitionReader.java:433)
at org.springframework.context.annotation.ConfigurationClassBeanDefinitionReader.loadBeanDefinitionsForConfigurationClass(ConfigurationClassBeanDefinitionReader.java:127)
at org.springframework.context.annotation.ConfigurationClassBeanDefinitionReader.loadBeanDefinitions(ConfigurationClassBeanDefinitionReader.java:116)
at org.springframework.context.annotation.ConfigurationClassPostProcessor.processConfigBeanDefinitions(ConfigurationClassPostProcessor.java:320)
at org.springframework.ide.eclipse.metadata.process.JdtConfigurationClassPostProcessor.postProcess(JdtConfigurationClassPostProcessor.java:88)
at org.springframework.ide.eclipse.beans.core.internal.model.BeansJavaConfig$3.run(BeansJavaConfig.java:332)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:45)
at org.springframework.ide.eclipse.beans.core.internal.model.BeansJavaConfig.executePostProcessor(BeansJavaConfig.java:321)
at org.springframework.ide.eclipse.beans.core.internal.model.BeansJavaConfig.access$5(BeansJavaConfig.java:319)
at org.springframework.ide.eclipse.beans.core.internal.model.BeansJavaConfig$2.call(BeansJavaConfig.java:233)
at org.springframework.ide.eclipse.beans.core.internal.model.BeansJavaConfig$2.call(BeansJavaConfig.java:1)
at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
at java.base/java.lang.Thread.run(Thread.java:834)
Caused by: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'org.springframework.boot.autoconfigure.condition.BeanTypeRegistry': Instantiation of bean failed; nested exception is org.springframework.beans.BeanInstantiationException: Failed to instantiate [org.springframework.boot.autoconfigure.condition.BeanTypeRegistry]: No default constructor found; nested exception is java.lang.NoSuchMethodException: org.springframework.boot.autoconfigure.condition.BeanTypeRegistry.<init>()
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.instantiateBean(AbstractAutowireCapableBeanFactory.java:1159)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBeanInstance(AbstractAutowireCapableBeanFactory.java:1103)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:511)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:481)
at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:312)
at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:230)
at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:308)
at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:202)
at org.springframework.boot.autoconfigure.condition.BeanTypeRegistry.get(BeanTypeRegistry.java:369)
at org.springframework.boot.autoconfigure.condition.OnBeanCondition.collectBeanNamesForType(OnBeanCondition.java:297)
at org.springframework.boot.autoconfigure.condition.OnBeanCondition.getBeanNamesForType(OnBeanCondition.java:289)
at org.springframework.boot.autoconfigure.condition.OnBeanCondition.getBeanNamesForType(OnBeanCondition.java:278)
at org.springframework.boot.autoconfigure.condition.OnBeanCondition.getMatchingBeans(OnBeanCondition.java:189)
at org.springframework.boot.autoconfigure.condition.OnBeanCondition.getMatchOutcome(OnBeanCondition.java:125)
at org.springframework.boot.autoconfigure.condition.SpringBootCondition.matches(SpringBootCondition.java:47)
... 19 more
Caused by: org.springframework.beans.BeanInstantiationException: Failed to instantiate [org.springframework.boot.autoconfigure.condition.BeanTypeRegistry]: No default constructor found; nested exception is java.lang.NoSuchMethodException: org.springframework.boot.autoconfigure.condition.BeanTypeRegistry.<init>()
at org.springframework.beans.factory.support.SimpleInstantiationStrategy.instantiate(SimpleInstantiationStrategy.java:85)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.instantiateBean(AbstractAutowireCapableBeanFactory.java:1151)
... 33 more
Caused by: java.lang.NoSuchMethodException: org.springframework.boot.autoconfigure.condition.BeanTypeRegistry.<init>()
at java.base/java.lang.Class.getConstructor0(Class.java:3350)
at java.base/java.lang.Class.getDeclaredConstructor(Class.java:2554)
at org.springframework.beans.factory.support.SimpleInstantiationStrategy.instantiate(SimpleInstantiationStrategy.java:80)
... 34 more
{code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 9 months
[JBoss JIRA] (JBIDE-26662) Profile -Pdownload-devstudio cannot satisfy dependencies
by Jeff MAURY (Jira)
[ https://issues.jboss.org/browse/JBIDE-26662?page=com.atlassian.jira.plugi... ]
Jeff MAURY commented on JBIDE-26662:
------------------------------------
I can reproduce on my laptop. I don't understand why because I set tycho debug traces and the only thing is that org.jboss.ide.eclipse.archives.feature.feature.group is loaded but version is org.jboss.ide.eclipse.archives.feature.feature.group 3.6.202.qualifier
so maybe the qualifier expansion is missing.
Did this profile ever worked on non integration tests repos ?
> Profile -Pdownload-devstudio cannot satisfy dependencies
> --------------------------------------------------------
>
> Key: JBIDE-26662
> URL: https://issues.jboss.org/browse/JBIDE-26662
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Reporter: Josef Kopriva
> Priority: Critical
>
> When running command mvn clean install -DskipTests=true -Pdownload-devstudio in jbosstools-server repo tycho is not able to to resolve dependencies:
> {code:java}
> [INFO] Resolving dependencies of MavenProject: org.jboss.tools.archives.plugins:org.jboss.tools.archives.scanner:3.6.202-SNAPSHOT @ /Users/jkopriva/git/jkopriva/jbosstools-server/archives/plugins/org.jboss.tools.archives.scanner/pom.xml
> [INFO] {osgi.os=macosx, osgi.ws=cocoa, org.eclipse.update.install.features=true, osgi.arch=x86_64}
> [ERROR] Cannot resolve project dependencies:
> [ERROR] Software being installed: com.jboss.devstudio.core.feature.feature.group 12.12.0.v20190606-1202
> [ERROR] Missing requirement: com.jboss.devstudio.core.rpm.feature.feature.group 12.12.0.v20190606-1202 requires 'org.eclipse.equinox.p2.iu; org.jboss.ide.eclipse.archives.feature.feature.group [3.6.202.v20181011-1445,3.6.202.v20181011-1445]' but it could not be found
> [ERROR] Cannot satisfy dependency: com.jboss.devstudio.core.feature.feature.group 12.12.0.v20190606-1202 depends on: org.eclipse.equinox.p2.iu; com.jboss.devstudio.core.rpm.feature.feature.group [12.12.0.v20190606-1202,12.12.0.v20190606-1202]
> [ERROR]
> [ERROR] See http://wiki.eclipse.org/Tycho/Dependency_Resolution_Troubleshooting for help.
> [ERROR] Cannot resolve dependencies of MavenProject: org.jboss.tools.archives.plugins:org.jboss.tools.archives.scanner:3.6.202-SNAPSHOT @ /Users/jkopriva/git/jkopriva/jbosstools-server/archives/plugins/org.jboss.tools.archives.scanner/pom.xml: See log for details -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please read the following articles:
> [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MavenExecutionException
> {code}
> This is blocking running integration tests with profile download-devstudio.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 10 months
[JBoss JIRA] (JBDS-4776) Errors when deploying Fuse projects in OpenShift (Mac)
by Bruno Meseguer (Jira)
Bruno Meseguer created JBDS-4776:
------------------------------------
Summary: Errors when deploying Fuse projects in OpenShift (Mac)
Key: JBDS-4776
URL: https://issues.jboss.org/browse/JBDS-4776
Project: Red Hat CodeReady Studio (devstudio)
Issue Type: Bug
Affects Versions: 12.11.0.GA
Environment: The problem has been identified on a MacOS (tested with v10.14.4)
Reporter: Bruno Meseguer
The option of deploying Fuse projects directly from Studio seems to be broken.
On previous versions (JBDS v11.0.0 GA) this used to work.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 10 months
[JBoss JIRA] (JBIDE-26662) Profile -Pdownload-devstudio cannot satisfy dependencies
by Josef Kopriva (Jira)
[ https://issues.jboss.org/browse/JBIDE-26662?page=com.atlassian.jira.plugi... ]
Josef Kopriva updated JBIDE-26662:
----------------------------------
Description:
When running command mvn clean install -DskipTests=true -Pdownload-devstudio in jbosstools-server repo tycho is not able to to resolve dependencies:
{code:java}
[INFO] Resolving dependencies of MavenProject: org.jboss.tools.archives.plugins:org.jboss.tools.archives.scanner:3.6.202-SNAPSHOT @ /Users/jkopriva/git/jkopriva/jbosstools-server/archives/plugins/org.jboss.tools.archives.scanner/pom.xml
[INFO] {osgi.os=macosx, osgi.ws=cocoa, org.eclipse.update.install.features=true, osgi.arch=x86_64}
[ERROR] Cannot resolve project dependencies:
[ERROR] Software being installed: com.jboss.devstudio.core.feature.feature.group 12.12.0.v20190606-1202
[ERROR] Missing requirement: com.jboss.devstudio.core.rpm.feature.feature.group 12.12.0.v20190606-1202 requires 'org.eclipse.equinox.p2.iu; org.jboss.ide.eclipse.archives.feature.feature.group [3.6.202.v20181011-1445,3.6.202.v20181011-1445]' but it could not be found
[ERROR] Cannot satisfy dependency: com.jboss.devstudio.core.feature.feature.group 12.12.0.v20190606-1202 depends on: org.eclipse.equinox.p2.iu; com.jboss.devstudio.core.rpm.feature.feature.group [12.12.0.v20190606-1202,12.12.0.v20190606-1202]
[ERROR]
[ERROR] See http://wiki.eclipse.org/Tycho/Dependency_Resolution_Troubleshooting for help.
[ERROR] Cannot resolve dependencies of MavenProject: org.jboss.tools.archives.plugins:org.jboss.tools.archives.scanner:3.6.202-SNAPSHOT @ /Users/jkopriva/git/jkopriva/jbosstools-server/archives/plugins/org.jboss.tools.archives.scanner/pom.xml: See log for details -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MavenExecutionException
{code}
This is blocking running integration tests with profile download-devstudio.
was:
When running command mvn clean install -DskipTests=true -Pdownload-devstudio in jbosstools-server repo tycho is not able to to resolve dependencies:
{code:java}
[INFO] Resolving dependencies of MavenProject: org.jboss.tools.archives.plugins:org.jboss.tools.archives.scanner:3.6.202-SNAPSHOT @ /Users/jkopriva/git/jkopriva/jbosstools-server/archives/plugins/org.jboss.tools.archives.scanner/pom.xml
[INFO] {osgi.os=macosx, osgi.ws=cocoa, org.eclipse.update.install.features=true, osgi.arch=x86_64}
[ERROR] Cannot resolve project dependencies:
[ERROR] Software being installed: com.jboss.devstudio.core.feature.feature.group 12.12.0.v20190606-1202
[ERROR] Missing requirement: com.jboss.devstudio.core.rpm.feature.feature.group 12.12.0.v20190606-1202 requires 'org.eclipse.equinox.p2.iu; org.jboss.ide.eclipse.archives.feature.feature.group [3.6.202.v20181011-1445,3.6.202.v20181011-1445]' but it could not be found
[ERROR] Cannot satisfy dependency: com.jboss.devstudio.core.feature.feature.group 12.12.0.v20190606-1202 depends on: org.eclipse.equinox.p2.iu; com.jboss.devstudio.core.rpm.feature.feature.group [12.12.0.v20190606-1202,12.12.0.v20190606-1202]
[ERROR]
[ERROR] See http://wiki.eclipse.org/Tycho/Dependency_Resolution_Troubleshooting for help.
[ERROR] Cannot resolve dependencies of MavenProject: org.jboss.tools.archives.plugins:org.jboss.tools.archives.scanner:3.6.202-SNAPSHOT @ /Users/jkopriva/git/jkopriva/jbosstools-server/archives/plugins/org.jboss.tools.archives.scanner/pom.xml: See log for details -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MavenExecutionException
code}
> Profile -Pdownload-devstudio cannot satisfy dependencies
> --------------------------------------------------------
>
> Key: JBIDE-26662
> URL: https://issues.jboss.org/browse/JBIDE-26662
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Reporter: Josef Kopriva
> Priority: Critical
>
> When running command mvn clean install -DskipTests=true -Pdownload-devstudio in jbosstools-server repo tycho is not able to to resolve dependencies:
> {code:java}
> [INFO] Resolving dependencies of MavenProject: org.jboss.tools.archives.plugins:org.jboss.tools.archives.scanner:3.6.202-SNAPSHOT @ /Users/jkopriva/git/jkopriva/jbosstools-server/archives/plugins/org.jboss.tools.archives.scanner/pom.xml
> [INFO] {osgi.os=macosx, osgi.ws=cocoa, org.eclipse.update.install.features=true, osgi.arch=x86_64}
> [ERROR] Cannot resolve project dependencies:
> [ERROR] Software being installed: com.jboss.devstudio.core.feature.feature.group 12.12.0.v20190606-1202
> [ERROR] Missing requirement: com.jboss.devstudio.core.rpm.feature.feature.group 12.12.0.v20190606-1202 requires 'org.eclipse.equinox.p2.iu; org.jboss.ide.eclipse.archives.feature.feature.group [3.6.202.v20181011-1445,3.6.202.v20181011-1445]' but it could not be found
> [ERROR] Cannot satisfy dependency: com.jboss.devstudio.core.feature.feature.group 12.12.0.v20190606-1202 depends on: org.eclipse.equinox.p2.iu; com.jboss.devstudio.core.rpm.feature.feature.group [12.12.0.v20190606-1202,12.12.0.v20190606-1202]
> [ERROR]
> [ERROR] See http://wiki.eclipse.org/Tycho/Dependency_Resolution_Troubleshooting for help.
> [ERROR] Cannot resolve dependencies of MavenProject: org.jboss.tools.archives.plugins:org.jboss.tools.archives.scanner:3.6.202-SNAPSHOT @ /Users/jkopriva/git/jkopriva/jbosstools-server/archives/plugins/org.jboss.tools.archives.scanner/pom.xml: See log for details -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please read the following articles:
> [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MavenExecutionException
> {code}
> This is blocking running integration tests with profile download-devstudio.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 10 months
[JBoss JIRA] (JBIDE-26662) Profile -Pdownload-devstudio cannot satisfy dependencies
by Josef Kopriva (Jira)
Josef Kopriva created JBIDE-26662:
-------------------------------------
Summary: Profile -Pdownload-devstudio cannot satisfy dependencies
Key: JBIDE-26662
URL: https://issues.jboss.org/browse/JBIDE-26662
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: build
Reporter: Josef Kopriva
When running command mvn clean install -DskipTests=true -Pdownload-devstudio in jbosstools-server repo tycho is not able to to resolve dependencies:
{code:java}
[INFO] Resolving dependencies of MavenProject: org.jboss.tools.archives.plugins:org.jboss.tools.archives.scanner:3.6.202-SNAPSHOT @ /Users/jkopriva/git/jkopriva/jbosstools-server/archives/plugins/org.jboss.tools.archives.scanner/pom.xml
[INFO] {osgi.os=macosx, osgi.ws=cocoa, org.eclipse.update.install.features=true, osgi.arch=x86_64}
[ERROR] Cannot resolve project dependencies:
[ERROR] Software being installed: com.jboss.devstudio.core.feature.feature.group 12.12.0.v20190606-1202
[ERROR] Missing requirement: com.jboss.devstudio.core.rpm.feature.feature.group 12.12.0.v20190606-1202 requires 'org.eclipse.equinox.p2.iu; org.jboss.ide.eclipse.archives.feature.feature.group [3.6.202.v20181011-1445,3.6.202.v20181011-1445]' but it could not be found
[ERROR] Cannot satisfy dependency: com.jboss.devstudio.core.feature.feature.group 12.12.0.v20190606-1202 depends on: org.eclipse.equinox.p2.iu; com.jboss.devstudio.core.rpm.feature.feature.group [12.12.0.v20190606-1202,12.12.0.v20190606-1202]
[ERROR]
[ERROR] See http://wiki.eclipse.org/Tycho/Dependency_Resolution_Troubleshooting for help.
[ERROR] Cannot resolve dependencies of MavenProject: org.jboss.tools.archives.plugins:org.jboss.tools.archives.scanner:3.6.202-SNAPSHOT @ /Users/jkopriva/git/jkopriva/jbosstools-server/archives/plugins/org.jboss.tools.archives.scanner/pom.xml: See log for details -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MavenExecutionException
code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 10 months