jesse DOT glick AT oracle DOT com
Features I am working on or investigating
- Extracting XML and SOA
- Experimentation with starting NB IDE over JNLP
Evaluate problems with Mercurial as applied to netbeans.org sources, record in HgBugs as needed, file in upstream bug tracker, offer patches where possible.
Use the latest Hg releases to get early notification of serious regressions.
Fix bugs (and evaluate pull requests) in Mercurial plugin, publish releases, get them installed.
Restart server when apparently hung / leaking.
Review golden file diffs sent to email@example.com. last diff
Review samples posted by Geertjan.
Evaluate test failures, esp. in nbms-and-javadoc.
Add @RandomlyFails to unstable unit tests.
NB Platform + Maven
Review contents of NB Maven repo when new releases are published, and dev repo as needed. Try making an NBM app using the staging repo and the new version, testing specifically:
- *.nbm and *.jar both present
- external libraries linked to in Maven Central where a match exists, rather than dumped in org.netbeans.external
- org.netbeans.libs.junit and other special modules correctly handled (i.e. are in right cluster group even though not part of regular Platform download)
- *-sources.jar, *-javadoc.jar secondary artifacts present and usable from IDE
- OSGi bundles in ide cluster functional (e.g. app including Mylyn can start and make a Bugzilla connection)
Integrate new Ant and Maven releases as they appear.
E.g. convert layer.xml registrations to annotations.
Reassign random issues that get filed in the apisupport "product" for no clear reason except that it is alphabetically first.
Run IDE on latest Linux & JDK releases. Among other things, report memory leaks (esp. ProjectManager.ProjectStateImpl instances live in heap even when all projects and files are closed).
Serve as Oracle contact. See Javeleon.
Moderate some lesser mailing lists: broken_builds, api-changes, reviewers, javeleon@apisupport, issues@contrib, commits@ide, etc. (How to get a complete list?)