[JBoss-dev] [JBoss JIRA] Updated: (JBBUILD-16) Use component-info to determine source repository information
[ http://jira.jboss.com/jira/browse/JBBUILD-16?page=history ] Ryan Campbell updated JBBUILD-16: - Description: Allow a component to expose its exports via a component-info.xml which other components will import as dependencies. The cvs repo location, module branch information need to be stored in a component's component-info.xml. This build.xml will be stored along with the component's artifacts in the build repository. This has significant impact on the synchronize lifecycle as the component-info for each component will need to be downloaded, and then each component will need to be synchronized based on that potentially updated information. was: The cvs repo location, module branch information need to be stored in a component's build.xml. This build.xml will be stored along with the component's artifacts in the build repository. This has significant impact on the synchronize lifecycle as the component-info for each component will need to be downloaded, and then each component will need to be synchronized based on that potentially updated information. Updated to include most recent required funtionality. Use component-info to determine source repository information - Key: JBBUILD-16 URL: http://jira.jboss.com/jira/browse/JBBUILD-16 Project: JBoss Build System Type: Feature Request Reporter: Ryan Campbell Assignee: Ryan Campbell Fix For: milestone-3 Allow a component to expose its exports via a component-info.xml which other components will import as dependencies. The cvs repo location, module branch information need to be stored in a component's component-info.xml. This build.xml will be stored along with the component's artifacts in the build repository. This has significant impact on the synchronize lifecycle as the component-info for each component will need to be downloaded, and then each component will need to be synchronized based on that potentially updated information. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Assigned: (JBAS-1668) Unit test failure: testJBossEditors (PropertyEditorsUnitTestCase)
[ http://jira.jboss.com/jira/browse/JBAS-1668?page=history ] Ryan Campbell reassigned JBAS-1668: --- Assign To: Scott M Stark Unit test failure: testJBossEditors (PropertyEditorsUnitTestCase) - Key: JBAS-1668 URL: http://jira.jboss.com/jira/browse/JBAS-1668 Project: JBoss Application Server Type: Bug Environment: win xp, linux Reporter: Pushkala Iyer Assignee: Scott M Stark We're seeing this test fail in multiple environments, can you please take a look at it. This is for the 4.0.2 Final release. The testJBossEditors test of the org.jboss.test.util.test.PropertyEditorsUnitTestCase fails due to an assertion failure. StackTrace: junit.framework.AssertionFailedError: Transform of Tue Jan 4 23:38:21 PST 2005 equals Tue Jan 04 23:38:21 CST 2005, output=Wed Jan 05 01:38:21 CST 2005 at org.jboss.test.util.test.PropertyEditorsUnitTestCase.doTests(PropertyEditorsUnitTestCase.java:226) at org.jboss.test.util.test.PropertyEditorsUnitTestCase.testJBossEditors(PropertyEditorsUnitTestCase.java:200) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Assigned: (JBAS-1666) Unit Test Failure: testSRPLoginWithAuxChallenge
[ http://jira.jboss.com/jira/browse/JBAS-1666?page=history ] Ryan Campbell reassigned JBAS-1666: --- Assign To: Scott M Stark Unit Test Failure: testSRPLoginWithAuxChallenge --- Key: JBAS-1666 URL: http://jira.jboss.com/jira/browse/JBAS-1666 Project: JBoss Application Server Type: Bug Components: Security Environment: win xp, linux Reporter: Pushkala Iyer Assignee: Scott M Stark We are seeing this test fail in multiple environments. As this is required for the 4.0.2 Final release, can you please take a look at it? Thanks, Test Case: org.jboss.test.security.test.SRPLoginModuleUnitTestCase Test : testSRPLoginWithAuxChallenge StackTrace: Unable to complete login: Failed to complete SRP login, msg=Failed to encrypt aux challenge junit.framework.AssertionFailedError: Unable to complete login: Failed to complete SRP login, msg=Failed to encrypt aux challenge at org.jboss.test.security.test.SRPLoginModuleUnitTestCase.testSRPLoginWithAuxChallenge(SRPLoginModuleUnitTestCase.java:128) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22) at junit.extensions.TestSetup$1.protect(TestSetup.java:19) at junit.extensions.TestSetup.run(TestSetup.java:23) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Assigned: (JBAS-1628) Naming SimpleUnitTestCase failures
[ http://jira.jboss.com/jira/browse/JBAS-1628?page=history ] Ryan Campbell reassigned JBAS-1628: --- Assign To: Scott M Stark Naming SimpleUnitTestCase failures -- Key: JBAS-1628 URL: http://jira.jboss.com/jira/browse/JBAS-1628 Project: JBoss Application Server Type: Bug Components: Naming Versions: JBossAS-4.0.2RC1 Environment: qa lab Reporter: Ryan Campbell Assignee: Scott M Stark testHaPartitionName and testDiscoveryPort are both failing due to a SocketTimeoutException: http://cruisecontrol.jboss.com/cc/artifacts/jboss-4.0-testsuite/20050323024613/results/org/jboss/test/naming/test/SimpleUnitTestCase.html org.jboss.test.naming.test.SimpleUnitTestCase.testHaPartitionName is failing: testHaParitionName: avax.naming.CommunicationException: Receive timed out [Root exception is java.net.SocketTimeoutException: Receive timed out] at org.jnp.interfaces.NamingContext.discoverServer(NamingContext.java:1302) at org.jnp.interfaces.NamingContext.checkRef(NamingContext.java:1382) at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:579) ... at org.jboss.test.naming.test.SimpleUnitTestCase.testHaParitionName(SimpleUnitTestCase.java:224) testDiscoveryPort is failing at the same point: ... at org.jboss.test.naming.test.SimpleUnitTestCase.testDiscoveryPort(SimpleUnitTestCase.java:265) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Assigned: (JBAS-1523) JBAS-30 - txtimers created via Servlet init get duplicated
[ http://jira.jboss.com/jira/browse/JBAS-1523?page=history ] Ryan Campbell reassigned JBAS-1523: --- Assign To: Pushkala Iyer (was: JBoss QA Lead) Pushkala, please drop this in your jboss-4.0.0 and run the testsuite. If it creates no additional failures, please resolve the issue. JBAS-30 - txtimers created via Servlet init get duplicated -- Key: JBAS-1523 URL: http://jira.jboss.com/jira/browse/JBAS-1523 Project: JBoss Application Server Type: Support Patch Versions: JBossAS-4.0.0 Final Reporter: Luc Texier Assignee: Pushkala Iyer Attachments: jboss_jar-patched.jar Some customers have expressed the wish to get the issue fixed in JBossAS 4.0.0 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Resolved: (HIBERNATE-13) testEjbInterception Unit Test failure
[ http://jira.jboss.com/jira/browse/HIBERNATE-13?page=history ] Ryan Campbell resolved HIBERNATE-13: Resolution: Done Well, it works now. Thanks, Steve. testEjbInterception Unit Test failure - Key: HIBERNATE-13 URL: http://jira.jboss.com/jira/browse/HIBERNATE-13 Project: Hibernate Type: Bug Environment: win xp sp2 Reporter: Pushkala Iyer Assignee: Ryan Campbell The following test is failing in the 4.0 branch and needs to be resolved before the 4.0.2 Final release. We've tested this in multiple environments and received the same error. Test Case: org.jboss.test.hibernate.test.HibernateIntgUnitTestCase Test : testEjbInterception Stack Trace: RemoteException occurred in server thread; nested exception is: java.rmi.ServerException: RuntimeException; nested exception is: org.jboss.util.NestedRuntimeException: Unable to retreive Session; - nested throwable: (net.sf.hibernate.HibernateException: Unable to locate SessionFactory in JNDI under name [java:/hibernate/SessionFactory]) java.rmi.ServerException: RemoteException occurred in server thread; nested exception is: java.rmi.ServerException: RuntimeException; nested exception is: org.jboss.util.NestedRuntimeException: Unable to retreive Session; - nested throwable: (net.sf.hibernate.HibernateException: Unable to locate SessionFactory in JNDI under name [java:/hibernate/SessionFactory]) at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:292) at sun.rmi.transport.Transport$1.run(Transport.java:148) at java.security.AccessController.doPrivileged(Native Method) at sun.rmi.transport.Transport.serviceCall(Transport.java:144) at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:460) at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:701) at java.lang.Thread.run(Thread.java:534) at sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(StreamRemoteCall.java:247) at sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:223) at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:133) at org.jboss.invocation.jrmp.server.JRMPInvoker_Stub.invoke(Unknown Source) at org.jboss.invocation.jrmp.interfaces.JRMPInvokerProxy.invoke(JRMPInvokerProxy.java:118) at org.jboss.invocation.InvokerInterceptor.invokeInvoker(InvokerInterceptor.java:227) at org.jboss.invocation.InvokerInterceptor.invoke(InvokerInterceptor.java:167) at org.jboss.proxy.TransactionInterceptor.invoke(TransactionInterceptor.java:46) at org.jboss.proxy.SecurityInterceptor.invoke(SecurityInterceptor.java:55) at org.jboss.proxy.ejb.StatelessSessionInterceptor.invoke(StatelessSessionInterceptor.java:97) at org.jboss.proxy.ClientContainer.invoke(ClientContainer.java:86) at $Proxy2.storeUser(Unknown Source) at org.jboss.test.hibernate.test.HibernateIntgUnitTestCase.testEjbInterception(HibernateIntgUnitTestCase.java:54) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22) at junit.extensions.TestSetup$1.protect(TestSetup.java:19) at junit.extensions.TestSetup.run(TestSetup.java:23) Caused by: java.rmi.ServerException: RuntimeException; nested exception is: org.jboss.util.NestedRuntimeException: Unable to retreive Session; - nested throwable: (net.sf.hibernate.HibernateException: Unable to locate SessionFactory in JNDI under name [java:/hibernate/SessionFactory]) at org.jboss.ejb.plugins.LogInterceptor.handleException(LogInterceptor.java:386) at org.jboss.ejb.plugins.LogInterceptor.invoke(LogInterceptor.java:196) at org.jboss.ejb.plugins.ProxyFactoryFinderInterceptor.invoke(ProxyFactoryFinderInterceptor.java:122) at org.jboss.ejb.SessionContainer.internalInvoke(SessionContainer.java:624) at org.jboss.ejb.Container.invoke(Container.java:873) at sun.reflect.GeneratedMethodAccessor315.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:141) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80) at org.jboss.mx.server.Invocation.invoke(Invocation.java:72) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:249) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644) at
[JBoss-dev] [JBoss JIRA] Assigned: (HIBERNATE-13) testEjbInterception Unit Test failure
[ http://jira.jboss.com/jira/browse/HIBERNATE-13?page=history ] Ryan Campbell reassigned HIBERNATE-13: -- Assign To: Steve Ebersole (was: Gavin King) testEjbInterception Unit Test failure - Key: HIBERNATE-13 URL: http://jira.jboss.com/jira/browse/HIBERNATE-13 Project: Hibernate Type: Bug Environment: win xp sp2 Reporter: Pushkala Iyer Assignee: Steve Ebersole The following test is failing in the 4.0 branch and needs to be resolved before the 4.0.2 Final release. We've tested this in multiple environments and received the same error. Test Case: org.jboss.test.hibernate.test.HibernateIntgUnitTestCase Test : testEjbInterception Stack Trace: RemoteException occurred in server thread; nested exception is: java.rmi.ServerException: RuntimeException; nested exception is: org.jboss.util.NestedRuntimeException: Unable to retreive Session; - nested throwable: (net.sf.hibernate.HibernateException: Unable to locate SessionFactory in JNDI under name [java:/hibernate/SessionFactory]) java.rmi.ServerException: RemoteException occurred in server thread; nested exception is: java.rmi.ServerException: RuntimeException; nested exception is: org.jboss.util.NestedRuntimeException: Unable to retreive Session; - nested throwable: (net.sf.hibernate.HibernateException: Unable to locate SessionFactory in JNDI under name [java:/hibernate/SessionFactory]) at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:292) at sun.rmi.transport.Transport$1.run(Transport.java:148) at java.security.AccessController.doPrivileged(Native Method) at sun.rmi.transport.Transport.serviceCall(Transport.java:144) at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:460) at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:701) at java.lang.Thread.run(Thread.java:534) at sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(StreamRemoteCall.java:247) at sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:223) at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:133) at org.jboss.invocation.jrmp.server.JRMPInvoker_Stub.invoke(Unknown Source) at org.jboss.invocation.jrmp.interfaces.JRMPInvokerProxy.invoke(JRMPInvokerProxy.java:118) at org.jboss.invocation.InvokerInterceptor.invokeInvoker(InvokerInterceptor.java:227) at org.jboss.invocation.InvokerInterceptor.invoke(InvokerInterceptor.java:167) at org.jboss.proxy.TransactionInterceptor.invoke(TransactionInterceptor.java:46) at org.jboss.proxy.SecurityInterceptor.invoke(SecurityInterceptor.java:55) at org.jboss.proxy.ejb.StatelessSessionInterceptor.invoke(StatelessSessionInterceptor.java:97) at org.jboss.proxy.ClientContainer.invoke(ClientContainer.java:86) at $Proxy2.storeUser(Unknown Source) at org.jboss.test.hibernate.test.HibernateIntgUnitTestCase.testEjbInterception(HibernateIntgUnitTestCase.java:54) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22) at junit.extensions.TestSetup$1.protect(TestSetup.java:19) at junit.extensions.TestSetup.run(TestSetup.java:23) Caused by: java.rmi.ServerException: RuntimeException; nested exception is: org.jboss.util.NestedRuntimeException: Unable to retreive Session; - nested throwable: (net.sf.hibernate.HibernateException: Unable to locate SessionFactory in JNDI under name [java:/hibernate/SessionFactory]) at org.jboss.ejb.plugins.LogInterceptor.handleException(LogInterceptor.java:386) at org.jboss.ejb.plugins.LogInterceptor.invoke(LogInterceptor.java:196) at org.jboss.ejb.plugins.ProxyFactoryFinderInterceptor.invoke(ProxyFactoryFinderInterceptor.java:122) at org.jboss.ejb.SessionContainer.internalInvoke(SessionContainer.java:624) at org.jboss.ejb.Container.invoke(Container.java:873) at sun.reflect.GeneratedMethodAccessor315.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:141) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80) at org.jboss.mx.server.Invocation.invoke(Invocation.java:72) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:249) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644) at
[JBoss-dev] [JBoss JIRA] Commented: (HIBERNATE-13) testEjbInterception Unit Test failure
[ http://jira.jboss.com/jira/browse/HIBERNATE-13?page=comments#action_12316776 ] Ryan Campbell commented on HIBERNATE-13: I'm still seeing this after applying Steve's fix from yesterday. The root exception is: Caused by: javax.naming.NameNotFoundException: hibernate not bound at org.jnp.server.NamingServer.getBinding(NamingServer.java:491) at org.jnp.server.NamingServer.getBinding(NamingServer.java:499) at org.jnp.server.NamingServer.getObject(NamingServer.java:505) at org.jnp.server.NamingServer.lookup(NamingServer.java:249) at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:610) at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:572) at javax.naming.InitialContext.lookup(InitialContext.java:347) at org.jboss.hibernate.session.HibernateContext.locateSessionFactory(HibernateContext.java:241) Looking at hibernate/src/etc/hibernate-service.xml it looks as though the session factory name may have changed from java:/hibernate/SessionFactory to java:/hibernate/HibernateFactory? Of course, the error is with hibernate not being bound, but I'm just wondering if the test is broken due to a config change w/ hibernate? testEjbInterception Unit Test failure - Key: HIBERNATE-13 URL: http://jira.jboss.com/jira/browse/HIBERNATE-13 Project: Hibernate Type: Bug Environment: win xp sp2 Reporter: Pushkala Iyer Assignee: Steve Ebersole The following test is failing in the 4.0 branch and needs to be resolved before the 4.0.2 Final release. We've tested this in multiple environments and received the same error. Test Case: org.jboss.test.hibernate.test.HibernateIntgUnitTestCase Test : testEjbInterception Stack Trace: RemoteException occurred in server thread; nested exception is: java.rmi.ServerException: RuntimeException; nested exception is: org.jboss.util.NestedRuntimeException: Unable to retreive Session; - nested throwable: (net.sf.hibernate.HibernateException: Unable to locate SessionFactory in JNDI under name [java:/hibernate/SessionFactory]) java.rmi.ServerException: RemoteException occurred in server thread; nested exception is: java.rmi.ServerException: RuntimeException; nested exception is: org.jboss.util.NestedRuntimeException: Unable to retreive Session; - nested throwable: (net.sf.hibernate.HibernateException: Unable to locate SessionFactory in JNDI under name [java:/hibernate/SessionFactory]) at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:292) at sun.rmi.transport.Transport$1.run(Transport.java:148) at java.security.AccessController.doPrivileged(Native Method) at sun.rmi.transport.Transport.serviceCall(Transport.java:144) at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:460) at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:701) at java.lang.Thread.run(Thread.java:534) at sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(StreamRemoteCall.java:247) at sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:223) at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:133) at org.jboss.invocation.jrmp.server.JRMPInvoker_Stub.invoke(Unknown Source) at org.jboss.invocation.jrmp.interfaces.JRMPInvokerProxy.invoke(JRMPInvokerProxy.java:118) at org.jboss.invocation.InvokerInterceptor.invokeInvoker(InvokerInterceptor.java:227) at org.jboss.invocation.InvokerInterceptor.invoke(InvokerInterceptor.java:167) at org.jboss.proxy.TransactionInterceptor.invoke(TransactionInterceptor.java:46) at org.jboss.proxy.SecurityInterceptor.invoke(SecurityInterceptor.java:55) at org.jboss.proxy.ejb.StatelessSessionInterceptor.invoke(StatelessSessionInterceptor.java:97) at org.jboss.proxy.ClientContainer.invoke(ClientContainer.java:86) at $Proxy2.storeUser(Unknown Source) at org.jboss.test.hibernate.test.HibernateIntgUnitTestCase.testEjbInterception(HibernateIntgUnitTestCase.java:54) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22) at junit.extensions.TestSetup$1.protect(TestSetup.java:19) at junit.extensions.TestSetup.run(TestSetup.java:23) Caused by: java.rmi.ServerException: RuntimeException; nested exception is: org.jboss.util.NestedRuntimeException: Unable to retreive Session; - nested throwable: (net.sf.hibernate.HibernateException: Unable to locate SessionFactory in JNDI under name
[JBoss-dev] [JBoss JIRA] Assigned: (JBAS-1284) SOAP SAAJ JBOSS implementation attachments bug
[ http://jira.jboss.com/jira/browse/JBAS-1284?page=history ] Ryan Campbell reassigned JBAS-1284: --- Assign To: Jason T. Greene (was: Jason T. Greene) SOAP SAAJ JBOSS implementation attachments bug -- Key: JBAS-1284 URL: http://jira.jboss.com/jira/browse/JBAS-1284 Project: JBoss Application Server Type: Feature Request Components: Web Services service Versions: JBossAS-4.0.1 Final Environment: Windows-XP SP2 Reporter: Frank Balba Assignee: Jason T. Greene Priority: Minor Using JBOSS-SAAJ implementation, no attachments could get through within a SOAP message. Creating attachments and adding them to a SOAP message will result a fine SOAP message on the client side however once it arrives to a dedicated servlet the received attachmentpart returns 'null' for attachmentPart.getContentType(). Using another SAAJ package (not the one included with JBOSS 4.0.1) eliminates this problem. Frank -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Updated: (HIBERNATE-13) testEjbInterception Unit Test failure
[ http://jira.jboss.com/jira/browse/HIBERNATE-13?page=history ] Ryan Campbell updated HIBERNATE-13: --- Description: The following test is failing in the 4.0 branch and needs to be resolved before the 4.0.2 Final release. We've tested this in multiple environments and received the same error. Test Case: org.jboss.test.hibernate.test.HibernateIntgUnitTestCase Test : testEjbInterception Stack Trace: RemoteException occurred in server thread; nested exception is: java.rmi.ServerException: RuntimeException; nested exception is: org.jboss.util.NestedRuntimeException: Unable to retreive Session; - nested throwable: (net.sf.hibernate.HibernateException: Unable to locate SessionFactory in JNDI under name [java:/hibernate/SessionFactory]) java.rmi.ServerException: RemoteException occurred in server thread; nested exception is: java.rmi.ServerException: RuntimeException; nested exception is: org.jboss.util.NestedRuntimeException: Unable to retreive Session; - nested throwable: (net.sf.hibernate.HibernateException: Unable to locate SessionFactory in JNDI under name [java:/hibernate/SessionFactory]) at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:292) at sun.rmi.transport.Transport$1.run(Transport.java:148) at java.security.AccessController.doPrivileged(Native Method) at sun.rmi.transport.Transport.serviceCall(Transport.java:144) at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:460) at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:701) at java.lang.Thread.run(Thread.java:534) at sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(StreamRemoteCall.java:247) at sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:223) at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:133) at org.jboss.invocation.jrmp.server.JRMPInvoker_Stub.invoke(Unknown Source) at org.jboss.invocation.jrmp.interfaces.JRMPInvokerProxy.invoke(JRMPInvokerProxy.java:118) at org.jboss.invocation.InvokerInterceptor.invokeInvoker(InvokerInterceptor.java:227) at org.jboss.invocation.InvokerInterceptor.invoke(InvokerInterceptor.java:167) at org.jboss.proxy.TransactionInterceptor.invoke(TransactionInterceptor.java:46) at org.jboss.proxy.SecurityInterceptor.invoke(SecurityInterceptor.java:55) at org.jboss.proxy.ejb.StatelessSessionInterceptor.invoke(StatelessSessionInterceptor.java:97) at org.jboss.proxy.ClientContainer.invoke(ClientContainer.java:86) at $Proxy2.storeUser(Unknown Source) at org.jboss.test.hibernate.test.HibernateIntgUnitTestCase.testEjbInterception(HibernateIntgUnitTestCase.java:54) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22) at junit.extensions.TestSetup$1.protect(TestSetup.java:19) at junit.extensions.TestSetup.run(TestSetup.java:23) Caused by: java.rmi.ServerException: RuntimeException; nested exception is: org.jboss.util.NestedRuntimeException: Unable to retreive Session; - nested throwable: (net.sf.hibernate.HibernateException: Unable to locate SessionFactory in JNDI under name [java:/hibernate/SessionFactory]) at org.jboss.ejb.plugins.LogInterceptor.handleException(LogInterceptor.java:386) at org.jboss.ejb.plugins.LogInterceptor.invoke(LogInterceptor.java:196) at org.jboss.ejb.plugins.ProxyFactoryFinderInterceptor.invoke(ProxyFactoryFinderInterceptor.java:122) at org.jboss.ejb.SessionContainer.internalInvoke(SessionContainer.java:624) at org.jboss.ejb.Container.invoke(Container.java:873) at sun.reflect.GeneratedMethodAccessor315.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:141) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:80) at org.jboss.mx.server.Invocation.invoke(Invocation.java:72) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:249) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:644) at org.jboss.invocation.jrmp.server.JRMPInvoker$MBeanServerAction.invoke(JRMPInvoker.java:805) at org.jboss.invocation.jrmp.server.JRMPInvoker.invoke(JRMPInvoker.java:406) at sun.reflect.GeneratedMethodAccessor90.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:261) at
[JBoss-dev] [JBoss JIRA] Updated: (JBBUILD-27) build for cache
[ http://jira.jboss.com/jira/browse/JBBUILD-27?page=history ] Ryan Campbell updated JBBUILD-27: - Description: Environment: Fix Version: milestone-2 (was: milestone-1) delaying until milestone 2 until I know what to do with this module. build for cache --- Key: JBBUILD-27 URL: http://jira.jboss.com/jira/browse/JBBUILD-27 Project: JBoss Build System Type: Sub-task Reporter: Ryan Campbell Assignee: Ryan Campbell Fix For: milestone-2 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Updated: (JBBUILD-32) build for deployment
[ http://jira.jboss.com/jira/browse/JBBUILD-32?page=history ] Ryan Campbell updated JBBUILD-32: - Description: Environment: Fix Version: milestone-1 (was: milestone-2) Moving to milestone-1 to compensate for cache build being delayed. build for deployment Key: JBBUILD-32 URL: http://jira.jboss.com/jira/browse/JBBUILD-32 Project: JBoss Build System Type: Sub-task Reporter: Ryan Campbell Assignee: Ryan Campbell Fix For: milestone-1 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Created: (JBBUILD-58) Cleanup of Common Module
Cleanup of Common Module Key: JBBUILD-58 URL: http://jira.jboss.com/jira/browse/JBBUILD-58 Project: JBoss Build System Type: Task Reporter: Ryan Campbell Assigned to: Ryan Campbell From Scott: There is a lot of unused utility classes along with obsolete functionality that is duplicating the jdk 1.4 behavior that I would like to get cleaned up jboss4.0+. Examples of such classes are: org.jboss.util.Coercible and all of org.jboss.util.coerce org.jboss.util.DirectoryBuilder org.jboss.util.MethodHashing org.jboss.util.Mu* org.jboss.util.collection.* much of this is now duplicate functionality org.jboss.net.sockets.RMI* is an unused experiement in multiplexing org.jboss.net.sockets.Timeout* is now obsolete functionality supported by the JDK sockets org.jboss.util.property.* is mostly unused org.jboss.util.stream.* org.jboss.xml.* should be incorported into the org.jboss.xml.* jbossxb framework at some point Before proceeding, modify this description with the precise list of classes to remove and get approval from affected developers. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Resolved: (JBBUILD-17) execant is broken on windows
[ http://jira.jboss.com/jira/browse/JBBUILD-17?page=history ]
Ryan Campbell resolved JBBUILD-17:
--
Resolution: Done
execant is broken on windows
Key: JBBUILD-17
URL: http://jira.jboss.com/jira/browse/JBBUILD-17
Project: JBoss Build System
Type: Bug
Reporter: Ryan Campbell
Fix For: milestone-1
When I tried to execute synchronize, I received an IOException: CreateProcess
ant -f jbossbuild.xml synchronize.after error=2
From what I can tell, error=2 is file not found. I think this is because of
the way execant is implemented using the exec task.
exec dir=@{dir}
executable=ant
arg line=-f jbossbuild.xml @{target}/
/exec
For windows it should be:
exec dir=@{dir}
executable=cmd
arg line=ant -f jbossbuild.xml @{target}/
/exec
So to fix this, we just need to do some conditional processing using the os
family information like in testsuite/imports/server-config.xml
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---
SF email is sponsored by - The IT Product Guide
Read honest candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Resolved: (JBBUILD-3) Add support for pre post-compilation tasks
[ http://jira.jboss.com/jira/browse/JBBUILD-3?page=history ] Ryan Campbell resolved JBBUILD-3: - Resolution: Done rmic, javacc have been implemented. Additional pre post processors will be implemented as needed, but the concept has been proven. Add support for pre post-compilation tasks - Key: JBBUILD-3 URL: http://jira.jboss.com/jira/browse/JBBUILD-3 Project: JBoss Build System Type: Task Reporter: Ryan Campbell Fix For: milestone-1 A component should be able to declare source which should be processed before or after compilation like rmic, javacc, or aopc. I belive this will work like the junit tests do. IE, a component declares some source which needs rmic (along with parameters), and tasks.xml declares a targetdef for rmic when it finds input requiring it. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Resolved: (JBBUILD-30) build for console
[ http://jira.jboss.com/jira/browse/JBBUILD-30?page=history ] Ryan Campbell resolved JBBUILD-30: -- Resolution: Done build for console - Key: JBBUILD-30 URL: http://jira.jboss.com/jira/browse/JBBUILD-30 Project: JBoss Build System Type: Sub-task Reporter: Ryan Campbell Fix For: milestone-1 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Resolved: (JBBUILD-29) build for connector
[ http://jira.jboss.com/jira/browse/JBBUILD-29?page=history ] Ryan Campbell resolved JBBUILD-29: -- Resolution: Done All artifacts for this build are complete. build for connector --- Key: JBBUILD-29 URL: http://jira.jboss.com/jira/browse/JBBUILD-29 Project: JBoss Build System Type: Sub-task Reporter: Ryan Campbell Fix For: milestone-1 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- This SF.net email is sponsored by Demarc: A global provider of Threat Management Solutions. Download our HomeAdmin security software for free today! http://www.demarc.com/info/Sentarus/hamr30 ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Resolved: (JBBUILD-44) build for messaging
[ http://jira.jboss.com/jira/browse/JBBUILD-44?page=history ] Ryan Campbell resolved JBBUILD-44: -- Assign To: Ryan Campbell Resolution: Done This build is complete. build for messaging --- Key: JBBUILD-44 URL: http://jira.jboss.com/jira/browse/JBBUILD-44 Project: JBoss Build System Type: Sub-task Reporter: Ryan Campbell Assignee: Ryan Campbell Fix For: milestone-1 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- This SF.net email is sponsored by Demarc: A global provider of Threat Management Solutions. Download our HomeAdmin security software for free today! http://www.demarc.com/info/Sentarus/hamr30 ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Commented: (JBBUILD-48) build for security
[ http://jira.jboss.com/jira/browse/JBBUILD-48?page=comments#action_12316559 ] Ryan Campbell commented on JBBUILD-48: -- As far as I can tell the existing server/build.xml does not indicate a dependency on the security module? I will move the org.jboss.security classes to the security module. build for security -- Key: JBBUILD-48 URL: http://jira.jboss.com/jira/browse/JBBUILD-48 Project: JBoss Build System Type: Sub-task Reporter: Ryan Campbell Fix For: milestone-1 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- This SF.net email is sponsored by Demarc: A global provider of Threat Management Solutions. Download our HomeAdmin security software for free today! http://www.demarc.com/info/Sentarus/hamr30 ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Commented: (JBBUILD-48) build for security
[ http://jira.jboss.com/jira/browse/JBBUILD-48?page=comments#action_12316563 ] Ryan Campbell commented on JBBUILD-48: -- To replicate the existing build, I think I would just need to add the following to security/jbossbuild.xml: artifactdef artifact=jbosssx.jar include input=jboss-security.jar include pattern=**/ /include ... I originally missed this in the security/build.xml. build for security -- Key: JBBUILD-48 URL: http://jira.jboss.com/jira/browse/JBBUILD-48 Project: JBoss Build System Type: Sub-task Reporter: Ryan Campbell Fix For: milestone-1 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- This SF.net email is sponsored by Demarc: A global provider of Threat Management Solutions. Download our HomeAdmin security software for free today! http://www.demarc.com/info/Sentarus/hamr30 ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Resolved: (JBBUILD-28) build for cluster
[ http://jira.jboss.com/jira/browse/JBBUILD-28?page=history ] Ryan Campbell resolved JBBUILD-28: -- Resolution: Done Fix Version: milestone-1 (was: milestone-2) The artifacts for this build are complete. build for cluster - Key: JBBUILD-28 URL: http://jira.jboss.com/jira/browse/JBBUILD-28 Project: JBoss Build System Type: Sub-task Reporter: Ryan Campbell Fix For: milestone-1 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- This SF.net email is sponsored by Demarc: A global provider of Threat Management Solutions. Download our HomeAdmin security software for free today! http://www.demarc.com/info/Sentarus/hamr30 ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Resolved: (JBBUILD-49) build for server
[ http://jira.jboss.com/jira/browse/JBBUILD-49?page=history ] Ryan Campbell resolved JBBUILD-49: -- Resolution: Done All artifacts for this build are complete. build for server Key: JBBUILD-49 URL: http://jira.jboss.com/jira/browse/JBBUILD-49 Project: JBoss Build System Type: Sub-task Reporter: Ryan Campbell Fix For: milestone-1 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- This SF.net email is sponsored by Demarc: A global provider of Threat Management Solutions. Download our HomeAdmin security software for free today! http://www.demarc.com/info/Sentarus/hamr30 ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Resolved: (JBBUILD-42) build for management
[ http://jira.jboss.com/jira/browse/JBBUILD-42?page=history ] Ryan Campbell resolved JBBUILD-42: -- Resolution: Done The artifacts for this module are complete. build for management Key: JBBUILD-42 URL: http://jira.jboss.com/jira/browse/JBBUILD-42 Project: JBoss Build System Type: Sub-task Reporter: Ryan Campbell Fix For: milestone-1 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- This SF.net email is sponsored by Demarc: A global provider of Threat Management Solutions. Download our HomeAdmin security software for free today! http://www.demarc.com/info/Sentarus/hamr30 ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Resolved: (JBBUILD-2) Add targetdefs for build.bin and build.resources
[ http://jira.jboss.com/jira/browse/JBBUILD-2?page=history ] Ryan Campbell resolved JBBUILD-2: - Assign To: Ryan Campbell Resolution: Done Both build.bin and build.resoureces have been implemented. Add targetdefs for build.bin and build.resources Key: JBBUILD-2 URL: http://jira.jboss.com/jira/browse/JBBUILD-2 Project: JBoss Build System Type: Task Reporter: Ryan Campbell Assignee: Ryan Campbell Fix For: milestone-1 Add targetdefs for build.bin and build.resources -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- This SF.net email is sponsored by Demarc: A global provider of Threat Management Solutions. Download our HomeAdmin security software for free today! http://www.demarc.com/info/Sentarus/hamr30 ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Resolved: (JBBUILD-48) build for security
[ http://jira.jboss.com/jira/browse/JBBUILD-48?page=history ] Ryan Campbell resolved JBBUILD-48: -- Resolution: Done All of the release artifacts for this module are now complete. build for security -- Key: JBBUILD-48 URL: http://jira.jboss.com/jira/browse/JBBUILD-48 Project: JBoss Build System Type: Sub-task Reporter: Ryan Campbell Fix For: milestone-1 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- This SF.net email is sponsored by Demarc: A global provider of Threat Management Solutions. Download our HomeAdmin security software for free today! http://www.demarc.com/info/Sentarus/hamr30 ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Created: (JBAS-1628) Naming SimpleUnitTestCase failures
Naming SimpleUnitTestCase failures -- Key: JBAS-1628 URL: http://jira.jboss.com/jira/browse/JBAS-1628 Project: JBoss Application Server Type: Bug Components: Naming Versions: JBossAS-4.0.2RC1 Environment: qa lab Reporter: Ryan Campbell testHaPartitionName and testDiscoveryPort are both failing due to a SocketTimeoutException: http://cruisecontrol.jboss.com/cc/artifacts/jboss-4.0-testsuite/20050323024613/results/org/jboss/test/naming/test/SimpleUnitTestCase.html org.jboss.test.naming.test.SimpleUnitTestCase.testHaPartitionName is failing: testHaParitionName: avax.naming.CommunicationException: Receive timed out [Root exception is java.net.SocketTimeoutException: Receive timed out] at org.jnp.interfaces.NamingContext.discoverServer(NamingContext.java:1302) at org.jnp.interfaces.NamingContext.checkRef(NamingContext.java:1382) at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:579) ... at org.jboss.test.naming.test.SimpleUnitTestCase.testHaParitionName(SimpleUnitTestCase.java:224) testDiscoveryPort is failing at the same point: ... at org.jboss.test.naming.test.SimpleUnitTestCase.testDiscoveryPort(SimpleUnitTestCase.java:265) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Resolved: (JBBUILD-39) build for jmx
[ http://jira.jboss.com/jira/browse/JBBUILD-39?page=history ] Ryan Campbell resolved JBBUILD-39: -- Resolution: Done all artifacts from this component are being built correctly build for jmx - Key: JBBUILD-39 URL: http://jira.jboss.com/jira/browse/JBBUILD-39 Project: JBoss Build System Type: Sub-task Reporter: Ryan Campbell Fix For: milestone-1 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Created: (JBBUILD-57) Support script (bin) artifacts
Support script (bin) artifacts -- Key: JBBUILD-57 URL: http://jira.jboss.com/jira/browse/JBBUILD-57 Project: JBoss Build System Type: Feature Request Reporter: Ryan Campbell Assigned to: Ryan Campbell Fix For: milestone-1 Allow an artifact like: artifact id=run.sh release=bin/ Which would come from component/output/bin. These bin artifacts will depend on the new build.bin target which copies them from src/bin, calls chmod and crlf as appropriate. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Resolved: (JBBUILD-57) Support script (bin) artifacts
[ http://jira.jboss.com/jira/browse/JBBUILD-57?page=history ] Ryan Campbell resolved JBBUILD-57: -- Resolution: Done This is complete, see server/jbossbuild.xml for an example. Support script (bin) artifacts -- Key: JBBUILD-57 URL: http://jira.jboss.com/jira/browse/JBBUILD-57 Project: JBoss Build System Type: Feature Request Reporter: Ryan Campbell Assignee: Ryan Campbell Fix For: milestone-1 Allow an artifact like: artifact id=run.sh release=bin/ Which would come from component/output/bin. These bin artifacts will depend on the new build.bin target which copies them from src/bin, calls chmod and crlf as appropriate. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Resolved: (JBBUILD-8) Add ResourceDefinition
[ http://jira.jboss.com/jira/browse/JBBUILD-8?page=history ] Ryan Campbell resolved JBBUILD-8: - Resolution: Done Ok, resources can now be artifacts. See sqlexception-service.xml in jboss/jbossbuild.xml for an example. Add ResourceDefinition -- Key: JBBUILD-8 URL: http://jira.jboss.com/jira/browse/JBBUILD-8 Project: JBoss Build System Type: Feature Request Reporter: Ryan Campbell Assignee: Ryan Campbell Priority: Critical Fix For: milestone-1 Allow resources to be defined like source. A component should be able to declare a resource where: resource id=jbossmq-httputil includes the source under src/resources/jbossmq-httputil which could be included in an artifact: artifactdef artifact=jbossmq.jar include input=jbossmq-httputil include pattern=*.xml/ /include /artifactdef which will add src/resources/jbossmq-httputil/*.xml to the jar. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Created: (JBCACHE-114) Standalone Build
Standalone Build Key: JBCACHE-114 URL: http://jira.jboss.com/jira/browse/JBCACHE-114 Project: JBoss Cache Type: Task Reporter: Ryan Campbell Assigned to: Bela Ban Ben and I have a plan for moving jboss-cache to a standalone build before the new build system is complete. 1. Bela eliminates dependencies 2. Ben creates basic standalone build.xml and adds jboss-cache.jar to jboss-thirdparty 3. Ryan removes cache from jboss-head, jboss-3.2 and jboss-4.0 cvs aliases 3. Ryan adds nightly jboss-cache standalone build to cruisecontrol Once jboss-cache has non-container tests migrated from testsuite... 1. Ben/Bela add tests to jboss-cache testsuite 2. Ryan adds test target to nightly cruisecontrol Ben said there will eventually be cache integration code in the AS, at which point: 1. Create a the new integration module (jboss-as-cache) 2. Add it to the cvs aliases as cache -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Assigned: (JBCACHE-114) Standalone Build
[ http://jira.jboss.com/jira/browse/JBCACHE-114?page=history ] Ryan Campbell reassigned JBCACHE-114: - Assign To: Ryan Campbell (was: Bela Ban) Standalone Build Key: JBCACHE-114 URL: http://jira.jboss.com/jira/browse/JBCACHE-114 Project: JBoss Cache Type: Task Reporter: Ryan Campbell Assignee: Ryan Campbell Ben and I have a plan for moving jboss-cache to a standalone build before the new build system is complete. 1. Bela eliminates dependencies 2. Ben creates basic standalone build.xml and adds jboss-cache.jar to jboss-thirdparty 3. Ryan removes cache from jboss-head, jboss-3.2 and jboss-4.0 cvs aliases 3. Ryan adds nightly jboss-cache standalone build to cruisecontrol Once jboss-cache has non-container tests migrated from testsuite... 1. Ben/Bela add tests to jboss-cache testsuite 2. Ryan adds test target to nightly cruisecontrol Ben said there will eventually be cache integration code in the AS, at which point: 1. Create a the new integration module (jboss-as-cache) 2. Add it to the cvs aliases as cache -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Created: (JBBUILD-55) JavaCC Support
JavaCC Support -- Key: JBBUILD-55 URL: http://jira.jboss.com/jira/browse/JBBUILD-55 Project: JBoss Build System Type: Feature Request Reporter: Ryan Campbell Assigned to: Ryan Campbell Fix For: milestone-1 Allow a project to generate parsers using javacc/jtree. The syntax should look like this: generatedsource id=jboss-ql-parser srcdir=main javacc=org/jboss/ejb/plugins/cmp/ejbql/JBossQLParser.jjt/ generatedsource id=ejb-ql-parser srcdir=main path=jboss-ql-parser javacc=org/jboss/ejb/plugins/cmp/ejbql/EJBQLParser.jjt/ source id=main include input=jboss-ql-parser/ ... This will put the output from javacc in output/gen-src/jboss-ql-parser. This directory will then be included in the compilation of the main source. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- This SF.net email is sponsored by Microsoft Mobile Embedded DevCon 2005 Attend MEDC 2005 May 9-12 in Vegas. Learn more about the latest Windows Embedded(r) Windows Mobile(tm) platforms, applications content. Register by 3/29 save $300 http://ads.osdn.com/?ad_id=6883alloc_id=15149op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Resolved: (JBBUILD-55) JavaCC Support
[ http://jira.jboss.com/jira/browse/JBBUILD-55?page=history ] Ryan Campbell resolved JBBUILD-55: -- Resolution: Done complete JavaCC Support -- Key: JBBUILD-55 URL: http://jira.jboss.com/jira/browse/JBBUILD-55 Project: JBoss Build System Type: Feature Request Reporter: Ryan Campbell Assignee: Ryan Campbell Fix For: milestone-1 Allow a project to generate parsers using javacc/jtree. The syntax should look like this: generatedsource id=jboss-ql-parser srcdir=main javacc=org/jboss/ejb/plugins/cmp/ejbql/JBossQLParser.jjt/ generatedsource id=ejb-ql-parser srcdir=main path=jboss-ql-parser javacc=org/jboss/ejb/plugins/cmp/ejbql/EJBQLParser.jjt/ source id=main include input=jboss-ql-parser/ ... This will put the output from javacc in output/gen-src/jboss-ql-parser. This directory will then be included in the compilation of the main source. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- This SF.net email is sponsored by Microsoft Mobile Embedded DevCon 2005 Attend MEDC 2005 May 9-12 in Vegas. Learn more about the latest Windows Embedded(r) Windows Mobile(tm) platforms, applications content. Register by 3/29 save $300 http://ads.osdn.com/?ad_id=6883alloc_id=15149op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Commented: (JBBUILD-49) build for server
[ http://jira.jboss.com/jira/browse/JBBUILD-49?page=comments#action_12316373 ] Ryan Campbell commented on JBBUILD-49: -- These classes are listed in the server/build.xml as requiring rmic, but they do not exist. org/jboss/jmx/adaptor/rmi/RMIAdaptorImpl.class, org/jboss/jmx/connector/notification/RMIClientNotificationListener.class build for server Key: JBBUILD-49 URL: http://jira.jboss.com/jira/browse/JBBUILD-49 Project: JBoss Build System Type: Sub-task Reporter: Ryan Campbell Fix For: milestone-1 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- This SF.net email is sponsored by Microsoft Mobile Embedded DevCon 2005 Attend MEDC 2005 May 9-12 in Vegas. Learn more about the latest Windows Embedded(r) Windows Mobile(tm) platforms, applications content. Register by 3/29 save $300 http://ads.osdn.com/?ad_id=6883alloc_id=15149op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Created: (JBBUILD-56) Add the buildpathelements element
Add the buildpathelements element - Key: JBBUILD-56 URL: http://jira.jboss.com/jira/browse/JBBUILD-56 Project: JBoss Build System Type: Feature Request Reporter: Ryan Campbell Assigned to: Ryan Campbell Fix For: milestone-1 Currently the pathelements/ node is used to expand the classpath for a given source. It does this by reading the class-path entry for included jars. This is used in javac, depend, and rmic. However, this node expands to include all transitive dependencies which is not what you want for compiling (though you do want it for testing, for example). So, we need a buildpathelements/ node which does not expand to include transitive dependencies. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- This SF.net email is sponsored by Microsoft Mobile Embedded DevCon 2005 Attend MEDC 2005 May 9-12 in Vegas. Learn more about the latest Windows Embedded(r) Windows Mobile(tm) platforms, applications content. Register by 3/29 save $300 http://ads.osdn.com/?ad_id=6883alloc_id=15149op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Resolved: (JBBUILD-56) Add the buildpathelements element
[ http://jira.jboss.com/jira/browse/JBBUILD-56?page=history ] Ryan Campbell resolved JBBUILD-56: -- Resolution: Done I added a getBuildPathElements to org/jboss/ant/util/MacroUtil to support this. I also modified tools/etc/jbossbuild/tasks.xml to use the new buildpathelements in the depends, javac, and rmic tasks. Add the buildpathelements element - Key: JBBUILD-56 URL: http://jira.jboss.com/jira/browse/JBBUILD-56 Project: JBoss Build System Type: Feature Request Reporter: Ryan Campbell Assignee: Ryan Campbell Fix For: milestone-1 Currently the pathelements/ node is used to expand the classpath for a given source. It does this by reading the class-path entry for included jars. This is used in javac, depend, and rmic. However, this node expands to include all transitive dependencies which is not what you want for compiling (though you do want it for testing, for example). So, we need a buildpathelements/ node which does not expand to include transitive dependencies. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- This SF.net email is sponsored by Microsoft Mobile Embedded DevCon 2005 Attend MEDC 2005 May 9-12 in Vegas. Learn more about the latest Windows Embedded(r) Windows Mobile(tm) platforms, applications content. Register by 3/29 save $300 http://ads.osdn.com/?ad_id=6883alloc_id=15149op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Commented: (JBAS-1595) Integrate EJB3 stable into JBoss 4.x
[ http://jira.jboss.com/jira/browse/JBAS-1595?page=comments#action_12316350 ] Ryan Campbell commented on JBAS-1595: - Ok, we will plan a jdk5 build of 4.0.2 Final. For now, we can run the EJB3 testsuite before building the jdk5 release. We can setup a cruisecontrol run for this in April. Integrate EJB3 stable into JBoss 4.x Key: JBAS-1595 URL: http://jira.jboss.com/jira/browse/JBAS-1595 Project: JBoss Application Server Type: Feature Request Components: EJBs Reporter: Ivelin Ivanov Assignee: Bill Burke Priority: Critical Stabilize the EJB3 implementation of spec DR2 and include it in the standard JBoss AS 4.x distribution. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- This SF.net email is sponsored by: 2005 Windows Mobile Application Contest Submit applications for Windows Mobile(tm)-based Pocket PCs or Smartphones for the chance to win $25,000 and application distribution. Enter today at http://ads.osdn.com/?ad_id=6882alloc_id=15148op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Created: (JBBUILD-25) Implement build for admin-console
Implement build for admin-console - Key: JBBUILD-25 URL: http://jira.jboss.com/jira/browse/JBBUILD-25 Project: JBoss Build System Type: Sub-task Reporter: Ryan Campbell Assigned to: Ryan Campbell -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Resolved: (JBBUILD-23) build for transaction
[ http://jira.jboss.com/jira/browse/JBBUILD-23?page=history ] Ryan Campbell resolved JBBUILD-23: -- Resolution: Done build for transaction - Key: JBBUILD-23 URL: http://jira.jboss.com/jira/browse/JBBUILD-23 Project: JBoss Build System Type: Sub-task Reporter: Ryan Campbell Assignee: Ryan Campbell Fix For: milestone-1 Build jboss-transaction.jar and jboss-transaction-client.jar -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Resolved: (JBBUILD-45) build for naming
[ http://jira.jboss.com/jira/browse/JBBUILD-45?page=history ] Ryan Campbell resolved JBBUILD-45: -- Resolution: Done Fix Version: milestone-1 (was: milestone-2) build for naming Key: JBBUILD-45 URL: http://jira.jboss.com/jira/browse/JBBUILD-45 Project: JBoss Build System Type: Sub-task Reporter: Ryan Campbell Fix For: milestone-1 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Resolved: (JBBUILD-31) build for container
[ http://jira.jboss.com/jira/browse/JBBUILD-31?page=history ] Ryan Campbell resolved JBBUILD-31: -- Resolution: Done Adrian completed this. build for container --- Key: JBBUILD-31 URL: http://jira.jboss.com/jira/browse/JBBUILD-31 Project: JBoss Build System Type: Sub-task Reporter: Ryan Campbell Fix For: milestone-1 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Resolved: (JBBUILD-47) build for remoting
[ http://jira.jboss.com/jira/browse/JBBUILD-47?page=history ] Ryan Campbell resolved JBBUILD-47: -- Resolution: Done build for remoting -- Key: JBBUILD-47 URL: http://jira.jboss.com/jira/browse/JBBUILD-47 Project: JBoss Build System Type: Sub-task Reporter: Ryan Campbell Fix For: milestone-1 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Resolved: (JBBUILD-19) Allow JARS to act as Sources
[ http://jira.jboss.com/jira/browse/JBBUILD-19?page=history ] Ryan Campbell resolved JBBUILD-19: -- Resolution: Done This is complete. There is no need to declare the source-jar, you just include the contents of the jar, like you would from output/classes: artifactdef artifact=log4j-boot.jar include input=log4j.jar include pattern=org/apache/log4j/*/ include pattern=org/apache/log4j/config/*/ include pattern=org/apache/log4j/helpers/*/ include pattern=org/apache/log4j/or/*/ include pattern=org/apache/log4j/spi/*/ /include /artifactdef This is using the zipfileset src attribute. If an archive is used as input, but there are no include subelements, it will be added to the artifact unexploded. Allow JARS to act as Sources Key: JBBUILD-19 URL: http://jira.jboss.com/jira/browse/JBBUILD-19 Project: JBoss Build System Type: Feature Request Reporter: Ryan Campbell Assignee: Ryan Campbell Priority: Critical Fix For: Q105 Original Estimate: 1 day Remaining: 1 day In the system module there is a need to unjar getopt log4j and recombine them into other artifacts. This is also done in security and perhaps in aspects. It seems like we should support this as a first-class construct. So this is another source, just like src/main or a resource: source-artifact id=log4j.jar/ which extracts the jar contents to output/log4j.jar/* . They could then be included in an artifact like any compiled class: artifactdef artifact=log4j-boot.jar include input=log4j.jar include pattern=org/apache/log4j/*/ include pattern=org/apache/log4j/config/*/ include pattern=org/apache/log4j/helpers/*/ include pattern=org/apache/log4j/or/*/ include pattern=org/apache/log4j/spi/*/ /include /artifactdef -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Updated: (JBBUILD-19) Allow JARS to act as Sources
[ http://jira.jboss.com/jira/browse/JBBUILD-19?page=history ] Ryan Campbell updated JBBUILD-19: - Description: In the system module there is a need to unjar getopt log4j and recombine them into other artifacts. This is also done in security and perhaps in aspects. It seems like we should support this as a first-class construct. They could then be included in an artifact like this: artifactdef artifact=log4j-boot.jar include input=log4j.jar include pattern=org/apache/log4j/*/ include pattern=org/apache/log4j/config/*/ include pattern=org/apache/log4j/helpers/*/ include pattern=org/apache/log4j/or/*/ include pattern=org/apache/log4j/spi/*/ /include /artifactdef was: In the system module there is a need to unjar getopt log4j and recombine them into other artifacts. This is also done in security and perhaps in aspects. It seems like we should support this as a first-class construct. So this is another source, just like src/main or a resource: source-artifact id=log4j.jar/ which extracts the jar contents to output/log4j.jar/* . They could then be included in an artifact like any compiled class: artifactdef artifact=log4j-boot.jar include input=log4j.jar include pattern=org/apache/log4j/*/ include pattern=org/apache/log4j/config/*/ include pattern=org/apache/log4j/helpers/*/ include pattern=org/apache/log4j/or/*/ include pattern=org/apache/log4j/spi/*/ /include /artifactdef Allow JARS to act as Sources Key: JBBUILD-19 URL: http://jira.jboss.com/jira/browse/JBBUILD-19 Project: JBoss Build System Type: Feature Request Reporter: Ryan Campbell Assignee: Ryan Campbell Priority: Critical Fix For: Q105 Original Estimate: 1 day Remaining: 1 day In the system module there is a need to unjar getopt log4j and recombine them into other artifacts. This is also done in security and perhaps in aspects. It seems like we should support this as a first-class construct. They could then be included in an artifact like this: artifactdef artifact=log4j-boot.jar include input=log4j.jar include pattern=org/apache/log4j/*/ include pattern=org/apache/log4j/config/*/ include pattern=org/apache/log4j/helpers/*/ include pattern=org/apache/log4j/or/*/ include pattern=org/apache/log4j/spi/*/ /include /artifactdef -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Created: (JBBUILD-21) Implement build for system module
Implement build for system module - Key: JBBUILD-21 URL: http://jira.jboss.com/jira/browse/JBBUILD-21 Project: JBoss Build System Type: Sub-task Reporter: Ryan Campbell Priority: Critical Fix For: Q105 Implement the build for this module. Completion of this module requires implementation of sourcejar as log4j.jar and getopt.jar need to be unpacked and their contents shuffled about. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Created: (JBBUILD-22) Implement Build for jaxrpc
Implement Build for jaxrpc -- Key: JBBUILD-22 URL: http://jira.jboss.com/jira/browse/JBBUILD-22 Project: JBoss Build System Type: Sub-task Reporter: Ryan Campbell Assigned to: Ryan Campbell Build axis-ws4ee.jar in the jaxrpc module. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Updated: (JBBUILD-22) Implement Build for jaxrpc
[ http://jira.jboss.com/jira/browse/JBBUILD-22?page=history ] Ryan Campbell updated JBBUILD-22: - Fix Version: Q105 Implement Build for jaxrpc -- Key: JBBUILD-22 URL: http://jira.jboss.com/jira/browse/JBBUILD-22 Project: JBoss Build System Type: Sub-task Reporter: Ryan Campbell Assignee: Ryan Campbell Fix For: Q105 Build axis-ws4ee.jar in the jaxrpc module. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Created: (JBBUILD-23) Implement build for transaction module
Implement build for transaction module -- Key: JBBUILD-23 URL: http://jira.jboss.com/jira/browse/JBBUILD-23 Project: JBoss Build System Type: Sub-task Reporter: Ryan Campbell Assigned to: Ryan Campbell Fix For: Q105 Build jboss-transaction.jar and jboss-transaction-client.jar -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Commented: (JBBUILD-19) Allow JARS to act as Sources
[ http://jira.jboss.com/jira/browse/JBBUILD-19?page=comments#action_12315818 ] Ryan Campbell commented on JBBUILD-19: -- Possibly look at zipfileset for this, as it can include files from other zip files, as well as those from the filesystem. Allow JARS to act as Sources Key: JBBUILD-19 URL: http://jira.jboss.com/jira/browse/JBBUILD-19 Project: JBoss Build System Type: Feature Request Reporter: Ryan Campbell Assignee: Ryan Campbell Priority: Critical Fix For: Q105 Original Estimate: 1 day Remaining: 1 day In the system module there is a need to unjar getopt log4j and recombine them into other artifacts. This is also done in security and perhaps in aspects. It seems like we should support this as a first-class construct. So this is another source, just like src/main or a resource: source-artifact id=log4j.jar/ which extracts the jar contents to output/log4j.jar/* . They could then be included in an artifact like any compiled class: artifactdef artifact=log4j-boot.jar include input=log4j.jar include pattern=org/apache/log4j/*/ include pattern=org/apache/log4j/config/*/ include pattern=org/apache/log4j/helpers/*/ include pattern=org/apache/log4j/or/*/ include pattern=org/apache/log4j/spi/*/ /include /artifactdef -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Created: (JBBUILD-24) Implement build for remoting module
Implement build for remoting module --- Key: JBBUILD-24 URL: http://jira.jboss.com/jira/browse/JBBUILD-24 Project: JBoss Build System Type: Sub-task Reporter: Ryan Campbell Assigned to: Ryan Campbell Fix For: Q105 Build jboss-remoting.jar -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Assigned: (JBBUILD-21) Implement build for system module
[ http://jira.jboss.com/jira/browse/JBBUILD-21?page=history ] Ryan Campbell reassigned JBBUILD-21: Assign To: Ryan Campbell Implement build for system module - Key: JBBUILD-21 URL: http://jira.jboss.com/jira/browse/JBBUILD-21 Project: JBoss Build System Type: Sub-task Reporter: Ryan Campbell Assignee: Ryan Campbell Priority: Critical Fix For: Q105 Implement the build for this module. Completion of this module requires implementation of sourcejar as log4j.jar and getopt.jar need to be unpacked and their contents shuffled about. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Commented: (JBBUILD-17) execant is broken on windows
[
http://jira.jboss.com/jira/browse/JBBUILD-17?page=comments#action_12315780 ]
Ryan Campbell commented on JBBUILD-17:
--
This needs to be fixed in tools/etc/jbossbuild/tasks.xml in jboss-head.
execant is broken on windows
Key: JBBUILD-17
URL: http://jira.jboss.com/jira/browse/JBBUILD-17
Project: JBoss Build System
Type: Bug
Reporter: Ryan Campbell
Fix For: Q105
When I tried to execute synchronize, I received an IOException: CreateProcess
ant -f jbossbuild.xml synchronize.after error=2
From what I can tell, error=2 is file not found. I think this is because of
the way execant is implemented using the exec task.
exec dir=@{dir}
executable=ant
arg line=-f jbossbuild.xml @{target}/
/exec
For windows it should be:
exec dir=@{dir}
executable=cmd
arg line=ant -f jbossbuild.xml @{target}/
/exec
So to fix this, we just need to do some conditional processing using the os
family information like in testsuite/imports/server-config.xml
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---
SF email is sponsored by - The IT Product Guide
Read honest candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Commented: (JBBUILD-22) Implement Build for jaxrpc
[ http://jira.jboss.com/jira/browse/JBBUILD-22?page=comments#action_12315785 ] Ryan Campbell commented on JBBUILD-22: -- I have implemented this build with the following caveats: 1. A compilation of any source now includes copying **/*.properties to the output! - the alternative (and real solution) to this is to extract those property files to a subdir under resources, but I don't want to alter the source just for the new build. 2. build.resources no longer requires src/resources to exist. jaxrpc has resources, but they aren't located in src/resources. 3. The old build required xerces to be in the root classpath of javac. This might be an issue when we port the build to 3.2 which needs to be compiled with jdk1.3? Implement Build for jaxrpc -- Key: JBBUILD-22 URL: http://jira.jboss.com/jira/browse/JBBUILD-22 Project: JBoss Build System Type: Sub-task Reporter: Ryan Campbell Assignee: Ryan Campbell Fix For: Q105 Build axis-ws4ee.jar in the jaxrpc module. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Created: (JBBUILD-19) Allow JARS to act as Sources
Allow JARS to act as Sources Key: JBBUILD-19 URL: http://jira.jboss.com/jira/browse/JBBUILD-19 Project: JBoss Build System Type: Feature Request Reporter: Ryan Campbell Priority: Critical Fix For: Q105 In the system module there is a need to unjar getopt log4j and recombine them into other artifacts. This is also done in security and perhaps in aspects. It seems like we should support this as a first-class construct. So this is another source, just like src/main or a resource: source-artifact id=log4j.jar/ which extracts the jar contents to output/log4j.jar/* . They could then be included in an artifact like any compiled class: artifactdef artifact=log4j-boot.jar include input=log4j.jar include pattern=org/apache/log4j/*/ include pattern=org/apache/log4j/config/*/ include pattern=org/apache/log4j/helpers/*/ include pattern=org/apache/log4j/or/*/ include pattern=org/apache/log4j/spi/*/ /include /artifactdef -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Assigned: (JBBUILD-19) Allow JARS to act as Sources
[ http://jira.jboss.com/jira/browse/JBBUILD-19?page=history ] Ryan Campbell reassigned JBBUILD-19: Assign To: Ryan Campbell Allow JARS to act as Sources Key: JBBUILD-19 URL: http://jira.jboss.com/jira/browse/JBBUILD-19 Project: JBoss Build System Type: Feature Request Reporter: Ryan Campbell Assignee: Ryan Campbell Priority: Critical Fix For: Q105 Original Estimate: 1 day Remaining: 1 day In the system module there is a need to unjar getopt log4j and recombine them into other artifacts. This is also done in security and perhaps in aspects. It seems like we should support this as a first-class construct. So this is another source, just like src/main or a resource: source-artifact id=log4j.jar/ which extracts the jar contents to output/log4j.jar/* . They could then be included in an artifact like any compiled class: artifactdef artifact=log4j-boot.jar include input=log4j.jar include pattern=org/apache/log4j/*/ include pattern=org/apache/log4j/config/*/ include pattern=org/apache/log4j/helpers/*/ include pattern=org/apache/log4j/or/*/ include pattern=org/apache/log4j/spi/*/ /include /artifactdef -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Created: (JBBUILD-14) Determine CVS Structure of Standalone Projects
Determine CVS Structure of Standalone Projects -- Key: JBBUILD-14 URL: http://jira.jboss.com/jira/browse/JBBUILD-14 Project: JBoss Build System Type: Task Reporter: Ryan Campbell Fix For: Q105 We need to determine how standalone builds will actually be stored in cvs. I'd like to propose the following: aop-standalone (viritual module in CVSROOT/modules) build (actual module: aop-build) release.xml jbossbuild.jar tasks.xml aop (actual module: jboss-aop) So you just have to do a cvs co aop-standalone, and you are ready to roll. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Created: (JBBUILD-15) Externalize Component.isLocal to property file
Externalize Component.isLocal to property file -- Key: JBBUILD-15 URL: http://jira.jboss.com/jira/browse/JBBUILD-15 Project: JBoss Build System Type: Feature Request Reporter: Ryan Campbell Fix For: Q105 To move a component from a binary build to a source build, you would need to add the version tag back on to the component definition. So that: [code]component id=container version=5.0-SNAPSHOT[/code]becomes this:[code]component id=container version=5.0-SNAPSHOT module=container[/code] And then you would do an ant -f release.xml synchronize.components to check it out. I know this needs to be in a property file instead. Perhaps just something like: [code] container.isLocal=true common.isLocal=false [/code] -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Created: (JBBUILD-16) Use component-info to determine source repository information
Use component-info to determine source repository information - Key: JBBUILD-16 URL: http://jira.jboss.com/jira/browse/JBBUILD-16 Project: JBoss Build System Type: Feature Request Reporter: Ryan Campbell Fix For: Q105 The cvs repo location, module branch information need to be stored in a component's component-info.xml in the build repository. This has significant impact on the synchronize lifecycle as the component-info for each component will need to be downloaded, and then each component will need to be synchronized based on that potentially updated information. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Created: (JBBUILD-17) execant is broken on windows
execant is broken on windows
Key: JBBUILD-17
URL: http://jira.jboss.com/jira/browse/JBBUILD-17
Project: JBoss Build System
Type: Bug
Reporter: Ryan Campbell
Fix For: Q105
When I tried to execute synchronize, I received an IOException: CreateProcess
ant -f jbossbuild.xml synchronize.after error=2
From what I can tell, error=2 is file not found. I think this is because of
the way execant is implemented using the exec task.
exec dir=@{dir}
executable=ant
arg line=-f jbossbuild.xml @{target}/
/exec
For windows it should be:
exec dir=@{dir}
executable=cmd
arg line=ant -f jbossbuild.xml @{target}/
/exec
So to fix this, we just need to do some conditional processing using the os
family information like in testsuite/imports/server-config.xml
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---
SF email is sponsored by - The IT Product Guide
Read honest candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Created: (JBBUILD-11) Publish target needed in tasks.xml
Publish target needed in tasks.xml -- Key: JBBUILD-11 URL: http://jira.jboss.com/jira/browse/JBBUILD-11 Project: JBoss Build System Type: Task Reporter: Ryan Campbell In order for cruisecontrol to publish the artifacts of the build to the repository, the build system must expose a publish target which locally copies each artifact of the build to a given location provided by cruisecontrol as a system property. This needs to be a part of the build system because that's where the artifacts are delineated, and the component version information is kept. Implementation-wise, there should be a new targetdef named publish with artifact nodes which copy each artifact to the given destination. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Commented: (JBBUILD-9) Implement build for aop
[ http://jira.jboss.com/jira/browse/JBBUILD-9?page=comments#action_12315460 ] Ryan Campbell commented on JBBUILD-9: - I have checked in an initial build for aop which reproduces the jdk 1.4 build. I have moved on to creating the standalone build for aop, which includes downloading of artifacts. Implement build for aop --- Key: JBBUILD-9 URL: http://jira.jboss.com/jira/browse/JBBUILD-9 Project: JBoss Build System Type: Sub-task Reporter: Ryan Campbell Implement the build for the aop module. This will need to include: - handling java 1.5 artifacts - building aop documentation - integrating with aop's non-standard unit tests - building standalone distribution -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Created: (JBBUILD-12) CruiseControl build for jboss-head/jbossas
CruiseControl build for jboss-head/jbossas -- Key: JBBUILD-12 URL: http://jira.jboss.com/jira/browse/JBBUILD-12 Project: JBoss Build System Type: Task Environment: cruisecontrol.jboss.com Reporter: Ryan Campbell Add the new build to cruisecontrol. Call the publish target to deploy the artifacts to the repository. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Updated: (JBBUILD-3) Add support for pre post-compilation tasks
[ http://jira.jboss.com/jira/browse/JBBUILD-3?page=history ] Ryan Campbell updated JBBUILD-3: Fix Version: Q105 Add support for pre post-compilation tasks - Key: JBBUILD-3 URL: http://jira.jboss.com/jira/browse/JBBUILD-3 Project: JBoss Build System Type: Task Reporter: Ryan Campbell Fix For: Q105 A component should be able to declare source which should be processed before or after compilation like rmic, javacc, or aopc. I belive this will work like the junit tests do. IE, a component declares some source which needs rmic (along with parameters), and tasks.xml declares a targetdef for rmic when it finds input requiring it. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Updated: (JBBUILD-4) Thirdparty module management
[ http://jira.jboss.com/jira/browse/JBBUILD-4?page=history ] Ryan Campbell updated JBBUILD-4: Fix Version: Q105 Thirdparty module management Key: JBBUILD-4 URL: http://jira.jboss.com/jira/browse/JBBUILD-4 Project: JBoss Build System Type: Bug Reporter: Scott M Stark Fix For: Q105 The management of the thirdparty jars in terms of duplication, version, licenses needs to be a natural part of the build system. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Updated: (JBBUILD-2) Add targetdefs for build.bin and build.resources
[ http://jira.jboss.com/jira/browse/JBBUILD-2?page=history ] Ryan Campbell updated JBBUILD-2: Fix Version: Q105 Add targetdefs for build.bin and build.resources Key: JBBUILD-2 URL: http://jira.jboss.com/jira/browse/JBBUILD-2 Project: JBoss Build System Type: Task Reporter: Ryan Campbell Fix For: Q105 Add targetdefs for build.bin and build.resources -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Updated: (JBBUILD-9) Implement build for aop
[ http://jira.jboss.com/jira/browse/JBBUILD-9?page=history ] Ryan Campbell updated JBBUILD-9: Fix Version: Q105 Implement build for aop --- Key: JBBUILD-9 URL: http://jira.jboss.com/jira/browse/JBBUILD-9 Project: JBoss Build System Type: Sub-task Reporter: Ryan Campbell Fix For: Q105 Implement the build for the aop module. This will need to include: - handling java 1.5 artifacts - building aop documentation - integrating with aop's non-standard unit tests - building standalone distribution -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Updated: (JBBUILD-1) Roll out new Build System to all modules under jboss-head
[ http://jira.jboss.com/jira/browse/JBBUILD-1?page=history ] Ryan Campbell updated JBBUILD-1: Fix Version: Q105 Roll out new Build System to all modules under jboss-head - Key: JBBUILD-1 URL: http://jira.jboss.com/jira/browse/JBBUILD-1 Project: JBoss Build System Type: Feature Request Reporter: Ryan Campbell Fix For: Q105 Adrian has implemented the common module build using the new build system. This needs to be rolled out to each module under jboss-head. Create a jbossbuild.xml in each module and integrate each with the top leve build in jbossas. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Updated: (JBBUILD-11) Publish target needed in tasks.xml
[ http://jira.jboss.com/jira/browse/JBBUILD-11?page=history ] Ryan Campbell updated JBBUILD-11: - Fix Version: Q105 Publish target needed in tasks.xml -- Key: JBBUILD-11 URL: http://jira.jboss.com/jira/browse/JBBUILD-11 Project: JBoss Build System Type: Task Reporter: Ryan Campbell Fix For: Q105 Original Estimate: 1 day Remaining: 1 day In order for cruisecontrol to publish the artifacts of the build to the repository, the build system must expose a publish target which locally copies each artifact of the build to a given location provided by cruisecontrol as a system property. This needs to be a part of the build system because that's where the artifacts are delineated, and the component version information is kept. Implementation-wise, there should be a new targetdef named publish with artifact nodes which copy each artifact to the given destination. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Updated: (JBBUILD-12) CruiseControl build for jboss-head/jbossas
[ http://jira.jboss.com/jira/browse/JBBUILD-12?page=history ] Ryan Campbell updated JBBUILD-12: - Fix Version: Q105 CruiseControl build for jboss-head/jbossas -- Key: JBBUILD-12 URL: http://jira.jboss.com/jira/browse/JBBUILD-12 Project: JBoss Build System Type: Task Environment: cruisecontrol.jboss.com Reporter: Ryan Campbell Fix For: Q105 Original Estimate: 1 day Remaining: 1 day Add the new build to cruisecontrol. Call the publish target to deploy the artifacts to the repository. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Updated: (JBBUILD-8) Add ResourceDefinition
[ http://jira.jboss.com/jira/browse/JBBUILD-8?page=history ] Ryan Campbell updated JBBUILD-8: Fix Version: Q105 Add ResourceDefinition -- Key: JBBUILD-8 URL: http://jira.jboss.com/jira/browse/JBBUILD-8 Project: JBoss Build System Type: Feature Request Reporter: Ryan Campbell Assignee: Ryan Campbell Priority: Critical Fix For: Q105 Allow resources to be defined like source. A component should be able to declare a resource where: resource id=jbossmq-httputil includes the source under src/resources/jbossmq-httputil which could be included in an artifact: artifactdef artifact=jbossmq.jar include input=jbossmq-httputil include pattern=*.xml/ /include /artifactdef which will add src/resources/jbossmq-httputil/*.xml to the jar. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Commented: (JBBUILD-8) Add ResourceDefinition
[ http://jira.jboss.com/jira/browse/JBBUILD-8?page=comments#action_12315461 ] Ryan Campbell commented on JBBUILD-8: - Resources can now be included in artifacts. However, a resource can not be an artifact itself yet. The current naieve implementation would add an artifactdef for each file type (xml, sh, etc). Perhaps we want an artifact of type resource which expects one file as input? Add ResourceDefinition -- Key: JBBUILD-8 URL: http://jira.jboss.com/jira/browse/JBBUILD-8 Project: JBoss Build System Type: Feature Request Reporter: Ryan Campbell Assignee: Ryan Campbell Priority: Critical Fix For: Q105 Allow resources to be defined like source. A component should be able to declare a resource where: resource id=jbossmq-httputil includes the source under src/resources/jbossmq-httputil which could be included in an artifact: artifactdef artifact=jbossmq.jar include input=jbossmq-httputil include pattern=*.xml/ /include /artifactdef which will add src/resources/jbossmq-httputil/*.xml to the jar. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Commented: (JBBUILD-8) Add ResourceDefinition
[ http://jira.jboss.com/jira/browse/JBBUILD-8?page=comments#action_12315462 ] Ryan Campbell commented on JBBUILD-8: - I meant to say that the current implementation could be extended naively, not that the current implementation is naieve. Add ResourceDefinition -- Key: JBBUILD-8 URL: http://jira.jboss.com/jira/browse/JBBUILD-8 Project: JBoss Build System Type: Feature Request Reporter: Ryan Campbell Assignee: Ryan Campbell Priority: Critical Fix For: Q105 Allow resources to be defined like source. A component should be able to declare a resource where: resource id=jbossmq-httputil includes the source under src/resources/jbossmq-httputil which could be included in an artifact: artifactdef artifact=jbossmq.jar include input=jbossmq-httputil include pattern=*.xml/ /include /artifactdef which will add src/resources/jbossmq-httputil/*.xml to the jar. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Created: (JBBUILD-10) Add Code Coverage
Add Code Coverage - Key: JBBUILD-10 URL: http://jira.jboss.com/jira/browse/JBBUILD-10 Project: JBoss Build System Type: Feature Request Reporter: Ryan Campbell Allow a component to generate unit test code coverage reports. Look at using Clover for this. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Created: (JBAOP-92) Move jboss-aop_1_0.dtd to src/resources/jboss-aop
Move jboss-aop_1_0.dtd to src/resources/jboss-aop - Key: JBAOP-92 URL: http://jira.jboss.com/jira/browse/JBAOP-92 Project: JBoss AOP Type: Task Reporter: Ryan Campbell Assigned to: Kabir Khan Priority: Optional Can I move jboss-aop_1_0.dtd from docs to src/resources/jboss-aop? Since its included in the jar, this seems like the Right Place. If it makes no difference to the existing build, it will make things easier for the new build which depends on projects following certain conventions such as this. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Commented: (JBAOP-92) Move jboss-aop_1_0.dtd to src/resources/jboss-aop
[ http://jira.jboss.com/jira/browse/JBAOP-92?page=comments#action_12315303 ] Ryan Campbell commented on JBAOP-92: Yes, I can work around this, which is why it is optional priority. This is not an immediate need. Move jboss-aop_1_0.dtd to src/resources/jboss-aop - Key: JBAOP-92 URL: http://jira.jboss.com/jira/browse/JBAOP-92 Project: JBoss AOP Type: Task Reporter: Ryan Campbell Assignee: Kabir Khan Priority: Optional Can I move jboss-aop_1_0.dtd from docs to src/resources/jboss-aop? Since its included in the jar, this seems like the Right Place. If it makes no difference to the existing build, it will make things easier for the new build which depends on projects following certain conventions such as this. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Created: (JBBUILD-9) Implement build for aop
Implement build for aop --- Key: JBBUILD-9 URL: http://jira.jboss.com/jira/browse/JBBUILD-9 Project: JBoss Build System Type: Sub-task Reporter: Ryan Campbell Implement the build for the aop module. This will need to include: - handling java 1.5 artifacts - building aop documentation - integrating with aop's non-standard unit tests - building standalone distribution -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Assigned: (JBBUILD-8) Add ResourceDefinition
[ http://jira.jboss.com/jira/browse/JBBUILD-8?page=history ] Ryan Campbell reassigned JBBUILD-8: --- Assign To: Ryan Campbell Add ResourceDefinition -- Key: JBBUILD-8 URL: http://jira.jboss.com/jira/browse/JBBUILD-8 Project: JBoss Build System Type: Feature Request Reporter: Ryan Campbell Assignee: Ryan Campbell Priority: Critical Allow resources to be defined like source. A component should be able to declare a resource where: resource id=jbossmq-httputil includes the source under src/resources/jbossmq-httputil which could be included in an artifact: artifactdef artifact=jbossmq.jar include input=jbossmq-httputil include pattern=*.xml/ /include /artifactdef which will add src/resources/jbossmq-httputil/*.xml to the jar. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag--drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Updated: (JBAS-1294) commons-logging.jar should be in default/lib
[ http://jira.jboss.com/jira/browse/JBAS-1294?page=history ] Ryan Campbell updated JBAS-1294: Fix Version: JBossAS-4.0.2RC1 commons-logging.jar should be in default/lib Key: JBAS-1294 URL: http://jira.jboss.com/jira/browse/JBAS-1294 Project: JBoss Application Server Type: Bug Versions: JBossAS-5.0 Alpha Reporter: Ryan Campbell Assignee: Ryan Campbell Priority: Minor Fix For: JBossAS-5.0 Alpha, JBossAS-4.0.2RC1 commons-logging is a dependency of Tomcat 5.5, however it is included in the default config via the ws4ee sar. Since it is a dependency of both, shouldn't it be removed from ws4ee and added to default lib? So that we go from: ./lib/commons-logging.jar ./server/all/lib/commons-logging.jar ./server/all/deploy/jboss-ws4ee.sar/commons-logging.jar ./server/default/deploy/jboss-ws4ee.sar/commons-logging.jar to: ./lib/commons-logging.jar ./server/all/lib/commons-logging.jar ./server/default/lib/commons-logging.jar -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595alloc_id=14396op=click ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Created: (JBBUILD-8) Add ResourceDefinition
Add ResourceDefinition -- Key: JBBUILD-8 URL: http://jira.jboss.com/jira/browse/JBBUILD-8 Project: JBoss Build System Type: Feature Request Reporter: Ryan Campbell Priority: Critical Allow resources to be defined like source. A component should be able to declare a resource where: resource id=jbossmq-httputil includes the source under src/resources/jbossmq-httputil which could be included in an artifact: artifactdef artifact=jbossmq.jar include input=jbossmq-httputil include pattern=*.xml/ /include /artifactdef which will add src/resources/jbossmq-httputil/*.xml to the jar. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag--drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Created: (JBBUILD-5) Add Ant task to modify 3rd party jar manifests
Add Ant task to modify 3rd party jar manifests -- Key: JBBUILD-5 URL: http://jira.jboss.com/jira/browse/JBBUILD-5 Project: JBoss Build System Type: Feature Request Reporter: Ryan Campbell We need to find/build a task to modify 3rd party jar manifests. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag--drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Created: (JBBUILD-1) Roll out new Build System to all modules under jboss-head
Roll out new Build System to all modules under jboss-head - Key: JBBUILD-1 URL: http://jira.jboss.com/jira/browse/JBBUILD-1 Project: JBoss Build System Type: Feature Request Reporter: Ryan Campbell Adrian has implemented the common module build using the new build system. This needs to be rolled out to each module under jboss-head. Create a jbossbuild.xml in each module and integrate each with the top leve build in jbossas. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag--drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Created: (JBBUILD-2) Add targetdefs for build.bin and build.resources
Add targetdefs for build.bin and build.resources Key: JBBUILD-2 URL: http://jira.jboss.com/jira/browse/JBBUILD-2 Project: JBoss Build System Type: Task Reporter: Ryan Campbell Add targetdefs for build.bin and build.resources -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag--drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Created: (JBBUILD-3) Add support for pre post-compilation tasks
Add support for pre post-compilation tasks - Key: JBBUILD-3 URL: http://jira.jboss.com/jira/browse/JBBUILD-3 Project: JBoss Build System Type: Task Reporter: Ryan Campbell A component should be able to declare source which should be processed before or after compilation like rmic, javacc, or aopc. I belive this will work like the junit tests do. IE, a component declares some source which needs rmic (along with parameters), and tasks.xml declares a targetdef for rmic when it finds input requiring it. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag--drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Assigned: (JBAS-1294) commons-logging.jar should be in default/lib
[ http://jira.jboss.com/jira/browse/JBAS-1294?page=history ] Ryan Campbell reassigned JBAS-1294: --- Assign To: Ryan Campbell (was: Scott M Stark) commons-logging.jar should be in default/lib Key: JBAS-1294 URL: http://jira.jboss.com/jira/browse/JBAS-1294 Project: JBoss Application Server Type: Bug Versions: JBossAS-5.0 Alpha Reporter: Ryan Campbell Assignee: Ryan Campbell Priority: Minor commons-logging is a dependency of Tomcat 5.5, however it is included in the default config via the ws4ee sar. Since it is a dependency of both, shouldn't it be removed from ws4ee and added to default lib? So that we go from: ./lib/commons-logging.jar ./server/all/lib/commons-logging.jar ./server/all/deploy/jboss-ws4ee.sar/commons-logging.jar ./server/default/deploy/jboss-ws4ee.sar/commons-logging.jar to: ./lib/commons-logging.jar ./server/all/lib/commons-logging.jar ./server/default/lib/commons-logging.jar -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Resolved: (JBAS-1294) commons-logging.jar should be in default/lib
[ http://jira.jboss.com/jira/browse/JBAS-1294?page=history ] Ryan Campbell resolved JBAS-1294: - Resolution: Done Fix Version: JBossAS-5.0 Alpha added commons-logging.jar to default/lib and removed it from jboss-ws4ee.jar commons-logging.jar should be in default/lib Key: JBAS-1294 URL: http://jira.jboss.com/jira/browse/JBAS-1294 Project: JBoss Application Server Type: Bug Versions: JBossAS-5.0 Alpha Reporter: Ryan Campbell Assignee: Ryan Campbell Priority: Minor Fix For: JBossAS-5.0 Alpha commons-logging is a dependency of Tomcat 5.5, however it is included in the default config via the ws4ee sar. Since it is a dependency of both, shouldn't it be removed from ws4ee and added to default lib? So that we go from: ./lib/commons-logging.jar ./server/all/lib/commons-logging.jar ./server/all/deploy/jboss-ws4ee.sar/commons-logging.jar ./server/default/deploy/jboss-ws4ee.sar/commons-logging.jar to: ./lib/commons-logging.jar ./server/all/lib/commons-logging.jar ./server/default/lib/commons-logging.jar -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Assigned: (JBPORTAL-180) Exception in JBossProfiler Forum
[ http://jira.jboss.com/jira/browse/JBPORTAL-180?page=history ] Ryan Campbell reassigned JBPORTAL-180: -- Assign To: Julien Viet (was: Ryan Campbell) Exception in JBossProfiler Forum Key: JBPORTAL-180 URL: http://jira.jboss.com/jira/browse/JBPORTAL-180 Project: JBoss Portal Type: Bug Components: Forums Environment: jboss.com Reporter: Clebert Suconic Assignee: Julien Viet Oftenly when replying messages into JbossProfiler forum I got a message Module threw an exception. This might be something related to the configuration on JBossProfiler or maybe some more generic bug. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Assigned: (JBPORTAL-180) Exception in JBossProfiler Forum
[ http://jira.jboss.com/jira/browse/JBPORTAL-180?page=history ] Ryan Campbell reassigned JBPORTAL-180: -- Assign To: Ryan Campbell (was: Julien Viet) Exception in JBossProfiler Forum Key: JBPORTAL-180 URL: http://jira.jboss.com/jira/browse/JBPORTAL-180 Project: JBoss Portal Type: Bug Components: Forums Environment: jboss.com Reporter: Clebert Suconic Assignee: Ryan Campbell Oftenly when replying messages into JbossProfiler forum I got a message Module threw an exception. This might be something related to the configuration on JBossProfiler or maybe some more generic bug. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Commented: (JBAS-1294) commons-logging.jar should be in default/lib
[ http://jira.jboss.com/jira/browse/JBAS-1294?page=comments#action_12314709 ] Ryan Campbell commented on JBAS-1294: - Ben added it to all/lib, but on further review I see it is excluded from default/lib by the partition-build target. I can fix this. Should commons-logging be removed from ws4ee.sar? It seems redundant if default all both include it. Perhaps this is a seperate issue for the webservice team to decide. commons-logging.jar should be in default/lib Key: JBAS-1294 URL: http://jira.jboss.com/jira/browse/JBAS-1294 Project: JBoss Application Server Type: Bug Versions: JBossAS-5.0 Alpha Reporter: Ryan Campbell Assignee: Scott M Stark Priority: Minor commons-logging is a dependency of Tomcat 5.5, however it is included in the default config via the ws4ee sar. Since it is a dependency of both, shouldn't it be removed from ws4ee and added to default lib? So that we go from: ./lib/commons-logging.jar ./server/all/lib/commons-logging.jar ./server/all/deploy/jboss-ws4ee.sar/commons-logging.jar ./server/default/deploy/jboss-ws4ee.sar/commons-logging.jar to: ./lib/commons-logging.jar ./server/all/lib/commons-logging.jar ./server/default/lib/commons-logging.jar -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Created: (JBAS-1294) commons-logging.jar should be in default/lib
commons-logging.jar should be in default/lib Key: JBAS-1294 URL: http://jira.jboss.com/jira/browse/JBAS-1294 Project: JBoss Application Server Type: Bug Versions: JBossAS-5.0 Alpha Reporter: Ryan Campbell Assigned to: Scott M Stark Priority: Minor commons-logging is a dependency of Tomcat 5.5, however it is included in the default config via the ws4ee sar. Since it is a dependency of both, shouldn't it be removed from ws4ee and added to default lib? So that we go from: ./lib/commons-logging.jar ./server/all/lib/commons-logging.jar ./server/all/deploy/jboss-ws4ee.sar/commons-logging.jar ./server/default/deploy/jboss-ws4ee.sar/commons-logging.jar to: ./lib/commons-logging.jar ./server/all/lib/commons-logging.jar ./server/default/lib/commons-logging.jar -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Assigned: (HIBERNATE-4) NPE in HibernateContext.prepareSession
[ http://jira.jboss.com/jira/browse/HIBERNATE-4?page=history ] Ryan Campbell reassigned HIBERNATE-4: - Assign To: Steve Ebersole (was: Gavin King) NPE in HibernateContext.prepareSession -- Key: HIBERNATE-4 URL: http://jira.jboss.com/jira/browse/HIBERNATE-4 Project: Hibernate Type: Bug Reporter: SourceForge User Assignee: Steve Ebersole Priority: Minor SourceForge Submitter: pilhuhn . Hi, this might be a pilot error ... When I try to obtain a session like this: Session = HibernateContext.getSession(java:/hibernate/SessionFactory); I get a NPE Caused by: java.lang.NullPointerException at org.jboss.hibernate.session.HibernateContext.prepareSession(HibernateContext.java:171) at org.jboss.hibernate.session.HibernateContext.getSession(HibernateContext.java:99) at de.bsd.adb_hibernate.server.ServerFacade.beispiel(ServerFacade.java:22) If I do it the classical way InitialContext ic = new InitialContext(); Object o = ic.lookup(java:/hibernate/SessionFactory); sf = (SessionFactory)o; Session sess = sf.openSession() it works as intended. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Assigned: (JBAS-1276) Remove usage of localhost in all tests
[ http://jira.jboss.com/jira/browse/JBAS-1276?page=history ]
Ryan Campbell reassigned JBAS-1276:
---
Assign To: Ryan Campbell (was: Scott M Stark)
Remove usage of localhost in all tests
--
Key: JBAS-1276
URL: http://jira.jboss.com/jira/browse/JBAS-1276
Project: JBoss Application Server
Type: Task
Components: Test Suite
Reporter: Ryan Campbell
Assignee: Ryan Campbell
All tests which currently hard code localhost need to use the value in
${node0} instead. Port these fixes to all branches. Make standard this clear
in the documentation.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Created: (JBAS-1276) Remove usage of localhost in all tests
Remove usage of localhost in all tests
--
Key: JBAS-1276
URL: http://jira.jboss.com/jira/browse/JBAS-1276
Project: JBoss Application Server
Type: Task
Components: Test Suite
Reporter: Ryan Campbell
Assigned to: Scott M Stark
All tests which currently hard code localhost need to use the value in ${node0}
instead. Port these fixes to all branches. Make standard this clear in the
documentation.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almosthttp://www.thinkgeek.com/sfshirt
___
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Created: (JBAS-76) Create Build Script for Functional Tests
Create Build Script for Functional Tests Key: JBAS-76 URL: http://jira.jboss.com/jira/browse/JBAS-76 Project: JBoss Application Server Type: Task Components: Test Suite Reporter: Ryan Campbell Assigned to: Scott M Stark There should be an ant build file for functional tests which can be imported by a module's tests/build.xml to define common targets such as compile, tests, and one-test. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Created: (JBAS-77) Document the Testsuite
Document the Testsuite -- Key: JBAS-77 URL: http://jira.jboss.com/jira/browse/JBAS-77 Project: JBoss Application Server Type: Task Components: Test Suite Reporter: Ryan Campbell Assigned to: Ryan Campbell Document the testsuite in docbook format. There needs to be an overall doc describing the layout of the testsuite, build.xml file structure, the files the build.xml imports and their usage. How tests are added to the build.xml depending on their need to use a specific unit test target like tests-clustering, tests-tomcat-sso, etc. also needs to be documented. It should also cover how to integrate module testsuites into the overall testsuite. http://www.jboss.org/wiki/Wiki.jsp?page=FunctionalTests http://www.jboss.org/wiki/Wiki.jsp?page=QualityAssurance -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Assigned: (JBAS-76) Create Build Script for Functional Tests
[ http://jira.jboss.com/jira/browse/JBAS-76?page=history ] Ryan Campbell reassigned JBAS-76: - Assign To: Ryan Campbell (was: Scott M Stark) Create Build Script for Functional Tests Key: JBAS-76 URL: http://jira.jboss.com/jira/browse/JBAS-76 Project: JBoss Application Server Type: Task Components: Test Suite Reporter: Ryan Campbell Assignee: Ryan Campbell There should be an ant build file for functional tests which can be imported by a module's tests/build.xml to define common targets such as compile, tests, and one-test. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Created: (JBAS-75) Test Server Binding Manager
Test Server Binding Manager Key: JBAS-75 URL: http://jira.jboss.com/jira/browse/JBAS-75 Project: JBoss Application Server Type: Task Components: Test Suite Reporter: Ryan Campbell Assigned to: Ryan Campbell There needs to be a regression test for the service binding functionality in the testsuite. A custom configuration will need to be created which uses the service binding manager to configures listners on non-standard ports. There will be at least one testcase for this configuration which will check that each service is listening on its assigned port. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Moved: (JBAS-17) Fix jboss.net MBeanProvider
[ http://jira.jboss.com/jira/browse/JBAS-17?page=history ] Ryan Campbell moved JBF-7 to JBAS-17: - Project: JBoss Application Server (was: JBoss_4.x) Key: JBAS-17 (was: JBF-7) Component: Web Services service (was: Web Services) Fix jboss.net MBeanProvider --- Key: JBAS-17 URL: http://jira.jboss.com/jira/browse/JBAS-17 Project: JBoss Application Server Type: Bug Components: Web Services service Reporter: Thomas Diesler Assignee: Ivelin Ivanov -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Moved: (JBAS-18) Check javax.ejb.EJBObject methods in ServiceDesc
[ http://jira.jboss.com/jira/browse/JBAS-18?page=history ] Ryan Campbell moved JBF-6 to JBAS-18: - Project: JBoss Application Server (was: JBoss_4.x) Key: JBAS-18 (was: JBF-6) Issue Type: Bug (was: Task) Component: Web Services service (was: Web Services) Check javax.ejb.EJBObject methods in ServiceDesc Key: JBAS-18 URL: http://jira.jboss.com/jira/browse/JBAS-18 Project: JBoss Application Server Type: Bug Components: Web Services service Reporter: Thomas Diesler Assignee: Ivelin Ivanov Priority: Minor Check if there are javax.ejb.EJBObject javax.ejb.EJBLocalObject methods in ServiceDesc. Do this for JBoss.Net as well. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] [JBoss JIRA] Moved: (JBAS-19) Notification based ws deployment
[ http://jira.jboss.com/jira/browse/JBAS-19?page=history ] Ryan Campbell moved JBF-5 to JBAS-19: - Project: JBoss Application Server (was: JBoss_4.x) Key: JBAS-19 (was: JBF-5) Component: Web Services service (was: Web Services) Notification based ws deployment Key: JBAS-19 URL: http://jira.jboss.com/jira/browse/JBAS-19 Project: JBoss Application Server Type: Bug Components: Web Services service Reporter: Thomas Diesler Assignee: Ivelin Ivanov The notification based web service deployment model does not fail the ejb/war deployment if there is an error in the ws deployment. Here we need the multiple deployers. The subdeployer model model does not work with ws4ee, because the ejb/servlet must be already deployed before ws deployment -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --- SF email is sponsored by - The IT Product Guide Read honest candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ ___ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
