|
| Re: How to build Riena from source? [message #585943 is a reply to message #585898] |
Tue, 22 June 2010 12:18   |
 Christian Campo
Messages: 597
Registered: July 2009 |
Senior Member |
|
|
Am 21.06.10 00:20, schrieb Christian Kesselheim:
> Me again,
>
> I wonder what's the best way to build the whole of Riena (target
> platform components) from source?! I've imported the Team Project Set
> file bundled with org.eclipse.riena.releng, but still see a lot of
> errors and unsolved dependencies.
>
> For example, what's the target platform definition I need to use? I
> suppose the one that comes with org.eclipse.riena.ui.templates should
> suffice for building the toolset component at least, but since it
> complains about a number of unresolved installable units when opened I
> also wonder whether or not its still being actively maintained.
>
> Also, why are there 3 different plug-ins starting in
> org.eclipse.riena.build*? Which one's currently being used?
>
> Any hints for me where to start looking? Is there perhaps some magic
> Wiki page on building Riena from source that I managed to miss so far :)?
>
> Thanks in advance,
>
> Chris
>
>
Hi Chris,
If you like to have Riena in your workspace you need to installed Equinox SDK and RCP SDK into a new target platform and
activate that target platform. You can easily do that using the Helios repo and that should be it.
That is true for the Riena runtime pieces.
You need a second workspace to deal with the Riena toolbox. The target platform there is just the IDE and there is a
seperate releng for the toolbox o.e.r.toolbox.releng.
When you install the Riena Toolbox one of the benefits is that a .target file that is anywhere within the plugins is
offered to become a new target. So say you have that installed as an IDE plugin, you can easily activate the definition
in o.e.r.ui.templates called riena_2.0.0.target which is the target definition for creating Riena-based applications.
Building Riena in a build process is a little tricky and we were fighting with our build since the beginning. Elias now
helped us create a build project org.eclipse.riena.build3 that finally does it all. So build and build2 are just
previous attempts to build Riena.
However the build only runs on windows and need to have a set of files and a certain directory structure that we havnt
come around to describe anywhere. If you like to have your own build running as a headless build, I think a good first
step would be to open a bug and push us to describe that directory structure for you :-)
regards
christian
|
|
|
| Re: How to build Riena from source? [message #585953 is a reply to message #585898] |
Tue, 22 June 2010 12:51 |
Christian Kesselheim
Messages: 59
Registered: June 2010 |
Member |
|
|
Thanks a lot, that really helped. Since we're planning on using Riena for our next RCP solution (and I guess there will come the time when we'll want to do our own patches and bug-fixes), I'm currently thinking about setting-up a private nightly build of Riena on our company's own Hudson server. So perhaps I'll have to file that "describe your directory structure" bug request you've mentioned after all :).
So far, my main source of confusion stems from the fact that importing the Riena Team Project Set from CVS doesn't seem to produce an error-free workspace configuration, at least not for me.
For example:
1. org.sl4j.* is missing while org.apache.log4j is not. Since org.sl4j.log4j also contains its own version of log4j (and is installed in the Riena target platform by default), the compiler seems so get confused and prefers the (outdated) target platform log4j over the one I have locally checked-out. As a result, recent changes in log4j (e.g. Category.setLevel) will not be visible and produce a problem marker in org.eclipse.riena.core. Checking out a fresh org.sl4j.* from Orbit CVS makes the problem go away, so I wonder if this should not be included in the team project set by default.
2. Bundles like org.eclipse.riena.exceptionmanager and org.eclipse.riena.workspace have broken imports (e.g. ServiceInjector) or dependencies (e.g. dependency on org.eclipse.riena.ui.core missing), so I wonder if these bundles are actively maintained/required at this point in time.
3. Bundles like org.eclipse.riena.ui.tests or org.eclipse.riena.security.services.config don't compile at all for me (source directory/class reference missing).
As soon as I get this working for me (and my Hudson) I might publish the results as part of some blog, so you can review and laugh at my rookie mistakes :).
|
|
|
| Re: How to build Riena from source? [message #585965 is a reply to message #585898] |
Wed, 23 June 2010 12:15 |
Christian Kesselheim
Messages: 59
Registered: June 2010 |
Member |
|
|
Argh, my mistake indeed. At some point I decided to create a GIT mirror of the Riena CVS repository and then clone & serve my sandbox from there. I then simply forgot to "filter" projects again (against the project set) when re-importing them into Eclipse.
Building my target platform by hand instead of using a physical target definition file (effectively by-passing the P2 Planner here) also makes the sl4j vs. log4j confusion go away.
I'm always surprised by the somewhat disproportional complexity of Eclipse topics like provisioning (P2) and head-less build (PDE Build, Buckminster, Tycho, etc.) when compared to some of the more runtime-oriented concepts, such as basic RCP UI, branding, help system or even Riena.
Anyway, thanks (again!) for your kind help and suggestions. It's deeply appreciated :).
Cheers,
Chris
|
|
|
| Re: How to build Riena from source? [message #585974 is a reply to message #585965] |
Wed, 23 June 2010 12:54 |
Christian Campo
Messages: 597
Registered: July 2009 |
Senior Member |
|
|
Am 23.06.10 14:15, schrieb Christian Kesselheim:
> Argh, my mistake indeed. At some point I decided to create a GIT mirror
> of the Riena CVS repository and then clone & serve my sandbox from
> there. I then simply forgot to "filter" projects again (against the
> project set) when re-importing them into Eclipse.
>
> Building my target platform by hand instead of using a physical target
> definition file (effectively by-passing the P2 Planner here) also makes
> the sl4j vs. log4j confusion go away.
>
> I'm always surprised by the somewhat disproportional complexity of
> Eclipse topics like provisioning (P2) and head-less build (PDE Build,
> Buckminster, Tycho, etc.) when compared to some of the more
> runtime-oriented concepts, such as basic RCP UI, branding, help system
> or even Riena.
>
> Anyway, thanks (again!) for your kind help and suggestions. It's deeply
> appreciated :).
>
> Cheers,
>
> Chris
>
>
>
>
>
>
>
>
I am sure you did not create your own Git mirror from CVS but knew :-) that the Eclipse foundation is actually already
doing that for all Eclipse projects providing a readonly Git repo as listed here http://dev.eclipse.org/git/index.html
So Riena is in a pretty up-to-date version right here git://dev.eclipse.org/org.eclipse.riena/org.eclipse.riena.gi t
Again that wouldnt help you with sorting out the redundant projects.....maybe now that the release is over, I will take
the time and ask the webmaster to delete those projects.
christian
|
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.47536 seconds
] 
Search
Help
Register
Login
Home
