Hi Thorsten i would agree that using "runtime" scopes will ensure you get your dependencies during the workflow execution BUT i must disagree on your 2nd statement : such dependencies WILL be included in a packaged war that is exactly my current problem
i package my templates and workflows as cartridges i put one or more of these cartridges in the project classpath and configure the oaw-m2 (2.0.0) plugin to run it => scope runtime, generation is fine but the final war's WEB-INF/lib contains my cartridges artifacts as well as ecore, eclipse and oaw runtimes => scope compile, same behavior i've manually forced the "requiredDependencyResolution" to take the value "test" and then i get the behavior you described and which i expect(-ed) : => scope test, generation is ok and the libraries don't get packaged i have not been able to find where the 2.0.0 plugin source code was located the sourceforge svn repository seems to only contain the 1.0.5 but i browsed the 1.0.5 source code and found that the requiredDependencyResolution was "test" in this version... Why was it changed to runtime for the 2.0.0 ? thorque wrote: > > 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 > > -- View this message in context: http://www.nabble.com/Workflow-invoked-from-maven-can%27t-read-profile-tp13668791s17564p16983335.html Sent from the Fornax-Platform mailing list archive at Nabble.com. ------------------------------------------------------------------------- This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone _______________________________________________ Fornax-developer mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/fornax-developer
