February 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-6565) single jdbc driver deployed inside ear takes name of ear

by jaikiran pai (JIRA)

[ https://issues.jboss.org/browse/AS7-6565?page=com.atlassian.jira.plugin.s... ] jaikiran pai commented on AS7-6565: ----------------------------------- I think there are 2 things to this: 1) There should be well know driver name format that user deployments can reliably use without having to bother about the internal implementation. 2) Whenever a driver is deployed, the driver name be logged so that it can help with debugging any dependency issues that might have occurred due to users not following the syntax dictated by #1. > single jdbc driver deployed inside ear takes name of ear > -------------------------------------------------------- > > Key: AS7-6565 > URL: https://issues.jboss.org/browse/AS7-6565 > Project: Application Server 7 > Issue Type: Feature Request > Components: JCA > Affects Versions: 7.1.1.Final, 8.0.0.Alpha1 > Reporter: Tom Eicher > Assignee: Stefano Maestri > > We need to always give service name for jdbdriver as > {code} > deploymentUnit.getName() + "_" + driverClassName + "_" + majorVersion +"_" + minorVersion > {code} > even if thre is only one driver in the deployment unit. Current behavior is to give just deploymentUnit name in case of only one driver in. The changes makes more clear/readable driver names. > Original description was: > Including a JDBC driver, in this case PostgreSQL, in an ear like > {code} > myapp.ear: > lib/postgresql-9.1-901.jdbc4.jar > {code} > does deploy the driver: > {code} > 23:37:28,118 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-1) JBAS010404: Deploying non-JDBC-compliant driver class org.postgresql.Driver (version 9.1) > {code} > however the service name is not {{postgresql_9_1_901_jdbc4_jar}} as expected, > but it's {{myapp_ear}}. > (Seen in admin console, and this is the only value accepted in my -ds.xml file.) > 1. JDBC driver service should pick name of innermost jar, not of containing ear > 2. driver name (as to be used in datasource definition) should be logged with the log message above. -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (AS7-6617) Struts actions are not getting linked to modules

by lalithambigai sigaamani (JIRA)

lalithambigai sigaamani created AS7-6617: -------------------------------------------- Summary: Struts actions are not getting linked to modules Key: AS7-6617 URL: https://issues.jboss.org/browse/AS7-6617 Project: Application Server 7 Issue Type: Clarification Environment: Windows XP Reporter: lalithambigai sigaamani Failed to define class *action.java in Module "deployment.XXX.war:main" from Service Module Loader: java.lang.LinkageError: Failed to link *action.java(Module "deployment.XXX.war:main" from Service Module Loader) Caused by: java.lang.NoClassDefFoundError: IllegalName: *action.java -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (AS7-6616) AS 8: Testsuite fails on Solaris SPARC 10

by Frank Langelage (JIRA)

[ https://issues.jboss.org/browse/AS7-6616?page=com.atlassian.jira.plugin.s... ] Frank Langelage updated AS7-6616: --------------------------------- Description: Compiling the current sources from github fails for me on this environment. On Windows everything is fine. Compiling 7.2.0.Final works in this environment. But regarding this test, nothing seems to have changed in between. Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 6.007 sec Running org.jboss.as.naming.subsystem.NamingSubsystemTestCase Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.346 sec Running org.jboss.as.naming.InitialContextTestCase Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.028 sec <<< FAILURE! Running org.jboss.as.naming.InitialContextFactoryTestCase Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.072 sec Running org.jboss.as.naming.NamingEventCoordinatorTestCase Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.059 sec Running org.jboss.as.naming.ServiceBasedNamingStoreTestCase Tests run: 8, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.091 sec Running org.jboss.as.naming.InMemoryNamingStoreTestCase Tests run: 16, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.057 sec Running org.jboss.as.naming.ObjectFactoryTestCase Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.012 sec Running org.jboss.as.naming.NamingContextTestCase Tests run: 20, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.151 sec Running org.jboss.as.naming.WritableServiceBasedNamingStoreTestCase Tests run: 9, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.175 sec Results : Tests in error: testRegisterURLSchemeHandler(org.jboss.as.naming.InitialContextTestCase): JBAS011857: NamingStore is null Tests run: 70, Failures: 0, Errors: 1, Skipped: 0 [INFO] ------------------------------------------------------------------------ [INFO] Reactor Summary: [INFO] [INFO] JBoss Application Server: Build Configuration ..... SUCCESS [16.745s] [INFO] JBoss Application Server: Parent Aggregator ....... SUCCESS [5.425s] [INFO] JBoss Application Server: Protocol Utilities ...... SUCCESS [38.109s] [INFO] JBoss Application Server: Controller Client ....... SUCCESS [18.200s] [INFO] JBoss Application Server: Controller Core ......... SUCCESS [1:07.854s] [INFO] JBoss Application Server: Deployment Repository ... SUCCESS [5.962s] [INFO] JBoss Application Server: Version ................. SUCCESS [3.578s] [INFO] JBoss Application Server: Process Controller ...... SUCCESS [12.553s] [INFO] JBoss Application Server: Platform MBean integration SUCCESS [12.141s] [INFO] JBoss Application Server: Domain Management ....... SUCCESS [14.524s] [INFO] JBoss Application Server: Domain HTTP Interface ... SUCCESS [0.381s] [INFO] JBoss Application Server: Domain HTTP Interface ... SUCCESS [7.821s] [INFO] JBoss Application Server: Network ................. SUCCESS [5.345s] [INFO] JBoss Application Server: Remoting Subsystem ...... SUCCESS [7.735s] [INFO] JBoss Application Server: Server .................. SUCCESS [35.813s] [INFO] JBoss Application Server: Management Client Content SUCCESS [6.731s] [INFO] JBoss Application Server: Common Code for Subsystem and Non-subsystem Test Harness SUCCESS [9.894s] [INFO] JBoss Application Server: Subsystem Test Harness .. SUCCESS [14.606s] [INFO] JBoss Application Server: Threading Subsystem ..... SUCCESS [30.757s] [INFO] JBoss Application Server: Host Controller ......... SUCCESS [29.205s] [INFO] JBoss Application Server: Core Model Test Parent .. SUCCESS [0.755s] [INFO] JBoss Application Server: Core Model Test Framework SUCCESS [8.585s] [INFO] JBoss Application Server: Domain HTTP Error Context SUCCESS [2.921s] [INFO] JBoss Application Server: Naming Subsystem ........ FAILURE [15.100s] [INFO] JBoss Application Server: JMX Subsystem ........... SKIPPED [INFO] JBoss Application Server: EE ...................... SKIPPED [INFO] JBoss Application Server: JacORB Subsystem ........ SKIPPED [INFO] JBoss Application Server: Transaction Subsystem ... SKIPPED [INFO] JBoss Application Server: Clustering Subsystem .... SKIPPED [INFO] JBoss Application Server: Clustering Server API ... SKIPPED [INFO] JBoss Application Server: Common code for clustering subsystems SKIPPED [INFO] JBoss Application Server: JGroups Subsystem ....... SKIPPED [INFO] JBoss Application Server: Infinispan Subsystem .... SKIPPED [INFO] JBoss Application Server: Security Subsystem ...... SKIPPED [INFO] JBoss Application Server: Connector Subsystem ..... SKIPPED [INFO] JBoss Application Server: Clustered registry service SKIPPED [INFO] JBoss Application Server: EJB Subsystem ........... SKIPPED [INFO] JBoss Application Server: Distributed Web Session SPI SKIPPED [INFO] JBoss Application Server: Clustering Server API implementation SKIPPED [INFO] JBoss Application Server: Distributed Web Session Infinispan provider SKIPPED [INFO] JBoss Application Server: Web Subsystem ........... SKIPPED [INFO] JBoss Application Server: Web Services Subsystem .. SKIPPED [INFO] JBoss Application Server: Web Services Server Integration Subsystem SKIPPED [INFO] JBoss Application Server: Application Client Bootstrap SKIPPED [INFO] JBoss Application Server: Config Assembly ......... SKIPPED [INFO] JBoss Application Server: Command line interface .. SKIPPED [INFO] JBoss Application Server: EJB Client BOM .......... SKIPPED [INFO] JBoss Application Server: JMS Client BOM .......... SKIPPED [INFO] JBoss Application Server: EJB and JMS client combined jar SKIPPED [INFO] JBoss Application Server: Clustered Stateful Session Bean cache Infinispan provider SKIPPED [INFO] JBoss Application Server: Clustered service provider registry services SKIPPED [INFO] JBoss Application Server: Clustered singleton services SKIPPED [INFO] JBoss Application Server: EJB Container Managed Persistence Subsystem SKIPPED [INFO] JBoss Application Server: Config Admin ............ SKIPPED [INFO] JBoss Application Server: Deployment Scanner ...... SKIPPED [INFO] JBoss Application Server: EE Deployment ........... SKIPPED [INFO] JBoss Application Server: Embedded ................ SKIPPED [INFO] JBoss Application Server: JAXR Client ............. SKIPPED [INFO] JBoss Application Server: JPA Subsystem ........... SKIPPED [INFO] JBoss Application Server: JPA SPI ................. SKIPPED [INFO] JBoss Application Server: JPA UTIL ................ SKIPPED [INFO] JBoss Application Server: JPA Subsystem ........... SKIPPED [INFO] JBoss Application Server: Weld Integration ........ SKIPPED [INFO] JBoss Application Server: JAX-RS Integration ...... SKIPPED [INFO] JBoss Application Server: JBoss Diagnostic Reporter SKIPPED [INFO] JBoss Application Server: JDR ..................... SKIPPED [INFO] JBoss Application Server: JSF ..................... SKIPPED [INFO] JBoss Application Server: JSF Subsystem ........... SKIPPED [INFO] JBoss Application Server: JSF Injection Handlers .. SKIPPED [INFO] JBoss Application Server: JSR-77 Subsystem ........ SKIPPED [INFO] JBoss Application Server: Logging Subsystem ....... SKIPPED [INFO] JBoss Application Server: Mail subsystem .......... SKIPPED [INFO] JBoss Application Server: Messaging Subsystem ..... SKIPPED [INFO] JBoss Application Server: ModCluster Subsystem .... SKIPPED [INFO] JBoss Application Server: OSGi .................... SKIPPED [INFO] JBoss Application Server: OSGi Subsystem .......... SKIPPED [INFO] JBoss Application Server: OSGi Integration ........ SKIPPED [INFO] JBoss Application Server: OSGi Integration ConfigAdmin SKIPPED [INFO] JBoss Application Server: OSGi Integration Http ... SKIPPED [INFO] JBoss Application Server: OSGi Integration JMX .... SKIPPED [INFO] JBoss Application Server: OSGi Integration JPA .... SKIPPED [INFO] JBoss Application Server: OSGi Integration JTA .... SKIPPED [INFO] JBoss Application Server: OSGi Integration Naming . SKIPPED [INFO] JBoss Application Server: OSGi Integration WebApp . SKIPPED [INFO] JBoss Application Server: POJO Subsystem .......... SKIPPED [INFO] JBoss Application Server: Service Archive Subsystem SKIPPED [INFO] JBoss Application Server: System JMX Module ....... SKIPPED [INFO] JBoss Application Server: XTS Subsystem ........... SKIPPED [INFO] JBoss Application Server: Hibernate 3.6.x JPA integration SKIPPED [INFO] JBoss Application Server: Hibernate 4.0.x JPA integration SKIPPED [INFO] JBoss Application Server: OpenJPA 2.x JPA integration SKIPPED [INFO] JBoss Application Server: Build ................... SKIPPED [INFO] JBoss Application Server: Build Modular ........... SKIPPED [INFO] JBoss Application Server: Arquillian .............. SKIPPED [INFO] JBoss Application Server: Arquillian TestEnricher MSC SKIPPED [INFO] JBoss Application Server: Arquillian Common ....... SKIPPED [INFO] JBoss Application Server: Arquillian Embedded Container SKIPPED [INFO] JBoss Application Server: Arquillian Protocol JMX . SKIPPED [INFO] JBoss Application Server: Arquillian Managed Container SKIPPED [INFO] JBoss Application Server: Arquillian Remote Container SKIPPED [INFO] JBoss Application Server: Exported Java EE Specification APIs SKIPPED [INFO] JBoss Application Server: Arquillian TestNG Integration SKIPPED [INFO] JBoss Application Server: Arquillian Common Domain SKIPPED [INFO] JBoss Application Server: Arquillian Remote Domain Container SKIPPED [INFO] JBoss Application Server: Arquillian Managed Domain Container SKIPPED [INFO] JBoss Application Server: Core Model Test Controller 7.1.2 SKIPPED [INFO] JBoss Application Server: Core Model Test Controller Optional SKIPPED [INFO] JBoss Application Server: Core Model Tests ........ SKIPPED [INFO] JBoss Application Server: Distribution ............ SKIPPED [INFO] JBoss Application Server Test Suite: Shared ....... SKIPPED [INFO] JBoss Application Server: OSGi Launcher ........... SKIPPED [INFO] JBoss Application Server: Remoting Subsystem Test . SKIPPED [INFO] JBoss Application Server: Validation Tests for Exported Java EE Specification APIs SKIPPED [INFO] JBoss Application Server: Web Services Tests Integration Subsystem SKIPPED [INFO] JBoss Application Server Test Suite: Aggregator ... SKIPPED [INFO] JBoss Application Server Test Suite: Integration .. SKIPPED [INFO] JBoss Application Server Test Suite: Integration - Smoke SKIPPED [INFO] ------------------------------------------------------------------------ [INFO] BUILD FAILURE [INFO] ------------------------------------------------------------------------ [INFO] Total time: 6:36.380s [INFO] Finished at: Sun Feb 24 22:56:01 CET 2013 [INFO] Final Memory: 122M/348M [INFO] ------------------------------------------------------------------------ [ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.11:test (default-test) on project jboss-as-naming: There are test failures. [ERROR] [ERROR] Please refer to /home/jboss/JBoss-8.0/jboss-as/naming/target/surefire-reports for the individual test results. [ERROR] -> [Help 1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException [ERROR] [ERROR] After correcting the problems, you can resume the build with the command [ERROR] mvn <goals> -rf :jboss-as-naming was: Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 6.007 sec Running org.jboss.as.naming.subsystem.NamingSubsystemTestCase Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.346 sec Running org.jboss.as.naming.InitialContextTestCase Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.028 sec <<< FAILURE! Running org.jboss.as.naming.InitialContextFactoryTestCase Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.072 sec Running org.jboss.as.naming.NamingEventCoordinatorTestCase Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.059 sec Running org.jboss.as.naming.ServiceBasedNamingStoreTestCase Tests run: 8, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.091 sec Running org.jboss.as.naming.InMemoryNamingStoreTestCase Tests run: 16, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.057 sec Running org.jboss.as.naming.ObjectFactoryTestCase Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.012 sec Running org.jboss.as.naming.NamingContextTestCase Tests run: 20, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.151 sec Running org.jboss.as.naming.WritableServiceBasedNamingStoreTestCase Tests run: 9, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.175 sec Results : Tests in error: testRegisterURLSchemeHandler(org.jboss.as.naming.InitialContextTestCase): JBAS011857: NamingStore is null Tests run: 70, Failures: 0, Errors: 1, Skipped: 0 [INFO] ------------------------------------------------------------------------ [INFO] Reactor Summary: [INFO] [INFO] JBoss Application Server: Build Configuration ..... SUCCESS [16.745s] [INFO] JBoss Application Server: Parent Aggregator ....... SUCCESS [5.425s] [INFO] JBoss Application Server: Protocol Utilities ...... SUCCESS [38.109s] [INFO] JBoss Application Server: Controller Client ....... SUCCESS [18.200s] [INFO] JBoss Application Server: Controller Core ......... SUCCESS [1:07.854s] [INFO] JBoss Application Server: Deployment Repository ... SUCCESS [5.962s] [INFO] JBoss Application Server: Version ................. SUCCESS [3.578s] [INFO] JBoss Application Server: Process Controller ...... SUCCESS [12.553s] [INFO] JBoss Application Server: Platform MBean integration SUCCESS [12.141s] [INFO] JBoss Application Server: Domain Management ....... SUCCESS [14.524s] [INFO] JBoss Application Server: Domain HTTP Interface ... SUCCESS [0.381s] [INFO] JBoss Application Server: Domain HTTP Interface ... SUCCESS [7.821s] [INFO] JBoss Application Server: Network ................. SUCCESS [5.345s] [INFO] JBoss Application Server: Remoting Subsystem ...... SUCCESS [7.735s] [INFO] JBoss Application Server: Server .................. SUCCESS [35.813s] [INFO] JBoss Application Server: Management Client Content SUCCESS [6.731s] [INFO] JBoss Application Server: Common Code for Subsystem and Non-subsystem Test Harness SUCCESS [9.894s] [INFO] JBoss Application Server: Subsystem Test Harness .. SUCCESS [14.606s] [INFO] JBoss Application Server: Threading Subsystem ..... SUCCESS [30.757s] [INFO] JBoss Application Server: Host Controller ......... SUCCESS [29.205s] [INFO] JBoss Application Server: Core Model Test Parent .. SUCCESS [0.755s] [INFO] JBoss Application Server: Core Model Test Framework SUCCESS [8.585s] [INFO] JBoss Application Server: Domain HTTP Error Context SUCCESS [2.921s] [INFO] JBoss Application Server: Naming Subsystem ........ FAILURE [15.100s] [INFO] JBoss Application Server: JMX Subsystem ........... SKIPPED [INFO] JBoss Application Server: EE ...................... SKIPPED [INFO] JBoss Application Server: JacORB Subsystem ........ SKIPPED [INFO] JBoss Application Server: Transaction Subsystem ... SKIPPED [INFO] JBoss Application Server: Clustering Subsystem .... SKIPPED [INFO] JBoss Application Server: Clustering Server API ... SKIPPED [INFO] JBoss Application Server: Common code for clustering subsystems SKIPPED [INFO] JBoss Application Server: JGroups Subsystem ....... SKIPPED [INFO] JBoss Application Server: Infinispan Subsystem .... SKIPPED [INFO] JBoss Application Server: Security Subsystem ...... SKIPPED [INFO] JBoss Application Server: Connector Subsystem ..... SKIPPED [INFO] JBoss Application Server: Clustered registry service SKIPPED [INFO] JBoss Application Server: EJB Subsystem ........... SKIPPED [INFO] JBoss Application Server: Distributed Web Session SPI SKIPPED [INFO] JBoss Application Server: Clustering Server API implementation SKIPPED [INFO] JBoss Application Server: Distributed Web Session Infinispan provider SKIPPED [INFO] JBoss Application Server: Web Subsystem ........... SKIPPED [INFO] JBoss Application Server: Web Services Subsystem .. SKIPPED [INFO] JBoss Application Server: Web Services Server Integration Subsystem SKIPPED [INFO] JBoss Application Server: Application Client Bootstrap SKIPPED [INFO] JBoss Application Server: Config Assembly ......... SKIPPED [INFO] JBoss Application Server: Command line interface .. SKIPPED [INFO] JBoss Application Server: EJB Client BOM .......... SKIPPED [INFO] JBoss Application Server: JMS Client BOM .......... SKIPPED [INFO] JBoss Application Server: EJB and JMS client combined jar SKIPPED [INFO] JBoss Application Server: Clustered Stateful Session Bean cache Infinispan provider SKIPPED [INFO] JBoss Application Server: Clustered service provider registry services SKIPPED [INFO] JBoss Application Server: Clustered singleton services SKIPPED [INFO] JBoss Application Server: EJB Container Managed Persistence Subsystem SKIPPED [INFO] JBoss Application Server: Config Admin ............ SKIPPED [INFO] JBoss Application Server: Deployment Scanner ...... SKIPPED [INFO] JBoss Application Server: EE Deployment ........... SKIPPED [INFO] JBoss Application Server: Embedded ................ SKIPPED [INFO] JBoss Application Server: JAXR Client ............. SKIPPED [INFO] JBoss Application Server: JPA Subsystem ........... SKIPPED [INFO] JBoss Application Server: JPA SPI ................. SKIPPED [INFO] JBoss Application Server: JPA UTIL ................ SKIPPED [INFO] JBoss Application Server: JPA Subsystem ........... SKIPPED [INFO] JBoss Application Server: Weld Integration ........ SKIPPED [INFO] JBoss Application Server: JAX-RS Integration ...... SKIPPED [INFO] JBoss Application Server: JBoss Diagnostic Reporter SKIPPED [INFO] JBoss Application Server: JDR ..................... SKIPPED [INFO] JBoss Application Server: JSF ..................... SKIPPED [INFO] JBoss Application Server: JSF Subsystem ........... SKIPPED [INFO] JBoss Application Server: JSF Injection Handlers .. SKIPPED [INFO] JBoss Application Server: JSR-77 Subsystem ........ SKIPPED [INFO] JBoss Application Server: Logging Subsystem ....... SKIPPED [INFO] JBoss Application Server: Mail subsystem .......... SKIPPED [INFO] JBoss Application Server: Messaging Subsystem ..... SKIPPED [INFO] JBoss Application Server: ModCluster Subsystem .... SKIPPED [INFO] JBoss Application Server: OSGi .................... SKIPPED [INFO] JBoss Application Server: OSGi Subsystem .......... SKIPPED [INFO] JBoss Application Server: OSGi Integration ........ SKIPPED [INFO] JBoss Application Server: OSGi Integration ConfigAdmin SKIPPED [INFO] JBoss Application Server: OSGi Integration Http ... SKIPPED [INFO] JBoss Application Server: OSGi Integration JMX .... SKIPPED [INFO] JBoss Application Server: OSGi Integration JPA .... SKIPPED [INFO] JBoss Application Server: OSGi Integration JTA .... SKIPPED [INFO] JBoss Application Server: OSGi Integration Naming . SKIPPED [INFO] JBoss Application Server: OSGi Integration WebApp . SKIPPED [INFO] JBoss Application Server: POJO Subsystem .......... SKIPPED [INFO] JBoss Application Server: Service Archive Subsystem SKIPPED [INFO] JBoss Application Server: System JMX Module ....... SKIPPED [INFO] JBoss Application Server: XTS Subsystem ........... SKIPPED [INFO] JBoss Application Server: Hibernate 3.6.x JPA integration SKIPPED [INFO] JBoss Application Server: Hibernate 4.0.x JPA integration SKIPPED [INFO] JBoss Application Server: OpenJPA 2.x JPA integration SKIPPED [INFO] JBoss Application Server: Build ................... SKIPPED [INFO] JBoss Application Server: Build Modular ........... SKIPPED [INFO] JBoss Application Server: Arquillian .............. SKIPPED [INFO] JBoss Application Server: Arquillian TestEnricher MSC SKIPPED [INFO] JBoss Application Server: Arquillian Common ....... SKIPPED [INFO] JBoss Application Server: Arquillian Embedded Container SKIPPED [INFO] JBoss Application Server: Arquillian Protocol JMX . SKIPPED [INFO] JBoss Application Server: Arquillian Managed Container SKIPPED [INFO] JBoss Application Server: Arquillian Remote Container SKIPPED [INFO] JBoss Application Server: Exported Java EE Specification APIs SKIPPED [INFO] JBoss Application Server: Arquillian TestNG Integration SKIPPED [INFO] JBoss Application Server: Arquillian Common Domain SKIPPED [INFO] JBoss Application Server: Arquillian Remote Domain Container SKIPPED [INFO] JBoss Application Server: Arquillian Managed Domain Container SKIPPED [INFO] JBoss Application Server: Core Model Test Controller 7.1.2 SKIPPED [INFO] JBoss Application Server: Core Model Test Controller Optional SKIPPED [INFO] JBoss Application Server: Core Model Tests ........ SKIPPED [INFO] JBoss Application Server: Distribution ............ SKIPPED [INFO] JBoss Application Server Test Suite: Shared ....... SKIPPED [INFO] JBoss Application Server: OSGi Launcher ........... SKIPPED [INFO] JBoss Application Server: Remoting Subsystem Test . SKIPPED [INFO] JBoss Application Server: Validation Tests for Exported Java EE Specification APIs SKIPPED [INFO] JBoss Application Server: Web Services Tests Integration Subsystem SKIPPED [INFO] JBoss Application Server Test Suite: Aggregator ... SKIPPED [INFO] JBoss Application Server Test Suite: Integration .. SKIPPED [INFO] JBoss Application Server Test Suite: Integration - Smoke SKIPPED [INFO] ------------------------------------------------------------------------ [INFO] BUILD FAILURE [INFO] ------------------------------------------------------------------------ [INFO] Total time: 6:36.380s [INFO] Finished at: Sun Feb 24 22:56:01 CET 2013 [INFO] Final Memory: 122M/348M [INFO] ------------------------------------------------------------------------ [ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.11:test (default-test) on project jboss-as-naming: There are test failures. [ERROR] [ERROR] Please refer to /home/jboss/JBoss-8.0/jboss-as/naming/target/surefire-reports for the individual test results. [ERROR] -> [Help 1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException [ERROR] [ERROR] After correcting the problems, you can resume the build with the command [ERROR] mvn <goals> -rf :jboss-as-naming > AS 8: Testsuite fails on Solaris SPARC 10 > ----------------------------------------- > > Key: AS7-6616 > URL: https://issues.jboss.org/browse/AS7-6616 > Project: Application Server 7 > Issue Type: Bug > Affects Versions: 8.0.0.Alpha1 > Environment: Solaris SPARC 10, Oracle JDK 1.6.0_41 > Reporter: Frank Langelage > Attachments: org.jboss.as.naming.InitialContextTestCase.txt, TEST-org.jboss.as.naming.InitialContextTestCase.xml > > > Compiling the current sources from github fails for me on this environment. > On Windows everything is fine. > Compiling 7.2.0.Final works in this environment. > But regarding this test, nothing seems to have changed in between. > Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 6.007 sec > Running org.jboss.as.naming.subsystem.NamingSubsystemTestCase > Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.346 sec > Running org.jboss.as.naming.InitialContextTestCase > Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.028 sec <<< FAILURE! > Running org.jboss.as.naming.InitialContextFactoryTestCase > Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.072 sec > Running org.jboss.as.naming.NamingEventCoordinatorTestCase > Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.059 sec > Running org.jboss.as.naming.ServiceBasedNamingStoreTestCase > Tests run: 8, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.091 sec > Running org.jboss.as.naming.InMemoryNamingStoreTestCase > Tests run: 16, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.057 sec > Running org.jboss.as.naming.ObjectFactoryTestCase > Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.012 sec > Running org.jboss.as.naming.NamingContextTestCase > Tests run: 20, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.151 sec > Running org.jboss.as.naming.WritableServiceBasedNamingStoreTestCase > Tests run: 9, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.175 sec > Results : > Tests in error: > testRegisterURLSchemeHandler(org.jboss.as.naming.InitialContextTestCase): JBAS011857: NamingStore is null > Tests run: 70, Failures: 0, Errors: 1, Skipped: 0 > [INFO] ------------------------------------------------------------------------ > [INFO] Reactor Summary: > [INFO] > [INFO] JBoss Application Server: Build Configuration ..... SUCCESS [16.745s] > [INFO] JBoss Application Server: Parent Aggregator ....... SUCCESS [5.425s] > [INFO] JBoss Application Server: Protocol Utilities ...... SUCCESS [38.109s] > [INFO] JBoss Application Server: Controller Client ....... SUCCESS [18.200s] > [INFO] JBoss Application Server: Controller Core ......... SUCCESS [1:07.854s] > [INFO] JBoss Application Server: Deployment Repository ... SUCCESS [5.962s] > [INFO] JBoss Application Server: Version ................. SUCCESS [3.578s] > [INFO] JBoss Application Server: Process Controller ...... SUCCESS [12.553s] > [INFO] JBoss Application Server: Platform MBean integration SUCCESS [12.141s] > [INFO] JBoss Application Server: Domain Management ....... SUCCESS [14.524s] > [INFO] JBoss Application Server: Domain HTTP Interface ... SUCCESS [0.381s] > [INFO] JBoss Application Server: Domain HTTP Interface ... SUCCESS [7.821s] > [INFO] JBoss Application Server: Network ................. SUCCESS [5.345s] > [INFO] JBoss Application Server: Remoting Subsystem ...... SUCCESS [7.735s] > [INFO] JBoss Application Server: Server .................. SUCCESS [35.813s] > [INFO] JBoss Application Server: Management Client Content SUCCESS [6.731s] > [INFO] JBoss Application Server: Common Code for Subsystem and Non-subsystem Test Harness SUCCESS [9.894s] > [INFO] JBoss Application Server: Subsystem Test Harness .. SUCCESS [14.606s] > [INFO] JBoss Application Server: Threading Subsystem ..... SUCCESS [30.757s] > [INFO] JBoss Application Server: Host Controller ......... SUCCESS [29.205s] > [INFO] JBoss Application Server: Core Model Test Parent .. SUCCESS [0.755s] > [INFO] JBoss Application Server: Core Model Test Framework SUCCESS [8.585s] > [INFO] JBoss Application Server: Domain HTTP Error Context SUCCESS [2.921s] > [INFO] JBoss Application Server: Naming Subsystem ........ FAILURE [15.100s] > [INFO] JBoss Application Server: JMX Subsystem ........... SKIPPED > [INFO] JBoss Application Server: EE ...................... SKIPPED > [INFO] JBoss Application Server: JacORB Subsystem ........ SKIPPED > [INFO] JBoss Application Server: Transaction Subsystem ... SKIPPED > [INFO] JBoss Application Server: Clustering Subsystem .... SKIPPED > [INFO] JBoss Application Server: Clustering Server API ... SKIPPED > [INFO] JBoss Application Server: Common code for clustering subsystems SKIPPED > [INFO] JBoss Application Server: JGroups Subsystem ....... SKIPPED > [INFO] JBoss Application Server: Infinispan Subsystem .... SKIPPED > [INFO] JBoss Application Server: Security Subsystem ...... SKIPPED > [INFO] JBoss Application Server: Connector Subsystem ..... SKIPPED > [INFO] JBoss Application Server: Clustered registry service SKIPPED > [INFO] JBoss Application Server: EJB Subsystem ........... SKIPPED > [INFO] JBoss Application Server: Distributed Web Session SPI SKIPPED > [INFO] JBoss Application Server: Clustering Server API implementation SKIPPED > [INFO] JBoss Application Server: Distributed Web Session Infinispan provider SKIPPED > [INFO] JBoss Application Server: Web Subsystem ........... SKIPPED > [INFO] JBoss Application Server: Web Services Subsystem .. SKIPPED > [INFO] JBoss Application Server: Web Services Server Integration Subsystem SKIPPED > [INFO] JBoss Application Server: Application Client Bootstrap SKIPPED > [INFO] JBoss Application Server: Config Assembly ......... SKIPPED > [INFO] JBoss Application Server: Command line interface .. SKIPPED > [INFO] JBoss Application Server: EJB Client BOM .......... SKIPPED > [INFO] JBoss Application Server: JMS Client BOM .......... SKIPPED > [INFO] JBoss Application Server: EJB and JMS client combined jar SKIPPED > [INFO] JBoss Application Server: Clustered Stateful Session Bean cache Infinispan provider SKIPPED > [INFO] JBoss Application Server: Clustered service provider registry services SKIPPED > [INFO] JBoss Application Server: Clustered singleton services SKIPPED > [INFO] JBoss Application Server: EJB Container Managed Persistence Subsystem SKIPPED > [INFO] JBoss Application Server: Config Admin ............ SKIPPED > [INFO] JBoss Application Server: Deployment Scanner ...... SKIPPED > [INFO] JBoss Application Server: EE Deployment ........... SKIPPED > [INFO] JBoss Application Server: Embedded ................ SKIPPED > [INFO] JBoss Application Server: JAXR Client ............. SKIPPED > [INFO] JBoss Application Server: JPA Subsystem ........... SKIPPED > [INFO] JBoss Application Server: JPA SPI ................. SKIPPED > [INFO] JBoss Application Server: JPA UTIL ................ SKIPPED > [INFO] JBoss Application Server: JPA Subsystem ........... SKIPPED > [INFO] JBoss Application Server: Weld Integration ........ SKIPPED > [INFO] JBoss Application Server: JAX-RS Integration ...... SKIPPED > [INFO] JBoss Application Server: JBoss Diagnostic Reporter SKIPPED > [INFO] JBoss Application Server: JDR ..................... SKIPPED > [INFO] JBoss Application Server: JSF ..................... SKIPPED > [INFO] JBoss Application Server: JSF Subsystem ........... SKIPPED > [INFO] JBoss Application Server: JSF Injection Handlers .. SKIPPED > [INFO] JBoss Application Server: JSR-77 Subsystem ........ SKIPPED > [INFO] JBoss Application Server: Logging Subsystem ....... SKIPPED > [INFO] JBoss Application Server: Mail subsystem .......... SKIPPED > [INFO] JBoss Application Server: Messaging Subsystem ..... SKIPPED > [INFO] JBoss Application Server: ModCluster Subsystem .... SKIPPED > [INFO] JBoss Application Server: OSGi .................... SKIPPED > [INFO] JBoss Application Server: OSGi Subsystem .......... SKIPPED > [INFO] JBoss Application Server: OSGi Integration ........ SKIPPED > [INFO] JBoss Application Server: OSGi Integration ConfigAdmin SKIPPED > [INFO] JBoss Application Server: OSGi Integration Http ... SKIPPED > [INFO] JBoss Application Server: OSGi Integration JMX .... SKIPPED > [INFO] JBoss Application Server: OSGi Integration JPA .... SKIPPED > [INFO] JBoss Application Server: OSGi Integration JTA .... SKIPPED > [INFO] JBoss Application Server: OSGi Integration Naming . SKIPPED > [INFO] JBoss Application Server: OSGi Integration WebApp . SKIPPED > [INFO] JBoss Application Server: POJO Subsystem .......... SKIPPED > [INFO] JBoss Application Server: Service Archive Subsystem SKIPPED > [INFO] JBoss Application Server: System JMX Module ....... SKIPPED > [INFO] JBoss Application Server: XTS Subsystem ........... SKIPPED > [INFO] JBoss Application Server: Hibernate 3.6.x JPA integration SKIPPED > [INFO] JBoss Application Server: Hibernate 4.0.x JPA integration SKIPPED > [INFO] JBoss Application Server: OpenJPA 2.x JPA integration SKIPPED > [INFO] JBoss Application Server: Build ................... SKIPPED > [INFO] JBoss Application Server: Build Modular ........... SKIPPED > [INFO] JBoss Application Server: Arquillian .............. SKIPPED > [INFO] JBoss Application Server: Arquillian TestEnricher MSC SKIPPED > [INFO] JBoss Application Server: Arquillian Common ....... SKIPPED > [INFO] JBoss Application Server: Arquillian Embedded Container SKIPPED > [INFO] JBoss Application Server: Arquillian Protocol JMX . SKIPPED > [INFO] JBoss Application Server: Arquillian Managed Container SKIPPED > [INFO] JBoss Application Server: Arquillian Remote Container SKIPPED > [INFO] JBoss Application Server: Exported Java EE Specification APIs SKIPPED > [INFO] JBoss Application Server: Arquillian TestNG Integration SKIPPED > [INFO] JBoss Application Server: Arquillian Common Domain SKIPPED > [INFO] JBoss Application Server: Arquillian Remote Domain Container SKIPPED > [INFO] JBoss Application Server: Arquillian Managed Domain Container SKIPPED > [INFO] JBoss Application Server: Core Model Test Controller 7.1.2 SKIPPED > [INFO] JBoss Application Server: Core Model Test Controller Optional SKIPPED > [INFO] JBoss Application Server: Core Model Tests ........ SKIPPED > [INFO] JBoss Application Server: Distribution ............ SKIPPED > [INFO] JBoss Application Server Test Suite: Shared ....... SKIPPED > [INFO] JBoss Application Server: OSGi Launcher ........... SKIPPED > [INFO] JBoss Application Server: Remoting Subsystem Test . SKIPPED > [INFO] JBoss Application Server: Validation Tests for Exported Java EE Specification APIs SKIPPED > [INFO] JBoss Application Server: Web Services Tests Integration Subsystem SKIPPED > [INFO] JBoss Application Server Test Suite: Aggregator ... SKIPPED > [INFO] JBoss Application Server Test Suite: Integration .. SKIPPED > [INFO] JBoss Application Server Test Suite: Integration - Smoke SKIPPED > [INFO] ------------------------------------------------------------------------ > [INFO] BUILD FAILURE > [INFO] ------------------------------------------------------------------------ > [INFO] Total time: 6:36.380s > [INFO] Finished at: Sun Feb 24 22:56:01 CET 2013 > [INFO] Final Memory: 122M/348M > [INFO] ------------------------------------------------------------------------ > [ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.11:test (default-test) on project jboss-as-naming: There are test failures. > [ERROR] > [ERROR] Please refer to /home/jboss/JBoss-8.0/jboss-as/naming/target/surefire-reports for the individual test results. > [ERROR] -> [Help 1] > [ERROR] > [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. > [ERROR] Re-run Maven using the -X switch to enable full debug logging. > [ERROR] > [ERROR] For more information about the errors and possible solutions, please read the following articles: > [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException > [ERROR] > [ERROR] After correcting the problems, you can resume the build with the command > [ERROR] mvn <goals> -rf :jboss-as-naming -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (AS7-6616) AS 8: Testsuite fails on Solaris SPARC 10

by Frank Langelage (JIRA)

[ https://issues.jboss.org/browse/AS7-6616?page=com.atlassian.jira.plugin.s... ] Frank Langelage updated AS7-6616: --------------------------------- Attachment: org.jboss.as.naming.InitialContextTestCase.txt TEST-org.jboss.as.naming.InitialContextTestCase.xml > AS 8: Testsuite fails on Solaris SPARC 10 > ----------------------------------------- > > Key: AS7-6616 > URL: https://issues.jboss.org/browse/AS7-6616 > Project: Application Server 7 > Issue Type: Bug > Affects Versions: 8.0.0.Alpha1 > Environment: Solaris SPARC 10, Oracle JDK 1.6.0_41 > Reporter: Frank Langelage > Attachments: org.jboss.as.naming.InitialContextTestCase.txt, TEST-org.jboss.as.naming.InitialContextTestCase.xml > > > Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 6.007 sec > Running org.jboss.as.naming.subsystem.NamingSubsystemTestCase > Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.346 sec > Running org.jboss.as.naming.InitialContextTestCase > Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.028 sec <<< FAILURE! > Running org.jboss.as.naming.InitialContextFactoryTestCase > Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.072 sec > Running org.jboss.as.naming.NamingEventCoordinatorTestCase > Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.059 sec > Running org.jboss.as.naming.ServiceBasedNamingStoreTestCase > Tests run: 8, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.091 sec > Running org.jboss.as.naming.InMemoryNamingStoreTestCase > Tests run: 16, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.057 sec > Running org.jboss.as.naming.ObjectFactoryTestCase > Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.012 sec > Running org.jboss.as.naming.NamingContextTestCase > Tests run: 20, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.151 sec > Running org.jboss.as.naming.WritableServiceBasedNamingStoreTestCase > Tests run: 9, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.175 sec > Results : > Tests in error: > testRegisterURLSchemeHandler(org.jboss.as.naming.InitialContextTestCase): JBAS011857: NamingStore is null > Tests run: 70, Failures: 0, Errors: 1, Skipped: 0 > [INFO] ------------------------------------------------------------------------ > [INFO] Reactor Summary: > [INFO] > [INFO] JBoss Application Server: Build Configuration ..... SUCCESS [16.745s] > [INFO] JBoss Application Server: Parent Aggregator ....... SUCCESS [5.425s] > [INFO] JBoss Application Server: Protocol Utilities ...... SUCCESS [38.109s] > [INFO] JBoss Application Server: Controller Client ....... SUCCESS [18.200s] > [INFO] JBoss Application Server: Controller Core ......... SUCCESS [1:07.854s] > [INFO] JBoss Application Server: Deployment Repository ... SUCCESS [5.962s] > [INFO] JBoss Application Server: Version ................. SUCCESS [3.578s] > [INFO] JBoss Application Server: Process Controller ...... SUCCESS [12.553s] > [INFO] JBoss Application Server: Platform MBean integration SUCCESS [12.141s] > [INFO] JBoss Application Server: Domain Management ....... SUCCESS [14.524s] > [INFO] JBoss Application Server: Domain HTTP Interface ... SUCCESS [0.381s] > [INFO] JBoss Application Server: Domain HTTP Interface ... SUCCESS [7.821s] > [INFO] JBoss Application Server: Network ................. SUCCESS [5.345s] > [INFO] JBoss Application Server: Remoting Subsystem ...... SUCCESS [7.735s] > [INFO] JBoss Application Server: Server .................. SUCCESS [35.813s] > [INFO] JBoss Application Server: Management Client Content SUCCESS [6.731s] > [INFO] JBoss Application Server: Common Code for Subsystem and Non-subsystem Test Harness SUCCESS [9.894s] > [INFO] JBoss Application Server: Subsystem Test Harness .. SUCCESS [14.606s] > [INFO] JBoss Application Server: Threading Subsystem ..... SUCCESS [30.757s] > [INFO] JBoss Application Server: Host Controller ......... SUCCESS [29.205s] > [INFO] JBoss Application Server: Core Model Test Parent .. SUCCESS [0.755s] > [INFO] JBoss Application Server: Core Model Test Framework SUCCESS [8.585s] > [INFO] JBoss Application Server: Domain HTTP Error Context SUCCESS [2.921s] > [INFO] JBoss Application Server: Naming Subsystem ........ FAILURE [15.100s] > [INFO] JBoss Application Server: JMX Subsystem ........... SKIPPED > [INFO] JBoss Application Server: EE ...................... SKIPPED > [INFO] JBoss Application Server: JacORB Subsystem ........ SKIPPED > [INFO] JBoss Application Server: Transaction Subsystem ... SKIPPED > [INFO] JBoss Application Server: Clustering Subsystem .... SKIPPED > [INFO] JBoss Application Server: Clustering Server API ... SKIPPED > [INFO] JBoss Application Server: Common code for clustering subsystems SKIPPED > [INFO] JBoss Application Server: JGroups Subsystem ....... SKIPPED > [INFO] JBoss Application Server: Infinispan Subsystem .... SKIPPED > [INFO] JBoss Application Server: Security Subsystem ...... SKIPPED > [INFO] JBoss Application Server: Connector Subsystem ..... SKIPPED > [INFO] JBoss Application Server: Clustered registry service SKIPPED > [INFO] JBoss Application Server: EJB Subsystem ........... SKIPPED > [INFO] JBoss Application Server: Distributed Web Session SPI SKIPPED > [INFO] JBoss Application Server: Clustering Server API implementation SKIPPED > [INFO] JBoss Application Server: Distributed Web Session Infinispan provider SKIPPED > [INFO] JBoss Application Server: Web Subsystem ........... SKIPPED > [INFO] JBoss Application Server: Web Services Subsystem .. SKIPPED > [INFO] JBoss Application Server: Web Services Server Integration Subsystem SKIPPED > [INFO] JBoss Application Server: Application Client Bootstrap SKIPPED > [INFO] JBoss Application Server: Config Assembly ......... SKIPPED > [INFO] JBoss Application Server: Command line interface .. SKIPPED > [INFO] JBoss Application Server: EJB Client BOM .......... SKIPPED > [INFO] JBoss Application Server: JMS Client BOM .......... SKIPPED > [INFO] JBoss Application Server: EJB and JMS client combined jar SKIPPED > [INFO] JBoss Application Server: Clustered Stateful Session Bean cache Infinispan provider SKIPPED > [INFO] JBoss Application Server: Clustered service provider registry services SKIPPED > [INFO] JBoss Application Server: Clustered singleton services SKIPPED > [INFO] JBoss Application Server: EJB Container Managed Persistence Subsystem SKIPPED > [INFO] JBoss Application Server: Config Admin ............ SKIPPED > [INFO] JBoss Application Server: Deployment Scanner ...... SKIPPED > [INFO] JBoss Application Server: EE Deployment ........... SKIPPED > [INFO] JBoss Application Server: Embedded ................ SKIPPED > [INFO] JBoss Application Server: JAXR Client ............. SKIPPED > [INFO] JBoss Application Server: JPA Subsystem ........... SKIPPED > [INFO] JBoss Application Server: JPA SPI ................. SKIPPED > [INFO] JBoss Application Server: JPA UTIL ................ SKIPPED > [INFO] JBoss Application Server: JPA Subsystem ........... SKIPPED > [INFO] JBoss Application Server: Weld Integration ........ SKIPPED > [INFO] JBoss Application Server: JAX-RS Integration ...... SKIPPED > [INFO] JBoss Application Server: JBoss Diagnostic Reporter SKIPPED > [INFO] JBoss Application Server: JDR ..................... SKIPPED > [INFO] JBoss Application Server: JSF ..................... SKIPPED > [INFO] JBoss Application Server: JSF Subsystem ........... SKIPPED > [INFO] JBoss Application Server: JSF Injection Handlers .. SKIPPED > [INFO] JBoss Application Server: JSR-77 Subsystem ........ SKIPPED > [INFO] JBoss Application Server: Logging Subsystem ....... SKIPPED > [INFO] JBoss Application Server: Mail subsystem .......... SKIPPED > [INFO] JBoss Application Server: Messaging Subsystem ..... SKIPPED > [INFO] JBoss Application Server: ModCluster Subsystem .... SKIPPED > [INFO] JBoss Application Server: OSGi .................... SKIPPED > [INFO] JBoss Application Server: OSGi Subsystem .......... SKIPPED > [INFO] JBoss Application Server: OSGi Integration ........ SKIPPED > [INFO] JBoss Application Server: OSGi Integration ConfigAdmin SKIPPED > [INFO] JBoss Application Server: OSGi Integration Http ... SKIPPED > [INFO] JBoss Application Server: OSGi Integration JMX .... SKIPPED > [INFO] JBoss Application Server: OSGi Integration JPA .... SKIPPED > [INFO] JBoss Application Server: OSGi Integration JTA .... SKIPPED > [INFO] JBoss Application Server: OSGi Integration Naming . SKIPPED > [INFO] JBoss Application Server: OSGi Integration WebApp . SKIPPED > [INFO] JBoss Application Server: POJO Subsystem .......... SKIPPED > [INFO] JBoss Application Server: Service Archive Subsystem SKIPPED > [INFO] JBoss Application Server: System JMX Module ....... SKIPPED > [INFO] JBoss Application Server: XTS Subsystem ........... SKIPPED > [INFO] JBoss Application Server: Hibernate 3.6.x JPA integration SKIPPED > [INFO] JBoss Application Server: Hibernate 4.0.x JPA integration SKIPPED > [INFO] JBoss Application Server: OpenJPA 2.x JPA integration SKIPPED > [INFO] JBoss Application Server: Build ................... SKIPPED > [INFO] JBoss Application Server: Build Modular ........... SKIPPED > [INFO] JBoss Application Server: Arquillian .............. SKIPPED > [INFO] JBoss Application Server: Arquillian TestEnricher MSC SKIPPED > [INFO] JBoss Application Server: Arquillian Common ....... SKIPPED > [INFO] JBoss Application Server: Arquillian Embedded Container SKIPPED > [INFO] JBoss Application Server: Arquillian Protocol JMX . SKIPPED > [INFO] JBoss Application Server: Arquillian Managed Container SKIPPED > [INFO] JBoss Application Server: Arquillian Remote Container SKIPPED > [INFO] JBoss Application Server: Exported Java EE Specification APIs SKIPPED > [INFO] JBoss Application Server: Arquillian TestNG Integration SKIPPED > [INFO] JBoss Application Server: Arquillian Common Domain SKIPPED > [INFO] JBoss Application Server: Arquillian Remote Domain Container SKIPPED > [INFO] JBoss Application Server: Arquillian Managed Domain Container SKIPPED > [INFO] JBoss Application Server: Core Model Test Controller 7.1.2 SKIPPED > [INFO] JBoss Application Server: Core Model Test Controller Optional SKIPPED > [INFO] JBoss Application Server: Core Model Tests ........ SKIPPED > [INFO] JBoss Application Server: Distribution ............ SKIPPED > [INFO] JBoss Application Server Test Suite: Shared ....... SKIPPED > [INFO] JBoss Application Server: OSGi Launcher ........... SKIPPED > [INFO] JBoss Application Server: Remoting Subsystem Test . SKIPPED > [INFO] JBoss Application Server: Validation Tests for Exported Java EE Specification APIs SKIPPED > [INFO] JBoss Application Server: Web Services Tests Integration Subsystem SKIPPED > [INFO] JBoss Application Server Test Suite: Aggregator ... SKIPPED > [INFO] JBoss Application Server Test Suite: Integration .. SKIPPED > [INFO] JBoss Application Server Test Suite: Integration - Smoke SKIPPED > [INFO] ------------------------------------------------------------------------ > [INFO] BUILD FAILURE > [INFO] ------------------------------------------------------------------------ > [INFO] Total time: 6:36.380s > [INFO] Finished at: Sun Feb 24 22:56:01 CET 2013 > [INFO] Final Memory: 122M/348M > [INFO] ------------------------------------------------------------------------ > [ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.11:test (default-test) on project jboss-as-naming: There are test failures. > [ERROR] > [ERROR] Please refer to /home/jboss/JBoss-8.0/jboss-as/naming/target/surefire-reports for the individual test results. > [ERROR] -> [Help 1] > [ERROR] > [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. > [ERROR] Re-run Maven using the -X switch to enable full debug logging. > [ERROR] > [ERROR] For more information about the errors and possible solutions, please read the following articles: > [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException > [ERROR] > [ERROR] After correcting the problems, you can resume the build with the command > [ERROR] mvn <goals> -rf :jboss-as-naming -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (AS7-6616) AS 8: Testsuite fails on Solaris SPARC 10

by Frank Langelage (JIRA)

Frank Langelage created AS7-6616: ------------------------------------ Summary: AS 8: Testsuite fails on Solaris SPARC 10 Key: AS7-6616 URL: https://issues.jboss.org/browse/AS7-6616 Project: Application Server 7 Issue Type: Bug Affects Versions: 8.0.0.Alpha1 Environment: Solaris SPARC 10, Oracle JDK 1.6.0_41 Reporter: Frank Langelage Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 6.007 sec Running org.jboss.as.naming.subsystem.NamingSubsystemTestCase Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.346 sec Running org.jboss.as.naming.InitialContextTestCase Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.028 sec <<< FAILURE! Running org.jboss.as.naming.InitialContextFactoryTestCase Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.072 sec Running org.jboss.as.naming.NamingEventCoordinatorTestCase Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.059 sec Running org.jboss.as.naming.ServiceBasedNamingStoreTestCase Tests run: 8, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.091 sec Running org.jboss.as.naming.InMemoryNamingStoreTestCase Tests run: 16, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.057 sec Running org.jboss.as.naming.ObjectFactoryTestCase Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.012 sec Running org.jboss.as.naming.NamingContextTestCase Tests run: 20, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.151 sec Running org.jboss.as.naming.WritableServiceBasedNamingStoreTestCase Tests run: 9, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.175 sec Results : Tests in error: testRegisterURLSchemeHandler(org.jboss.as.naming.InitialContextTestCase): JBAS011857: NamingStore is null Tests run: 70, Failures: 0, Errors: 1, Skipped: 0 [INFO] ------------------------------------------------------------------------ [INFO] Reactor Summary: [INFO] [INFO] JBoss Application Server: Build Configuration ..... SUCCESS [16.745s] [INFO] JBoss Application Server: Parent Aggregator ....... SUCCESS [5.425s] [INFO] JBoss Application Server: Protocol Utilities ...... SUCCESS [38.109s] [INFO] JBoss Application Server: Controller Client ....... SUCCESS [18.200s] [INFO] JBoss Application Server: Controller Core ......... SUCCESS [1:07.854s] [INFO] JBoss Application Server: Deployment Repository ... SUCCESS [5.962s] [INFO] JBoss Application Server: Version ................. SUCCESS [3.578s] [INFO] JBoss Application Server: Process Controller ...... SUCCESS [12.553s] [INFO] JBoss Application Server: Platform MBean integration SUCCESS [12.141s] [INFO] JBoss Application Server: Domain Management ....... SUCCESS [14.524s] [INFO] JBoss Application Server: Domain HTTP Interface ... SUCCESS [0.381s] [INFO] JBoss Application Server: Domain HTTP Interface ... SUCCESS [7.821s] [INFO] JBoss Application Server: Network ................. SUCCESS [5.345s] [INFO] JBoss Application Server: Remoting Subsystem ...... SUCCESS [7.735s] [INFO] JBoss Application Server: Server .................. SUCCESS [35.813s] [INFO] JBoss Application Server: Management Client Content SUCCESS [6.731s] [INFO] JBoss Application Server: Common Code for Subsystem and Non-subsystem Test Harness SUCCESS [9.894s] [INFO] JBoss Application Server: Subsystem Test Harness .. SUCCESS [14.606s] [INFO] JBoss Application Server: Threading Subsystem ..... SUCCESS [30.757s] [INFO] JBoss Application Server: Host Controller ......... SUCCESS [29.205s] [INFO] JBoss Application Server: Core Model Test Parent .. SUCCESS [0.755s] [INFO] JBoss Application Server: Core Model Test Framework SUCCESS [8.585s] [INFO] JBoss Application Server: Domain HTTP Error Context SUCCESS [2.921s] [INFO] JBoss Application Server: Naming Subsystem ........ FAILURE [15.100s] [INFO] JBoss Application Server: JMX Subsystem ........... SKIPPED [INFO] JBoss Application Server: EE ...................... SKIPPED [INFO] JBoss Application Server: JacORB Subsystem ........ SKIPPED [INFO] JBoss Application Server: Transaction Subsystem ... SKIPPED [INFO] JBoss Application Server: Clustering Subsystem .... SKIPPED [INFO] JBoss Application Server: Clustering Server API ... SKIPPED [INFO] JBoss Application Server: Common code for clustering subsystems SKIPPED [INFO] JBoss Application Server: JGroups Subsystem ....... SKIPPED [INFO] JBoss Application Server: Infinispan Subsystem .... SKIPPED [INFO] JBoss Application Server: Security Subsystem ...... SKIPPED [INFO] JBoss Application Server: Connector Subsystem ..... SKIPPED [INFO] JBoss Application Server: Clustered registry service SKIPPED [INFO] JBoss Application Server: EJB Subsystem ........... SKIPPED [INFO] JBoss Application Server: Distributed Web Session SPI SKIPPED [INFO] JBoss Application Server: Clustering Server API implementation SKIPPED [INFO] JBoss Application Server: Distributed Web Session Infinispan provider SKIPPED [INFO] JBoss Application Server: Web Subsystem ........... SKIPPED [INFO] JBoss Application Server: Web Services Subsystem .. SKIPPED [INFO] JBoss Application Server: Web Services Server Integration Subsystem SKIPPED [INFO] JBoss Application Server: Application Client Bootstrap SKIPPED [INFO] JBoss Application Server: Config Assembly ......... SKIPPED [INFO] JBoss Application Server: Command line interface .. SKIPPED [INFO] JBoss Application Server: EJB Client BOM .......... SKIPPED [INFO] JBoss Application Server: JMS Client BOM .......... SKIPPED [INFO] JBoss Application Server: EJB and JMS client combined jar SKIPPED [INFO] JBoss Application Server: Clustered Stateful Session Bean cache Infinispan provider SKIPPED [INFO] JBoss Application Server: Clustered service provider registry services SKIPPED [INFO] JBoss Application Server: Clustered singleton services SKIPPED [INFO] JBoss Application Server: EJB Container Managed Persistence Subsystem SKIPPED [INFO] JBoss Application Server: Config Admin ............ SKIPPED [INFO] JBoss Application Server: Deployment Scanner ...... SKIPPED [INFO] JBoss Application Server: EE Deployment ........... SKIPPED [INFO] JBoss Application Server: Embedded ................ SKIPPED [INFO] JBoss Application Server: JAXR Client ............. SKIPPED [INFO] JBoss Application Server: JPA Subsystem ........... SKIPPED [INFO] JBoss Application Server: JPA SPI ................. SKIPPED [INFO] JBoss Application Server: JPA UTIL ................ SKIPPED [INFO] JBoss Application Server: JPA Subsystem ........... SKIPPED [INFO] JBoss Application Server: Weld Integration ........ SKIPPED [INFO] JBoss Application Server: JAX-RS Integration ...... SKIPPED [INFO] JBoss Application Server: JBoss Diagnostic Reporter SKIPPED [INFO] JBoss Application Server: JDR ..................... SKIPPED [INFO] JBoss Application Server: JSF ..................... SKIPPED [INFO] JBoss Application Server: JSF Subsystem ........... SKIPPED [INFO] JBoss Application Server: JSF Injection Handlers .. SKIPPED [INFO] JBoss Application Server: JSR-77 Subsystem ........ SKIPPED [INFO] JBoss Application Server: Logging Subsystem ....... SKIPPED [INFO] JBoss Application Server: Mail subsystem .......... SKIPPED [INFO] JBoss Application Server: Messaging Subsystem ..... SKIPPED [INFO] JBoss Application Server: ModCluster Subsystem .... SKIPPED [INFO] JBoss Application Server: OSGi .................... SKIPPED [INFO] JBoss Application Server: OSGi Subsystem .......... SKIPPED [INFO] JBoss Application Server: OSGi Integration ........ SKIPPED [INFO] JBoss Application Server: OSGi Integration ConfigAdmin SKIPPED [INFO] JBoss Application Server: OSGi Integration Http ... SKIPPED [INFO] JBoss Application Server: OSGi Integration JMX .... SKIPPED [INFO] JBoss Application Server: OSGi Integration JPA .... SKIPPED [INFO] JBoss Application Server: OSGi Integration JTA .... SKIPPED [INFO] JBoss Application Server: OSGi Integration Naming . SKIPPED [INFO] JBoss Application Server: OSGi Integration WebApp . SKIPPED [INFO] JBoss Application Server: POJO Subsystem .......... SKIPPED [INFO] JBoss Application Server: Service Archive Subsystem SKIPPED [INFO] JBoss Application Server: System JMX Module ....... SKIPPED [INFO] JBoss Application Server: XTS Subsystem ........... SKIPPED [INFO] JBoss Application Server: Hibernate 3.6.x JPA integration SKIPPED [INFO] JBoss Application Server: Hibernate 4.0.x JPA integration SKIPPED [INFO] JBoss Application Server: OpenJPA 2.x JPA integration SKIPPED [INFO] JBoss Application Server: Build ................... SKIPPED [INFO] JBoss Application Server: Build Modular ........... SKIPPED [INFO] JBoss Application Server: Arquillian .............. SKIPPED [INFO] JBoss Application Server: Arquillian TestEnricher MSC SKIPPED [INFO] JBoss Application Server: Arquillian Common ....... SKIPPED [INFO] JBoss Application Server: Arquillian Embedded Container SKIPPED [INFO] JBoss Application Server: Arquillian Protocol JMX . SKIPPED [INFO] JBoss Application Server: Arquillian Managed Container SKIPPED [INFO] JBoss Application Server: Arquillian Remote Container SKIPPED [INFO] JBoss Application Server: Exported Java EE Specification APIs SKIPPED [INFO] JBoss Application Server: Arquillian TestNG Integration SKIPPED [INFO] JBoss Application Server: Arquillian Common Domain SKIPPED [INFO] JBoss Application Server: Arquillian Remote Domain Container SKIPPED [INFO] JBoss Application Server: Arquillian Managed Domain Container SKIPPED [INFO] JBoss Application Server: Core Model Test Controller 7.1.2 SKIPPED [INFO] JBoss Application Server: Core Model Test Controller Optional SKIPPED [INFO] JBoss Application Server: Core Model Tests ........ SKIPPED [INFO] JBoss Application Server: Distribution ............ SKIPPED [INFO] JBoss Application Server Test Suite: Shared ....... SKIPPED [INFO] JBoss Application Server: OSGi Launcher ........... SKIPPED [INFO] JBoss Application Server: Remoting Subsystem Test . SKIPPED [INFO] JBoss Application Server: Validation Tests for Exported Java EE Specification APIs SKIPPED [INFO] JBoss Application Server: Web Services Tests Integration Subsystem SKIPPED [INFO] JBoss Application Server Test Suite: Aggregator ... SKIPPED [INFO] JBoss Application Server Test Suite: Integration .. SKIPPED [INFO] JBoss Application Server Test Suite: Integration - Smoke SKIPPED [INFO] ------------------------------------------------------------------------ [INFO] BUILD FAILURE [INFO] ------------------------------------------------------------------------ [INFO] Total time: 6:36.380s [INFO] Finished at: Sun Feb 24 22:56:01 CET 2013 [INFO] Final Memory: 122M/348M [INFO] ------------------------------------------------------------------------ [ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.11:test (default-test) on project jboss-as-naming: There are test failures. [ERROR] [ERROR] Please refer to /home/jboss/JBoss-8.0/jboss-as/naming/target/surefire-reports for the individual test results. [ERROR] -> [Help 1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException [ERROR] [ERROR] After correcting the problems, you can resume the build with the command [ERROR] mvn <goals> -rf :jboss-as-naming -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (AS7-6565) single jdbc driver deployed inside ear takes name of ear

by Tom Eicher (JIRA)

[ https://issues.jboss.org/browse/AS7-6565?page=com.atlassian.jira.plugin.s... ] Tom Eicher commented on AS7-6565: --------------------------------- Well, it should output the effective driver name, ready to use in the datasource, that was the idea of my bug report/feature request. Like: 23:07:12,011 INFO org.jboss.as.server#handleResult JBAS018559: Deployed "ifxjdbc_all.jar" (runtime-name : "ifxjdbc_all.jar_com.informix.jdbc.IfxDriver_3_70") > single jdbc driver deployed inside ear takes name of ear > -------------------------------------------------------- > > Key: AS7-6565 > URL: https://issues.jboss.org/browse/AS7-6565 > Project: Application Server 7 > Issue Type: Feature Request > Components: JCA > Affects Versions: 7.1.1.Final, 8.0.0.Alpha1 > Reporter: Tom Eicher > Assignee: Stefano Maestri > > We need to always give service name for jdbdriver as > {code} > deploymentUnit.getName() + "_" + driverClassName + "_" + majorVersion +"_" + minorVersion > {code} > even if thre is only one driver in the deployment unit. Current behavior is to give just deploymentUnit name in case of only one driver in. The changes makes more clear/readable driver names. > Original description was: > Including a JDBC driver, in this case PostgreSQL, in an ear like > {code} > myapp.ear: > lib/postgresql-9.1-901.jdbc4.jar > {code} > does deploy the driver: > {code} > 23:37:28,118 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-1) JBAS010404: Deploying non-JDBC-compliant driver class org.postgresql.Driver (version 9.1) > {code} > however the service name is not {{postgresql_9_1_901_jdbc4_jar}} as expected, > but it's {{myapp_ear}}. > (Seen in admin console, and this is the only value accepted in my -ds.xml file.) > 1. JDBC driver service should pick name of innermost jar, not of containing ear > 2. driver name (as to be used in datasource definition) should be logged with the log message above. -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-989) Build failure under windows due to UTF-8 characters

by Jan Roman (JIRA)

[ https://issues.jboss.org/browse/JBJCA-989?page=com.atlassian.jira.plugin.... ] Jan Roman updated JBJCA-989: ---------------------------- Attachment: JBJCA-989.diff resolution > Build failure under windows due to UTF-8 characters > --------------------------------------------------- > > Key: JBJCA-989 > URL: https://issues.jboss.org/browse/JBJCA-989 > Project: IronJacamar > Issue Type: Feature Request > Reporter: Jan Roman > Assignee: Jesper Pedersen > Priority: Minor > Attachments: JBJCA-989.diff > > > Build tasks are using default system charset which under windows can differ (in my case it was cp1451). As there are UTF-8 characters in sourcecode build is failing. > It is better to not rely on system defaults in build descriptors. > There is another problem with build on windows causing error message: > [metadata-parser] Generating Interface: Connector > [metadata-parser] Error at xsl:result-document on line 237 of : > [metadata-parser] Resolved URL is malformed: unknown protocol: c > This is caused by bug in ShrinkWrap which has been fixed in 2.0.0-alpha-5. -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-989) Build failure under windows due to UTF-8 characters

by Jan Roman (JIRA)

Jan Roman created JBJCA-989: ------------------------------- Summary: Build failure under windows due to UTF-8 characters Key: JBJCA-989 URL: https://issues.jboss.org/browse/JBJCA-989 Project: IronJacamar Issue Type: Feature Request Reporter: Jan Roman Assignee: Jesper Pedersen Priority: Minor Attachments: JBJCA-989.diff Build tasks are using default system charset which under windows can differ (in my case it was cp1451). As there are UTF-8 characters in sourcecode build is failing. It is better to not rely on system defaults in build descriptors. There is another problem with build on windows causing error message: [metadata-parser] Generating Interface: Connector [metadata-parser] Error at xsl:result-document on line 237 of : [metadata-parser] Resolved URL is malformed: unknown protocol: c This is caused by bug in ShrinkWrap which has been fixed in 2.0.0-alpha-5. -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-52) Both kie-api.jar and drools-compiler.jar contain org/kie/KieBase.class

by Geoffrey De Smet (JIRA)

[ https://issues.jboss.org/browse/DROOLS-52?page=com.atlassian.jira.plugin.... ] Geoffrey De Smet commented on DROOLS-52: ---------------------------------------- The latest snapshot build by jenkins of drools-compiler is 4.6 MB, so it's still a fat jar: https://repository.jboss.org/nexus/content/groups/public/org/drools/drool... > Both kie-api.jar and drools-compiler.jar contain org/kie/KieBase.class > ---------------------------------------------------------------------- > > Key: DROOLS-52 > URL: https://issues.jboss.org/browse/DROOLS-52 > Project: Drools > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Geoffrey De Smet > Assignee: Edson Tirelli > Priority: Blocker > > Both kie-api.jar and drools-compiler.jar contain org/kie/KieBase.class. > It looks like drools-compiler is fat jar. Fat jars (even shaded fat jars) are evil. See slide 39-42: > http://ge0ffrey.github.com/maven-dependency-puzzlers/maven-dependency-puz... > Certain platforms (android, ...) don't even allow to deploy such jars. Others (osgi, ...) throw warnings. -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-52) Both kie-api.jar and drools-compiler.jar contain org/kie/KieBase.class

by Geoffrey De Smet (JIRA)

Geoffrey De Smet created DROOLS-52: -------------------------------------- Summary: Both kie-api.jar and drools-compiler.jar contain org/kie/KieBase.class Key: DROOLS-52 URL: https://issues.jboss.org/browse/DROOLS-52 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Geoffrey De Smet Assignee: Edson Tirelli Priority: Blocker Both kie-api.jar and drools-compiler.jar contain org/kie/KieBase.class. It looks like drools-compiler is fat jar. Fat jars (even shaded fat jars) are evil. See slide 39-42: http://ge0ffrey.github.com/maven-dependency-puzzlers/maven-dependency-puz... Certain platforms (android, ...) don't even allow to deploy such jars. Others (osgi, ...) throw warnings. -- 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

13 years, 2 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira February 2013