Home » Eclipse Projects » P2 » set additional update sites in p2.inf(Can't get it to work - how to debug it?)
| set additional update sites in p2.inf [message #1469164] |
Tue, 11 November 2014 06:04  |
Eclipse User |
|
|
|
I am trying to set additional update sites vi p2.inf and addRepository. The generated content.xml has the touchpoint generated, but when I install my plugin the additional sites are not searched.
Is there a way to debug what's going on (normal "debug verbose" log doesn't say anyhing useful) without downloading all the source code and setting breakpoints?
best regards,
Vlad
|
|
|
| Re: set additional update sites in p2.inf [message #1469668 is a reply to message #1469164] |
Tue, 11 November 2014 15:18  |
| Eclipse User |
|
|
|
On 11/11/2014 12:04, Vlad Dumitrescu wrote:
> I am trying to set additional update sites vi p2.inf and addRepository.
> The generated content.xml has the touchpoint generated, but when I
> install my plugin the additional sites are not searched.
>
> Is there a way to debug what's going on (normal "debug verbose" log
> doesn't say anyhing useful) without downloading all the source code and
> setting breakpoints?
>
Hi
If I understand correctly what you did, those update sites will be part
of the update sites that will be available, after your features are
installed, for installing new software (or updating), but they're not
searched for when installing your features.
Hope this helps
Lorenzo
--
Lorenzo Bettini, PhD in Computer Science, DI, Univ. Torino
HOME: http://www.lorenzobettini.it
Xtext Book:
http://www.packtpub.com/implementing-domain-specific-languages-with-xtext-and-xtend/book
|
|
| | |
| Re: set additional update sites in p2.inf [message #1470764 is a reply to message #1469164] |
Wed, 12 November 2014 11:08 |
| Eclipse User |
|
|
|
The addRepository instructions added to an IU are only made available once the installation of the IU has been completed.
So imagine I have a p2 repo at http://foo.com/repo1 which contains an IU that has an instruction to add http://bar.com/repo2. When the user adds repo1 and install something from it, the repo2 will not be consulted.
For repo2 to become active, the user will have to have installed the IU. Once this is done, subsequent provisioning operations will be able to consult repo2.
In a sense, this "addRepository" action is no different than any other action like those that install a plugin, change memory settings, etc.
Now if what you want to do is have repo2 be consulted while content from repo1 is installed, then you need to use the concept of additional repositories. This can be configured through various ways, but I would recommend using the category editor included in Eclipse 4.4 and the most recent version of Tycho. Note that even though the editor support is in 4.4, the generated metadata works with older versions of p2 (e.g. Kepler and probably even before this).
HTH
|
|
| | |
| Re: set additional update sites in p2.inf [message #1476811 is a reply to message #1470764] |
Mon, 17 November 2014 06:17 |
| Eclipse User |
|
|
|
On 12/11/2014 17:08, Pascal Rapicault wrote:
> The addRepository instructions added to an IU are only made available
> once the installation of the IU has been completed.
>
> So imagine I have a p2 repo at http://foo.com/repo1 which contains an IU
> that has an instruction to add http://bar.com/repo2. When the user adds
> repo1 and install something from it, the repo2 will not be consulted.
> For repo2 to become active, the user will have to have installed the IU.
> Once this is done, subsequent provisioning operations will be able to
> consult repo2.
> In a sense, this "addRepository" action is no different than any other
> action like those that install a plugin, change memory settings, etc.
> Now if what you want to do is have repo2 be consulted while content from
> repo1 is installed, then you need to use the concept of additional
> repositories. This can be configured through various ways, but I would
> recommend using the category editor included in Eclipse 4.4 and the most
> recent version of Tycho. Note that even though the editor support is in
> 4.4, the generated metadata works with older versions of p2 (e.g. Kepler
> and probably even before this).
Pascal, I don't see such feature in 4.4... are you referring to the one
introduced in 4.5M1? https://www.eclipse.org/eclipse/news/4.5/M1/#PDE
cheers
Lore
--
Lorenzo Bettini, PhD in Computer Science, DI, Univ. Torino
HOME: http://www.lorenzobettini.it
Xtext Book:
http://www.packtpub.com/implementing-domain-specific-languages-with-xtext-and-xtend/book
|
|
|
| Re: set additional update sites in p2.inf [message #1479776 is a reply to message #1470764] |
Wed, 19 November 2014 13:23 |
| Eclipse User |
|
|
|
In case someone reads this later.
* Pascal's suggestion doesn't seem to work for older Eclipse versions, I need to support Juno...
* Using a composite repository is confusing, because my feature ends in the middle of seemingly unrelated stuff. Users should only see what's relevant for them. I couldn't find a way to "uncategorize" the content in the remote repositories.
* Additionally, my dependencies include even "incubation" projects, and these might change unexpectedly causing my code to crash... I want to have a fixed version dependency without having to edit my code whenever something changes elsewhere.
So my solution is something I didn't think it would work, but it does: I included the third-party features (part of the target platform) in my feature and it gets included very nicely in the generated update site. Neat!
regards,
Vlad
|
|
|
Goto Forum:
Current Time: Mon Jul 07 02:26:58 EDT 2025
Powered by FUDForum. Page generated in 0.11401 seconds |
Home