| View previous topic :: View next topic |
| Author |
Message |
der_bonner
Joined: 16 Dec 2004 Posts: 27
|
Posted: Tue Dec 28, 2004 5:08 pm Post subject: build path and other pains |
|
|
Hi team,
getting on and on with testing I'm facing some probs (as already expected by you guys).
After playing around a little with the code I now tried to debug Compiere completely with Eclipse. I imported the code and the first thing I face was a build path. Eclipse tells me that the source folders "/server/src" and "serverRoot/src/main/client" are missing a building wiould not be possible
I used the Eclipse files from red1.....
Second thing is that Eclispe doen't allow me to change the code as all codes are displayed in Eclipse "read only".
For sure... something very easy to solve - but I've just no idea....
And if it's working then... some more questions will follow
(just for example: how do I create a process sending special information at a certain event to a certain person ) |
|
| Back to top |
|
 |
lofx Regular
Joined: 24 Sep 2004 Posts: 86
|
Posted: Tue Dec 28, 2004 6:03 pm Post subject: |
|
|
Hi!!
as you are using red1 files, he will know the answer better....................
but i can give you a hint as regards your example question. this is solved via alerts, where you can send an e-mail to a user when certain conditions are met. you just have to create a SQL script in the own compiere telling the program the exact conditions.................
regards, |
|
| Back to top |
|
 |
red1 Site Admin
Joined: 06 Jul 2004 Posts: 1756 Location: Kuala Lumpur, Malaysia
|
Posted: Tue Dec 28, 2004 10:21 pm Post subject: |
|
|
Hi der,
U have to 'force' your way through to rid of the errors. My eclipsefiles are just pointing to relative folders paths, so u have to check your local paths in your PC setup.
It sometimes takes time to figure out whats missing. Maybe by creating the dummy folders that do not exist. Maybe u can give some screenshots of your Eclipse (just crop to the left panel that shows the package layout.
Whatever it is, u aren;t far off.
red1 |
|
| Back to top |
|
 |
red1 Site Admin
Joined: 06 Jul 2004 Posts: 1756 Location: Kuala Lumpur, Malaysia
|
Posted: Wed Dec 29, 2004 1:35 am Post subject: |
|
|
Hi bonner,
From what u sent me. it seems that on the left side of the Eclipse screen, u did not select the proper package view, so i cannot see if the source packages are arranged automatically. U are showing only the Navigator view.
U can also right click the project and go to Properties > Build Path, and see the error or warining messages besides each jar. Then u restore them to the right paths.
red1 |
|
| Back to top |
|
 |
der_bonner
Joined: 16 Dec 2004 Posts: 27
|
Posted: Wed Dec 29, 2004 2:43 am Post subject: found the problem... |
|
|
Hey red,
good hint (even if do not understand what happened) but I had a look at the build path, saw the errors and clicked ok.... and suddenly all problems were gone
really nice.....
But still the situation is that the changes I make in files for the "welcome page" or other web stuff has no affect on the running system. Do have to make changes and then debug Compiere or am I just changing the wrong files?
Cheers, |
|
| Back to top |
|
 |
red1 Site Admin
Joined: 06 Jul 2004 Posts: 1756 Location: Kuala Lumpur, Malaysia
|
Posted: Wed Jan 05, 2005 8:02 am Post subject: |
|
|
Hi Bonner,
Ok, now i have time to rethink your problem.
Ah! yes, u cannot debug your codes using normal Eclipse debug, but u must use Remote Debug as shown here at http://compiere.red1.org/RemoteDebug.zip .
Using remote debug means u need not compile yet and get to test your changes first in Eclipse
Whenever you change web and accounting areas the effect will not happen in the Eclipse normal run mode.
This is because the Jars for these components have to be compiled first and given to JBoss to run, as (u guessed it) these components doesnt run in the local JVM but Jboss - which is the application service to handle multiple transactions, clients and over the http.
And this Jboss is separate service and the Jars must be place in them before they are to run (without remote debug, or deployed).
red1 |
|
| Back to top |
|
 |
der_bonner
Joined: 16 Dec 2004 Posts: 27
|
Posted: Thu Jan 06, 2005 4:21 pm Post subject: totally confused |
|
|
Hi red,
now I'm totally confused. Well - not totally as I understood that I will have to do my changings in Eclipse and THEN debug Compiere again in order to make my changings work, is that right?
But now I'm totally confused with the way to go (maybe I do not understand the naming of things I have to do as I'm not a programmer).
On my machine I have a folder /Compiere2 where I run setup to get the properties file (then imported the database) und got it run with RUN_Server2.
OK - so as I got it this is the "user" way... and I shut it down again.
Then I have a folder /Compiere-all2 that I imported to Eclipse. I did the jboss modification in /Compiere2 for remote debug and get it working in Eclipse.... cool
But now... what do I have to do to get a package like the zip files from Compiere.org including what I have changed. And, please excuse - what does "build" really mean?
How can I manage to make all my necessary modification on a test machine and "update" the production (and how do I get the database modification from my test installation to the working system)
Well... I know that this is quite a lot of questions and I really tried to figure it out on my own... but I'm a little bit stuck in my small world
And even though I know that you should never change the code until you really know what you are doing... I would like to learn! ! !
cheers |
|
| Back to top |
|
 |
red1 Site Admin
Joined: 06 Jul 2004 Posts: 1756 Location: Kuala Lumpur, Malaysia
|
Posted: Thu Jan 06, 2005 6:56 pm Post subject: |
|
|
Hi Bonner,
It took me months to understand anyway, so u have to be patient.
Build is when u want to compile and produce the zip files such as Compiere2.
That zip file is the binary version of your program that u use to deploy your application. When u ask someone, "Hey! Here's my modified version of Compiere!" U pass to him those zip files that has Compiere2.
U do this when u finally finished your programming work and so u zip them up thru a build process.
About messing around with the codes, u must do that alot!. Don;t get me wrong. What i meant about not messing is with the production or live system which has real data that cannot be corrupted. So if u are just learning then that is different as u will be using a test system. Go crazy and throw all the paint at the canvas! The more mistakes u make the more faster u learn.
PEACE!
red1 |
|
| Back to top |
|
 |
|