can you pleas give an workaround of nukes on Jboss ide?
I am new to nukes and jboss ide (eclipse) and would apreciate any help.
the .project file is created by eclipse when you import the sources. the .classpath file gets created when you start adding libraries to the project.
for every nukes module except common and core, you only need to worry about importing the nukes-lib.jar file.
for the common and core, you have to add pretty much every library that is contained in the thirdparty directory.
<?xml version="1.0" encoding="UTF-8"?> <classpath> <classpathentry kind="src" path="src/main"/> <classpathentry kind="src" path="output/gen/classes"/> <classpathentry kind="con" path="org.eclipse.jdt.launching.JRE_CONTAINER"/> <classpathentry kind="var" path="JBOSS_HOME/client/jbossall-client.jar"/> <classpathentry kind="var" path="JBOSS_HOME/lib/jboss-jmx.jar"/> <classpathentry kind="var" path="JBOSS_HOME/server/default/lib/javax.servlet.jar"/> <classpathentry kind="var" path="JBOSS_HOME/server/default/lib/log4j.jar"/> <classpathentry kind="var" path="JBOSS_HOME/lib/jdom.jar"/> <classpathentry kind="var" path="JBOSS_HOME/lib/jboss-system.jar"/> <classpathentry kind="var" path="JBOSS_NUKES/thirdparty/javassist/lib/javassist.jar"/> <classpathentry kind="var" path="JBOSS_NUKES/thirdparty/dom4j-dom4j/lib/dom4j.jar"/> <classpathentry kind="output" path="bin"/> </classpath>
.classpath file for nukes/common
hrm - there is still a problem posting xml - i gotta look into fixing that this weekend.
i need to run out right now, but when i get back, i'll post a link w/ a zip so you can d/l my .classpath files for nukes/common and nukes/core.
if you can't wait, you can view the page source and see what libraries i added to the classpath.
here you go
it contains classpath files for common, nukes, and bb
you will have to create teh following classpath variables inside eclipse for these to work properly:
JBOSS_HOME: points to the directory where jboss lives, ie: C:/jboss
NUKES_HOME: points to the directory where the nukes cvs checkout
lives, ie: C:\development\nukes
I am working on fixing XML, please wait a little bit
Thanks for your help. With the given .classpath files it works. Eclipse compiles with many warnings and one error in resource Persmission.java saying:
"Error The method initialize is defined in an inherited type and an enclosing scope Permission.java nukes/src/main/org/jboss/nukes/security line 148"
is this an configuration problem? Compiling with build.sh under /nukes/build/ works fine.
what version of eclipse are you running? did you change any options under "preferences -> java -> compiler"?
You need to use a JDK 1.4.X compiler.
My eclipse version is: 2.1.3 Build 200402041431 .
My installed java version was is 1.4.2 but eclipse use 1.3.
I have been changing this to 1.4 and it compiles well.
Thank you very much.
I am happy now.
Will try to make an module.
The reasen I am experiencing Nukes is that I have to make an portal engine. Knowing that nukes and jboss developers are experienced I like to learn how you designed Nukes. I been reading somthing about creating an portlet engine within nukes. That sounds great. Hope I can contribute also developing an open source portal engine running on jboss.
Thank alot for your help.
I also am having some problems creating a good project in Eclipse. Can someone who has a project created please give me the directory structure? I use the cvs plugin in Eclipse and get everything from cvs to folder c:\nukes. Is there one project for each module or one for the whole nukes cvs checkout? I've set up the classpath variables and I tried the classpath files provided here but still have problems getting everything to compile in Eclispe.
I created only the core and common.
Try first core and if it works so try more.
I created into my /eclipse/workspace the new Java Project. After I created an /src/main and an /output/gen/classes folder. Then import the to folders from /nukes/nukes/src/main and /nukes/nukes/output/gen/classes ( to get this compile first with the given build.xml <- this creates the folder) And at least add all external jars from /nukes/thirdparty/ .. and even more.
Thanks NIK. I got a project created and compiled for /nukes/common. I deleted the one that Eclipse CVS made and created one myself using the .classpath file example in this thread. After making sure my classpath varibales were correct, everything compiled. I did the same with /nukes/nukes but I have many errors with the nukes.core.ejb classes...no source for FileEJBLocal, FileEJBLocalHome etc. Not sure whats up yet. Did you create them or does the build do it somewhere?
I went through that myself recently and it actually works.
Basically you can find the eclipse file from a fresh CVS checkout, so do that first. Then from Eclipse tell him to import the project pointing to that file. It automatically pulls down all the files from the central repository (so it does a second checkout).
I got the stuff to compile after adding 2 missing classpath files. It compiles in Eclipse now. I really like the differential compiler feature.