-
Notifications
You must be signed in to change notification settings - Fork 165
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
Few configuration issues #815
Comments
@llorllale/z please, pay attention to this issue |
@0crat in |
@llorllale Job #815 is now in scope, role is |
@0crat assign @llorllale |
@llorllale Job |
Manual assignment of issues is discouraged, see §19: -5 point(s) just awarded to @llorllale/z |
@llorllale Job #815 is already assigned to @llorllale/z |
@krzyk
|
@llorllale just ignore the |
@llorllale thanks |
Order was finished: +30 point(s) just awarded to @llorllale/z |
The job #815 is now out of scope |
.travis.yml
:gem install est
(and do we need xcop?, I don't see it used anywhere)pdd --source=$(pwd) --verbose --file=/dev/null
(just like in .rultor.yml) to catch PDD errors earlymvn clean site -Psite --errors --batch-mode
should be aftermvn clean install ...
.rultor.yml
:-XX:MaxPermSize=256m
should be removed (it is not used by java 8)@rultor merge
)pdd --source=$(pwd) --verbose --file=/dev/null
should be first in themerge
part (to catch PDD errors early without doing long maven build)sudo gem install --no-rdoc --no-ri xcop
?And general question, do we deploy the result of
mvn site
anywhere? It is build in both rultor and travis, but I don't know if there is a point in doing two almost full maven builds if we don't put the site anywhere.The text was updated successfully, but these errors were encountered: