Giter Club home page Giter Club logo

sawdust's Introduction

sawdust build status

rebooting...

useful mvn commands

Show which Java module names you need to include in your module-info.java files via:

mvn compile org.apache.maven.plugins:maven-dependency-plugin:3.1.1:resolve -DexcludeTransitive

Robert Scholte The 'compile' is only required in case of a multi-module project. You can use 'package' if you also want to know the (automatic module) name of every created jar. With colors!

sawdust's People

Contributors

cschneider71 avatar sormuras avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar

sawdust's Issues

Enhance Eclipse support

Initial Eclipse support was added via b693312

You may import 3 projects (1 root, 2 nested) into your workspace:
eclipsesawdust-1

Running JUnit 5 tests is not supported, yet.

IntelliJ complains about duplicate module-info.java

I've tried the newest version of IntelliJ EAP (2020.1) and still, IntelliJ complains about the two module-info.java via:

'module-info.java' already exists in the module

Maven compiles just fine though. And I was not able to find any other problems besides these red underlines that indicate errors in IntelliJ.
Any ideas about that?

Is there any questionable aspect on creating another module for tests purpose only?

Sorry, I know this is more a question than an issue, but I got confused by some objections I had to face on testing in a modular context that I want to be cleared :)

Let's suppose we have the following project structure:

src/
  main/
    java/
      my.library/
        internals/
          Internal.java
        Util.java
      module-info.java

with the following module-info:

module my.library {
  exports my.library;
}

In order to make tests on Internal.java as well, I have to define another module-info with the following project structure for test folder only, and fix the original module-info:

src/
  main/
    java/
      my.library.test/               <<<<< pay attention
        internals/
          InternalTest.java
        UtilTest.java
      module-info.java

with the following module-info:

open module my.library.test {
  requires my.library;

  requires // junit, assert4j, ...
}

with the fix for the original module-info:

module my.library {
  exports my.library;
  exports my.library.internals to my.library.test;
}

Do you know if there is any evident issue with this approach? Unfortunately, this is the only way I found to make IntelliJ happy.

Thank you in advance for any reply!

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.