X-TagToolbar-Keys: D20110315230545409
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit

That's because log4j 1.2.16 uses a packaging of 'bundle', instead of the
usual 'jar' packaging.

On 15/03/11 17:29, Miguel Landaeta wrote:
> 
> On Mon, Mar 14, 2011 at 5:45 PM, Ludovic Claude
> <[email protected]> wrote:
>>> liblog4j-1.2-java 1.2.15-11 (unstable) provides
>>> /usr/share/maven-repo/log4j/log4j/1.2.x/log4j-1.2.x.pom
>>>
>>> liblog4j-1.2-java 1.2.16-1 (experimental) doesn't
>>> provide that file anymore.
>>>
>>
>> That looks wrong, as this package should keep log4j-1.2.x.pom in the
>> Maven repository. Actually, I have a fix for maven-repo-helper which
>> will fix this issue, I need to commit it first.
>>
>> Ludovic
> 
> Just curiosity, what change in liblog4j1.2-java 1.2.16-1 triggers this issue
> in maven-repo-helper? Since the helper had not been updated in a while
> I didn't suspect of that.
> 




-- 
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

Reply via email to