[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [p2-dev] creating artifact repo from arbitrary files
- From: Pascal Rapicault <pascal.rapicault@xxxxxxxxxxxx>
- Date: Thu, 28 Nov 2013 15:41:12 +0000
- Accept-language: en-CA, en-US
- Delivered-to: firstname.lastname@example.org
- Thread-index: AQHO7EpcVtNSvhZkGEmHp2Ycqp7ZxZo6xsbw
- Thread-topic: [p2-dev] creating artifact repo from arbitrary files
Depending on the content of partial profiles, it may get complicated to get them integrated in the real profile
I would rely on shipping artifacts.jar that can be used by the profile generating mechanism and I would do the same for metadata repo with a content.jar.
If you want we can try to have a voice chat about the approach you are taking,
From: p2-dev-bounces@xxxxxxxxxxx [mailto:p2-dev-bounces@xxxxxxxxxxx] On Behalf Of Krzysztof Daniel
Sent: November-28-13 9:58 AM
Subject: [p2-dev] creating artifact repo from arbitrary files
I've found a problem when trying to install things loaded from a custom *.info file into a base profile - P2 requires metadata (which I generate from a running platform) and artifact repository, connected with an artifact key. The point is that I don't have any artifact repository connected with the *.info files, hence my question: what is more appropriate to do - create repositories on the fly (is that even
possible) or ship entire repos?
I like the speed of shipping partial profiles, as there is no startup overhead unless dropins are engaged on startup, but shipping repos has its pros and cons - writing second dropins-like mechanism (tracking repo changes etc etc) seems to be a bit overkill.
Krzysztof Daniel <kdaniel@xxxxxxxxxx>
p2-dev mailing list