[ 
https://issues.apache.org/jira/browse/EXTCDI-91?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12968487#action_12968487
 ] 

Jakob Korherr commented on EXTCDI-91:
-------------------------------------

It turned out to be a configuration problem of the assembly-plugin. The problem 
is that you can specify a finalName for the assembly output files, but in the 
further maven-lifecycle (for install and deploy) the .zip and .tar.gz files are 
referred to as attached artifacts. Thus the specified finalName gets lost and 
the "new" filename is generated from the artifacts details (artifactId and 
version).

The only way to add our "src" and "bin" suffixes is to set appendAssemblyId to 
true and to change the assembly-ids to "src" and "bin" respectively. I 
committed the necessary changes including some config-cleanup on the 
assembly-plugin and now both assemblies are installed correctly.

NOTE that the final name of the assemblies is now e.g. 
myfaces-extcdi-assembly-jsf20-0.9.1-bin.zip instead of 
myfaces-extcdi-jsf20-0.9.1.zip, because maven generates this filename from the 
project artifactId (as described above).


> src-assemblies are lost during release procedure and bin-asseblies are renamed
> ------------------------------------------------------------------------------
>
>                 Key: EXTCDI-91
>                 URL: https://issues.apache.org/jira/browse/EXTCDI-91
>             Project: MyFaces CODI
>          Issue Type: Task
>    Affects Versions: 0.9.1
>            Reporter: Jakob Korherr
>
> During the release procedure the bin-assemlies which are normally named 
> myfaces-extcdi-assembly-jsfxx-0.9.1-bin.zip are renamed to 
> myfaces-extcdi-assembly-jsfxx-0.9.1.zip (without bin) and the src-assemblies 
> are not uploaded to the staging-repo at all.
> This is most likely a misconfiguration of the assembly or the release plugin. 
> I guess we somehow have to tell the release-plugin which files have to be 
> uploaded to the staging repo and currently we have no such configuration.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to