Because you have a transitive dependency that you don't want polluting your Eclipse classpath but you still need at runtime? For example, when I hit Ctrl+Space to suggest a class I don't want to see the BSF classes but Tapestry needs that jar at runtime.
Can dependency scopes solve most of this problem? Maybe the only jars to appear in the eclipse .classpath should be those in the compile, test and provided scopes? Or should the eclipse classpath reflect the full set of libraries required at runtime? mike -----Original Message----- From: Kenney Westerhof [mailto:[EMAIL PROTECTED] Sent: Tuesday, September 27, 2005 4:07 PM To: Maven Users List Subject: Re: [M2] equivalent to <eclipse.dependency>false</eclipse.dependency> On Tue, 27 Sep 2005, Erick Dovale wrote: No, there isn't, why would you want that? Maybe there's some other solution? > Hello there, > is there an equivalento to > <eclipse.dependency>false</eclipse.dependency> in M2 so that when I > call > m2 eclipse:eclipse these dependecies don;t get added to the .classpath > file?? > > Thanks. > > edovale > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > -- Kenney Westerhof http://www.neonics.com GPG public key: http://www.gods.nl/~forge/kenneyw.key --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
