Hi Felix,
I think it is not sufficient to enable the Eclipse Maven plugin to scan
the artifact directory and seek out javadoc and sources .... at least
with my current configuration it does not work. I had to buid and
install on my local repository javadoc as secondary artifact.
Of course if you add the felix osgi .core project in your workspace you
have access to the help (I mean the automatic text completition or the
javadoc explanation of the method you are over with the mouse) But I
don't know alternative way to enable the help for the external Maven
dependencies (i.e. osgi core) linked by your POM.
How do you do?
francesco
Felix Meschberger ha scritto:
Hi Francesco,
The source files are below OSGI-OPT inside the JAR files.
Regards
Felix
Francesco Furfari schrieb:
Hello,
I wrote some days ago that osgi.core artifact deployed with
*apache.felix groupId* should have, at least, javadoc:jar artifacts to
enable help tools (e.g. enabling javadoc download in Maven prepferences)
Looking at these official artifacts they suffer of the same problem !!! :(
Who should fix it?
regards,
francesco
Alin Dreghiciu ha scritto:
FYI,
Finally the official OSGi Alliance artifacts are now in Maven Central so
there is no need of using third party repository to get access to them.
For those that already used them from
OPS4J repository there is no change in groupId/artifactId.
http://repo1.maven.org/maven2/org/osgi/org.osgi.core/
http://repo1.maven.org/maven2/org/osgi/org.osgi.compendium/
<dependency>
<groupId>org.osgi</groupId>
<artifactId>org.osgi.core</artifactId>
<version>4.1.0</version>
</dependency>
<dependency>
<groupId>org.osgi</groupId>
<artifactId>org.osgi.compendium</artifactId>
<version>4.1.0</version>
</dependency>
