I know that Rob commented on something similar about a year ago but I am wondering if there is a common solution to the following problem:
I do a gig clone of the Jean repository. I do an eclipse import existing maven from the root Jena directory. Eclipse gets stuck in a null pointer loop during the build. (Maven builds fine). jena-arq fails to build and continiously loops. If I build the shaded guava first and force the eclipse build to point to the jar it seems to solve the problem. Other packages will not compile because they have references to the shaded package names but the shaded jar is not on the classpath. Seems to me we need a way to make sure the shaded jar appears in the maven dependencies so that it will be included in the pom. However, I think that since the shaded guava does not have any source eclipse does not run it and so does not build the jar that is needed by the other projects. I am not certian this is the case. Anybody have a solution to making Jena compile in Eclipse directly after doing a git clone? Thx, Claude -- I like: Like Like - The likeliest place on the web <http://like-like.xenei.com> LinkedIn: http://www.linkedin.com/in/claudewarren
