I think the issue is less about "getting reporting mavenized" and more about empowering those who actually release new versions of modules to be able to update Nexus with their artifacts. As far as I know, this privilege is still restricted to a privileged few (as Rowan writes below, asking for help in a mysterious TODO ticket). Reporting does not need to be mavenized for me to create a jar and omod and put these on Nexus. But I need the privileges and processes documented to do so...

Mike


On 01/20/2012 08:53 AM, Rowan Seymour wrote:
I think I'm doing more complaining than actually fixing the problem...

Maybe we can have a special Mavenization Day...

It would be great to see this mavenization thing through - though I'm not sure we've found a satisfactory process for getting things deployed in the main OpenMRS maven repo - Saptarshi ends up doing it all it seems

On 20 January 2012 14:53, Friedman, Roger (CDC/CGH/DGHA) (CTR) <[email protected] <mailto:[email protected]>> wrote:

    Rowan --

        Thanks for a great contribution.  I think it would be great in
    conjunction with 1.10 if we went through all the modules,
    determined which ones were used or had potential, make sure they
    are mavenized under the appropriate model, and get them and their
    jars in the repo.  I know this is a little outside our current
    policy re modules but it would reduce the burden to new developers
    if everything was in the expected form.  Also, the current policy
    doesn't really reflect the goal of being more deployable out of
    the box.

        If we are moving to git, it might be a good moment to do that
    as well.

    *From:*[email protected] <mailto:[email protected]>
    [mailto:[email protected] <mailto:[email protected]>] *On Behalf Of
    *Rowan Seymour
    *Sent:* Friday, January 20, 2012 5:34 AM
    *To:* [email protected]
    <mailto:[email protected]>
    *Subject:* [OPENMRS-DEV] Maven repo additions: reporting and
    Jembi's SDMX-HD library

    I always wondered what "TODO tickets" were until I just discovered
    there's a JIRA project called TODO.. anyway...

    I just mavenized the SDMX-HD Integration module. This has two
    dependencies that need to end up in a Maven repository

    1. Reporting - is there a plan for this to be mavenized? In the
    interim I put the .omod in my local repo as follows

    mvn install:install-file -DgroupId=org.openmrs.module
    -DartifactId=reporting -Dversion=0.7.0 -Dfile=reporting-0.7.0.omod
    -Dpackaging=jar -DgeneratePom=true

    2. Jembi's SDMX-HD library. I assume this can belong in the
    OpenMRS maven repo? I've created a TODO and attached the JAR that
    was bundled in this module. Maybe Ryan or someone from Jembi
    should comment on whether these POM fields work for them:

    <dependency>

    <groupId>jembi</groupId>

    <artifactId>sdmx-hd</artifactId>

    <version>0.3.2</version>

    </dependency>

    https://tickets.openmrs.org/browse/TODO-30

    Rowan

    ------------------------------------------------------------------------

    Click here to unsubscribe
    <mailto:[email protected]?body=SIGNOFF%20openmrs-devel-l> from
    OpenMRS Developers' mailing list

    ------------------------------------------------------------------------
    Click here to unsubscribe
    <mailto:[email protected]?body=SIGNOFF%20openmrs-devel-l> from
    OpenMRS Developers' mailing list




--
*Rowan Seymour*
tel: +250 783835665
http://twitter.com/rowanseymour

------------------------------------------------------------------------
Click here to unsubscribe <mailto:[email protected]?body=SIGNOFF%20openmrs-devel-l> from OpenMRS Developers' mailing list

_________________________________________

To unsubscribe from OpenMRS Developers' mailing list, send an e-mail to 
[email protected] with "SIGNOFF openmrs-devel-l" in the  body (not 
the subject) of your e-mail.

[mailto:[email protected]?body=SIGNOFF%20openmrs-devel-l]

Reply via email to