Issue 38 Implement The Dependency Processor Lookup When A Model Type Is Installed
For modeshape-modeler-java and modeshape-modeler-xsd now created a "module-with-dependencies" jar. There is a problem with reading the XSD jar. Added more operation classes.
Issue Implement The Dependency Processor Lookup When A Model Type Is Installed
Fixed some errors and warnings.
Issue 38 Implement The Dependency Processor Lookup When A Model Type Is Installed
Adding more operations.
Some changes.
Copy test resources from the test project differently now. Moved tests out of modeshape-modeler-engine that were checking for specific dependency processors or desequences into either the modeshape-modeler-java or modeshape-modeler-xsd projects. All unit and integration tests are working on command-line and within Eclipse. Still have to replace use of shade plugin with the assembly plugin. Also now not making it a requirement to have a schema node under the XSD model node. In some cases the XSD model node will have the schema node mixin so there won't be a schema node.
Replaced maven shade plugin with the assemply plugin. The assembly plugin creates the extensions module-with-dependencies zip file and stores it in the test model type repository. Also fixed an issue in extension installer that prevented the potential extension classes from being found.
Adding more operations. Changed the XSD desequencer test from a unit test to an integration test. Had to do this because the test archive containing the XSD desequencer was not available yet when running unit tests.
Added a few more operations.
Added OperationFactory and concept of an operation descriptor.
Merge pull request #61 from elvisisking/38

Issue 38 Implement The Dependency Processor Lookup When A Model Type Is Installed