2010/4/26 Deepak Bhole <dbhole(a)redhat.com>
* Guido Grazioli <guido.grazioli(a)gmail.com> [2010-04-25
06:30]:
> 2010/4/22 Deepak Bhole <dbhole(a)redhat.com>
> Ok, let me recapitulate to know if im doing it right. I have a maven-release
> parent pom, defining two modules maven-release-manager and
> maven-release-plugin,
> one depending on the other.
> - maven-release pom (no jar) goes to maven-common-poms
> - from the sources i build two rpms (actually two distinct package reviews) and
> make them buildrequire maven-common-poms
The parent pom should then go into a maven-release package which
installs only the pom.
Got it; i put my specfile for maven-release here:
http://guidograzioli.fedorapeople.org/packages/maven-release/
i'll be glad if anyone would take a look on it, as it's a bit messy.
Installing a pom does not necessitate requiring maven. There are
many
ant built packages that install a pom. As long as the
add_to_maven_depmap and update_maven_depmap macros are run, it should be
fine.
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
cheers,
--
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