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

Mvn build #198

Open
wants to merge 28 commits into
base: master
Choose a base branch
from
Open

Mvn build #198

wants to merge 28 commits into from

Conversation

includealex
Copy link
Member

@includealex includealex commented Nov 3, 2022

This is a fully working maven build. Issues about failing tests were created. Closes #224

@includealex
Copy link
Member Author

@yegor256 please review.

@yegor256 yegor256 requested a review from mximp November 3, 2022 18:35
@includealex
Copy link
Member Author

.rultor.yml file should be changed too

@mximp
Copy link

mximp commented Nov 7, 2022

@includealex Please advise on the following:

  1. What was the task to force these changes? There must be issue created with description/request.
  2. Relevant created issues must be referenced here so that it can be tracked.
  3. I can see branch conflicts - it can be merged
  4. How this can be merged if the build is failing. Can we fix (stub) the tests first (if fix tasks are created)?

Copy link

@mximp mximp left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@includealex please check the above

@includealex
Copy link
Member Author

Closes #224.
@mximp please take a look.

@includealex
Copy link
Member Author

@mximp please take a look.

@includealex
Copy link
Member Author

@mximp please take a look

1 similar comment
@includealex
Copy link
Member Author

@mximp please take a look

@includealex
Copy link
Member Author

@yegor256 please, take a look

@yegor256
Copy link
Member

@rultor merge

@rultor
Copy link
Contributor

rultor commented Nov 15, 2022

@rultor merge

@yegor256 OK, I'll try to merge now. You can check the progress of the merge here

@rultor
Copy link
Contributor

rultor commented Nov 15, 2022

@rultor merge

@includealex @yegor256 Oops, I failed. You can see the full log here (spent 3min)

Loaded CA certificate '/etc/ssl/certs/ca-certificates.crt'
Resolving www.antlr.org (www.antlr.org)... 185.199.109.153, 185.199.110.153, 185.199.108.153, ...
Connecting to www.antlr.org (www.antlr.org)|185.199.109.153|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 2100564 (2.0M) [application/java-archive]
Saving to: ‘antlr-4.9.2-complete.jar’


antlr-4.9.2-complet   0%[                    ]       0  --.-KB/s               
antlr-4.9.2-complet 100%[===================>]   2.00M  11.2MB/s    in 0.2s    

2022-11-15 16:21:46 (11.2 MB/s) - ‘antlr-4.9.2-complete.jar’ saved [2100564/2100564]

+ gradle build --info
Initialized native services in: /root/.gradle/native
Initialized jansi services in: /root/.gradle/native
Removing daemon from the registry due to communication failure. Daemon information: DaemonInfo{pid=63, address=[d4998927-8b9d-4d04-a34f-2b45122b76a9 port:41555, addresses:[/127.0.0.1]], state=Idle, lastBusy=1658483579203, context=DefaultDaemonContext[uid=6214c473-6995-4d29-99f0-7e808a06990b,javaHome=/usr/lib/jvm/java-18-openjdk,daemonRegistryDir=/root/.gradle/daemon,pid=63,idleTimeout=10800000,priority=NORMAL,daemonOpts=--add-opens,java.base/java.util=ALL-UNNAMED,--add-opens,java.base/java.lang=ALL-UNNAMED,--add-opens,java.base/java.lang.invoke=ALL-UNNAMED,--add-opens,java.base/java.util=ALL-UNNAMED,--add-opens,java.prefs/java.util.prefs=ALL-UNNAMED,--add-opens,java.prefs/java.util.prefs=ALL-UNNAMED,--add-opens,java.base/java.nio.charset=ALL-UNNAMED,--add-opens,java.base/java.net=ALL-UNNAMED,--add-opens,java.base/java.util.concurrent.atomic=ALL-UNNAMED,-XX:MaxMetaspaceSize=256m,-XX:+HeapDumpOnOutOfMemoryError,-Xms256m,-Xmx512m,-Dfile.encoding=UTF-8,-Duser.country=US,-Duser.language=en,-Duser.variant]}
Removing 0 daemon stop events from registry
Previous Daemon (63) stopped at Tue Nov 15 16:21:47 GMT 2022 by user or operating system
Starting a Gradle Daemon, 1 incompatible and 1 stopped Daemons could not be reused, use --status for details


\u001b[2A\u001b[1B\u001b[1m> Starting Daemon\u001b[m\u001b[17D\u001b[1B\u001b[2AStarting process 'Gradle build daemon'. Working directory: /root/.gradle/daemon/7.5 Command: /usr/lib/jvm/java-18-openjdk/bin/java --add-opens java.base/java.util=ALL-UNNAMED --add-opens java.base/java.lang=ALL-UNNAMED --add-opens java.base/java.lang.invoke=ALL-UNNAMED --add-opens java.base/java.util=ALL-UNNAMED --add-opens java.prefs/java.util.prefs=ALL-UNNAMED --add-opens java.prefs/java.util.prefs=ALL-UNNAMED --add-opens java.base/java.nio.charset=ALL-UNNAMED --add-opens java.base/java.net=ALL-UNNAMED --add-opens java.base/java.util.concurrent.atomic=ALL-UNNAMED -XX:MaxMetaspaceSize=256m -XX:+HeapDumpOnOutOfMemoryError -Xms256m -Xmx512m -Dfile.encoding=UTF-8 -Duser.country=US -Duser.language=en -Duser.variant -cp /usr/share/java/gradle/lib/gradle-launcher-7.5.jar org.gradle.launcher.daemon.bootstrap.GradleDaemon 7.5
Successfully started process 'Gradle build daemon'\u001b[0K

\u001b[0K
\u001b[2A\u001b[1B\u001b[1m> Starting Daemon\u001b[m\u001b[17D\u001b[1B\u001b[2AAn attempt to start the daemon took 0.942 secs.
\u001b[1B\u001b[0K
\u001b[2A\u001b[0K\u001b[1B> IDLE\u001b[6D\u001b[1B\u001b[2AThe client will now receive all logging from the daemon (pid: 53). The daemon log file: /root/.gradle/daemon/7.5/daemon-53.out.log
Starting build in new daemon [memory: 512 MiB]\u001b[0K

\u001b[0K
\u001b[2A\u001b[1B> IDLE\u001b[6D\u001b[1B\u001b[2AUsing 12 worker leases.
\u001b[1B\u001b[0K
\u001b[2A\u001b[0K\u001b[1B> IDLE\u001b[6D\u001b[1B\u001b[2A
\u001b[31mFAILURE: \u001b[39m\u001b[31mBuild failed with an exception.\u001b[39m\u001b[0K

* What went wrong:
Directory '/home/r/repo' does not contain a Gradle build.

A Gradle build should contain a 'settings.gradle' or 'settings.gradle.kts' file in its root directory. It may also contain a 'build.gradle' or 'build.gradle.kts' file.

To create a new Gradle build in this directory run 'gradle init'

For more detail on the 'init' task see https://docs.gradle.org/7.5/userguide/build_init_plugin.html

For more detail on creating a Gradle build see https://docs.gradle.org/7.5/userguide/tutorial_using_tasks.html

* Try:
\u001b[33m> \u001b[39mRun \u001b[1mgradle init\u001b[m to create a new Gradle build in this directory.

\u001b[0K
\u001b[2A\u001b[1m<\u001b[0;1m-------------> 0% WAITING\u001b[m\u001b[26D\u001b[1B> IDLE\u001b[6D\u001b[1B\u001b[2A\u001b[33m> \u001b[39mRun with \u001b[1m--stacktrace\u001b[m option to get the stack trace.\u001b[0K
\u001b[33m> \u001b[39mRun with \u001b[1m--debug\u001b[m option to get more log output.\u001b[0K

* Get more help at \u001b[1mhttps://help.gradle.org\u001b[m

\u001b[31;1mBUILD FAILED\u001b[0;39m in 2s
\u001b[0K
\u001b[0K
\u001b[2A\u001b[1m<\u001b[0;1m-------------> 0% WAITING\u001b[m\u001b[26D\u001b[1B> IDLE\u001b[6D\u001b[1B\u001b[2A\u001b[2K\u001b[1B\u001b[2K\u001b[1A\u001b[0m\u001b[?12l\u001b[?25hcontainer 7178d79476aae88cf43cce6d36390592552d41beceeea3d4cd08bd633065a1c3 is dead
Tue 15 Nov 2022 05:22:08 PM CET

@includealex
Copy link
Member Author

includealex commented Nov 15, 2022

@yegor256 .rultor.yml was modified to maven but it ruins with gradle. This is strange, how to fix it?

@yegor256
Copy link
Member

@includealex you can't modify .rultor.yml together with other files. submit a separate PR with only this file first.

This was referenced Nov 16, 2022
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.

Maven build
4 participants