maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yann Le Du (JIRA)" <j...@codehaus.org>
Subject [jira] Commented: (MNG-2145) Plugins' dependencies are not always checked
Date Mon, 13 Mar 2006 18:12:35 GMT
    [ http://jira.codehaus.org/browse/MNG-2145?page=comments#action_60912 ] 

Yann Le Du commented on MNG-2145:
---------------------------------

OK, I've made a small test suite, and here is a clumsy guess about the process. Let's assume
that main <build> is assimilated to a <profile> (in first position).
# (!) In an <execution>, if no <id> is defined, then <id>default</id>
is added
# (!) If an <execution> is defined in several activated <profile> with the same
<id>, the <execution> in the last <profile> overwrites the <execution>
in the first <profile>
# (/) If several <execution> with different <id> are defined in several activated
<profile> for the same <artifactId>, they are merged in the first <profile>
# (x) If several <dependency> are defined in several activated <profile> for the
same <artifactId>, they are NOT merged in the first <profile>
# (!) If several <plugin> are defined in the same <profile> with the same <artifactId>,
I don't know what happens :p
# (/) If no <plugin> is defined in main <build> for a given <artifactId>,
the one in the first <profile> is copied into main <build>

I think that :
* because of points 1. and 2. , <id> should be mandatoty
* point 4. should be corrected
* situation in point 5. should not be allowed

> Plugins' dependencies are not always checked
> --------------------------------------------
>
>          Key: MNG-2145
>          URL: http://jira.codehaus.org/browse/MNG-2145
>      Project: Maven 2
>         Type: Bug

>   Components: Dependencies
>     Versions: 2.0.2
>     Reporter: Daiyam
>     Priority: Blocker
>  Attachments: pom-echo.xml, pom-merge.xml, pom-profile.xml, pom.xml, test-suite.zip
>
>
> I want to run two ant task, one on the phase 'generate-sources' which contains a dependency
and another on the phase 'package'.
> When I want to compile with the project like that, maven don't check the dependency.
> But when I comment the plugin on the phase 'package', maven check it.
> PS: In the pom.xml in attachement, maven must check the library junit:junit:jar:30.80.10
(which don't exsist)

-- 
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


Mime
View raw message