[weld-dev] manifest frinder

[Gavin King]

then the manifest is the right place.

On Tue, Dec 1, 2009 at 11:10 AM, Pete Muir <pmuir at redhat.com> wrote:
> The module.
>
> On 1 Dec 2009, at 16:09, Gavin King wrote:
>
>> Well, a package-level annotation would do it. It all depends upon
>> whether you really want info about the package, or about the *module*.
>> Which is it?
>>
>> On Tue, Dec 1, 2009 at 10:35 AM, Pete Muir <pmuir at redhat.com> wrote:
>>> We want some extra info from the manifest that isn't defined on Package (and Package doesn't allow you to get arbitrary info, just specific info...)
>>>
>>> Nik, if you put this in core, you can make it a Service with a default impl (JDKManifestFinder), and JBoss can use the VFSManifestFinder.
>>>
>>> On 1 Dec 2009, at 15:32, Ales Justin wrote:
>>>
>>>> http://anonsvn.jboss.org/repos/jbossas/projects/weld-int/trunk/deployer/src/main/java/org/jboss/weld/integration/util/
>>>>
>>>> But why Manifest in the first place?
>>>> If the classloading is done right,
>>>> Class::getPackage() should get you the right info.
>>>>
>>>> -Ales
>>>
>>>
>>> _______________________________________________
>>> weld-dev mailing list
>>> weld-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/weld-dev
>>>
>>
>>
>>
>> --
>> Gavin King
>> gavin.king at gmail.com
>> http://in.relation.to/Bloggers/Gavin
>> http://hibernate.org
>> http://seamframework.org
>
>



-- 
Gavin King
gavin.king at gmail.com
http://in.relation.to/Bloggers/Gavin
http://hibernate.org
http://seamframework.org