Uploaded image for project: 'NetBeans'
  1. NetBeans
  2. NETBEANS-3582

Not enough space to download and unpack index for Maven 'Central Repository'

VotersWatch issueWatchersLinkUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Not A Bug
    • 11.2
    • 11.2
    • None

    Description

      Both the automatic download process that occurs when you create a Maven project, and in the 'Services' tab for Maven, of the index completes up to the point of unpacking.  Looking at the exception info I can only assume that Netbeans doesn't know that 491Gb is larger than 802Mb!  Unless the zip file unpacks out to over 491Gb?!?!  If this is so, then how can ANYONE develop a Maven based project.  I would not expect everyone to have this must free disk space.

       

      ================================================================

      [indexing] ERROR org.apache.maven.index.updater.DefaultIndexUpdater - Fallback to *.zip also failed: java.io.FileNotFoundException: Resource nexus-maven-repository-index.zip does not exist
      INFO [org.netbeans.modules.maven.indexer.NexusRepositoryIndexerImpl]: Downloaded maven index file has size 802,161,664 (zipped). The usable space in /home/bwillcott/.cache/netbeans/11.2 is 491,860,180,992.
      INFO [org.netbeans.modules.maven.indexer.NexusRepositoryIndexerImpl]
      java.io.IOException: No space left on device

      ================================================================

      Attachments

        1. UI-Log.xml
          11 kB
          Bradley Willcott

        Issue Links

        Activity

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

          People

            Unassigned Unassigned
            bwillcott Bradley Willcott
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment