[ 
http://jira.codehaus.org/browse/MEAR-77?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_110830
 ] 

Stephane Nicoll edited comment on MEAR-77 at 10/22/07 9:08 AM:
---------------------------------------------------------------

I didn't say it isn't a bug. I am saying that EAR plugin has nothing to do with 
that at a glance.

If you're running mvn something from the parent project, the dependencies are 
taken from the reactor list (so the files in the target directory of each 
project). I've never seen a situation where they were duplicated, unless clean 
wasn't called of course).

Please provide a project that reproduces your issue.




 was:
I didn't say it isn't a bug. I am saying that EAR plugin has nothing to do with 
that at a glance.

If you're running mvn something from the parent project, the dependencies are 
taken from the reactor result (so the files in the target directory of each 
project). I've never seen a situation when they were duplicated, unless clean 
wasn't called of course).

Please provide a projet that reproduces your issue.



> Duplicated jars in ear
> ----------------------
>
>                 Key: MEAR-77
>                 URL: http://jira.codehaus.org/browse/MEAR-77
>             Project: Maven 2.x Ear Plugin
>          Issue Type: Bug
>    Affects Versions: 2.3.2
>         Environment: Win XP SP2, JDK 1.6.0, JRE 1.6.0_03, Maven 2.0.7
>            Reporter: Tomek Matynia
>            Priority: Trivial
>         Attachments: poms.txt
>
>
> Hi, this is my first issue submition, hope it is one, otherwise sorry for 
> bothering. If i did something wrong feel fre to teach me (I'm a beggining 
> software devloper, eager to learn).
> I use Maven as an integration tool for an enterprise application with web, 
> ejb and simple jar modules.
> I have poms like included in attachment, in my projects (I use Eclipse as 
> IDE, therefore its flat projects structure). I build the ear using 
> aggregation mechanism by calling goals 'clean package' on the 
> parent/aggregating project. It builds me an ear. That is ok. But when I 
> assign project.build.finalName on p5041a-krk-core (as "krk-core"), 
> p5041a-krk-ejb (as "krk-ejb") and p5041a-krk-web (as "krk-web"), for more 
> readable, then I get duplicated jars (core, ejb and web) in ear. In generated 
> application.xml, there are only those which I included in maven-ear-plugin's 
> configuration. I imagine, I get them from dependency, they are copied from my 
> local maven repo.
> This is rather trivial issue, but i spent some time finding out what was 
> wrong. Now I don't use project.build.finalName.
> Geetings to all Maven team, You're doing a great job, and sorry for my 
> english, if it's bad.

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