|Source vs. binaries vs. docs/javadocs [message #561422]
||Sat, 02 September 2006 02:53
| Philippe Ombredanne
Registered: July 2009
A topic I did not see addressed so far is that of source code for provided|
There is no standard way suggested by OSGi for that afaik .
There is a standard way offered by PDE for that.
Keeping the sources accessible is *important* imho.
Being able to build from source can be important too.
Providing ways for sources and javadocs that can contribute to their parent
jar's Eclipse classpath entries is also nice for consumers.
Given the large number of bundles that already exists and the even larger
number of jars that Orbit could provide access to, this is a serious issue
For instance, I find it very unreliable over time to rely on a jar provider
to consistenly provide over time a proper source for a jar, or an accessible
SVN/CVS repo (do not even think that the repo will be tagged properly).
I save religiously the source and docs of every jar I use, even when it
comes from a reputable provider.
This is a duanting task for a developer.
It is wild out there.
Note that this will be important for linux distros that recompile from
I do not have an answer.
Just another 2 cents ( I must on a roll with yet another post today).
philippe ombredanne | nexB
1 650 799 0949 | pombredanne at nexb.com
Powered by FUDForum
. Page generated in 0.01961 seconds