You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomee.apache.org by Romain Manni-Bucau <rm...@gmail.com> on 2012/02/01 15:29:03 UTC
update checker
An idea from JL:
should we do sthg like the update checker of ehcache?
http://grepcode.com/file/repo1.maven.org/maven2/net.sf.ehcache/ehcache-core/2.4.0/net/sf/ehcache/util/UpdateChecker.java
- Romain
Re: update checker
Posted by Romain Manni-Bucau <rm...@gmail.com>.
because it was visible.
if we manage to do it in parallel it will not be visible so nobody will
shout, no?
- Romain
2012/2/1 David Blevins <da...@gmail.com>
>
> On Feb 1, 2012, at 10:29 AM, David Blevins wrote:
>
> >
> > On Feb 1, 2012, at 10:20 AM, Romain Manni-Bucau wrote:
> >
> >> shouldn't cost anything
> >
> > My preference would be for it not being enabled by default for testing
> and for getting out of core and as a separate jar. Or at the very least a
> separate class very decoupled form Assembler/ConfigurationFactory.
>
> To add, even maven doesn't check for snapshots on every build anymore. :)
>
> People did not like it.
>
>
> -David
>
>
>
> >
> >
> > -David
> >
> >> 2012/2/1 David Blevins <da...@gmail.com>
> >>
> >>>
> >>> On Feb 1, 2012, at 10:06 AM, Romain Manni-Bucau wrote:
> >>>
> >>>> it doesn't really match,
> >>>>
> >>>> it is nice to get the info in test mode too so it should be in the
> core.
> >>>
> >>> Having it on for a test would seem to be a really bad idea. We'd be
> doing
> >>> 100+ checks per build per person on our own build alone.
> >>>
> >>>
> >>> -David
> >>>
> >>>>
> >>>> 2012/2/1 David Blevins <da...@gmail.com>
> >>>>
> >>>>>
> >>>>> On Feb 1, 2012, at 9:57 AM, Romain Manni-Bucau wrote:
> >>>>>
> >>>>>> already added a version but not as a service.
> >>>>>>
> >>>>>> it can be desactivated using configuration factory offline mode or a
> >>>>>> dedicated system property. The downloadable url and check url are
> >>>>>> configurable through system properties.
> >>>>>>
> >>>>>> I use maven (repo1) to check the latest version.
> >>>>>
> >>>>> Let's move that to a ServerService under server/openejb-updates
> >>>>>
> >>>>> That way it can easily be excluded by virtue of it simply not being
> >>>>> included in a distro. It'll get booted when the server boots,
> shutdown
> >>>>> when the server shuts down. And if we wanted to maybe someday add a
> >>> rest
> >>>>> call to see if their server is up to date (it would report the cached
> >>> value
> >>>>> from the last check) it would be really easy.
> >>>>>
> >>>>> -David
> >>>>>
> >>>>>> 2012/2/1 David Blevins <da...@gmail.com>
> >>>>>>
> >>>>>>>
> >>>>>>> On Feb 1, 2012, at 7:51 AM, Romain Manni-Bucau wrote:
> >>>>>>>
> >>>>>>>> i would like to see it activated by default.
> >>>>>>>>
> >>>>>>>> a little timeout (3s?)
> >>>>>>>>
> >>>>>>>> a thread ran in the configuration factory
> >>>>>>>> and the result get (through a future) in the assembler (to avoid
> to
> >>>>>>> wait)?
> >>>>>>>
> >>>>>>> If we did have it on by default, should definitely something really
> >>> easy
> >>>>>>> to shut off.
> >>>>>>>
> >>>>>>> This could easily be a ServerService with a file that extracts to
> >>>>>>> conf/updates.properties. Some of the config params could be the
> URL
> >>> we
> >>>>>>> check for updates and the frequency we check.
> >>>>>>>
> >>>>>>>
> >>>>>>> -David
> >>>>>>>
> >>>>>>>> 2012/2/1 David Blevins <da...@gmail.com>
> >>>>>>>>
> >>>>>>>>> This sounds like a great feature.
> >>>>>>>>>
> >>>>>>>>> My gut instinct is that maybe it should be disabled by default
> and
> >>>>>>>>> something we encourage people to enable.
> >>>>>>>>>
> >>>>>>>>> What do others think?
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>> -David
> >>>>>>>>>
> >>>>>>>>> On Feb 1, 2012, at 6:36 AM, Jean-Louis MONTEIRO wrote:
> >>>>>>>>>
> >>>>>>>>>> +1
> >>>>>>>>>> Of course if that is one of my idea.
> >>>>>>>>>> Just to argue a bit.
> >>>>>>>>>>
> >>>>>>>>>> With Apache TomEE (it was also the case before), a lot of
> companies
> >>>>> or
> >>>>>>>>>> people are using OpenEJB/TomEE in production.
> >>>>>>>>>>
> >>>>>>>>>> It would be great to have kinda Apache TomEE server, we can use
> to
> >>>>>>>>> publish
> >>>>>>>>>> important releases or security/bugfixes.
> >>>>>>>>>>
> >>>>>>>>>> During startup and if the network is available, just ping our
> >>> central
> >>>>>>>>>> server and check whereas there is an important update available.
> >>>>>>>>>>
> >>>>>>>>>> If yes, just send a message in logs or an email to the
> >>> administrator
> >>>>> to
> >>>>>>>>>> inform him about new important updates.
> >>>>>>>>>> We could imagine enhencing our current webapp installer to ask
> for
> >>>>>>>>>> administrator information such as email, smtp server or so.
> >>>>>>>>>>
> >>>>>>>>>> That was my initial thought.
> >>>>>>>>>>
> >>>>>>>>>> Jean-Louis
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>> 2012/2/1 Romain Manni-Bucau <rm...@gmail.com>
> >>>>>>>>>>
> >>>>>>>>>>> An idea from JL:
> >>>>>>>>>>>
> >>>>>>>>>>> should we do sthg like the update checker of ehcache?
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>>>
> >>>>>>>>>
> >>>>>>>
> >>>>>
> >>>
> http://grepcode.com/file/repo1.maven.org/maven2/net.sf.ehcache/ehcache-core/2.4.0/net/sf/ehcache/util/UpdateChecker.java
> >>>>>>>>>>>
> >>>>>>>>>>> - Romain
> >>>>>>>>>>>
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>
> >>>>>
> >>>
> >>>
> >
>
>
Re: update checker
Posted by David Blevins <da...@gmail.com>.
On Feb 1, 2012, at 10:29 AM, David Blevins wrote:
>
> On Feb 1, 2012, at 10:20 AM, Romain Manni-Bucau wrote:
>
>> shouldn't cost anything
>
> My preference would be for it not being enabled by default for testing and for getting out of core and as a separate jar. Or at the very least a separate class very decoupled form Assembler/ConfigurationFactory.
To add, even maven doesn't check for snapshots on every build anymore. :)
People did not like it.
-David
>
>
> -David
>
>> 2012/2/1 David Blevins <da...@gmail.com>
>>
>>>
>>> On Feb 1, 2012, at 10:06 AM, Romain Manni-Bucau wrote:
>>>
>>>> it doesn't really match,
>>>>
>>>> it is nice to get the info in test mode too so it should be in the core.
>>>
>>> Having it on for a test would seem to be a really bad idea. We'd be doing
>>> 100+ checks per build per person on our own build alone.
>>>
>>>
>>> -David
>>>
>>>>
>>>> 2012/2/1 David Blevins <da...@gmail.com>
>>>>
>>>>>
>>>>> On Feb 1, 2012, at 9:57 AM, Romain Manni-Bucau wrote:
>>>>>
>>>>>> already added a version but not as a service.
>>>>>>
>>>>>> it can be desactivated using configuration factory offline mode or a
>>>>>> dedicated system property. The downloadable url and check url are
>>>>>> configurable through system properties.
>>>>>>
>>>>>> I use maven (repo1) to check the latest version.
>>>>>
>>>>> Let's move that to a ServerService under server/openejb-updates
>>>>>
>>>>> That way it can easily be excluded by virtue of it simply not being
>>>>> included in a distro. It'll get booted when the server boots, shutdown
>>>>> when the server shuts down. And if we wanted to maybe someday add a
>>> rest
>>>>> call to see if their server is up to date (it would report the cached
>>> value
>>>>> from the last check) it would be really easy.
>>>>>
>>>>> -David
>>>>>
>>>>>> 2012/2/1 David Blevins <da...@gmail.com>
>>>>>>
>>>>>>>
>>>>>>> On Feb 1, 2012, at 7:51 AM, Romain Manni-Bucau wrote:
>>>>>>>
>>>>>>>> i would like to see it activated by default.
>>>>>>>>
>>>>>>>> a little timeout (3s?)
>>>>>>>>
>>>>>>>> a thread ran in the configuration factory
>>>>>>>> and the result get (through a future) in the assembler (to avoid to
>>>>>>> wait)?
>>>>>>>
>>>>>>> If we did have it on by default, should definitely something really
>>> easy
>>>>>>> to shut off.
>>>>>>>
>>>>>>> This could easily be a ServerService with a file that extracts to
>>>>>>> conf/updates.properties. Some of the config params could be the URL
>>> we
>>>>>>> check for updates and the frequency we check.
>>>>>>>
>>>>>>>
>>>>>>> -David
>>>>>>>
>>>>>>>> 2012/2/1 David Blevins <da...@gmail.com>
>>>>>>>>
>>>>>>>>> This sounds like a great feature.
>>>>>>>>>
>>>>>>>>> My gut instinct is that maybe it should be disabled by default and
>>>>>>>>> something we encourage people to enable.
>>>>>>>>>
>>>>>>>>> What do others think?
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> -David
>>>>>>>>>
>>>>>>>>> On Feb 1, 2012, at 6:36 AM, Jean-Louis MONTEIRO wrote:
>>>>>>>>>
>>>>>>>>>> +1
>>>>>>>>>> Of course if that is one of my idea.
>>>>>>>>>> Just to argue a bit.
>>>>>>>>>>
>>>>>>>>>> With Apache TomEE (it was also the case before), a lot of companies
>>>>> or
>>>>>>>>>> people are using OpenEJB/TomEE in production.
>>>>>>>>>>
>>>>>>>>>> It would be great to have kinda Apache TomEE server, we can use to
>>>>>>>>> publish
>>>>>>>>>> important releases or security/bugfixes.
>>>>>>>>>>
>>>>>>>>>> During startup and if the network is available, just ping our
>>> central
>>>>>>>>>> server and check whereas there is an important update available.
>>>>>>>>>>
>>>>>>>>>> If yes, just send a message in logs or an email to the
>>> administrator
>>>>> to
>>>>>>>>>> inform him about new important updates.
>>>>>>>>>> We could imagine enhencing our current webapp installer to ask for
>>>>>>>>>> administrator information such as email, smtp server or so.
>>>>>>>>>>
>>>>>>>>>> That was my initial thought.
>>>>>>>>>>
>>>>>>>>>> Jean-Louis
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> 2012/2/1 Romain Manni-Bucau <rm...@gmail.com>
>>>>>>>>>>
>>>>>>>>>>> An idea from JL:
>>>>>>>>>>>
>>>>>>>>>>> should we do sthg like the update checker of ehcache?
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>
>>>>>>>
>>>>>
>>> http://grepcode.com/file/repo1.maven.org/maven2/net.sf.ehcache/ehcache-core/2.4.0/net/sf/ehcache/util/UpdateChecker.java
>>>>>>>>>>>
>>>>>>>>>>> - Romain
>>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>
>>>>>
>>>
>>>
>
Re: update checker
Posted by David Blevins <da...@gmail.com>.
On Feb 1, 2012, at 10:20 AM, Romain Manni-Bucau wrote:
> shouldn't cost anything
My preference would be for it not being enabled by default for testing and for getting out of core and as a separate jar. Or at the very least a separate class very decoupled form Assembler/ConfigurationFactory.
-David
> 2012/2/1 David Blevins <da...@gmail.com>
>
>>
>> On Feb 1, 2012, at 10:06 AM, Romain Manni-Bucau wrote:
>>
>>> it doesn't really match,
>>>
>>> it is nice to get the info in test mode too so it should be in the core.
>>
>> Having it on for a test would seem to be a really bad idea. We'd be doing
>> 100+ checks per build per person on our own build alone.
>>
>>
>> -David
>>
>>>
>>> 2012/2/1 David Blevins <da...@gmail.com>
>>>
>>>>
>>>> On Feb 1, 2012, at 9:57 AM, Romain Manni-Bucau wrote:
>>>>
>>>>> already added a version but not as a service.
>>>>>
>>>>> it can be desactivated using configuration factory offline mode or a
>>>>> dedicated system property. The downloadable url and check url are
>>>>> configurable through system properties.
>>>>>
>>>>> I use maven (repo1) to check the latest version.
>>>>
>>>> Let's move that to a ServerService under server/openejb-updates
>>>>
>>>> That way it can easily be excluded by virtue of it simply not being
>>>> included in a distro. It'll get booted when the server boots, shutdown
>>>> when the server shuts down. And if we wanted to maybe someday add a
>> rest
>>>> call to see if their server is up to date (it would report the cached
>> value
>>>> from the last check) it would be really easy.
>>>>
>>>> -David
>>>>
>>>>> 2012/2/1 David Blevins <da...@gmail.com>
>>>>>
>>>>>>
>>>>>> On Feb 1, 2012, at 7:51 AM, Romain Manni-Bucau wrote:
>>>>>>
>>>>>>> i would like to see it activated by default.
>>>>>>>
>>>>>>> a little timeout (3s?)
>>>>>>>
>>>>>>> a thread ran in the configuration factory
>>>>>>> and the result get (through a future) in the assembler (to avoid to
>>>>>> wait)?
>>>>>>
>>>>>> If we did have it on by default, should definitely something really
>> easy
>>>>>> to shut off.
>>>>>>
>>>>>> This could easily be a ServerService with a file that extracts to
>>>>>> conf/updates.properties. Some of the config params could be the URL
>> we
>>>>>> check for updates and the frequency we check.
>>>>>>
>>>>>>
>>>>>> -David
>>>>>>
>>>>>>> 2012/2/1 David Blevins <da...@gmail.com>
>>>>>>>
>>>>>>>> This sounds like a great feature.
>>>>>>>>
>>>>>>>> My gut instinct is that maybe it should be disabled by default and
>>>>>>>> something we encourage people to enable.
>>>>>>>>
>>>>>>>> What do others think?
>>>>>>>>
>>>>>>>>
>>>>>>>> -David
>>>>>>>>
>>>>>>>> On Feb 1, 2012, at 6:36 AM, Jean-Louis MONTEIRO wrote:
>>>>>>>>
>>>>>>>>> +1
>>>>>>>>> Of course if that is one of my idea.
>>>>>>>>> Just to argue a bit.
>>>>>>>>>
>>>>>>>>> With Apache TomEE (it was also the case before), a lot of companies
>>>> or
>>>>>>>>> people are using OpenEJB/TomEE in production.
>>>>>>>>>
>>>>>>>>> It would be great to have kinda Apache TomEE server, we can use to
>>>>>>>> publish
>>>>>>>>> important releases or security/bugfixes.
>>>>>>>>>
>>>>>>>>> During startup and if the network is available, just ping our
>> central
>>>>>>>>> server and check whereas there is an important update available.
>>>>>>>>>
>>>>>>>>> If yes, just send a message in logs or an email to the
>> administrator
>>>> to
>>>>>>>>> inform him about new important updates.
>>>>>>>>> We could imagine enhencing our current webapp installer to ask for
>>>>>>>>> administrator information such as email, smtp server or so.
>>>>>>>>>
>>>>>>>>> That was my initial thought.
>>>>>>>>>
>>>>>>>>> Jean-Louis
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> 2012/2/1 Romain Manni-Bucau <rm...@gmail.com>
>>>>>>>>>
>>>>>>>>>> An idea from JL:
>>>>>>>>>>
>>>>>>>>>> should we do sthg like the update checker of ehcache?
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>
>>>>>>
>>>>
>> http://grepcode.com/file/repo1.maven.org/maven2/net.sf.ehcache/ehcache-core/2.4.0/net/sf/ehcache/util/UpdateChecker.java
>>>>>>>>>>
>>>>>>>>>> - Romain
>>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>
>>>>>>
>>>>
>>>>
>>
>>
Re: update checker
Posted by Romain Manni-Bucau <rm...@gmail.com>.
shouldn't cost anything
- Romain
2012/2/1 David Blevins <da...@gmail.com>
>
> On Feb 1, 2012, at 10:06 AM, Romain Manni-Bucau wrote:
>
> > it doesn't really match,
> >
> > it is nice to get the info in test mode too so it should be in the core.
>
> Having it on for a test would seem to be a really bad idea. We'd be doing
> 100+ checks per build per person on our own build alone.
>
>
> -David
>
> >
> > 2012/2/1 David Blevins <da...@gmail.com>
> >
> >>
> >> On Feb 1, 2012, at 9:57 AM, Romain Manni-Bucau wrote:
> >>
> >>> already added a version but not as a service.
> >>>
> >>> it can be desactivated using configuration factory offline mode or a
> >>> dedicated system property. The downloadable url and check url are
> >>> configurable through system properties.
> >>>
> >>> I use maven (repo1) to check the latest version.
> >>
> >> Let's move that to a ServerService under server/openejb-updates
> >>
> >> That way it can easily be excluded by virtue of it simply not being
> >> included in a distro. It'll get booted when the server boots, shutdown
> >> when the server shuts down. And if we wanted to maybe someday add a
> rest
> >> call to see if their server is up to date (it would report the cached
> value
> >> from the last check) it would be really easy.
> >>
> >> -David
> >>
> >>> 2012/2/1 David Blevins <da...@gmail.com>
> >>>
> >>>>
> >>>> On Feb 1, 2012, at 7:51 AM, Romain Manni-Bucau wrote:
> >>>>
> >>>>> i would like to see it activated by default.
> >>>>>
> >>>>> a little timeout (3s?)
> >>>>>
> >>>>> a thread ran in the configuration factory
> >>>>> and the result get (through a future) in the assembler (to avoid to
> >>>> wait)?
> >>>>
> >>>> If we did have it on by default, should definitely something really
> easy
> >>>> to shut off.
> >>>>
> >>>> This could easily be a ServerService with a file that extracts to
> >>>> conf/updates.properties. Some of the config params could be the URL
> we
> >>>> check for updates and the frequency we check.
> >>>>
> >>>>
> >>>> -David
> >>>>
> >>>>> 2012/2/1 David Blevins <da...@gmail.com>
> >>>>>
> >>>>>> This sounds like a great feature.
> >>>>>>
> >>>>>> My gut instinct is that maybe it should be disabled by default and
> >>>>>> something we encourage people to enable.
> >>>>>>
> >>>>>> What do others think?
> >>>>>>
> >>>>>>
> >>>>>> -David
> >>>>>>
> >>>>>> On Feb 1, 2012, at 6:36 AM, Jean-Louis MONTEIRO wrote:
> >>>>>>
> >>>>>>> +1
> >>>>>>> Of course if that is one of my idea.
> >>>>>>> Just to argue a bit.
> >>>>>>>
> >>>>>>> With Apache TomEE (it was also the case before), a lot of companies
> >> or
> >>>>>>> people are using OpenEJB/TomEE in production.
> >>>>>>>
> >>>>>>> It would be great to have kinda Apache TomEE server, we can use to
> >>>>>> publish
> >>>>>>> important releases or security/bugfixes.
> >>>>>>>
> >>>>>>> During startup and if the network is available, just ping our
> central
> >>>>>>> server and check whereas there is an important update available.
> >>>>>>>
> >>>>>>> If yes, just send a message in logs or an email to the
> administrator
> >> to
> >>>>>>> inform him about new important updates.
> >>>>>>> We could imagine enhencing our current webapp installer to ask for
> >>>>>>> administrator information such as email, smtp server or so.
> >>>>>>>
> >>>>>>> That was my initial thought.
> >>>>>>>
> >>>>>>> Jean-Louis
> >>>>>>>
> >>>>>>>
> >>>>>>> 2012/2/1 Romain Manni-Bucau <rm...@gmail.com>
> >>>>>>>
> >>>>>>>> An idea from JL:
> >>>>>>>>
> >>>>>>>> should we do sthg like the update checker of ehcache?
> >>>>>>>>
> >>>>>>>>
> >>>>>>>>
> >>>>>>
> >>>>
> >>
> http://grepcode.com/file/repo1.maven.org/maven2/net.sf.ehcache/ehcache-core/2.4.0/net/sf/ehcache/util/UpdateChecker.java
> >>>>>>>>
> >>>>>>>> - Romain
> >>>>>>>>
> >>>>>>
> >>>>>>
> >>>>
> >>>>
> >>
> >>
>
>
Re: update checker
Posted by David Blevins <da...@gmail.com>.
On Feb 1, 2012, at 10:06 AM, Romain Manni-Bucau wrote:
> it doesn't really match,
>
> it is nice to get the info in test mode too so it should be in the core.
Having it on for a test would seem to be a really bad idea. We'd be doing 100+ checks per build per person on our own build alone.
-David
>
> 2012/2/1 David Blevins <da...@gmail.com>
>
>>
>> On Feb 1, 2012, at 9:57 AM, Romain Manni-Bucau wrote:
>>
>>> already added a version but not as a service.
>>>
>>> it can be desactivated using configuration factory offline mode or a
>>> dedicated system property. The downloadable url and check url are
>>> configurable through system properties.
>>>
>>> I use maven (repo1) to check the latest version.
>>
>> Let's move that to a ServerService under server/openejb-updates
>>
>> That way it can easily be excluded by virtue of it simply not being
>> included in a distro. It'll get booted when the server boots, shutdown
>> when the server shuts down. And if we wanted to maybe someday add a rest
>> call to see if their server is up to date (it would report the cached value
>> from the last check) it would be really easy.
>>
>> -David
>>
>>> 2012/2/1 David Blevins <da...@gmail.com>
>>>
>>>>
>>>> On Feb 1, 2012, at 7:51 AM, Romain Manni-Bucau wrote:
>>>>
>>>>> i would like to see it activated by default.
>>>>>
>>>>> a little timeout (3s?)
>>>>>
>>>>> a thread ran in the configuration factory
>>>>> and the result get (through a future) in the assembler (to avoid to
>>>> wait)?
>>>>
>>>> If we did have it on by default, should definitely something really easy
>>>> to shut off.
>>>>
>>>> This could easily be a ServerService with a file that extracts to
>>>> conf/updates.properties. Some of the config params could be the URL we
>>>> check for updates and the frequency we check.
>>>>
>>>>
>>>> -David
>>>>
>>>>> 2012/2/1 David Blevins <da...@gmail.com>
>>>>>
>>>>>> This sounds like a great feature.
>>>>>>
>>>>>> My gut instinct is that maybe it should be disabled by default and
>>>>>> something we encourage people to enable.
>>>>>>
>>>>>> What do others think?
>>>>>>
>>>>>>
>>>>>> -David
>>>>>>
>>>>>> On Feb 1, 2012, at 6:36 AM, Jean-Louis MONTEIRO wrote:
>>>>>>
>>>>>>> +1
>>>>>>> Of course if that is one of my idea.
>>>>>>> Just to argue a bit.
>>>>>>>
>>>>>>> With Apache TomEE (it was also the case before), a lot of companies
>> or
>>>>>>> people are using OpenEJB/TomEE in production.
>>>>>>>
>>>>>>> It would be great to have kinda Apache TomEE server, we can use to
>>>>>> publish
>>>>>>> important releases or security/bugfixes.
>>>>>>>
>>>>>>> During startup and if the network is available, just ping our central
>>>>>>> server and check whereas there is an important update available.
>>>>>>>
>>>>>>> If yes, just send a message in logs or an email to the administrator
>> to
>>>>>>> inform him about new important updates.
>>>>>>> We could imagine enhencing our current webapp installer to ask for
>>>>>>> administrator information such as email, smtp server or so.
>>>>>>>
>>>>>>> That was my initial thought.
>>>>>>>
>>>>>>> Jean-Louis
>>>>>>>
>>>>>>>
>>>>>>> 2012/2/1 Romain Manni-Bucau <rm...@gmail.com>
>>>>>>>
>>>>>>>> An idea from JL:
>>>>>>>>
>>>>>>>> should we do sthg like the update checker of ehcache?
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>
>>>>
>> http://grepcode.com/file/repo1.maven.org/maven2/net.sf.ehcache/ehcache-core/2.4.0/net/sf/ehcache/util/UpdateChecker.java
>>>>>>>>
>>>>>>>> - Romain
>>>>>>>>
>>>>>>
>>>>>>
>>>>
>>>>
>>
>>
Re: update checker
Posted by Romain Manni-Bucau <rm...@gmail.com>.
it doesn't really match,
it is nice to get the info in test mode too so it should be in the core.
- Romain
2012/2/1 David Blevins <da...@gmail.com>
>
> On Feb 1, 2012, at 9:57 AM, Romain Manni-Bucau wrote:
>
> > already added a version but not as a service.
> >
> > it can be desactivated using configuration factory offline mode or a
> > dedicated system property. The downloadable url and check url are
> > configurable through system properties.
> >
> > I use maven (repo1) to check the latest version.
>
> Let's move that to a ServerService under server/openejb-updates
>
> That way it can easily be excluded by virtue of it simply not being
> included in a distro. It'll get booted when the server boots, shutdown
> when the server shuts down. And if we wanted to maybe someday add a rest
> call to see if their server is up to date (it would report the cached value
> from the last check) it would be really easy.
>
> -David
>
> > 2012/2/1 David Blevins <da...@gmail.com>
> >
> >>
> >> On Feb 1, 2012, at 7:51 AM, Romain Manni-Bucau wrote:
> >>
> >>> i would like to see it activated by default.
> >>>
> >>> a little timeout (3s?)
> >>>
> >>> a thread ran in the configuration factory
> >>> and the result get (through a future) in the assembler (to avoid to
> >> wait)?
> >>
> >> If we did have it on by default, should definitely something really easy
> >> to shut off.
> >>
> >> This could easily be a ServerService with a file that extracts to
> >> conf/updates.properties. Some of the config params could be the URL we
> >> check for updates and the frequency we check.
> >>
> >>
> >> -David
> >>
> >>> 2012/2/1 David Blevins <da...@gmail.com>
> >>>
> >>>> This sounds like a great feature.
> >>>>
> >>>> My gut instinct is that maybe it should be disabled by default and
> >>>> something we encourage people to enable.
> >>>>
> >>>> What do others think?
> >>>>
> >>>>
> >>>> -David
> >>>>
> >>>> On Feb 1, 2012, at 6:36 AM, Jean-Louis MONTEIRO wrote:
> >>>>
> >>>>> +1
> >>>>> Of course if that is one of my idea.
> >>>>> Just to argue a bit.
> >>>>>
> >>>>> With Apache TomEE (it was also the case before), a lot of companies
> or
> >>>>> people are using OpenEJB/TomEE in production.
> >>>>>
> >>>>> It would be great to have kinda Apache TomEE server, we can use to
> >>>> publish
> >>>>> important releases or security/bugfixes.
> >>>>>
> >>>>> During startup and if the network is available, just ping our central
> >>>>> server and check whereas there is an important update available.
> >>>>>
> >>>>> If yes, just send a message in logs or an email to the administrator
> to
> >>>>> inform him about new important updates.
> >>>>> We could imagine enhencing our current webapp installer to ask for
> >>>>> administrator information such as email, smtp server or so.
> >>>>>
> >>>>> That was my initial thought.
> >>>>>
> >>>>> Jean-Louis
> >>>>>
> >>>>>
> >>>>> 2012/2/1 Romain Manni-Bucau <rm...@gmail.com>
> >>>>>
> >>>>>> An idea from JL:
> >>>>>>
> >>>>>> should we do sthg like the update checker of ehcache?
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>
> >>
> http://grepcode.com/file/repo1.maven.org/maven2/net.sf.ehcache/ehcache-core/2.4.0/net/sf/ehcache/util/UpdateChecker.java
> >>>>>>
> >>>>>> - Romain
> >>>>>>
> >>>>
> >>>>
> >>
> >>
>
>
Re: update checker
Posted by David Blevins <da...@gmail.com>.
On Feb 1, 2012, at 9:57 AM, Romain Manni-Bucau wrote:
> already added a version but not as a service.
>
> it can be desactivated using configuration factory offline mode or a
> dedicated system property. The downloadable url and check url are
> configurable through system properties.
>
> I use maven (repo1) to check the latest version.
Let's move that to a ServerService under server/openejb-updates
That way it can easily be excluded by virtue of it simply not being included in a distro. It'll get booted when the server boots, shutdown when the server shuts down. And if we wanted to maybe someday add a rest call to see if their server is up to date (it would report the cached value from the last check) it would be really easy.
-David
> 2012/2/1 David Blevins <da...@gmail.com>
>
>>
>> On Feb 1, 2012, at 7:51 AM, Romain Manni-Bucau wrote:
>>
>>> i would like to see it activated by default.
>>>
>>> a little timeout (3s?)
>>>
>>> a thread ran in the configuration factory
>>> and the result get (through a future) in the assembler (to avoid to
>> wait)?
>>
>> If we did have it on by default, should definitely something really easy
>> to shut off.
>>
>> This could easily be a ServerService with a file that extracts to
>> conf/updates.properties. Some of the config params could be the URL we
>> check for updates and the frequency we check.
>>
>>
>> -David
>>
>>> 2012/2/1 David Blevins <da...@gmail.com>
>>>
>>>> This sounds like a great feature.
>>>>
>>>> My gut instinct is that maybe it should be disabled by default and
>>>> something we encourage people to enable.
>>>>
>>>> What do others think?
>>>>
>>>>
>>>> -David
>>>>
>>>> On Feb 1, 2012, at 6:36 AM, Jean-Louis MONTEIRO wrote:
>>>>
>>>>> +1
>>>>> Of course if that is one of my idea.
>>>>> Just to argue a bit.
>>>>>
>>>>> With Apache TomEE (it was also the case before), a lot of companies or
>>>>> people are using OpenEJB/TomEE in production.
>>>>>
>>>>> It would be great to have kinda Apache TomEE server, we can use to
>>>> publish
>>>>> important releases or security/bugfixes.
>>>>>
>>>>> During startup and if the network is available, just ping our central
>>>>> server and check whereas there is an important update available.
>>>>>
>>>>> If yes, just send a message in logs or an email to the administrator to
>>>>> inform him about new important updates.
>>>>> We could imagine enhencing our current webapp installer to ask for
>>>>> administrator information such as email, smtp server or so.
>>>>>
>>>>> That was my initial thought.
>>>>>
>>>>> Jean-Louis
>>>>>
>>>>>
>>>>> 2012/2/1 Romain Manni-Bucau <rm...@gmail.com>
>>>>>
>>>>>> An idea from JL:
>>>>>>
>>>>>> should we do sthg like the update checker of ehcache?
>>>>>>
>>>>>>
>>>>>>
>>>>
>> http://grepcode.com/file/repo1.maven.org/maven2/net.sf.ehcache/ehcache-core/2.4.0/net/sf/ehcache/util/UpdateChecker.java
>>>>>>
>>>>>> - Romain
>>>>>>
>>>>
>>>>
>>
>>
Re: update checker
Posted by Romain Manni-Bucau <rm...@gmail.com>.
already added a version but not as a service.
it can be desactivated using configuration factory offline mode or a
dedicated system property. The downloadable url and check url are
configurable through system properties.
I use maven (repo1) to check the latest version.
- Romain
2012/2/1 David Blevins <da...@gmail.com>
>
> On Feb 1, 2012, at 7:51 AM, Romain Manni-Bucau wrote:
>
> > i would like to see it activated by default.
> >
> > a little timeout (3s?)
> >
> > a thread ran in the configuration factory
> > and the result get (through a future) in the assembler (to avoid to
> wait)?
>
> If we did have it on by default, should definitely something really easy
> to shut off.
>
> This could easily be a ServerService with a file that extracts to
> conf/updates.properties. Some of the config params could be the URL we
> check for updates and the frequency we check.
>
>
> -David
>
> > 2012/2/1 David Blevins <da...@gmail.com>
> >
> >> This sounds like a great feature.
> >>
> >> My gut instinct is that maybe it should be disabled by default and
> >> something we encourage people to enable.
> >>
> >> What do others think?
> >>
> >>
> >> -David
> >>
> >> On Feb 1, 2012, at 6:36 AM, Jean-Louis MONTEIRO wrote:
> >>
> >>> +1
> >>> Of course if that is one of my idea.
> >>> Just to argue a bit.
> >>>
> >>> With Apache TomEE (it was also the case before), a lot of companies or
> >>> people are using OpenEJB/TomEE in production.
> >>>
> >>> It would be great to have kinda Apache TomEE server, we can use to
> >> publish
> >>> important releases or security/bugfixes.
> >>>
> >>> During startup and if the network is available, just ping our central
> >>> server and check whereas there is an important update available.
> >>>
> >>> If yes, just send a message in logs or an email to the administrator to
> >>> inform him about new important updates.
> >>> We could imagine enhencing our current webapp installer to ask for
> >>> administrator information such as email, smtp server or so.
> >>>
> >>> That was my initial thought.
> >>>
> >>> Jean-Louis
> >>>
> >>>
> >>> 2012/2/1 Romain Manni-Bucau <rm...@gmail.com>
> >>>
> >>>> An idea from JL:
> >>>>
> >>>> should we do sthg like the update checker of ehcache?
> >>>>
> >>>>
> >>>>
> >>
> http://grepcode.com/file/repo1.maven.org/maven2/net.sf.ehcache/ehcache-core/2.4.0/net/sf/ehcache/util/UpdateChecker.java
> >>>>
> >>>> - Romain
> >>>>
> >>
> >>
>
>
Re: update checker
Posted by David Blevins <da...@gmail.com>.
On Feb 1, 2012, at 7:51 AM, Romain Manni-Bucau wrote:
> i would like to see it activated by default.
>
> a little timeout (3s?)
>
> a thread ran in the configuration factory
> and the result get (through a future) in the assembler (to avoid to wait)?
If we did have it on by default, should definitely something really easy to shut off.
This could easily be a ServerService with a file that extracts to conf/updates.properties. Some of the config params could be the URL we check for updates and the frequency we check.
-David
> 2012/2/1 David Blevins <da...@gmail.com>
>
>> This sounds like a great feature.
>>
>> My gut instinct is that maybe it should be disabled by default and
>> something we encourage people to enable.
>>
>> What do others think?
>>
>>
>> -David
>>
>> On Feb 1, 2012, at 6:36 AM, Jean-Louis MONTEIRO wrote:
>>
>>> +1
>>> Of course if that is one of my idea.
>>> Just to argue a bit.
>>>
>>> With Apache TomEE (it was also the case before), a lot of companies or
>>> people are using OpenEJB/TomEE in production.
>>>
>>> It would be great to have kinda Apache TomEE server, we can use to
>> publish
>>> important releases or security/bugfixes.
>>>
>>> During startup and if the network is available, just ping our central
>>> server and check whereas there is an important update available.
>>>
>>> If yes, just send a message in logs or an email to the administrator to
>>> inform him about new important updates.
>>> We could imagine enhencing our current webapp installer to ask for
>>> administrator information such as email, smtp server or so.
>>>
>>> That was my initial thought.
>>>
>>> Jean-Louis
>>>
>>>
>>> 2012/2/1 Romain Manni-Bucau <rm...@gmail.com>
>>>
>>>> An idea from JL:
>>>>
>>>> should we do sthg like the update checker of ehcache?
>>>>
>>>>
>>>>
>> http://grepcode.com/file/repo1.maven.org/maven2/net.sf.ehcache/ehcache-core/2.4.0/net/sf/ehcache/util/UpdateChecker.java
>>>>
>>>> - Romain
>>>>
>>
>>
Re: update checker
Posted by Romain Manni-Bucau <rm...@gmail.com>.
yep i agree, for now here are the
messages org.apache.openejb.util.UpdateChecker#message, any idea to enhance
it is welcome. Should we do as hibernate and so on using code for message
too? kind of "OEJB-1234 you are not up-to-date"?
- Romain
2012/2/2 Alan D. Cabrera <li...@toolazydogs.com>
>
> On Feb 2, 2012, at 6:43 AM, Alan D. Cabrera wrote:
>
> > With that said, nobody sits down with a bag of beer and chips and
> casually scans the logs, not when there are thousands of logs to scan. :)
> The engineers have to setup some kind of Splunk report.
>
> It will be important that some bits of the update message be unchanging so
> that it can be consistently caught by a Splunk type report.
>
>
> Regards,
> Alan
>
Re: update checker
Posted by "Alan D. Cabrera" <li...@toolazydogs.com>.
On Feb 2, 2012, at 6:43 AM, Alan D. Cabrera wrote:
> With that said, nobody sits down with a bag of beer and chips and casually scans the logs, not when there are thousands of logs to scan. :) The engineers have to setup some kind of Splunk report.
It will be important that some bits of the update message be unchanging so that it can be consistently caught by a Splunk type report.
Regards,
Alan
Re: update checker
Posted by Romain Manni-Bucau <rm...@gmail.com>.
it is currently deactiated by default.
can be turn on by activating a syst prop which can be put in
system.properties or ~/.openejb/system.properties. I think it is a good
compromise since it can always be activated if a user wants but it doesn't
modify the default behavior.
- Romain
2012/2/2 Alan D. Cabrera <li...@toolazydogs.com>
> Reaching out to some external server would never go well in the production
> environments of the organizations that I am and have worked at. They're
> really kind of anal about that kind of stuff.
>
> With that said, nobody sits down with a bag of beer and chips and casually
> scans the logs, not when there are thousands of logs to scan. :) The
> engineers have to setup some kind of Splunk report. I'm sure they would
> opt for a simple announcement list to be notified of updates and security
> issues.
>
> imo, it should be in a jar that you can add if you want the feature so it
> can't be accidentally turned on.
>
>
> Regards,
> Alan
>
>
> On Feb 1, 2012, at 7:51 AM, Romain Manni-Bucau wrote:
>
> > i would like to see it activated by default.
> >
> > a little timeout (3s?)
> >
> > a thread ran in the configuration factory
> > and the result get (through a future) in the assembler (to avoid to
> wait)?
> >
> > - Romain
> >
> >
> > 2012/2/1 David Blevins <da...@gmail.com>
> >
> >> This sounds like a great feature.
> >>
> >> My gut instinct is that maybe it should be disabled by default and
> >> something we encourage people to enable.
> >>
> >> What do others think?
>
>
Re: update checker
Posted by "Alan D. Cabrera" <li...@toolazydogs.com>.
Reaching out to some external server would never go well in the production environments of the organizations that I am and have worked at. They're really kind of anal about that kind of stuff.
With that said, nobody sits down with a bag of beer and chips and casually scans the logs, not when there are thousands of logs to scan. :) The engineers have to setup some kind of Splunk report. I'm sure they would opt for a simple announcement list to be notified of updates and security issues.
imo, it should be in a jar that you can add if you want the feature so it can't be accidentally turned on.
Regards,
Alan
On Feb 1, 2012, at 7:51 AM, Romain Manni-Bucau wrote:
> i would like to see it activated by default.
>
> a little timeout (3s?)
>
> a thread ran in the configuration factory
> and the result get (through a future) in the assembler (to avoid to wait)?
>
> - Romain
>
>
> 2012/2/1 David Blevins <da...@gmail.com>
>
>> This sounds like a great feature.
>>
>> My gut instinct is that maybe it should be disabled by default and
>> something we encourage people to enable.
>>
>> What do others think?
Re: update checker
Posted by Romain Manni-Bucau <rm...@gmail.com>.
i would like to see it activated by default.
a little timeout (3s?)
a thread ran in the configuration factory
and the result get (through a future) in the assembler (to avoid to wait)?
- Romain
2012/2/1 David Blevins <da...@gmail.com>
> This sounds like a great feature.
>
> My gut instinct is that maybe it should be disabled by default and
> something we encourage people to enable.
>
> What do others think?
>
>
> -David
>
> On Feb 1, 2012, at 6:36 AM, Jean-Louis MONTEIRO wrote:
>
> > +1
> > Of course if that is one of my idea.
> > Just to argue a bit.
> >
> > With Apache TomEE (it was also the case before), a lot of companies or
> > people are using OpenEJB/TomEE in production.
> >
> > It would be great to have kinda Apache TomEE server, we can use to
> publish
> > important releases or security/bugfixes.
> >
> > During startup and if the network is available, just ping our central
> > server and check whereas there is an important update available.
> >
> > If yes, just send a message in logs or an email to the administrator to
> > inform him about new important updates.
> > We could imagine enhencing our current webapp installer to ask for
> > administrator information such as email, smtp server or so.
> >
> > That was my initial thought.
> >
> > Jean-Louis
> >
> >
> > 2012/2/1 Romain Manni-Bucau <rm...@gmail.com>
> >
> >> An idea from JL:
> >>
> >> should we do sthg like the update checker of ehcache?
> >>
> >>
> >>
> http://grepcode.com/file/repo1.maven.org/maven2/net.sf.ehcache/ehcache-core/2.4.0/net/sf/ehcache/util/UpdateChecker.java
> >>
> >> - Romain
> >>
>
>
Re: update checker
Posted by David Blevins <da...@gmail.com>.
This sounds like a great feature.
My gut instinct is that maybe it should be disabled by default and something we encourage people to enable.
What do others think?
-David
On Feb 1, 2012, at 6:36 AM, Jean-Louis MONTEIRO wrote:
> +1
> Of course if that is one of my idea.
> Just to argue a bit.
>
> With Apache TomEE (it was also the case before), a lot of companies or
> people are using OpenEJB/TomEE in production.
>
> It would be great to have kinda Apache TomEE server, we can use to publish
> important releases or security/bugfixes.
>
> During startup and if the network is available, just ping our central
> server and check whereas there is an important update available.
>
> If yes, just send a message in logs or an email to the administrator to
> inform him about new important updates.
> We could imagine enhencing our current webapp installer to ask for
> administrator information such as email, smtp server or so.
>
> That was my initial thought.
>
> Jean-Louis
>
>
> 2012/2/1 Romain Manni-Bucau <rm...@gmail.com>
>
>> An idea from JL:
>>
>> should we do sthg like the update checker of ehcache?
>>
>>
>> http://grepcode.com/file/repo1.maven.org/maven2/net.sf.ehcache/ehcache-core/2.4.0/net/sf/ehcache/util/UpdateChecker.java
>>
>> - Romain
>>
Re: update checker
Posted by Jean-Louis MONTEIRO <je...@gmail.com>.
+1
Of course if that is one of my idea.
Just to argue a bit.
With Apache TomEE (it was also the case before), a lot of companies or
people are using OpenEJB/TomEE in production.
It would be great to have kinda Apache TomEE server, we can use to publish
important releases or security/bugfixes.
During startup and if the network is available, just ping our central
server and check whereas there is an important update available.
If yes, just send a message in logs or an email to the administrator to
inform him about new important updates.
We could imagine enhencing our current webapp installer to ask for
administrator information such as email, smtp server or so.
That was my initial thought.
Jean-Louis
2012/2/1 Romain Manni-Bucau <rm...@gmail.com>
> An idea from JL:
>
> should we do sthg like the update checker of ehcache?
>
>
> http://grepcode.com/file/repo1.maven.org/maven2/net.sf.ehcache/ehcache-core/2.4.0/net/sf/ehcache/util/UpdateChecker.java
>
> - Romain
>