rebarizing log4erl #7
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This included removing derived files and copied files from dependencies.
This will avoid dependency resolution problems for projects that use both webmachine and log4erl.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I've rebarized log4erl.
The main motivation for this was to fix the dependencies. Currently you pull in mochinum.erl from mochiweb directly, but this causes release generation to fail if the project also includes mochiweb proper. log4erl now pulls in mochiweb as a dependency and gets rid of the copied file.
Also, the .xrl and .yrl files are built automatically by rebar, so there's no longer any need to put the derived files in Git.