topic Re: Development Environment without modify Alfresco src in Alfresco Archive

Development Environment without modify Alfresco src

relax — Mon, 08 Mar 2010 11:18:07 GMT

Hello,I'm changing some core alfresco features, for example on group administration.Is there an external development environment to change alfresco src without modify Alfresco src projects as Core, Remote API, Web-Client…?In http://wiki.alfresco.com/wiki/Developer_Guide there isAlfresco SVN - Direct

Re: Development Environment without modify Alfresco src

billerby — Mon, 08 Mar 2010 12:50:20 GMT

Well, since you not have write access to the Alfresco core you won't be changing in svn. Here is what I did to do some home written paches to 3.2.r2:

1. First I checked out the Rev 17458 of Alfresco which is the revision number for 3.2r2.

2. Changed the appropriate java-classes, jsp-pages etc. Wrote a very detailed instruction of what I did and why. (You could even create svn patch files) (Anyone should be able to do these patches again upon a new Alfresco release)

3. Rebuilt Alfresco with the ANT scripts.

4. Renamed the resulting files to alfresco-3.2.r2-[exension]-patched.jar

5. Since I use maven for my Alfresco development lifecycle (http://wiki.alfresco.com/wiki/Managing_Alfresco_Lifecyle_with_Maven) I installed my patches in my local maven repository, and changed the dependency version in my pom.xml.

Regards
/Erik

Re: Development Environment without modify Alfresco src

relax — Mon, 08 Mar 2010 14:53:08 GMT

Hello,
sorry, but I was not very clear. I wish I had a project with the only classes or web content changed respect Alfresco source project.

Re: Development Environment without modify Alfresco src

billerby — Mon, 08 Mar 2010 15:12:52 GMT

I would have developed an Alfresco Module Package (AMP) http://wiki.alfresco.com/wiki/AMP_Files

The easiest way to get started in my opinion is to go with the maven-alfresco-lifecycle approach as I referred to in my last post:

http://wiki.alfresco.com/wiki/Managing_Alfresco_Lifecyle_with_Maven

Create two archetypes, one extension project and one amp project.

In the pom.xml of the extension project you set a dependency to the amp project.

Happy coding

/Erik