Thank you for the reply. I'm finally getting back to this problem after
getting sidetracked yet again. I'm not really getting anywhere, unfortunately.
I'm by no means a build expert/release engineer of any sort, so please bear
with me.
We don't use CVS at all, so for me, the gef example fails saying "[build] [eclipse.fetch] Could not retrieve feature.xml and/or build.properties: java.io.IOException:
The Eclipse SDK comes with a CVS client built-in; you can use that to
fetch the GEF sources into your workspace, then build against the local
sources (if you don't want the build to do the cvs fetch for you).
It's recommended that you start with a working build because then you
have examples of well-crafted plugins and features, including correct
syntax in MANIFEST.MF, feature.xml, build.properties, etc.
Cannot run program "cvs" (in directory "C:\tmp\build\N200910221443\eclipse\tempFeature"): CreateProcess error=2, The system cannot find the file specified.".
I'm not sure installing and configuring CVS is a good use of my time, just to make an example work.
That translates to "you need to install Cygwin for a linux-friendly
build to work on Windows; while installing Cygwin, be sure to include
the cvs client so that the program 'cvs' can be found."
If you don't want to go down the CVS route, there are SVN-based builds
too. See
http://wiki.eclipse.org/MoDisco/Releng/How_to_Use#Building_on_Windows
But in either case, you can point Athena at your workspace and have it
build all the plugins/features it finds there using the
localSourceCheckoutDir=/path/to/workspace/or/some/cvs/tree/dump/folder
in your athena releng project's build.properties.
1. Created a feature that contains all of my plugins (3) and fragments (2), and includes my feature (which in turn also includes the 3 plugins).
2. Created an update site
2a. Added my master feature
2b. Built the site. It generated jars for the master feature, my
feature, and for each of my 5 plugins/fragments, as well as the artifacts.jar
and contents.jar.
Sounds good so far.
3. Start a clean debug instance of eclipse with none of my workspace plugins
enabled.
3a. Add the local update site
3b. Install the "all in one" feature
3c. Let Eclipse it restart itself.
Yep, that sounds good too.
My feature is listed as installed software (under Help -> About -> Installation Details), but none
of my plugins are listed in the plugin registry, nor are the GUI elements being loaded. It's also not
showing up under "Features" in the Installation Details box. I'm obviously missing something
fundamental. If in step 2a, I also add my other (non-master) feature to the update site, then in step 3b
try to install that one instead, I get the same result. What I find rather odd is that in the list of
installed software, the ID is feature.a.feature.group. Where's this "feature.group" thing
coming from? I don't get the error I was having previously any more (I think there may have been a
spurious dependency on one of my plugins in my feature), but I'm not exactly getting any further, either.
Are you plugins set to be lazily-loaded (check MANIFEST.MF)? Installing
software does not mean activating software; Eclipse will only
instantiate classes as needed so that initial workbench startup time is
calculated in minutes instead of in hours or days. :)
If you plugins contribute UI (eg., a tool bar button), they will only be
activated if the UI is visible in the current perspective. If they
contribute a view the plugins won't show in the registry until the view
is opened.
For deeper assistance re: bundle activation and start levels... and all
that fun stuff... try asking questions in #equinox-dev on freenode. See
http://wiki.eclipse.org/IRC for other channels.
--
Nick Boldt :: http://nick.divbyzero.com
Release Engineer :: Eclipse Modeling & Dash Athena
_______________________________________________
dash-dev mailing list
dash-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/dash-dev
