Hi,

Let's first answer your two last questions:

1. You don't need the source code to start the server: source code is for building the server.
2. Yes, they do but this is only useful for contributors (ie advanced Nuxeo core developers). Nuxeo is designed in order to never require to change the source code, only to extend or overwrite it.

Here are a few answers to your questions or remarks:

• First of all, you can see the documentation is huge and requires a continuous maintenance. Remarks and contributions are welcome.
• Solving your SQL error has to do with server administration, logs analysis, asking questions like you did on why-do-i-get-an-error-occured-when-creating-a-workspace… building the source code won't help.
• Of course, « compiling from source is really viable » since we do it everyday and have and advanced continuous integration building the source code too.
• The README (have been renamed from .txt to .md), I've updated the doc, thank you.
• About Ant, the end of the sentence you pointed is « we don't cover all possibilities and Ant targets may be out of date ». We recommend to use Maven. Ant scripts are kept for their aficionados and maintained by contribution only.
• I'm sorry you fall into so much headaches but the CORG part of the documentation is effectively focused on Linux and addressed to advanced (Nuxeo) developers. All your other remarks are out of purpose too. I could answer and explain in details to each one but there would be no point at doing it, it wouldn't help you.
• Starting the server in Eclipse (Nuxeo IDE) is done with “Nuxeo > Run/Debug” as explained in IDEDOC/Running your Projects on the Server.

Regards,

Hi Utopian,

First, I am glad you get interest on Nuxeo product and community and hope you will find what you need here. I also hope you'll get the habit of asking only one question per post, that's the way this “answers” tool should be used. I think it is interesting to mention here that for most (if not 100%) of any customization use case (whether from IDE or Studio) you don't need to compile Nuxeo sources. Nuxeo is fully extensible and customization is made in external bundles (the “plugins”). That's probably why the “checkout Nuxeo sources” path is not fully optimized.

Of course, checking out the sources is a recommended path if you want to accelerate your learning curve of the framework, since you will find in there many interesting examples (as your customization is made the same way the built-in bundles are made). But even then, you don't need to build the product, you just get them locally to be able to browse the sources comfortably.

The main case where you really want to build from the sources is if you want to test then contribute some bug-fixes via pull requests and we will be glad if you can do so !

I can only speak for myself but I have compiled (successfully) the source code; although I haven't done a full build in a while. So it is possible. When I need to change a core component (if you use DAM in any serious way with big objects, multiple formats and colorspaces then you will find it unavoidable) I do not recompile the entire platform. In this case I…

• get the latest updated source using python (agreed this is a little odd),
• import the project of interest into Eclipse,
• use git (command line) to switch to the release or hotfix of interest,
• make the changes in Eclipse,
• make a local commit,
• use maven (command line) to recompile the affected project(s), and
• then deploy the updated JAR to the server.

Because there are so many different technologies and moving parts compiling from source is challenging - especially for those new to Nuxeo. It would be extremely useful if there were recorded webinars for activities like building a server from scratch.