[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
[dash-dev] Re: Build questions
|
Ingo Muschenetz wrote:
A few questions:
1) How should org.mozilla.rhino be handled? I notice it's not packaged
with org.eclipse.eclipsemonkey-feature, and it's also not listed as a
dependency.
Not listed as a dependency? Oops, that's an error. Can you fix that?
2) I've noticed there are a few more plugins in CVS than in the rmap
file. Should those also be part of the build, especially a feature
specifically for Rhino?
Some of them are older/broken previous attempts at various things. I
think the current set of plug-ins in the feature are the correct current
set. I guess we could just delete the old plug-ins from CVS.
3) I've made a simple build file using the PDE build method. I started
down the initial path of doing it the manual way, but ran into a number
of issues whereby it became somewhat difficult to deal with an
automatically generated plugin version, such as 0.1.9.xxxxxx. This will
build the feature, but I have not added JAR signing or Pack200 yet.
Basically, this relies on a few small configuration settings:
a) location of Eclipse install on machine
b) location of org.eclipse.pde.build plugin
c) output location for generated site.xml and plugins/features
Id be happy to package up what I have and send it along with notes on
how to configure it, or if you let me know a bit more about the build
process itself, I can configure it ready to go.
So we really should be doing on build.eclipse.org. Right now Ward and I
are doing the builds on our local G5 Mac OS X machine. On the
build.eclipse.org machine (as soon as you get your committer account),
you can install a copy of Eclipse in your local account and thus put (a)
and (b) where ever you want. Currently (c) is at
/home/data/httpd/download.eclipse.org/technology/dash/update
- Bjorn
