Hi:
Good morning. You are right. I forgot to clean and install a common build.
After I did that using jdk1.8, the errors for snapshot went away. Now, the
apache FOP is upset. These are software errors nothing to do with maven at
all. I need to refactor all the org.apache.xmlgraphics usages for usin
Hi,
Your previous error was about the snapshot policy, which the -U flag has
definitely solved. If you still hit an issue, it has to be a different
error, can you show what it is?
Guillaume
Le 18/10/2016 à 16:19, Gopal a écrit :
Hi:
I have cleaned out the repository, used the -U option and
Hi:
I have cleaned out the repository, used the -U option and still it will not
build with jdk 1.8
I am getting confused by this situation. It builds successfully with jdk 1.7
with no pom changes.
Is the jdk 1.8 compiler not happy?
Gopal
--
View this message in context:
http://maven.40175.n5
Hi,
The error you have is "... was cached in the local repository,
resolution will not be reattempted until the update interval of
Proper-Resolution has elapsed or updates are forced". The typical
resolution to this is to force Maven to update releases and snapshots
with the -U parameter. On
Hi:
I am not an expert at maven. Here's the scenario.
My entire project compiles without any errors under jdk1.7
I use artifactory to store common libraries. Under jdk 1.7, they got resolved
without any problems. All I did was to change the jdk from 1.7 to 1.8. I am
using intellij 2016. I
