[JBoss JIRA] (JBDS-2793) Align JDF and WFK quickstarts/examples/tutorials with a project layout that works with eclipse tooling
by Vlado Pakan (JIRA)
[ https://issues.jboss.org/browse/JBDS-2793?page=com.atlassian.jira.plugin.... ]
Vlado Pakan closed JBDS-2793.
-----------------------------
> Align JDF and WFK quickstarts/examples/tutorials with a project layout that works with eclipse tooling
> ------------------------------------------------------------------------------------------------------
>
> Key: JBDS-2793
> URL: https://issues.jboss.org/browse/JBDS-2793
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: aerogear-hybrid
> Reporter: Max Rydahl Andersen
> Assignee: Vineet Reynolds
> Priority: Blocker
> Fix For: 8.0.0.CR2
>
> Attachments: directoryStructure.tiff
>
>
> wfk/jdf has or will get quickstarts/tutorials that works with cordova.
> Needs to sync up with them on what we support/dont support.
> Current suggestion is that the cordova app should be *separate* from the webapp, not "mixed" in.
> With a structure like:
> TicketMonster/
> www/config.xml
> plugins
> .project
> platforms
> ios
> android
> it can build both with cordova-cli and the eclipse tools (eclipse will ignore platforms directory)
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 6 months
[JBoss JIRA] (JBDS-2793) Align JDF and WFK quickstarts/examples/tutorials with a project layout that works with eclipse tooling
by Vlado Pakan (JIRA)
[ https://issues.jboss.org/browse/JBDS-2793?page=com.atlassian.jira.plugin.... ]
Vlado Pakan commented on JBDS-2793:
-----------------------------------
Verified with JBT 4.2.0.CR2-v20141005-0541-B267
Cordova project of Ticket Monster v. 2.5.0.Final is imported to JBT without any problems
> Align JDF and WFK quickstarts/examples/tutorials with a project layout that works with eclipse tooling
> ------------------------------------------------------------------------------------------------------
>
> Key: JBDS-2793
> URL: https://issues.jboss.org/browse/JBDS-2793
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: aerogear-hybrid
> Reporter: Max Rydahl Andersen
> Assignee: Vineet Reynolds
> Priority: Blocker
> Fix For: 8.0.0.CR2
>
> Attachments: directoryStructure.tiff
>
>
> wfk/jdf has or will get quickstarts/tutorials that works with cordova.
> Needs to sync up with them on what we support/dont support.
> Current suggestion is that the cordova app should be *separate* from the webapp, not "mixed" in.
> With a structure like:
> TicketMonster/
> www/config.xml
> plugins
> .project
> platforms
> ios
> android
> it can build both with cordova-cli and the eclipse tools (eclipse will ignore platforms directory)
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 6 months
[JBoss JIRA] (JBIDE-18521) On RHEL7, Browsersim cannot use the SWT Browser (GTK) as the browser engine
by Konstantin Marmalyukov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18521?page=com.atlassian.jira.plugi... ]
Konstantin Marmalyukov edited comment on JBIDE-18521 at 10/7/14 12:06 PM:
--------------------------------------------------------------------------
Everything happens because webkitgtk package(which is needed for creating WebKit browser under GTK2) is not available for RHEL7.
But we cannot completely disable GTK2 for RHEL7 cause user can use javaFX engine with GTK2
was (Author: kmarmaliykov):
Everything happens because webkitgtk package(which is needed for creating WebKit browser under GTK2) is not available for RHEL7
> On RHEL7, Browsersim cannot use the SWT Browser (GTK) as the browser engine
> ---------------------------------------------------------------------------
>
> Key: JBIDE-18521
> URL: https://issues.jboss.org/browse/JBIDE-18521
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: browsersim
> Affects Versions: 4.2.0.CR2
> Environment: RHEL7
> Java 1.7
> Java 1.8
> Reporter: Len DiMaggio
> Assignee: Konstantin Marmalyukov
> Priority: Critical
> Fix For: 4.2.0.Final
>
> Attachments: screenshot_JBIDE-18521.png
>
>
> Steps to reproduce:
> * Configure Browsersim to use either Oracle 1.7 or 1.8 JDK on RHEL7
> * Open Browsersim
> * Right-click to open the Browsersim context menu
> * Observe the "please install webkitgtk to to use SWT.WebKit.engine" error
> (See attached screenshot)
> The webkitgtk package does not exist for RHEL7 - webkitgtk3 is installed in RHEL7 OOTB.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 6 months
[JBoss JIRA] (JBIDE-18521) On RHEL7, Browsersim cannot use the SWT Browser (GTK) as the browser engine
by Konstantin Marmalyukov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18521?page=com.atlassian.jira.plugi... ]
Konstantin Marmalyukov commented on JBIDE-18521:
------------------------------------------------
Everything happens because webkitgtk package(which is needed for creating WebKit browser under GTK2) is not available for RHEL7
> On RHEL7, Browsersim cannot use the SWT Browser (GTK) as the browser engine
> ---------------------------------------------------------------------------
>
> Key: JBIDE-18521
> URL: https://issues.jboss.org/browse/JBIDE-18521
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: browsersim
> Affects Versions: 4.2.0.CR2
> Environment: RHEL7
> Java 1.7
> Java 1.8
> Reporter: Len DiMaggio
> Assignee: Konstantin Marmalyukov
> Priority: Critical
> Fix For: 4.2.0.Final
>
> Attachments: screenshot_JBIDE-18521.png
>
>
> Steps to reproduce:
> * Configure Browsersim to use either Oracle 1.7 or 1.8 JDK on RHEL7
> * Open Browsersim
> * Right-click to open the Browsersim context menu
> * Observe the "please install webkitgtk to to use SWT.WebKit.engine" error
> (See attached screenshot)
> The webkitgtk package does not exist for RHEL7 - webkitgtk3 is installed in RHEL7 OOTB.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 6 months
[JBoss JIRA] (JBIDE-18312) CordovaSim struggles with POST
by Vlado Pakan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18312?page=com.atlassian.jira.plugi... ]
Vlado Pakan closed JBIDE-18312.
-------------------------------
Resolution: Done
Thanks for fast response. Verified with JBT 4.2.0.CR2-v20141005-0541-B267
> CordovaSim struggles with POST
> ------------------------------
>
> Key: JBIDE-18312
> URL: https://issues.jboss.org/browse/JBIDE-18312
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: browsersim
> Reporter: Burr Sutter
> Assignee: Ilya Buziuk
> Priority: Blocker
> Fix For: 4.2.0.CR2
>
> Attachments: hybrid1001.zip, post_error.png
>
>
> I will attach the project.
> The $.ajax post does not fire correctly from inside of CordovaSim - but it does via the iOS Simulator and from a real Android Device. Nothing in the error message on the client-side.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 6 months
[JBoss JIRA] (JBIDE-18367) Unable to choose a subsystem error when right-clicking on a stopped server (management profile)
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18367?page=com.atlassian.jira.plugi... ]
Martin Malina closed JBIDE-18367.
---------------------------------
Verified in JBDS 8.0.0.CR2 B486
> Unable to choose a subsystem error when right-clicking on a stopped server (management profile)
> -----------------------------------------------------------------------------------------------
>
> Key: JBIDE-18367
> URL: https://issues.jboss.org/browse/JBIDE-18367
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.2.0.CR1
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Priority: Critical
> Fix For: 4.2.0.CR2
>
>
> When you right-click on a stopped EAP6/WF8/AS7 server that uses the management profile, you'll get two identical errors thrown:
> {code}
> !ENTRY org.jboss.ide.eclipse.as.wtp.core 4 0 2014-09-17 12:29:08.536
> !MESSAGE Unable to choose a subsystem. Multiple subsystems found for servertype org.jboss.ide.eclipse.as.eap.61 and system type deploymentOptions
> !ENTRY org.jboss.ide.eclipse.as.wtp.core 4 0 2014-09-17 12:29:08.538
> !MESSAGE Unable to choose a subsystem. Multiple subsystems found for servertype org.jboss.ide.eclipse.as.eap.61 and system type deploymentOptions
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 6 months
[JBoss JIRA] (JBIDE-18373) Error when trying to publish seam project to EAP 6.3 in management profile
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18373?page=com.atlassian.jira.plugi... ]
Martin Malina closed JBIDE-18373.
---------------------------------
Closing this jira - another one was created for the remaining part.
> Error when trying to publish seam project to EAP 6.3 in management profile
> --------------------------------------------------------------------------
>
> Key: JBIDE-18373
> URL: https://issues.jboss.org/browse/JBIDE-18373
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.2.0.CR1
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Priority: Blocker
> Fix For: 4.2.0.CR2
>
> Attachments: seam-publish.png, seam-remote.png
>
>
> When I try to deploy a seam web project to a remote EAP 6.3 server, it takes a few minutes (expected - big seam lib) and then fails (not expected) with this error:
> {code}
> !ENTRY org.jboss.ide.eclipse.as.core 4 1644298251 2014-09-17 15:47:40.273
> !MESSAGE Deployment of module seamproj has failed
> !SUBENTRY 1 org.jboss.ide.eclipse.as.management.as71 4 0 2014-09-17 15:47:40.273
> !MESSAGE The operation DEPLOY for unit seamproj.war was rolled back
> !ENTRY org.jboss.ide.eclipse.as.wtp.core 4 1644298249 2014-09-17 15:47:55.797
> !MESSAGE Error renaming /Users/rasp/jbossqa/runtimes/jboss-eap-6.3.0/standalone/tmp/tmp7639865478274379783.jar to /Users/rasp/jbossqa/runtimes/jboss-eap-6.3.0/standalone/deployments/seamproj.war/WEB-INF/lib/jboss-seam.jar.
> This may be caused by your server's temporary deploy directory being on a different filesystem than the final destination.
> You may adjust these settings in the server editor.
> {code}
> This is the server console on the remote host:
> {code}
> 15:47:37,811 INFO [org.jboss.as.repository] (management-handler-thread - 1) JBAS014900: Content added at location /home/rasp/jbossqa/runtimes/jboss-eap-6.3.0/standalone/data/content/ca/f4ac569df88605a785004d5f7683a20e809753/content
> 15:47:37,836 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015876: Starting deployment of "seamproj.war" (runtime-name: "seamproj.war")
> 15:47:39,474 INFO [org.jboss.as.jpa] (MSC service thread 1-2) JBAS011401: Read persistence.xml for seamproj
> 15:47:39,639 WARN [org.jboss.as.dependency.private] (MSC service thread 1-3) JBAS018567: Deployment "deployment.seamproj.war" is using a private module ("com.sun.jsf-impl:main") which may be changed or removed in future versions without notice.
> 15:47:39,639 WARN [org.jboss.as.dependency.private] (MSC service thread 1-3) JBAS018567: Deployment "deployment.seamproj.war" is using a private module ("com.sun.jsf-impl:main") which may be changed or removed in future versions without notice.
> 15:47:39,640 WARN [org.jboss.as.dependency.unsupported] (MSC service thread 1-3) JBAS018568: Deployment "deployment.seamproj.war" is using an unsupported module ("org.dom4j:main") which may be changed or removed in future versions without notice.
> 15:47:39,640 WARN [org.jboss.as.dependency.unsupported] (MSC service thread 1-3) JBAS018568: Deployment "deployment.seamproj.war" is using an unsupported module ("org.dom4j:main") which may be changed or removed in future versions without notice.
> 15:47:39,800 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-3) JNDI bindings for session bean named EjbSynchronizations in deployment unit deployment "seamproj.war" are as follows:
> java:global/seamproj/EjbSynchronizations!org.jboss.seam.transaction.LocalEjbSynchronizations
> java:app/seamproj/EjbSynchronizations!org.jboss.seam.transaction.LocalEjbSynchronizations
> java:module/EjbSynchronizations!org.jboss.seam.transaction.LocalEjbSynchronizations
> java:global/seamproj/EjbSynchronizations
> java:app/seamproj/EjbSynchronizations
> java:module/EjbSynchronizations
> 15:47:39,801 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-3) JNDI bindings for session bean named TimerServiceDispatcher in deployment unit deployment "seamproj.war" are as follows:
> java:global/seamproj/TimerServiceDispatcher!org.jboss.seam.async.LocalTimerServiceDispatcher
> java:app/seamproj/TimerServiceDispatcher!org.jboss.seam.async.LocalTimerServiceDispatcher
> java:module/TimerServiceDispatcher!org.jboss.seam.async.LocalTimerServiceDispatcher
> java:global/seamproj/TimerServiceDispatcher
> java:app/seamproj/TimerServiceDispatcher
> java:module/TimerServiceDispatcher
> 15:47:39,981 WARN [org.jboss.weld.deployer] (MSC service thread 1-3) JBAS016012: Deployment deployment "seamproj.war" contains CDI annotations but beans.xml was not found.
> 15:47:40,109 ERROR [org.jboss.as.server] (management-handler-thread - 1) JBAS015870: Deploy of deployment "seamproj.war" was rolled back with the following failure message: {"JBAS014771: Services with missing/unavailable dependencies" => ["jboss.persistenceunit.\"seamproj.war#seamproj\" is missing [jboss.naming.context.java.seamprojDatasource]"]}
> 15:47:40,161 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015877: Stopped deployment seamproj.war (runtime-name: seamproj.war) in 51ms
> 15:47:40,169 INFO [org.jboss.as.controller] (management-handler-thread - 1) JBAS014774: Service status report
> JBAS014775: New missing/unsatisfied dependencies:
> service jboss.deployment.unit."seamproj.war".component.EjbSynchronizations.CREATE (missing) dependents: [service jboss.deployment.unit."seamproj.war".component.EjbSynchronizations.START]
> service jboss.deployment.unit."seamproj.war".component.EjbSynchronizations.START (missing) dependents: [service jboss.deployment.unit."seamproj.war".moduleDeploymentRuntimeInformationStart, service jboss.web.deployment.default-host./seamproj, service jboss.deployment.unit."seamproj.war".deploymentCompleteService]
> service jboss.deployment.unit."seamproj.war".component.EjbSynchronizations.VIEW."org.jboss.seam.transaction.LocalEjbSynchronizations".LOCAL (missing) dependents: [service jboss.deployment.unit."seamproj.war".component.EjbSynchronizations.START]
> service jboss.deployment.unit."seamproj.war".component.TimerServiceDispatcher.CREATE (missing) dependents: [service jboss.deployment.unit."seamproj.war".component.TimerServiceDispatcher.START]
> service jboss.deployment.unit."seamproj.war".component.TimerServiceDispatcher.START (missing) dependents: [service jboss.deployment.unit."seamproj.war".moduleDeploymentRuntimeInformationStart, service jboss.web.deployment.default-host./seamproj, service jboss.deployment.unit."seamproj.war".deploymentCompleteService]
> service jboss.deployment.unit."seamproj.war".component.TimerServiceDispatcher.VIEW."org.jboss.seam.async.LocalTimerServiceDispatcher".LOCAL (missing) dependents: [service jboss.deployment.unit."seamproj.war".component.TimerServiceDispatcher.START]
> service jboss.deployment.unit."seamproj.war".component.TimerServiceDispatcher.ejb3.timerService (missing) dependents: [service jboss.deployment.unit."seamproj.war".component.TimerServiceDispatcher.START]
> service jboss.deployment.unit."seamproj.war".component."com.sun.faces.config.ConfigureListener".CREATE (missing) dependents: [service jboss.deployment.unit."seamproj.war".component."com.sun.faces.config.ConfigureListener".START]
> service jboss.deployment.unit."seamproj.war".component."com.sun.faces.config.ConfigureListener".START (missing) dependents: [service jboss.web.deployment.default-host./seamproj, service jboss.deployment.unit."seamproj.war".deploymentCompleteService]
> service jboss.deployment.unit."seamproj.war".component."javax.faces.webapp.FacesServlet".CREATE (missing) dependents: [service jboss.deployment.unit."seamproj.war".component."javax.faces.webapp.FacesServlet".START]
> service jboss.deployment.unit."seamproj.war".component."javax.faces.webapp.FacesServlet".START (missing) dependents: [service jboss.web.deployment.default-host./seamproj, service jboss.deployment.unit."seamproj.war".deploymentCompleteService]
> service jboss.deployment.unit."seamproj.war".component."javax.faces.webapp.FacetTag".CREATE (missing) dependents: [service jboss.deployment.unit."seamproj.war".component."javax.faces.webapp.FacetTag".START]
> service jboss.deployment.unit."seamproj.war".component."javax.faces.webapp.FacetTag".START (missing) dependents: [service jboss.web.deployment.default-host./seamproj, service jboss.deployment.unit."seamproj.war".deploymentCompleteService]
> service jboss.deployment.unit."seamproj.war".component."javax.servlet.jsp.jstl.tlv.PermittedTaglibsTLV".CREATE (missing) dependents: [service jboss.deployment.unit."seamproj.war".component."javax.servlet.jsp.jstl.tlv.PermittedTaglibsTLV".START]
> service jboss.deployment.unit."seamproj.war".component."javax.servlet.jsp.jstl.tlv.PermittedTaglibsTLV".START (missing) dependents: [service jboss.web.deployment.default-host./seamproj, service jboss.deployment.unit."seamproj.war".deploymentCompleteService]
> service jboss.deployment.unit."seamproj.war".component."javax.servlet.jsp.jstl.tlv.ScriptFreeTLV".CREATE (missing) dependents: [service jboss.deployment.unit."seamproj.war".component."javax.servlet.jsp.jstl.tlv.ScriptFreeTLV".START]
> service jboss.deployment.unit."seamproj.war".component."javax.servlet.jsp.jstl.tlv.ScriptFreeTLV".START (missing) dependents: [service jboss.web.deployment.default-host./seamproj, service jboss.deployment.unit."seamproj.war".deploymentCompleteService]
> service jboss.deployment.unit."seamproj.war".component."managed-bean.org.richfaces.VersionBean".CREATE (missing) dependents: [service jboss.deployment.unit."seamproj.war".component."managed-bean.org.richfaces.VersionBean".START]
> service jboss.deployment.unit."seamproj.war".component."managed-bean.org.richfaces.VersionBean".START (missing) dependents: [service jboss.web.deployment.default-host./seamproj, service jboss.deployment.unit."seamproj.war".deploymentCompleteService]
> service jboss.deployment.unit."seamproj.war".component."managed-bean.org.richfaces.skin.SkinBean".CREATE (missing) dependents: [service jboss.deployment.unit."seamproj.war".component."managed-bean.org.richfaces.skin.SkinBean".START]
> service jboss.deployment.unit."seamproj.war".component."managed-bean.org.richfaces.skin.SkinBean".START (missing) dependents: [service jboss.web.deployment.default-host./seamproj, service jboss.deployment.unit."seamproj.war".deploymentCompleteService]
> service jboss.deployment.unit."seamproj.war".component."org.apache.catalina.servlets.DefaultServlet".CREATE (missing) dependents: [service jboss.deployment.unit."seamproj.war".component."org.apache.catalina.servlets.DefaultServlet".START]
> service jboss.deployment.unit."seamproj.war".component."org.apache.catalina.servlets.DefaultServlet".START (missing) dependents: [service jboss.web.deployment.default-host./seamproj, service jboss.deployment.unit."seamproj.war".deploymentCompleteService]
> service jboss.deployment.unit."seamproj.war".component."org.apache.jasper.servlet.JspServlet".CREATE (missing) dependents: [service jboss.deployment.unit."seamproj.war".component."org.apache.jasper.servlet.JspServlet".START]
> service jboss.deployment.unit."seamproj.war".component."org.apache.jasper.servlet.JspServlet".START (missing) dependents: [service jboss.web.deployment.default-host./seamproj, service jboss.deployment.unit."seamproj.war".deploymentCompleteService]
> service jboss.deployment.unit."seamproj.war".component."org.jboss.seam.servlet.SeamFilter".CREATE (missing) dependents: [service jboss.deployment.unit."seamproj.war".component."org.jboss.seam.servlet.SeamFilter".START]
> service jboss.deployment.unit."seamproj.war".component."org.jboss.seam.servlet.SeamFilter".START (missing) dependents: [service jboss.web.deployment.default-host./seamproj, service jboss.deployment.unit."seamproj.war".deploymentCompleteService]
> service jboss.deployment.unit."seamproj.war".component."org.jboss.seam.servlet.SeamListener".CREATE (missing) dependents: [service jboss.deployment.unit."seamproj.war".component."org.jboss.seam.servlet.SeamListener".START]
> service jboss.deployment.unit."seamproj.war".component."org.jboss.seam.servlet.SeamListener".START (missing) dependents: [service jboss.web.deployment.default-host./seamproj, service jboss.deployment.unit."seamproj.war".deploymentCompleteService]
> service jboss.deployment.unit."seamproj.war".component."org.jboss.seam.servlet.SeamResourceServlet".CREATE (missing) dependents: [service jboss.deployment.unit."seamproj.war".component."org.jboss.seam.servlet.SeamResourceServlet".START]
> service jboss.deployment.unit."seamproj.war".component."org.jboss.seam.servlet.SeamResourceServlet".START (missing) dependents: [service jboss.web.deployment.default-host./seamproj, service jboss.deployment.unit."seamproj.war".deploymentCompleteService]
> service jboss.deployment.unit."seamproj.war".jndiDependencyService (missing) dependents: [service jboss.deployment.unit."seamproj.war".component."org.apache.jasper.servlet.JspServlet".START, service jboss.deployment.unit."seamproj.war".component."javax.servlet.jsp.jstl.tlv.PermittedTaglibsTLV".START, service jboss.web.deployment.default-host./seamproj, service jboss.deployment.unit."seamproj.war".component."javax.faces.webapp.FacesServlet".START, JBAS014799: ... and 12 more ]
> service jboss.deployment.unit."seamproj.war".moduleDeploymentRuntimeInformation (missing) dependents: [service jboss.deployment.unit."seamproj.war".component.TimerServiceDispatcher.START, service jboss.deployment.unit."seamproj.war".moduleDeploymentRuntimeInformationStart, service jboss.deployment.unit."seamproj.war".component.EjbSynchronizations.START]
> service jboss.naming.context.java.module.seamproj.seamproj.env."org.jboss.seam.async.TimerServiceDispatcher".timerService (missing) dependents: [service jboss.deployment.unit."seamproj.war".component.TimerServiceDispatcher.START]
> service jboss.naming.context.java.seamprojDatasource (missing) dependents: [service jboss.persistenceunit."seamproj.war#seamproj"]
> service jboss.persistenceunit."seamproj.war#seamproj" (missing) dependents: [service jboss.deployment.unit."seamproj.war".component."org.apache.jasper.servlet.JspServlet".START, service jboss.naming.context.java.seamprojEntityManagerFactory, service jboss.deployment.unit."seamproj.war".component."javax.servlet.jsp.jstl.tlv.PermittedTaglibsTLV".START, service jboss.deployment.unit."seamproj.war".deploymentCompleteService, JBAS014799: ... and 14 more ]
> service jboss.web.deployment.default-host./seamproj (missing) dependents: [service jboss.deployment.unit."seamproj.war".deploymentCompleteService]
> service jboss.web.deployment.default-host./seamproj.realm (missing) dependents: [service jboss.web.deployment.default-host./seamproj, service jboss.deployment.unit."seamproj.war".deploymentCompleteService]
> {code}
> So clearly the deployment is incomplete on the server. In fact, the first line says that new content was added to /home/rasp/jbossqa/runtimes/jboss-eap-6.3.0/standalone/data/content/ca/f4ac569df88605a785004d5f7683a20e809753/content but this directory is empty.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 6 months
[JBoss JIRA] (JBIDE-18506) Usage plugin sometimes locks JBT/JBDS
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18506?page=com.atlassian.jira.plugi... ]
Alexey Kazakov commented on JBIDE-18506:
----------------------------------------
Anyway, it's too risky to make big changes in how loading/initiolization usage and its settings in 4.2.0.
This PR is simple and safe enough though.
> Usage plugin sometimes locks JBT/JBDS
> -------------------------------------
>
> Key: JBIDE-18506
> URL: https://issues.jboss.org/browse/JBIDE-18506
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: usage
> Affects Versions: 4.2.0.CR1
> Reporter: Snjezana Peco
> Assignee: Alexey Kazakov
> Priority: Blocker
> Labels: respin-a
> Fix For: 4.2.0.CR2
>
> Attachments: usagestacktrace.out
>
>
> JBossToolsUsageActivator initializes settings when starting and calls
> AbstractEclipseEnvironment.initScreenSettings()
> that uses the Display.syncExec method
> which causes JBT/JBDS to freeze. The issue isn't always reproducible, but it often happens when starting JBDS/JBT in a new workspace.
> While I was testing JBIDE-16379, I reproduced it each time when I started Eclipse 4.4.1/JBT 4.2.0.CR1 in a new workspace.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 6 months
[JBoss JIRA] (JBIDE-18527) "rm -rf project" in Forge Console doesn't delete project
by Pavol Srna (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18527?page=com.atlassian.jira.plugi... ]
Pavol Srna updated JBIDE-18527:
-------------------------------
Priority: Critical (was: Major)
> "rm -rf project" in Forge Console doesn't delete project
> --------------------------------------------------------
>
> Key: JBIDE-18527
> URL: https://issues.jboss.org/browse/JBIDE-18527
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: forge
> Affects Versions: 4.2.0.CR2
> Reporter: Pavol Srna
> Priority: Critical
> Fix For: 4.2.0.CR2
>
>
> {code}
> org.eclipse.core.internal.resources.ResourceException: Errors occurred while refreshing resources with the local file system.
> at org.eclipse.core.internal.localstore.FileSystemResourceManager.refreshResource(FileSystemResourceManager.java:923)
> at org.eclipse.core.internal.localstore.FileSystemResourceManager.refresh(FileSystemResourceManager.java:904)
> at org.eclipse.core.internal.localstore.FileSystemResourceManager.refreshRoot(FileSystemResourceManager.java:951)
> at org.eclipse.core.internal.localstore.FileSystemResourceManager.refresh(FileSystemResourceManager.java:897)
> at org.eclipse.core.internal.resources.Resource.refreshLocal(Resource.java:1705)
> at org.jboss.tools.forge.ui.internal.cli.CommandLineListener.refreshResource(CommandLineListener.java:315)
> at org.jboss.tools.forge.ui.internal.cli.CommandLineListener.refresh(CommandLineListener.java:129)
> at org.jboss.tools.forge.ui.internal.cli.CommandLineListener.access$2(CommandLineListener.java:126)
> at org.jboss.tools.forge.ui.internal.cli.CommandLineListener$1.run(CommandLineListener.java:86)
> 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:483)
> 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)
> Contains: The project description file (.project) for 'jboss-as-kitchensink-html5-mobile' is missing. This file contains important information about the project. The project will not function properly until this file is restored.
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 6 months