Hi All!
I recently tested the fornax oaw-m2-plugin to run my workflows from maven
(great plugin :). Using the plugin, I played around with dependency
configuration. What I would like to achieve is as follows:
- Preconfigure the Plugin with the important dependencies in my root-pom
<pluginManagement>
<plugins>
<plugin>
<groupId>org.fornax.toolsupport</groupId>
<artifactId>fornax-oaw-m2-plugin</artifactId>
<version>1.0.3</version>
<configuration>
....
</configuration>
<dependencies>
<dependency>
<groupId>org.fornax.openarchitectureware</groupId>
<artifactId>oaw-uml2</artifactId>
<version>4.1.1</version>
...
</dependency>
</dependencies>
<executions>
<execution>
<phase>generate-sources</phase>
<goals>
<goal>run-workflow</goal>
</goals>
</execution>
</executions>
</plugin>
</plugins>
</pluginManagement>
Because all my application projects use the same workflow.oaw-location I
already can specify the goal in the pluginManagment section of the root-pom
The transformation project now has a workflow that exports a profile from EA
Architect by means of the EA Exporter Plugin. The Configuration looks as
follows:
<groupId>mygroup</groupId>
<artifactId>my-transformation-project</artifactId>
<version>1.0</version
<build>
<plugins>
<plugin>
<groupId>org.fornax.toolsupport</groupId>
<artifactId>fornax-oaw-m2-plugin</artifactId>
</plugin
</plugins>
</builds>
Because the configuration of the plugin is already specified in the root pom
this works perfectly when I issue "mvn clean install" - the profile is
exported and the jar is build and installed
In my application project I now have the following configuration
<groupId>mygroup</groupId>
<artifactId>my-application-project</artifactId>
<version>1.0</version
<dependencies>
<dependency>
....
</dependency>
</dependencies>
<build>
<plugins>
<plugin>
<groupId>org.fornax.toolsupport</groupId>
<artifactId>fornax-oaw-m2-plugin</artifactId>
<dependencies>
<dependency>
<groupId>mygroup</groupId>
<artifactId>my-transformation-project</artifactId>
<version>1.0</version
</dependency>
</dependencies>
</plugin>
</plugins>
</builds>
As above, this works perfectly when I issue "mvn clean install" - the
workflow first exports the model from EA and generates the sources...
Now my problem:
When I issue "mvn clean install" from the root, the first workflow (of the
my-transformation-project) is executed correctly but the second workflow (of
the my-application-project) complains that it does not find things that are
in the my-transformation-project, e.g. the cartridge.oaw that resides in the
my-transformation-project.jar and is called from the workflow.oaw that
resides in my-application-project
Issuing "mvn clean install" independently only on the projects works, as
described above, without problems. Therefore I suppose there is a problem
with the dependencies mechanism of the fornax-plugin, e.g. it does not
recognize the dependency to the my-transformation-project in the
my-application-project after the workflow of the my-transformation-projcet
was executed....
Thank you for any hints on this issue.
Hannes
--
View this message in context:
http://www.nabble.com/Plugin-Dependencies-Configuration-tf3183228s17564.html#a8834582
Sent from the Fornax-Platform mailing list archive at Nabble.com.
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier.
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Fornax-developer mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/fornax-developer
