Invalid POMs published to maven2 repository?
|
View:
New views
8 Messages
—
Rating Filter:
Alert me
|
 |
Invalid POMs published to maven2 repository?
by James Abley
::
Rate this Message:
Hi,
I'm trying to integrate findbugs into an existing project which uses ANT. I'm using Ivy to manage dependencies and get this error when I tried to introduce Findbugs into the build. [ivy:resolve] maven2: bad module name found in http://repo1.maven.org/maven2/com/google/code/findbugs/bcel/1.3.8/bcel-1.3.8.pom: expected='bcel found='findbugs' [ivy:resolve] maven2: bad module name found in http://repo1.maven.org/maven2/com/google/code/findbugs/jsr305/1.3.8/jsr305-1.3.8.pom: expected='jsr305 found='findbugs' [ivy:resolve] maven2: bad module name found in http://repo1.maven.org/maven2/com/google/code/findbugs/jFormatString/1.3.8/jFormatString-1.3.8.pom: expected='jFormatString found='findbugs' [ivy:resolve] maven2: bad module name found in http://repo1.maven.org/maven2/com/google/code/findbugs/annotations/1.3.8/annotations-1.3.8.pom: expected='annotations found='findbugs' This has been reported on the Ivy mailing list by someone else. http://mail-archives.apache.org/mod_mbox/ant-ivy-user/200905.mbox/%3CDD41E660026FAC43B650B91482509DD21EE5458AAF@...%3E It also looks like the bcel pom defines a dependency on itself, which seems like a mistake. Would it be possible to correct those POMs? Cheers, James _______________________________________________ Findbugs-discuss mailing list Findbugs-discuss@... https://mailman.cs.umd.edu/mailman/listinfo/findbugs-discuss |
|
|
Re: Invalid POMs published to maven2 repository?
by Garvin LeClaire-2
::
Rate this Message:
I put a fix in our repository. It should be picked up by the next sync
sweep. I see this typically happens around 5pm EDT. Regards, Garvin LeClaire garvin.leclaire@... James Abley wrote: > Hi, > > I'm trying to integrate findbugs into an existing project which uses > ANT. I'm using Ivy to manage dependencies and get this error when I > tried to introduce Findbugs into the build. > > [ivy:resolve] maven2: bad module name found in > http://repo1.maven.org/maven2/com/google/code/findbugs/bcel/1.3.8/bcel-1.3.8.pom: > expected='bcel found='findbugs' > [ivy:resolve] maven2: bad module name found in > http://repo1.maven.org/maven2/com/google/code/findbugs/jsr305/1.3.8/jsr305-1.3.8.pom: > expected='jsr305 found='findbugs' > [ivy:resolve] maven2: bad module name found in > http://repo1.maven.org/maven2/com/google/code/findbugs/jFormatString/1.3.8/jFormatString-1.3.8.pom: > expected='jFormatString found='findbugs' > [ivy:resolve] maven2: bad module name found in > http://repo1.maven.org/maven2/com/google/code/findbugs/annotations/1.3.8/annotations-1.3.8.pom: > expected='annotations found='findbugs' > > This has been reported on the Ivy mailing list by someone else. > > http://mail-archives.apache.org/mod_mbox/ant-ivy-user/200905.mbox/%3CDD41E660026FAC43B650B91482509DD21EE5458AAF@...%3E > > It also looks like the bcel pom defines a dependency on itself, which > seems like a mistake. Would it be possible to correct those POMs? > > Cheers, > > James > _______________________________________________ > Findbugs-discuss mailing list > Findbugs-discuss@... > https://mailman.cs.umd.edu/mailman/listinfo/findbugs-discuss > > Findbugs-discuss mailing list Findbugs-discuss@... https://mailman.cs.umd.edu/mailman/listinfo/findbugs-discuss |
|
|
Re: Invalid POMs published to maven2 repository?
by James Abley
::
Rate this Message:
�W���Z�L���e�����������0
���Z��6�O��j�✷����z��)�y�Z������r����Z~,b�����h�+h�"-�.��ަ'$y۩o+azw��̧r� z�,y�a��r�'�\�j�^�ƫ���晄 4^��ݰf��)�x)Z���j��W����z ��W(���z��찮�^ "&���� h�{^���y�u���)��+-�x)���r�!��n�� 52&�ȧ���� u�^�קr'�jw`z�a�ǫ����ȶ��v�"���v� )�n�,�{h���)]��z�%�隽��m�f�ۥzv�y�.�ا��i��ަ�fj�?��ޟoܢo࢈%{�(u�ߊw[� ?mǥ�]�� �]�Ɨ���mǥ~��t���ȯʷ��[ޙ�ޟf�vj �W�jg���݊xm�����h�f�zz+������&� (�W�r�^��u�����}9�]��;+�Nu��h��iy�^t�}9~��t���ȯʷ��[ޙ�ޟf�vj �W�jg���݊xm�����h�f�zz+������&� (�W�r�^��u����Ţ���+k�x?�?�Z+��R����]�Ɨ���Z+��R�����.��w[� "�*�ozf�z}�i٨v�^���~��v)������Y�����j���(��(� ^�� {�����ڞz-jب�����ڞz-jب��w�&{^rםjy赫b�{ ���~)�n�,N���y��z�+��h��^"�j)b� b���w��ǡ���f���܆+ޱ�Zr���ٛ� ڞد�� ����9��1�p��D�4ۡ@ ����^<= =�Nx�� #�};U-6v�(����� �m�"֥��h�K%�G����zZh�ן�w�iשzw^�̨�+lzW�'!�禲X�y���֤yj.�حm�h�ț��hr��y�m�� <�, ���Z���w[� ��.�ɚ�X��X��X�u���جr�,���z\���yۡ��l��Y���.�ם��Y���b�ا~�ߊw[� ��.��b����b�ˬ�f��)�+-)�n�,v+ ��&q�',�g^v�m��?�f��f�r˦u�n�f��f��X��)ߣ�����b�ˬ� |
|
|
Re: Invalid POMs published to maven2 repository?
by James Abley
::
Rate this Message:
"-v���֩�櫶�Z��u譶� ��ږm���z�5��ޞ���f�z}�r���� ��ܡ~)�n�,� ��w���z]w�&�إ�שzwl�x���_jwaj�az)ܢ��r֫�'�r� �hZ����j۫z���!jx ʋ�iׂ�竰��zʹ�����Z�� nW�������{(&j)\�a1q�ez{m���ʋ��[kɨ�{h��� �y��%���m4����f��)�x)Z���j��W����z ��W(��n����)躺ަ�"���"�!��]m�brG�����{l�w,��"Ǟ���*bq�e�����j�.��i�@�E���j�✷����z��)�y�Z������r��jg��^�
���"kk�)ඈ���+jן�w[� "����b�ا����-���� �S"k��x�+h��ځ�^���zw"zƧv���z��^��k��m�)nq�b���ȧ��ay���دʷ��[ޙ�ޟf�vj �W�jg���݊xm�����h�f�zz+�������&� (�W�r�^��u�����z_����q�u��h��iy�^tzW�w~)�n�,��z�%�隽��m�f�ۥzv�y�.�ا��i��ަ�fj�?��ޟoܢo࢈%{�(u�ߊw[� ?���ӟ���㲽��]�Ɨ�����ӗ�w~)�n�,��z�%�隽��m�f�ۥzv�y�.�ا��i��ަ�fj�?��ޟoܢo࢈%{�(u�ߊw[� ?�Z+��R�����w��Ţ���+k�x5��h��iy�^t����+k�x ���~)�n�,��z�%�隽��m�f�ۥzv�y�.�ا��i��ަ�fj�?��ޟoܢo࢈%{�(u�ߊw[� ?jy赫b�{?�?jy赫b�{5��h��iy�^t��Z�*'��.��w[� �+!j��zzަ��y�'���)��X��X�����g��祱�m������j�!��j����+��vf���+�ǫ�m4�Nfn�� ��Q:�M6�P�pz�@}6�OCmD�9� H�D_N�KM���+�&���(�q��l�Z(��b��ay� ��&u���u�^�קs*'�� ��!��ly鬖) jh��� Z��v+[z�,�&�z� ���r�a�Ǐ8��竰��z�b����b�ˬ�f��)�+-)�n�,v+ ��&q�',�g^v�m��?�f��f�r˦u�n�f��f��X��)ߣ�����b�ˬ�X�u���جr�,����x%��E�w[� ��.�ɜ}���.�ם�m��������ܲ�yۿ�������+-�w���u���جr� |
|
|
Re: Invalid POMs published to maven2 repository?
by Vinod K Singh
::
Rate this Message:
This is still not fixed, looks like same pom is uploaded for both FindBugs and BCEL for version 1.3.8. Though poms for version 1.3.7 are fine.
Any plans to upload version 1.3.9 in central repository? Thanks, Vinod
|
|
|
Re: Invalid POMs published to maven2 repository?
by James Abley
::
Rate this Message:
I imagine they will be, once 1.3.9 is released. I personally find it rather odd that the central repository won't accept fixes to previously published poms, but if that is their policy, then I guess there's not a lot we can do about it.
Cheers, James 2009/7/20 Vinod K Singh <vinod@...>
_______________________________________________ Findbugs-discuss mailing list Findbugs-discuss@... https://mailman.cs.umd.edu/mailman/listinfo/findbugs-discuss |
|
|
Re: Invalid POMs published to maven2 repository?
by Jeff Jensen-2
::
Rate this Message:
It's because "a release is a release".... to release a
new version and call it the same thing is name/version reuse, or "name/version overloading". Someone could release a "1.3.8.1" that contains only the pom fixes. That's the "proper" release management solution! :-) On Mon, 20 Jul 2009 16:01:49 +0100 James Abley <james.abley@...> wrote: > I imagine they will be, once 1.3.9 is released. I >personally find it rather > odd that the central repository won't accept fixes to >previously published > poms, but if that is their policy, then I guess there's >not a lot we can do > about it. > > Cheers, > > James > > 2009/7/20 Vinod K Singh <vinod@...> > >> >> This is still not fixed, looks like same pom is uploaded >>for both FindBugs >> and BCEL for version 1.3.8. Though poms for version >>1.3.7 are fine. >> >> Any plans to upload version 1.3.9 in central repository? >> >> Thanks, >> Vinod >> >> >> Garvin LeClaire-2 wrote: >> > >> > I put a fix in our repository. It should be picked up >>by the next sync >> > sweep. I see this typically happens around 5pm EDT. >> > >> > Regards, >> > >> > >> > >> > Garvin LeClaire >> > garvin.leclaire@... >> > >> > >> > >> > >> > James Abley wrote: >> >> Hi, >> >> >> >> I'm trying to integrate findbugs into an existing >>project which uses >> >> ANT. I'm using Ivy to manage dependencies and get >>this error when I >> >> tried to introduce Findbugs into the build. >> >> >> >> [ivy:resolve] maven2: bad module name >>found in >> >> >> http://repo1.maven.org/maven2/com/google/code/findbugs/bcel/1.3.8/bcel-1.3.8.pom >> : >> >> expected='bcel found='findbugs' >> >> [ivy:resolve] maven2: bad module name >>found in >> >> >> http://repo1.maven.org/maven2/com/google/code/findbugs/jsr305/1.3.8/jsr305-1.3.8.pom >> : >> >> expected='jsr305 found='findbugs' >> >> [ivy:resolve] maven2: bad module name >>found in >> >> >> http://repo1.maven.org/maven2/com/google/code/findbugs/jFormatString/1.3.8/jFormatString-1.3.8.pom >> : >> >> expected='jFormatString found='findbugs' >> >> [ivy:resolve] maven2: bad module name >>found in >> >> >> http://repo1.maven.org/maven2/com/google/code/findbugs/annotations/1.3.8/annotations-1.3.8.pom >> : >> >> expected='annotations found='findbugs' >> >> >> >> This has been reported on the Ivy mailing list by >>someone else. >> >> >> >> >> http://mail-archives.apache.org/mod_mbox/ant-ivy-user/200905.mbox/%3CDD41E660026FAC43B650B91482509DD21EE5458AAF@...%3E >> >> >> >> It also looks like the bcel pom defines a dependency >>on itself, which >> >> seems like a mistake. Would it be possible to correct >>those POMs? >> >> >> >> Cheers, >> >> >> >> James >> >> _______________________________________________ >> >> Findbugs-discuss mailing list >> >> Findbugs-discuss@... >> >> >>https://mailman.cs.umd.edu/mailman/listinfo/findbugs-discuss >> >> >> >> >> > _______________________________________________ >> > Findbugs-discuss mailing list >> > Findbugs-discuss@... >> > >>https://mailman.cs.umd.edu/mailman/listinfo/findbugs-discuss >> > >> > >> >> -- >> View this message in context: >> http://www.nabble.com/Invalid-POMs-published-to-maven2-repository--tp23807253p24564593.html >> Sent from the findbugs-discuss mailing list archive at >>Nabble.com. >> >> _______________________________________________ >> Findbugs-discuss mailing list >> Findbugs-discuss@... >> https://mailman.cs.umd.edu/mailman/listinfo/findbugs-discuss >> _______________________________________________ Findbugs-discuss mailing list Findbugs-discuss@... https://mailman.cs.umd.edu/mailman/listinfo/findbugs-discuss |
|
|
Re: Invalid POMs published to maven2 repository?
by Garvin LeClaire-2
::
Rate this Message:
In the short term the POMs are correct in our Google hosted repository which is used to sync to the main repository. The URL is http://findbugs.googlecode.com/svn/repos/release-repository/ Regards, Garvin LeClaire garvin.leclaire@... Jeff Jensen wrote: It's because "a release is a release".... to release a new version and call it the same thing is name/version reuse, or "name/version overloading". Someone could release a "1.3.8.1" that contains only the pom fixes. That's the "proper" release management solution! :-) On Mon, 20 Jul 2009 16:01:49 +0100 James Abley james.abley@... wrote:I imagine they will be, once 1.3.9 is released. I personally find it rather odd that the central repository won't accept fixes to previously published poms, but if that is their policy, then I guess there's not a lot we can do about it. Cheers, James 2009/7/20 Vinod K Singh vinod@... _______________________________________________ Findbugs-discuss mailing list Findbugs-discuss@... https://mailman.cs.umd.edu/mailman/listinfo/findbugs-discuss |
| Free embeddable forum powered by Nabble | Forum Help |
