Checkout specific revision of svn repo

[csiege]

How can I checkout a specific "tagged" revision of the codebase?

Specifically, I want to be able to get the svn code base for the official 1.3 release to I can build in some changes/fixes I need.

(fyi - the changes I am wanting to build are those provided in a forum post to create user home spaces upon LDAP sync… 🙂 )

thanks.

Chris

[gavinc]

Your best bet is to download the 1.3 SDK from sourceforge as that contains all the source and the Eclipse projects to build it.

[csiege]

Was wondering if that was the case…  setting it up now.  Thanks!

[csiege]

ok, another question here…

I have read the statement on the wiki…

"The SDK is not designed for re-building Alfresco i.e. it does not provide full build scripts and artifacts, therefore if you wish to develop bug fixes or extend the core functionality of the Alfresco platform, you should use the full Alfresco development environment provided in the Alfresco SVN Repository. "

I want to extend core functionality, but I want to use the 1.3 code base to extend from, not code that may be post 1.3.  I am not seeing the eclipse project necessary to rebuild, for instance, the repository.jar in the sdk.

[gavinc]

Apologies, my mistake.

As the wiki says, The SDK is for building extensions upon Alfresco not for re-building it.

To re-build our JARs the easiest thing to do is to get the code from SVN where you'll find all the build scripts. You could probably work out the revision number to check out from the SVN log command and the date we released.

Alternatively, I believe the SDK contains the source in zip files, so you could extract the source zips and get the build scripts from SVN (they don't change very often) and create your environment that way.

[csiege]

This is somewhat painful…

Is there no way to just checkout the codebase label for 1.3 from SVN?

[csiege]

Using the code from the sdk and the build scripts from svn, I was able to get this working…  but it was painful…

For 1.4 could the sdk be delivered in a way that the build scripts are included and everything already structured out (the directories that is)?

thanks for the help!

Chris

[davidc]

The issue here is that the public community SVN is not tagged for specific releases.  If it were you'd be able to checkout and re-build any part of Alfresco.  The SDK isn't tailored for re-building our core; it could be in the future but it's been deliberately kept simple.

The enterprise svn (restricted access) is tagged.

We should fix the tagging of the public svn.