Upcoming project proposal
Marcus Hirt
marcus.hirt at oracle.com
Tue Mar 13 19:30:42 UTC 2018
Hi Volker,
That is correct. ;) JMC will have its own versioning precisely since it will
work with multiple versions of the JDK. And "working with" is a tad complicated
as it can mean multiple things (runtime dependency, ability to handle JFR
file formats and JDK version specific JFR content etc).
The intent is that:
* The core components will run _on_ JDK 7u40 and above.
* The core components will be able to handle JFR recordings from the
OracleJDK 7u40 and above, and OpenJDK 11 and above.
* The "application" will require JDK 8 or above to run.
* The JFR part of the "application" will be able to handle the same kinds of
flight recordings as the core components (OracleJDK 7u40 and above,
OpenJDK 11 and above).
* The "application" should be able to "connect" to running JVMs 7u40 and
above.
Hope this helps!
Kind regards,
Marcus
On 2018-03-13, 19:51, "Volker Simonis" <volker.simonis at gmail.com> wrote:
Hi Marcus,
thanks for the detailed answers. My question was not so much about
distributions / binary releases, but more about the relation (i.e.
compatibility) with the OpenJDK.
From my current understanding, JMC will be a stand-alone project with
its own repository and release cycle, correct?
What versions of OpenJDK will JCM support? I.e. will there be a
specific JMC version for every JDK release (you know, that happens
quite often nowadays - every six month :)
Or will the JMC have its own, independent release cycle with every new
version of JMC supporting a reasonable range of available OpenJDK
releases?
Thanks,
Volker
On Tue, Mar 13, 2018 at 7:00 PM, Marcus Hirt <marcus.hirt at oracle.com> wrote:
> I should probably expand a bit on #3. So here are the current plans for making
> binary builds of JMC available:
>
> * We're looking at making the core parts (includes the JFR-file-version
> independent JFR parser, the automated analysis of JFR Recordings and
> more) available on Maven Central.
>
> * The stand-alone (RCP) version of JMC will either be bundled as part of the
> Oracle JDK 11, or provided as a separate download with an embedded JRE.
>
> * We also plan on hosting an Eclipse plug-in version of JMC like before.
> The only difference will be that all plug-ins (including experimental
> ones) will be hosted on the same update site, making them easier to
> download from Eclipse marketplace.
>
> I cannot promise that this is exactly what will happen, but this is what we
> are currently working towards.
>
> Kind regards,
> Marcus
>
> On 2018-03-13, 18:46, "Marcus Hirt" <marcus.hirt at oracle.com> wrote:
>
> Hi Volker,
>
> Thanks for the kind words!
>
> 1. JFR will be open sourced as part of an OpenJDK JEP.
>
> 2. Yes. You can, for example, use the JMX console and the JOverflow
> heap waste analysis tooling (http://hirt.se/blog/?p=854), to mention
> two of the tools available. That said, JFR is being open sourced too.
>
> 3. You will be able to very easily build JMC from source using Maven.
> Oracle will very likely build and ship JMC in a binary form, but I
> don't think distribution commitments should be part of the project
> proposal.
>
> Kind regards,
> Marcus
>
>
> On 2018-03-13, 18:33, "Volker Simonis" <volker.simonis at gmail.com> wrote:
>
> Hi Marcus,
>
> great to see this finally happening!
>
> I have some questions though :)
>
> 1. Your proposal mentions JFR several times. Will the JFR
> functionality be open sourced as part of and within the new "Mission
> Control Project" or will it be done within another project (or maybe
> as a separate JEP).
>
> 2. Can JMC be used without JFR being available in the OpenJDK?
>
> 3. Will JMC become a part of the regular OpenJDK (i.e. will it be
> build together with the OpenJDK and be part of a normal OpenJDK
> images/distribution) or will JMC will be stand-alone project with
> different release cycles. Could you please write some words about this
> in your final project proposal?
>
> Thanks a lot for making this possible and good look with the remaining steps,
> Volker
>
>
> On Tue, Mar 13, 2018 at 6:13 PM, Marcus Hirt <marcus.hirt at oracle.com> wrote:
> > Hi all,
> >
> > I’m currently in the process of finalizing a project proposal for open
> > sourcing JDK Mission Control (formerly known as Java Mission Control).
> > Please let me know if you have any thoughts or concerns!
> >
> > Here is a draft of the proposal:
> > ---8<---
> > I hereby propose the creation of the Mission Control Project with myself
> > (Marcus Hirt) as the Lead and the HotSpot Group as the sponsoring Group.
> >
> > In accordance with the OpenJDK guidelines [1], this project will provide a
> > home for the continued development of the JDK Mission Control suite of tools,
> > also known as JMC. JMC is a profiling and diagnostics tools suite for the JVM,
> > primarily targeting systems running in production. JMC also provides
> > independent bundles for parsing Java flight recordings, headless analysis of
> > Java flight recordings, and more.
> >
> > We are now open-sourcing JMC to help keep the JVM-based languages in the
> > absolute forefront in terms of production time profiling and diagnostics.
> >
> > Open sourcing the core libraries of JMC enables the Java ecosystem to quickly
> > take advantage of features currently in the process of being open sourced in
> > the JVM, such as the Java Flight Recorder (JFR), across all contemporary
> > versions of Java.
> >
> > Open sourcing the stand alone JMC application will provide the community with
> > a base suite of tooling for advanced JVM features, such as Java Flight
> > Recorder. It will also provide the community with an opportunity to build upon
> > this tooling to, for example, expand the number of IDEs supported, not to
> > mention provide new features and capabilities.
> >
> > I (Marcus Hirt) am a member of the Java Platform Group at Oracle, and I have
> > been working with Java and JVM technology since the early days of Java. I was
> > one of the founders of Appeal Virtual Machines, and the original team leader
> > of Java Mission Control.
> >
> > Many people have made significant contributions to Java Mission Control.
> > Special thanks go out to Klara Ward, Erik Gahlin and Markus Persson who
> > have been around for most of the journey.
> >
> > The initial Reviewers and Committers will be:
> >
> > * Marcus Hirt (Reviewer)
> > * Klara Ward (Reviewer)
> > * Ola Westin (Reviewer)
> > * Henrik Dafgård (Reviewer)
> > * Per Kroon (Reviewer)
> > * Erik Greijus (Reviewer)
> > * Erik Gahlin (Reviewer)
> > * Guru Hb (Committer)
> > * Suchita Chaturvedi (Committer)
> > * Sharath Ballal (Committer)
> >
> > The initial source of this project will be based on the development branch of
> > Mission Control 7. The final development and stabilization of Mission Control 7
> > will take place in the open. Change review policy will be determined by the
> > Lead and a consensus of Reviewers. Review is expected to be relaxed initially,
> > but made more strict as we get closer to the first release.
> >
> > The project will host at least the following mailing list:
> >
> > * jmc-dev for developers
> >
> > Votes are due by 23:59 CET on <day of week>, <month> <day>, 2018.
> >
> > Only current OpenJDK Members [1] are eligible to vote on this motion.
> > Votes must be cast in the open on the discuss list. Replying to this
> > message is sufficient if your mail program honors the Reply-To header.
> >
> > For Lazy Consensus voting instructions, see [2].
> >
> > Kind regards,
> > Marcus Hirt
> >
> > [1] http://openjdk.java.net/census#members
> > [2] http://openjdk.java.net/projects/#new-project-vote
> > ---8<---
> >
> > We’ve been working on the open sourcing for a while now, and if nothing
> > unexpected happens, I plan on posting the project proposal within 6 weeks.
> > Again, please let me know if you have any concerns! Friendly letters of
> > encouragement are welcome too; open sourcing something that has been part
> > of a commercial offering for more than a decade is a bit painful. ;)
> >
> > Kind regards,
> > Marcus
> >
> >
>
>
>
>
>
>
More information about the discuss
mailing list