[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
RE: [p2-dev] RE: Metadata generator app creates metadata that causes IU installation to fail
|
I have found the apparent source of the problem: the
org.apache.ivy plugin. The version in the site at the moment is 2.0.0.cr2,
however in the plugin MANIFEST.MF seemed wrong: Bundle-Version:
2.0.0.cr2_20081028224207. I edited this to Bundle-Version: 2.0.0.cr2, reran the
metadata generator and hey presto: everything installed perfectly.
Thoughts?
Thanks,
Miles
Miles Daffin
Morgan Stanley | IDEAS PRACTICE
AREAS
20 Cabot
Square | Canary Wharf | Floor 01
London, E14 4QW
Phone: +44 20
7677-5119
Fax: +44 20 7056-4572
Miles.Daffin@xxxxxxxxxxxxxxxxx
2. I can install other IUs into my eclipse install without
error.
There are lots of differences between the 2 sets of
metadata. So many that it would be better to let it speak for itself, so I have
attached the files to this mail. Would you mind taking a look? I would be
interested to know what you think.
Thanks,
Miles
Miles Daffin
Morgan Stanley | IDEAS PRACTICE
AREAS
20 Cabot
Square | Canary Wharf | Floor 01
London, E14 4QW
Phone: +44 20
7677-5119
Fax: +44 20 7056-4572
Miles.Daffin@xxxxxxxxxxxxxxxxx
Two questions:
- Do you know if the IvyDE update site is a p2 repository
or a legacy update site?
- If you try to install IvyDE and then you try to
install something in that installation, do you get the same error?
I'm
suspecting that the problem here is with the fact that p2 does not have the
complete metadata when installing from a p2 update site.
Did you try to see
what was the difference in the two
metadata?
Thx
PaScaL
"Daffin,
Miles \(IDEAS PRACTICE AREAS\)" ---01/19/2009 01:19:14 PM---The basic point here
is that, when I mirror the IvyDE update site I get meta data that allows me
to
From: |
"Daffin, Miles \(IDEAS PRACTICE AREAS\)"
<Miles.Daffin@xxxxxxxxxxxxxxxxx> |
To: |
"P2 developer discussions"
<p2-dev@xxxxxxxxxxx> |
Date: |
01/19/2009 01:19 PM |
Subject: |
[p2-dev] RE: Metadata generator app
creates metadata that causesIUinstallation to
fail |
The basic point here is that, when
I mirror the IvyDE update site I get meta data that allows me to install the
Apache IvyDE and Apache Ivy features. If I generate metadata for the site using
the p2 metadata generator app then I get metadata that causes installation to
fail. Does anyone know why this might be and why the 2 operations result in
different metadata? Is different code being used in each case? Why do I care? Because I need
to create a large, mixed mirror based on stuff from update sites across the
planet. This one problem means that I may need to create a separate internal
repo just for IvyDE since the only way to get viable p2 meta for it is a
straight mirror. This is not very convenient.Thanks,MilesMiles Daffin
Morgan Stanley | IDEAS PRACTICE AREAS
20 Cabot Square | Canary Wharf | Floor 01
London, E14
4QW
Phone: +44 20 7677-5119
Fax: +44 20 7056-4572
Miles.Daffin@xxxxxxxxxxxxxxxxx
From:
p2-dev-bounces@xxxxxxxxxxx [mailto:p2-dev-bounces@xxxxxxxxxxx] On Behalf Of Daffin, Miles (IT)
Sent: 15 January 2009
14:52
To: P2
developer discussions
Subject: [p2-dev] RE: Metadata generator app creates metadata that causes
IUinstallation to fail
If anyone has read this message and you need more information I
will happily provide it.As a workaround I tried copying the mirrored metadata (which works
- allows me to install Apache Ivy and Apache IvyDE) into the build directory. I
then ran the metadata generator over the result in append mode hoping that it
would merely add metadata to the initial set. Unfortunately it rewrote the
sections on the Apache IUs and resulted in metadata that caused installation of
the Apache Ivy IU to fail.Thanks.Miles
From:
p2-dev-bounces@xxxxxxxxxxx [mailto:p2-dev-bounces@xxxxxxxxxxx] On Behalf Of Daffin, Miles (IT)
Sent: 13 January 2009
15:21
To:
p2-dev@xxxxxxxxxxx
Subject: [p2-dev] Metadata generator app creates metadata that causes IU
installation to fail
Hi
All,I have run into a
problem whilst trying to mirror the Apache IvyDE site. Here are the steps to
reproduce:
1. Mirror http://www.apache.org/dist/ant/ivyde/updatesite using mirror apps from 3.5M3 as per these docs: http://wiki.eclipse.org/Equinox_p2_Repository_Mirroring
2. Try installing both IUs from mirror
into vanilla 3.4.1 install: success.
3. Uninstall both IUs from 3.4.1
4.
Discard mirrored metadata and generate using the metadata
generator app (also from 3.5M3) as per these docs: http://wiki.eclipse.org/Equinox_p2_Metadata_Generator
5. Try installing both IUs from the
resulting mirror (with new metadata): install fails with the following
error:
Unsatisfied dependency: [org.apache.ivy.feature.feature.group
2.0.0.cr2] requiredCapability:
org.eclipse.equinox.p2.iu/org.apache.ivy/[2.0.0.cr2,2.0.0.cr2]
Unsatisfied
dependency: [org.apache.ivy.feature.feature.group 2.0.0.cr2]
requiredCapability:
org.eclipse.equinox.p2.iu/org.apache.ivy/[2.0.0.cr2,2.0.0.cr2]
I do not know how to interpret this error but it seems to me that
there is some kind of circularity occurring here. Does anyone have any idea what
is going wrong and where?Thanks,MilesMiles
Daffin
Morgan Stanley |
Technology
20 Cabot Square | Canary Wharf
| Floor 01
London, E14 4QW
Phone: +44 20 7677-5119
Fax: +44 20
7056-4572
Miles.Daffin@xxxxxxxxxxxxxxxxx
NOTICE: If received in error, please
destroy and notify sender. Sender does not intend to waive confidentiality or
privilege. Use of this email is prohibited when received in error.
NOTICE: If received in error, please
destroy and notify sender. Sender does not intend to waive confidentiality or
privilege. Use of this email is prohibited when received in error.
NOTICE: If received in error, please
destroy and notify sender. Sender does not intend to waive confidentiality or
privilege. Use of this email is prohibited when received in
error._______________________________________________
p2-dev
mailing list
p2-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/p2-dev
NOTICE: If received in error, please destroy and
notify sender. Sender does not intend to waive confidentiality or privilege. Use
of this email is prohibited when received in error.
NOTICE: If received in error, please destroy and notify sender. Sender does not intend to waive confidentiality or privilege. Use of this email is prohibited when received in error.
