ArmorMain
A model written in C++ intended to represent the use of legacy models in the ARRoW environment.

The project is incorporated into a mvn pom so it can be deployed to the CML repository.

A custom assembly is defined in src/main/assembly/src.xml

I put src/bin in as a place to put the resultant executable.

'mvn  install' will package the projct as a zip and put it in the local mvn repo.

'$ mvn -gs cml_settings.xml deploy' will deploy it to the artifactory server.

UsesArmorMain:
The pom includes an ArmorMain Dependency.

  <!-- mvn dependency:unpack-dependencies -->
  <!--  How do I bind dependency:unpack-dependencies to a goal like compile? -->
  	<dependency>
  		<groupId>com.bae.meta.arrow</groupId>
  		<artifactId>ArmorMain</artifactId>
  		<version>0.0.1-SNAPSHOT</version>
  		<type>zip</type>
  		<classifier>bin</classifier>
  		<scope>compile</scope>
  	</dependency>
  	
Issuing 'mvn dependency:unpack-dependencies' will unpack ArmorMain<foo>.zip into target/dependency.
I fixed the pom so that 'mvn package' will do the same.


The story of ArmorMain:
ArmorMain is a legacy model written in C++. It needs to be available for use in the composition of other ARRoW Projects.
To be found, it needs to be in the Component Model Library and have enough information about itself to be found in some search.
Maybe it has a description; "Armor Thickness Model". Maybe its method signature is searchable; "Thickness, projectile, angle, energy".
To be used in an ARRoW Project it needs to have a unique identifier, and include enough information on how to be executed.

Identifier: maven coordinate tripple.
Invocation: some amil fragment, which tells what arguments it takes?
ArrowMetaData: I think we can put a src/main/arrow directory in the project for arrow files; META data, node info, whatever.



Tim points out no user should likely know about ArmorMain. He thinks that the model would be ArmorThickness or ArmorProtection.
It is a model we need to support building a vehicle. But I don't know what this model would look like in ARRoW.

For the time being focus on getting something into a mvn repo, getting it out, and executing it.