[Building Sakai] Lesson Builder 1.3.x and building with Sakai 2.7.1 question

Walters, Cynthia (cmw6s) cmw6s at eservices.virginia.edu
Wed Sep 7 08:01:23 PDT 2011 

Thank-you for this information, Charles.  We'll get the most recent from the 1.3.x branch, or use the tag you create, as you suggest.

Will also check into KNL-433, thanks for the tip.

Cindy

________________________________
From: sakai-dev-bounces at collab.sakaiproject.org [sakai-dev-bounces at collab.sakaiproject.org] on behalf of Charles Hedrick [hedrick at rutgers.edu]
Sent: Tuesday, September 06, 2011 4:57 PM
To: Walters, Cynthia (cmw6s)
Cc: sakai-dev at collab.sakaiproject.org
Subject: Re: [Building Sakai] Lesson Builder 1.3.x and building with Sakai 2.7.1 question

You absolutely want the most recent from the 1.3 branch. 1.3.0 turned out to have a couple of serious problems. We've now done a fair amount of work in production under the most recent revision in the 1.3 branch. While I'm never going to claim that anything is bug-free, I don't expect any show-stoppers in the most recent 1.3 revision. The same is not true, unfortunately, for the 1.3.0 tag.

Now that it's remained constant for a while, I'll do another tag. But tags simply document reference points. There's no reason to think that a tag is more stable than the most current code. 1.3 is now in maintenance, so I won't check things in unless I'm pretty confident. You might want to wait a couple of days after a revision is checked in, but otherwise I'd take the most recent. Take a look at RELEASE-NOTES from the top level of the lesson builder source (above the level of trunk, branches, tags). It will document the changes in every revision in the branches.

By the way, this probably isn't an issue for you, but you also don't want to use  Sakai with KNL-433 applied. The issue isn't specific to LB, but since LB does allow you to make various adjustments to sites, it can trigger the problem. See the comments on KNL-433 for an explanation.


On Sep 6, 2011, at 3:29 PM, Walters, Cynthia (cmw6s) wrote:

Hello,
A follow-on question...

I have the LB 1.3.0 tag, which seems to be the recommended source for use in production.  I also see a number of additional revisions to 1.3.x (in addition to the popAdvisor fix in rev 97795).

Would you recommend some or all of these fixes also be applied to the 1.3.0 tag as we prepare LB for our Sakai 2.7.1 installation?

Thanks for your feedback,
Cynthia Gast Walters @ UVa


________________________________
From: Charles Hedrick [hedrick at rutgers.edu<mailto:hedrick at rutgers.edu>]
Sent: Friday, September 02, 2011 11:04 AM
To: Walters, Cynthia (cmw6s)
Cc: Eric Jeney; sakai-dev at collab.sakaiproject.org<mailto:sakai-dev at collab.sakaiproject.org>
Subject: Re: [Building Sakai] Lesson Builder 1.3.x and building with Sakai 2.7.1 question

My apologies. We had a coordination failure. I thought Eric had done this. I've just done it. to 1.3.x. rev 97795.  I'll do it to trunk shortly.

You wouldn't want to have put up 1.3 until a couple of days ago anyway. Not surprisingly, when we put real users on it we found a couple of serious issues. We've now survived a week of real usage, with heavy creation of new material, so I'm a bit more confident.




On Sep 2, 2011, at 10:17 AM, Walters, Cynthia (cmw6s) wrote:

Hello:

Regarding the suggestion that Lesson Builder 1.3 will be fixed to enable the popAdvisor(SecurityAdvisor) method to work with Sakai 2.7.1, I was wondering if you can share when you anticipate this fix will be available?  We would like to start using the improved LB 1.3 version with our Sakai 2.7.1 installation.

Thanks for any updates,
Cynthia Gast Walters @ UVa

________________________________
From: Charles Hedrick [hedrick at rutgers.edu<mailto:hedrick at rutgers.edu>]
Sent: Friday, August 19, 2011 2:35 PM
To: Eric Jeney
Cc: Walters, Cynthia (cmw6s); sakai-dev at collab.sakaiproject.org<mailto:sakai-dev at collab.sakaiproject.org>
Subject: Re: [Building Sakai] Lesson Builder 1.3.x and building with Sakai 2.7.1 question

To add to this: Lesson Buidler uses hibernate. As long as you have auto.ddl on, it will update automatically. Hibernate does not update indices for Mysql, but we have a separate .sql file that will do that automatically.

If you have multiple front ends, I recommend moving to the new version at the same time. However when doing development work, I have run 1.2.2 with a database that has been updated to 1.4. Generally the new fields have default values.


On Aug 19, 2011, at 2:21 PM, Eric Jeney wrote:

The pages should transfer without any issue.

On Fri, Aug 19, 2011 at 1:56 PM, Walters, Cynthia (cmw6s) <cmw6s at eservices.virginia.edu<mailto:cmw6s at eservices.virginia.edu>> wrote:
Thank-you, Charles, that sounds great.

A question arises... if folks start creating pages and content with LB 1.2.2 and we upgrade soon to 1.3.x, what sort of migration process would they follow (if any) to continue to use their LB pages and content?

Thanks again,
Cindy / UVa


________________________________
From: Charles Hedrick [hedrick at rutgers.edu<mailto:hedrick at rutgers.edu>]
Sent: Friday, August 19, 2011 1:23 PM
To: Walters, Cynthia (cmw6s)
Cc: Matthew Jones; sakai-dev at collab.sakaiproject.org<mailto:sakai-dev at collab.sakaiproject.org>

Subject: Re: [Building Sakai] Lesson Builder 1.3.x and building with Sakai 2.7.1 question

We'll fix it to use a pattern that works with 2.7.

On Aug 19, 2011, at 12:20 PM, Walters, Cynthia (cmw6s) wrote:

Matthew, thank you for your feedback.  This is good information to know.
Appreciate it,
Cindy

________________________________
From: sakai-dev-bounces at collab.sakaiproject.org<mailto:sakai-dev-bounces at collab.sakaiproject.org> [sakai-dev-bounces at collab.sakaiproject.org<mailto:sakai-dev-bounces at collab.sakaiproject.org>] on behalf of Matthew Jones [jonespm at umich.edu<mailto:jonespm at umich.edu>]
Sent: Friday, August 19, 2011 11:42 AM
To: Walters, Cynthia (cmw6s)
Cc: sakai-dev at collab.sakaiproject.org<mailto:sakai-dev at collab.sakaiproject.org>
Subject: Re: [Building Sakai] Lesson Builder 1.3.x and building with Sakai 2.7.1 question

It looks like lessonbuilder is using the popAdvisor(SecurityAdvisor) method recommended and added in the 1.2 kernel in https://jira.sakaiproject.org/browse/KNL-542. You'll either need to add this method to a custom kernel you have, upgrade to 2.8+ (where that kernel is used), or modify lesson builder to reflect/wrap around it (or use the old pattern mentioned in the jira).

So this would currently make lesson builder only 2.8+ compatible.

-Matthew

On Fri, Aug 19, 2011 at 11:29 AM, Walters, Cynthia (cmw6s) <cmw6s at eservices.virginia.edu<mailto:cmw6s at eservices.virginia.edu>> wrote:
Hello Charles:

Here at UVa, we are excited about the features and improvements in Lesson Builder 1.3.x. I have downloaded it, but I have not been able to get it to build completely with our Sakai 2.7.1 tag source.  (Background: we build all the source, including kernel and pure-poms, and we append ".uva" to all version numbers.)

With the previous 1.2.2 version of LB, it built and ran easily, with only some version number changes, as you suggested.  We changed the <parent> version number in the top pom.xml file, like this, to reference our 2.7.1.uva version number:

  <parent>
    <artifactId>master</artifactId>
    <groupId>org.sakaiproject</groupId>
    <relativePath>../master/pom.xml</relativePath>
    <version>2.7.1.uva</version>
<!--   <version>M2</version>--><!-- 2.5.x -->
  </parent>


Now, I see a key change in the 1.3.x top pom.xml file ...  The 1.2.2 <parent> refers to the 'master' project;  in 1.3.x it refers to 'pure-poms'.  In Sakai 2.7.1, the pure-poms project has its own version number, different from the Sakai version (for us, it is 2.7.10.uva).

When I attempt to build 1.3.x using our pure-poms version, like this:
    <parent>
        <groupId>org.sakaiproject.purepoms</groupId>
        <artifactId>sakai-edu-tool</artifactId>
        <version>2.7.10.uva</version>          <!-- UVa 2.7.1 pure-poms is 2.7.10.uva -->
        <!-- <version>2.9-SNAPSHOT</version> -->
        <!-- <version>2.8.1</version> --> <!-- purepom deployed with sakai-2.8.0 -->
    </parent>


... I see the following compile errors from the 'tool' directory -- and wonder if I should change the <parent> section back to referring to 'master', as it did in 1.2.2?  Or, if there is a change you recommend related to the SecurityAdvisor errors that I can make in 2.7.1 or LB 1.3.x source?  I have not explored this latter possibility, and welcome your comments.

Compile errors (mvn compile):
[INFO] Compiling 70 source files to /usr/local/sakai/sakai_2-7-x_dev/tools/lessonbuilder/tool/target/classes
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Compilation failure

/usr/local/sakai/sakai_2-7-x_dev/tools/lessonbuilder/tool/src/java/org/sakaiproject/lessonbuildertool/tool/beans/SimplePageBean.java:[2504,44] popAdvisor() in org.sakaiproject.authz.api.SecurityService cannot be applied to (org.sakaiproject.authz.api.SecurityAdvisor)

/usr/local/sakai/sakai_2-7-x_dev/tools/lessonbuilder/tool/src/java/org/sakaiproject/lessonbuildertool/tool/beans/SimplePageBean.java:[3896,38] popAdvisor() in org.sakaiproject.authz.api.SecurityService cannot be applied to (org.sakaiproject.authz.api.SecurityAdvisor)

/usr/local/sakai/sakai_2-7-x_dev/tools/lessonbuilder/tool/src/java/org/sakaiproject/lessonbuildertool/tool/beans/SimplePageBean.java:[4293,38] popAdvisor() in org.sakaiproject.authz.api.SecurityService cannot be applied to (org.sakaiproject.authz.api.SecurityAdvisor)

/usr/local/sakai/sakai_2-7-x_dev/tools/lessonbuilder/tool/src/java/org/sakaiproject/lessonbuildertool/tool/beans/SimplePageBean.java:[4429,42] popAdvisor() in org.sakaiproject.authz.api.SecurityService cannot be applied to (org.sakaiproject.authz.api.SecurityAdvisor)

/usr/local/sakai/sakai_2-7-x_dev/tools/lessonbuilder/tool/src/java/org/sakaiproject/lessonbuildertool/service/LessonBuilderAccessService.java:[311,25] popAdvisor() in org.sakaiproject.authz.api.SecurityService cannot be applied to (org.sakaiproject.authz.api.SecurityAdvisor)

/usr/local/sakai/sakai_2-7-x_dev/tools/lessonbuilder/tool/src/java/org/sakaiproject/lessonbuildertool/service/LessonBuilderAccessService.java:[363,61] popAdvisor() in org.sakaiproject.authz.api.SecurityService cannot be applied to (org.sakaiproject.authz.api.SecurityAdvisor)

/usr/local/sakai/sakai_2-7-x_dev/tools/lessonbuilder/tool/src/java/org/sakaiproject/lessonbuildertool/service/LessonBuilderAccessService.java:[526,57] popAdvisor() in org.sakaiproject.authz.api.SecurityService cannot be applied to (org.sakaiproject.authz.api.SecurityAdvisor)



It is important for us to be able to build with our Sakai 2.7.1 versions of kernel and other jars, because we have made local changes.  So, building with the <parent> set to 2.8.1, which does work, is not a good option because it downloads community versions of kernel and other files.

Also, I have tried changing the value to our version of sakai (2.7.1.uva), but it fails to build because that is not the pure-poms version.

Interested to know if you think my changing the <parent> to refer to 'master' (as it did in 1.2.2) is a viable possibility?  Or, should we return to LB 1.2.2 as long as we are running Sakai 2.7.1?

Thanks for your feedback,
Cynthia Walters
University of Virginia



_______________________________________________
sakai-dev mailing list
sakai-dev at collab.sakaiproject.org<mailto: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<mailto:sakai-dev-unsubscribe at collab.sakaiproject.org> with a subject of "unsubscribe"

_______________________________________________
sakai-dev mailing list
sakai-dev at collab.sakaiproject.org<mailto: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<mailto:sakai-dev-unsubscribe at collab.sakaiproject.org> with a subject of "unsubscribe"


_______________________________________________
sakai-dev mailing list
sakai-dev at collab.sakaiproject.org<mailto: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<mailto: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/20110907/4564a843/attachment.html

More information about the sakai-dev mailing list