Yes, this is the project currently being built. It is Maven based Desktop app dependend on the common library. My procedure: 1) Clean and Build of common library 2) assembly:single of my Desktop app
Clean and build of my Desktop app before assembly:single doesn't help. I have almost the same POM file used for another project (no Java 7) and there is no similar warning using the same procedure as described above. It was the main reason why I initially suspected incompatibility in this area. If anybody interested, I can share my code. It is quite simple. Jan ---------- Původní zpráva ---------- Od: Wayne Fay <wayne...@gmail.com> Datum: 13. 2. 2013 Předmět: Re: Re: Assembly plugin - Java 7 classes are missing in the final JAR file "> [assembly:single] > Cannot include project artifact: in.drifted.documentation:xmlmodifier:jar: > 1.0; it doesn't have an associated file or directory. Is this project the one which is currently being built, or a dependency, or a parent, or what? Wayne --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org"
