James Protocols
  1. James Protocols
  2. PROTOCOLS-94

Fresh checkout of protocols currently doesn't compile (imap)

    Details

    • Type: Bug Bug
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: imap
    • Labels:
      None

      Description

      I checkout the latest code version (all of james; not just protocols) from trunk (svn co ...) and used maven 3.0.3 to maven clean compile. I also created the eclipse projects (maven eclipse:eclipse) and imported them. Both approaches (as you would expect) show the same compile time errors. Looks like some dependencies are not properly defined.

        Activity

        Juergen Donnerstag made changes -
        Field Original Value New Value
        Status Open [ 1 ] Resolved [ 5 ]
        Resolution Fixed [ 1 ]
        Hide
        Juergen Donnerstag added a comment -

        I downloaded the latest changes and that made the difference. No need to clean the maven repository or anything else. Thanks a lot.

        Show
        Juergen Donnerstag added a comment - I downloaded the latest changes and that made the difference. No need to clean the maven repository or anything else. Thanks a lot.
        Hide
        Eric Charles added a comment -

        Hi,
        I just committed a fix in protocols-imap, can you svn up and give it a second try ?

        btw, clean your maven cache ($HOME/.m2/repository/org/apache/james/...) will help. There has been recent some refactoring a few days ago (it should not give issues, but maven publication is not an true science...).

        Also, if you import in eclipse with m2eclipse plugin (without generating your .classpath, .project files with mvn eclipse:eclipse), you will benefit from workspace resolution, and will have less risk to rely on outdated jar in you local repo.

        Hopes this help, Eric

        Show
        Eric Charles added a comment - Hi, I just committed a fix in protocols-imap, can you svn up and give it a second try ? btw, clean your maven cache ($HOME/.m2/repository/org/apache/james/...) will help. There has been recent some refactoring a few days ago (it should not give issues, but maven publication is not an true science...). Also, if you import in eclipse with m2eclipse plugin (without generating your .classpath, .project files with mvn eclipse:eclipse), you will benefit from workspace resolution, and will have less risk to rely on outdated jar in you local repo. Hopes this help, Eric
        Hide
        Eric Charles added a comment -

        Hi, Can you paste here the details:

        • The svn command you invoke (the current project or the server ?)
        • The mvn command you invoke, and from which folder
        • The exception you receive
          Thx, Eric
        Show
        Eric Charles added a comment - Hi, Can you paste here the details: The svn command you invoke (the current project or the server ?) The mvn command you invoke, and from which folder The exception you receive Thx, Eric
        Juergen Donnerstag created issue -

          People

          • Assignee:
            Norman Maurer
            Reporter:
            Juergen Donnerstag
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development