Perhaps I wasn't clear. I've successfully created a complete plugin via the Maven archetype that does what I want...with one caveat. I need to implement a custom Preferences page.
Under the old architecture my actions/custom step were housed in a JAR that my installer delivered to bin\ext. Along with that were an actions XML file and a factories XML file delivered to the actions and factories directories respectively. Obviously the Plugin Manager greatly simplifies this.
This is my factories file:
<?xml version="1.0" encoding="UTF-8"?>
<tns:soapui-factories xmlns:tns="http://eviware.com/soapui/config">
<<tns:factory id="MyPrefs"
factoryType="com.eviware.soapui.actions.PrefsFactory"
factoryClass="com.mycompany.MyPrefsFactory"/>
</tns:soapui-factories>
As you can see, I have it working fine under the old architecture.
I'm trying to figure out how to get the PrefsFactory to be recognized by the new architecture. I tried building a folder structure in my Maven project but it didn't get picked up.
