Saptarshi, At first thought I'd say that we should have the same rules for the maven repo as we have for the module repo. I.e. we allow people to publish omods without sharing the source, so we should do the same with jars and maven.
-Darius (by phone) On Jan 20, 2012 10:55 AM, "Saptarshi Purkayastha" <[email protected]> wrote: > I wanted to put a slightly different question to the list though. > How do we organize the artifacts that do not have the source code present > in our repository. > Although these should be added to the 3rd party repository... I think we > should also mandate that *src.jar should also be submitted to the maven > repo. > > Does everyone agree to this?? > > --- > Regards, > Saptarshi PURKAYASTHA > > My Tech Blog: http://sunnytalkstech.blogspot.com > You Live by CHOICE, Not by CHANCE > > > On 20 January 2012 20:58, Burke Mamlin <[email protected]> wrote: > >> FWIW, this was discussed on a dev forum a while ago. We unfortunately >> don't have OpenMRS ID tied into the maven repo, so maven repo privs need to >> be managed separately. Any dev who submits an ITSM ticket requesting >> access to the repo will get it. I think Saptarshi was going to document >> how to add artificacts to the repo. >> >> -Burke >> >> >> On Fri, Jan 20, 2012 at 9:54 AM, Mark Goodrich <[email protected]> wrote: >> >>> IMO, whenever a new version of a “core” module is released (mavenized or >>> unmavenized), the module developer should be responsible for uploading the >>> latest version of the jar(s) (not the omod) to the maven repo.**** >>> >>> ** ** >>> >>> For mavenized modules, this can be done using a mvn deploy. For >>> non-mavenized modules, the jar needs to be installed manually. **** >>> >>> ** ** >>> >>> It was discussed a few months back who should have access to upload jars >>> to the maven repo, and it was decided (I believe) that core developers >>> should be given access upon request. I requested access, and am now able >>> to deploy mavenized modules using mvn deploy. However, I still cannot >>> install jar manually (via the steps listed in the link below) because the >>> “Artifact Upload” option is still not available to me on the maven repo. I >>> followed up about this, and I believe the response from Michael (don’t want >>> to misquote him) was that the mavenrepo had numerous levels of permissions, >>> and that we still need to figure out exactly who should have what >>> permissions. To my knowledge, nothing has been done since then.**** >>> >>> ** ** >>> >>> So the current process to post a non-mavenized module to the repo is to >>> enter a TODO ticket for Saptarshi and attach the jar. I still believe that >>> core developers should be able to do this directly, but Saptarshi has been >>> very responsive to getting modules installed for me.**** >>> >>> ** ** >>> >>> More documentation can be found here:**** >>> >>> https://wiki.openmrs.org/display/docs/Managing+the+Maven+Repository**** >>> >>> * * >>> >>> *Take care,* >>> >>> *Mark* >>> >>> * * >>> >>> *From:* [email protected] [mailto:[email protected]] *On Behalf Of *Rowan >>> Seymour >>> *Sent:* Friday, January 20, 2012 8:54 AM >>> *To:* [email protected] >>> *Subject:* Re: [OPENMRS-DEV] Maven repo additions: reporting and >>> Jembi's SDMX-HD library**** >>> >>> ** ** >>> >>> 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]> 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]] *On Behalf Of *Rowan >>> Seymour >>> *Sent:* Friday, January 20, 2012 5:34 AM >>> *To:* [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<[email protected]?body=SIGNOFF%20openmrs-devel-l>from >>> OpenMRS Developers' mailing list >>> **** >>> ------------------------------ >>> >>> Click here to >>> unsubscribe<[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<[email protected]?body=SIGNOFF%20openmrs-devel-l>from >>> OpenMRS Developers' mailing list >>> **** >>> ------------------------------ >>> Click here to >>> unsubscribe<[email protected]?body=SIGNOFF%20openmrs-devel-l>from >>> OpenMRS Developers' mailing list >>> >> >> > ------------------------------ > Click here to > unsubscribe<[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]
