Requires us to have them online. Separate TODO

Create a badge to be included in a github project's REAMDE if it

• implements MicroProfile (provides MicroProfile API)
• Works with MicroProfile (uses/depends MicroProfile API)

An example of "Works with MicroProfile" is Togglz.

There could be badges for umbrella and for separate specs and for every released version. Ideally, a badge is generated and published automatically by CI during each release.

Targeted for MicroProfile 1.3.

MP-0006 Talks about some default properties that can be expected in a runtime. While the config spec talks about the Configuration API, these properties are more around MicroProfile in general.

I think we should change the style of the MP BOM to enclose the dependencies in a <dependencyManagement>...</dependencyManagement> section so that importers can select the set of dependencies they are importing.

See the discussion in this thread for the background of this issue:
https://groups.google.com/forum/#!topic/microprofile/UINnSKJBtrI

If I missed a thread on why this style was chosen, just point me to that.

Targeting the spec for MP 1.3

There are missing tags/GH release for 1.4 and 2.x

cc) @jclingan @kwsutter

Targeting for MicroProfile 1.3 (Opening on behalf of Stephen Fontes)

CDI Implementations need javax.annotation to work, so it has to be there. In addition, the JWT API will be requiring its use, we may as well add it to ensure its always present.

Possibly targeted at 1.3, perhaps later. This introduces a type safe rest client for use within MicroProfile runtimes.

Per the Initial Contribution Questionnaire process, we need to file Contribution Questionnaires for all of the 3rd party software that we are dependent on.
https://dev.eclipse.org/ipzilla/show_bug.cgi?id=12628

The Process is documented here:
https://www.eclipse.org/projects/handbook/#ip-third-party

I grepped the pom.xml files for this component and found the following dependencies... We will need to get these filed before we could release microprofile-1.1.

<dependency>
    <groupId>javax.enterprise</groupId>
    <artifactId>cdi-api</artifactId>
    <version>${cdi-version}</version>
</dependency>
<dependency>
    <groupId>javax.ws.rs</groupId>
    <artifactId>javax.ws.rs-api</artifactId>
    <version>${jaxrs-version}</version>
</dependency>
<dependency>
    <groupId>javax.json</groupId>
    <artifactId>javax.json-api</artifactId>
    <version>${jsonp-version}</version>
</dependency>
<dependency>
    <groupId>org.eclipse.microprofile.spec</groupId>
    <artifactId>microprofile-config-api</artifactId>
    <version>${config-version}</version>
</dependency>

Need to update the pom.xml to include Config 1.2 into MicroProfile 1.3

The spec pom.xml needs some updates to properly generate the html. Currently, the html generation does not properly display the version of the spec. The pdf generation is good, we just need to update the html generation.

Here's the content of the config spec pom.xml (and the html generation looks good):

                    <execution>
                        <id>output-html</id>
                        <phase>generate-resources</phase>
                        <goals>
                            <goal>process-asciidoc</goal>
                        </goals>
                        <configuration>
                            <backend>html5</backend>
                            <attributes>
                                <revnumber>${project.version}</revnumber>
                                <revremark>${revremark}</revremark>
                                <revdate>${revisiondate}</revdate>
                            </attributes>
                        </configuration>
                    </execution>

Once we get this figured out, then we need to update the download site with the properly generated 1.3 html.

This was discussed on the opentracing gitter thread:
https://gitter.im/eclipse/microprofile-opentracing

I see in the required-apis asciidoc that it refers to "Health Metrics 1.0"... there shouldn't be "Health" in that name, nor in the corresponding section later in that page. It's just "MicroProfile Metrics 1.0"

When 1.1 was finally made available in Maven, we went with a 3 digit version numbering scheme (1.1.0) to match the announced release and spec. But, to be consistent with the other components, maybe we should change this to just the 2 digit scheme (ie. 1.2 instead of 1.2.0).

In the interim or as an alternative to #9 this issue updates the current README to be more explicit about the required usage.

The readme doc says

1.1.0-SNAPSHOT, which should be 1.1.0