GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Sign in
  • ActionsCI/CD and automation
  • CodespacesCloud development environments
  • All Features
  • Documentation
  • Training
  • Certifications
  • Build with Copilot
  • Customize Copilot
  • Integrations
  • Trending repos
  • GitHub Sponsors
  • Developer articles
  • Enterprises

This view

  • Original page
  • New address

GeezerVison is showing github.com — Convert the repository into a Java project · Issue #474 · TheAlgorithms/Java

Convert the repository into a Java project  #474

New issue
Copy link
New issue
Copy link
Closed
Closed
Convert the repository into a Java project #474
Copy link
Labels
help wantedstale

Description

@varunu28
varunu28
opened on Jul 29, 2018
Issue body actions

@christianbender @AnupKumarPanwar @dynamitechetan

This is something which something which we have discussed in the past and have been raised by multiple users of the repo. The repo can be converted to a complete Java project with correct package structure, JUnit tests and Java language standard checkers. I want that anyone who is adding a new algorithm should add respective tests and follow a set coding standard so that the repo can become more usable for users who can then clone it into a local IDE and work on it.

Similar to Scala Repo

I propose that we create a development branch on which we can start making the changes and replace it with the master once it fulfills the above-mentioned requirement. I would like to take the initiative and start this task.

Please share your feedback.

Reacted by Mahmoud Khalil, Leif Gruenwoldt, kaypeegithub, CoderP, Zachary, xletme, GQH1993, Danpatpang, Vishal Gole, Alex and 13 more
Reacted by CoderP and zhousFOREVER

Activity

Next
  1. burnz248 commented on Jul 29, 2018

    @burnz248
    burnz248
    on Jul 29, 2018
    More actions

    Hey Anup. I would like to help with this as well. Let me know what you need help with

  2. MarisaAfuera commented on Jul 30, 2018

    @MarisaAfuera
    MarisaAfuera
    on Jul 30, 2018
    Contributor
    More actions

    Hi Anup. Great idea. I also can help if you need.

  3. rahul-vishwadhaar commented on Aug 3, 2018

    @rahul-vishwadhaar
    rahul-vishwadhaar
    on Aug 3, 2018
    More actions

    Hello Anup,

    This seems to be great thing. Please let me know if I can contribute.

  4. ahmedsameha1 commented on Aug 4, 2018

    @ahmedsameha1
    ahmedsameha1
    on Aug 4, 2018
    More actions

    I'm in.

  5. mkabdullahi commented on Aug 5, 2018

    @mkabdullahi
    mkabdullahi
    on Aug 5, 2018
    More actions

    Also, I am in and happy to contributes

  6. lq920320 commented on Aug 10, 2018

    @lq920320
    lq920320
    on Aug 10, 2018
    More actions

    So great, happy to join and contribute.

  7. esarella commented on Aug 15, 2018

    @esarella
    esarella
    on Aug 15, 2018
    More actions

    Presently working on solving most problems. I'm more than willing to help and contribute.

  8. asdiamond commented on Aug 15, 2018

    @asdiamond
    asdiamond
    on Aug 15, 2018
    More actions

    I can definitely help and contribute to this.

  9. giannisal commented on Aug 20, 2018

    @giannisal
    giannisal
    on Aug 20, 2018
    More actions

    I'd love to contribute to make this repo a java project.

    From what I've seen so far, the development branch is identical to the master in terms of structure and content. I'm used to working with maven in Java, however I saw that the scala repo is based on Travis CI. Would you like me to work on either of them, create the project and test for some of the existing classes?

  10. varunu28 commented on Aug 23, 2018

    @varunu28
    varunu28
    on Aug 23, 2018
    ContributorAuthor
    More actions

    @giannisal I initially created the development branch. I would move the code to that branch in a project structure by the weekend and would update the README for the test case format. After that we can start accepting contributions to the development branch for the tests
    We are using ScalaTest spec in the Java repo

  11. varunu28 commented on Aug 24, 2018

    @varunu28
    varunu28
    on Aug 24, 2018
    ContributorAuthor
    More actions

    I have updated the development branch and added a instructions to the README. We can start with the migration.

    @christianbender Please make sure every PR is adhering to the points mentioned in README on Development branch

  12. varunu28
    added
    help wanted
    on Aug 24, 2018
  13. lq920320 commented on Aug 25, 2018

    @lq920320
    lq920320
    on Aug 25, 2018
    More actions

    which build tool should be used, maven or gradle? @varunu28 I didn't see on the Development branch.

  14. asdiamond commented on Aug 25, 2018

    @asdiamond
    asdiamond
    on Aug 25, 2018
    More actions

    What about bazel?

  15. varunu28 commented on Aug 25, 2018

    @varunu28
    varunu28
    on Aug 25, 2018
    ContributorAuthor
    More actions

    @lq920320 As of now we are concentrating on adding test coverage. We would be deciding on the build tool later

  16. 47 remaining items

  17. mainrs commented on Aug 25, 2019

    @mainrs
    mainrs
    on Aug 25, 2019
    More actions

    I've added a PR #815 that cleans up the code base to make working on it easier. After it gets merged I'll start with adding tests and all missing algorithms to the repo.

  18. jayyusi commented on Sep 14, 2019

    @jayyusi
    jayyusi
    on Sep 14, 2019
    More actions

    is this still going on ? If yes, I want in on it !! Which algorithms need JUnit tests ?

  19. mainrs commented on Sep 14, 2019

    @mainrs
    mainrs
    on Sep 14, 2019
    More actions

    Just take a look at the development branch. Everything in there is OK. Everything else needs a port plus Junit tests

  20. jayyusi commented on Sep 14, 2019

    @jayyusi
    jayyusi
    on Sep 14, 2019
    More actions

    Just take a look at the development branch. Everything in there is OK. Everything else needs a port plus Junit tests

    Here's a question before I dive into this.
    CombSort.java exists in the master branch, but doesn't exist in the development branch. So based on what you said, it needs a test, can you confirm ? and what do you mean by port ?
    Thanks

  21. mainrs commented on Sep 14, 2019

    @mainrs
    mainrs
    on Sep 14, 2019
    More actions

    If it doesn't exist in development you have to get the code from master and add it to development. After that, you need to write unit tests for it. The tests should cover up most of the behavior of each algorithm. Like exceptions that might be thrown, wrong input formats etc.

    By port I meant taking the algorithm from master and adding it to development. They need some tweaking because you don't need the main method anymore. The stuff in main should be covered by the tests.
    You also need to add package statements because the project structure changed to maven.

  22. jayyusi commented on Sep 14, 2019

    @jayyusi
    jayyusi
    on Sep 14, 2019
    More actions

    If it doesn't exist in development you have to get the code from master and add it to development. After that, you need to write unit tests for it. The tests should cover up most of the behavior of each algorithm. Like exceptions that might be thrown, wrong input formats etc.

    By port I meant taking the algorithm from master and adding it to development. They need some tweaking because you don't need the main method anymore. The stuff in main should be covered by the tests.
    You also need to add package statements because the project structure changed to maven.

    Great, thank you, I will get to it soon, I'm gonna do CombSort.java first.

  23. jayyusi commented on Sep 14, 2019

    @jayyusi
    jayyusi
    on Sep 14, 2019
    More actions

    I've added PR #825, which has 2 new files:

    1. CombSort.java ( copied from master as is, with minor changes to import statements and class interface implementation to accommodate project structure changes )
    2. CombSortTest.java ( which has 4 tests within it, Integer, String, Double, Character )
  24. mainrs commented on Sep 15, 2019

    @mainrs
    mainrs
    on Sep 15, 2019
    More actions

    Looks good.
    Edit: Added some changes that you should make to match with java's coding style.

  25. renjithgr commented on Sep 28, 2019

    @renjithgr
    renjithgr
    on Sep 28, 2019
    More actions

    Hi all,
    I raised a pull request to change the build tool from Maven to Gradle. #902

    Nowadays, Gradle is the most common build tool for new Java projects.

  26. burnz248 commented on Apr 29, 2020

    @burnz248
    burnz248
    on Apr 29, 2020
    More actions

    Is this still something that needs to be addressed?

  27. Adhikaribharath commented on May 13, 2020

    @Adhikaribharath
    Adhikaribharath
    on May 13, 2020
    More actions

    Is this still on going task? If so I would like to contribute :)

  28. Detective-Khalifah commented on May 28, 2020

    @Detective-Khalifah
    Detective-Khalifah
    on May 28, 2020
    More actions

    Excellent Idea!

  29. stale commented on Mar 20, 2021

    @stale
    staleBot
    on Mar 20, 2021
    More actions

    This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

  30. stale
    added
    stale
    on Mar 20, 2021
  31. varunu28
    closed this as completedon Mar 20, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    help wantedstale

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions

      You are visitor 01402503 — GeezerVison does not store the pages you look up.
      Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.