maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ben Tomasini (JIRA)" <>
Subject [jira] Commented: (MNG-4148) Apply profiles from settings.xml to POMs built from the repository
Date Thu, 23 Dec 2010 22:08:00 GMT


Ben Tomasini commented on MNG-4148:

I have created a plugin which depends on a jar in a heavyweight application server which has
a number of hard coded class path entries in the jar's manifest.  Uploading all of the jar
files to our internal repository is simply not practical.

Using a systemPath in the dependency declaration of the plugin with a property to set the
directory of the app server would be ideal in this case.  

> Apply profiles from settings.xml to POMs built from the repository
> ------------------------------------------------------------------
>                 Key: MNG-4148
>                 URL:
>             Project: Maven 2 & 3
>          Issue Type: Improvement
>          Components: Artifacts and Repositories, POM, Profiles
>    Affects Versions: 2.1.0
>            Reporter: John Casey
>            Assignee: John Casey
>             Fix For: 2.2.2
>         Attachments:
> When we declare a profile in the settings.xml, it will never be applied to POMs loaded
from the Maven repository. This means that overriding the central repository definition -
for instance - cannot be done without using mirror definitions, since transitive dependencies
(any dependency of a direct dependency) will skip the modified definition and use the original
from the super-POM instead.
> I'm attaching a testing setup that was originally reported for MNG-3553, which exhibits
this problem when dealing with scope == import. The instructions for using it are as follows:
> {noformat}
> I installed locally a nexus server (1.3.3 Open Source) and I'm using maven 2.1.0 (I reproduced
the issue with 2.0.10).
> In the releases repository of nexus you upload all artifacts given in the toUpload directory
>     * parent 1.0.0 pom
>     * dependencies 1.0.0 pom
>     * module 1.0.0 pom and jar
> You'll find in the root of the archive my settings. It defines to use nexus for the central
> You launch a build of the project and you'll have :
> [INFO] Scanning for projects...
> [INFO] ------------------------------------------------------------------------
> [INFO] Building Unnamed -
> [INFO]    task-segment: [install]
> [INFO] ------------------------------------------------------------------------
> [INFO] [resources:resources]
> [WARNING] Using platform encoding (Cp1252 actually) to copy filtered resources, i.e.
build is platform dependent!
> [INFO] skip non existing resourceDirectory E:\jtb\workspaces\tests\test-mng3553\project\src\main\resources
> Downloading: http://localhost:8081/nexus/content/groups/public//org/apache/maven/it/mng3553/module/1.0.0/module-1.0.0.pom
> 867b downloaded  (module-1.0.0.pom)
> Downloading:
> [WARNING] Unable to get resource ''
> from repository central ( Authorization failed: Access
denied to:
> [INFO] ------------------------------------------------------------------------
> [INFO] ------------------------------------------------------------------------
> [INFO] Failed to resolve artifact.
> GroupId:
> ArtifactId: dependencies
> Version: 1.0.0
> Reason: Unable to download the artifact from any repository
> from the specified remote repositories:
>   central (
> [INFO] ------------------------------------------------------------------------
> [INFO] For more information, run Maven with the -e switch
> [INFO] ------------------------------------------------------------------------
> [INFO] Total time: 1 second
> [INFO] Finished at: Thu Apr 30 15:19:47 CEST 2009
> [INFO] Final Memory: 6M/254M
> [INFO] ------------------------------------------------------------------------
> You can see that the project downloads successfully the module-1.0.0 from nexus but
> it fails for depencencies which is an import. It tries to download it from the real central
> and not from the one I defined in my settings.
> The behavior is inconsistent...
> {noformat}

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