This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--shs9t6iextlsoCEeWdpX1bwPkeG6VpQxw
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
On Tue 25 Feb 2014 02:05:30 PM CET, Alon Bar-Lev wrote:
----- Original Message -----
> From: "Itamar Heim" <iheim(a)redhat.com>
> To: "Juan Hernandez" <jhernand(a)redhat.com>, "arch"
<arch(a)ovirt.org>, "=
infra" <infra(a)ovirt.org>, "David
Caro Estevez"
> <dcaroest(a)redhat.com>
> Sent: Tuesday, February 25, 2014 2:56:19 PM
> Subject: Re: New git repository for maven-modules-plugin
>
> On 02/21/2014 04:48 PM, Juan Hernandez wrote:
>> Hello,
>>
>> I would like to request a new git repository named maven-modules-plug=
in
>> to manage the source of a little tool that we use for the
build proce=
ss
>> of the engine.
>>
>> Currently the source of this tool is inside the ovirt-engine reposito=
ry,
>> but I want to start distributing it via maven central, in
order to bu=
ild
>> other projects. This is much simpler if the source is in
it's own
>> repository and has its own release cycle.
>>
>> What I would like to have in that repository is the same that I
>> currently have here:
>>
>>
https://github.com/jhernand/modules-maven-plugin
>>
>> Once the code is moved to this new repository, and distributed via Ma=
ven
>> Central, the build process of the engine can be updated
accordingly w=
ith
>> the following patch:
>>
>>
http://gerrit.ovirt.org/24866
>>
>> Thanks in advance,
>> Juan Hernandez
>>
>
> I see no other comment on this.
> none of the other repo's used to manage our infra/build is a match
> currently?
If we fork this out, we need it packaged for fedora as well, and other =
distros as
we go.
So it requires own repository.
If it is ovirt specific, I would like to see ovirt within the name... b=
ut not
critical.
Regards,
Alon
Is this still required?
--
David Caro
Red Hat S.L.
Continuous Integration Engineer - EMEA ENG Virtualization R&D
Email: dcaro(a)redhat.com
Web:
www.redhat.com
RHT Global #: 82-62605
--shs9t6iextlsoCEeWdpX1bwPkeG6VpQxw
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iQEcBAEBAgAGBQJTLA2GAAoJEEBxx+HSYmnDGgIH/3vk6TWJdgB7VuqcNRUSNhiJ
mrqliDNHXcXsXoND4fe1Ug73bsEoFOoVSVZZqsQY/w3GvHYPU59ouH9gEGXdk4qu
ZbL6JPslgUkQrrCBo2krZQD+qrJ1OjONxKqPXvKUIEySydBf2K53OEBxeftWIzsx
nK8naLiYst3ZWz+A80rO2oVQ7i9nVu5RIreGcChdn8C1mPFQ47fX7x1Kspg1a/5h
LuX2+dCFCwhA6DmA8L6jMsfgz63tBUiwG5w29eDg4Eq+PYSf+ZVk5698DqBFRPZM
LzcuC8YZcUI2ZJAfYjNLpLSG9eNrfP95JmmLvBopsMmoXzaA282sjWkbGzy6wYw=
=d0bD
-----END PGP SIGNATURE-----
--shs9t6iextlsoCEeWdpX1bwPkeG6VpQxw--