| Morning Dave - We were hoping to split the process, we would commit the updates to the original CDA plugins and then submit separately the schematron generation Do you think it will be a problem to keep the org.openhealth package names for the runtime cda packages (datatpes,cda) ? We can change project name, etc Who do we need to get involved ? Ken Rubin can probable speak for hl7 at least initially
As far as committing to master - just when i get used to branches - sure we can do that, I will look to delete the develop branch i created
Have we been “reviewing” the changes ? That part of the process i am still bit unsure of
thanks
Sean
Sean,
So, what have you decided on the process for updating eclipse git repo for 'cda' module? I have not done anything with the 'cda' module in eclipse git, as I thought you intended to submit a new copy of code for IP review??
OK, I will make changes to 'fhir' module for Java 1.8 and add MDHT format style settings. I am committing all changes to 'master', which is consistent with process I've seen on all other eclipse.org projects.
I've been looking into the attach-sources and attach-javadocs. I did not include these in each plugin pom, as I thought they were already in the module parent pom for 'core' and 'fhir'. I copied a subset of the module pom content from Papyrus. I see that they use tycho-source-plugin, which seems to have similar function as maven-source-plugin.
There is also a tycho documentation plugin that may have similar or improved functionality with the maven javadoc plugin?
We can add this to each module pom and should not need to add into each plugin pom.
Dave
mdht-dev mailing list
mdht-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/mdht-dev
|
