Polly, the plugin searches on the classpath for the workflow file. I'm pretty sure that it works that way since I'm using it in my project.
There is a deeper sense behind those one-line workflows. A cartridge project is reusable, and normally it does not know about which model to read at least. The project that contains the model will call the cartridge workflow and pass the model uri and maybe other project specific properties. This is usually the project that executes the generator plugin. Do not try to execute the plugin from the cartridge project. ~Karsten > > Hi, > > Does the fornax-oaw-m2-plugin support finding a workflow.oaw file > from the > classpath instead of inside the project? The plugin can pass in > properties > for everything that I want to configure, so there's no need for me > to have a > one-line workflow.oaw file inside my project that just refers to the > cartridge file inside the classpath. It would be nice to be able to > get rid > of this local file completely. But when I set the plugin's > <workflowDescriptor> to the workflow file that is inside my > classpath, the > plugin doesn't seem like it's able to find it. > -- > View this message in context: > http://www.nabble.com/-fornax-oaw-m2-plugin--find-workflow.oaw-file-in-classpath--tp24358345s17564p24358345.html > Sent from the Fornax-Platform mailing list archive at Nabble.com. > > > ------------------------------------------------------------------------------ > _______________________________________________ > Fornax-developer mailing list > Fornax-developer@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/fornax-developer ------------------------------------------------------------------------------ _______________________________________________ Fornax-developer mailing list Fornax-developer@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/fornax-developer
