Re: maven build broken with jdk1.8

2016-10-19 Thread Gopal
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 using the
latest version FOP2.1 ...

Thanks for listening to me and helping me narrow down the error and replying
to my message,
Gopal



--
View this message in context: 
http://maven.40175.n5.nabble.com/maven-build-broken-with-jdk1-8-tp5883777p5883917.html
Sent from the Maven - Users mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org



Re: maven build broken with jdk1.8

2016-10-18 Thread Guillaume Boué

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 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.nabble.com/maven-build-broken-with-jdk1-8-tp5883777p5883871.html
Sent from the Maven - Users mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org




---
L'absence de virus dans ce courrier électronique a été vérifiée par le logiciel 
antivirus Avast.
https://www.avast.com/antivirus


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org



Re: maven build broken with jdk1.8

2016-10-18 Thread Gopal
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.nabble.com/maven-build-broken-with-jdk1-8-tp5883777p5883871.html
Sent from the Maven - Users mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org



Re: maven build broken with jdk1.8

2016-10-17 Thread Guillaume Boué

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 the command line, you would do "mvn -U clean 
package".


To do it inside IntelliJ, you can probably refer to this Stack Overflow 
question 
http://stackoverflow.com/questions/9980869/force-intellij-idea-to-reread-all-maven-dependencies.


Guillaume,


Le 17/10/2016 à 17:16, Gopalakrishnan, Gopal (CORP) a écrit :

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 change the jdk version using
Run --> Edit Configuration -- > select the maven configuration --> Runner tab 
--> 1.8

However, if change the jdk to jdk 1.8

I get errors on dependency resolution ...

[ERROR] Failed to execute goal on project modulecore: Could not resolve 
dependencies for project com.adp.sass:modulecore:jar:1.0.0-SNAPSHOT: Failed to 
collect dependencies at com.adp.sass:sasscommon:jar:1.0.0-SNAPSHOT: Failed to read 
artifact descriptor for com.adp.sass:sasscommon:jar:1.0.0-SNAPSHOT: Failure to 
find com.adp.sass:sassbuild:pom:1.0.0 in 
http://avsf-depsvr01:8082/artifactory/Proper-Resolution was cached in the local 
repository, resolution will not be reattempted until the update interval of 
Proper-Resolution has elapsed or updates are forced -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal 
on project modulecore: Could not resolve dependencies for project 
com.adp.sass:modulecore:jar:1.0.0-SNAPSHOT: Failed to collect dependencies at 
com.adp.sass:sasscommon:jar:1.0.0-SNAPSHOT
 at 
org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.getDependencies(LifecycleDependencyResolver.java:221)
 at 
org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.resolveProjectDependencies(LifecycleDependencyResolver.java:127)
 at 
org.apache.maven.lifecycle.internal.MojoExecutor.ensureDependenciesAreResolved(MojoExecutor.java:245)
 at 
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:199)
 at 
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
 at 
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
 at 
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
 at 
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
 at 
org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
 at 
org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
 at 
org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307)
 at 
org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193)
 at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106)
 at org.apache.maven.cli.MavenCli.execute(MavenCli.java:863)
 at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288)
 at org.apache.maven.cli.MavenCli.main(MavenCli.java:199)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
 at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
 at java.lang.reflect.Method.invoke(Method.java:498)
 at 
org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
 at 
org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
 at 
org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
 at 
org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
 at org.codehaus.classworlds.Launcher.main(Launcher.java:47)
Caused by: org.apache.maven.project.DependencyResolutionException: Could not 
resolve dependencies for project com.adp.sass:modulecore:jar:1.0.0-SNAPSHOT: 
Failed to collect dependencies at com.adp.sass:sasscommon:jar:1.0.0-SNAPSHOT
 at 
org.apache.maven.project.DefaultProjectDependenciesResolver.resolve(DefaultProjectDependenciesResolver.java:180)
 at 
org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.getDependencies(LifecycleDependencyResolver.java:195)
   

maven build broken with jdk1.8

2016-10-17 Thread Gopalakrishnan, Gopal (CORP)
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 change the jdk version using
Run --> Edit Configuration -- > select the maven configuration --> Runner tab 
--> 1.8

However, if change the jdk to jdk 1.8

I get errors on dependency resolution ...

[ERROR] Failed to execute goal on project modulecore: Could not resolve 
dependencies for project com.adp.sass:modulecore:jar:1.0.0-SNAPSHOT: Failed to 
collect dependencies at com.adp.sass:sasscommon:jar:1.0.0-SNAPSHOT: Failed to 
read artifact descriptor for com.adp.sass:sasscommon:jar:1.0.0-SNAPSHOT: 
Failure to find com.adp.sass:sassbuild:pom:1.0.0 in 
http://avsf-depsvr01:8082/artifactory/Proper-Resolution was cached in the local 
repository, resolution will not be reattempted until the update interval of 
Proper-Resolution has elapsed or updates are forced -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal 
on project modulecore: Could not resolve dependencies for project 
com.adp.sass:modulecore:jar:1.0.0-SNAPSHOT: Failed to collect dependencies at 
com.adp.sass:sasscommon:jar:1.0.0-SNAPSHOT
at 
org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.getDependencies(LifecycleDependencyResolver.java:221)
at 
org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.resolveProjectDependencies(LifecycleDependencyResolver.java:127)
at 
org.apache.maven.lifecycle.internal.MojoExecutor.ensureDependenciesAreResolved(MojoExecutor.java:245)
at 
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:199)
at 
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
at 
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
at 
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
at 
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
at 
org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
at 
org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
at 
org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307)
at 
org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:863)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:199)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at 
org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
at 
org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
at 
org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
at 
org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
at org.codehaus.classworlds.Launcher.main(Launcher.java:47)
Caused by: org.apache.maven.project.DependencyResolutionException: Could not 
resolve dependencies for project com.adp.sass:modulecore:jar:1.0.0-SNAPSHOT: 
Failed to collect dependencies at com.adp.sass:sasscommon:jar:1.0.0-SNAPSHOT
at 
org.apache.maven.project.DefaultProjectDependenciesResolver.resolve(DefaultProjectDependenciesResolver.java:180)
at 
org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.getDependencies(LifecycleDependencyResolver.java:195)
... 24 more
Caused by: org.eclipse.aether.collection.DependencyCollectionException: Failed 
to collect dependencies at com.adp.sass:sasscommon:jar:1.0.0-SNAPSHOT
at 
org.eclipse.aether.internal.impl.DefaultDependencyCollector.collectDependencies(DefaultDependencyCollector.java:291)
at 
org.eclipse.aether.internal.impl.DefaultRepositorySystem.collectDependencies(DefaultRepositorySystem.java:316)
at 
org.apache.maven.project.DefaultProjectDependenciesResolver.resolve(DefaultProjectDependenciesResolver.java:172)
... 25 more
Caused by: