[
https://issues.apache.org/jira/browse/OODT-29?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Woollard updated OODT-29:
-------------------------------
Attachment: xmlps.rat.txt
pom.xml
Regarding RAT, there was some discussion on the email list regarding its use
and you'll notice that we actually only incorporated for the sub-projects that
have already been vetted for licensing issues. If you want, while importing
code, you can not include it as part of the pom file (or comment it out).
I applied the patch and looked specifically at the licensing and it all looks
good save the two example files you have. I have also attached a modified pom
file that includes an exclude statement that will allow RAT to ignore the two
example files.
As an alternative, you can add licensing info to the examples. The only reason
we have not added it to other examples is when the addition would adversely
effect the use of the example.
-Dave
> Import (ERNE) XMLPS component
> -----------------------------
>
> Key: OODT-29
> URL: https://issues.apache.org/jira/browse/OODT-29
> Project: OODT
> Issue Type: New Feature
> Components: product server, profile server
> Environment: XML configurable Product- and Profile- server package
> for connecting to databases
> Reporter: Dave Kale
> Fix For: 0.1-incubating
>
> Attachments: oodt-xmlps+grid_ignore_target.diff, pom.xml,
> xmlps.rat.txt
>
> Original Estimate: 120h
> Remaining Estimate: 120h
>
> Another CHLA/JPL motivated task. Many of our data sources reside in
> databases (welcome to health IT...everything lives in normalized M$ SQL
> servers). The XMLPS package from ERNE makes it easy to deploy rapidly
> product servers, profile servers, and query handlers by separating the
> mechanisms for setting up connections, parsing queries, etc. (which lives in
> java code) from the data definitions, i.e., table names, field names, etc.
> (which are defined in XML-based configuration files). This probably requires
> the web-grid component, as well.
> In fact, I am almost done with this task! I have ported the code to the
> apache namespace and removed or generalized ERNE-specific naming conventions.
> The following remains to be done:
> 1. Add apache license headers.
> 2. New unit tests that aren't dependent on details specific to the ERNE
> project.
> 3. Testing.
> I think I can finish it by the end of next week.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
