2010/4/27 Deepak Bhole <dbhole(a)redhat.com>:
> Agreed that the right place for the pom is with the package
providing the jar;
> so my plan is:
> * install the pom in maven-scm temporarily
> * watch progress on netbeans-ide
> * ask to move the pom there when cvsclient is extracted as a subpackage
> and update maven-scm
>
Ah, in that case you might be better off putting it in
maven2-common-poms ...
Take a look at maven-scm spec:
http://cvs.fedoraproject.org/viewvc/rpms/maven-scm/devel/maven-scm.spec?v...
It is already downloading the cvsclient pom for the build, ( "123: #
Doing this here means we
don't have to modify the netbeans package " ); so i think its better
to have just one place
to fix against two.
.. Sorry, I forgot that maven-scm is a direct
dependency of maven2. I see no harm in putting the pom in common-poms.
That rpm already contains poms of indirect maven deps.
Sorry i dont get the implications of being a direct dep; do you mean
it will require a maven2 rebuild? Just bumping the release and adding a file
should not require that.
Thanks for your time!
--
Guido Grazioli <guido.grazioli(a)gmail.com>
Via Parri 11 48011 - Alfonsine (RA)
Mobile: +39 347 1017202 (10-18)
Key FP = 7040 F398 0DED A737 7337 DAE1 12DC A698 5E81 2278
Linked in:
http://www.linkedin.com/in/guidograzioli