Announcement Announcement Module
Collapse
No announcement yet.
Missing POM for net.sourceforge.jline dependency Page Title Module
Move Remove Collapse
X
Conversation Detail Module
Collapse
  • Filter
  • Time
  • Show
Clear All
new posts

  • Missing POM for net.sourceforge.jline dependency

    Hi,

    I'm new to the Spring Framework, and Spring Shell got me interested.

    However, using Maven, I added the repository and the dependency to my pom.xml and tried running mvn compile. But it keeps complaining about the following:

    Downloading: http://repo.springframework.org/libs...e-1.0.S2-B.pom
    [WARNING] The POM for net.sourceforge.jline:jline:jar:1.0.S2-B is missing, no dependency information available
    Downloading: http://repo.springframework.org/libs...e-1.0.S2-B.jar
    [INFO] ------------------------------------------------------------------------
    [INFO] BUILD FAILURE
    [INFO] ------------------------------------------------------------------------

    Any ideas on how why this is happening and how I can solve it?

    Thank you in advance.


    Edit:

    The same thing happens with the release repository:
    Downloading: http://repo.springframework.org/rele...e-1.0.S2-B.pom
    Downloading: http://repo1.maven.org/maven2/net/so...e-1.0.S2-B.pom
    [WARNING] The POM for net.sourceforge.jline:jline:jar:1.0.S2-B is missing, no dependency information available
    Downloading: http://repo.springframework.org/rele...e-1.0.S2-B.jar
    Downloading: http://repo1.maven.org/maven2/net/so...e-1.0.S2-B.jar
    [INFO] ------------------------------------------------------------------------
    [INFO] BUILD FAILURE
    [INFO] ------------------------------------------------------------------------

  • #2
    It's a late reply but perhaps it helps someone else... Had the same issue and resolved it by adding this to my pom.xml (into repositories section):
    Code:
    <repository>
      <snapshots>
        <enabled>false</enabled>
      </snapshots>
      <id>central</id>
      <name>libs-release</name>
      <url>http://repo.springsource.org/libs-release</url>
    </repository>
    Got the idea from here: https://jira.springsource.org/browse/SHL-52

    Comment


    • #3
      Another late reply, but might help if someone else hits the same bump

      For Gradle, I had changed the following properties
      1. build.gradle
        Code:
        repositories {
          maven { url "http://repo.springsource.org/libs-snapshot" }
          maven { url "http://repo.springsource.org/plugins-release" }
          maven { url "http://spring-roo-repository.springsource.org/release" }
          maven { url "http://repo.springsource.org/simple/ext-release-local/" }
          maven { url "http://repo1.maven.org/maven/" }
          maven { url "http://repo1.maven.org/maven2" }
        }

      If building a maven application using spring-shell, below is the repositories tag I have used. It covers most of my situation.

      Code:
      <repositories>
          <repository>
          	<!-- Release -->
      		<snapshots>
          		<enabled>false</enabled>
        		</snapshots>
       		<id>spring-release</id>
       		<name>Spring Maven RELEASE Repository</name>
       		<url>http://repo.springframework.org/release</url>
          </repository>
          <!-- libs-release for JLine fork, artifacts may not be in maven central -->
      	<repository>
      		<snapshots>
          		<enabled>false</enabled>
        		</snapshots>
       		<id>libs-release</id>
       		<name>Spring Maven libs-release Repository</name>
       		<url>http://repo.springframework.org/libs-release</url>
      	</repository>
      	<repository>
      		<!-- see https://jira.springsource.org/browse/SHL-52 -->
      		<snapshots>
          		<enabled>false</enabled>
        		</snapshots>
       		<id>ext-release-local</id>
      = 		<url>http://repo.springsource.org/simple/ext-release-local/</url>
      	</repository>
      	<repository>
      		<snapshots>
          		<enabled>false</enabled>
        		</snapshots>
       		<id>spring-roo-repository</id>
       		<name>Spring Roo Repository</name>
       		<url>http://spring-roo-repository.springsource.org/release</url>
      	</repository>
          <repository>
      		<snapshots>
          		<enabled>false</enabled>
        		</snapshots>
                  <id>central-maven-release</id>
                  <name>Central Maven Repository</name>
                  <url>http://repo1.maven.org/maven/</url>
           </repository>
           <repository>
      		<snapshots>
          		<enabled>false</enabled>
        		</snapshots>
                  <id>central-maven2-release</id>
                  <name>Central Maven2 Repository</name>
                  <url>http://repo1.maven.org/maven2</url>
              </repository>
      	<repository>
      		<snapshots>
          		<enabled>false</enabled>
        		</snapshots>
       		<id>plugins-release</id>
       		<name>plugins-release</name>
       		<url>http://repo.springsource.org/plugins-release</url>
      	</repository>
        </repositories>

      Comment


      • #4
        I will add the additional maven repo to the main shell project page and create an issue to put this in the docs. Eventually we want to shift to jline2. This version of jline is a fork that was done for Roo and we can't find the source code for it (amazing isn't it )
        Mark

        Comment

        Working...
        X