Hi David,
Am 02.02.2012 23:17, schrieb David M Williams:
> In the types of cases I mentioned, such as if a bundle depended on
> org.mortbay.jetty.server, then a build (or, test, I'd think) would fail on
> Juno and but succeed on Indigo and would require some type of change
> (perhaps different str
I've increased the executors to 6 until we can resolve the issues with
the new slaves. That should help clear things up.
Denis
On 02/02/2012 07:44 PM, Matthias Sohn wrote:
Currently there is a huge queue of 17 Hudson build jobs waiting for an
executor thread.
It seems only 2 threads are used.
Currently there is a huge queue of 17 Hudson build jobs waiting for an
executor thread.
It seems only 2 threads are used. Could someone having the license kick
Hudson to
use more threads ?
--
Matthias
___
cross-project-issues-dev mailing list
cross-proj
Well, good point, and maybe that's how these other projects do it ... and
its successfulness I guess depends on how good your tests are ... but, if
it was me I'd try building against Indigo specifically, and then building
against Juno specifically to make sure there were no compile time breakages
I am not sure I understand what you recommend. Using m2e as an example.
Our goal is to maintain compatibility with at least one previous Eclipse
release. The version we ship with Juno is expected to install and wort
on Indigo. So we build m2e against Indigo and then test with both Indigo
and Juno.
M5 is not even out the door and problems already known about M6
aggregation! ... how's that for early warning? :)
See bug 370405 [1] for details (and feel free to comment there) but by a
series of bugs, coincidence, and my own missteps, our Juno aggregation
repository still "points to" an old In
License feature support is coming in soon to be released Tycho 0.14...
assuming I properly understood how it is supposed to work, of course.
I'd appreciate if somebody tried current Tycho 0.14.0-SNAPSHOT and
provided feedback in the bugzilla or on tycho-dev mailing list.
https://bugs.eclipse.org/
Thank you so much, Greg, for explaining how this happened. Sounds like
something everyone should be aware of ... one difference between PDE build
and Tycho build that they'd have to plan for if switching.
Do you (or others?) know if there is a feature request open for this
function in Tycho? I wo
The missing files are because I had to manually revert from the shared license
feature (which is not supported by Tycho) when we switched our build to
Hudson/Maven, and I forgot to add them to the build.properties. They are
actually in the repo. Will be fixed for RC3.
Greg
On Feb 1, 2012, at 1
