| How to use multiple p2 repos in a pdebuild? [message #538915] |
Wed, 09 June 2010 05:39  |
Eclipse User |
|
|
|
Originally posted by: wbeckwith.gmail.com
My situation is that I have a target composed of the eclipse RCP runtime
+ the delta pack and another directory of 3rd party dependencies. We
can add the dependencies directory to the pluginPath variable and all
will compile down fine. However, when the ant task p2.mirror executes,
it only sees the repo at the target. The dependencies repo is not taken
into context.
I figure there might be ant properties that maybe go into the builder's
build.properties file that may instruct the build file generation to
create another <source> element that points to the 2nd dependencies
repo. If there is, or there is a better of structure this outside of
dumping everything into the same directory, please let me know.
Wb
|
|
|
|
| Re: How to use multiple p2 repos in a pdebuild? [message #539230 is a reply to message #539083] |
Thu, 10 June 2010 06:06  |
| Eclipse User |
|
|
|
Originally posted by: wbeckwith.gmail.com
That was what I needed. Now p2.mirror can see the dependencies repo.
One final (ATM) question, but the mirror process seems to resolved all
bundles into the product install. There are some bundles I need in my
target platform for compilation which are provided via Import-Package
but we can't ship the actual bundles themselves. How do I keep these
guys from being included?
Wb
On 6/9/2010 10:17 AM, Andrew Niefer wrote:
> You want "p2.context.repos" which should be a comma separated list of URIs.
>
> Somewhat related are:
> "repoBaseLocation" - a folder containing other repositories in zips or
> subfolders. These repositories will be transformed using repo2runnable.
> "transformedRepoLocation" - the location of the repository where the
> results of the repoBaseLocation transformation should go.
>
> "transformedRepoLocation" is automatically added to the list of context
> repositories with p2.context.repos.
>
> -Andrew
>
> Wendell Beckwith wrote:
>
>> My situation is that I have a target composed of the eclipse RCP runtime
>> + the delta pack and another directory of 3rd party dependencies. We
>> can add the dependencies directory to the pluginPath variable and all
>> will compile down fine. However, when the ant task p2.mirror executes,
>> it only sees the repo at the target. The dependencies repo is not taken
>> into context.
>>
>> I figure there might be ant properties that maybe go into the builder's
>> build.properties file that may instruct the build file generation to
>> create another<source> element that points to the 2nd dependencies
>> repo. If there is, or there is a better of structure this outside of
>> dumping everything into the same directory, please let me know.
>>
>> Wb
>
|
|
|
|
|
| Re: How to use multiple p2 repos in a pdebuild? [message #605973 is a reply to message #539083] |
Thu, 10 June 2010 06:06 |
| Eclipse User |
|
|
|
Originally posted by: wbeckwith.gmail.com
That was what I needed. Now p2.mirror can see the dependencies repo.
One final (ATM) question, but the mirror process seems to resolved all
bundles into the product install. There are some bundles I need in my
target platform for compilation which are provided via Import-Package
but we can't ship the actual bundles themselves. How do I keep these
guys from being included?
Wb
On 6/9/2010 10:17 AM, Andrew Niefer wrote:
> You want "p2.context.repos" which should be a comma separated list of URIs.
>
> Somewhat related are:
> "repoBaseLocation" - a folder containing other repositories in zips or
> subfolders. These repositories will be transformed using repo2runnable.
> "transformedRepoLocation" - the location of the repository where the
> results of the repoBaseLocation transformation should go.
>
> "transformedRepoLocation" is automatically added to the list of context
> repositories with p2.context.repos.
>
> -Andrew
>
> Wendell Beckwith wrote:
>
>> My situation is that I have a target composed of the eclipse RCP runtime
>> + the delta pack and another directory of 3rd party dependencies. We
>> can add the dependencies directory to the pluginPath variable and all
>> will compile down fine. However, when the ant task p2.mirror executes,
>> it only sees the repo at the target. The dependencies repo is not taken
>> into context.
>>
>> I figure there might be ant properties that maybe go into the builder's
>> build.properties file that may instruct the build file generation to
>> create another<source> element that points to the 2nd dependencies
>> repo. If there is, or there is a better of structure this outside of
>> dumping everything into the same directory, please let me know.
>>
>> Wb
>
|
|
|
|
Powered by
FUDForum. Page generated in 0.03719 seconds
] 
Search
Help
Register
Login
Home
