Hi Polly,
the project that executes the Fornax plugin needs a dependency to the
project containing sculptorworkflow.oaw. This workflow must be found
on the classpath, you maybe have to add the folder containing the
workflow as additional resource folder when not following the defaults
(e.g. /src/main/resources is on the classpath by default). When
sculptorworkflow.oaw resides not in the classpath root then you have
to qualify the workflow with the package path.
This should be all. The Fornax plugin adds all runtime dependencies of
the project that it is executed within to the context classpath and
then invokes the WorkflowRunner.
Hope this helps you a bit,
~Karsten
Am 06.07.2009 um 20:02 schrieb polly.c.chang:
>
> Hi Karsten,
>
> Thanks for the quick reply! Yup, I'm using the Fornax plugin to
> pass the
> project-specific properties to the generator project. I'll give you
> some
> more details.
>
> In my user project POM, I normally pass in the properties like this:
> <plugin>
>
> <groupId>org.fornax.toolsupport</groupId>
>
> <artifactId>fornax-oaw-m2-plugin</artifactId>
> <executions>
> <execution>
> <id>generate-main</id>
> <configuration>
>
> <checkResources>...</checkResources>
>
> <workflowDescriptor>workflow.oaw</workflowDescriptor>
> <properties>
>
> <modelFile>${codegen.model.basedir}/${codegen.model}</
> modelFile>
>
> <appProject>${codegen.project}</appProject>
> ...
> </properties>
> </configuration>
> </execution>
> </executions>
> </plugin>
>
> The local workflow.oaw file in my user project says:
>
> <workflow>
> <cartridge file="sculptorworkflow.oaw" inheritAll="true" />
> </workflow>
>
> This is because I modified sculptorworkflow.oaw to declare the two
> properties:
> <property name="modelFile" value="${modelFile}"/>
> <property name="appProject" value="${appProject}"/>
>
> All that works fine with the local workflow.oaw file. So I was
> trying to
> see if I can get rid of the workflow.oaw file completely since my
> plugin
> config is being run in the user project and already has all the
> properties
> that I need to send into the generator.
>
> This is what I tried. I changed the plugin config to say
> <workflowDescriptor>sculptorworkflow.oaw</workflowDescriptor>
>
> And then modified the sculptorworkflow.oaw file to not be abstract
> and to
> "inheritAll" so it will take properties from the Fornax plugin:
>
> <workflow inheritAll="true">
> <property name="modelFile" value="${modelFile}"/>
> <property name="appProject" value="${appProject}"/>
> ...
> </workflow>
>
> When I run this, I get the error:
> "Could not find the Workflow-Descriptor "sculptorworkflow.oaw"."
>
> I am running plugin version 2.1.1, and the generator project is not
> in my
> workspace. Does the generator's workflow file have to be in the
> workspace
> for the file to be found by the plugin?
>
> Thanks!
> --Polly
>
>
>
> Karsten Thoms wrote:
>>
>> 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
>>
>>
>
> --
> View this message in context:
> http://www.nabble.com/-fornax-oaw-m2-plugin--find-workflow.oaw-file-in-classpath--tp24358345s17564p24360149.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
