error upgrading aspectj-maven-plugin v1.8

Question

Upgrading the maven plugin from 1.7 to 1.8 results in the following error message:

[ERROR] 'dependencies.dependency.systemPath' for com.sun:tools:jar must specify an absolute path but is ${toolsjarSystemPath} @ pom.xml /ash-domain line 1

I found a bug in the plugin's Maven configuration and fixed it. Cross your fingers that my [pull request](https://github.com/mojohaus/aspectj-maven-plugin/pull/19) will get into the next release. — kriegaex, Sep 25 '16 at 12:44
Would you terribly mind accepting and upvoting my answer? This question is still listed as unanswered and my answer really solves the root cause of the problem, no workaround needed. — kriegaex, Oct 08 '19 at 02:07

tiagocorreia · Accepted Answer · 2017-07-21T12:08:26.370

13

I had the same problem and I've just added in eclipse.ini the path to the JDK8.
In my case:

-vm
C:\Program Files (x86)\Java\jdk1.8.0_60\bin\javaw.exe

(must be before -vmargs)

edited Jul 21 '17 at 12:08

answered Oct 19 '15 at 09:25

tiagocorreia

153
1
6

it should be accepted as correct answer. JDK usually asks by default to install a JRE together and eclipse uses by default JRE if you don't point it on eclipse.ini to use JDK/jre. – Frohlich Sep 23 '16 at 11:15
Nut that is a path to a JRE.. no JDK – Mariano L Feb 21 '17 at 16:21
Updated the path – tiagocorreia Jul 21 '17 at 12:08

score 9 · Answer 2 · answered Dec 04 '16 at 10:42

9

I found a problem in AspectJ Maven plugin and fixed it. My pull request was finally merged and is contained in the new plugin version 1.9. Just upgrade your POM and enjoy.

P.S.: The real problem is in Eclipse, but it was easier to put a workaround into the Maven plugin than to get it fixed upstream.

answered Dec 04 '16 at 10:42

kriegaex

63,017
15
111
202

2

I verify that Mojo's AspectJ Maven Plugin version 1.9 does NOT display the described error message using Eclipse 4.6 Neon with JDK 1.8 update 101. Thanks. – JasonTolotta Dec 05 '16 at 22:22
1

upgrading to AspectJ plugin 1.9 (from 1.8) in Spring Tool Suite 3.9 fixed my issue. Thanks. – CatsAndCode Aug 28 '17 at 18:22
1

More specifically, I updated my pom as follows (changed from 1.8 to 1.10) and this worked for me: org.codehaus.mojo aspectj-maven-plugin1.10 – Kt Mack Dec 07 '17 at 21:04

score 5 · Answer 3 · answered Jan 27 '16 at 09:04

5

I solved the problem in eclipse by adding toolsjarSystemPath as a default vm argument

Windows-->Preferences-->Java-->InstalledJREs-->EditJRE Add default vm argument: -DtoolsjarSystemPath=%JAVA_HOME%\lib\tools.jar

answered Jan 27 '16 at 09:04

Aviram

59
1
3

score 3 · Answer 4 · answered Jul 18 '16 at 09:28

3

I’m ashamed to admit that in my case this error was caused by wrong JAVA_HOME path: I point it out to jre, not jdk folder

answered Jul 18 '16 at 09:28

divideByZero

1,120
16
27

score 0 · Answer 5 · answered Oct 02 '21 at 01:18

If you're from command line, you need to have a parameter passed to the maven command with the absolute path of the $JAVA_HOME/lib/tools.jar

So, the thing would end something like this:

mvn -DtoolsjarSystemPath=$JAVA_HOME/lib/tools.jar clean

In my case even a simple clean was failing.

score 0 · Answer 6 · answered Nov 10 '22 at 08:51

I was facing the same issue. Went to check my build path and realised its due to a lack of Maven Dependency in the library table. I follow here: Missing Maven dependencies in Eclipse project and matter was resolved. So perhaps check if Maven is present in the build path.

error upgrading aspectj-maven-plugin v1.8

6 Answers6

Linked

Related