For p2.Mirrors functionality and getting it added to artifacts.xml,
one can use the maven xml plugin, and the p2.xsl file linked from
here:
http://wiki.eclipse.org/Equinox/p2/p2.mirrorsURL#via_site.xml
In addition you can use the Ant tasks, and the previously antrunner
plugin from tycho to run eclispe ant tasks.
Dave
On 03/06/2012 01:56 PM, David Carver wrote:
BTW,
in case people didn't know. As of 0.14, Tycho fully supports
using p2.inf during p2 repository creation.
http://wiki.eclipse.org/Tycho/Release_Notes/0.14
Dave
On 03/06/2012 01:47 PM, David Carver wrote:
It looks like some of this stuff should be
doable using Tycho 0.14 and the Tycho P2 Extras plugin.
Included is the ability to run the various Ant Tasks provided by
eclipse.
http://wiki.eclipse.org/Tycho/Additional_Tools
Dave
On 03/06/2012 01:37 PM, Jesse McConnell wrote:
having to go to the cli to tweak this
stuff is a non-starter, i have a
mechanism leveraging that for the packing process and I
dislike that
immensely
anyway, i am already in java code and mucking with the xml
fixing
checksums and the leftovers from the packing process so
probably
easier to just add a couple of properties for these settings
and
inject them into the xml at that point
not ideal but little about the situation is so will make do
with what I have
jesse
--
jesse mcconnell
jesse.mcconnell@xxxxxxxxx
On Tue, Mar 6, 2012 at 12:10, David M Williams
<david_williams@xxxxxxxxxx> wrote:
I think your eyes glazed over reading
my original note before you got to
the part where I said there is already such a tool. See
http://wiki.eclipse.org/WTP/Releng/Tools/addRepoProperties
Feel free to use/copy that as you'd like.
The advantage of having a "stand-alone app" or tool (not
only as "part of a
build") is that is allows you to change the properties after
the repo is
created, as is sometimes required, after moving or mirroring
the repo
elsewhere.
Good luck,
From: Jesse McConnell<jesse.mcconnell@xxxxxxxxx>
To: Cross project
issues<cross-project-issues-dev@xxxxxxxxxxx>,
Date: 03/06/2012 12:38 PM
Subject: Re: [cross-project-issues-dev] p2
repositories ... we can do
better
Sent by: cross-project-issues-dev-bounces@xxxxxxxxxxx
Not sure for tycho but given some time I could have that in
the
signing plugin in an hour or so I would think.
I'll see if I can scrape some time together to get that
support added
in, at least in the interm until tycho could support it
cheers,
jesse
--
jesse mcconnell
jesse.mcconnell@xxxxxxxxx
On Tue, Mar 6, 2012 at 11:25, Marcel
Bruch<bruch@xxxxxxxxxxxxxxxxxx>
wrote:
On 06.03.2012, at 13:04, Jesse
McConnell wrote:
could the
eclipse-signing-maven-plugin provide a parameter to
inject the p2.mirrorsURL property into artifact
repositories and
parameters to generate the p2.index file ?
can you give me a specific example of what that xml
(assuming that
would be in some of the xml metadata) would look like?
= Support for p2.mirrorsURL =
According to
http://wiki.eclipse.org/Equinox/p2/p2.mirrorsURL just add:
<property name="p2.mirrorsURL" value="
http://www.eclipse.org/downloads/download.php?file=
{repository_path}&format=xml"/>
Since webmaster thinks that we have
been hit by this issue recently (
https://bugs.eclipse.org/bugs/show_bug.cgi?id=373352) this
makes me think
even more about how to integrate this into our builds. As
last means of
resort I'll write a bash script that unzips artifacs.jar,
adds the property
to the artifacts.xml, and zips the file again.
But I wonder how much effort it
takes to add this in Tycho's
eclipse-repository packaging since tycho generates these
files?
It wouldn't be specify to Eclipse;
just a generic support for properties
- I think.
= Adding support for p2.index =
The file looks like this:
version = 1
metadata.repository.factory.order =
compositeContent.xml,\!
artifact.repository.factory.order =
compositeArtifacts.xml,\!
Whether it's "xml" or "jar" should depend on the
"compress" property we
already specify in the eclipse-repository.
= Enabling download stat in your repository =
And if we are already on defining properties: to enable
download stats
it's...
...for artifacts.xml/repository:
<property name='p2.statsURI'
value='http://your.stats.server/stats'/>
...for bundles:
<property name='download.stats'
value='test.plugin1.bundle'/>
http://wiki.eclipse.org/Equinox_p2_download_stats
So, in theory it's just adding properties and looks from
outside like a
simple thing to do. But how long it takes to implement it -
at least the
p2.mirrorsURL feature - I've no idea. But maybe a tycho
committer knows
better?
I suspect is
possible but I also think it is probably more
appropriate to have that
support in tycho
the signing plugin is really just a hack to support this
aspect of the
eclipse requirements that is outside of the traditional
tycho
workflow...having said that we can always put another
hack or two into
it :)
cheers,
jesse
--
Matthias
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
Thanks,
Marcel
--
Eclipse Code Recommenders:
w www.eclipse.org/recommenders
tw www.twitter.com/marcelbruch
g+ www.gplus.to/marcelbruch
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
|
