That is definitly doable, but would be nicer to just specify it once and be doen with it. If I can't find a solution here pretty soon, I can just do that.
Jim On Mon, 30 Sep 2002 [EMAIL PROTECTED] wrote: > Sounds like it'd be easier to update a file they fill in in the correct > format, i.e. maven will generate pieces of the file and they can then add > their own pieces after. > > If it's arbitrary stuff, I'd much rather they updated a generated file. > > What do you think? > -- > dIon Gillard, Multitask Consulting > Work: http://www.multitask.com.au > Developers: http://adslgateway.multitask.com.au/developers > > > Jim Birchfield <[EMAIL PROTECTED]> wrote on 30/09/2002 10:56:21 AM: > > > > > > > On Mon, 30 Sep 2002 [EMAIL PROTECTED] wrote: > > > > > Jim Birchfield <[EMAIL PROTECTED]> wrote on 30/09/2002 09:37:18 AM: > > > > > > > Can I have something likke this? > > > > > > > > maven.jnlp.property=foo,bar > > > > maven.jnlp.property=foo.baz > > > > maven.jnlp.property=bar.baz > > > > > > Well, no, because properties are like variables - the name must be > unique. > > > The above simply assigns three different values to the same property > > > 'maven.jnlp.property' in sequence. > > > > That's what I thought, but thought you had something in mind...;-) > > > > > > > > > > > > > then somehow do > > > > for allProperties { > > > > handle prop? > > > > } > > > > > > > > If possible, can you send me soemthing showing how to do this? > > > > > > How about you tell me what you're trying to do, and we try working out > a > > > way of doing it. > > > > What I need to do is allow people to put a variable number of things in > > the properties file(or somewhere. The best (but ugly) solution I have > is > > something like this: > > > > maven.jnlp.property.number=2 > > maven.jnlp.property.name.1=foo > > maven.jnlp.property.value.1=bar > > maven.jnlp.property.name.2=bar > > maven.jnlp.property.value.2=baz > > > > Then write a Jelly tag that looks similar to: > > > > <jnlp:propertyIterator > > propertyName="maven.jnlp.property"/> > > > > And this tag looked up $propertyName.number, loops over > $propertyName.name > > and $propertyName.value and printed out the appropriate tag. > > > > I remember doing some serious ugly stuff in properties files several > years > > ago, hence my appreciation for XML based property files. > > > > Do you see a better approach for this? > > > > Jim > > > > > > > > > Thanks! > > > > > > > > Jim > > > -- > > > dIon Gillard, Multitask Consulting > > > Work: http://www.multitask.com.au > > > Developers: http://adslgateway.multitask.com.au/developers > > > > > > > > > > > > > > > -- > > > To unsubscribe, e-mail: <mailto:turbine-maven-user- > > [EMAIL PROTECTED]> > > > For additional commands, e-mail: <mailto:turbine-maven-user- > > [EMAIL PROTECTED]> > > > > > > > > > > > > -- > > To unsubscribe, e-mail: <mailto:turbine-maven-user- > > [EMAIL PROTECTED]> > > For additional commands, e-mail: <mailto:turbine-maven-user- > > [EMAIL PROTECTED]> > > > > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
