[Building Sakai] Learning - Development Environment Setup Walkthrough

[Matthew Jones]

I haven't tried the 2.9.0-all, though I wouldn't use the "cafe" profile.
The first error will go away if you remove cafe because "portal" is in the
cafe profile but not in the regular profile (because it's an indie) if you
look at the root pom
https://source.sakaiproject.org/svn/sakai/tags/sakai-2.9.0/pom.xml

You can see the profiles and all of the modules it will try to build
depending on which one is activated.

Cafe is a small subset of Sakai with the least amount of tools. In some
cases cafe was just a profile in the regular version of Sakai, in other
cases cafe was it's own project and set of externals entirely:
See: https://source.sakaiproject.org/svn/cafe/trunk/

The only -P (profiles) we usually use are for
-Ppack (builds demo and binary artifacts)
-Ppack-demo (builds demo artifacts)
-Ppack-bin (builds bin artifacts)

If the docs still talk about cafe and are referring to these directories
then they should probably be updated. I used to use cafe because it was
faster, but really don't even use it anymore. It's mostly there only *if*
you wanted a Sakai install with the absolute minimum number of tools.


On Tue, Dec 4, 2012 at 1:29 PM, Neal Caidin
<nealcaidin at sakaifoundation.org>wrote:

> Hey all,
>
> I am using the Development Environment Setup Walkthrough but I'm stuck on
> step 11, using Maven to build Sakai .
>
>
> https://confluence.sakaiproject.org/display/BOOT/Development+Environment+Setup+Walkthrough
>
> Using the 2.9.0 tag source, I execute mvn -Pcafe clean install but I get
> an error:
> mvn -Pcafe clean install
> [INFO] Scanning for projects...
> [ERROR] The build could not read 1 project -> [Help 1]
> [ERROR]
> [ERROR]   The project org.sakaiproject:base:2.9.0
> (/Users/nealcaidin/dev/sakai-2.9.0/pom.xml) has 1 error
> [ERROR]     Child module /Users/nealcaidin/dev/sakai-2.9.0/portal of
> /Users/nealcaidin/dev/sakai-2.9.0/pom.xml does not exist
> …. (more error info here)
>
> So, thinking that maybe I would need to download the portal module
> separately (?), I decided to try the newly created sakai-2.9.0-all tag
> instead. This seems to chug along, but at the end I get this:
>
> INFO]
> ------------------------------------------------------------------------
> [INFO] BUILD SUCCESS
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Total time: 9:34.022s
> [INFO] Finished at: Tue Dec 04 13:08:37 EST 2012
> [INFO] Final Memory: 329M/618M
> [INFO]
> ------------------------------------------------------------------------
> [WARNING] The requested profile "cafe" could not be activated because it
> does not exist.
>
> How could the "cafe" profile not exist if it used it to build the source
> successfully?
>
> Thinking this might only be a warning, I proceed to the next step, which
> is mvm -Pcafe sakai:deploy , but that fails. I get a lot of warnings like
> this:
>
> [INFO] Scanning for projects...
> [WARNING]
> [WARNING] Some problems were encountered while building the effective
> model for org.sakaiproject.kernel:sakai-kernel-impl:jar:1.3.0
> [WARNING] 'dependencies.dependency.(groupId:artifactId:type:classifier)'
> must be unique: org.slf4j:slf4j-log4j12:jar -> duplicate declaration of
> version (?) @ line 114, column 17
>
> followed by lots of [INFO]'s and SKIPPED's  , with at the end:
>
> [INFO]
> ------------------------------------------------------------------------
> [INFO] BUILD FAILURE
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Total time: 5.951s
> [INFO] Finished at: Tue Dec 04 13:09:37 EST 2012
> [INFO] Final Memory: 110M/311M
> [INFO]
> ------------------------------------------------------------------------
> [WARNING] The requested profile "cafe" could not be activated because it
> does not exist.
> [ERROR] Failed to execute goal
> org.sakaiproject.maven.plugins:sakai:1.4.0:deploy (default-cli) on project
> shared-deploy: Failed to deploy to container
> :/opt/tomcat/shared/lib/commons-el-1.0.jar (No such file or directory) ->
> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the
> -e switch.
> [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/MojoFailureException
> [ERROR]
> [ERROR] After correcting the problems, you can resume the build with the
> command
> [ERROR]   mvn <goals> -rf :shared-deploy
>
> Not having much luck. Any suggestions?
>
> Thanks,
>
>
>  Neal Caidin
>
> Sakai CLE Community Coordinator
> nealcaidin at sakaifoundation.org
> Skype: nealkdin
> AIM: ncaidin at aol.com
>
> P.S. I think the Confluence doc needs updating to reflect Tomcat 7
> support, etc?
>
>
>
> _______________________________________________
> sakai-dev mailing list
> sakai-dev at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
>
> TO UNSUBSCRIBE: send email to
> sakai-dev-unsubscribe at collab.sakaiproject.org with a subject of
> "unsubscribe"
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20121204/fe96e85d/attachment.html