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 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 visi
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.
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,
>
>
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
---
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 es
