my workspace configuration is as follows (exemplary): 1) JAR project + ZIP attachment with classifier (depends on some stuff, doesn't matter); 2) POM project aggregation which depends on the JAR above (and also on some other stuff); 3) WAR module project of the POM above (packaged as skinny, no specific deps apart from the parent ones); 4) EAR module, which lists the above POM as parent (to not having to duplicate all the deps declaration), but is placed in a subdirectory of the WAR module (like it's described in "building skinny wars" maven tutorial). this EAR includes the above WAR and the above classified ZIP and also is configured to put all the libs into "/lib" directory (like in the tutorial).
what i encounter is when i run "mvn package" on the EAR from the command line, JAR dependency 1) doesn't go to EAR (while all its transitive dependencies strangely do). However if i choose "Run As -> Maven package" on the EAR in eclipse - it does. This is 100% reproducable (at least with my project configuration). As far as I understand, both m2eclipse and maven command line should behave the same way in any case, so I'm curious where the problem is. Environment: Jdk6, m2eclipse 0.9.6, maven 2.1.0-M1, eclipse ganymede. -- View this message in context: http://www.nabble.com/Different-behavior-between-m2eclipse-and-maven-command-line-tp20830604p20830604.html Sent from the Maven Eclipse - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
