[
https://jira.jboss.org/browse/TEIIDDES-449?page=com.atlassian.jira.plugin...
]
John Verhaeg commented on TEIIDDES-449:
---------------------------------------
I still see one warning about a deprecated attribute being using in the plugin.xml, and 2
related to code (which I presume will be the ones fixed by TEIIDDES-451). The API
Baseline thing is a real PITA. I've done this myself accidentally in the past, and it
was difficult to get rid of, but I did eventually succeed. I don't remember how I did
it, but I'll try to do some more research. We shouldn't have to do anything
special with our preferences.
Data tools plug-ins have lots of warnings that need to be addressed
-------------------------------------------------------------------
Key: TEIIDDES-449
URL:
https://jira.jboss.org/browse/TEIIDDES-449
Project: Teiid Designer
Issue Type: Task
Affects Versions: 7.0
Reporter: John Verhaeg
Assignee: John Doyle
Fix For: 7.0
I cleaned up some of the warnings, but there are 3 types left that John Doyle needs to
address:
1) The most prevalent warnings are about strings that haven't been externalized in
the code, the plugin.xml, and the MANIFEST.MF. All of these need to be internationalized
or, if not applicable, marked with NLS tags
2) A couple of the attributes specified in the plugin.xml have been deprecated.
3) There are 2 warnings about API baselines not being set on the project. Not sure how
or why the API tooling nature got set on these projects, but I removed the nature and
builders from the .projects files, along with the .externalBuilder... folders, but still
see the warnings for some reason.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira