RE: Using Maven as Eclipse class-path container
Kenney Westerhof wrote on Tuesday, November 08, 2005 9:25 AM: > On Tue, 8 Nov 2005, [iso-8859-1] Jörg Schaible wrote: > >>> A problem might be that eclipse >>> doesn't have the concept of scopes for its dependencies. >> >> It has. You can define dependencies to be "exported". >> > > Isn't that on by default? And does that provide for 'test' > dependencies not being visible in the main sources? And for > 'runtime' dependencies not being visible in main/test sources, but > only runtime? OK. I have to redefine my statement. You can explicitly export your dependencies, but your source folders are unfortunately always exported (unfortunately). This forces test cases always into the classpath of the child projects :( - Jörg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Using Maven as Eclipse class-path container
On Tue, 8 Nov 2005, [iso-8859-1] Jörg Schaible wrote: > > A problem might be that eclipse > > doesn't have the concept of scopes for its dependencies. > > It has. You can define dependencies to be "exported". > Isn't that on by default? And does that provide for 'test' dependencies not being visible in the main sources? And for 'runtime' dependencies not being visible in main/test sources, but only runtime? Btw I think that the maven2 plugin for eclipse will provide this support. It's not public yet and in the early stages of development. -- Kenney > - Jörg > > - > 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]
RE: Using Maven as Eclipse class-path container
Marcel Schutte wrote on Tuesday, November 08, 2005 8:48 AM: > Sounds like a good idea. I think the eclipse plugin works > only in the opposite direction, generating .classpath etc > files for eclipse to use. A problem might be that eclipse > doesn't have the concept of scopes for its dependencies. It has. You can define dependencies to be "exported". - Jörg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Using Maven as Eclipse class-path container
Sounds like a good idea. I think the eclipse plugin works only in the opposite direction, generating .classpath etc files for eclipse to use. A problem might be that eclipse doesn't have the concept of scopes for its dependencies. Marcel --- Michael Böckling <[EMAIL PROTECTED]> wrote: > Hi, > > I'd like to know if there is, or if there are any plans to create, an > > Eclipse plugin that cann add a Maven2 class-path container to a > project, > so there is a way to use the Maven artifact resolver (adding > dependencies automatically to the Eclipse classpath) inside Eclipse. > This would be especially useful for transitive depencies... > The idea for this stems from the Necessitas Ivy plugin for Eclipse: > http://kevin.oneill.id.au/2005/06/06/necessitas-jar-management-for-eclipse > > Are there any informations about this topic? Maybe the soon-to-be > released M2 Eclipse plugin > (http://jira.codehaus.org/secure/BrowseProject.jspa?id=11093) can do > this? > > Thanks, > Michael Böckling > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > __ Yahoo! Mail - PC Magazine Editors' Choice 2005 http://mail.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Using Maven as Eclipse class-path container
On 11/8/05, Michael Böckling <[EMAIL PROTECTED]> wrote: > Are there any informations about this topic? Maybe the soon-to-be > released M2 Eclipse plugin > (http://jira.codehaus.org/secure/BrowseProject.jspa?id=11093) can do this? Correct, and more. - Brett - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
