I am just a newbie on Adempiere. I downloaded the Adempiere's project and run setup. After that, I've got this error and couldn't find the answer on google.
Does anyone have any idea about this error.
The error you have is due to custom code been defined in the ModelValidator window of ADempiere where the custom module is not compiled together into the binary. But as Colin Rooney asked for clarification, your error pop up box is specifying 'iDempiere' in some data. I can see it is ADempiere as the project logo is clearly ADempiere's and not to be the newer fork, iDempiere's. Also in your error-stack the log name is ADempiere.
Nevertheless the issue is the same for both. Just go to your database (most likely Postgres) go to the ModelValidator table and the FA module record, uncheck the IsActive field or delete the record.
To introduce the FA module you have to first compile it together with the whole ADempiere codebase before deploying.
iDempiere is different, as it does not lock modules in its meta data anymore. It is injected purely by OSGi plugin much like how Eclipse IDE works. I have a movie comparing both ways of deploying custom changes: http://youtu.be/Pm0DzUbVhes
I downloaded the Adempiere's project and run setup.
Did you download Adempiere or iDempiere? From the error it looks like iDemiere but that's not what you say. For support questions like this on Adempiere you'd be better asking for help in their forums or their gitter room
Stackoverflow is directed at developers and development/coding issues.
I can't seem to find a setting in Eclipse to save and back-up a single Project to multiple paths.
I have a single Java Project in Eclipse that I save on my local machine and either save as... or copy replace to a local network and local mass storage, for BACKUP. I'd like that to occur on any, all Project saves.
I saw Project properties, but I'm not too familiar with Eclipse and team dev options, and I don't want to F the paths, links, etc.
Thanks.
EDIT: I'll try what user101 recommended, but to avoid confusion, My own personal, primary Linux box is where development is performed. The other locations are, for lack of a better word, BACKUPS. I used the term "Sync" for the sake of what my question may be related to.
Sorry for any confusion.
What I understood is that you want the sources from different paths , if so You can try as below
1> Create new java project
2> Click on link additional source
I'm using Eclipse in server and I have two users who can connect on this server. I want to find a solution which allows me to use the same workspace by they two users. I tried it and I got an error message which tells me that you can't use this workspace because it is used by another user and it makes sense. But I want to know if they have a solution which allows me to open the same workspace in the same time by the differents users who use the different authority.
Thank you
you cannot do that as it locks the workspace for one user. others cant edit the same. Try using Version Control like Git or SVN.
You can make developers use the same Eclipse by starting it's launcher with the "-data" argument set to a unique folder. (Let's say the user's name)
You can write a startup-script that copies the contents of a reference workspace, each time a user starts using this shared Eclipse.
But that's the most you can achieve; two instances of Eclipse can not use the same workspace. In server terms: think of it as a Session rather than a Workspace.
I'm adding JPA diagram from database in NetBeans. After I click "finish" this error message will pop up:
Could not determine nor create a location for the configuration files.
And it's happened in a gcm demo project I download, however, using a new project will be ok. I cannot find out the different between them.
Anyone experienced a similar situation or know the meaning of this message?
I use Eclipse to write Java code and use DropBox to sync my code with others' across our multiple computers. Most of the time, everything works as expected: if anyone makes a change on either end, the change is saved and when the other person refreshes the Eclipse workspace, the changes come through and can be viewed and run successfully.
Sometimes, one of several errors arises. Sometimes Eclipse says it cannot find a main class and sometimes it says it could not find the class itself. Sometimes it will not report an error but for some reason will not actually update the .class file and therefore run an old version even though the compiler displays the new source code and that saves. I've then noticed that if I manually copy the code into a new .java file elsewhere in the file system and then compile it, it works fine, but for some reason it refuses to regenerate the .class file and I have to delete it manually and replace it with the one generated in the other project--then it works. But for solving the other problems everything needs to be manually copied, deleted, and re-pasted....
[The actual errors include NoClassDefFoundError, UnsupportedClassVersionError, and some other error related to not having a main class.]
I realize that the description here is somewhat vague, but unfortunately I'm not entirely sure what's going on. I hope I'm just missing some basic fact that would help solve all these problems.
Thanks!
I'm sure you will see issues using Dropbox for sharing your source.
Eclipse does not know what Dropbox is doing whilst it's uploading and downloading updates and their activities will certainly not be synchronised. At arbitrary points in time when Eclipse tries to do builds etc. it will find unexpected activity going on, maybe even partially downloaded source files which might explain the specific errors you are seeing.
You're trying to do something more complex than sharing photos or documents. The advice I would give is to use a source control system like git or subversion for source code sharing and control. You can then make use of plugins for Eclipse that are designed to integrate these systems in an easy to use way. There's a learning curve there, but the skills will serve you well.
You can use online versions of these solutions like github and unfuddle if you want to consume sharing, backup and version control of source as a service like you do with Dropbox. They're free, too.
Subversion, Git and all version control software solve all of these problems for you.
Dropbox is not really an adapted system for sharing code. What you should do is set up a SVN, and commit only the source files. This way, you won't have these kind of errors.
Dropbox does have versioning (you can restore old versions of a file), and doesn't seem to be a horrible solution for the problem. I keep my Eclipse repository on Dropbox so it is available on any computer; but since I only use it myself, I haven't encountered your problems.
There is one case I can absolutely see you running into problems--it's if your class files are stored in the dropbox as well. This would just screw everything up. Make sure you specify a location on your local hard-drive for all build artifacts (classes, jars, ...) and that the only thing on your dropbox is the .java sources.
In fact, I suggest you don't keep your eclipse project in your dropbox, just create your eclipse project and point it to the java files in your dropbox.
If this doesn't work for you, go with what other people here said and set up a SVN repository somewhere, it's easier than you would think.
Oh, another possible problem--dates! You may want to make sure the date on your java files isn't jumping forwards and backwards (as might happen if one of your developers were in another time zone). In this case, Eclipse may prefer not to re-compile your file.
Also, instead of the copy/etc procedure you are currently going through, try forcing a project clean.
Response to request for more info:
When you start Eclipse, select/create a workspace that is NOT on your dropbox. The best place is probably off your home directory. If you have already specified a default workspace, there should be a switch workspace item in the file menu.
Create your project. select "Create project from existing source" and specify the source files in your dropbox. I think you want "create separate folders for source and class files" to keep your class files out of your dropbox. If you see anything saying "Copy files into your workspace, say "no".
This should give you a valid, working project. I hope you don't see those problems any more.
One more thing may help--and this may work on your existing project--without the above procedure...
Whenever you refresh your files (f5) to load in changes from the dropbox, select the Project/clean menu and select the project. This should delete all the class files and rebuild them.
If your classfiles are shared on the dropbox, this could still have strange consequences on other people with eclipse open, so I really do suggest rebuilding your workspace as I said above.
How to avoid no main class
Provide one. That issue has nothing to do with DropBox