First this is a great project; I'm trying to integrate it into a data migration effort and things, for the most part, are working out great.
However, I've got my own components that I need to register. The component xml file is included in my built jar file, so it is in the class path.
The ComponentDescriptionReader has the functionality I could use (the getComponentDescriptions(InputStream inputStream) method), but the member function(s) are all declared as private. They are therefore inaccessible from an external entity or a subclass.
Please change the visibility from private to at least protected (for subclass access) or expose the getComponentDescriptions(InputStream inputStream) as a public method.
However, I've got my own components that I need to register. The component xml file is included in my built jar file, so it is in the class path.
The ComponentDescriptionReader has the functionality I could use (the getComponentDescriptions(InputStream inputStream) method), but the member function(s) are all declared as private. They are therefore inaccessible from an external entity or a subclass.
Please change the visibility from private to at least protected (for subclass access) or expose the getComponentDescriptions(InputStream inputStream) as a public method.
-
Hello Dave!
As you wich, in next clover update 1.9.1 method getComponentDescriptions (InputStream inputStream) will be public.
Nevertheless, new clover version 2.0 will be released soon. As was mentioned, new plugins framework is right now in testing process and solve probably a lot of problems like this. For example custom components can be distributed as separate jar file same as eclipse plugin.
OtaSanek
Please sign in to leave a comment.
Comments 1