Announcement Announcement Module
Collapse
No announcement yet.
Error when importing Spring Integration samples into STS 2.3.3.M1 Page Title Module
Move Remove Collapse
X
Conversation Detail Module
Collapse
  • Filter
  • Time
  • Show
Clear All
new posts

  • Error when importing Spring Integration samples into STS 2.3.3.M1

    Hi

    I'm trying to get the samples working in STS 2.3.3.M1. When I import the projects from the Maven directory I get the following error. Thanks in advance for any pointers.


    Project build error: Non-resolvable parent POM
    org.springframework.integration:spring-integration-samples:2.0.0.M4 for
    cafe:cafe:2.0.0.M4: Failed to resolve POM for
    org.springframework.integration:spring-integration-samples:2.0.0.M4 due
    to Missing:
    ----------
    1) org.springframework.integration:spring-integration-samplesom:
    2.0.0.M4
    ----------
    1 required artifact is missing.

    for artifact:
    org.springframework.integration:spring-integration-samplesom:
    2.0.0.M4

    from the specified remote repositories:
    springsource-external (http://repository.springsource.com/maven/
    bundles/external, releases=true, snapshots=true),
    springsource-snapshot (http://repository.springsource.com/maven/
    bundles/snapshot, releases=true, snapshots=true),
    springsource-milestone (http://repository.springsource.com/maven/
    bundles/milestone, releases=true, snapshots=true),
    springsource-release (http://repository.springsource.com/maven/bundles/
    release, releases=true, snapshots=true),
    apache-maven-snapshots (http://svn.apache.org/maven-snapshot-
    repository/, releases=true, snapshots=true),
    central (http://repo1.maven.org/maven2, releases=true, snapshots=false)

  • #2
    Actually, the samples were not deployed to any repository for M4. You simply need to run `mvn install` from the samples directory before importing them into STS.

    The reason for this is that the samples parent pom (the one you're having trouble with) is not being managed directly by STS / m2eclipse. Once you install it and have it in your local cache, the m2eclipse plugin will be happy and will stop trying to download the pom.

    Comment


    • #3
      Hi,

      Thanks for a quick response. I've found a couple of errors though.
      • The build fails because the HelloWorld example doesn't have a manifest when it tries to create the HelloWorld jar.


        [INFO] [jar:jar {execution: default-jar}]
        [INFO] ------------------------------------------------------------------------
        [ERROR] BUILD ERROR
        [INFO] ------------------------------------------------------------------------
        [INFO] Error assembling JAR

        Embedded error: Manifest file: C:\Users\XXXX\tools\spring-integrati
        on\spring-integration-2.0.0.M4\samples\helloworld\src\main\resources\MET A-INF\MA
        NIFEST.MF does not exist.
      • The build complains about there being no ws-outbound-gateway. I've looked at the samples and there is an inbound-gaetway so I changed the modules in the main POM file accordingly

        <modules>
        <module>cafe</module>
        <module>errorhandling</module>
        <module>filecopy</module>
        <module>helloworld</module>
        <module>jms</module>
        <module>oddeven</module>
        <module>quote</module>
        <module>ws-inbound-gateway</module>
        <module>xml</module>
        </modules>

      I've commented out HelloWorld for now as I was more interested in the other samples. These now compile correctly in STS.

      Thanks.

      Comment


      • #4
        Are you building the samples from the 2.0.0.M4 zip file? Or are you building from latest source?

        Comment


        • #5
          Hi,

          I'm building from the 2.0.0.M4.zip distribution downloaded from:

          http://s3.amazonaws.com/dist.springf...n-2.0.0.M4.zip

          Comment


          • #6
            OK, thanks. It sounds like everything is working for you now, after the pom modifications. Let us know if there are additional issues.

            Comment


            • #7
              by the way, sorry for the error in the pom, and I'm glad you caught it. It happens to already be fixed in the 2.0.0 trunk. If you care to build from source, you'll find that's the case.

              - Chris

              Comment

              Working...
              X