Note that there are some explanatory texts on larger screens.

plurals
  1. POMaven updating .project files, project can no longer successfully build
    text
    copied!<p>I am using Maven in Eclipse Kepler with JRE 1.7.09 for a large project at work. We have a few hundred plugins for our Maven project. Initially, after checking everything out from our Git/SVN repos, I am able to do a Maven Clean/Install without a single issue. But after some time, all of my projects update and I can no longer perform a successful build. I also get errors by almost every project (which is discouraging considering there are about 200 in my workspace). </p> <p>Comparing my local copy and the HEAD version, the only differences are the .project files. In my workspace version, most of the information has been completely removed. Updating these files to the HEAD restores the content and resolves the errors...but updating 200+ .project files everytime it breaks isn't the most efficient. </p> <p>If it helps, I am also a victim of the infinite SVN Status Cache Update error. </p> <p>Any tips would be appreciated. I would really love to fix this shit so I can get back to actual work.</p> <p>Thanks!</p> <p>Edit: The first error was nonsense, so I removed the Maven nature from the offending package. Now I am getting this --</p> <pre><code>[ERROR] QueryResult cannot be resolved to a type [ERROR] &lt;dir/file.java&gt;:[152,0] [ERROR] List&lt;Status&gt; tweets = result.getTweets(); [ERROR] ^^^^^^ [ERROR] Status cannot be resolved to a type [ERROR] &lt;dir/file.java&gt;:[166,0] [ERROR] private Table covertResultIntoTable(List&lt;Status&gt; statuses) { [ERROR] ^^^^^^ [ERROR] Status cannot be resolved to a type [ERROR] &lt;dir/file.java&gt;:[172,0] [ERROR] for (Status status : statuses) { [ERROR] ^^^^^^ [ERROR] Status cannot be resolved to a type [ERROR] 30 problems (30 errors) </code></pre> <p>I can export this package without a single error and all of the types come from a .JAR that has been added to the build path.</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload