Jérôme Renard wrote: > Hi Gaetano, > Hi JR, thanks for the quick reply.
It would be great to have this mail as a blog post/article on share.ez.no! > Le 16/02/10 16:30, Gaetano Giunta a écrit : >> I think we have a build process for extensions that are hosted on >> projects.ez.no based on ant files. >> >> Is there any document/information available on how to set those up / >> how the build process works? > > I do not know if there are automatic builds for extension hosted on > projects.ez.no howere here are the > informations I can give : > > 1. we use eZExtensionBuilder = http://projects.ez.no/ezextensionbuilder/ > 2. doc is available here : > http://svn.projects.ez.no/ezextensionbuilder/trunk/README > I just read the instructions, and there are a couple of questions I have that are not answered in there: - I have a trunk and many branches. Shall the ant files be put in /trunk/ant and /branches/2.0/ant or in /trunk/extension/ezoracle/ant and /branches/2.0/extension/ezoracle/ant - how about a max and min supported versions for ezp? In the example below you specify a single ezp version, but my branch 2.0 is compatible with ezp 4.0 to 4.2 (and other branches have different compatibilities) - what is the usage of the create.tarball setting? - can you give more details about management of packages? ciao Gaetano > Attached a screenshot that shows the extensions we build with hudson and > ezextension builder. mmm.... no ezoracle in there... ;) > Below, an Ant configuration file for eZFlow which (AFAIR) is the biggest > certified extension we build : > > <!-- version properties --> > ezflow.version.major = 2 > ezflow.version.minor = 1 > ezflow.version.release = 0alpha1 > > ezflow.create.tarball=no > > <!-- ezpublish properties --> > ezp.version.major = 4 > ezp.version.minor = 3 > ezp.version.release = 0alpha1 > > <!-- Subversion properties --> > ezflow.svn.url = http://svn.ez.no/svn/extensions/ezflow/trunk > > ezflow.package.ezflow_extension = ezflow_extension > ezflow.package.ezflow_classes = ezflow_classes > ezflow.package.ezflow_democontent = ezflow_democontent > ezflow.package.ezflow_democontent_clean = ezflow_democontent_clean > ezflow.package.ezflow_design = ezflow_design > ezflow.package.ezflow_site = ezflow_site > ezflow.package.ezflow_site_clean = ezflow_site_clean > > <!-- external dependancy properties --> > ezflow.external.dependency.ezwebin.repository = > http://svn.ez.no/svn/extensions/ezwebin/trunk > > Here is how to build it on your own : > > 1. cd path/to/ezflow/trunk > 2. ant clean-all -Dextension.name=ezflow && ant all -Dextension.name=ezflow > > And then 10 minutes later, eZFlow will be built with all its > dependencies and eZPackages. > > Attached the configuration we use in Hudson to get this build > automatically. > -- Sdk-public mailing list [email protected] http://lists.ez.no/mailman/listinfo/sdk-public
