[ANNOUNCE] Apache Geronimo Config 1.0 Release!

[John D. Ament]

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,


 org.apache.geronimo.config
 geronimo-config-impl
 1.0


Cheers!

John D. Ament
On behalf of the Geronimo PMC

Re: [DRAFT] Announcement for Geronimo Config release

[Romain Manni-Bucau]

works for me

about the theme: do you have some idea? we can just grab a bootstrap one
(just need to check the license). Staying blue sounds good to me but we can
move to something else if we have a good reason.


Romain Manni-Bucau
@rmannibucau  |  Blog
 | Old Blog
 | Github  |
LinkedIn  | JavaEE Factory


2017-09-17 16:02 GMT+02:00 John D. Ament :

> 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,
>
> 
>  org.apache.geronimo.config
>  geronimo-config-impl
>  1.0
> 
>
> Cheers!
>
> John D. Ament
> On behalf of the Geronimo PMC
>
>
>
> On Sun, Sep 17, 2017 at 9:50 AM Romain Manni-Bucau 
> wrote:
>
>> +1
>>
>>
>> Romain Manni-Bucau
>> @rmannibucau  |  Blog
>>  | Old Blog
>>  | Github
>>  | LinkedIn
>>  | JavaEE Factory
>> 
>>
>> 2017-09-17 9:37 GMT+02:00 David Blevins :
>>
>>> 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 
>>> 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"  a
>>> écrit :
>>>
 On Sep 15, 2017, at 5:43 PM, John D. Ament 
 wrote:



 On Fri, Sep 15, 2017 at 2:36 PM David Blevins 
 wrote:

> On Sep 14, 2017, at 3:54 AM, John D. Ament 
> 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




>>>
>>

Re: [DRAFT] Announcement for Geronimo Config release

[John D. Ament]

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,


 org.apache.geronimo.config
 geronimo-config-impl
 1.0


Cheers!

John D. Ament
On behalf of the Geronimo PMC



On Sun, Sep 17, 2017 at 9:50 AM Romain Manni-Bucau 
wrote:

> +1
>
>
> Romain Manni-Bucau
> @rmannibucau  |  Blog
>  | Old Blog
>  | Github
>  | LinkedIn
>  | JavaEE Factory
> 
>
> 2017-09-17 9:37 GMT+02:00 David Blevins :
>
>> 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 
>> 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"  a
>> écrit :
>>
>>> On Sep 15, 2017, at 5:43 PM, John D. Ament 
>>> wrote:
>>>
>>>
>>>
>>> On Fri, Sep 15, 2017 at 2:36 PM David Blevins 
>>> wrote:
>>>
 On Sep 14, 2017, at 3:54 AM, John D. Ament 
 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
>>>
>>>
>>>
>>>
>>
>

Re: [DRAFT] Announcement for Geronimo Config release

[John D. Ament]

We need to get a theme together for the website.

On Sat, Sep 16, 2017 at 3:08 AM Romain Manni-Bucau 
wrote:

> Not sure what you refer too but can have a few cycles tomorrow to help if
> clarified ;).
>
> Le 16 sept. 2017 02:44, "John D. Ament"  a écrit :
>
>>
>>
>> On Thu, Sep 14, 2017 at 7:06 AM Romain Manni-Bucau 
>> wrote:
>>
>>> Overall +1 (and a big thank you for doing that)
>>>
>>> The small (not blocking at all) "?" I have is if we should wait for the
>>> website or not to be there. Depends the energy we have to do it I guess
>>>
>>
>> I'm a few weeks out from finishing the website.  I do plan to get config
>> up and running in the next few days, but need help with things like
>> skinning.  Maybe you could apply some of the magic from the TomEE website
>> here? :-)
>>
>>
>>
>>>
>>>
>>> Romain Manni-Bucau
>>> @rmannibucau  |  Blog
>>>  | Old Blog
>>>  | Github
>>>  | LinkedIn
>>>  | JavaEE Factory
>>> 
>>>
>>> 2017-09-14 12:54 GMT+02:00 John D. Ament :
>>>
 Hi All,

 I think it'll be good if we send an announcement to dev@, user@ as
 well as announce@a.o indicating we release Geronimo Config 1.0.  I've
 drafted something below.  Thoughts?

 

 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 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,

 
 org.apache.geronimo.config
 geronimo-config-impl
 1.0
 

 Cheers!

 John D. Ament
 On behalf of the Geronimo PMC

>>>
>>>

Re: [DRAFT] Announcement for Geronimo Config release

[Romain Manni-Bucau]

+1


Romain Manni-Bucau
@rmannibucau  |  Blog
 | Old Blog
 | Github  |
LinkedIn  | JavaEE Factory


2017-09-17 9:37 GMT+02:00 David Blevins :

> 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 
> 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"  a
> écrit :
>
>> On Sep 15, 2017, at 5:43 PM, John D. Ament  wrote:
>>
>>
>>
>> On Fri, Sep 15, 2017 at 2:36 PM David Blevins 
>> wrote:
>>
>>> On Sep 14, 2017, at 3:54 AM, John D. Ament 
>>> 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
>>
>>
>>
>>
>

Re: [DRAFT] Announcement for Geronimo Config release

[David Blevins]

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  
> 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"  > a écrit :
>> On Sep 15, 2017, at 5:43 PM, John D. Ament > > wrote:
>> 
>> 
>> 
>> On Fri, Sep 15, 2017 at 2:36 PM David Blevins > > wrote:
>>> On Sep 14, 2017, at 3:54 AM, John D. Ament >> > 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
> 
> 
> 

Re: [DRAFT] Announcement for Geronimo Config release

[Romain Manni-Bucau]

"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"  a écrit :

> On Sep 15, 2017, at 5:43 PM, John D. Ament  wrote:
>
>
>
> On Fri, Sep 15, 2017 at 2:36 PM David Blevins 
> wrote:
>
>> On Sep 14, 2017, at 3:54 AM, John D. Ament  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
>
>
>
>