|Updated description for setting up development environment [message #671203]
||Tue, 17 May 2011 06:21
| Michel r
Registered: May 2011
I just followed the wiki page for setting up the development environment. Unfortunately, the wiki page seems to be slightly out of date. I got stuck in installing the Ecore Tools. The install wizard says, it requires org.eclipse.emf.ocl.feature.group [1.1.100,2.0.0), but cannot find it. It seems the current version of OCL is actually 3.0.2, so this is obviously the reason for the conflict.
Since the wiki page says that the Ecore Tools are optional (although recommended) I skipped this step and tried to install Xtext. I could not find a component called mwe2 in the referred update site, so I installed Xtext 1.0.2 only.
After that I imported the projects into my workspace but I got a lot of compiler errors (which was of course not a surprise for me). Most of the errors are caused by a missing package org.kohasuke.
Is the description in the Wiki outdated or am I doing something wrong? I'd really like to experiment with b3 and I would be glad if someone could help me setting up the workspace correctly.
Thank you very much,
|Re: Updated description for setting up development environment [message #671461 is a reply to message #671411]
||Wed, 18 May 2011 01:04
| Henrik Lindberg
Registered: July 2009
On 5/17/11 9:16 PM, Michel r wrote:|
> I'm interested in the build language.
> We're currently using
> PDE and want to migrate to a more modern build system. I
> know that you're currently recommending Buckminster, but I
> just wanted to have a look at what's coming next.
I hate to disappoint you, but currently (as you probably have already
figured out, the b3 build language project is quite dormant mainly due
to lack of resources).
I would naturally very much see it continue as I still think the b3
build language (when finished) offers significant value in a build process.
At the point where I left off, the b3 language, and its ability run
build processes in a generic fashion is pretty much all implemented and
works quite well. We used b3 in a project for p2 meta data publishing
and used many of the advanced features (that project is not in open
source). The b3 build language is not equipped with any specific build
capabilities at this point.
With that disclaimer, if you still want to play with it, I will be more
than happy to help you out to set things up and help make sense of what
is going on in the code.
> I cannot post the link to the wiki page with the
> instructions, because the forum says, I need at least 5
> posts in order to do that. It's something like "wiki dot
> eclipse dot org slash
I looked at the issues you reported in your first post on this topic.
And besides the issues with installing Ecoretools etc. I mainly think
that you got a mix of b3 aggregator and b3 build in your workspace.
(The instructions you found are the latest available, and they are for
the build language only). To work with the build language, you should
check out the projects named:
org.eclipse.b3 [ .backend*, .beelang*, .build*, .core ]
The dependency on org.kohasuke should afaik come from org.eclipse.b3.cli
(which is used in the headless aggregator only at this point).
So... remove all the other *b3* projects in your workspace...
I know the Xtext guys have checked out b3 on several occasions so it
should be buildable with too many strange things taking place...
You can get me more directly on irc.freenode.net - channel #b3 if you
get stuck and want to ask questions - I do have a b3 workspace set up so
not difficult to answer questions. (if you contact on irc, you may need
to type "helindbe: ping" or similar to get my attention
|Re: Updated description for setting up development environment [message #672008 is a reply to message #671819]
||Thu, 19 May 2011 14:49
| Henrik Lindberg
Registered: July 2009
On 5/19/11 7:16 AM, Michel r wrote:|
> Thanks for your help. I removed the projects related to the aggregator
> and now I have only 68 errors left :) It's really weird because it
> complains about missing classes in well known packages. For example:
> Could it be I need Indigo actually, and not Helios?
Everything was done before Indigo. That can not be the problem.
> I was wondering if you know when work on b3 build will be continued.
There are no plans to continue the development at present, and I don't
think that will change in the foreseeable future. Note that the plans we
did have included using Buckminster to perform the builds - the intent
was to not be disruptive.
> I said, we're currently using PDE build and are looking for a modern
> build system. I checked out Buckminster and Tycho. At the moment I like
> Buckminster better but I don't want to introduce a system that is not
> going to be developed further in the future. Can you say something about
Buckminster is maintained and is kept up to date with the latest in PDE,
p2, Git, SVN, etc. etc. We use Buckminster for our own builds and will
continue to do so.
Powered by FUDForum
. Page generated in 0.02467 seconds