[ 
http://jira.codehaus.org/browse/MASSEMBLY-464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=208494#action_208494
 ] 

Basil James Whitehouse III commented on MASSEMBLY-464:
------------------------------------------------------

Impossible is an exgaration.  Not expected, yes; and difficult for Nexus and 
other repo managers to index, yes 
([NEXUS-3158|https://issues.sonatype.org/browse/NEXUS-3158]).  A project can 
still depend on one of these assemblies and it will download the zip from the 
repo (even a Nexus repo) provided the type is defined.

I 
[posted|http://old.nabble.com/Missing-search-results-with-assembly-attached-artifacts-td26581535ef34835.html#a26581535]
 about this on the Nexus mailing list too.

Based on the examples from the above thread if you add this dependency:
{code:xml}
<dependency> 
  <groupId>com.example.maven</groupId> 
  <artifactId>zip-distribution-packaging-pom</artifactId> 
  <version>1.0.0-SNAPSHOT</version> 
  <type>zip</type> 
</dependency>
{code}

The zip will be downloaded.

Also note that there's currently an option to [exclude the assemblyId from the 
final 
name|http://maven.apache.org/plugins/maven-assembly-plugin/single-mojo.html#appendAssemblyId]
 which conflict with this issue.

The use case I have is to create a distribution bundle in a multi-module build. 
 There is a separate module to create this assembly and from an esthetic's 
perspective it's redundant to add a classifier to the filename.  If there were 
a packaging type of 'zip' I'd use that instead and AFAIK that would be more 
correct from a maven coordinates perspective and probably indexed correctly by 
Nexus.

> assembly descriptor id should be mandatory
> ------------------------------------------
>
>                 Key: MASSEMBLY-464
>                 URL: http://jira.codehaus.org/browse/MASSEMBLY-464
>             Project: Maven 2.x Assembly Plugin
>          Issue Type: Bug
>    Affects Versions: 2.2-beta-5
>            Reporter: Juven Xu
>
> I can create assembly using descriptor like this:
> {code:xml}
> <assembly>
>   <id></id>
>   <formats>
>     <format>zip</format>
>   </formats>
>   <fileSets>
>     <fileSet>
>       <directory>src/main/java</directory>
>     </fileSet>
>   </fileSets>
> </assembly>
> {code}
> the file created does not have a classifier, and it's not the main artifact 
> either, so it's impossible to locate it using maven coordinates. 
> the id should be mandatory so there will always a classifier.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to