Yep, we had some discussion regarding this on #weld-dev and came to
the same conclusion but thought it would better to use custom keys to
make sure they aren't accidently populated. Now I'm mostly looking for
a good way to read the manifest file from within a web application
without getting a random one from the classloader. I'm currently
looking at the Package source code for hints...
On Mon, Nov 30, 2009 at 11:08 PM, Dan Allen <dan.j.allen(a)gmail.com> wrote:
Yes, the manifest would absolutely be the right choice. Remember
there are
already some standard keys such as Implementation-Version.
- Dan Allen
Sent from my Android-powered phone:
An open platform for carriers, consumers
and developers.
On Nov 30, 2009 6:20 AM, "Pete Muir" <pmuir(a)redhat.com> wrote:
Not a bad idea, want to prototype something?
Note that if you put it in beans.xml it will leak into user configuration
too, probably something we don't want. It would better to do this using the
Manifest IMO.
On 30 Nov 2009, at 06:38, Nicklas Karlsson wrote: > A minor detail but do
you think it would be ha...
--
---
Nik