January 2008 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBBUILD-408) Figure out a way to use alternate pom files in modules.

by Paul Gier (JIRA)

Figure out a way to use alternate pom files in modules. ------------------------------------------------------- Key: JBBUILD-408 URL: http://jira.jboss.com/jira/browse/JBBUILD-408 Project: JBoss Build System Issue Type: Task Components: Maven Reporter: Paul Gier Fix For: Maven Build - App Server Currently the jdk14 builds have to be done as separate modules, because maven is not able to use alternate files (pom-jdk14.xml) in modules. This issue has been created to address this in maven: http://jira.codehaus.org/browse/MNG-3150 Until this issue is resolved, maybe an ant script can be created to build the modules as an aggregate. -- 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 - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 3 months

1
4
0 / 0

[JBoss JIRA] Created: (JBBUILD-417) Change maven classpath ordering for dependencies

by Paul Gier (JIRA)

Change maven classpath ordering for dependencies ------------------------------------------------ Key: JBBUILD-417 URL: http://jira.jboss.com/jira/browse/JBBUILD-417 Project: JBoss Build System Issue Type: Feature Request Components: Maven Reporter: Paul Gier Fix For: Maven Build - Maint 2007 Currently maven puts transitive dependencies first in the compile and test classpaths. It would be better to have direct dependencies listed first. See this maven issue: http://jira.codehaus.org/browse/MNG-3197 -- 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 - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 3 months

1
2
0 / 0

[JBoss JIRA] Created: (JBBUILD-391) Create jboss.org site for maven-jdocbook-plugin

by Paul Gier (JIRA)

Create jboss.org site for maven-jdocbook-plugin ----------------------------------------------- Key: JBBUILD-391 URL: http://jira.jboss.com/jira/browse/JBBUILD-391 Project: JBoss Build System Issue Type: Task Reporter: Paul Gier Assigned To: Paul Gier Fix For: Maven Build - Maint 2007 Steve created the jdocbook plugin for maven. This should be the new standard docbook configuration within jboss. A site needs to be created for the plugin documentation on jboss.org. -- 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 - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 3 months

1
4
0 / 0

[JBoss JIRA] Updated: (JBBUILD-251) Pulling down src or binaries based upon configuration

by Paul Gier (JIRA)

[ http://jira.jboss.com/jira/browse/JBBUILD-251?page=all ] Paul Gier updated JBBUILD-251: ------------------------------ Fix Version/s: JBossBuild - Maint 2008 (was: JBossBuild - Maint 2007) > Pulling down src or binaries based upon configuration > ----------------------------------------------------- > > Key: JBBUILD-251 > URL: http://jira.jboss.com/jira/browse/JBBUILD-251 > Project: JBoss Build System > Issue Type: Feature Request > Components: Maven > Reporter: Ruel Loehr > Fix For: JBossBuild - Maint 2008 > > Original Estimate: 4 days > Remaining Estimate: 4 days > > From Adrian on the dev list: > The problem I don't see addressed (and the main reason why I started the jbossbuild prototype) is to have a top level which includes multiple projects. > e.g. I wanted people to be able to do something like: > <build> > <component name="JBossAS" download="binary" quality="LastGoodTests"> > <component name="EJB3" download="source"/> > </component> > <component name="Seam" download="source"/> </build> > This would checkout the last binaries for JBossAS that passed the testsuite (except EJB3 which is latest source) and also Seam. > You would then be able to build a Seam environment with just the > EJB3 and Seam sources. > i.e. the developer only has to worry about the problems with the stuff he is working on, rather than figuring out why something unrelated doesn't compile/work. > Instead, the jbossbuild project morphed into a mechanism to download thirdparty binaries with buildmagic still used for the main build. -- 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 - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 3 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBBUILD-316) Disallow releases other than snapshots to depend on a snapshot version

by Paul Gier (JIRA)

[ http://jira.jboss.com/jira/browse/JBBUILD-316?page=all ] Paul Gier updated JBBUILD-316: ------------------------------ Fix Version/s: JBossBuild - Maint 2008 (was: JBossBuild - Maint 2007) > Disallow releases other than snapshots to depend on a snapshot version > ---------------------------------------------------------------------- > > Key: JBBUILD-316 > URL: http://jira.jboss.com/jira/browse/JBBUILD-316 > Project: JBoss Build System > Issue Type: Feature Request > Components: Maven, JBossBuild > Reporter: Scott M Stark > Assigned To: Paul Gier > Fix For: JBossBuild - Maint 2008 > > > We need to disallow releases other than snapshots to depend on a snapshot version. If a release does not have a snapshot qualifier, it cannot declare that it depends on another release's snapshot version. -- 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 - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 3 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBBUILD-53) Create an installer based on the build repository and dependecy features

by Paul Gier (JIRA)

[ http://jira.jboss.com/jira/browse/JBBUILD-53?page=all ] Paul Gier updated JBBUILD-53: ----------------------------- Fix Version/s: JBossBuild - Maint 2008 (was: JBossBuild - Maint 2007) > Create an installer based on the build repository and dependecy features > ------------------------------------------------------------------------ > > Key: JBBUILD-53 > URL: http://jira.jboss.com/jira/browse/JBBUILD-53 > Project: JBoss Build System > Issue Type: Feature Request > Components: JBossBuild > Reporter: Ivelin Ivanov > Fix For: JBossBuild - Maint 2008 > > Attachments: eee installation tree.JPG > > > Build an installer document or set of convenience utilities using the capability of the build system to package a container configuration beased on high level services dependency definitions and binary repository download. -- 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 - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 3 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBBUILD-157) Libs not deleted when updating from repository

by Paul Gier (JIRA)

[ http://jira.jboss.com/jira/browse/JBBUILD-157?page=all ] Paul Gier updated JBBUILD-157: ------------------------------ Fix Version/s: JBossBuild - Maint 2008 (was: JBossBuild - Maint 2007) > Libs not deleted when updating from repository > ---------------------------------------------- > > Key: JBBUILD-157 > URL: http://jira.jboss.com/jira/browse/JBBUILD-157 > Project: JBoss Build System > Issue Type: Sub-task > Components: Repository > Affects Versions: Repsository Build Branch_4_0 > Reporter: Adrian Brock > Fix For: JBossBuild - Maint 2008 > > > The synchronize does not clear the thirdparty component when updating to a new version. > This leads to old jars being left lying around: > adrian@dev22:~/jboss-4.0/workspace/thirdparty/apache-tomcat/lib> ls -l > total 2817 > -rw-r--r-- 1 adrian adrian 664241 2005-09-26 02:03 catalina.jar > -rw-r--r-- 1 adrian adrian 45746 2005-09-26 02:03 catalina-manager.jar > -rw-r--r-- 1 adrian adrian 115234 2005-09-26 02:03 catalina-optional.jar > -rw-r--r-- 1 adrian adrian 109670 2005-07-06 12:33 commons-modeler.jar  > -rw-r--r-- 1 adrian adrian 383690 2005-09-26 02:03 jasper-compiler.jar > -rw-r--r-- 1 adrian adrian 918743 2005-09-26 02:03 jasper-compiler-jdt.jar > -rw-r--r-- 1 adrian adrian 76664 2005-09-26 02:03 jasper-runtime.jar > -rw-r--r-- 1 adrian adrian 46606 2005-09-26 02:03 naming-resources.jar > -rw-r--r-- 1 adrian adrian 18062 2005-09-26 02:03 servlets-default.jar > -rw-r--r-- 1 adrian adrian 6008 2005-09-26 02:03 servlets-invoker.jar > -rw-r--r-- 1 adrian adrian 22060 2005-09-26 02:03 servlets-webdav.jar > -rw-r--r-- 1 adrian adrian 123399 2005-09-26 02:03 tomcat-ajp.jar > -rw-r--r-- 1 adrian adrian 19247 2005-09-26 02:03 tomcat-coyote.jar > -rw-r--r-- 1 adrian adrian 51679 2005-09-26 02:03 tomcat-http.jar > -rw-r--r-- 1 adrian adrian 245885 2005-09-26 02:03 tomcat-util.jar > Should be: > http://repository.jboss.com/apache-tomcat/5.5.9jboss/lib/ > Modeler is here: > http://repository.jboss.com/apache-modeler/1.1patch/lib/ -- 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 - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (JBAS-5107) jboss-aop-jdk50-client.jar missing classes

by Dimitris Andreadis (JIRA)

jboss-aop-jdk50-client.jar missing classes ------------------------------------------ Key: JBAS-5107 URL: http://jira.jboss.com/jira/browse/JBAS-5107 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: AOP Affects Versions: JBossAS-5.0.0.Beta3 Reporter: Dimitris Andreadis Assigned To: Kabir Khan Fix For: JBossAS-5.0.0.Beta4 >From the forum post: Set up a remote stateless bean and a remote client. When the client was calling the bean i got the following | Exception in thread "main" java.lang.NoClassDefFoundError: org/jboss/aop/joinpoint/MethodExecution | at java.lang.Class.getDeclaredConstructors0(Native Method) | at java.lang.Class.privateGetDeclaredConstructors(Class.java:2357) | at java.lang.Class.getConstructor0(Class.java:2671) | at java.lang.Class.getDeclaredConstructor(Class.java:1953) | at java.io.ObjectStreamClass.getExternalizableConstructor(ObjectStreamClass.java:1269) | at java.io.ObjectStreamClass.access$1400(ObjectStreamClass.java:52) | at java.io.ObjectStreamClass$2.run(ObjectStreamClass.java:418) | at java.security.AccessController.doPrivileged(Native Method) | at java.io.ObjectStreamClass.<init>(ObjectStreamClass.java:400) | at java.io.ObjectStreamClass.lookup(ObjectStreamClass.java:297) | at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1035) | at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1375) | at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1347) | at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1290) | at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1079) | at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:302) | at org.jboss.remoting.serialization.impl.java.JavaSerializationManager.sendObjectVersion2_2(JavaSerializationManager.java:120) | at org.jboss.remoting.serialization.impl.java.JavaSerializationManager.sendObject(JavaSerializationManager.java:95) | at org.jboss.remoting.marshal.serializable.SerializableMarshaller.write(SerializableMarshaller.java:120) | at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.versionedWrite(MicroSocketClientInvoker.java:943) | at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(MicroSocketClientInvoker.java:586) | at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:122) | at org.jboss.remoting.Client.invoke(Client.java:1634) | at org.jboss.remoting.Client.invoke(Client.java:548) | at org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterceptor.java:62) | at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) | at org.jboss.aspects.tx.ClientTxPropagationInterceptor.invoke(ClientTxPropagationInterceptor.java:61) | at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) | at org.jboss.aspects.security.SecurityClientInterceptor.invoke(SecurityClientInterceptor.java:65) | at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) | at org.jboss.ejb3.remoting.IsLocalInterceptor.invoke(IsLocalInterceptor.java:74) | at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:101) | at org.jboss.ejb3.stateless.StatelessRemoteProxy.invoke(StatelessRemoteProxy.java:108) | at $Proxy1.getQuote(Unknown Source) | | | In the client package under $JBOSS_HOME/client i would expect all the right jars to be there for my remote client but it would seem that the jboss-aop-jdk50-client.jar is not packaged correctly i.e it is missing the "MethodExecution" class and what ever dependencies that has also. To carry on i just added the jboss-aop-jdk50.jar located under $JBOSS_HOME/lib to my classpath and was able to make a remote call. I assume that the $JBOSS_HOME/client dir should have everything needed for me to make a remote call for my remote client but looks like it doesnt -- 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 - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 3 months

2
1
0 / 0

[JBoss JIRA] Created: (JBAOP-506) jboss-aop-jdk50-client.jar missing classes

by Kabir Khan (JIRA)

jboss-aop-jdk50-client.jar missing classes ------------------------------------------ Key: JBAOP-506 URL: http://jira.jboss.com/jira/browse/JBAOP-506 Project: JBoss AOP Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Kabir Khan Assigned To: Kabir Khan Fix For: 2.1.0.GA -- 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 - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 3 months

1
2
0 / 0

[JBoss JIRA] Deleted: (JBAS-4653) Upgrade Hibernate Entity Manager to 3.3.2 (from 3.3.1)

by Dimitris Andreadis (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-4653?page=all ] Dimitris Andreadis deleted JBAS-4653: ------------------------------------- > Upgrade Hibernate Entity Manager to 3.3.2 (from 3.3.1) > ------------------------------------------------------ > > Key: JBAS-4653 > URL: http://jira.jboss.com/jira/browse/JBAS-4653 > Project: JBoss Application Server > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Reporter: Dimitris Andreadis > -- 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 - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 3 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira January 2008