Ideally, all the project tests should be executed - using dependencies from
the simultaneous release repository.
Also, some checks of the compiled classes should be made (e.g. load them
all?), to verify that dependencies in the repository are compatible with
those used at compile time.
Regards,
On 07/04/2013 11:52 AM, Alexey Panchenko wrote:
Ideally, all the project tests should be executed - using dependencies
from the simultaneous release repository.
Projects are free to execute their tests on output of aggregated repo.
The process is technically accessible to any plugin developer:
Hi
On 04/07/2013 10:52, Alexey Panchenko wrote:
Ideally, all the project tests should be executed - using dependencies
from the simultaneous release repository.
NO. Most project tests are to do with project functionality and so
should be guaranteed passes on an aggregation. Dependencies on
The aggregation tests need only focus on overall integration whereby P2
compromises what is available leading to a completely missing bundle.
p2 will never decide to *not* install a bundle just to get the rest to
install... Do you have a scenario where this happen?
The remediation is about
On 07/04/2013 12:34 PM, Pascal Rapicault wrote:
What you seem to suggest is that a project higher up the stack test
against the base. I think that by construct this is true bearing the
change of version of the base.
Not exactly, what I'm suggesting is that a project run test against *all
I don't think this is a workable approach.
First, such a test needs to run on all supported platform and jvm
combinations, which makes already involved task pretty much impossible
to perform, at least for small dev teams like we have in m2e.
Second, this won't actually find interoperability
Or, we could test packages the old-fashioned way -- by actively getting
our community involved and excited about the developer builds. This
means Tweeting, blogging, announcing and selling the cool new features
that go into the new releases.
It's a lot of work, but I'm willing to bet that a
Denis,
It may be unrelated, but slow response times appear to be occurring again. Am
attempting to ssh to build.eclipse.org, and login response is slow and terminal
periodically freezes. sometimes for up to a minute.
Eric
On 03/07/2013 1:16 PM, Denis Roy wrote:
Our ISP has located the
