title: java.lang.IllegalStateException: endPosTable already set
body: <p>Trying to build an alexa (amazon:echo) skills set. At the same time, trying to use this experience as a learning testbed for dependency injection through dagger 2. However, building the package using maven-2 cmd:</p>
  
  <pre><code>mvn assembly:assembly -DdescriptorId=jar-with-dependencies package'. 
  </code></pre>
  
  <p>to generate a zip jar with the complete dependencies produces the following exception trace:</p>
  
  <pre><code>[INFO] ------------------------------------------------------------------------
  [INFO] Building Echo Device Client 1.0
  [INFO] ------------------------------------------------------------------------
  [INFO] 
  [INFO] --- maven-resources-plugin:2.6:resources (default-resources) @ echo-device-client ---
  [WARNING] Using platform encoding (UTF-8 actually) to copy filtered resources, i.e. build is platform dependent!
  [INFO] skip non existing resourceDirectory /Users/apil.tamang/Dropbox/Git/echo-device-client/src/main/resources
  [INFO] 
  [INFO] --- maven-compiler-plugin:3.3:compile (default-compile) @ echo-device-client ---
  [INFO] Changes detected - recompiling the module!
  [WARNING] File encoding has not been set, using platform encoding UTF-8, i.e. build is platform dependent!
  [INFO] Compiling 46 source files to /Users/apil.tamang/Dropbox/Git/echo-device-client/target/classes
  An exception has occurred in the compiler (1.8.0_60). Please file a bug at the Java Bug Database (http://bugreport.java.com/bugreport/) after checking the database for duplicates. Include your program and the following diagnostic in your report.  Thank you.
  java.lang.IllegalStateException: endPosTable already set
          at com.sun.tools.javac.util.DiagnosticSource.setEndPosTable(DiagnosticSource.java:136)
          at com.sun.tools.javac.util.Log.setEndPosTable(Log.java:350)
          at com.sun.tools.javac.main.JavaCompiler.parse(JavaCompiler.java:667)
          at com.sun.tools.javac.main.JavaCompiler.parseFiles(JavaCompiler.java:950)
          at com.sun.tools.javac.processing.JavacProcessingEnvironment$Round.&lt;init&gt;(JavacProcessingEnvironment.java:892)
          at com.sun.tools.javac.processing.JavacProcessingEnvironment$Round.next(JavacProcessingEnvironment.java:921)
          at com.sun.tools.javac.processing.JavacProcessingEnvironment.doProcessing(JavacProcessingEnvironment.java:1187)
          at com.sun.tools.javac.main.JavaCompiler.processAnnotations(JavaCompiler.java:1170)
          at com.sun.tools.javac.main.JavaCompiler.compile(JavaCompiler.java:856)
          at com.sun.tools.javac.main.Main.compile(Main.java:523)
          at com.sun.tools.javac.api.JavacTaskImpl.doCall(JavacTaskImpl.java:129)
          at com.sun.tools.javac.api.JavacTaskImpl.call(JavacTaskImpl.java:138)
  </code></pre>
  
  <p>The initial compilation happens fine, and all tests are run and successfully executed. I feel like it is during 'linking' the dependencies that things go south. Please take a look at <a href="https://www.dropbox.com/s/7gaiza6utkrrag9/echo_build.txt?dl=0" rel="noreferrer">this file</a> to see the console output during the build.</p>
  
  <p>My question is if it's worth a shot to try generate the dependencies using a different way. I don't know much about maven for that purpose. Is there a patch or something out there that can be used? Do you think it's even possible to come up with a workaround? I would like to be able to continue to use the dagger 2 framework for building this project. </p>