We're using "target" as the output both with Eclipse builds and with straight Maven builds and haven't encountered any significant problems with that. If we do the command line build we may have to refresh the projects in Eclipse so that it knows about the files, but that's it.
Art Kaufmann Chief Architect, IRIS (Traceability Server) "The life so short, the craft so long to learn" "By hammer and hand do all things stand" 3960 Fabian Way Palo Alto, CA 94303 art.kaufm...@frequentz.com www.frequentz.com O: (650)397-2553 M: (310)418-8410 *This E-mail and its attachments may contain proprietary and/or confidential information belonging to Frequentz, LLC. Dissemination and copying of this E-mail is strictly prohibited. This E-mail is intended solely for the use of the individual and entity to which it is addressed. If you have received this E-mail in error, please notify the sender immediately and delete the original and any copies.* On Wed, May 25, 2016 at 7:09 AM, David M. Karr <davidmichaelk...@gmail.com> wrote: > I've always been under the impression that Eclipse Maven projects should > write their classes (from Eclipse) into the default "bin" and not share the > same output folder as the command line build, using "target". However, > I've never had definite information about this. Are there specific issues > or risks with having Eclipse write classes into the same location as the > command-line build? > _______________________________________________ > m2e-users mailing list > m2e-users@eclipse.org > To change your delivery options, retrieve your password, or unsubscribe > from this list, visit > https://dev.eclipse.org/mailman/listinfo/m2e-users >
_______________________________________________ m2e-users mailing list m2e-users@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/m2e-users
