Ahh, Ok
there was a change to the shindig-server pom that added some end to end tests a few days ago. If you imported the pom into eclipse before then, and did an update afterwards it wont have the correct dependent paths in place. If you are using the M2 eclipse plugin, then some sort of refresh wrt the pom should fix it. If you import using mvn edlipse:elipse from the command line, then re-issuing that command and refreshing eclipse should fix.

Also, could you just update as I put a fix in against SHINDIG-462 that changes the relelative path of the pom.xml file in features/ pom.xml. I would be interested to know if this fixes your problem (and keeps the parent artifact as shindig-parent)

Ian

On 20 Jul 2008, at 19:26, David Ranalli wrote:

Inside eclipse...
Without the change, I get the following compile errors within the
shindig-server project:
Description     Resource        Path    Location        Type
BasicSecurityToken cannot be resolved to a type EndToEndTests.java
shindig-server/src/test/java/org/apache/shindig/server/endtoend line 107
Java Problem
BasicSecurityToken cannot be resolved to a type EndToEndTests.java
shindig-server/src/test/java/org/apache/shindig/server/endtoend line 155
Java Problem
BasicSecurityToken cannot be resolved to a type EndToEndTests.java
shindig-server/src/test/java/org/apache/shindig/server/endtoend line 157
Java Problem
BasicSecurityToken cannot be resolved to a type FetchPersonTest.java
shindig-server/src/test/java/org/apache/shindig/server/endtoend line 28 Java
Problem
BasicSecurityToken cannot be resolved to a type FetchPersonTest.java
shindig-server/src/test/java/org/apache/shindig/server/endtoend line 32 Java
Problem
BasicSecurityToken cannot be resolved to a type FetchPersonTest.java
shindig-server/src/test/java/org/apache/shindig/server/endtoend line 37 Java
Problem
BasicSecurityToken cannot be resolved to a type FetchPersonTest.java
shindig-server/src/test/java/org/apache/shindig/server/endtoend line 42 Java
Problem
BasicSecurityToken cannot be resolved to a type FetchPersonTest.java
shindig-server/src/test/java/org/apache/shindig/server/endtoend line 47 Java
Problem
BasicSecurityTokenDecoder cannot be resolved to a type EndToEndTests.java shindig-server/src/test/java/org/apache/shindig/server/endtoend line 111
Java Problem
BasicSecurityTokenDecoder cannot be resolved to a type EndToEndTests.java shindig-server/src/test/java/org/apache/shindig/server/endtoend line 111
Java Problem
BlobCrypterException cannot be resolved to a type       EndToEndTests.java
shindig-server/src/test/java/org/apache/shindig/server/endtoend line 156
Java Problem
ConcatProxyServlet cannot be resolved to a type EndToEndTests.java
shindig-server/src/test/java/org/apache/shindig/server/endtoend line 149
Java Problem
DataServiceServlet cannot be resolved to a type EndToEndTests.java
shindig-server/src/test/java/org/apache/shindig/server/endtoend line 145
Java Problem
DataServiceServletFetcher cannot be resolved to a type EndToEndModule.java shindig-server/src/test/java/org/apache/shindig/server/endtoend line 35 Java
Problem
GadgetRenderingServlet cannot be resolved to a type     EndToEndTests.java
shindig-server/src/test/java/org/apache/shindig/server/endtoend line 140
Java Problem
GuiceServletContextListener cannot be resolved  EndToEndTests.java
shindig-server/src/test/java/org/apache/shindig/server/endtoend line 136
Java Problem
GuiceServletContextListener cannot be resolved to a type
EndToEndTests.java
shindig-server/src/test/java/org/apache/shindig/server/endtoend line 130
Java Problem
HttpGuiceModule cannot be resolved to a type    EndToEndTests.java
shindig-server/src/test/java/org/apache/shindig/server/endtoend line 134
Java Problem
ParameterFetcher cannot be resolved to a type   EndToEndModule.java
shindig-server/src/test/java/org/apache/shindig/server/endtoend line 34 Java
Problem
The import org.apache.shindig.common cannot be resolved EndToEndModule.java shindig-server/src/test/java/org/apache/shindig/server/endtoend line 20 Java
Problem
The import org.apache.shindig.common cannot be resolved EndToEndTests.java shindig-server/src/test/java/org/apache/shindig/server/endtoend line 29 Java
Problem
The import org.apache.shindig.common cannot be resolved EndToEndTests.java shindig-server/src/test/java/org/apache/shindig/server/endtoend line 30 Java
Problem
The import org.apache.shindig.common cannot be resolved EndToEndTests.java shindig-server/src/test/java/org/apache/shindig/server/endtoend line 31 Java
Problem
The import org.apache.shindig.common cannot be resolved EndToEndTests.java shindig-server/src/test/java/org/apache/shindig/server/endtoend line 32 Java
Problem
The import org.apache.shindig.common cannot be resolved FetchPersonTest.java shindig-server/src/test/java/org/apache/shindig/server/endtoend line 20 Java
Problem
The import org.apache.shindig.gadgets cannot be resolved
EndToEndTests.java
shindig-server/src/test/java/org/apache/shindig/server/endtoend line 33 Java
Problem
The import org.apache.shindig.gadgets cannot be resolved
EndToEndTests.java
shindig-server/src/test/java/org/apache/shindig/server/endtoend line 34 Java
Problem
The import org.apache.shindig.gadgets cannot be resolved
EndToEndTests.java
shindig-server/src/test/java/org/apache/shindig/server/endtoend line 35 Java
Problem
The import org.apache.shindig.social cannot be resolved EndToEndModule.java shindig-server/src/test/java/org/apache/shindig/server/endtoend line 21 Java
Problem
The import org.apache.shindig.social cannot be resolved EndToEndTests.java shindig-server/src/test/java/org/apache/shindig/server/endtoend line 36 Java
Problem
The method bind(Class<ParameterFetcher>) from the type AbstractModule refers
to the missing type ParameterFetcher    EndToEndModule.java
shindig-server/src/test/java/org/apache/shindig/server/endtoend line 34 Java
Problem
The method createToken(String, String) from the type EndToEndTests refers to
the missing type BasicSecurityToken     FetchPersonTest.java
shindig-server/src/test/java/org/apache/shindig/server/endtoend line 32 Java
Problem

-----Original Message-----
From: Ian Boston [mailto:[EMAIL PROTECTED] On Behalf Of Ian Boston
Sent: Sunday, July 20, 2008 1:28 PM
To: [EMAIL PROTECTED]
Cc: [email protected]
Subject: Re: [jira] Created: (SHINDIG-462) Project build error on
shindig-features eclipse project

When you say "changed the Java Build Path" are you talking about
inside eclipse or using the maven command line.

The recommended mvn build is

cd shindigsource
mvn
mvn -Prun


or to do a clean build
mvn clean install
mvn -Prun


BTW, could you send through an error.
Thanks

Ian

On 20 Jul 2008, at 15:47, David Ranalli wrote:

That worked. Thanks.
Though after doing that, the shindig-server project didn't compile,
until I
changed the Java Build Path to require the common, features and
social-api
projects.
With Maven, should I be doing that?

-----Original Message-----
From: Ian Boston [mailto:[EMAIL PROTECTED] On Behalf Of Ian
Boston
Sent: Saturday, July 19, 2008 12:52 PM
To: [EMAIL PROTECTED]
Cc: [email protected]
Subject: Re: [jira] Created: (SHINDIG-462) Project build error on
shindig-features eclipse project


Change the parent pom in features/pom.xml from shindig-parent to
shindig-project.

If thats the fixes then we a change made on 6 May caused this
problem, easy to fix, please confirm that the above works.

Ian

On 19 Jul 2008, at 16:53, David Ranalli (JIRA) wrote:

Project build error on shindig-features eclipse project
-------------------------------------------------------

                 Key: SHINDIG-462
                 URL: https://issues.apache.org/jira/browse/
SHINDIG-462
             Project: Shindig
          Issue Type: Question
          Components: Features (Javascript)
         Environment: Eclipse, Vista 32-bit, jdk 1.6, shindig
source from about 10:00 am July 19th, 2008
            Reporter: David Ranalli


Project won't build because of:
Project build error:Cannot find artifact for parent POM:
org.apache.shindig:shindig-parent::1-SNAPSHOT for project
[inherited]:shindig-features:jar:[inherited] at C:\dev\projects
\shindig\features\pom.xml
Am I doing something wrong? How do I get past this?
Thanks.

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.




Reply via email to