Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fixed #244 #245

Closed
wants to merge 1 commit into from
Closed

Fixed #244 #245

wants to merge 1 commit into from

Conversation

khmarbaise
Copy link
Contributor

o Configured maven to use the local build cache as
Maven cache.

 o Configured maven to use the local build cache as
   Maven cache.
@coveralls
Copy link

coveralls commented Jul 17, 2016

Coverage Status

Coverage remained the same at 60.053% when pulling d1abc57 on khmarbaise:issue-244 into a15f77d on asciidoctor:master.

@mojavelinux
Copy link
Member

mojavelinux commented Jul 17, 2016

As I mentioned in the other thread, let's just update the cache:

cache:
  - C:\maven
  - C:\Users\appveyor\.m2

@abelsromero
Copy link
Member

Shouldn't we cache just the repo folder ?

C:\\Users\\appveyor\\.m2\\repository

If someday we want to tinker with settings.xml we shouldn't cache it.

@mojavelinux
Copy link
Member

We are caching C:\maven because that is where we extracted Maven. I think we can avoid having to download Maven each time if it is cached. However....

I think we should have an environment variable for the version of Maven we are using. We would then only have to change one value and it would a) download the right version and b) only cache the version we are using. wdyt?

@khmarbaise
Copy link
Contributor Author

khmarbaise commented Jul 18, 2016

Downloading Maven and using it from a cache is something different than the dependencies which have been downloaded. The download of Maven is not a problem. Apart from that you can the maven wrapper instead of doing this on your own...https://github.com/mojohaus/buildnumber-maven-plugin/blob/master/.travis.yml but this is a separate issue..

@mojavelinux
Copy link
Member

I like the idea of using the Maven wrapper!

@abelsromero
Copy link
Member

Maven Wrapper does not support Java6, it's scheduled for 1.6.0 though (#204)

@mojavelinux
Copy link
Member

mojavelinux commented Jul 18, 2016 via email

@khmarbaise
Copy link
Contributor Author

If you correctly configure toolchain its not a problem at all...

@abelsromero
Copy link
Member

I can look into this tomorrow if everyone agrees. Both updating the cache and setting the wrapper for AppVeyour only.
I'd like to include this for next release 😄

@abelsromero
Copy link
Member

Just an update, Appveyor ships with maven 3.3.9 and Java 6 now, using both is not compatible of course. I am seeing to replace the default version to avoid issues due to AppVeyor changes.
For instance, a few days after releasing this version they did a rollback and projects using the installed maven started to fail.

@abelsromero
Copy link
Member

I created this PR #272.
I kind of digressed from the original idea, so I am open to any comment.

@abelsromero
Copy link
Member

Closing with PR #272

@abelsromero abelsromero closed this Oct 4, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants