|
Wouter,
I added the funtionality you were looking for when
it came to specifying properties to your cartridge. Namely I just changed
the existing "userProperty" notation to be consistent with the way properties
are now populated within the namespace for metafacades, outlets and
templateObjects. So now everyting is using the same property notation
through the namespaces with is a good thing I
think. The Maven plugin can now be used as is to do what
you want without added elements. In order to use this, you need to
define a property reference in your andromda-cartridge.xml: <property
reference="someProperty"/>, this reference tells the core that this property
is expected to be populated by the user (i.e ant task) through a namespace,
so in the andromda ant task we would have the below, just like its used for
outlets, and metafacade properties:
<namepsaces name="bpm4struts">
<property name="someProperty"
value="myPropertyValue"/>
</namespace>
Since you're using the maven cartridge, you would
just add another property to the plugin.properties like I was telling you
yesterday:
maven.andromda.namespace.1.property.8.name=someProperty maven.andromda.namespace.1.property.8.value=somePropertyValue Let me know if you have any questions, Thanks, Chad P.S. Matthias, I'm assuming a change like this is OK with you, as it makes things more consistent. |
- [Andromda-devel] RE: Template properties Chad Brandon
- [Andromda-devel] RE: Template properties Wouter Zoons
- Re: [Andromda-devel] RE: Template properties Chad Brandon
- RE: [Andromda-devel] RE: Template properties Wouter Zoons
