Dave,
While I seem to have gotten a clean build, I started running into problems with RMI. I think I neglected to include the virtual-tomcat stuff and I was recently told (on these forums) how to include this in my build.
FYI: I am using eclipse for the build (and ant). I followed the build procedure that told us to install ant, DL the code from svn, then perform the build (using eclipse and ant). The steps that were not very clear were the ones that mentioned having the virtual-tomcat. For those of us bouncing back and forth between Linux installs and Windows installs there seem to be some subtle differences regarding what is included in the install. Also, I found that when I was trying to perform my first build, the svn was in such a state of flux that I grabbed a version that was not yet stable (due to incroporation of the WCM code). Further, there seem to be two approaches - one using the sdk, the other using the svn. A bit confusing. I also saw some note that you need some items from the alfresco sdk. I can't remember what these are or if in its current state this step is still needed.
What I did notice after the build was that I had a new batch of files that I could apparently move into my directory structure on my Linux box. That was going to be my next step - move the files from my Windows box build into a similart (test) directory structure on my Linux server.
I have not gotten that far - yet. However, I surmise that you should be able to perform the process I mention above and possibly end up with a working install. I am nearing another window of opportunity where I will give it another crack. I will update you.
As far as documentation for doing this, I have found it to be rather thin. This does make it difficult for us newbies, but look on the bright side, it's an opportunity to learn a new skill!
Please update me if you make progress on this. We (the collective we) need to be able to build alfresco on our own if we wish to use it in a stable environment. For example, the recent stable 1.4 is not fully functional regarding WebDav, but the SVN DOES include the fix for it. If we can perform a clean build and replace on our production servers, then we can derive the benfit of this svn fix. Otherwise, we will have to wait till the next release.
Regards,
-Matt
While I seem to have gotten a clean build, I started running into problems with RMI. I think I neglected to include the virtual-tomcat stuff and I was recently told (on these forums) how to include this in my build.
FYI: I am using eclipse for the build (and ant). I followed the build procedure that told us to install ant, DL the code from svn, then perform the build (using eclipse and ant). The steps that were not very clear were the ones that mentioned having the virtual-tomcat. For those of us bouncing back and forth between Linux installs and Windows installs there seem to be some subtle differences regarding what is included in the install. Also, I found that when I was trying to perform my first build, the svn was in such a state of flux that I grabbed a version that was not yet stable (due to incroporation of the WCM code). Further, there seem to be two approaches - one using the sdk, the other using the svn. A bit confusing. I also saw some note that you need some items from the alfresco sdk. I can't remember what these are or if in its current state this step is still needed.
What I did notice after the build was that I had a new batch of files that I could apparently move into my directory structure on my Linux box. That was going to be my next step - move the files from my Windows box build into a similart (test) directory structure on my Linux server.
I have not gotten that far - yet. However, I surmise that you should be able to perform the process I mention above and possibly end up with a working install. I am nearing another window of opportunity where I will give it another crack. I will update you.
As far as documentation for doing this, I have found it to be rather thin. This does make it difficult for us newbies, but look on the bright side, it's an opportunity to learn a new skill!
Please update me if you make progress on this. We (the collective we) need to be able to build alfresco on our own if we wish to use it in a stable environment. For example, the recent stable 1.4 is not fully functional regarding WebDav, but the SVN DOES include the fix for it. If we can perform a clean build and replace on our production servers, then we can derive the benfit of this svn fix. Otherwise, we will have to wait till the next release.
Regards,
-Matt
