Hi Laurent
On 19/01/2012 08:04, Laurent Goubet wrote:
I mentionned it as an aside, but this is aggravated by the fact we
cannot build on master and are thus tied down to slave1. I'll need to
try again now, but I am pretty sure I'll stumble once again on the bug
Adolfo and I hit for our builds
Just tested anew ... and the build failed with the same error it had in
august :
https://hudson.eclipse.org/hudson/view/Modeling/job/m2t-acceleo-master/124/console
failed with the single message
Required plug-in 'org.eclipse.jdt.junit4.runtime' could not be found.
I might be missing
Ed,
I'll try and get in touch with Adolfo to see if he remembers doing
anything on that matter.
Laurent Goubet
Obeo
On 19/01/2012 09:11, Ed Willink wrote:
Hi Laurent
On 19/01/2012 08:04, Laurent Goubet wrote:
I mentionned it as an aside, but this is aggravated by the fact we
cannot build
Hi,
we (the Graphiti project) are using the same GEF update site for our Juno
version, also the Juno aggregation points there.
I checked the filesystem, the folder is gone, instead there is a folder
update-site/milestones and a updates-pre-3_8/milestones. Does anybody know what
the correct
Hi Michael,
we could solve our issue by just dropping this location. Buckminster is able to
resolve the bundle without it.
I still stick with Indigo though...
-Henrik
Am 19.01.2012 10:57, schrieb Wenz, Michael:
Hi,
we (the Graphiti project) are using the same GEF update site for our
Hi all,
after some iterations I managed to consume the maintenance repository and
created the 'RC1' EPP packages which are available for download here:
http://build.eclipse.org/technology/epp/epp_build/indigo/download/20120119-1117/
David wrote it in another mail, but I'd like to mention
Hi all,
Updating to 4.2m4 as my SDK for development, I'm finding myself swamped with
tons of new errors such that I can't compile my code any more.
I do see some value in reporting issues such as version constraints in
require-bundle, but ...
- Some messages do not seem appropriate
Martin, this may be caused by new PDE tooling, not 4.2...what was the
environment you were using before the switch ?
Do you get the same errors when using 3.8M4 ?
Note that we only modify the org.eclipse.ui.workbench bundle (effectively)
so there should be no way for us to introduce compile
Hi Martin
Do you only want to develop using 4.2 as your IDE or do you also want your
code be based on 4.2 i.e. use 4.2 as target platform? If the former, I
suspect that your target platform is wrong (4.2 instead of 3.x).
For instance, I?d expect a quickfix ?convert this error into a warning?
I suggest entering a bug against PDE and we can track it down from there.
According to Curtis the default severity for missing versions is ignore
and this hasn't changed in Juno. I quickly checked these settings in
latest 4.2 build and I also see them as ignore. It could be something
peculiar
10 matches
Mail list logo
