Karl Heinz Marbaise wrote:
> Hi Jörg,
>
> thanks for answering...
>>
>> The id of the assembly *is* the classifier ... so how do you
>> create distinct files, if you use always the same assembly?
>> Note, that the result of the assembly *is* already an
>> attached artifact. Simply call "mvn deploy" and you will see
>> which artifact Maven explicitly knows about. Remember, those
>> are the only ones that will be published in the "official" repository
>> making a release.
> Ok. I just do in my pom for the assembly plugin:
>
> <execution>
> <id>config-1</id>
> <phase>package</phase>
> </goals><goal>single</goal></goals>
> <configuration>
> <descriptors><descriptor>.../assembly/config.xml</descriptor><
> /descriptors> <filters><filter>filterC1.properties</filter></filters>
> <finalName>${basename}-config1</finalName>
> </execution>
> This part i repeat for every config i need where i change only the
> filter file...
IIRC setting the finalName will only change the name locally in your target
directory. If Maven deploys those filed into the repository, they will
overwrite themselves, since from Maven's view they are all the same and the
artifacts name in the repo is build from the artifactId and the classifier
defined in the assembly/config.xml. This also means that performing a release
your files are lost after you cleaned out your local build directory. Call "mvn
install" and look into your local repo. Will you find all 8 configured files? I
bet not.
- Jörg
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
