Re: [jdt-dev] discussion about my current "Enable Classpath Cycles"proje

[Stephan Herrmann <stephan.herrmann@xxxxxxxxx>]

Re export I wrote: "exporting a feature via the Export wizard"
- more precisely:
  - use org.eclipse.jdt-feature from git 
ssh://<user>@git.eclipse.org:29418/jdt/eclipse.jdt.git
  - Export > Plug-in Development > Deployable features
    make sure org.eclipse.jdt is selected
  - if you want to export it to a different machine select "Archive file"
  - other defaults should be OK

Regarding the import: "this will normally create an update site"
- more precisely:
  - in the workhost Eclipse select Install New Software ...
    - Press Add ... > Archive ... find the file created by step 1
    - deselect [ ] Group items by category
    - follow the wizard

You may want to check the "Qualifier replacement" during export to ensure that 
you create a version that compares as greater than your current version.

HTH,
Stephan

On 27.03.20 22:38, R Steiger wrote:
> Hi Stephan,
>
> I've been testing the various options for delta transporting deltas from my jdt-master host to my workhost (where I do normal non-eclipse development), and with your take, that exporting the modified plugins as generated executable plugin jars, appears to be the easiest approach.  I haven't been able to find how to perform the last step, importing the jars, it's not an option in the Import wizard.  Suggestions?
>
> Thanks,
>
> -rjs
>
> > -----Original Message-----
> > From: Stephan Herrmann <stephan.herrmann@xxxxxxxxx>
> > Sent: Thursday, March 26, 2020 7:22 AM
> > To: R Steiger <rsteiger@xxxxxxxxxxxxxxxx>; jdt-dev@xxxxxxxxxxx
> > Subject: Re: [jdt-dev] discussion about my current "Enable Classpath
> > Cycles"project
> >
> > On 24.03.20 09:34, R Steiger wrote:
> > > The next step is to road-test these mods.  My thought is to locally build a
> > stock Eclipse IDE for Java Developers package, having the above mods, and
> > put it into daily use for a couple of weeks, using it to work on a large code-
> > base.  What’s the recipe for building the IDE?  I’d like to use the most
> > lightweight path, e.g. don’t need to create an update site, doesn’t require
> > pushing to git, etc.
> >
> > FWIW, I still believe, "lightweight" suggests exporting a feature via the Export
> > wizard. In a workspace that is fully set up for JDT development, just
> > exporting the JDT feature should be done with only a few clicks.
> >
> > Of course, this will normally create an update site -- unless you opt to install
> > into the current host Eclipse, is that an option?
> >
> > If, OTOH, you try to run a full maven build, I don't think the JDT team will be
> > able to give a lot of help, because we don't use this approach in daily
> > business.
> >
> > Maybe I misunderstood what you mean by "lightweight".
> > Easiest to produce? Use the export wizard.
> > Easiest to consume? You'd need the help of several experts in different
> > areas if you try to build your own downloadable "IDE for Java Developers",
> > i.e., an Eclipse Package.
> >
> > best,
> > Stephan