[JBoss JIRA] (JBIDE-24963) Create CDI 2 integration tests
by Zbyněk Červinka (Jira)
[ https://issues.jboss.org/browse/JBIDE-24963?page=com.atlassian.jira.plugi... ]
Zbyněk Červinka updated JBIDE-24963:
------------------------------------
Git Pull Request: https://github.com/jbosstools/jbosstools-integration-tests/pull/1947, https://github.com/jbosstools/jbosstools-integration-tests/pull/1949, https://github.com/jbosstools/jbosstools-integration-tests/pull/1954, https://github.com/jbosstools/jbosstools-integration-tests/pull/1957, https://github.com/jbosstools/jbosstools-integration-tests/pull/1958, https://github.com/jbosstools/jbosstools-integration-tests/pull/1959, https://github.com/jbosstools/jbosstools-integration-tests/pull/1960 (was: https://github.com/jbosstools/jbosstools-integration-tests/pull/1947, https://github.com/jbosstools/jbosstools-integration-tests/pull/1949, https://github.com/jbosstools/jbosstools-integration-tests/pull/1954, https://github.com/jbosstools/jbosstools-integration-tests/pull/1957, https://github.com/jbosstools/jbosstools-integration-tests/pull/1958, https://github.com/jbosstools/jbosstools-integration-tests/pull/1959)
> Create CDI 2 integration tests
> ------------------------------
>
> Key: JBIDE-24963
> URL: https://issues.jboss.org/browse/JBIDE-24963
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: cdi, integration-tests
> Affects Versions: 4.5.1.AM2
> Reporter: Lukáš Valach
> Assignee: Zbyněk Červinka
> Priority: Major
> Fix For: 4.13.x
>
>
> The support for CDI 2.0 has been added recently, see JBIDE-24949.
> Spec:
> http://docs.jboss.org/cdi/spec/2.0/cdi-spec.html
> Change log:
> https://issues.jboss.org/secure/ReleaseNote.jspa?version=12325406&styleNa...
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 8 months
[JBoss JIRA] (JBIDE-12283) Unable to connect to SOAP web service in IPv6 environment
by Josef Kopriva (Jira)
[ https://issues.jboss.org/browse/JBIDE-12283?page=com.atlassian.jira.plugi... ]
Josef Kopriva closed JBIDE-12283.
---------------------------------
Resolution: Done
Closing as EAP issue.
> Unable to connect to SOAP web service in IPv6 environment
> ---------------------------------------------------------
>
> Key: JBIDE-12283
> URL: https://issues.jboss.org/browse/JBIDE-12283
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: upstream, webservices
> Affects Versions: 3.3.0.Final
> Environment: Two Fedora 17 machines connected to each other with IPv6 protocol, JBDS 5.0.0 GA, EAP 6
> Reporter: Jaroslav Jankovič
> Assignee: Brian Fitzpatrick
> Priority: Blocker
> Labels: jax-ws
> Fix For: LATER, 4.1.x, 4.2.x
>
>
> When I was trying to obtain the content of WSDL file of deployed SOAP WS, an error was thrown in error log and no content could be viewed:
> {code}
> 08:45:31,450 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/prj].[HelloWorld]] (http-/fc00:0:0:0:0:0:0:1%2:8080-1) Servlet.service() for servlet HelloWorld threw exception: javax.servlet.ServletException: Cannot obtain destination for: /prj/HelloWorld
> at org.jboss.wsf.stack.cxf.RequestHandlerImpl.findDestination(RequestHandlerImpl.java:164)
> at org.jboss.wsf.stack.cxf.RequestHandlerImpl.handleHttpRequest(RequestHandlerImpl.java:81)
> at org.jboss.wsf.stack.cxf.transport.ServletHelper.callRequestHandler(ServletHelper.java:169)
> at org.jboss.wsf.stack.cxf.CXFServletExt.invoke(CXFServletExt.java:87)
> at org.apache.cxf.transport.servlet.AbstractHTTPServlet.handleRequest(AbstractHTTPServlet.java:185)
> at org.apache.cxf.transport.servlet.AbstractHTTPServlet.doGet(AbstractHTTPServlet.java:113)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:734) [jboss-servlet-api_3.0_spec-1.0.1.Final-redhat-1.jar:1.0.1.Final-redhat-1]
> at org.jboss.wsf.stack.cxf.CXFServletExt.service(CXFServletExt.java:135)
> at org.jboss.wsf.spi.deployment.WSFServlet.service(WSFServlet.java:140) [jbossws-spi-2.0.3.GA-redhat-1.jar:2.0.3.GA-redhat-1]
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:847) [jboss-servlet-api_3.0_spec-1.0.1.Final-redhat-1.jar:1.0.1.Final-redhat-1]
> at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:329) [jbossweb-7.0.16.Final-redhat-1.jar:]
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:248) [jbossweb-7.0.16.Final-redhat-1.jar:]
> at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275) [jbossweb-7.0.16.Final-redhat-1.jar:]
> at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:161) [jbossweb-7.0.16.Final-redhat-1.jar:]
> at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:153) [jboss-as-web-7.1.2.Final-redhat-1.jar:7.1.2.Final-redhat-1]
> at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:155) [jbossweb-7.0.16.Final-redhat-1.jar:]
> at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) [jbossweb-7.0.16.Final-redhat-1.jar:]
> at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) [jbossweb-7.0.16.Final-redhat-1.jar:]
> at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:368) [jbossweb-7.0.16.Final-redhat-1.jar:]
> at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877) [jbossweb-7.0.16.Final-redhat-1.jar:]
> at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:679) [jbossweb-7.0.16.Final-redhat-1.jar:]
> at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:931) [jbossweb-7.0.16.Final-redhat-1.jar:]
> at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_32]
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 8 months
[JBoss JIRA] (JBIDE-3113) Consolidation/clean up of preference pages
by Josef Kopriva (Jira)
[ https://issues.jboss.org/browse/JBIDE-3113?page=com.atlassian.jira.plugin... ]
Josef Kopriva closed JBIDE-3113.
--------------------------------
> Consolidation/clean up of preference pages
> ------------------------------------------
>
> Key: JBIDE-3113
> URL: https://issues.jboss.org/browse/JBIDE-3113
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: common, drools, jbpm
> Affects Versions: 3.0.0.cr1
> Environment: JBossTools-3.0.0.CR1-N200811050757-ALL-linux-gtk
> Reporter: John Graham
> Assignee: Kris Verlaenen
> Priority: Critical
> Labels: usability
> Fix For: 4.12.0.Final
>
> Original Estimate: 0 minutes
> Remaining Estimate: 0 minutes
>
> JBT currently has three preference page categories:
> 1. Drools
> 2. JBoss jBPM
> 3. JBoss Tools
> The first two should be listed as subsections of the JBoss Tools category. Alternatively, I suggest that the top level category should just be JBoss:
> - JBoss
> -- Drools
> -- jBPM
> Also, the JBoss Tools and JBoss jBPM top level pages in each of these categories do not expose preferences, but rather the default buttons or simply a label ("JBoss Tools"). These top level pages should show overall JBT preferences. See the Java preferences or other examples in the Eclipse platform for this idea. (Also note that the DTP 1.6.x way of doing this is wrong... ;) )
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 8 months
[JBoss JIRA] (JBIDE-26684) Jobs are red due to issues with target platform
by Josef Kopriva (Jira)
[ https://issues.jboss.org/browse/JBIDE-26684?page=com.atlassian.jira.plugi... ]
Josef Kopriva closed JBIDE-26684.
---------------------------------
Jobs are ok.
> Jobs are red due to issues with target platform
> -----------------------------------------------
>
> Key: JBIDE-26684
> URL: https://issues.jboss.org/browse/JBIDE-26684
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Affects Versions: 4.12.0.Final
> Reporter: Josef Kopriva
> Assignee: Jeff MAURY
> Priority: Blocker
> Fix For: 4.12.0.Final
>
>
> https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud...
> https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud...
> https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud...
> https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud...
> Error:
> https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud...
> {code:java}
> 02:01:54 [INFO] Downloading from jboss-ga-repository: http://maven.repository.redhat.com/ga/org/jboss/tools/targetplatforms/jbo...
> 02:01:55 [ERROR] Internal error: java.lang.RuntimeException: Could not resolve target platform specification artifact org.jboss.tools.targetplatforms:jbosstools-unified:target:jbosstools-unified:4.12.0.Final-SNAPSHOT -> [Help 1]
> 02:01:55 org.apache.maven.InternalErrorException: Internal error: java.lang.RuntimeException: Could not resolve target platform specification artifact org.jboss.tools.targetplatforms:jbosstools-unified:target:jbosstools-unified:4.12.0.Final-SNAPSHOT
> 02:01:55 at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:122)
> 02:01:55 at org.apache.maven.cli.MavenCli.execute (MavenCli.java:955)
> 02:01:55 at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:290)
> 02:01:55 at org.apache.maven.cli.MavenCli.main (MavenCli.java:194)
> 02:01:55 at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
> 02:01:55 at sun.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:62)
> 02:01:55 at sun.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:43)
> 02:01:55 at java.lang.reflect.Method.invoke (Method.java:498)
> 02:01:55 at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced (Launcher.java:289)
> 02:01:55 at org.codehaus.plexus.classworlds.launcher.Launcher.launch (Launcher.java:229)
> 02:01:55 at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode (Launcher.java:415)
> 02:01:55 at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:356)
> 02:01:55 Caused by: java.lang.RuntimeException: Could not resolve target platform specification artifact org.jboss.tools.targetplatforms:jbosstools-unified:target:jbosstools-unified:4.12.0.Final-SNAPSHOT
> 02:01:55 at org.eclipse.tycho.core.resolver.DefaultTargetPlatformConfigurationReader.addTargetArtifact (DefaultTargetPlatformConfigurationReader.java:389)
> 02:01:55 at org.eclipse.tycho.core.resolver.DefaultTargetPlatformConfigurationReader.setTarget (DefaultTargetPlatformConfigurationReader.java:342)
> 02:01:55 at org.eclipse.tycho.core.resolver.DefaultTargetPlatformConfigurationReader.getTargetPlatformConfiguration (DefaultTargetPlatformConfigurationReader.java:75)
> 02:01:55 at org.eclipse.tycho.core.resolver.DefaultTychoResolver.setupProject (DefaultTychoResolver.java:87)
> 02:01:55 at org.eclipse.tycho.core.maven.TychoMavenLifecycleParticipant.afterProjectsRead (TychoMavenLifecycleParticipant.java:90)
> 02:01:55 at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:267)
> 02:01:55 at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:194)
> 02:01:55 at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:107)
> 02:01:55 at org.apache.maven.cli.MavenCli.execute (MavenCli.java:955)
> 02:01:55 at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:290)
> 02:01:55 at org.apache.maven.cli.MavenCli.main (MavenCli.java:194)
> 02:01:55 at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
> 02:01:55 at sun.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:62)
> 02:01:55 at sun.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:43)
> 02:01:55 at java.lang.reflect.Method.invoke (Method.java:498)
> 02:01:55 at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced (Launcher.java:289)
> 02:01:55 at org.codehaus.plexus.classworlds.launcher.Launcher.launch (Launcher.java:229)
> 02:01:55 at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode (Launcher.java:415)
> 02:01:55 at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:356)
> 02:01:55 [ERROR]
> 02:01:55 [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> 02:01:55 [ERROR]
> 02:01:55 [ERROR] For more information about the errors and possible solutions, please read the following articles:
> 02:01:55 [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/InternalErrorException
> 02:01:55 Build step 'Invoke top-level Maven targets' marked build as failure
> 02:01:56 [description-setter] Description set:
> 02:01:56 Sending e-mails to: jboss-devstudio-builds-list(a)redhat.com jmaury(a)redhat.com
> 02:01:59 Started calculate disk usage of build
> 02:01:59 Finished Calculation of disk usage of build in 0 seconds
> 02:01:59 Started calculate disk usage of workspace
> 02:02:00 Finished Calculation of disk usage of workspace in 0 seconds
> 02:02:00 Finished: FAILURE
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 8 months
[JBoss JIRA] (JBIDE-12394) Unable to load dialect Error in Drools project
by Josef Kopriva (Jira)
[ https://issues.jboss.org/browse/JBIDE-12394?page=com.atlassian.jira.plugi... ]
Josef Kopriva closed JBIDE-12394.
---------------------------------
Closing, deprecated.
> Unable to load dialect Error in Drools project
> ----------------------------------------------
>
> Key: JBIDE-12394
> URL: https://issues.jboss.org/browse/JBIDE-12394
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: drools
> Environment: JBoss Tools 2.3.0.v20120321-1339-H91-Beta2
> JBoss Drools Plugin 5.2.1.Final
> On classpath of project in question (configured via maven):
> * drools-compiler, drools-core, knowledge-api, knowledge-internal-api 5.4.0.Final
> * antlr, antlr-runtime 3.3
> * mvel2 2.1.0.drools16
> * ecj 3.5.1
> * stringtemplate 3.2.1
> * xstream 1.4.1
> * xmlpull 1.1.3
> * xpp3_min 1.1.4c
> Reporter: Jörg Henne
> Assignee: Kris Verlaenen
> Priority: Blocker
> Fix For: 4.0.0.Alpha1-SOA, 4.12.0.Final
>
>
> When new Drools project is created there is this error:
> Unable to load dialect 'org.drools.rule.builder.dialect.mvel.MVELDialectConfiguration:mvel:org.drools.rule.builder.dialect.mvel.MVELDialectConfiguration'
> See attached screenshot.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 8 months
[JBoss JIRA] (JBIDE-6608) Ability to remove drools nature from project
by Josef Kopriva (Jira)
[ https://issues.jboss.org/browse/JBIDE-6608?page=com.atlassian.jira.plugin... ]
Josef Kopriva closed JBIDE-6608.
--------------------------------
> Ability to remove drools nature from project
> --------------------------------------------
>
> Key: JBIDE-6608
> URL: https://issues.jboss.org/browse/JBIDE-6608
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: drools
> Affects Versions: 3.1.0.GA
> Reporter: Libor Zoubek
> Priority: Major
> Fix For: 3.3.x, 4.12.0.Final
>
>
> Regarding to http://community.jboss.org/message/552490 at this time, there is no possibility to remove drools "nature" (as it is probably not the nature in sense of eclipse nature)
> We should be able to remove drools from project. Menu item 'Convert to drools project' should be called 'Add drools nature' and when a project has a drools nature it should be called 'Remove drools nature'.
> Maybe it would be good, not to have 'Convert to drools project' menu item in main context menu, but move it into 'Configure' submenu
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 8 months
[JBoss JIRA] (JBIDE-26746) Deployment Page: changing location, deploys to new jar but wont remove old one
by André Dietisheim (Jira)
[ https://issues.jboss.org/browse/JBIDE-26746?page=com.atlassian.jira.plugi... ]
André Dietisheim updated JBIDE-26746:
-------------------------------------
Labels: deployment_page server_adapter (was: )
> Deployment Page: changing location, deploys to new jar but wont remove old one
> ------------------------------------------------------------------------------
>
> Key: JBIDE-26746
> URL: https://issues.jboss.org/browse/JBIDE-26746
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.13.0.AM1
> Reporter: André Dietisheim
> Assignee: André Dietisheim
> Priority: Major
> Labels: deployment_page, server_adapter
> Fix For: 4.13.0.AM1
>
>
> steps:
> # EXEC: Create application based on "eap72-basic-s2i" template & import source & create server adapter
> # ASSERT: application is running, server adapter created.
> # EXEC: open server editor, switch to "Deployment" tag and change the value in "Deployment Location" to "ROOT" & save editor
> # EXEC: start the server adapter
> # ASSERT: Console: adapter rsyncs local project into a folder "ROOT" on the pod.
> # EXEC: open the application log for the pod
> Result:
> the new deployment was picked up but failed with an error:
> {code}
> [0m[31m15:42:29,955 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC000001: Failed to start service jboss.deployment.unit.ROOT.FIRST_MODULE_USE: org.jboss.msc.service.StartException in service jboss.deployment.unit.ROOT.FIRST_MODULE_USE: WFLYSRV0153: Failed to process phase FIRST_MODULE_USE of deployment "ROOT"
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:172)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:2032)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1955)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYJCA0064: Exception deploying datasource java:jboss/datasources/KitchensinkQuickstartDS
> at org.jboss.as.connector.deployers.ds.processors.DsXmlDeploymentInstallProcessor.deploy(DsXmlDeploymentInstallProcessor.java:154)
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:165)
> ... 5 more
> Caused by: org.jboss.msc.service.DuplicateServiceException: Service jboss.data-source."jboss.naming.context.java.jboss.datasources.KitchensinkQuickstartDS".statistics is already registered
> at org.jboss.msc.service.ServiceRegistrationImpl.setInstance(ServiceRegistrationImpl.java:158)
> at org.jboss.msc.service.ServiceControllerImpl.startInstallation(ServiceControllerImpl.java:235)
> at org.jboss.msc.service.ServiceContainerImpl.install(ServiceContainerImpl.java:768)
> at org.jboss.msc.service.ServiceTargetImpl.install(ServiceTargetImpl.java:223)
> at org.jboss.msc.service.ServiceControllerImpl$ChildServiceTarget.install(ServiceControllerImpl.java:2555)
> at org.jboss.msc.service.ServiceTargetImpl.install(ServiceTargetImpl.java:223)
> at org.jboss.msc.service.ServiceControllerImpl$ChildServiceTarget.install(ServiceControllerImpl.java:2555)
> at org.jboss.msc.service.ServiceBuilderImpl.install(ServiceBuilderImpl.java:317)
> at org.jboss.as.connector.deployers.ds.processors.DsXmlDeploymentInstallProcessor.startDataSource(DsXmlDeploymentInstallProcessor.java:338)
> at org.jboss.as.connector.deployers.ds.processors.DsXmlDeploymentInstallProcessor.deploy(DsXmlDeploymentInstallProcessor.java:151)
> ... 6 more
> [0m[31m15:42:29,958 ERROR [org.jboss.as.controller.management-operation] (DeploymentScanner-threads - 2) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "ROOT")]) - failure description: {"WFLYCTL0080: Failed services" => {"jboss.deployment.unit.ROOT.FIRST_MODULE_USE" => "WFLYSRV0153: Failed to process phase FIRST_MODULE_USE of deployment \"ROOT\"
> Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYJCA0064: Exception deploying datasource java:jboss/datasources/KitchensinkQuickstartDS
> Caused by: org.jboss.msc.service.DuplicateServiceException: Service jboss.data-source.\"jboss.naming.context.java.jboss.datasources.KitchensinkQuickstartDS\".statistics is already registered"}}
> [0m[0m15:42:30,001 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) WFLYSRV0010: Deployed "ROOT" (runtime-name : "ROOT")
> [0m[0m15:42:30,001 INFO [org.jboss.as.controller] (DeploymentScanner-threads - 2) WFLYCTL0183: Service status report
> WFLYCTL0186: Services which failed to start: service jboss.deployment.unit.ROOT.FIRST_MODULE_USE: WFLYSRV0153: Failed to process phase FIRST_MODULE_USE of deployment "ROOT"
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 8 months