Nam Nguyen wrote:
> Hi Paul,
>
> I have some question in-line...
>
> Paul Sandoz wrote:
>> Jakub Podlesak wrote:
>>> Hi all,
>>>
>>> Aaron suggests to push [localizer.jar] file along with Jersey
>>> artifacts to java.net maven repository. The reason is that then he
>>> would be able to mavenize Jersey build process. [localizer.jar] is
>>> the only dependency jar, which is not available on a maven repo yet.
>>>
>>>
>>
>> This is one of those cases where we just grabbed it without thinking
>> about the future consequences!
>>
>>
>>> I think we should ask people producing the [localizer.jar] file for
>>> it, or at least let them know we want to push the jar to the java.net
>>> maven repo.
>>>
>>> Does anybody know where was the [localizer.jar] file taken from? (And
>>> whom to contact in that matter?)
>>>
>>
>> It was from an internal project Kohsuke created. AFAIK it is not on
>> java.net. The jsr311-api.jar also has a dependency on this jar.
> I tend to think that in general pure API module should not depends on
> non-API. Could you please explain what is this dependency? Would it
> be cleaner if we try to remove this dependency instead of going deeper?
Note that this dependency is only during the build time, and at runtime
there's no additional dependency.
--
Kohsuke Kawaguchi
Sun Microsystems kohsuke.kawaguchi_at_sun.com