Hi Adolfo,
Perhaps
I misunderstand your problem, but for some of the bundles
you mention the source just doesn’t exist in Orbit CVS and
thus also not in the Orbit repo. I know for sure that sat4j
doesn’t have source, for instance, and for log4j https://bugs.eclipse.org/bugs/show_bug.cgi?id=320977
is open against Orbit.
I
agree that Orbit should be providing source wherever
possible, but sometimes it is not easy (eg in the case of
Xerces where we split the original distro into separate
bundles, see
http://wiki.eclipse.org/Orbit/Xerces_in_Eclipse
HTH,
Martin
--
Martin Oberhuber, SMTS / Product Architect – Development Tools,
Wind River
direct +43.662.457915.85 fax
+43.662.457915.6
Thomas,
I think that this is not the solution. Reading the bucky book:
"
cbi.include.source
Controls generation of source features and bundles. When set
to true, source bundles are generated
and included in the update site.
Warning:
Source features and bundles are generated and included in the
update site unless you
set this property to false. For open source projects this is
typically what is wanted,
but it may not be suitable for your project."
This doesn't seem to be the problem, our sources bundles are
successfully generated and included into the p2 repository.
The problem is that I want a third party bundle and the
corresponding source bundle from the target platform to be
included in the p2 repository. The binary bundle is included,
the source counterpart is not included.
Anyway I tried to give a chance to that property setting
explicitly to true. The result was the same.
Any other idea ?
Regards,
Adolfo.
El 01/03/2011 16:26, Thomas Hallgren escribió:
Hi Adolfo,
How do you provision your target platform? Are your source
bundles included there? If not, and if Bucky is resolving
what's put there, do you have the buckminster.download.source
property set to true?
If the source bundles are present in your TP but not in the
resulting p2 repository, perhaps you're missing the
cbi.include.source = true setting.
HTH,
Thomas Hallgren
On 2011-03-01 15:53, Adolfo Sánchez-Barbudo Herrera wrote:
Hi All,
Retaking this issue up. I've gathered from a Indigo M5
Modeling distribution the list of orbit bundles which doesn't
have the corresponding source bundle in said installation:
- com.google.collect
- com.google.inject
- javax.activation
- lpg.runtime.java
- org.antlr.runtime
- org.aopalliance
- org.apache.batik.*
- org.apache.common.cli
- org.apache.commons.lang
- org.apache.derby
- org.apache.log4j
- org.apache.lucene.highlighter
- org.apache.lucene.memory
- org.apache.lucene.misc
- org.apache.lucene.queries
- org.apache.lucene.spellchecker
- org.apache.ws.commons.util
- org.apache.xmlrpc
- org.h2
- org.hoksuke.args4j
- org.sat4j.core
- org.sat4j.pb
- org.w3c.*
I'm wondering why there are a lot plugins which don't have
corresponding source bundle. Probably, some of those bundles
don't need source counterpart, however it looks like there a
lot of them which should probably have their corresponding
source bundle...
Could anybody put some light on this ? Any tip/suggestion
about what to do with this absence of source bundles?
Thanks in advance,
Adolfo.
El 22/12/2010 11:13, Adolfo Sánchez-Barbudo Herrera escribió:
Hi Folks,
- Moving the question to dev-cross-project to find any Bucky
releng-er who had faced this problem -
Detailed background and information around the issue is in the
following forum's thread:
http://www.eclipse.org/forums/index.php?t=msg&th=201971&start=0&S=b19a799edb96ebdc69b900b74b0c5d91
<http://www.eclipse.org/forums/index.php?t=msg&th=201971&start=0&S=b19a799edb96ebdc69b900b74b0c5d91>
As an high level overview, I'm trying to solve the following
issue:
In our M4 Modeling Distribution the following bundle, which is
obtained from an Orbit's p2 repo, is included into the
distribution's set of plugins:
lpg.runtime.java
However, the corresponding lpg.runtime.java.source is not
included.
Have any buckminter-based releng-er faced a similar problem ?
Best Regards,
Adolfo.
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
