Hello, a better way is to define the fornax artifacts:
<dependency> <groupId>org.fornax.openarchitectureware</groupId> <artifactId>oaw-uml2</artifactId> <version>4.2.0</version> <scope>runtime</scope> </dependency> With this you always get all needed deps for the work with oaw and uml2-models. The scope runtime should work and avoids the oaw-deps to added to an assembly or packed in a war if your package type is war. Thorsten ----- Thorsten Kamann Software-Architect, Coach http://www.itemis.de http://www.thorsten-kamann.de Please visit the Fornax-Platform, the development platform for MDSD related component and tools: http://www.fornax-platform.org/ -- View this message in context: http://www.nabble.com/Workflow-invoked-from-maven-can%27t-read-profile-tf4778221s17564.html#a13672261 Sent from the Fornax-Platform mailing list archive at Nabble.com. ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Fornax-developer mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/fornax-developer
