Yes, the property is required in the Ant task only, makes sense. Okay I'll run with it, thanks again
Wouter. > -----Original Message----- > From: Chad Brandon [mailto:[EMAIL PROTECTED] > Sent: Wednesday, March 24, 2004 4:23 PM > To: [EMAIL PROTECTED] > Cc: 'Matthias Bohlen'; [EMAIL PROTECTED] > Subject: Re: [Andromda-devel] RE: Template properties > > The property is required, unless you explicity ignore > it, by setting the ignore attribute to true if you > want a default, you just set the property in the > 'default' namespace (within the ant task). For your > cartridge, to make a default, just add the propery to > the plugin.properties file (like the property in the > previous email) Does that answer your question? > > --- Wouter Zoons <[EMAIL PROTECTED]> wrote: > > Already ? Awesome, thanks Chad! > > > > One question though, is the property required or is > > there a default > > value in case the user did not specify it ? > > > > I could not deduct this from your email. although > > when you wrote the > > Maven properties I guessed the somePropertyValue > > would be the default > > one > > > > Thanks > > Wouter. > > > > -----Original Message----- > > From: Chad Brandon [mailto:[EMAIL PROTECTED] > > Sent: Wednesday, March 24, 2004 1:48 PM > > To: [EMAIL PROTECTED] > > Cc: Matthias Bohlen; > > [EMAIL PROTECTED] > > Subject: Template properties > > > > 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. > > > > > > ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ Andromda-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/andromda-devel
