problems with OEM license/enhancing

we did add this section to our maven pom.xml (from within Eclipse):

...

<build>
  <pluginManagement>

...

<plugin>
     <groupId>org.codehaus.mojo</groupId>
     <artifactId>exec-maven-plugin</artifactId>
     <version>1.2</version>
     <executions>
      <execution>
       <id>enhance</id>
       <phase>process-classes</phase>
       <goals>
        <goal>java</goal>
       </goals>
       <configuration>
        <mainClass>com.objectdb.Enhancer</mainClass>
        <arguments>
         <argument>com.agile.hummingbird.Document</argument>
         <argument>com.agile.hummingbird.ObjectType</argument>
         <argument>com.agile.hummingbird.ObjectNode</argument>
         <argument>com.agile.hummingbird.ObjectProperty</argument>
         <argument>com.agile.hummingbird.LogEntry</argument>
         <argument>com.agile.hummingbird.Action</argument>
         <argument>com.agile.hummingbird.CurrentData</argument>
         <argument>com.agile.hummingbird.SystemConfiguration</argument>
        </arguments>
       </configuration>
      </execution>
     </executions>
    </plugin>

...

After creating our application jar on a workstation with the OEM license activation, we cannot start the application on another workstation. We receive a message that the evaluation limit of 1000000 objects is reached ...

The classes are probably not enhanced with the OEM Enhancer.

Please check if in the build output the classes implement the interfaces:

• com.objectdb.spi.TrackableUserType - indicates a class is enhanced (OEM or not).
• com.objectdb.spi.SignedType - indicates that a class is OEM enhanced.

If the classes are enhanced but not OEM enhanced, probably the OEM activation key is not available during enhancement. Check the location of the objectdb.jar file and make sure that the objectdb.conf file with the activation key is located in the correct location (same directory as objectdb.jar, except if that directory is lib, bin or build).

as regards the correct location:

where to place the objectdb.conf in a maven environment (objectdb is referenced via a dependency and therefore located in the maven repository) ?

The same rules apply also when using Maven, i.e. by default the objectdb.conf is searched relative to the location of the objectdb.jar file (which could be in your local repository, web application, etc.)

But you can change the default by setting the objectdb.home or objectdb.conf system properties.

I did set now the objected.home via :

...

<plugin>
    <groupId>org.codehaus.mojo</groupId>
    <artifactId>properties-maven-plugin</artifactId>
    <version>1.0.0</version>
    <executions>
        <execution>
            <goals>
                <goal>set-system-properties</goal>
            </goals>
            <configuration>
                <properties>
                    <property>
                        <name>objectdb.home</name>
                        <value>MyObjectdb.home</value>
                    </property>
                </properties>
            </configuration>
        </execution>
    </executions>
</plugin>

...

what works fine