[JBoss JIRA] (JBIDE-15402) Doubled warnings Multiple JAX-RS Activators
by Radoslav Rábara (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15402?page=com.atlassian.jira.plugi... ]
Radoslav Rábara updated JBIDE-15402:
------------------------------------
Fix Version/s: 4.1.1.Alpha2
(was: 4.2.0.Alpha1)
> Doubled warnings Multiple JAX-RS Activators
> -------------------------------------------
>
> Key: JBIDE-15402
> URL: https://issues.jboss.org/browse/JBIDE-15402
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: webservices
> Affects Versions: 4.1.0.Final
> Reporter: Radoslav Rábara
> Assignee: Max Rydahl Andersen
> Labels: jax-rs, warning_messages, webservices
> Fix For: 4.1.1.Alpha2
>
> Attachments: jax-rs warnings.jpg
>
>
> After creating multiple JAX-RS Activators in Dynamic Web Project with JAX-RS support, there are doubled warnings ("Multiple JAX-RS Activators are defined for the project.") for each activator.
--
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, 3 months
[JBoss JIRA] (JBIDE-15402) Doubled warnings Multiple JAX-RS Activators
by Radoslav Rábara (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15402?page=com.atlassian.jira.plugi... ]
Radoslav Rábara closed JBIDE-15402.
-----------------------------------
Fix Version/s: (was: 4.1.1.Alpha2)
Resolution: Done
> Doubled warnings Multiple JAX-RS Activators
> -------------------------------------------
>
> Key: JBIDE-15402
> URL: https://issues.jboss.org/browse/JBIDE-15402
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: webservices
> Affects Versions: 4.1.0.Final
> Reporter: Radoslav Rábara
> Assignee: Max Rydahl Andersen
> Labels: jax-rs, warning_messages, webservices
> Fix For: 4.2.0.Alpha1
>
> Attachments: jax-rs warnings.jpg
>
>
> After creating multiple JAX-RS Activators in Dynamic Web Project with JAX-RS support, there are doubled warnings ("Multiple JAX-RS Activators are defined for the project.") for each activator.
--
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, 3 months
[JBoss JIRA] (JBIDE-16588) Remote EAP 6.2 fails to stop
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16588?page=com.atlassian.jira.plugi... ]
Martin Malina reassigned JBIDE-16588:
-------------------------------------
Assignee: Rob Stryker (was: Martin Malina)
Now I cannot even start the remote EAP 6.2 (without management port enabled). I get a NPE.
> Remote EAP 6.2 fails to stop
> ----------------------------
>
> Key: JBIDE-16588
> URL: https://issues.jboss.org/browse/JBIDE-16588
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.2.0.Alpha2
> Environment: JBDS 8.0.0.Alpha2a B70
> EAP 6.2.0.GA
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Priority: Critical
> Fix For: 4.2.0.Beta1
>
> Attachments: remote-server-stop-error.png, rse-server-start-npe.png
>
>
> When I create a remote EAP 6.2 server (ssh connection) without using the management port, the server starts and deploys ok, but when I try to stop it, I get this error:
> {code}
> !ENTRY org.eclipse.wst.server.core 4 0 2014-02-14 16:44:14.239
> !MESSAGE Server JBoss EAP 6.2 Server marvin failed to stop.
> {code}
> Very informative ;)
> !remote-server-stop-error.png!
> The server remains "Started" and the java process on the remote machine is still running. If I try it again and again, the result is the same. So the only way of stopping the server is killing the java process on the remote machine. But Eclipse will still show Started, so need a restart.
--
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, 3 months
[JBoss JIRA] (JBIDE-16588) Remote EAP 6.2 fails to stop
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16588?page=com.atlassian.jira.plugi... ]
Martin Malina updated JBIDE-16588:
----------------------------------
Attachment: rse-server-start-npe.png
!rse-server-start-npe.png!
> Remote EAP 6.2 fails to stop
> ----------------------------
>
> Key: JBIDE-16588
> URL: https://issues.jboss.org/browse/JBIDE-16588
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.2.0.Alpha2
> Environment: JBDS 8.0.0.Alpha2a B70
> EAP 6.2.0.GA
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Priority: Critical
> Fix For: 4.2.0.Beta1
>
> Attachments: remote-server-stop-error.png, rse-server-start-npe.png
>
>
> When I create a remote EAP 6.2 server (ssh connection) without using the management port, the server starts and deploys ok, but when I try to stop it, I get this error:
> {code}
> !ENTRY org.eclipse.wst.server.core 4 0 2014-02-14 16:44:14.239
> !MESSAGE Server JBoss EAP 6.2 Server marvin failed to stop.
> {code}
> Very informative ;)
> !remote-server-stop-error.png!
> The server remains "Started" and the java process on the remote machine is still running. If I try it again and again, the result is the same. So the only way of stopping the server is killing the java process on the remote machine. But Eclipse will still show Started, so need a restart.
--
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, 3 months
[JBoss JIRA] (JBIDE-16588) Remote EAP 6.2 fails to stop
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16588?page=com.atlassian.jira.plugi... ]
Martin Malina edited comment on JBIDE-16588 at 3/6/14 5:07 AM:
---------------------------------------------------------------
Now I cannot even start the remote EAP 6.2 (with or without management port enabled). I get a NPE.
was (Author: mmalina):
Now I cannot even start the remote EAP 6.2 (without management port enabled). I get a NPE.
> Remote EAP 6.2 fails to stop
> ----------------------------
>
> Key: JBIDE-16588
> URL: https://issues.jboss.org/browse/JBIDE-16588
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.2.0.Alpha2
> Environment: JBDS 8.0.0.Alpha2a B70
> EAP 6.2.0.GA
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Priority: Critical
> Fix For: 4.2.0.Beta1
>
> Attachments: remote-server-stop-error.png, rse-server-start-npe.png
>
>
> When I create a remote EAP 6.2 server (ssh connection) without using the management port, the server starts and deploys ok, but when I try to stop it, I get this error:
> {code}
> !ENTRY org.eclipse.wst.server.core 4 0 2014-02-14 16:44:14.239
> !MESSAGE Server JBoss EAP 6.2 Server marvin failed to stop.
> {code}
> Very informative ;)
> !remote-server-stop-error.png!
> The server remains "Started" and the java process on the remote machine is still running. If I try it again and again, the result is the same. So the only way of stopping the server is killing the java process on the remote machine. But Eclipse will still show Started, so need a restart.
--
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, 3 months
[JBoss JIRA] (JBIDE-15162) User must install and reference an installed local EAP instance to create a remote server definition
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15162?page=com.atlassian.jira.plugi... ]
Martin Malina commented on JBIDE-15162:
---------------------------------------
Sorry, I was wrong. You can change the path. But I simply didn't see it. That's probably because there is something filled in by default and I didn't notice I had to change it. So while you're working on this already, can you please change the handling of the Remote server home field? It should be empty by default and the user shouldn't be allowed to proceed (Next or Finish) unless they fill in the path (either using the Browse button or manually).
> User must install and reference an installed local EAP instance to create a remote server definition
> ----------------------------------------------------------------------------------------------------
>
> Key: JBIDE-15162
> URL: https://issues.jboss.org/browse/JBIDE-15162
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.1.0.CR1
> Reporter: Len DiMaggio
> Assignee: Rob Stryker
> Priority: Blocker
> Fix For: 4.2.0.Beta1
>
> Attachments: Van_1.png, Van_2.png, Van_3.png
>
>
> See the attached screenshots - it seems counter-intuitive for a user to have to reference an installed local EAP instance to too create a remote server definition
> - open the "Servers" tab (where servers are stopped/started)
> - click in the area
> - now right mouse click and select "New->Server"
> - select JBoss Middleware EAP 6.1, click next
> - this next panel requires you to enter a directory to a local EAP install
--
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, 3 months
[JBoss JIRA] (JBDS-2932) Verify VJET/0.10.0.201309201624 with JBDS 8.0
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBDS-2932?page=com.atlassian.jira.plugin.... ]
Marián Labuda commented on JBDS-2932:
-------------------------------------
JBIDE-16164 persists. Also found that assist help or hoover help (or what does it call) is black text on dark gray background. It's just for VJET's elements. Also it is, as you can see a bit cut off from bottom side and need to press F2 key to focus and scroll down. I think it is a bit annoying.
Otherwise it looks ok. No more issues found.
Verified in JBDS 8.0.0.Alpha2b
Build id: Alpha2-v20140214-1707-B71
> Verify VJET/0.10.0.201309201624 with JBDS 8.0
> ---------------------------------------------
>
> Key: JBDS-2932
> URL: https://issues.jboss.org/browse/JBDS-2932
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Sub-task
> Security Level: Public(Everyone can see)
> Components: 3rd-party-certification
> Affects Versions: 8.0.0.Beta1
> Reporter: Len DiMaggio
> Assignee: Marián Labuda
> Fix For: 8.0.0.Beta1
>
> Attachments: hoover_doc.png
>
>
> See: https://issues.jboss.org/browse/JBIDE-15677
--
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, 3 months
[JBoss JIRA] (JBIDE-16696) IllegalStateException when Arquillian deployment uses Maven resolver
by Karel Piwko (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16696?page=com.atlassian.jira.plugi... ]
Karel Piwko commented on JBIDE-16696:
-------------------------------------
As for the ISE, I've filled https://issues.jboss.org/browse/SHRINKRES-171 to make message more appropriate.
bq. there is no way to tell arquillian to use another dir than current working direcotry ?
By default, all relative paths are relative to current directory. Scanning could not fix that. However, what we could do is to use Maven.configureResolverViaPlugin(). This way Eclipse/JBDS will need just to setup a few system properties (pom.xml file, settings.xml file, active profiles etc) and user does not have to handle with it anymore.
See *ShrinkWrap Resolver Maven Plugin* - https://github.com/shrinkwrap/resolver/blob/master/README.asciidoc
[~snjeza] where did you got your pom.xml file? Depchain should be used, see *adding shrinkwrap resolvers to your project* at - https://github.com/shrinkwrap/resolver/blob/master/README.asciidoc - this is also related to missing Service.
> 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, 3 months