Before upgrading, you first need to understand how to create a project which is based on eXo Platform 3.5. For more details, refer to the eXo Platform Developer Guide.

And now, you need to gather all requirements for your upgraded project by clarifying the following questions:

You need to create a new branch for eXo Platform 3.5 extension project, then clone your source code of eXo Platform 3.0 with that of eXo Platform 3.5.

The way to package your project customization called extensions has been introduced in eXo Platform 3.0. Therefore, by using the WAR extension configuration approach, you can overload eXo Platform's default files defined in WARs, such as gtmpl, favicon, xml, jsp. For more details on how to create your extension project, refer to the Create Your Own Portal section.

Because there are not any changes on the eXo Platform 3.5 extension mechanism, your extensions should be mostly compatible. However, if your extension was overriding either of the eXo Platform 3.0 built-in files, you should check that the file has not been changed in eXo Platform 3.5 and update it if any.

There are 4 main steps which need to be defined for updating eXo Platform extension from 3.0 to 3.5:

eXo Platform include many components, so if you want to update your eXo Platform extension to use eXo Platform 3.5, you need to update all dependencies version in the POM files, and select dependencies version which are compatible with the eXo Platform 3.5. For example, eXo Platform 3.5.1 needs to have the following main dependencies:

<!-- kernel -->

<dependency>

    <groupId>org.exoplatform.kernel</groupId>

    <artifactId>kernel-parent</artifactId>

    <version>2.3.5-GA</version>

</dependency>

<!-- core -->

<dependency>

   <groupId>org.exoplatform.core</groupId>

   <artifactId>core-parent</artifactId>

   <version>2.4.5-GA</version>

</dependency>

<!-- ws -->

<dependency>

   <groupId>org.exoplatform.ws</groupId>

   <artifactId>ws-parent</artifactId>

   <version>2.2.5-GA</version>

</dependency>



<!-- jcr -->

<dependency>

  <groupId>org.exoplatform.jcr</groupId>

  <artifactId>jcr-parent</artifactId>

  <version>1.14.5-GA</version>

</dependency>



<!-- jcr service -->

<dependency>

  <groupId>org.exoplatform</groupId>

  <artifactId>exo-jcr-services</artifactId>

  <version>1.14.5-GA</version>

</dependency>



<!-- commons -->

<dependency>

  <groupId>org.exoplatform.commons</groupId>

  <artifactId>exo.platform.commons</artifactId>

  <version>1.1.5</version>

</dependency>



<!-- exogtn -->

<dependency>

   <groupId>org.exoplatform.portal</groupId>

   <artifactId>exo.portal.parent</artifactId>

   <version>3.2.2-PLF</version>

</dependency>



<!-- webos -->

<dependency>

  <groupId>org.exoplatform.webos</groupId>

  <artifactId>webos-parent</artifactId>

  <version>2.0.2</version>

</dependency>



<!-- ecms -->

<dependency>

  <groupId>org.exoplatform.ecms</groupId>

  <artifactId>exo-ecms</artifactId>

  <version>2.3.5</version>

</dependency>



<!-- ide -->

<dependency>

   <groupId>org.exoplatform.ide</groupId>

   <artifactId>exo-ide-parent</artifactId>

   <version>1.1.4</version>

</dependency>



<!-- cs -->

<dependency>

  <groupId>org.exoplatform.cs</groupId>

  <artifactId>cs</artifactId>

  <version>2.2.7</version>

</dependency>



<!-- ks -->

<dependency>

  <groupId>org.exoplatform.ks</groupId>

  <artifactId>ks</artifactId>

  <version>2.2.7</version>

</dependency>



<!-- social -->

<dependency>

  <groupId>org.exoplatform.social</groupId>

  <artifactId>social-project</artifactId>

  <version>1.2.7</version>

</dependency>



<!-- integration -->

<dependency>

  <groupId>org.exoplatform.integration</groupId>

  <artifactId>integ</artifactId>

  <version>1.0.5</version>

</dependency>

After updating Maven dependencies, you need to update configurations via answering two questions:

After that, you can put them into $PLATFORM-TOMCAT-HOME/gatein/conf.

There are many components in eXo Platform, so if you update your eXo Platform extension to eXo Platform 3.5, you need to update the version of all eXo Platform 3.5's components. To do so, simply configure the Maven POM file that allows you to use the artifacts (eXo Platform 3.5 and its components). For more details, see the Update project Maven dependencies section. All eXo Platform 3.5's components will be automatically included in your eXo Platform extension.

There are some new components in eXo Platform 3.5 that have not been existing in eXo Platform 3.0, including Webos, Wiki, and Gadget-pack. To use these components, simply activate their profiles. For more details, see the Profiles of eXo Platform section.

In eXo Platform 3.5, the "intranet" portal is defined in the acme-intranet.war file (not in the office-portal.war file of eXo Platform 3.0). So if you have overridden anything in the "intranet" portal, you need to synchronize your extension with the acme-intranet.war file of eXo Platform-3.5.

This section details how to update your custom eXo Platform extension, including updating Kernel XML Schema, portal and APIs.

<configuration xmlns="http://www.exoplatform.org/xml/ns/kernel_1_2.xsd" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.exoplatform.org/xml/ns/kernel_1_2.xsd http://www.exoplatform.org/xml/ns/kernel_1_2.xsd">

    .....

</configuration>

<object-param>

  <name>portal.configuration</name>

  <object type="org.exoplatform.portal.config.NewPortalConfig">

    <field name="predefinedOwner">

     <collection type="java.util.HashSet">

       <value><string>classic</string></value>

     </collection>

    </field>

    <field name="ownerType">

      <string>portal</string>

    </field>

    <field name="templateLocation">

      <string>war:/conf/portal</string>

    </field>

    <field name="importMode">

      <string>merge</string>

    </field>

  </object>

</object-param>

<!--this configuration for defaul portal container with name "portal"-->
gatein-domain {
  org.gatein.wci.security.WCILoginModule optional;
  org.exoplatform.services.security.jaas.SharedStateLoginModule required;
  org.exoplatform.services.security.j2ee.TomcatLoginModule required;
};

<!--this configuration for new portal container with name "company"-->
gatein-domain-company {
  org.gatein.wci.security.WCILoginModule optional
    portalContainerName="company"
  	realmName="gatein-domain-company";
  org.exoplatform.services.security.jaas.SharedStateLoginModule required
    portalContainerName="company"
  	realmName="gatein-domain-company";
  org.exoplatform.services.security.j2ee.TomcatLoginModule required
    portalContainerName="company"
  	realmName="gatein-domain-company";
};