Nicolas,

I have opened IVYDE-166 with a (hopefully) reproducible test case in the ticket.

Nicolas Lalevée wrote:
On jeudi 12 février 2009 20:11:38 Dmitriy Korobskiy wrote:
Nicolas,

this is very strange. If Javadoc is attached, it should work in all
these 3 places: tooltip, Javadoc view and Shift+F2.
I'd not suspect Jadclipse. I'm using Jadclipse as well, BTW. However,
you never know...

I wasn't able to reopen IVYDE-55:
https://issues.apache.org/jira/browse/IVYDE-55. I left a comment with
all details there.

Could somebody with the right privileges please reopen it? It is not
resolved in beta1.

I think you should open an new jira issue. The underlying real issue might not be related to what has been fixed with IVYDE-55.

Nicolas


Nicolas Lalevée wrote:
On mercredi 11 février 2009 20:47:56 Dmitriy Korobskiy wrote:
Nicolas,

you can easily check whether source or Javadoc attachment happened:

- expand Ivy container and find the main artifact JAR
- right-click to Properties (or Alt-Enter)
- see whether the source zip is attached or not
- see if Javadoc location specifies "Javadoc in archive"

I do see Javadocs attachments working in my IDE. Make sure that your JAR
with attached Javadoc comes first in the Build classpath order.
When sources *or* Javadocs are attached, Eclipse makes use of it in the
following places:

1. Tooltip - hover over a library method

2. Javadoc view. If neither source nor Javadoc is attached, you'd see a
message:
/Note: This element neither has attached source nor attached Javadoc and
hence no Javadoc could be found./

When Javadocs are attached, you can also use them in :
3. Shift+F2 - browse external Javadoc which is very handy.
Something weired in happening in my Eclipse. In both my simple project
and my Ivy project I got the javadoc attached but not the sources. And
for both project:
* in the tooltip: no javadoc or source
* in the javadoc view: no javadoc or source
* Shift+F2 : works like a charm for both...

I think I cannot help you further with your issue, my Eclipse seems
fracked up (maybe because of JadClipse ?).

Nicolas

Nicolas Lalevée wrote:
On mardi 10 février 2009 21:01:01 Dmitriy Korobskiy wrote:
Hi, all

I have a slightly different issue - IvyDE is downloading sources, but
Javadocs do not work for the life of me.
I had that issue a year and a half ago with IvyDE 1.2, and it seems
now as a resurgence of closed IvyDE-55:
https://issues.apache.org/jira/browse/IVYDE-55.

I'm using Eclipse 3.4.1 platform (IBM RAD 7.5.1 distribution) and
IvyDE 2.0.0.beta1. The difference with your, Gael, configuration from
what I understood could be that I declare all artifacts explicitly in
ivy.xml.

Here are the steps.
1. ivy.xml
<?xml version="1.0"?>
<?xml version="1.0"?>
<ivy-module version="2.0"
  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:noNamespaceSchemaLocation="http://ant.apache.org/ivy/schemas/ivy.x
sd "> <info organisation="xxx" module="mmm" status="integration" />
<configurations>
    <conf name="compile" />
    <conf name="war" /> <!-- Artifacts to be included in a WAR -->
    <conf name="ide" extends="compile" description="+ Javadocs and
sources" />
  </configurations>
  <dependencies defaultconf="compile,war->default;ide->ide(default)">
    <dependency org="apache" name="commons-logging" rev="1.1"/>
  </dependencies>
</ivy-module>

2. Repository files:
{repository}\apache\commons-logging\commons-logging-1.1\commons-loggin
g- 1.1 -doc.zip
{repository}\apache\commons-logging\commons-logging-1.1\commons-loggin
g- 1.1 -src.zip
{repository}\apache\commons-logging\commons-logging-1.1\commons-loggin
g- 1.1 .jar

3. commons-logging-1.1-ivy.xml
<?xml version="1.0"?>
<?xml-stylesheet type="text/xsl"
href="http://ivyrep.jayasoft.org/ivy-doc.xsl";?>
<ivy-module version="2.0"
  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:noNamespaceSchemaLocation="http://ant.apache.org/ivy/schemas/ivy.x
sd "> <info organisation="apache" module="commons-logging"
revision="1.1" status="release"/>
  <configurations>
    <conf name="default"/>
    <conf name="ide" extends="default" description="JavaDoc and
sources"/> </configurations>
  <publications>
    <artifact name="commons-logging-1.1" type="jar" conf="default"/>
    <artifact name="commons-logging-1.1-src" type="source" ext="zip"
conf="ide"/>
    <artifact name="commons-logging-1.1-doc" type="javadoc" ext="zip"
conf="ide"/>
  </publications>
</ivy-module>

I get commons-logging-1.1.jar with an attached source, but not
Javadocs.
I have some similar configuration to yours. Looking into the properties
of the jar in the IvyDE container, they look good. But me too the
javadoc view tells me that nothing is attached.
I then setup an non-Ivy project, with a jar and some attached javadoc.
Eclipse tells me that it looks good ("Validate..." button). But the
javadoc view still tell me that nothing is attached... Am I missing
something here ? Could you try to setup some simple non-Ivy project and
tells me if it works ? And if it works post your .classpath ?

Nicolas



Nicolas

Marziou, Gael wrote:
I think you are hitting this issue:
https://issues.apache.org/jira/browse/IVYDE-146
Merci Nicolas, the description matches indeed.

But in this case I don't understand why I still have the issue with
trunk build #20 IvyDE-updatesite on Hudson server, this fix is
supposed to be included.

Gael



--
DK AIM: DKroot1, Skype: DKroot

Reply via email to