-
1. Re: Maven quickstart archetype fails: org.jacoco.agent not in repository?
cbrock Dec 31, 2011 1:07 PM (in response to dan.kazansky)Hmm. I'll look into this. Might not be able to get this resolved until after the new year, though.
-
2. Re: Maven quickstart archetype fails: org.jacoco.agent not in repository?
jfuerth Jan 2, 2012 1:57 PM (in response to dan.kazansky)This was my fault; embarrasingly, I thought I had already fixed this problem but I didn't wipe my local maven cache thoroughly enough to detect the problem you're reporting.
I will update jacoco-gwt-maven-plugin so it only depends on things in the JBoss repo and Maven Central. So if you can wait until tomorrow, it should "just work" if you try again.
To get things going right away, add the following to the pluginRepositories section of your new project's pom.xml. This is the repo where the missing snapshot dependencies can be downloaded from:
{code:xml}
<pluginRepository>
<id>jacoco-snapshot-repository</id>
<name>JaCoCo Snapshot Build Repository</name>
<url>https://oss.sonatype.org/content/repositories/snapshots</url>
<layout>default</layout>
</pluginRepository>
{code}
Jonathan
-
3. Re: Maven quickstart archetype fails: org.jacoco.agent not in repository?
jfuerth Jan 2, 2012 5:15 PM (in response to jfuerth)The jacoco-gwt-maven-plugin now only depends on stuff in the JBoss and Maven Central repositories. If you try your build again without any changes, it should work properly.
Sorry for the difficulties!
Jonathan
-
4. Re: Maven quickstart archetype fails: org.jacoco.agent not in repository?
dan.kazansky Jan 4, 2012 4:41 PM (in response to jfuerth)Is working now.
Thanks a lot!
-
5. Re: Maven quickstart archetype fails: org.jacoco.agent not in repository?
dan.kazansky Jan 4, 2012 8:42 PM (in response to dan.kazansky)I rush to say is was working, the project gets created but mvn gwt:run still fails.
Nevertheless, adding the plugin repo works fine.
(side note) I've just realized a
!-- Uncomment this to make mvn gwt:run work (you will see warnings about "complex dependency conflicts"
comment in the pom.xml
but the plugin repo works fine and it doesn't give me a "complex dependency conflicts" warning.
thanks