In general this should work. Our daily build are running on linux.
But why are you compiling version 6.0? Do you have special needs for it?
Have you checked out a certain tag or branch?
Can you provide the maven output, at least the interesting part?
After this I am able to compile snap-engine successfully. But when I compiled snap-desktop.
I again encounter errors. And I had to download many jars again to compile some of the modules in snap-desktop. Following were the jars:
I would suggest you to check once by just flushing the local repository and pulling the master branch from github. Or there is any other source from where it can be downloaded.? Kindly guide.
This error is coming because the expected vfs jar that is installed in local repo doesnt have classes. It shows stale message in maven compilation. Kindly help and guide.
I have tried with snap 6.0, 7.0 and nightly builds. All have similar behavior. Someone should try a to clone the git repo in a fresh account and see most of the maven jars are not up to date for whatever reason it may be.
I know that maven has had problems in the past downloading many dependencies on the first attempt. But when invoking it again it worked. But actually I haven’t seen this problem anymore since a while.
Since you experience this issue with all branches, it seems not to be an issue with the project. Otherwise, others would have complained earlier.
It could be an issue with our maven server (@obarrilero can you have a look?) or maybe some special settings on your side. Do you have set something in the maven settings.xml file?
First of all thanks for putting some time to do the exercise of doing fresh compilation. I have not set anything in settings.xml. I will try one more time with nightly afresh and send you the console messages. First time the snap engine compilation stops when it is unable to find the jai jars used by snap-jai. Did you clone the github repo or from somewhere else?
I could make it out. The issue was related to SSL certificates.
I had to add a few options in the maven build command. This was the command I used.
mvn install -DskipTests=true -Dmaven.wagon.http.ssl.insecure=true -Dmavn.wagon.http.ssl.allowall=true -Dmaven.wagon.http.ssl.ignore.validity.dates=true
Thanks a lot Sir for taking pain to help me solve this issue.
And sorry for creating confusion.
I will now try to run it.
No idea why it happened so. Tried to check on internet. Seems like certificate needs to be fetched and stored in java installation directory at appropriate place. Will try at my end and provide the fix if possible. This one is a hack not a fix by the way