[Deploying Sakai] Installing sakai

Steve Swinsburg steve.swinsburg at gmail.com
Tue Nov 16 15:00:06 PST 2010 

Hi,

What do you need to modify? That will dictate what you need to bring in to Eclipse.

If you have done a full build of Sakai, your local Maven repo will be populated with all jars you need, so you can resolve the Eclipse build path issues by pointing to those.

cheers,
Steve


On 16/11/2010, at 10:01 PM, Suhas Tumkur Jagadeesh wrote:

> I (actually its we) intend to modify a part of code, but how can I import only a part of it; I mean, how would I know which are the basic packages required to be imported?
> I have created M2_REPO in Eclipse and 'extend'ed it to point to some of the jars which had different versions of missing jars, for example, 
> M2_REPO/uk/org/ponder/sakairsf/SakaiRSF/0.7.2-sakai_2.2.x/sakairsf-0.7.2-sakai_2.2.x.jar
> These missing jars error and missing "entity-api" occurs when creating a new tool.
> 
> And in sakai 2.7.1, there is no kernel-api.
> 
> The basic think what I intend to do is to run sakai through eclipse.
> And for now, when I say "maven build", following is the error message which I get in console of eclipse:
> 
> [INFO] Error stacktraces are turned on.
> [INFO] Scanning for projects...
> [ERROR] The build could not read 1 project -> [Help 1]
> org.apache.maven.project.ProjectBuildingException: Some problems were encountered while processing the POMs:
> [ERROR] 'dependencyManagement.dependencies.dependency.(groupId:artifactId:type:classifier)' must be unique: javax.jcr:jcr:jar -> version 1.0 vs ${sakai.jcr.version} @ org.sakaiproject:master:2.7.1, C:\Users\suhas\workspace1\sakai-2\master\pom.xml
> [WARNING] The expression ${artifactId} is deprecated. Please use ${project.artifactId} instead. @ org.sakaiproject:base:2.7.1, C:\Users\suhas\workspace1\sakai-2\pom.xml
> [WARNING] The expression ${version} is deprecated. Please use ${project.version} instead. @ org.sakaiproject:base:2.7.1, C:\Users\suhas\workspace1\sakai-2\pom.xml
> [WARNING] 'reporting.plugins.plugin.version' is missing for org.apache.maven.plugins:maven-surefire-plugin @ org.sakaiproject:base:2.7.1, C:\Users\suhas\workspace1\sakai-2\pom.xml
> [WARNING] 'reporting.plugins.plugin.version' is missing for org.apache.maven.plugins:maven-pmd-plugin @ org.sakaiproject:base:2.7.1, C:\Users\suhas\workspace1\sakai-2\pom.xml
> [WARNING] 'reporting.plugins.plugin.version' is missing for org.codehaus.mojo:changelog-maven-plugin @ org.sakaiproject:base:2.7.1, C:\Users\suhas\workspace1\sakai-2\pom.xml
> [WARNING] 'reporting.plugins.plugin.version' is missing for org.codehaus.mojo:taglist-maven-plugin @ org.sakaiproject:base:2.7.1, C:\Users\suhas\workspace1\sakai-2\pom.xml
> [WARNING] 'reporting.plugins.plugin.version' is missing for org.codehaus.mojo:jdepend-maven-plugin @ org.sakaiproject:base:2.7.1, C:\Users\suhas\workspace1\sakai-2\pom.xml
> [WARNING] 'reporting.plugins.plugin.version' is missing for org.codehaus.mojo:jxr-maven-plugin @ org.sakaiproject:base:2.7.1, C:\Users\suhas\workspace1\sakai-2\pom.xml
> [WARNING] 'reporting.plugins.plugin.version' is missing for net.sourceforge.maven-taglib:maven-taglib-plugin @ org.sakaiproject:base:2.7.1, C:\Users\suhas\workspace1\sakai-2\pom.xml
> 
>     at org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:293)
>     at org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:402)
>     at org.apache.maven.DefaultMaven.getProjectsForMavenReactor(DefaultMaven.java:351)
>     at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:171)
>     at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:104)
>     at org.apache.maven.cli.MavenCli.execute(MavenCli.java:427)
>     at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:157)
>     at org.apache.maven.cli.MavenCli.main(MavenCli.java:121)
>     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>     at java.lang.reflect.Method.invoke(Method.java:597)
>     at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
>     at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
>     at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
>     at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
> [ERROR]   The project org.sakaiproject:base:2.7.1 (C:\Users\suhas\workspace1\sakai-2\pom.xml) has 1 error
> [ERROR]     'dependencyManagement.dependencies.dependency.(groupId:artifactId:type:classifier)' must be unique: javax.jcr:jcr:jar -> version 1.0 vs ${sakai.jcr.version} @ org.sakaiproject:master:2.7.1 (C:\Users\suhas\workspace1\sakai-2\master\pom.xml)
> [ERROR] 
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR] 
> [ERROR] For more information about the errors and possible solutions, please read the following articles:
> [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/ProjectBuildingException
> 
> 
> 
> On Sat, Nov 13, 2010 at 6:04 AM, Steve Swinsburg <steve.swinsburg at gmail.com> wrote:
> Hello,
> 
> Firstly, if you have imported all of Sakai into Eclipse, then remove it. It's unneccesary. If you need to modify parts of Sakai, then bring in just that module. But as you are just starting out, you won't need to (yet).
> Second, you need to resolve the build path issues within Eclipse. You can create an M2_REPO variable in Eclipse and then 'extend' it and point it at the jars in your repo. For the ones you are missing you want org/sakaiproject/kernel kernel-api.
> 
> cheers,
> Steve
> 
> On 12/11/2010, at 11:37 AM, Suhas Tumkur Jagadeesh wrote:
> 
>> Hi,
>> 
>> I am trying to install sakai on my local machine.
>> I have completed all the necessary steps given in Programmer's Cafe (http://confluence.sakaiproject.org/display/BOOT/Programmer%27s+Cafe).
>> I am trying to install 2.7.1 version of sakai.
>> I am able to build (through maven) and run sakai through command line.
>> But I am not able to run sakai through "eclipse".
>> I have installed "maven" and "sakai app builder" plugins for "eclipse".
>> I have tried to create a "Hello World" tool.
>> The creation is successful but with errors.
>> error 1: Required projects on the build path: 
>>                                 entity-api (missing)
>>                                 user-api (missing)
>> error 2: error showing in HelloWorldProducer.java - "The import org.sakaiproject.user cannot be resolved"
>> 
>> Can somebody please help me resolve this issue and give some suggestions on running sakai through eclipse?
>> 
>> Thanks in advance.
>> 
>> -- 
>> Suhas Jagadeesh
>> 
>> _______________________________________________
>> production mailing list
>> production at collab.sakaiproject.org
>> http://collab.sakaiproject.org/mailman/listinfo/production
>> 
>> TO UNSUBSCRIBE: send email to production-unsubscribe at collab.sakaiproject.org with a subject of "unsubscribe"
> 
> 
> 
> 
> -- 
> Suhas Jagadeesh

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/production/attachments/20101117/f244a383/attachment.html

More information about the production mailing list