Hi John,
John Casey wrote on Monday, November 14, 2005 6:09 PM:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> This is going to sound completely ugly, but what I've found
> to work best when I have multiple interrelated (ie. same
> application) projects is to create one massive eclipse
>
> From: John Casey [mailto:[EMAIL PROTECTED]
> Sent: lundi 14 novembre 2005 18:09
> To: Maven Developers List
> Subject: Re: making behaviour of ide plugins consistent
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> This is going to sound completely ugly, but wh
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
This is going to sound completely ugly, but what I've found to work best
when I have multiple interrelated (ie. same application) projects is to
create one massive eclipse project with all the subprojects' source
roots mapped as src dirs, all the reso
btw the same project interdependecies resolution is done in mevenide for
netbeans (both for m1 and m2)
since that one is an IDE plugin, not maven plugin, it allows to dynamically
change the jar/project linking on project open/close.
for example if I work on mevenide, then maven dependencies are onl
Ok.. after some thought I need to reevaluate my opinion on this.
I have now played a little with the eclipse plugin, and well.. i must
admit that i like the way it behaves. So using project references for
projects in the same reactor build where the version of the project in
the reactor, and the v
My mistake
You are right Mark. So it seems like the eclipse plugin does it alot
like what Brett are describing.. But again.. this is to automagically
for me ;)
On 14/11/05, Mark Hobson <[EMAIL PROTECTED]> wrote:
> The eclipse plugin *does* create different project files depending on
> where it's
The eclipse plugin *does* create different project files depending on
where it's run. It uses project references if the other projects are
within the reactor build. It's also very particular regarding
versions, as this thread details:
http://www.nabble.com/eclipse%3Aeclipse-and-direct-project-re
Well, no..
I think that what you are describing is somewhat to magical for me ;)
You say that the idea plugin creates different projects depending on
where you run the command, i personally finds that very confusing. In
my opinion a plugin after configured in the module pom (or a parent)
should beh
Yes, I definitely agree with that. This discussion should be about the
default, but be configurable.
So, you say the eclipse plugin does well - is it the same or different
to the idea plugin as I described it?
- Brett
Kaare Nilsen wrote:
Then supply good default behaviour (where i really do
In my opinion, giving the choise to the individual developer would be
the best solution.
When plugins tries to get "too smart" they often fail, and a lot of
discussions appear. It should not be the responsibility of the plugin
writer to tell people how they must manage their IDE's projects.
Rather
Hi,
Can we discuss how to make the ide plugins behave consistently? It
appears that, in particular, there are a lot of discussions about
Eclipse and direct project references, and as I'm not a user I don't
really follow them - but I'm concerned that they might be arriving at a
different solut
11 matches
Mail list logo
