-----Original Message----- From: jboss-development-bounces(a)lists.jboss.org [mailto:jboss-development-bounces@lists.jboss.org] On Behalf Of Scott M Stark Sent: 26 October 2006 19:17 To: JBoss.org development list Subject: Re: [jboss-dev] jbossas/aspects not building for me Even if I set the source target to 1.5, there is a problem with the org.jboss.aop.Domain class in the jboss-aop-jdk50.jar coming from the 2.0.0.alpha1 version not having the required ctor: [javac] Compiling 201 source files to /home/svn/JBossHead/jboss-head/aspects/output/classes [javac] /home/svn/JBossHead/jboss-head/aspects/src/main/org/jboss/aop/ deployment/ScopedClassLoaderDomain.java:51: cannot find symbol [javac] symbol : constructor Domain(org.jboss.aop.AspectManager,java.lang.String,boolean) [javac] location: class org.jboss.aop.Domain [javac] super(manager, name, parentFirst); [starksm@succubus lib]$ javap -classpath jboss-aop-jdk50.jar org.jboss.aop.Domain Compiled from "Domain.java" public class org.jboss.aop.Domain extends org.jboss.aop.AspectManager{ protected org.jboss.aop.AspectManager parent; protected boolean parentFirst; protected boolean inheritsDeclarations; protected boolean inheritsBindings; public org.jboss.aop.Domain(org.jboss.aop.AspectManager, boolean); public void setInheritsDeclarations(boolean); I have to use the current snapshot version to get this to compile. Scott M Stark wrote: > It looks like the aspects module requires a 1.5 source compile target > now. Is the command line build out of sync with the eclipse project? > > > _______________________________________________ > jboss-development mailing list > jboss-development(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jboss-development _______________________________________________ jboss-development mailing list jboss-development(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-development

It was not, but it looks like it was a merge problem. After I cleaned up everything and got a good merge its building. Kabir Khan wrote: > Isn't build-thirdparty.xml set up to use the aop snapshot? > _______________________________________________ jboss-development mailing list jboss-development(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-development

If I did it was unintentional - I normally create thirdparty as a java project. What is the proper thing to create it as? > -----Original Message----- > From: jboss-development-bounces(a)lists.jboss.org > [mailto:jboss-development-bounces@lists.jboss.org] On Behalf > Of Scott M Stark > Sent: 26 October 2006 20:03 > To: JBoss.org development list > Subject: Re: [jboss-dev] jbossas/aspects not building for me > > However, after the restoration I'm having a problem with the > eclipse thirdparty project being a java project as it has no > .classpath. I removed this earlier, and reverted thirdparty > to a simple project, but you put it back to a java project. > Why, for source attachments? We need to get this thirdparty > source problem figured out. > > Scott M Stark wrote: > >> It was not, but it looks like it was a merge problem. After >> > I cleaned > >> up everything and got a good merge its building. >> >> Kabir Khan wrote: >> >>> Isn't build-thirdparty.xml set up to use the aop snapshot? >>> >>>