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