Brian E. Fox wrote:
So I propose:
- if -DdownloadSources is specified, download sources and fallback to javadoc,
just as it is now
- if -DdownloadJavaDoc is specified, download javadoc (possibly fallback to
sources)
- if both are specified, download both.
And:
- don't make this a def
>So I propose:
>- if -DdownloadSources is specified, download sources and fallback to javadoc,
>just as it is now
>- if -DdownloadJavaDoc is specified, download javadoc (possibly fallback to
>sources)
>- if both are specified, download both.
>And:
>- don't make this a default; the default beh
Ok, if you really need both sources and javadoc then that should
be possible. I never heard of the shift-f2 but indeed it doesn't work here.
I either use the tooltip when I hover over an element and possibly f2 for focus,
or open the javadoc view which displays the javadoc as soon as I select any
On 05/07/07, Cabasson Denis <[EMAIL PROTECTED]> wrote:
Well, I kinda changed the suject of the discussion.
The matter here is whether the eclipse-plugin should be able to download "sources AND
javadoc" or only (as is the cas right now) "sources, and only javadoc as a fallback if
sources are mi
De : Jochen Wiedmann [mailto:[EMAIL PROTECTED]
> Envoyé : Thursday, July 05, 2007 11:42 AM
> À : Maven Developers List
> Objet : Re: [VOTE] Configure IDE plugins to download sources
> by default within Maven projects
>
> On 7/5/07, Cabasson Denis <[EMAIL PROTECTED]> wrote:
De : Jochen Wiedmann [mailto:[EMAIL PROTECTED]
> Envoyé : Thursday, July 05, 2007 11:42 AM
> À : Maven Developers List
> Objet : Re: [VOTE] Configure IDE plugins to download sources
> by default within Maven projects
>
> On 7/5/07, Cabasson Denis <[EMAIL PROTECTED]> wrote:
On 7/5/07, Cabasson Denis <[EMAIL PROTECTED]> wrote:
Basically, I tend to agree with you Kenney. But I have users who love to use
Shift+F2 within eclipse (which opens a browser like window with the view of the
javadoc in eclipse), and I don't really see why those users should be denied to
use
age d'origine-
> De : Kenney Westerhof [mailto:[EMAIL PROTECTED]
> Envoyé : Wednesday, July 04, 2007 3:05 PM
> À : Maven Developers List
> Objet : Re: [VOTE] Configure IDE plugins to download sources
> by default within Maven projects
>
>
>
> Cabasson Denis wrote
[EMAIL PROTECTED]
Envoyé : Tuesday, July 03, 2007 4:08 PM
À : Maven Developers List
Objet : Re: [VOTE] Configure IDE plugins to download sources
by default within Maven projects
On 03/07/07, Brett Porter <[EMAIL PROTECTED]> wrote:
+1 to Javadoc
-1 to sources (just a vote, not a veto
Downloading the non-available sources should not be slow:
Just cache in the repository (not in target which get cleaned) if the
sources of an _available_ jar are available or not.
Then lay down an extra repository law:
"Do not deploy sources on a later date after the pom has been deployed"
to m
+1
Its in my settings.xml too.
On 7/3/07, Mark Hobson <[EMAIL PROTECTED]> wrote:
Following the recent thread "Maven POM plugin config", this is a vote
to add downloadSources=true to both the eclipse and idea plugin
configurations in the maven-parent POM:
[ ] +1: I like Javadoc and easy debug
I have had second thoughts on the proposal.
To me, we are discussing something, that clearly is a user preference.
As such, it belongs into either settings.xml or profiles.xml, possibly
with activeByDefault=true. It should not enter a projects POM, if it
is used by as many people as the Maven POM
On 04/07/2007, at 12:04 AM, Jochen Wiedmann wrote:
Downloading sources (or javadocs) is an excellent thing, if the
sources (or the javadocs) are available. Unfortunately this isn't the
case in a real lot of cases. As a consequence, running the plugins can
get darned slow.
Apart from that, why
Okay, bit of a mixed bag for this vote:
+1 javadoc: Brett, Dennis, Brian, Christian, Rahul
-1 javadoc: Jochen, Stephane, Reinhard
+1 sources: Mark, Dennis, Brian, Christian
-1 sources: Brett, Jochen, Stephane, Reinhard, Rahul
It seems there's a few prerequisites to this being widely accepted:
Cabasson Denis wrote on Tuesday, July 03, 2007 4:57 PM:
> About this link, why couldn't we have a consistent behaviour
> for javadoc and sources jar?
[snip]
Because here it becomes IDE dependent. Eclipse displays Javadoc automatically
if the sources are available. No need to download Javadocs s
Same here.
+1 to Javadoc
-1 to download sources
Cheers,
Rahul
- Original Message -
From: "Brett Porter" <[EMAIL PROTECTED]>
To: "Maven Developers List"
Sent: Wednesday, July 04, 2007 1:50 AM
Subject: Re: [VOTE] Configure IDE plugins to download source
+1 for both (non binding), but the unavailability of either shouldn't
spam consoles. Small concise warnings would be sufficient, if at all.
Christian.
On Jul 3, 2007, at 9:48 AM, Mark Hobson wrote:
Following the recent thread "Maven POM plugin config", this is a vote
to add downloadSources=
Envoyé : Tuesday, July 03, 2007 5:00 PM
> À : Maven Developers List
> Objet : Re: [VOTE] Configure IDE plugins to download sources
> by default within Maven projects
>
> And make this consistent with the IDEA plugin as well.
>
> On 7/3/07, Cabasson Denis <[EMAIL PROTECTED]
to me).
But I guess it's none of the above behaviours you were looking forward to.
Denis.
> -Message d'origine-
> De : Stephane Nicoll [mailto:[EMAIL PROTECTED]
> Envoyé : Tuesday, July 03, 2007 5:00 PM
> À : Maven Developers List
> Objet : Re: [VOTE] Configure IDE plu
À : Maven Developers List
> Objet : Re: [VOTE] Configure IDE plugins to download sources
> by default within Maven projects
>
> On 03/07/07, Brett Porter <[EMAIL PROTECTED]> wrote:
> > +1 to Javadoc
> >
> > -1 to sources (just a vote, not a veto :)
>
Jochen Wiedmann wrote:
On 7/3/07, Mark Hobson <[EMAIL PROTECTED]> wrote:
Following the recent thread "Maven POM plugin config", this is a vote
to add downloadSources=true to both the eclipse and idea plugin
configurations in the maven-parent POM:
[ ] +1: I like Javadoc and easy debugging
[ ] +0
-1 (vote) in the way it's handled right now
When you have lots of dependencies, it takes way much time to generate
the project. I would go either into a FAQ explaining how to set this
up in the pluginsManagement section of a super pom.
Aligning the cache system from the eclipse plugin to the IDE
ra.codehaus.org/browse/MECLIPSE-292
Denis.
> -Message d'origine-
> De : Mark Hobson [mailto:[EMAIL PROTECTED]
> Envoyé : Tuesday, July 03, 2007 4:08 PM
> À : Maven Developers List
> Objet : Re: [VOTE] Configure IDE plugins to download sources
> by default within
e
it won't or find a way around it.
From: Mark Hobson [mailto:[EMAIL PROTECTED]
Sent: Tue 7/3/2007 9:48 AM
To: Maven Developers List
Subject: [VOTE] Configure IDE plugins to download sources by default within
Maven projects
Following the recent thread "M
On 03/07/07, Jochen Wiedmann <[EMAIL PROTECTED]> wrote:
-1 for both, although I like to have sources and javadocs attached to
Eclipse. (Non-binding)
Downloading sources (or javadocs) is an excellent thing, if the
sources (or the javadocs) are available. Unfortunately this isn't the
case in a rea
On 03/07/07, Brett Porter <[EMAIL PROTECTED]> wrote:
+1 to Javadoc
-1 to sources (just a vote, not a veto :)
In the eclipse plugin, the downloadSources flag controls them both:
http://maven.apache.org/plugins/maven-eclipse-plugin/faq.html#import-javadoc
Mark
-
On 7/3/07, Mark Hobson <[EMAIL PROTECTED]> wrote:
Following the recent thread "Maven POM plugin config", this is a vote
to add downloadSources=true to both the eclipse and idea plugin
configurations in the maven-parent POM:
[ ] +1: I like Javadoc and easy debugging
[ ] +0: I'll go with the flow
+1
Mark Hobson wrote:
Following the recent thread "Maven POM plugin config", this is a vote
to add downloadSources=true to both the eclipse and idea plugin
configurations in the maven-parent POM:
[ ] +1: I like Javadoc and easy debugging
[ ] +0: I'll go with the flow
[ ] -1: I like superfluous
+1 to Javadoc
-1 to sources (just a vote, not a veto :)
On 03/07/2007, at 11:48 PM, Mark Hobson wrote:
Following the recent thread "Maven POM plugin config", this is a vote
to add downloadSources=true to both the eclipse and idea plugin
configurations in the maven-parent POM:
[ ] +1: I like J
Following the recent thread "Maven POM plugin config", this is a vote
to add downloadSources=true to both the eclipse and idea plugin
configurations in the maven-parent POM:
[ ] +1: I like Javadoc and easy debugging
[ ] +0: I'll go with the flow
[ ] -1: I like superfluous typing, guessing Javadoc
FYI: we have the same problem with M1 plugins. We might need to consider any
solution for m1 as well.
Stéphane
On 4/1/06, Fabrizio Giustina <[EMAIL PROTECTED]> wrote:
>
> Hi,
> I recently noticed a lot of duplicated effort in order to implement
> similar things in the eclipse and idea plugins. Do
Hi,
> > I think collecting all the code used for IDE work is a good idea. But I
> > think we should try not only to collect common code for the Maven 2
> > plugins but also for the IDE extensions as much of the same code could
> > be shared.
Sure, also IDE extensions will have lots of code to sha
On 4/4/06, Jason van Zyl <[EMAIL PROTECTED]> wrote:
> Hi Fabrizio,
>
> I think collecting all the code used for IDE work is a good idea. But I
> think we should try not only to collect common code for the Maven 2
> plugins but also for the IDE extensions as much of the same code could
> be shared.
Hi Fabrizio,
I think collecting all the code used for IDE work is a good idea. But I
think we should try not only to collect common code for the Maven 2
plugins but also for the IDE extensions as much of the same code could
be shared. For example I know that Milos and Eugene have separately
a
+1. We have a shared space for these types of libraries.
I should really be doing the same thing with the JXR support code I've
been wiring in everywhere :)
- Brett
Fabrizio Giustina wrote:
> Hi,
> I recently noticed a lot of duplicated effort in order to implement
> similar things in the eclips
Hi,
I recently noticed a lot of duplicated effort in order to implement
similar things in the eclipse and idea plugins. Downloading of source
artifacts and javadocs has been reimplemented in the idea one, and I
recently took off some bits of the custom artifact resolution used in
the idea plugin an
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
eaner separation of APIs, and keeps your IDE more lined up
with your build environment...it also keeps the versions of your
dependencies up to date.
Just my 2c.
- -john
Brett Porter wrote:
| Hi,
|
| Can we discuss how to make the ide plugins behave consistently? It
| appears that, in particula
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
ob). And finally let the users
choose how they want to use it.
On 14/11/05, Brett Porter <[EMAIL PROTECTED]> wrote:
> 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
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
[ http://jira.codehaus.org/browse/MNG-1127?page=all ]
Brett Porter closed MNG-1127:
-
Resolution: Fixed
Fix Version: 2.0-beta-4
> IDE plugins get wrong path to snapshots
> ---
>
> K
[ http://jira.codehaus.org/browse/MNG-1127?page=all ]
Brett Porter reopened MNG-1127:
---
not a dupe of MNG-230
> IDE plugins get wrong path to snapshots
> ---
>
> Key: MNG-1127
>
[ http://jira.codehaus.org/browse/MNG-1127?page=comments#action_48038 ]
Mark Hobson commented on MNG-1127:
--
I think you mean MNG-230 ;)
> IDE plugins get wrong path to snapshots
> ---
>
> K
[ http://jira.codehaus.org/browse/MNG-1127?page=all ]
Brett Porter closed MNG-1127:
-
Resolution: Duplicate
Fix Version: (was: 2.0-beta-4)
is actually a duplicate of MNG-320 entirely
> IDE plugins get wrong path to snapsh
[ http://jira.codehaus.org/browse/MNG-1127?page=all ]
Brett Porter updated MNG-1127:
--
Remaining Estimate: 15 minutes
Original Estimate: 900
> IDE plugins get wrong path to snapshots
> ---
>
> K
IDE plugins get wrong path to snapshots
---
Key: MNG-1127
URL: http://jira.codehaus.org/browse/MNG-1127
Project: Maven 2
Type: Bug
Components: maven-artifact
Reporter: Brett Porter
Assigned to: Brett Porter
Fix For
This is definitely a possiblity in Maven 2.x - in fact one of the
earlier prototypes was built in a client/server fashion. However, the
more common case would be for it to be embedded as I explained earlier
so you can add your own components and listeners. If you wanted to embed
it in a small serve
:[EMAIL PROTECTED]
Sent: Friday, April 22, 2005 2:11 AM
To: Maven Developers List
Subject: Re: IDE Plugins
On 4/21/05, Inger, Matthew <[EMAIL PROTECTED]> wrote:
> Is there any plans to implement a sort of Remote API to ease development of
> plugins
> for IDE's?
>
> R
: Thursday, April 21, 2005 8:07 PM
To: Maven Developers List
Subject: Re: IDE Plugins
You're probably thinking of the IDEA plugins previously in existence? I
never got them to work for me, and attempts to contact the authors went
unanswered.
I'd endorse the MevenIDE project's work - I
ssage-
From: Milos Kleint [mailto:[EMAIL PROTECTED]
Sent: den 22 april 2005 08:11
To: Maven Developers List
Subject: Re: IDE Plugins
On 4/21/05, Inger, Matthew <[EMAIL PROTECTED]> wrote:
> Is there any plans to implement a sort of Remote API to ease
> development of plugins for
On 4/21/05, Inger, Matthew <[EMAIL PROTECTED]> wrote:
> Is there any plans to implement a sort of Remote API to ease development of
> plugins
> for IDE's?
>
> Right now, I think most IDE plugins are starting maven in console mode,
> issuing commands
> t
cally). We need some more work and testing on this, but if
anyone starts using it in this fashion it will definitely be possible.
- Brett
Inger, Matthew wrote:
>Is there any plans to implement a sort of Remote API to ease development of
>plugins
>for IDE's?
>
>Right now, I
Is there any plans to implement a sort of Remote API to ease development of
plugins
for IDE's?
Right now, I think most IDE plugins are starting maven in console mode, issuing
commands
through the processes standard in (process.getOutputStream), and reading the
results back
from the proces
60 matches
Mail list logo
