Or are you talking about when people are configuring within the pom

in which case I don't mind prefixing them with

forCliUseOnly

so that the configuration block would be

<configuration>
  <forCliUseOnlyFiles>...</forCliUSeOnlyFiles>
</configuration>

but it's still tied to the property "files" so that on the CLI I just type
-Dfiles=...

On 23 June 2011 10:15, Stephen Connolly <stephen.alan.conno...@gmail.com>wrote:

> This is for the CLI
>
> mvn deploy:deploy-file -Dpom=myart.pom -Dfile=myart.jar
> -Dsources=myart-sources.jar -Djavadoc=myart-javadoc.jar
> -Dfiles=myart-src.zip,myart-src.tar.gz,myart-bin.zip,myart-bin.tar.gz
> -Dtypes=zip,tar.gz,zip,tar,gz -Dclassifiers=src,src,bin,bin
>
> Do we really want to force people to type out a lot lot more
>
>
> On 23 June 2011 09:41, Brett Porter <br...@apache.org> wrote:
>
>> On 21/06/2011, at 4:25 PM, steph...@apache.org wrote:
>>
>> > Author: stephenc
>> > Date: Tue Jun 21 08:25:23 2011
>> > New Revision: 1137904
>> >
>> > URL: http://svn.apache.org/viewvc?rev=1137904&view=rev
>> > Log:
>> > [MDEPLOY-137] Allow deployment of multiple side artifacts at the same
>> time via the CLI
>> >
>> [snip]
>> > +    /**
>> > +     * A comma separated list of types for each of the extra side
>> artifacts to deploy. If there is a mis-match in
>> > +     * the number of entries in {@link #files} or {@link #classifiers},
>> then an error will be raised.
>> > +     *
>> > +     * @parameter expression="${types}";
>> > +     */
>> > +    private String types;
>> > +
>> > +    /**
>> > +     * A comma separated list of classifiers for each of the extra side
>> artifacts to deploy. If there is a mis-match in
>> > +     * the number of entries in {@link #files} or {@link #types}, then
>> an error will be raised.
>> > +     *
>> > +     * @parameter expression="${classifiers}";
>> > +     */
>> > +    private String classifiers;
>> > +
>> > +    /**
>> > +     * A comma separated list of files for each of the extra side
>> artifacts to deploy. If there is a mis-match in
>> > +     * the number of entries in {@link #types} or {@link #classifiers},
>> then an error will be raised.
>> > +     *
>> > +     * @parameter expression="${files}"
>> > +     */
>> > +    private String files;
>>
>> Given these are so closely tied together - would it be better to use a
>> list of <attachedArtifacts> each with <file> <type> and <classifier> ? I
>> know it's more verbose, but probably less error prone.
>>
>> Either way, I think these args should have something more on the front -
>> attachedFiles or extraFiles, or similar.
>>
>> - Brett
>>
>> --
>> Brett Porter
>> br...@apache.org
>> http://brettporter.wordpress.com/
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
>> For additional commands, e-mail: dev-h...@maven.apache.org
>>
>>
>

Reply via email to