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
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
We use the target folder as the Eclipse output. The only risk I can think
of is that CLI builds may cause Eclipse to rebuild, possibly while the CLI
build is occurring. Obviously if the build output is different (e.g.
different profiles) then you could have weird results.
On 25 May 2016 at 10:16,
I've also been using the same output dir with both for many years. The
only hassle I've encountered is the rare need to clean build in Eclipse (I
think only occasionally after a "mvn clean ..."). Otherwise, they
cohabitate well.
On Wed, May 25, 2016 at 9:34 AM, Matthew Piggott
wrote:
> We use
It doesn't matter whether this directory is called "bin" or "target",but it should be the same for Eclipse and Maven, says Igor Fedorenko:https://dev.eclipse.org/mhonarc/lists/m2e-users/msg05030.html> Are there> specific issues or risks with having Eclipse write classes into the same> location as t
For a while I've been struggling with an issue where I see the search
facility in the "Add" dialog offering some artifacts that are "jar"
artifacts, and some that are "bundle" artifacts. I know the basic
difference between them. The funny thing is, I believe that these
artifacts are all struc
Type is actually determined only by the packaging of the referenced artifact’s
pom. Therefore m2e behaves 100% correct.
Whether a JAR (or more accurate, the manifest within) actually contains OSGi
specific headers doesn’t matter here.
Just as a side note:
Actually, even if the type is set to bun
On 05/25/2016 10:54 AM, Konrad Windszus wrote:
Type is actually determined only by the packaging of the referenced artifact’s
pom. Therefore m2e behaves 100% correct.
Whether a JAR (or more accurate, the manifest within) actually contains OSGi
specific headers doesn’t matter here.
Just as a si
