title: Maven Iterator but Focus on one item
body: <p>So I have a unique problem based on a more-complicated-than-it-needs-to-be environment that is out of my control.</p>
  <p>I have been tasked to create a Maven application whose sole purpose is to take the files found under the resources directory and compile them into a zip file while filtering environment specific values into the copied file. Easy enough. I replicated the vendor's build process based on the little information I was allowed to have since they have a proprietary system.</p>
  <p>Now what I'd like to do it focus in on a particular item in this iteration and only build that item. My issue is I'm not using profiles at this time and was trying to find a way to use what I have to complete this action.</p>
  <p>Here is a simple mock up of my pom.xml file.</p>
  <pre><code>&lt;project xmlns=&quot;http://maven.apache.org/POM/4.0.0&quot;
      xmlns:xsi=&quot;http://www.w3.org/2001/XMLSchema-instance&quot;
      xsi:schemaLocation=&quot;http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd&quot;&gt;
      &lt;modelVersion&gt;4.0.0&lt;/modelVersion&gt;
      &lt;groupId&gt;com.im.special&lt;/groupId&gt;
      &lt;artifactId&gt;So-Special&lt;/artifactId&gt;
      &lt;version&gt;0.1&lt;/version&gt;
      &lt;packaging&gt;pom&lt;/packaging&gt;
  
      &lt;properties&gt;
          &lt;project.build.sourceEncoding&gt;UTF-8&lt;/project.build.sourceEncoding&gt;
          &lt;maven.compiler.source&gt;1.8&lt;/maven.compiler.source&gt;
          &lt;maven.compiler.target&gt;1.8&lt;/maven.compiler.target&gt;
      &lt;/properties&gt;
  
      &lt;dependencies&gt;
          &lt;dependency&gt;
              &lt;groupId&gt;com.soebes.maven.plugins&lt;/groupId&gt;
              &lt;artifactId&gt;iterator-maven-plugin&lt;/artifactId&gt;
              &lt;version&gt;0.5.1&lt;/version&gt;
          &lt;/dependency&gt;
          &lt;dependency&gt;
              &lt;groupId&gt;org.apache.maven.plugins&lt;/groupId&gt;
              &lt;artifactId&gt;maven-assembly-plugin&lt;/artifactId&gt;
              &lt;version&gt;3.3.0&lt;/version&gt;
          &lt;/dependency&gt;
      &lt;/dependencies&gt;
  
      &lt;build&gt;
          &lt;plugins&gt;
              &lt;plugin&gt;
                  &lt;groupId&gt;com.soebes.maven.plugins&lt;/groupId&gt;
                  &lt;artifactId&gt;iterator-maven-plugin&lt;/artifactId&gt;
                  &lt;version&gt;0.5.1&lt;/version&gt;
                  &lt;executions&gt;
                      &lt;execution&gt;
                          &lt;phase&gt;package&lt;/phase&gt;
                          &lt;goals&gt;
                              &lt;goal&gt;iterator&lt;/goal&gt;
                          &lt;/goals&gt;
                          &lt;configuration&gt;
                              &lt;itemsWithProperties&gt;
                                  &lt;itemWithProperty&gt;
                                      &lt;name&gt;DEV&lt;/name&gt;
                                      &lt;properties&gt;
                                          &lt;prop.one&gt;Some&lt;/prop.one&gt;
                                          &lt;prop.two&gt;Unique&lt;/prop.two&gt;
                                          &lt;prop.eh&gt;Values&lt;/prop.eh&gt;                                        
                                      &lt;/properties&gt;
                                  &lt;/itemWithProperty&gt;
                                  &lt;itemWithProperty&gt;
                                      &lt;name&gt;DEV2&lt;/name&gt;
                                      &lt;properties&gt;
                                          &lt;prop.one&gt;More&lt;/prop.one&gt;
                                          &lt;prop.two&gt;Unique&lt;/prop.two&gt;
                                          &lt;prop.eh&gt;Values&lt;/prop.eh&gt;                                        
                                      &lt;/properties&gt;
                                  &lt;/itemWithProperty&gt;
                              &lt;/itemsWithProperties&gt;
                              &lt;pluginExecutors&gt;
                                  &lt;pluginExecutor&gt;
                                      &lt;goal&gt;single&lt;/goal&gt;
                                      &lt;plugin&gt;
                                          &lt;artifactId&gt;maven-assembly-plugin&lt;/artifactId&gt;
                                          &lt;version&gt;3.3.0&lt;/version&gt;
                                      &lt;/plugin&gt;
                                      &lt;configuration&gt;
                                          &lt;descriptors&gt;
                                              &lt;descriptor&gt;src/main/assembly/assembly.xml&lt;/descriptor&gt;
                                          &lt;/descriptors&gt;
                                      &lt;/configuration&gt;
                                  &lt;/pluginExecutor&gt;
                              &lt;/pluginExecutors&gt;
                          &lt;/configuration&gt;
                      &lt;/execution&gt;
                  &lt;/executions&gt;
              &lt;/plugin&gt;
          &lt;/plugins&gt;
      &lt;/build&gt;
  
  &lt;/project&gt;
  </code></pre>
  <p>Let's assume I have way more items specified than the two here and those items have more properties than I have defined as well. The current assembly plugin produces exactly what I need; one compilation of resources for each item with properties with the appropriate filtered files and it's beautiful.</p>
  <p>Now, the wrench. How would I go about or is it even possible to run this build structured the way it is for only one of the items in the defined list. My example scenario is this:</p>
  <ul>
  <li>I'm processing the list items for their relative environments and
  then deploy those compiled items to the appropriate environment.</li>
  <li>I am then asked to regenerate a compiled artifact for DEV because someone
  deleted the file because; why not.</li>
  <li>I now need to change my workspace to my latest tag and run the
  process for one item based on time constraints and priority. Running all would
  take to long and I have SLAs to meet.</li>
  </ul>
  <p>I know if I was using profiles my pom would be different and I could simply <code>mvn clean package -PDEV</code> and go about my day. Unfortunately that's not my build process and I am looking to see if I need to create a completely different process in case my request is not viable.</p>
  <p>Also; not having so many env.properties files is nice because all my maintenance is in the pom.xml and not across multiple files.</p>