[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
16 years, 11 months
[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 <!-- Should not be HERE -->
> -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
16 years, 11 months
[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
16 years, 11 months
[JBoss JIRA] Closed: (GPD-194) CLONE -JBDS - cannot generate a form for a task via (jBPM) GPD
by Koen Aers (JIRA)
[ http://jira.jboss.com/jira/browse/GPD-194?page=all ]
Koen Aers closed GPD-194.
-------------------------
Resolution: Done
> CLONE -JBDS - cannot generate a form for a task via (jBPM) GPD
> --------------------------------------------------------------
>
> Key: GPD-194
> URL: http://jira.jboss.com/jira/browse/GPD-194
> Project: JBoss jBPM GPD
> Issue Type: Bug
> Affects Versions: jBPM jPDL Designer 3.1.1
> Environment: JBoss Developer Studio, Build id: 200712091205-nightly
> and
> Eclipse Europa + jbpm-jpdl-designer-3.0.13 Stable 9.2 MB 2007-01-25
> Reporter: Koen Aers
> Assigned To: Koen Aers
> Fix For: jBPM jPDL Designer 3.2.0.alpha1, jBPM jPDL Designer 3.1.2
>
>
> I'm unable to generate a new form for a task with either the 1.0 JBDS bits or Eclipse Europa + jbpm-jpdl-designer-3.0.13 Stable 9.2 MB 2007-01-25
> To recreate the problem - using the attached jBPM process project - it's based on the 'holiday request' jBPM demo - at the start task node, attempt to generate a form.
> The screen displayed in the screenshot attachment is brought up - pressing OK has no effect. The form xhtml file is not created - and no error/sttaus message is displayed.
>
--
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
16 years, 11 months