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 <[email protected]> > > 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 <[email protected]> > > > >> > >> 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 <[email protected]> > >>> > >>>> 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 <[email protected]> > >>>>> > >>>>>> 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 > >>>>>> > >>>> > >>>> > >> > >> > >
