maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Donatas Ciuksys (JIRA)" <j...@codehaus.org>
Subject [jira] (MASSEMBLY-584) Assembly Plugin is looking for SNAPSHOT artifacts in release repositories
Date Sat, 18 Feb 2012 11:21:02 GMT

    [ https://jira.codehaus.org/browse/MASSEMBLY-584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=292077#comment-292077
] 

Donatas Ciuksys commented on MASSEMBLY-584:
-------------------------------------------

{quote}
I believe this only happens when you have both snapshot and release repos pointing at the
same URL.
{quote}
Yes, this is a case - our snapshot and release repositories have the same URL. Yet this makes
no problems for war and similar plugins.
                
> Assembly Plugin is looking for SNAPSHOT artifacts in release repositories
> -------------------------------------------------------------------------
>
>                 Key: MASSEMBLY-584
>                 URL: https://jira.codehaus.org/browse/MASSEMBLY-584
>             Project: Maven 2.x Assembly Plugin
>          Issue Type: Bug
>    Affects Versions: 2.2.1
>         Environment: Windows 7, java 1.6.0_29, Maven 3.0.3
>            Reporter: Donatas Ciuksys
>            Priority: Blocker
>
> Assembly plugin fails to retrieve snapshot with unique version from repository, and as
a result the generated zip file contains signatures-xades-1.2-SNAPSHOT.jar instead of signatures-xades-1.2-20111121.181823-3.jar.
> Descriptor:
> {code}
> <assembly>
>   <id>bin</id>
>   <formats>
>     <format>zip</format>
>   </formats>
>   <includeBaseDirectory>false</includeBaseDirectory>
>   <dependencySets>
>     <dependencySet>
>       <outputDirectory>lib/</outputDirectory>
>       <useProjectArtifact>false</useProjectArtifact>
>     </dependencySet>
>     <dependencySet>
>       <outputDirectory>/</outputDirectory>
>       <useProjectArtifact>true</useProjectArtifact>
>       <includes>
>           <include>${project.groupId}:${project.artifactId}</include>
>       </includes>
>     </dependencySet>
>   </dependencySets>
> </assembly>
> {code}
> Maven debug output (-X) contains:
> {quote}
> [DEBUG] Resolving project dependencies transitively.
> [DEBUG] lt.mitsoft.vmi:eds3-batch:war:1.0-SNAPSHOT (selected for null)
> [DEBUG]   lt.mitsoft.vmi:eds3-mdoc:jar:1.0-SNAPSHOT:compile (selected for compile)
> [DEBUG]     lt.mitsoft.adoc:adoc-core:jar:1.1:compile (selected for compile)
> ...
> [DEBUG]       lt.mitsoft.pki.signatures:signatures-xades:jar:1.1:compile (selected for
compile)
> ...
> [DEBUG] Verifying availability of C:\Users\Donatas\.m2\repository\lt\mitsoft\pki\signatures\signatures-xades\1.2-SNAPSHOT\signatures-xades-1.2-20111121.181823-3.pom
from [central (https://int.mitsoft.lt:3681/artifactory/repo, releases), google (http://mbari-maven-repository.googlecode.com/svn/repository/,
releases), org.tmatesoft.svnkit-releases (http://maven.tmatesoft.com/content/repositories/releases/,
releases)]
> [WARNING] Missing POM for lt.mitsoft.pki.signatures:signatures-xades:jar:1.2-SNAPSHOT:
Error resolving project artifact: Could not find artifact lt.mitsoft.pki.signatures:signatures-xades:pom:1.2-20111121.181823-3
for project lt.mitsoft.pki.signatures:signatures-xades:pom:1.2-SNAPSHOT
> [DEBUG]   lt.mitsoft.pki.signatures:signatures-xades:jar:1.1:compile (removed - nearer
found: 1.2-SNAPSHOT)
> [DEBUG]   lt.mitsoft.pki.signatures:signatures-xades:jar:1.2-SNAPSHOT:compile (selected
for compile)
> ...
> {quote}
> The problem is that artifact signatures-xades-1.2-20111121.181823-3.pom (that is, signatures-xades-1.2-SNAPSHOT)
is being looked-up in *release* repositories (as shown above):
> {code}
> [central (https://int.mitsoft.lt:3681/artifactory/repo, releases), 
> google (http://mbari-maven-repository.googlecode.com/svn/repository/, releases), 
> org.tmatesoft.svnkit-releases (http://maven.tmatesoft.com/content/repositories/releases/,
releases)]
> {code}
> The culprit might be the dependency override: 
> {code}
> [DEBUG]   lt.mitsoft.pki.signatures:signatures-xades:jar:1.1:compile (removed - nearer
found: 1.2-SNAPSHOT)
> [DEBUG]   lt.mitsoft.pki.signatures:signatures-xades:jar:1.2-SNAPSHOT:compile (selected
for compile)
> {code}
> The first candidate was signatures-xades:jar:1.1 (release), but the chosen artifact is
signatures-xades:jar:1.2-SNAPSHOT. I guess the repository type was chosen based on the first
candidate, and this is wrong.
> *Even bigger problem is that since POM retrieval failed, all dependencies specified in
signatures-xades-1.2-20111121.181823-3.pom were not being taken into account (and are absent
in generated zip file).*

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message