I am using Eclipse Luna (v4.4) and I am using the latest version of m2e
using the official update site
(|http://download.eclipse.org/technology/m2e/releases|).
The auto-build option should be enabled by default but anyway this is
enabled in my Eclipse too.
If you check out the trunk, does it build without any further changes in
the settings or something?
I don't want to modify the pom.xml since I intend to stay in sync with
all changes that is going to be made in the trunk folder.
Best regards,
Stefan
On 2015-01-25 19:27, Maruan Sahyoun wrote:
Hi Stefan
I'm using Eclipse 4.4 and for Maven integration m2e 1.5.0. Normally I build
from the command line but doing it from Eclipse works too. I've enabled the
Java Builder in the Projects Properties in Eclipse to get an automatic rebuild
whenever I do changes so errors are reflected in the GUI directly.
BR
Maruan
Am 25.01.2015 um 16:37 schrieb Stefan Falk <[email protected]>:
That would be great!
But don't you use a plugin for the project integration? Or do you build the
project from command line and import the single projects manually?
Best regards,
Stefan
On 2015-01-25 16:34, Maruan Sahyoun wrote:
Hi Stefan - I'm using Eclipse and Maven to build PDFBox - can send you my
configuration later today
Maruan Sahyoun
Am 25.01.2015 um 16:27 schrieb Stefan Falk <[email protected]>:
Alright I think I'll use another building tool
Can you recommend a plugin that should work "on the fly" with the pdfbox
project?
I do not necessarily have to use m2e ..
Thank you!
Best regards, Stefan
On 2015-01-24 13:46, Tilman Hausherr wrote:
Am 24.01.2015 um 13:03 schrieb Stefan Falk:
Isn't here anybody else who has built pdfbox in Eclipse?
to which should be added "with m2e". Assuming the JCE problem is now a low
priority and the eclipse problem is a high priority, please attach the current log unless
it's the same you attached to your SO post:
https://stackoverflow.com/questions/28087186/
Re m2e "Plugin execution not covered by lifecycle configuration", I found this:
https://stackoverflow.com/questions/6352208/how-to-solve-plugin-execution-not-covered-by-lifecycle-configuration-for-sprin
The best answer here was to introduce "<pluginManagement>" which is already
done.
*
*The 2nd best answer here was to switch to the Apache Eclipse plug-in
<http://maven.apache.org/plugins/maven-eclipse-plugin/>.
The 3rd best answer mentions some background on your error message "Plugin execution
not covered by lifecycle configuration" and points to this:
https://www.eclipse.org/m2e/documentation/m2e-execution-not-covered.html
although I guess it's complex stuff like this what would probably make me
switch to a different tool, i.e. m2e is more part of the problem than part of
the solution.
Tilman
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
