Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Newcomers » Newcomers » Dual Installation JavaDoc
Dual Installation JavaDoc [message #733215] Tue, 04 October 2011 15:07 Go to next message
Wojtek  is currently offline Wojtek Friend
Messages: 47
Registered: August 2011
Member
I have two instances of Eclipse installed, one for RCP and one for the
Web. Both of course point to a Java JDK. Both also point to the JavaDoc
for that JDK.

If I add a tool, or change the JDK, I need to also update the JavaDoc
location. I am planning to add an Android installation, and then I need
to keep three Eclipses up to date.

Is there a way to have all three "read" the same JavaDoc locations when
I update one? It sure would simplify things, especially as I might use
one for a month or two then go to a different one, and why can I not
see the JavaDoc, grumble, grumble.

Maybe a known directory (or one I specify) which I can point Eclipse
to, which has an XML file?

--
Wojtek :-)
Re: Dual Installation JavaDoc [message #734016 is a reply to message #733215] Thu, 06 October 2011 11:29 Go to previous messageGo to next message
Russell Bateman is currently offline Russell BatemanFriend
Messages: 3798
Registered: July 2009
Location: Provo, Utah, USA
Senior Member

On 2011.10.04 9:07, Wojtek wrote:
> I have two instances of Eclipse installed, one for RCP and one for the
> Web. Both of course point to a Java JDK. Both also point to the JavaDoc
> for that JDK.
>
> If I add a tool, or change the JDK, I need to also update the JavaDoc
> location. I am planning to add an Android installation, and then I need
> to keep three Eclipses up to date.
>
> Is there a way to have all three "read" the same JavaDoc locations when
> I update one? It sure would simplify things, especially as I might use
> one for a month or two then go to a different one, and why can I not see
> the JavaDoc, grumble, grumble.
>
> Maybe a known directory (or one I specify) which I can point Eclipse to,
> which has an XML file?

Note that you don't have to use separate Eclipse installations for all
of this; you can just use one or two. (This said, I prefer to do as you
are doing.) Sorry I don't have an answer for your question.
Re: Dual Installation JavaDoc [message #734436 is a reply to message #734016] Fri, 07 October 2011 19:03 Go to previous messageGo to next message
Eric Rizzo is currently offline Eric RizzoFriend
Messages: 3070
Registered: July 2009
Senior Member
On 10/6/11 7:29 AM, Russell Bateman wrote:
> On 2011.10.04 9:07, Wojtek wrote:
>> I have two instances of Eclipse installed, one for RCP and one for the
>> Web. Both of course point to a Java JDK. Both also point to the JavaDoc
>> for that JDK.
>>
>> If I add a tool, or change the JDK, I need to also update the JavaDoc
>> location. I am planning to add an Android installation, and then I need
>> to keep three Eclipses up to date.

I'm not sure why this is a manual process. I never set a Javadoc
location, just point Eclipse at my JDK installation (with src.jar) and
it automatically finds what it needs.

By the way, that information is stored in the workspace, so it doesn't
really matter how many installations of Eclipse you use, it depends on
how many different workspaces you use.

Eric
Re: Dual Installation JavaDoc [message #734633 is a reply to message #734436] Sun, 09 October 2011 00:07 Go to previous messageGo to next message
Wojtek  is currently offline Wojtek Friend
Messages: 47
Registered: August 2011
Member
Eric Rizzo wrote :
> On 10/6/11 7:29 AM, Russell Bateman wrote:
>> On 2011.10.04 9:07, Wojtek wrote:
>>> I have two instances of Eclipse installed, one for RCP and one for the
>>> Web. Both of course point to a Java JDK. Both also point to the JavaDoc
>>> for that JDK.
>>>
>>> If I add a tool, or change the JDK, I need to also update the JavaDoc
>>> location. I am planning to add an Android installation, and then I need
>>> to keep three Eclipses up to date.
>
> By the way, that information is stored in the workspace, so it doesn't really
> matter how many installations of Eclipse you use, it depends on how many
> different workspaces you use.

And of course I use a separate workspace for each installation. Just to
keep things separate.

If I were to put in an enhancement request, what would I put it under?
I always have the hardest time trying to figure out what component I
want, and usually I pick the wrong one and the bug gets moved.

--
Wojtek :-)
Re: Dual Installation JavaDoc [message #734961 is a reply to message #734633] Mon, 10 October 2011 14:27 Go to previous messageGo to next message
David Wegener is currently offline David WegenerFriend
Messages: 1445
Registered: July 2009
Senior Member
The JavaDoc from source is automatically associated with a JDK when you install the source along with the JDK. When you create a new Workspace, Eclipse will automatically pick it up. You should not need to define it manually.
Re: Dual Installation JavaDoc [message #735093 is a reply to message #734961] Mon, 10 October 2011 21:42 Go to previous messageGo to next message
Wojtek  is currently offline Wojtek Friend
Messages: 47
Registered: August 2011
Member
dpwegener wrote :
> The JavaDoc from source is automatically associated with a JDK when you
> install the source along with the JDK. When you create a new Workspace,
> Eclipse will automatically pick it up. You should not need to define it
> manually.

But if I install a library, then I need to associate the library's
JavaDoc with the .jar file.

--
Wojtek :-)
Re: Dual Installation JavaDoc [message #735329 is a reply to message #735093] Tue, 11 October 2011 14:31 Go to previous message
Eric Rizzo is currently offline Eric RizzoFriend
Messages: 3070
Registered: July 2009
Senior Member
On 10/10/11 5:42 PM, Wojtek wrote:
> dpwegener wrote :
>> The JavaDoc from source is automatically associated with a JDK when
>> you install the source along with the JDK. When you create a new
>> Workspace, Eclipse will automatically pick it up. You should not need
>> to define it manually.
>
> But if I install a library, then I need to associate the library's
> JavaDoc with the .jar file.
>

For that I usually have a "Common Libs" project that other projects
depend on. Common Libs is a plain Java project that contains the JARs
and their source attachments, with the JARs on its build path. It is
configured to export the JARs, so that any other project that depends on
Common Libs automatically gets those dependencies.
But in any case, this seems a bit away from your original description
that revolved around the JDK Javadoc.

Eric
Previous Topic:custom "new project" with libraries set
Next Topic:HTML files in runnable JAR
Goto Forum:
  


Current Time: Thu Apr 25 07:27:46 GMT 2024

Powered by FUDForum. Page generated in 0.09181 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top