Skip to main content
Attendees
- Andrew Niefer
- DJ Houghton
- Eric Li
- Matt Flaherty
- Mcq
- Oleg Besedin
- Pascal Rapicault
- Simon Kaegi
- Tim Mok
- Tom Watson
Minutes
Jetty5 vs Jetty6
- Jetty5 is currently shipped in the SDK
- Jetty5 relies on old APIs
- people are installing new APIs
- suddenly help doesn't work
- happens, for instance, with WTP
- could we use version ranges?
- how much work is to upgrade to Jetty6?
- too much
- short term solution is to hack Jetty5 to say it runs on the new APIs
- Simon to contact the Jetty folks to see if this is a reasonable solution
- what SWT does (for Mac for instance) is they say they only run on the newest versions
OSGi
- Tom doing OSGi specification work
- there are some great discussions happening on the e4 mailing list
- we should be having similar discussions surrounding OSGi
- perhaps the meeting next week should be blue sky ideas around the runtime?
eclipse.home
- there is discussion around a new Location variable
- p2 would like to know the location to initialize the dropins
- currently it is treated as a sibling of the configuration folder
- this can't be the story going forward
- we should have a page which lists all our locations and what they mean
Security
- Eric and Tim have been working with Scott to get SSH working within ECF
- things are looking good and we believe we have a story for this
Password Command-Line Arg
- in M6 we introduced eclipse.password command-line arg which takes a password
- would like to change it to take a file which contains the password
- this is considered an API change so we need to ask permission to change it
- is this arg a URL or file location? need to explicitly spec this
- a consistent story for URLs and Files might be a good e4 topic
Back to the top