[ 
https://issues.apache.org/jira/browse/PROTOCOLS-94?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13206386#comment-13206386
 ] 

Eric Charles commented on PROTOCOLS-94:
---------------------------------------

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
                
> Fresh checkout of protocols currently doesn't compile (imap)
> ------------------------------------------------------------
>
>                 Key: PROTOCOLS-94
>                 URL: https://issues.apache.org/jira/browse/PROTOCOLS-94
>             Project: JAMES Protocols
>          Issue Type: Bug
>          Components: imap
>            Reporter: Juergen Donnerstag
>            Assignee: Norman Maurer
>
> 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.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to