Coupling Overture to MDA and UML

Create eclipse projects from a maven repo.

• Check out the source
• Run mvn eclipse:clean to de sure that no eclipse settings exist
  • Also ensure that no .settings, .project .classpath files exist in the repo structure they should be in the svn ignore
• Run mvn eclipse:eclipse
• Open eclipse and set the workspace location to the same path where mvn eclipse:eclipse was executed.
• Go to Files->Import then select General-> Maven Projects and select the current workspace location.
• Now select all the projects shown in the list.
• Click ok and wait for eclipse to build the workspace.

Setting up Eclipse to use the Proper Maven Settings.xml

In order to use the settings.xml file where maven reads the user settings from Eclipse needs to know the path to this file. The integration in Eclipse by default sets the path to the user settings.xml so if you use the global settings instead you need to change the path:

The two most common places to store the settings:

• The Maven install: $M2_HOME/conf/settings.xml
• A user's install: ${user.home}/.m2/settings.xml

Settings can be stored at these locations in the respected files.

• Per Project
  • Defined in the POM itself (pom.xml).
• Per User
  • Defined in the Maven-settings (%USER_HOME%/.m2/settings.xml).
• Global
  • Defined in the global maven-settings (%M2_HOME%/conf/settings.xml).
• Profile descriptor
  • a descriptor located in project basedir (profiles.xml)

Set default profile in settings.xml

To set the default profile in the settings file insert this tag.

<activeProfiles>
    <activeProfile>profile-1</activeProfile>
</activeProfiles>

Get active profile

To get the actine profile used in maven use this:

mvn help:active-profiles

Maven

To set the Main class in a Jar file created as output in a Maven project the following is needed in the pom.xml file.

<plugin>
  <groupId>org.apache.maven.plugins</groupId>
  <artifactId>maven-jar-plugin</artifactId>
  <configuration>
    <archive>
      <manifest>
        <mainClass>com.someclass.Main</mainClass>
        <packageName>com.someclass</packageName>
      </manifest>
      <manifestEntries>
        <mode>development</mode>
        <url>${pom.url}</url>
      </manifestEntries>
    </archive>
  </configuration>
</plugin>

Maven

FAQ: unofficial faq

Mojo Developer cookbook http://docs.codehaus.org/display/MAVENUSER/Mojo+Developer+Cookbook

Introduction to Maven 2.0 Plugin Development http://maven.apache.org/guides/introduction/introduction-to-plugins.html

Maven

Here are a simple guide to create simple maven plugins

I have created a simple maven plugin to connect a java project to VDM Tools. This means that VDM files will be type checked at project buid and a vdmJava goal is added to support vdm to java code gen inside the eclipse project.

POM file for project using the plugin

<build>

<plugins>

<plugin>

           <groupId>org.overture.maven.plugin</groupId>

          <artifactId>vdmForMaven</artifactId>

           <configuration>

                      <mainVdmDirectory>src\main\vdm</mainVdmDirectory>

                      <mainJavaDirectory>src\main\java</mainJavaDirectory>

                      <javaPackage>org.overture.umltrans</javaPackage>

                      <testVdmDirectory>src\test\vdm</testVdmDirectory>

                      <testJavaDirectory>src\test\java</testJavaDirectory>

                      <vdmToolsCmd>c:\Program Files\The VDM++ Toolbox v8.1.1b\bin\vppde.exe</vdmToolsCmd>

           </configuration>

         <executions>

          <execution>

            <phase>compile</phase>

            <goals>

              <goal>typeCheck</goal>

            </goals>

          </execution>

        </executions>

</plugin>

</plugins>

</build>

Goals:

Code gen: org.overture.maven.plugin:vdmJava

Type check: .overture.maven.plugin:typeCheck

plugin mavn.zip (116.48 kb)

Maven