Mauro Botelho wrote:
The eclipse plug in seems to check if it is running in reactor mode, and
if it is it will then accumulate sources and artifacts/dependencies to
generate a single project.
Well it apparently generates 1 eclipse project for 1 m2 project in
non-reactor mode. I'd be much surp
The eclipse plug in seems to check if it is running in reactor mode, and
if it is it will then accumulate sources and artifacts/dependencies to
generate a single project.
What I expected was that it would read the modules section of the pom
and then create a single project with all of them.
Mauro Botelho wrote:
It makes sense, but in what cases would that code be activated then?
If you run m2 eclipse in the top level directory it will successfully
generate project descriptors in level 1 subdirectories that contain Java
(jar) projects. These can be imported into an eclipse works
Sorry, I don't understand your question here?
Mauro Botelho wrote:
> It makes sense, but in what cases would that code be activated then?
>
> Mauro
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-
It makes sense, but in what cases would that code be activated then?
Mauro
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
No, you can't create a single eclipse project for all the sources. They
produce multiple jars.
- Brett
Mauro Botelho wrote:
> Does anybody have an easy way of creating a single eclipse project for
> the whole m2 code base?
>
> Looking at the source code for the eclipse plug in, it looks like it
Does anybody have an easy way of creating a single eclipse project for
the whole m2 code base?
Looking at the source code for the eclipse plug in, it looks like it
would do something like that in reactor mode, but when I do m2
eclipse:eclipse in the top level directory, I get multiple projects
