[JBoss JIRA] (JBIDE-19518) FH imported app cannot talk to FH cloud
by Pavol Srna (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19518?page=com.atlassian.jira.plugi... ]
Pavol Srna updated JBIDE-19518:
-------------------------------
Description:
1) Create "Cordova Hello World Project" in FH cloud
2) build cordova app in cloud, QR install and ASSERT app works
3) import cordova app into jbds
4) run imported app on real device /or simulator
5) Fill in a name and click on "Say Hello From The Cloud"
{code}
Error occured: No Cloud App connected to this Client App. Please Configure a Cloud App for this Client App to talk to: [object Object] {code}
was:
1) Create cordova app in FH cloud
2) build in cloud, QR install and ASSERT app works
3) import cordova app into jbds
4) run imported app on real device /or simulator
5) Fill in a name and click on "Say Hello From The Cloud"
{code}
Error occured: No Cloud App connected to this Client App. Please Configure a Cloud App for this Client App to talk to: [object Object] {code}
> FH imported app cannot talk to FH cloud
> ---------------------------------------
>
> Key: JBIDE-19518
> URL: https://issues.jboss.org/browse/JBIDE-19518
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: aerogear-hybrid
> Affects Versions: 4.2.3.CR1
> Reporter: Pavol Srna
> Priority: Critical
> Fix For: 4.2.3.Final
>
>
> 1) Create "Cordova Hello World Project" in FH cloud
> 2) build cordova app in cloud, QR install and ASSERT app works
> 3) import cordova app into jbds
> 4) run imported app on real device /or simulator
> 5) Fill in a name and click on "Say Hello From The Cloud"
> {code}
> Error occured: No Cloud App connected to this Client App. Please Configure a Cloud App for this Client App to talk to: [object Object] {code}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
10 years, 11 months
[JBoss JIRA] (JBIDE-19518) FH imported app cannot talk to FH cloud
by Ilya Buziuk (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19518?page=com.atlassian.jira.plugi... ]
Ilya Buziuk commented on JBIDE-19518:
-------------------------------------
[~psrna] does it work with CordovaSim?
> FH imported app cannot talk to FH cloud
> ---------------------------------------
>
> Key: JBIDE-19518
> URL: https://issues.jboss.org/browse/JBIDE-19518
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: aerogear-hybrid
> Affects Versions: 4.2.3.CR1
> Reporter: Pavol Srna
> Priority: Critical
> Fix For: 4.2.3.Final
>
>
> 1) Create cordova app in FH cloud
> 2) build in cloud, QR install and ASSERT app works
> 3) import cordova app into jbds
> 4) run imported app on real device /or simulator
> 5) Fill in a name and click on "Say Hello From The Cloud"
> {code}
> Error occured: No Cloud App connected to this Client App. Please Configure a Cloud App for this Client App to talk to: [object Object] {code}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
10 years, 11 months
[JBoss JIRA] (JBDS-3208) reorg/refactor directories for consistency across JBT/JBDS
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBDS-3208?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen commented on JBDS-3208:
-------------------------------------------
what is _composite_ and _emptycomposite_ about ? why do we need an extra level of composites ?
I don't recall nor see them in the proposals discussed ?
> reorg/refactor directories for consistency across JBT/JBDS
> ----------------------------------------------------------
>
> Key: JBDS-3208
> URL: https://issues.jboss.org/browse/JBDS-3208
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: build
> Affects Versions: 9.0.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 9.0.0.Alpha2
>
>
> Be it resolved - we should reorg directories for consistency across JBT/JBDS:
> Latest suggestion:
> * /\{mars,9.0}/
> ** /\{{color:red}snapshots{color},{color:orange}staging{color},{color:blue}development{color},{color:green}stable{color}\}/
> *** /*updates*/
> **** /\{requirements, jbosstoolstarget,jbdevstudiotarget, core,coretests,webtools,hibernatetools, discovery, central,earlyaccess, integration-stack,integration-stack-earlyaccess}/
> ***** /<build-version = 4.3.0.Alpha1, 4.3.0.Final, 4.41.\*, 4.50.\*...>/
> *** /*builds*/
> **** /<job-name>/
> ***** /{<pull-request-version = PR123, PR124, PR125...>, <build-version = B123, B124, B125...>}/
> ---
> Older idea:
> {code}
> <download.jboss.org,devstudio.redhat.com>
> <earlyaccess,updates,discovery>/<mars,9.0>
> /snapshots [replace nightly]
> /staging [rename content for QE, moves to development when approved]
> /development
> /stable (updates/<mars,9.0>/stable is a pointer back into parent folder so published URL can be simpler
> drop /integration (not used)
> builds/<jobname>/<buildid>
> builds/<jobname>/composite*.xml for last N builds
> targetplatforms/<type>/<version>
> {code}
> Further discussion in http://ether-man.rhcloud.com/p/build.next.20141112
> This would remove the idea of the composite staging site [1] and the composite install job [2], today used to determine when it's time to run the aggregate builds, in favour of a new p2diff mechanism for determining if aggregates should be published. See JBIDE-18742 and JBIDE-16970.
> [1] http://download.jboss.org/jbosstools/builds/staging/_composite_/core/4.2....
> [2] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS...
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
10 years, 11 months
[JBoss JIRA] (JBIDE-19518) FH imported app cannot talk to FH cloud
by Pavol Srna (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19518?page=com.atlassian.jira.plugi... ]
Pavol Srna updated JBIDE-19518:
-------------------------------
Description:
1) Create cordova app in FH cloud
2) build in cloud, QR install and ASSERT app works
3) import cordova app into jbds
4) run imported app on real device /or simulator
5) Fill in a name and click on "Say Hello From The Cloud"
{code}
Error occured: No Cloud App connected to this Client App. Please Configure a Cloud App for this Client App to talk to: [object Object] {code}
was:
1) Create cordova app in FH cloud
2) build in cloud, QR install and assert app works
3) import cordova app into jbds
4) run imported app on real device /or simulator
5) Fill in a name and click on "Say Hello From The Cloud"
{code}
Error occured: No Cloud App connected to this Client App. Please Configure a Cloud App for this Client App to talk to: [object Object] {code}
> FH imported app cannot talk to FH cloud
> ---------------------------------------
>
> Key: JBIDE-19518
> URL: https://issues.jboss.org/browse/JBIDE-19518
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: aerogear-hybrid
> Affects Versions: 4.2.3.CR1
> Reporter: Pavol Srna
> Priority: Critical
> Fix For: 4.2.3.Final
>
>
> 1) Create cordova app in FH cloud
> 2) build in cloud, QR install and ASSERT app works
> 3) import cordova app into jbds
> 4) run imported app on real device /or simulator
> 5) Fill in a name and click on "Say Hello From The Cloud"
> {code}
> Error occured: No Cloud App connected to this Client App. Please Configure a Cloud App for this Client App to talk to: [object Object] {code}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
10 years, 11 months
[JBoss JIRA] (JBIDE-19518) FH imported app cannot talk to FH cloud
by Pavol Srna (JIRA)
Pavol Srna created JBIDE-19518:
----------------------------------
Summary: FH imported app cannot talk to FH cloud
Key: JBIDE-19518
URL: https://issues.jboss.org/browse/JBIDE-19518
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: aerogear-hybrid
Affects Versions: 4.2.3.CR1
Reporter: Pavol Srna
Priority: Critical
1) Create cordova app in FH cloud
2) build in cloud, QR install and assert app works
3) import cordova app into jbds
4) run imported app on real device /or simulator
5) Fill in a name and click on "Say Hello From The Cloud"
{code}
Error occured: No Cloud App connected to this Client App. Please Configure a Cloud App for this Client App to talk to: [object Object] {code}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
10 years, 11 months
[JBoss JIRA] (JBIDE-19518) FH imported app cannot talk to FH cloud
by Pavol Srna (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19518?page=com.atlassian.jira.plugi... ]
Pavol Srna updated JBIDE-19518:
-------------------------------
Fix Version/s: 4.2.3.Final
> FH imported app cannot talk to FH cloud
> ---------------------------------------
>
> Key: JBIDE-19518
> URL: https://issues.jboss.org/browse/JBIDE-19518
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: aerogear-hybrid
> Affects Versions: 4.2.3.CR1
> Reporter: Pavol Srna
> Priority: Critical
> Fix For: 4.2.3.Final
>
>
> 1) Create cordova app in FH cloud
> 2) build in cloud, QR install and assert app works
> 3) import cordova app into jbds
> 4) run imported app on real device /or simulator
> 5) Fill in a name and click on "Say Hello From The Cloud"
> {code}
> Error occured: No Cloud App connected to this Client App. Please Configure a Cloud App for this Client App to talk to: [object Object] {code}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
10 years, 11 months
[JBoss JIRA] (JBIDE-19469) java.lang.IllegalStateException: A project is required in the current context
by Pavol Srna (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19469?page=com.atlassian.jira.plugi... ]
Pavol Srna closed JBIDE-19469.
------------------------------
Verified.
> java.lang.IllegalStateException: A project is required in the current context
> -----------------------------------------------------------------------------
>
> Key: JBIDE-19469
> URL: https://issues.jboss.org/browse/JBIDE-19469
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: forge
> Affects Versions: 4.2.3.CR1
> Reporter: Pavol Srna
> Assignee: George Gastaldi
> Priority: Critical
> Fix For: 4.2.3.CR1
>
> Attachments: forge-err-2.png
>
>
> {code}
> java.lang.IllegalStateException: A project is required in the current context
> at org.jboss.forge.addon.projects.ui.AbstractProjectCommand.getSelectedProject(AbstractProjectCommand.java:78)
> at org.jboss.forge.addon.as.ui.AbstractASWizardImpl.getSelectedProvider(AbstractASWizardImpl.java:82)
> at org.jboss.forge.addon.as.ui.AbstractASWizardImpl.isEnabled(AbstractASWizardImpl.java:61)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at org.jboss.forge.furnace.proxy.ClassLoaderInterceptor$1.call(ClassLoaderInterceptor.java:87)
> at org.jboss.forge.furnace.util.ClassLoaders.executeIn(ClassLoaders.java:42)
> at org.jboss.forge.furnace.proxy.ClassLoaderInterceptor.invoke(ClassLoaderInterceptor.java:103)
> at org.jboss.forge.addon.as.ui.ASShutdownWizardImpl_$$_javassist_ab26a278-6cdf-48c3-8310-63c36d4f93cb.isEnabled(ASShutdownWizardImpl_$$_javassist_ab26a278-6cdf-48c3-8310-63c36d4f93cb.java)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback$2.call(ClassLoaderAdapterCallback.java:123)
> at org.jboss.forge.furnace.util.ClassLoaders.executeIn(ClassLoaders.java:42)
> at org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback.invoke(ClassLoaderAdapterCallback.java:96)
> at org.jboss.forge.addon.ui.wizard.UIWizard_$$_javassist_6536f3f8-f9ef-4b61-af8f-308725a51e37.isEnabled(UIWizard_$$_javassist_6536f3f8-f9ef-4b61-af8f-308725a51e37.java)
> at org.jboss.tools.forge.ui.internal.ext.dialog.WizardDialogHelper.getAllCandidatesAsList(WizardDialogHelper.java:65)
> at org.jboss.tools.forge.ui.internal.ext.dialog.UICommandListDialog.getProviders(UICommandListDialog.java:255)
> at org.jboss.tools.forge.ui.internal.ext.dialog.UICommandListDialog.access$1(UICommandListDialog.java:251)
> at org.jboss.tools.forge.ui.internal.ext.dialog.UICommandListDialog$1.run(UICommandListDialog.java:195)
> at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
> at org.jboss.tools.forge.ui.internal.ext.dialog.UICommandListDialog.createDialogArea(UICommandListDialog.java:184)
> at org.eclipse.jface.dialogs.PopupDialog.createContents(PopupDialog.java:715)
> at org.eclipse.jface.window.Window.create(Window.java:435)
> at org.eclipse.jface.dialogs.PopupDialog.open(PopupDialog.java:1159)
> at org.jboss.tools.forge.ui.internal.ext.handlers.ForgeCommandHandler$1$1.run(ForgeCommandHandler.java:55)
> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:136)
> at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3774)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3412)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1151)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1032)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:148)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:636)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:579)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:135)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:380)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:235)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:648)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:603)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1465)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1438)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
10 years, 11 months
[JBoss JIRA] (JBIDE-19513) multiple versions of jetty and java.servlet plugins in JBDS 9
by Ilya Buziuk (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19513?page=com.atlassian.jira.plugi... ]
Ilya Buziuk commented on JBIDE-19513:
-------------------------------------
[~xcoulon] want to give a heads up. I haven't added whole pack of websockets bundles, only:
- org.eclipse.jetty.websocket.api
- org.eclipse.jetty.websocket.common
- org.eclipse.jetty.websocket.server
- org.eclipse.jetty.websocket.servlet
In case you need something extra (e.g. websocket.client) just let me know - I will update PR
> multiple versions of jetty and java.servlet plugins in JBDS 9
> -------------------------------------------------------------
>
> Key: JBIDE-19513
> URL: https://issues.jboss.org/browse/JBIDE-19513
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, qa, target-platform, updatesite
> Affects Versions: 4.3.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Ilya Buziuk
> Fix For: 4.3.0.Alpha2
>
>
> These plugins versions are included in JBDS 9 with multiple versions. We need to decide if this is acceptable / intentional, or something to fix.
> {code}
> org.eclipse.jetty.http_8.1.14.v20131031 and 9.2.5
> org.eclipse.jetty.servlet_8.1.14.v20131031 and 9.2.5
> org.eclipse.jetty.server_8.1.14.v20131031 and 9.2.5
> org.eclipse.jetty.security_8.1.14.v20131031 and 9.2.5
> org.eclipse.jetty.continuation_8.1.14.v20131031 and 9.2.5
> org.eclipse.jetty.util_8.1.14.v20131031 and 9.2.5
> org.eclipse.jetty.io_8.1.14.v20131031 and 9.2.5
> - and -
> javax.servlet_3.1.0.v201410161800 and 3.0.0{code}
> Pre-existing ignored/known issues:
> {code}
> org.eclipse.jdt.annotation_1.1.100.v20140704-0625
> com.jcraft.jsch_0.1.50.v201403120620
> org.apache.commons.logging_1.0.4.v201101211617
> javax.wsdl_1.5.1.v201012040544 {code}
> See detailed reports here:
> https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS...
> https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS...
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
10 years, 11 months
[JBoss JIRA] (JBIDE-18578) Additional javaee7-samples import issues
by Jiri Peterka (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18578?page=com.atlassian.jira.plugi... ]
Jiri Peterka commented on JBIDE-18578:
--------------------------------------
yes, specifically "mvn clean verify -DskipTests=true" is without errors
> Additional javaee7-samples import issues
> ----------------------------------------
>
> Key: JBIDE-18578
> URL: https://issues.jboss.org/browse/JBIDE-18578
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: upstream
> Affects Versions: 4.2.0.CR2
> Environment: JBDS 8.0.0.CR2
> Reporter: Jiri Peterka
> Fix For: 4.3.0.Alpha2
>
>
> Additional javaee7-samples import issues
> Clone and import https://github.com/javaee-samples/javaee7-samples as maven projects
> They should import nicely (without errors) into JBT/JBDS and deploy to a JBT/JBDS managed Wildfly.
> There are still some Java Problems, Maven Problems and XML Problems after import, most projects are without errors. Project should be imported without errors
> Java Problems
> {code}
> Description Resource Path Location Type
> EBook cannot be resolved to a type EBookStoreClientSampleTest.java /jaxws-client/src/test/java/org/javaee7/jaxws/client line 71 Java Problem
> EBook cannot be resolved to a type EBookStoreClientSampleTest.java /jaxws-client/src/test/java/org/javaee7/jaxws/client line 71 Java Problem
> EBook cannot be resolved to a type EBookStoreClientSampleTest.java /jaxws-client/src/test/java/org/javaee7/jaxws/client line 76 Java Problem
> EBook cannot be resolved to a type EBookStoreClientSampleTest.java /jaxws-client/src/test/java/org/javaee7/jaxws/client line 85 Java Problem
> EBookStore cannot be resolved to a type EBookStoreClientSampleTest.java /jaxws-client/src/test/java/org/javaee7/jaxws/client line 63 Java Problem
> EBookStore cannot be resolved to a type EBookStoreClientSampleTest.java /jaxws-client/src/test/java/org/javaee7/jaxws/client line 69 Java Problem
> EBookStore cannot be resolved to a type EBookStoreClientSampleTest.java /jaxws-client/src/test/java/org/javaee7/jaxws/client line 69 Java Problem
> EBookStoreImplService cannot be resolved to a type EBookStoreClientSampleTest.java /jaxws-client/src/test/java/org/javaee7/jaxws/client line 35 Java Problem
> EBookStoreImplService cannot be resolved to a type EBookStoreClientSampleTest.java /jaxws-client/src/test/java/org/javaee7/jaxws/client line 56 Java Problem
> EBookStoreImplService cannot be resolved to a type EBookStoreClientSampleTest.java /jaxws-client/src/test/java/org/javaee7/jaxws/client line 56 Java Problem
> EBookStoreImplService cannot be resolved to a type EBookStoreClientSampleTest.java /jaxws-client/src/test/java/org/javaee7/jaxws/client line 63 Java Problem
> EBookStoreImplService cannot be resolved to a type EBookStoreClientSampleTest.java /jaxws-client/src/test/java/org/javaee7/jaxws/client line 69 Java Problem
> Greeting cannot be resolved to a type GreetingTest.java /bean-discovery-all/src/test/java/org/javaee7/cdi/nobeans/xml line 28 Java Problem
> Greeting cannot be resolved to a type GreetingTest.java /bean-discovery-all/src/test/java/org/javaee7/cdi/nobeans/xml line 32 Java Problem
> Greeting cannot be resolved to a type GreetingTest.java /bean-discovery-all/src/test/java/org/javaee7/cdi/nobeans/xml line 36 Java Problem
> Greeting cannot be resolved to a type GreetingTest.java /bean-discovery-all/src/test/java/org/javaee7/cdi/nobeans/xml line 37 Java Problem
> SimpleGreeting cannot be resolved to a type GreetingTest.java /bean-discovery-all/src/test/java/org/javaee7/cdi/nobeans/xml line 28 Java Problem
> SimpleGreeting cannot be resolved to a type GreetingTest.java /bean-discovery-all/src/test/java/org/javaee7/cdi/nobeans/xml line 37 Java Problem
> The declared package "org.javaee7.cdi.bean.discovery" does not match the expected package "main.java.org.javaee7.cdi.bean.discovery" Greeting.java /bean-discovery-all/src/main/java/org/javaee7/cdi/bean/discovery line 1 Java Problem
> The declared package "org.javaee7.cdi.bean.discovery" does not match the expected package "main.java.org.javaee7.cdi.bean.discovery" SimpleGreeting.java /bean-discovery-all/src/main/java/org/javaee7/cdi/bean/discovery line 1 Java Problem
> The declared package "org.javaee7.cdi.nobeans.xml" does not match the expected package "test.java.org.javaee7.cdi.nobeans.xml" GreetingTest.java /bean-discovery-all/src/test/java/org/javaee7/cdi/nobeans/xml line 1 Java Problem
> The import org.javaee7 cannot be resolved GreetingTest.java /bean-discovery-all/src/test/java/org/javaee7/cdi/nobeans/xml line 3 Java Problem
> The import org.javaee7 cannot be resolved GreetingTest.java /bean-discovery-all/src/test/java/org/javaee7/cdi/nobeans/xml line 4 Java Problem
> The import org.javaee7.jaxws.client.gen cannot be resolved EBookStoreClientSampleTest.java /jaxws-client/src/test/java/org/javaee7/jaxws/client line 12 Java Problem
> The import org.javaee7.jaxws.client.gen cannot be resolved EBookStoreClientSampleTest.java /jaxws-client/src/test/java/org/javaee7/jaxws/client line 13 Java Problem
> The import org.javaee7.jaxws.client.gen cannot be resolved EBookStoreClientSampleTest.java /jaxws-client/src/test/java/org/javaee7/jaxws/client line 14 Java Problem
> {code}
> Maven Problems:
> {code}
> Description Resource Path Location Type
> Plugin execution not covered by lifecycle configuration: org.codehaus.mojo:jaxws-maven-plugin:1.11:wsgen (execution: default, phase: process-classes) pom.xml /jaxws-endpoint line 21 Maven Project Build Lifecycle Mapping Problem
> Plugin execution not covered by lifecycle configuration: org.codehaus.mojo:jaxws-maven-plugin:1.11:wsimport (execution: default, phase: generate-sources) pom.xml /jaxws-client line 21 Maven Project Build Lifecycle Mapping Problem
> {code}
> and xml problems
> {code}
> Description Resource Path Location Type
> cvc-complex-type.2.1: Element 'jboss' must have no character or element information item [children], because the type's content type is empty. enforce-beans.xml /jax-rs-angularjs/src/test/resources line 4 XML Problem
> cvc-complex-type.2.2: Element 'value' must have no element [children], and the value must be valid. flow1-flow.xml /flows-declarative/src/main/webapp/flow1 line 31 XML Problem
> cvc-complex-type.2.2: Element 'value' must have no element [children], and the value must be valid. flow1-flow.xml /flows-declarative/src/main/webapp/flow1 line 35 XML Problem
> cvc-complex-type.2.2: Element 'value' must have no element [children], and the value must be valid. flow2-flow.xml /flows-declarative/src/main/webapp/flow2 line 31 XML Problem
> cvc-complex-type.2.2: Element 'value' must have no element [children], and the value must be valid. flow2-flow.xml /flows-declarative/src/main/webapp/flow2 line 35 XML Problem
> cvc-complex-type.2.2: Element 'value' must have no element [children], and the value must be valid. flow2-flow.xml /flows-mixed/src/main/webapp/flow2 line 34 XML Problem
> cvc-complex-type.2.2: Element 'value' must have no element [children], and the value must be valid. flow2-flow.xml /flows-mixed/src/main/webapp/flow2 line 38 XML Problem
> cvc-complex-type.2.4.a: Invalid content was found starting with element 'flow-call'. One of '{"http://xmlns.jcp.org/xml/ns/javaee":inbound-parameter}' is expected. flow1-flow.xml /flows-declarative/src/main/webapp/flow1 line 25 XML Problem
> cvc-complex-type.2.4.a: Invalid content was found starting with element 'flow-call'. One of '{"http://xmlns.jcp.org/xml/ns/javaee":inbound-parameter}' is expected. flow2-flow.xml /flows-declarative/src/main/webapp/flow2 line 25 XML Problem
> cvc-complex-type.2.4.a: Invalid content was found starting with element 'flow-call'. One of '{"http://xmlns.jcp.org/xml/ns/javaee":inbound-parameter}' is expected. flow2-flow.xml /flows-mixed/src/main/webapp/flow2 line 28 XML Problem
> cvc-elt.1: Cannot find the declaration of element 'arquillian'. arquillian.xml /jaxrs-endpoint/src/test/resources line 3 XML Problem
> cvc-elt.1: Cannot find the declaration of element 'arquillian'. arquillian.xml /jpa-converter/src/test/resources-glassfish-embedded line 5 XML Problem
> cvc-elt.1: Cannot find the declaration of element 'arquillian'. arquillian.xml /jpa-converter/src/test/resources-glassfish-remote line 5 XML Problem
> cvc-elt.1: Cannot find the declaration of element 'arquillian'. arquillian.xml /jpa-converter/src/test/resources-jbosseap-remote line 5 XML Problem
> cvc-elt.1: Cannot find the declaration of element 'arquillian'. arquillian.xml /send-receive/src/test/resources line 3 XML Problem
> cvc-elt.1: Cannot find the declaration of element 'arquillian'. arquillian.xml /standalone/src/test/resources line 3 XML Problem
> cvc-elt.1: Cannot find the declaration of element 'arquillian'. arquillian.xml /transactional/src/test/resources line 3 XML Problem
> cvc-elt.1: Cannot find the declaration of element 'arquillian'. arquillian.xml /user-transaction/src/test/resources line 3 XML Problem
> cvc-pattern-valid: Value 'param1 flow1 value' is not facet-valid with respect to pattern '#\{.*\}' for type 'faces-config-el-expressionType'. flow1-flow.xml /flows-declarative/src/main/webapp/flow1 line 31 XML Problem
> cvc-pattern-valid: Value 'param1 flow2 value' is not facet-valid with respect to pattern '#\{.*\}' for type 'faces-config-el-expressionType'. flow2-flow.xml /flows-declarative/src/main/webapp/flow2 line 31 XML Problem
> cvc-pattern-valid: Value 'param1 flow2 value' is not facet-valid with respect to pattern '#\{.*\}' for type 'faces-config-el-expressionType'. flow2-flow.xml /flows-mixed/src/main/webapp/flow2 line 34 XML Problem
> cvc-pattern-valid: Value 'param2 flow1 value' is not facet-valid with respect to pattern '#\{.*\}' for type 'faces-config-el-expressionType'. flow1-flow.xml /flows-declarative/src/main/webapp/flow1 line 35 XML Problem
> cvc-pattern-valid: Value 'param2 flow2 value' is not facet-valid with respect to pattern '#\{.*\}' for type 'faces-config-el-expressionType'. flow2-flow.xml /flows-declarative/src/main/webapp/flow2 line 35 XML Problem
> cvc-pattern-valid: Value 'param2 flow2 value' is not facet-valid with respect to pattern '#\{.*\}' for type 'faces-config-el-expressionType'. flow2-flow.xml /flows-mixed/src/main/webapp/flow2 line 38 XML Problem
> {code}
> Additional issues:
> https://issues.jboss.org/browse/JBIDE-18352
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
10 years, 11 months