Closed Digo closed 6 years ago
I'm actually working on that right now. We can discuss it after tomorrow's meeting. On Jul 16, 2013 1:47 PM, "Di Wang" notifications@github.com wrote:
I would like to create an OA maven parent project for : 1) importing common dependencies and plugins 2) better managing dependency versions and plugin goals
What do you think?
— Reply to this email directly or view it on GitHubhttps://github.com/oaqa/uima-ecd/issues/18 .
Sure.
I am sure @CollinM would have a lot to say about the documentation of the project and maintainability.
I think we should discuss this more in depth tomorrow.
But, to the point, it would be useful to standardize a few common dependencies (mysql connector, etc) and the plugins for resource inclusion and documentation. Having standard goals for build, install, and deploy (both local and remote) would certainly ease some of our development pains.
Wait. MySQL connector is only about only option for persisting stuffs, which is not required at least at CSE or ECD level.
Another thing is that since this artifact will obviously become the very fundamental one for the whole open source project, I assume it will be hosted by sonatype and indexed by the central repo. I hope some maintenance guideline could be discussed as well tomorrow.
On 07/16/2013 06:51 PM, Collin McCormack wrote:
I think we should discuss this more in depth tomorrow.
But, to the point, it would be useful to standardize a few common dependencies (mysql connector, etc) and the plugins for resource inclusion and documentation. Having standard goals for build, install, and deploy (both local and remote) would certainly ease some of our development pains.
— Reply to this email directly or view it on GitHub https://github.com/oaqa/uima-ecd/issues/18#issuecomment-21080168.
Can someone look into the principles behind structuring a parent POM? I.e. what should go in it, what shouldn't go in it, and why?
I am very glad @CollinM has brought it up, which has struggled me since last year Rui and I were TAing the course.
On 07/16/2013 08:33 PM, Collin McCormack wrote:
Can someone look into the principles behind structuring a parent POM? I.e. what should go in it, what shouldn't go in it, and why?
— Reply to this email directly or view it on GitHub https://github.com/oaqa/uima-ecd/issues/18#issuecomment-21084471.
Sorry, should me "I has been struggling against it" instead of "it has struggled me"...
I would like to create an OA maven parent project for : 1) importing common dependencies and plugins 2) better managing dependency versions and plugin goals
What do you think?