Hmm, it should work if you add a dependency to the jar containing the workflow file.
if the workflow file is in a package you mustadd this to the workflowDescriptor. But this can be buggy, because this isn't tested for now. If this really doesn't want work please file an issue and append a simple testproject to simplify the repoduction of this behaviour. Thanks Thorsten Am Montag, den 03.03.2008, 06:06 -0800 schrieb Stefan Bley: > Hi, > > in the oaw-m2-plugin one can select the workflow file that ought to be > executed by setting the parameter <workflowDescriptor> which works fine if > the workflow is in the project (thus, in the classpath). > How can I do to specify a workflow outside of this project, e.g. from a > dependent plugin. > I set a <dependency> and tried all kind of <scope>s, but obviously it was > not appended to the classpath. > > Did I ignore something? > > Regards, Stefan ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Fornax-developer mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/fornax-developer
