Thanks Andrew and Ian,
I did double check and
made sure I use newer version of the repository, and the build id portion in
the product ID was newer.
I enabled all the P2 trace
options in the “.options” file:
org.eclipse.equinox.p2.core/debug=true
org.eclipse.equinox.p2.core/updatechecker=true
org.eclipse.equinox.p2.core/generator/parsing=true
org.eclipse.equinox.p2.core/engine/installregistry=true
org.eclipse.equinox.p2.core/metadata/parsing=true
org.eclipse.equinox.p2.core/artifacts/mirrors=true
org.eclipse.equinox.p2.core/core/parseproblems=true
org.eclipse.equinox.p2.core/planner/operands=true
org.eclipse.equinox.p2.core/planner/projector=true
org.eclipse.equinox.p2.core/engine/profilepreferences=true
org.eclipse.equinox.p2.core/publisher=true
org.eclipse.equinox.p2.core/reconciler=true
org.eclipse.equinox.p2.core/core/removeRepo=true
I see P2 pounding
the update site and produced a lot of “Unexpected attribute for element
license: url="" messages and then quietly exited without any
error.
Besides the above trace
options is there any other way I can ask P2 to produce more verbose debug
information, e.g. what it finds and what it compares with?
Thanks,
Andy
From:
p2-dev-bounces@xxxxxxxxxxx [mailto:p2-dev-bounces@xxxxxxxxxxx] On Behalf Of Andrew Niefer
Sent: Friday, October 02, 2009
1:16 PM
To: P2 developer discussions
Subject: Re: [p2-dev] update site
from the product build
The key will be that you will need your very top
level product Installable Unit, which is named based on the id in the .product
file, to increase in version between each build.
You indicate this should be happening since you're
updating the qualifier, but you can do as Ian suggests and look in the
content.xml directly to see whats there.
-Andrew
From:
|
Ian Bull
<irbull@xxxxxxxxxxxxxxxxx>
|
To:
|
P2 developer discussions
<p2-dev@xxxxxxxxxxx>
|
Date:
|
10/02/2009 12:33 PM
|
Subject:
|
Re: [p2-dev] update site from
the product build
|
Sent
by:
|
p2-dev-bounces@xxxxxxxxxxx
|
This should work exactly as you describe it (I assume your bundles also have
monotonically increasing version numbers).
If you crack open the content.xml do you see your updated IUs (that is, the
metadata corresponding to the new products / features / bundles you
built)? I wonder if you are pointing to an old version of the repository.
cheers,
ian
On Fri, Oct 2, 2009 at 9:23 AM, Andy Jin <AJin@xxxxxxx>
wrote:
I have a product build using P2 with
“p2.gathering” on. The product contains of one master feature which
contains all the other sub-features. The master feature also contains the
Eclipse platform (which contains all the P2 bundles).
The product build generates a “buildRepo” directory. In that
directory there are “binary”, “feature” and
“plugins” folder, and “content.xml” and “artifacts.xml”
file.
We have daily builds. Each build increase the build qualifier in the
product ID (e.g. 1.0.0.20090930 to 1.0.0.20091001). The main features and
sub-features also has build qualifier increased daily.
I run build 1.0.0.20090930 and add a new update site URL pointing to the
“buildRepo” from build 1.0.0.20091001. However when I run
“Check for update” I get “There is nothing to update”
message.
Is there anything wrong with my config? Can I use the
“buildRepo” directly as update site?
Thanks,
Andy
_______________________________________________
p2-dev mailing list
p2-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/p2-dev
--
R. Ian Bull | EclipseSource Victoria
| +1 250 477 7484
http://eclipsesource.com
| http://twitter.com/eclipsesource_______________________________________________
p2-dev mailing list
p2-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/p2-dev