[Design of JBoss Build System] - Build System Meeting Agenda Mar 15, 2007
by pgier
Progress Since Last Meeting
Released basic version of jboss-retro-maven-plugin. It can now generate and deploy jdk1.4 compatible files. Still need to implement the retro check functionality.
Tested the maven release plugin. This plugin was used to generate svn tags and deploy the maven plugins
Tested the assembly plugin. Created an assembly for jboss-common that could be used to create a combined common file.
Topics to Discuss
Review the release and assembly plugins. Discuss how they can be used for releases of various projects.
Discuss deployment of jdk1.4 compatible artifacts.
Carlo has started working on mavenizing the EJB project.
Have not heard from IT regarding the snapshot repository and the maven build server or the svn migration.
Goals for Next Meeting
Switch jboss microcontainer over to maven.
Migrate jboss-retro builds to maven
Complete the retro check functionality of the retro plugin
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4028461#4028461
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4028461
19 years
[Design of AOP on JBoss (Aspects/JBoss)] - Re: AspectFactory and classloading
by clebert.suconic＠jboss.com
I had a problem with this, when loading a perVM Aspect:
java.lang.ExceptionInInitializerError
| at org.jboss.jms.server.endpoint.ServerConnectionFactoryEndpoint.createConnectionDelegateInternal(ServerConnectionFactoryEndpoint.java:238)
| at org.jboss.jms.server.endpoint.ServerConnectionFactoryEndpoint.createConnectionDelegate(ServerConnectionFactoryEndpoint.java:137)
| at org.jboss.jms.server.endpoint.advised.ConnectionFactoryAdvised.org$jboss$jms$server$endpoint$advised$ConnectionFactoryAdvised$createConnectionDelegate$aop(ConnectionFactoryAdvised.java:88)
| at org.jboss.jms.server.endpoint.advised.ConnectionFactoryAdvised.createConnectionDelegate(ConnectionFactoryAdvised.java)
| at org.jboss.jms.wireformat.ConnectionFactoryCreateConnectionDelegateRequest.serverInvoke(ConnectionFactoryCreateConnectionDelegateRequest.java:103)
| at org.jboss.jms.server.remoting.JMSServerInvocationHandler.invoke(JMSServerInvocationHandler.java:125)
| at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:734)
| at org.jboss.remoting.transport.local.LocalClientInvoker.invoke(LocalClientInvoker.java:101)
| at org.jboss.remoting.Client.invoke(Client.java:1513)
| at org.jboss.remoting.Client.invoke(Client.java:527)
| at org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate.org$jboss$jms$client$delegate$ClientConnectionFactoryDelegate$createConnectionDelegate$aop(ClientConnectionFactoryDelegate.java:159)
| at org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate$createConnectionDelegate_4579211046834694258.invokeNext(ClientConnectionFactoryDelegate$createConnectionDelegate_4579211046834694258.java)
| at org.jboss.jms.client.container.StateCreationAspect.handleCreateConnectionDelegate(StateCreationAspect.java:83)
| at org.jboss.aop.advice.org.jboss.jms.client.container.StateCreationAspect0.invoke(StateCreationAspect0.java)
| at org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate$createConnectionDelegate_4579211046834694258.invokeNext(ClientConnectionFactoryDelegate$createConnectionDelegate_4579211046834694258.java)
| at org.jboss.jms.client.container.ExceptionInterceptor.invoke(ExceptionInterceptor.java:71)
| at org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate$createConnectionDelegate_4579211046834694258.invokeNext(ClientConnectionFactoryDelegate$createConnectionDelegate_4579211046834694258.java)
| at org.jboss.jms.client.container.ClientLogInterceptor.invoke(ClientLogInterceptor.java:107)
| at org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate$createConnectionDelegate_4579211046834694258.invokeNext(ClientConnectionFactoryDelegate$createConnectionDelegate_4579211046834694258.java)
| at org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate.createConnectionDelegate(ClientConnectionFactoryDelegate.java)
| at org.jboss.jms.client.JBossConnectionFactory.createConnectionInternal(JBossConnectionFactory.java:205)
| at org.jboss.jms.client.JBossConnectionFactory.createQueueConnection(JBossConnectionFactory.java:101)
| at org.jboss.jms.client.JBossConnectionFactory.createQueueConnection(JBossConnectionFactory.java:95)
| at org.jboss.resource.adapter.jms.inflow.dlq.AbstractDLQHandler.setupDLQConnection(AbstractDLQHandler.java:137)
| at org.jboss.resource.adapter.jms.inflow.dlq.AbstractDLQHandler.setup(AbstractDLQHandler.java:83)
| at org.jboss.resource.adapter.jms.inflow.dlq.JBossMQDLQHandler.setup(JBossMQDLQHandler.java:48)
| at org.jboss.resource.adapter.jms.inflow.JmsActivation.setupDLQ(JmsActivation.java:359)
| at org.jboss.resource.adapter.jms.inflow.JmsActivation.setup(JmsActivation.java:305)
| at org.jboss.resource.adapter.jms.inflow.JmsActivation$SetupActivation.run(JmsActivation.java:589)
| at org.jboss.resource.work.WorkWrapper.execute(WorkWrapper.java:204)
| at org.jboss.util.threadpool.BasicTaskWrapper.run(BasicTaskWrapper.java:275)
| at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:743)
| at java.lang.Thread.run(Thread.java:595)
| Caused by: java.lang.RuntimeException: java.lang.ClassNotFoundException: No ClassLoaders found for: org.jboss.jms.server.container.ServerLogInterceptor
| at org.jboss.aop.advice.GenericAspectFactory.getClazz(GenericAspectFactory.java:141)
| at org.jboss.aop.advice.GenericAspectFactory.createPerVM(GenericAspectFactory.java:152)
| at org.jboss.aop.AspectManager.createPerVmAspect(AspectManager.java:1744)
| at org.jboss.aop.AspectManager.getPerVMAspect(AspectManager.java:1726)
| at org.jboss.aop.AspectManager.getPerVMAspect(AspectManager.java:1716)
| at org.jboss.aop.advice.ScopedInterceptorFactory.create(ScopedInterceptorFactory.java:66)
| at org.jboss.aop.Advisor.createInterceptorChain(Advisor.java:613)
| at org.jboss.aop.Advisor.pointcutResolved(Advisor.java:883)
| at org.jboss.aop.Advisor.resolveMethodPointcut(Advisor.java:645)
| at org.jboss.aop.ClassAdvisor.createInterceptorChains(ClassAdvisor.java:604)
| at org.jboss.aop.ClassAdvisor.access$300(ClassAdvisor.java:82)
| at org.jboss.aop.ClassAdvisor$1.run(ClassAdvisor.java:299)
| at java.security.AccessController.doPrivileged(Native Method)
| at org.jboss.aop.ClassAdvisor.attachClass(ClassAdvisor.java:271)
| at org.jboss.aop.AspectManager.initialiseClassAdvisor(AspectManager.java:590)
| at org.jboss.aop.AspectManager.getAdvisor(AspectManager.java:578)
| at org.jboss.jms.server.endpoint.advised.ConnectionAdvised.<clinit>(ConnectionAdvised.java)
| ... 33 more
| Caused by: java.lang.ClassNotFoundException: No ClassLoaders found for: org.jboss.jms.server.container.ServerLogInterceptor
| at org.jboss.mx.loading.LoadMgr3.beginLoadTask(LoadMgr3.java:212)
| at org.jboss.mx.loading.RepositoryClassLoader.loadClassImpl(RepositoryClassLoader.java:511)
| at org.jboss.mx.loading.RepositoryClassLoader.loadClass(RepositoryClassLoader.java:405)
| at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
| at org.jboss.aop.advice.AspectFactoryWithClassLoaderSupport.loadClass(AspectFactoryWithClassLoaderSupport.java:80)
| at org.jboss.aop.advice.GenericAspectFactory.getClazz(GenericAspectFactory.java:137)
| ... 49 more
|
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4028460#4028460
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4028460
19 years
[Design of JBoss Build System] - Re: New JBoss Deploy Plugin
by pgier
"wolfc" wrote : I spotted a few problems:
|
| 1. The maven artifacts are getting deployed to ${maven.cvs.root}, which is an unset variable. Do I have to set it, or should it be derived from jboss.repository.root by the plugin?
|
They are two separate variable, so you will have to add ${maven.cvs.root} to your settings.xml. Since the location of these two repositories could be separate, they are separate variables. I will add some information to the wiki. I think I'll change ${maven.cvs.root} to ${maven.repository.root} in the next parent pom so that the names are more clear.
"wolfc" wrote :
| 2. My aggrate is ignored: [INFO] Ignoring project with packaging type: pom
| 3. Will imports be autogenerated or shall I add them to the poms (TODO in plugin)?
Both of these are todo items. I wasn't sure how to handle aggregates with the deploy plugin, but I think I have some ideas now and I should be able to get that implemented next week.
For the imports, you can put the list into the deploy plugin configuration. I added a 1.1-beta version of the deploy plugin to the repository, and I updated the wiki page here with an example of how to use the imports and exports config.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4028456#4028456
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4028456
19 years