* Alexander Kurtakov <akurtako@redhat.com> [2010-04-22 02:52]:

> > On Thursday 22 April 2010, Guido Grazioli wrote:
> > Well it turns out that i actually need that pom to build maven-release;
> > some advice needed:
> > - should i bother netbeans maintainer to add the pom (but no pom
> > distribuited with netbeans sources)
> > - would it be a candidate for maven-common-poms rpm?
> > - packaging cvsclient itself, and make netbeans depend on it?
>
> Hi Guido,
>
> I've talked with the netbeans maintainer and he agreed that cvsclient should
> be packaged in a subpackage and available in the standard places. See
> https://bugzilla.redhat.com/show_bug.cgi?id=572165.  Please add your
> comments/needs to this bug and let him know what work is pending on this.
> Hopefully this will give it a higher priority. And I doubt that Victor will
> deny help :).
>

Agreed. maven2-common-poms was created only to contain poms that are:
1) Direct/indirect maven dependencies
2) Parent level poms with no corresponding jars (e.g.
  commons-parent.pom)

This this case, the package providing cvsclient.jar should provide the pom.