search

spideruci / tacoco

Integrated Software Analysis Framework
https://github.com/spideruci/tacoco
MIT License
8 stars 7 forks source link

consuming-projects4testing #108

Closed VijayKrishna closed 4 years ago

VijayKrishna commented 4 years ago
  1. Consuming projects4testing:1.0.0 as a jar file, which is then unpacked with the maven-dependency-plugin as part of mvn:package. This will then be used by mvn:integration-test to run tests on sample projects. projects4testing's maven repo is distributed via Github Packages
  2. Removing git clone projects4testing from tavisCI. mvn clean integration-test should now be self contained.
  3. Ignoring projects4testing/ locally in git

Why do this?

  1. This removes the requirement to clone the entire project4testing repo by TravisCI.
  2. mvn install|package work just the same locally as they do on TravisCI.
  3. Aside: Projects tacoco and projects4testing are now configured with distributionManagement in their build script to be deployed to Github.

Devs running mvn commands on Tacoco will need to replicate what is available in .travis.settings.xml to their own setting.xml file of choice (typically $HOME/.m2/settings.xml) and setup their own Github Token in that file.

VijayKrishna commented 4 years ago

@kajdreef i am going to hold on the merge till i know that you are able to successfully build locally with mvn install. You will need to setup a settings.xml, but if doing that is too much trouble, then this change would not be worth it (?). :) let me know...

kajdreef commented 4 years ago

I was able to get this to work myself by updating the settings.xml as you mentioned. This is something to update in the documentation, so other people can easily set it up and run it themselves. However looks good! I will merge it!

kajdreef commented 4 years ago

I added one line to the wiki to briefly mention to update the settings.xml, see wiki.