maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marc Wirth (JIRA)" <>
Subject [jira] Created: (MNG-4714) "legacy" repositories are silently treated as "default" repositories?
Date Wed, 23 Jun 2010 11:45:12 GMT
"legacy" repositories are silently treated as "default" repositories?

                 Key: MNG-4714
             Project: Maven 2 & 3
          Issue Type: Bug
          Components: Artifacts and Repositories
    Affects Versions: 3.0-beta-1
            Reporter: Marc Wirth
            Priority: Minor
         Attachments: pom.xml

Support for legacy repositories was removed for but
if you now try to build something were an artifact exists only on a "legacy" repository the
build will warn:

[WARNING] 'repositories.repository.layout' for uses the deprecated
value 'legacy'. @ 
[WARNING] For this reason, future Maven versions might no longer support building such malformed

but then the build just fails with a missing artifact message.

Class org.apache.maven.repository.legacy.LegacyRepositorySystem has explicitly:

    public ArtifactRepository createArtifactRepository( String repositoryId, String url, ArtifactRepositoryLayout
repositoryLayout, ArtifactRepositoryPolicy snapshots, ArtifactRepositoryPolicy releases )
        if ( repositoryLayout == null )
            repositoryLayout = layouts.get( "default" );

So while the LegacyRepositoryLayout does not exist anymore, Maven will treat the repository
as Default-Repository and of course fail to find something.

>From my point of view the Warning at the beginning should rather be an error. The reference
to "future" versions is also quite misleading as the support was already removed in the current
version (-> org.apache.maven.model.validation.DefaultModelValidator#validateRepository
reports that violation).

What's the intended behaviour here?

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


View raw message