geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "John D. Ament" <johndam...@apache.org>
Subject Re: [DRAFT] Announcement for Geronimo Config release
Date Sun, 17 Sep 2017 14:02:07 GMT
So then how does this look?  If no objections, I'll send out towards the
end of my day.

-----

The Apache Geronimo community is happy to announce the first release of
Apache Geronimo Config, 1.0!  This is the first release of the MicroProfile
Config compatible library here at Apache, as well as being the first
release of a MicroProfile component specification implementation here at
Apache!

Geronimo Config adds support for basic configuration nomenclatures based on
the MicroProfile Config specification.  Out of the box, it allows you to
work with system properties, classpath property files, as well as
environment variables within your Java based applications.  In addition to
the specification, Geronimo Config provides a few extension points to ease
integration into your application stack:

  - SPI for reading additional property files
  - Automatic conversion of environment variables into Java property
standard syntax
  - Support for Java 8 Supplier types

We're still working on some website details, but you can still get the code
a few ways:

- Download via Apache Mirrors:
http://www.apache.org/dyn/closer.cgi/geronimo/config/geronimo-config-1.0-source-release.zip
- SVN Tag:
https://svn.apache.org/repos/asf/geronimo/components/config/tags/geronimo-config-1.0/
- As well as Maven repository:
http://search.maven.org/remotecontent?filepath=org/apache/geronimo/config/geronimo-config/1.0/geronimo-config-1.0-source-release.zip

Since it's built using Maven, you can directly add it to your existing
project to get started,

<dependency>
     <groupId>org.apache.geronimo.config</groupId>
     <artifactId>geronimo-config-impl</artifactId>
     <version>1.0</version>
</dependency>

Cheers!

John D. Ament
On behalf of the Geronimo PMC



On Sun, Sep 17, 2017 at 9:50 AM Romain Manni-Bucau <rmannibucau@gmail.com>
wrote:

> +1
>
>
> Romain Manni-Bucau
> @rmannibucau <https://twitter.com/rmannibucau> |  Blog
> <https://blog-rmannibucau.rhcloud.com> | Old Blog
> <http://rmannibucau.wordpress.com> | Github
> <https://github.com/rmannibucau> | LinkedIn
> <https://www.linkedin.com/in/rmannibucau> | JavaEE Factory
> <https://javaeefactory-rmannibucau.rhcloud.com>
>
> 2017-09-17 9:37 GMT+02:00 David Blevins <david.blevins@gmail.com>:
>
>> How about "MicroProfile component specification" ?
>>
>> "first implementation of a MicroProfile component specification here at
>> Apache"
>>
>> --
>> David Blevins
>> http://twitter.com/dblevins
>> http://www.tomitribe.com
>>
>> On Sep 16, 2017, at 11:06 PM, Romain Manni-Bucau <rmannibucau@gmail.com>
>> wrote:
>>
>> "MP specific specification"? MP 1.0 not being anything special (just
>> referencing EE without bringing more consistency or features) it can work
>> and be less ambiguous than "subcomponent" which means not much to me, wdyt?
>>
>> Le 17 sept. 2017 05:05, "David Blevins" <david.blevins@gmail.com> a
>> écrit :
>>
>>> On Sep 15, 2017, at 5:43 PM, John D. Ament <johndament@apache.org>
>>> wrote:
>>>
>>>
>>>
>>> On Fri, Sep 15, 2017 at 2:36 PM David Blevins <david.blevins@gmail.com>
>>> wrote:
>>>
>>>> On Sep 14, 2017, at 3:54 AM, John D. Ament <johndament@apache.org>
>>>> wrote:
>>>>
>>>> as well as being the first release of a MicroProfile specification
>>>> implementation here at Apache
>>>>
>>>>
>>>> Note TomEE is the first MP implementation at Apache.  We intentionally
>>>> defined MP 1.0 as a subset of the WebProfile so all servers were by default
>>>> MP compatible.  TomEE, WildFly, Payara and Liberty were all used in the MP
>>>> 1.0 Conference demo and initial presentations.
>>>>
>>>>
>>> Sure, are you asking me to rephrase it? I'm referring to the individual
>>> components, rather than the overall MicroProfile umbrella.
>>>
>>>
>>> Yeah, maybe use "first implementation of a MicroProfile sub-component
>>> here at Apache" or something similar.
>>>
>>> MP 1.0, 1.1 are all MicroProfile specifications as well, so someone with
>>> that perspective will read "MicroProfile specification implementation"
>>> differently than intended.
>>>
>>>
>>> -David
>>>
>>>
>>>
>>>
>>
>

Mime
View raw message