No. My reports don't get near that sophisticated! I'm not even sure how I'd
approach it ... there must be some way using aggregator + p2 + URL
connection tests, but ... it would take a week or two to program it (3 or
4 weeks for me :)
This is part of the reason why we stopped automatically disco
Hi David
I get some irritations from bad Update Site URLs; possibly because
project A references project B and fails to track a rationalization
of project B. Is it possible for one of your magic reports to detect
bad Update Site URLs?
Regards
Great, thanks.
Greg
On May 25, 2012, at 5:39 PM, David M Williams wrote:
> 3.
>
> I'm not sure where documented either, but the general advice, I've heard, and
> agree with, is for _products_ to include update sites but not features. So,
> EPP Java EE I know likes to include some for webtools
3.
I'm not sure where documented either, but the general advice, I've heard,
and agree with, is for _products_ to include update sites but not features.
So, EPP Java EE I know likes to include some for webtools, mylyn, others?
And its makes sense for them as a "product" as it usually would for ot
Hi all,
I recall a discussion a while ago about update site URLs but I don't seem to be
able to find the reference. So, a couple of questions:
1. Should we be providing update site URLs in our feature.xml files?
2. If so, do they need to be in every feature.xml, or only the "main" features?
3.
Ok, we're using 0.13 so we should be ok.
Thanks,
Greg
On May 25, 2012, at 2:45 PM, Igor Fedorenko wrote:
> Tycho 0.13 and newer generate optional/non-greedy p2 requirements, which
> I believe is the new behaviour.
>
>
> --
> Regards,
> Igor
>
> On 12-05-25 2:19 PM, Greg Watson wrote:
>> Marti
Tycho 0.13 and newer generate optional/non-greedy p2 requirements, which
I believe is the new behaviour.
--
Regards,
Igor
On 12-05-25 2:19 PM, Greg Watson wrote:
Martin,
Many thanks for this.
Sorry if this is a dumb question, but how do we know what publisher
we're using? We're using maven/t
Martin,
Many thanks for this.
Sorry if this is a dumb question, but how do we know what publisher we're
using? We're using maven/tycho for our builds.
Thanks
Greg
On May 25, 2012, at 11:30 AM, Oberhuber, Martin wrote:
> Hi all,
>
> Here is a very quick and easy way for any project contribu
> Means, using the new p2 publisher is obligatory and greedy=false is
> not obligatory.
> If the old behaviour is desired, i.e. an optional dependency
> shall be satisfied during installation whenever possible, the
> dependency can be annotated with an additional
> directive:resolution:=optional;x-
Actually this one is for Olivier Thomann, who is currently using 3.8 and
hunts me down every time it tries to upgrade him to 4.2 ;)
John
David M Williams
Sent by: cross-project-issues-dev-boun...@eclipse.org
05/25/2012 01:23 PM
Please respond to
Cross project issues
To
Cross project issu
What John wants, John gets :)
I'll reverse the logic and say if someone needs it, they'll have to speak
up. For now, I'll remove the M7 tie-in (but leave the "sub repo" there on
disk, if someone really needs it).
Thanks,
From: John Arthorne
To: Cross project issues ,
Date: 05/25/20
The main problem I am aware of is that the M7 build had incorrect p2
metadata causing it to offer upgrading from 3.8 to 4.2 M7. This is
annoying for those with a need to stay on 3.x, some of whom have been
personally pestering me about fixing it... so from my perspective we could
remove M7 but
Hi all,
Here is a very quick and easy way for any project contributing to Juno to see
whether their contribution has any unwanted “greedy default optional”
contributions:
cd /your/contribution/repo
unzip -p content.jar | grep optional=.true | grep -v greedy
This shows whether YOU are declaring
Most EPP packages are now available from
http://www.eclipse.org/downloads/index-developer.php, the remaining
packages will be made available as soon as their package maintainer sent a
'go'.
Thanks,
Markus
On Fri, May 25, 2012 at 3:33 PM, David M Williams wrote:
> I have "flipped the switch" for
I have "flipped the switch" for Juno software repository so it now contains
RC1 content, along with the previous M7 content.
http://download.eclipse.org/releases/juno/
I haven't officially tested RC1 and M7 "coexistence compatibility", but am
assuming its close enough not to cause problems, an
Thank you for your briefly response, David.
>
> Obligatory. To be in common repo. From
> http://wiki.eclipse.org/SimRel/Simultaneous_Release_Requirements#OSGi_bundle_format
>
>
> Clarification on 02/01/2012: the repositories produced and contributed must
> use p2 publishers that produce greedy=
16 matches
Mail list logo
