[Building Sakai] Installing salora-csv - problems

[Steve Swinsburg]

Hi Greg,

> 1) Who creates (or should have created) these new tables, and when?
Is auto.ddl=true in sakai.properties? I'd expect the tool to handle this
itself though there may be a requirement to run the DDL yourself, what does
the install guide say?

> 2) Once I install/deploy sakora into the sakai-src home directory, do I
need to manually rebuild/deploy csv from its home (sub-)directory ever again
If you make changes, yes. Sakai won't know about it in the normal build
unless you edit the base pom and add the subdirectoy name to the <modules>
section.

> 3) Is the order important here?
If auto.ddl=true  then it should check on each startup and create anything
that is missing, assuming 1.

> 4) Also all of the cm_* tables are empty - I presume that is ok?
The Sakora import is meant to load the data into these, right?

See if you can find the SQL it is using to create the tables and run it
yourself. The tools isnt working presumably because it doesn't have those
tables and can't do its thing.

cheers,
Steve



On Fri, Feb 28, 2014 at 8:05 AM, Gregory Guthrie <guthrie at mum.edu> wrote:

> After several iterations, I wanted to clarify and re-query the questions
> that I have in this case.
>
> I installed Sakai-2.9.1 (source), and tomcat 7.0.21, all work fine. Then I
> downloaded and installed Sakora-csv (into the sakai-src home directory),
> did the mvn build in its own home (sub-)directory, and then did the mvn
> deploy from sakai-src again.
>
> All seemed to go well and report success, but the sakora-csv tests fail. I
> find that the additional database tables it uses were never created in
> MySql and that causes the failures.
>
> 1) Who creates (or should have created) these new tables, and when?
>
> 2) Once I install/deploy sakora into the sakai-src home directory, do I
> need to manually rebuild/deploy csv from its home (sub-)directory ever
> again, or will the sakai master mvn automatically pick-up all such
> sub-projects and run the mvn builds from them?
> That is a common approach in make - but I don't know how the mvn
> configurations is setup.
> I presume this same question would apply to any additional contrib
> projects that get added to sakai before a source build; do they
> automatically get handled by the master mvn of sakai or do they require
> manual re-makes.
>
> 3) Is the order important here? Did Sakai build all tables (only) at its
> first startup, and so later deploy's skip that step? I.e. do I need to
> install svn and deploy before the first sakai mvn-deploy?
> If so, what does that mean, I have to remove all previous installs and
> start over anytime I add a sub-feature to Sakai?
>
> 4) Also all of the cm_* tables are empty - I presume that is ok?
>
> -------------------------------------------
>
>
> _______________________________________________
> 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/20140228/008fcfd3/attachment.html