[JBoss JIRA] (JBIDE-14964) LiveReload doesn't reload when JRebel is used, because resources are "never published automatically"
by Lukáš Fryč (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14964?page=com.atlassian.jira.plugi... ]
Lukáš Fryč updated JBIDE-14964:
-------------------------------
Description:
When JRebel is used together with LiveReload, "Never Publish Automatically" needs to be turned on in Publishing setup of Server Runtime (AS/EAP) settings.
In this mode, LiveReload does not work, because new resources are never published according to the IDE.
However JRebel reloads those resources in a background.
----
In the opposite case ("Automatically publish after resource change"), I'm getting "Concurrent resource modification" error occasionally which might not be related to JRebel usage.
was:
When JRebel is used together with LiveReload, "Never Publish Automatically" needs to be turned on in Publishing setup of Server Runtime (AS/EAP) settings.
In this mode, LiveReload does not work, because new resources are never published according to the IDE.
However JRebel reloads those resources in a background.
----
In the opposite case ("Automatically publish after resource change"), I'm getting "Concurrent resource modification" error occasionally.
> LiveReload doesn't reload when JRebel is used, because resources are "never published automatically"
> ----------------------------------------------------------------------------------------------------
>
> Key: JBIDE-14964
> URL: https://issues.jboss.org/browse/JBIDE-14964
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: livereload
> Affects Versions: 4.1.0.Beta1
> Reporter: Lukáš Fryč
> Assignee: Xavier Coulon
> Priority: Critical
> Fix For: 4.2.x
>
>
> When JRebel is used together with LiveReload, "Never Publish Automatically" needs to be turned on in Publishing setup of Server Runtime (AS/EAP) settings.
> In this mode, LiveReload does not work, because new resources are never published according to the IDE.
> However JRebel reloads those resources in a background.
> ----
> In the opposite case ("Automatically publish after resource change"), I'm getting "Concurrent resource modification" error occasionally which might not be related to JRebel usage.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 1 month
[JBoss JIRA] (JBIDE-16696) IllegalStateException when Arquillian deployment uses Maven resolver
by Snjezana Peco (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16696?page=com.atlassian.jira.plugi... ]
Snjezana Peco reassigned JBIDE-16696:
-------------------------------------
Assignee: Snjezana Peco
> IllegalStateException when Arquillian deployment uses Maven resolver
> --------------------------------------------------------------------
>
> Key: JBIDE-16696
> URL: https://issues.jboss.org/browse/JBIDE-16696
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Affects Versions: 4.1.1.Final
> Reporter: Rich DiCroce
> Assignee: Snjezana Peco
>
> In an Arquillian test class, if the @Deployment method uses the ShrinkWrap Maven Resolver API, the method will be marked with the following warning and the Arquillian Cruiser view does not show the deployment:
> {noformat}
> java.lang.IllegalStateException: There is more then a one service for serviceClass org.jboss.shrinkwrap.resolver.api.maven.MavenResolverSystem(project=arquillian-bug-test)
> {noformat}
> There is no stack trace to indicate how the problem might be happening. At first, I thought this might be a ShrinkWrap bug, but this exception doesn't occur when I actually run the test. Eclipse shows only one implementation of MavenResolverSystem on the classpath.
> Example test class to reproduce the problem:
> {code}
> package test;
> import org.jboss.arquillian.container.test.api.Deployment;
> import org.jboss.arquillian.junit.Arquillian;
> import org.jboss.shrinkwrap.api.Archive;
> import org.jboss.shrinkwrap.api.ShrinkWrap;
> import org.jboss.shrinkwrap.api.spec.WebArchive;
> import org.jboss.shrinkwrap.resolver.api.maven.Maven;
> import org.junit.Test;
> import org.junit.runner.RunWith;
> @RunWith(Arquillian.class)
> public class ARQJBTBugTest {
> @Test
> public void test() {
>
> }
>
> @Deployment
> public static Archive<?> createDeployment() {
> return ShrinkWrap.create(WebArchive.class)
> .addAsLibraries(Maven.resolver()
> .loadPomFromFile("pom.xml")
> .importRuntimeDependencies()
> .resolve()
> .withTransitivity()
> .asFile());
> }
>
> }
> {code}
> And the POM to go with it:
> {code:xml}
> <project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
> <modelVersion>4.0.0</modelVersion>
> <groupId>com.lapis.throwaway</groupId>
> <artifactId>arquillian-bug-test</artifactId>
> <version>0.0.1-SNAPSHOT</version>
> <packaging>war</packaging>
> <properties>
> <project.build.sourceEncoding>
> UTF-8
> </project.build.sourceEncoding>
> <version.arquillian_core>1.1.3.Final</version.arquillian_core>
> </properties>
> <dependencies>
> <dependency>
> <groupId>junit</groupId>
> <artifactId>junit</artifactId>
> <version>4.10</version>
> <scope>test</scope>
> </dependency>
> <dependency>
> <groupId>org.jboss.arquillian.junit</groupId>
> <artifactId>arquillian-junit-container</artifactId>
> <scope>test</scope>
> </dependency>
> <dependency>
> <groupId>org.jboss.shrinkwrap.resolver</groupId>
> <artifactId>shrinkwrap-resolver-impl-maven-archive</artifactId>
> <scope>test</scope>
> </dependency>
> </dependencies>
> <dependencyManagement>
> <dependencies>
> <dependency>
> <groupId>org.jboss.arquillian</groupId>
> <artifactId>arquillian-bom</artifactId>
> <version>${version.arquillian_core}</version>
> <type>pom</type>
> <scope>import</scope>
> </dependency>
> </dependencies>
> </dependencyManagement>
> <build>
> <plugins>
> <plugin>
> <groupId>org.apache.maven.plugins</groupId>
> <artifactId>maven-compiler-plugin</artifactId>
> <version>2.5.1</version>
> <configuration>
> <source>1.7</source>
> <target>1.7</target>
> </configuration>
> </plugin>
> <plugin>
> <groupId>org.apache.maven.plugins</groupId>
> <artifactId>maven-surefire-plugin</artifactId>
> <version>2.12</version>
> </plugin>
> </plugins>
> </build>
> </project>
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 1 month
[JBoss JIRA] (JBIDE-16696) IllegalStateException when Arquillian deployment uses Maven resolver
by Snjezana Peco (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16696?page=com.atlassian.jira.plugi... ]
Snjezana Peco updated JBIDE-16696:
----------------------------------
Component/s: testing-tools
> IllegalStateException when Arquillian deployment uses Maven resolver
> --------------------------------------------------------------------
>
> Key: JBIDE-16696
> URL: https://issues.jboss.org/browse/JBIDE-16696
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: testing-tools
> Affects Versions: 4.1.1.Final
> Reporter: Rich DiCroce
> Assignee: Snjezana Peco
>
> In an Arquillian test class, if the @Deployment method uses the ShrinkWrap Maven Resolver API, the method will be marked with the following warning and the Arquillian Cruiser view does not show the deployment:
> {noformat}
> java.lang.IllegalStateException: There is more then a one service for serviceClass org.jboss.shrinkwrap.resolver.api.maven.MavenResolverSystem(project=arquillian-bug-test)
> {noformat}
> There is no stack trace to indicate how the problem might be happening. At first, I thought this might be a ShrinkWrap bug, but this exception doesn't occur when I actually run the test. Eclipse shows only one implementation of MavenResolverSystem on the classpath.
> Example test class to reproduce the problem:
> {code}
> package test;
> import org.jboss.arquillian.container.test.api.Deployment;
> import org.jboss.arquillian.junit.Arquillian;
> import org.jboss.shrinkwrap.api.Archive;
> import org.jboss.shrinkwrap.api.ShrinkWrap;
> import org.jboss.shrinkwrap.api.spec.WebArchive;
> import org.jboss.shrinkwrap.resolver.api.maven.Maven;
> import org.junit.Test;
> import org.junit.runner.RunWith;
> @RunWith(Arquillian.class)
> public class ARQJBTBugTest {
> @Test
> public void test() {
>
> }
>
> @Deployment
> public static Archive<?> createDeployment() {
> return ShrinkWrap.create(WebArchive.class)
> .addAsLibraries(Maven.resolver()
> .loadPomFromFile("pom.xml")
> .importRuntimeDependencies()
> .resolve()
> .withTransitivity()
> .asFile());
> }
>
> }
> {code}
> And the POM to go with it:
> {code:xml}
> <project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
> <modelVersion>4.0.0</modelVersion>
> <groupId>com.lapis.throwaway</groupId>
> <artifactId>arquillian-bug-test</artifactId>
> <version>0.0.1-SNAPSHOT</version>
> <packaging>war</packaging>
> <properties>
> <project.build.sourceEncoding>
> UTF-8
> </project.build.sourceEncoding>
> <version.arquillian_core>1.1.3.Final</version.arquillian_core>
> </properties>
> <dependencies>
> <dependency>
> <groupId>junit</groupId>
> <artifactId>junit</artifactId>
> <version>4.10</version>
> <scope>test</scope>
> </dependency>
> <dependency>
> <groupId>org.jboss.arquillian.junit</groupId>
> <artifactId>arquillian-junit-container</artifactId>
> <scope>test</scope>
> </dependency>
> <dependency>
> <groupId>org.jboss.shrinkwrap.resolver</groupId>
> <artifactId>shrinkwrap-resolver-impl-maven-archive</artifactId>
> <scope>test</scope>
> </dependency>
> </dependencies>
> <dependencyManagement>
> <dependencies>
> <dependency>
> <groupId>org.jboss.arquillian</groupId>
> <artifactId>arquillian-bom</artifactId>
> <version>${version.arquillian_core}</version>
> <type>pom</type>
> <scope>import</scope>
> </dependency>
> </dependencies>
> </dependencyManagement>
> <build>
> <plugins>
> <plugin>
> <groupId>org.apache.maven.plugins</groupId>
> <artifactId>maven-compiler-plugin</artifactId>
> <version>2.5.1</version>
> <configuration>
> <source>1.7</source>
> <target>1.7</target>
> </configuration>
> </plugin>
> <plugin>
> <groupId>org.apache.maven.plugins</groupId>
> <artifactId>maven-surefire-plugin</artifactId>
> <version>2.12</version>
> </plugin>
> </plugins>
> </build>
> </project>
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 1 month
[JBoss JIRA] (JBIDE-16696) IllegalStateException when Arquillian deployment uses Maven resolver
by Rich DiCroce (JIRA)
Rich DiCroce created JBIDE-16696:
------------------------------------
Summary: IllegalStateException when Arquillian deployment uses Maven resolver
Key: JBIDE-16696
URL: https://issues.jboss.org/browse/JBIDE-16696
Project: Tools (JBoss Tools)
Issue Type: Bug
Affects Versions: 4.1.1.Final
Reporter: Rich DiCroce
In an Arquillian test class, if the @Deployment method uses the ShrinkWrap Maven Resolver API, the method will be marked with the following warning and the Arquillian Cruiser view does not show the deployment:
{noformat}
java.lang.IllegalStateException: There is more then a one service for serviceClass org.jboss.shrinkwrap.resolver.api.maven.MavenResolverSystem(project=arquillian-bug-test)
{noformat}
There is no stack trace to indicate how the problem might be happening. At first, I thought this might be a ShrinkWrap bug, but this exception doesn't occur when I actually run the test. Eclipse shows only one implementation of MavenResolverSystem on the classpath.
Example test class to reproduce the problem:
{code}
package test;
import org.jboss.arquillian.container.test.api.Deployment;
import org.jboss.arquillian.junit.Arquillian;
import org.jboss.shrinkwrap.api.Archive;
import org.jboss.shrinkwrap.api.ShrinkWrap;
import org.jboss.shrinkwrap.api.spec.WebArchive;
import org.jboss.shrinkwrap.resolver.api.maven.Maven;
import org.junit.Test;
import org.junit.runner.RunWith;
@RunWith(Arquillian.class)
public class ARQJBTBugTest {
@Test
public void test() {
}
@Deployment
public static Archive<?> createDeployment() {
return ShrinkWrap.create(WebArchive.class)
.addAsLibraries(Maven.resolver()
.loadPomFromFile("pom.xml")
.importRuntimeDependencies()
.resolve()
.withTransitivity()
.asFile());
}
}
{code}
And the POM to go with it:
{code:xml}
<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
<modelVersion>4.0.0</modelVersion>
<groupId>com.lapis.throwaway</groupId>
<artifactId>arquillian-bug-test</artifactId>
<version>0.0.1-SNAPSHOT</version>
<packaging>war</packaging>
<properties>
<project.build.sourceEncoding>
UTF-8
</project.build.sourceEncoding>
<version.arquillian_core>1.1.3.Final</version.arquillian_core>
</properties>
<dependencies>
<dependency>
<groupId>junit</groupId>
<artifactId>junit</artifactId>
<version>4.10</version>
<scope>test</scope>
</dependency>
<dependency>
<groupId>org.jboss.arquillian.junit</groupId>
<artifactId>arquillian-junit-container</artifactId>
<scope>test</scope>
</dependency>
<dependency>
<groupId>org.jboss.shrinkwrap.resolver</groupId>
<artifactId>shrinkwrap-resolver-impl-maven-archive</artifactId>
<scope>test</scope>
</dependency>
</dependencies>
<dependencyManagement>
<dependencies>
<dependency>
<groupId>org.jboss.arquillian</groupId>
<artifactId>arquillian-bom</artifactId>
<version>${version.arquillian_core}</version>
<type>pom</type>
<scope>import</scope>
</dependency>
</dependencies>
</dependencyManagement>
<build>
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-compiler-plugin</artifactId>
<version>2.5.1</version>
<configuration>
<source>1.7</source>
<target>1.7</target>
</configuration>
</plugin>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-surefire-plugin</artifactId>
<version>2.12</version>
</plugin>
</plugins>
</build>
</project>
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 1 month
[JBoss JIRA] (JBIDE-16695) Arquillian deployment method detection does not consider Archive subclasses
by Rich DiCroce (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16695?page=com.atlassian.jira.plugi... ]
Rich DiCroce commented on JBIDE-16695:
--------------------------------------
I just discovered that this behavior also occurs if the @Deployment method is non-static.
> Arquillian deployment method detection does not consider Archive subclasses
> ---------------------------------------------------------------------------
>
> Key: JBIDE-16695
> URL: https://issues.jboss.org/browse/JBIDE-16695
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: testing-tools
> Affects Versions: 4.1.1.Final
> Reporter: Rich DiCroce
> Assignee: Snjezana Peco
> Fix For: 4.2.0.Beta1
>
>
> In an Arquillian test class, any method marked @Deployment that returns something other than Archive is not being detected. For example, this method is not detected by the tooling, despite the fact that WebArchive extends Archive:
> {code}
> @Deployment
> public static WebArchive createDeployment() {
> ...code to create deployment here...
> }
> {code}
> As a result, the deployment validation features do not work, and the Arquillian Cruiser view does not allow the archive to be browsed. Curiously, however, there is no warning about a missing @Deployment method.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 1 month
[JBoss JIRA] (JBIDE-16441) NPE in JSPProblemMarkerResolutionGenerator.getAddTLD() when getting quick fixes for html page in dynamic web project (no KB nature)
by Vlado Pakan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16441?page=com.atlassian.jira.plugi... ]
Vlado Pakan closed JBIDE-16441.
-------------------------------
Verified with JBDS 7.1.1.GA-v20140303-1841-B672
> NPE in JSPProblemMarkerResolutionGenerator.getAddTLD() when getting quick fixes for html page in dynamic web project (no KB nature)
> -----------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-16441
> URL: https://issues.jboss.org/browse/JBIDE-16441
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jsp/jsf/xml/html source editing
> Affects Versions: 4.1.1.Final
> Reporter: Victor Rubezhny
> Assignee: Victor Rubezhny
> Fix For: 4.1.2.CR1
>
>
> When trying to get quick fixes for some error in HTML page of dynamic web project that has no KB-nature set up, the following NPE occurs:
> {code}
> !ENTRY org.eclipse.ui 4 0 2014-02-05 21:03:21.007
> !MESSAGE Unhandled event loop exception
> !STACK 0
> org.eclipse.swt.SWTException: Failed to execute runnable (java.lang.NullPointerException)
> at org.eclipse.swt.SWT.error(SWT.java:4397)
> at org.eclipse.swt.SWT.error(SWT.java:4312)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:138)
> at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3717)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3366)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1113)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:997)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:138)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:610)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:567)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:124)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:354)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:181)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:601)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:636)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:591)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1450)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1426)
> Caused by: java.lang.NullPointerException
> at org.jboss.tools.jst.web.ui.action.JSPProblemMarkerResolutionGenerator.getAddTLD(JSPProblemMarkerResolutionGenerator.java:278)
> at org.jboss.tools.jst.web.ui.action.JSPProblemMarkerResolutionGenerator.findResolutions(JSPProblemMarkerResolutionGenerator.java:323)
> at org.jboss.tools.jst.web.ui.action.JSPProblemMarkerResolutionGenerator.getResolutions(JSPProblemMarkerResolutionGenerator.java:72)
> at org.eclipse.ui.internal.ide.registry.MarkerHelpRegistry.getResolutions(MarkerHelpRegistry.java:253)
> at org.jboss.tools.common.quickfix.MarkerAnnotationInfo.getMarkerProposals(MarkerAnnotationInfo.java:62)
> at org.jboss.tools.common.quickfix.MarkerAnnotationInfo.getCompletionProposals(MarkerAnnotationInfo.java:50)
> at org.jboss.tools.common.text.xml.xpl.MarkerProblemAnnotationHoverProcessor$MarkerAnnotationInformationControl.createContent(MarkerProblemAnnotationHoverProcessor.java:220)
> at org.jboss.tools.common.text.xml.xpl.MarkerProblemAnnotationHoverProcessor$MarkerAnnotationInformationControl.setInput(MarkerProblemAnnotationHoverProcessor.java:189)
> at org.eclipse.jface.text.AbstractInformationControlManager.internalShowInformationControl(AbstractInformationControlManager.java:1181)
> at org.eclipse.jface.text.AbstractInformationControlManager.presentInformation(AbstractInformationControlManager.java:1150)
> at org.eclipse.jface.text.AbstractHoverInformationControlManager.presentInformation(AbstractHoverInformationControlManager.java:902)
> at org.eclipse.jface.text.TextViewerHoverManager.doPresentInformation(TextViewerHoverManager.java:243)
> at org.eclipse.jface.text.TextViewerHoverManager$5.run(TextViewerHoverManager.java:233)
> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135)
> ... 24 more
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 1 month
[JBoss JIRA] (JBIDE-16618) CordovaSim doesn't work on Fedora 20
by Konstantin Marmalyukov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16618?page=com.atlassian.jira.plugi... ]
Konstantin Marmalyukov commented on JBIDE-16618:
------------------------------------------------
You don't need to do it. I thought you are using Fedora 20 just now. Having everything ok on Fedora 18 is good news. Thanks.
> CordovaSim doesn't work on Fedora 20
> ------------------------------------
>
> Key: JBIDE-16618
> URL: https://issues.jboss.org/browse/JBIDE-16618
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: browsersim
> Affects Versions: 4.1.1.Final
> Environment: Fedora 20. Fully updated. Sun JDK 1.7.0_51
> Reporter: Boleslaw Dawidowicz
> Assignee: Konstantin Marmalyukov
> Fix For: 4.2.0.Beta1
>
>
> Basically following burr's video:
> http://vimeo.com/82204444
> - Install JBoss Tools
> - Install Cordova/Hybrid stuff
> - Create simple hybrid app
> - "Run as CordovaSim"
> - CordovaSim doesn't show up. There is blank window visible for a second.
> Some additional hints:
> - Same behaviour on JBDS 7.1 with Cordova and Google Android plugings
> - BrowserSim seems to run fine - just opening it by clicking the button on the toolbar.
> - Cordova app works fine when deployed to actual android device or android emulator.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 1 month
[JBoss JIRA] (JBIDE-16618) CordovaSim doesn't work on Fedora 20
by Vlado Pakan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16618?page=com.atlassian.jira.plugi... ]
Vlado Pakan edited comment on JBIDE-16618 at 3/4/14 2:19 PM:
-------------------------------------------------------------
Right now I'm busy with verifying issues for JBT 4.1.2.CR1. I will try it tomorrow in case I will find Fedora 20 machine.
Works fine with JBT 4.1.2.CR1 on Fedora 18 x_64 KDE
was (Author: vpakan):
Right now I'm busy with verifying issues for JBT 4.1.2.CR1. I will try it tomorrow in case I will find Fedora 20 machine
> CordovaSim doesn't work on Fedora 20
> ------------------------------------
>
> Key: JBIDE-16618
> URL: https://issues.jboss.org/browse/JBIDE-16618
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: browsersim
> Affects Versions: 4.1.1.Final
> Environment: Fedora 20. Fully updated. Sun JDK 1.7.0_51
> Reporter: Boleslaw Dawidowicz
> Assignee: Konstantin Marmalyukov
> Fix For: 4.2.0.Beta1
>
>
> Basically following burr's video:
> http://vimeo.com/82204444
> - Install JBoss Tools
> - Install Cordova/Hybrid stuff
> - Create simple hybrid app
> - "Run as CordovaSim"
> - CordovaSim doesn't show up. There is blank window visible for a second.
> Some additional hints:
> - Same behaviour on JBDS 7.1 with Cordova and Google Android plugings
> - BrowserSim seems to run fine - just opening it by clicking the button on the toolbar.
> - Cordova app works fine when deployed to actual android device or android emulator.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 1 month
[JBoss JIRA] (JBIDE-16695) Arquillian deployment method detection does not consider Archive subclasses
by Snjezana Peco (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16695?page=com.atlassian.jira.plugi... ]
Snjezana Peco updated JBIDE-16695:
----------------------------------
Fix Version/s: 4.2.0.Alpha2
> Arquillian deployment method detection does not consider Archive subclasses
> ---------------------------------------------------------------------------
>
> Key: JBIDE-16695
> URL: https://issues.jboss.org/browse/JBIDE-16695
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: testing-tools
> Affects Versions: 4.1.1.Final
> Reporter: Rich DiCroce
> Assignee: Snjezana Peco
> Fix For: 4.2.0.Alpha2
>
>
> In an Arquillian test class, any method marked @Deployment that returns something other than Archive is not being detected. For example, this method is not detected by the tooling, despite the fact that WebArchive extends Archive:
> {code}
> @Deployment
> public static WebArchive createDeployment() {
> ...code to create deployment here...
> }
> {code}
> As a result, the deployment validation features do not work, and the Arquillian Cruiser view does not allow the archive to be browsed. Curiously, however, there is no warning about a missing @Deployment method.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 1 month