Attach filesAttach ScreenshotAdd voteVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Task
    • Status: Open
    • Major
    • Resolution: Unresolved
    • None
    • 4.0.0
    • go-offline
    • None

    Description

      The simplest and trivial way to "go offline" is to quick build (using -Dtest=void and NOT -DskipTests!) the project with empty local repository and use that.

      There are two "go offline" mojos out there (ours and an independent one) and both suffer from issues like "annotation processor is not downloaded", etc. This will just become worse. But not only this: by NOT building but by artificially collecting artifacts needed for build and resolving them (not doable correctly, only "almost correctly") messes up the recorded contexts in the reverse dependency tree in local repository as well.

      Remember, Maven2 times are past, Maven3+ local repository is much much more than Maven2 local repository was, just a bunch a files...

      Related issues:

      Attachments

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            Unassigned Unassigned
            cstamas Tamas Cservenak

            Dates

              Created:
              Updated:

              Slack

                Issue deployment