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

Rename +junit meta to +tests #1869

Closed
yegor256 opened this issue Mar 5, 2023 · 13 comments
Closed

Rename +junit meta to +tests #1869

yegor256 opened this issue Mar 5, 2023 · 13 comments
Assignees
Labels
Milestone

Comments

@yegor256
Copy link
Member

yegor256 commented Mar 5, 2023

It seems that the name junit is not generic enough. We may compile .eo files into other languages, not only Java. I believe, +tests name would be more appropriate. Let's rename.

@yegor256
Copy link
Member Author

yegor256 commented Mar 5, 2023

@mximp pls, help with this

@mximp
Copy link
Contributor

mximp commented Apr 12, 2023

@yegor256 what do you think about +xunit instead of +tests?

@mximp
Copy link
Contributor

mximp commented Apr 17, 2023

@yegor256 any objection?

@mximp
Copy link
Contributor

mximp commented May 4, 2023

@yegor256 can we please release & publish eo-runtime.
We need to make +tests available to continue changes on this task.

@yegor256
Copy link
Member Author

yegor256 commented May 4, 2023

@rultor release, tag is 0.29.4

@rultor
Copy link
Contributor

rultor commented May 4, 2023

@rultor release, tag is 0.29.4

@yegor256 OK, I will release it now. Please check the progress here

@rultor
Copy link
Contributor

rultor commented May 4, 2023

@rultor release, tag is 0.29.4

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

                     ^
  symbol:   class EOstring
  location: package EOorg.EOeolang
/home/r/repo/eo-runtime/src/main/java/org/eolang/Data.java:32: error: cannot find symbol
import EOorg.EOeolang.EOtuple;
                     ^
  symbol:   class EOtuple
  location: package EOorg.EOeolang
/home/r/repo/eo-runtime/src/main/java/org/eolang/Main.java:27: error: cannot find symbol
import EOorg.EOeolang.EOstring;
                     ^
  symbol:   class EOstring
  location: package EOorg.EOeolang

Command line was: /usr/lib/jvm/java-11-openjdk-amd64/bin/javadoc @options @packages

Refer to the generated Javadoc files in '/home/r/repo/eo-runtime/target/apidocs' dir.

    at org.apache.maven.plugins.javadoc.AbstractJavadocMojo.doExecuteJavadocCommandLine (AbstractJavadocMojo.java:6092)
    at org.apache.maven.plugins.javadoc.AbstractJavadocMojo.executeJavadocCommandLine (AbstractJavadocMojo.java:5968)
    at org.apache.maven.plugins.javadoc.AbstractJavadocMojo.executeReport (AbstractJavadocMojo.java:2277)
    at org.apache.maven.plugins.javadoc.JavadocJar.doExecute (JavadocJar.java:189)
    at org.apache.maven.plugins.javadoc.AbstractJavadocMojo.execute (AbstractJavadocMojo.java:2034)
    at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo (DefaultBuildPluginManager.java:126)
    at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2 (MojoExecutor.java:342)
    at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute (MojoExecutor.java:330)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:213)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:175)
    at org.apache.maven.lifecycle.internal.MojoExecutor.access$000 (MojoExecutor.java:76)
    at org.apache.maven.lifecycle.internal.MojoExecutor$1.run (MojoExecutor.java:163)
    at org.apache.maven.plugin.DefaultMojosExecutionStrategy.execute (DefaultMojosExecutionStrategy.java:39)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:160)
    at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:105)
    at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:73)
    at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build (SingleThreadedBuilder.java:53)
    at org.apache.maven.lifecycle.internal.LifecycleStarter.execute (LifecycleStarter.java:118)
    at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:261)
    at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:173)
    at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:101)
    at org.apache.maven.cli.MavenCli.execute (MavenCli.java:827)
    at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:272)
    at org.apache.maven.cli.MavenCli.main (MavenCli.java:195)
    at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
    at jdk.internal.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:62)
    at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke (Method.java:566)
    at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced (Launcher.java:282)
    at org.codehaus.plexus.classworlds.launcher.Launcher.launch (Launcher.java:225)
    at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode (Launcher.java:406)
    at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:347)
[ERROR] 
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR] 
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
[ERROR] 
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR]   mvn <args> -rf :eo-runtime
\u001b[0m\u001b[0mcontainer f6f7e8a9baef0a36a967c748196e50636d2a6bfdd6d0dfcbb0b920b4160d9fe3 is dead
Thu 04 May 2023 10:36:14 AM CEST

@yegor256
Copy link
Member Author

yegor256 commented May 4, 2023

@mximp any ideas?

@mximp
Copy link
Contributor

mximp commented May 4, 2023

@yegor256 not yet.. trying to reproduce it locally.
Has anything been changed in run command?

@mximp mximp added this to the EO backlog burndown - M1 milestone May 10, 2023
@mximp
Copy link
Contributor

mximp commented May 11, 2023

@yegor256 can you please try to release now

@yegor256
Copy link
Member Author

@rultor release, tag is 0.29.4

@rultor
Copy link
Contributor

rultor commented May 11, 2023

@rultor release, tag is 0.29.4

@yegor256 OK, I will release it now. Please check the progress here

@rultor
Copy link
Contributor

rultor commented May 11, 2023

@rultor release, tag is 0.29.4

@yegor256 Done! FYI, the full log is here (took me 16min)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants