[Building Sakai] lesson builder 2.7.1
Adrian Fish
a.fish at lancaster.ac.uk
Thu Sep 22 05:54:26 PDT 2011
Eric's right. Anything you upload via the Add Website button gets
unzipped via the unzip functionality in KNL-273. If you don't have unzip
built into your kernel the Add Website button is never shown.
On 22/09/2011 00:48, Eric Jeney wrote:
> In order for the "Add Website" button to appear, KNL-273 must be
> applied. Once that's applied, the button should show up in the
> dropdown with all of the others.
> https://jira.sakaiproject.org/browse/KNL-273
>
> More information on the Add Website button can be found here:
> https://jira.sakaiproject.org/browse/LSNBLDR-18
>
> I believe that everything gets unzipped into resources, but I may be
> mistaken on that.
>
> On Wed, Sep 21, 2011 at 11:33 AM, Firdyiwek, Yitna (ybf2u)
> <ybf2u at eservices.virginia.edu <mailto:ybf2u at eservices.virginia.edu>>
> wrote:
>
> Hi -- We, at the University of Virginia, are testing Lesson
> Builder on 2.7.1. The Lesson Builder Help page lists "Add Website"
> as another thing you can add to a page ("Add Website - Upload a
> ZIP file. Supports Camtasia, Wimba Create, and Articulate, but any
> ZIP file containing resources may be uploaded"). My question is:
> Where is the "Add Website" button located, and where does the zip
> file get unzipped and stored?
>
> Thanks.
> Yitna
>
> Yitna Firdyiwek, PhD
> Faculty Consultant in IT
> Advanced Technology Group, ITS
> University of Virginia
> 434.924-4055 <tel:434.924-4055>
> ybf2u at virginia.edu <mailto:ybf2u at virginia.edu>
> http://faculty.virginia.edu/firdyiwek
>
> -----Original Message-----
> From: sakai-dev-bounces at collab.sakaiproject.org
> <mailto:sakai-dev-bounces at collab.sakaiproject.org>
> [mailto:sakai-dev-bounces at collab.sakaiproject.org
> <mailto:sakai-dev-bounces at collab.sakaiproject.org>] On Behalf Of
> Hedrick Charles
> Sent: Monday, September 19, 2011 3:07 PM
> To: Charles Hedrick
> Cc: sakai-dev at collab.sakaiproject.org
> <mailto:sakai-dev at collab.sakaiproject.org>
> Subject: [Building Sakai] lesson builder 2.7.1, fixed repository
>
> I have fixed both 1.3.x and trunk. 1.3.x should build and run on
> 2.7.1. I assume trunk will as well but haven't checked it yet.
>
> This involved making my own copy of ResourceLoaderMessageSource
> and a couple of other things, also making some javascript defend
> against differences between 2.7 and 2.8 ways of handling editors.
>
>
> ---------------------------------
>
> At the same time I fixed a blunder in location of a repository. I
> need a jar file for Mneme. Because it's not in a standard Sakai
> repository, I put it on our most stable campus web server.
> Unfortunately I used my departmental virtual hostname. That
> hostname just got moved to another system, where none of my staff
> have access to put up files. So I've had to change the URL for the
> repository.
>
> 1.2 doesn't use it. 1.3.x and trunk are now OK. But if you want to
> build any of the older revs from 1.3.x or trunk, you'll need to
> edit the local-hack repository in tool/pom.xml, to change
>
> <url>http://oirt.rutgers.edu/repos</url>
>
> to
>
> <url>http://rci.rutgers.edu/~oirt/repos
> <http://rci.rutgers.edu/%7Eoirt/repos></url>
>
> My apologies for any inconvenience.
>
>
> On Sep 12, 2011, at 9:15:19 AM, Charles Hedrick wrote:
>
> > I'm working madly on 1.3 before the code freeze Sept 20. At some
> point I'll try it on 2.7 and make a recommendation, but that may
> not happen for a week. I think you'll probably want to add the
> class that it's looking for to your Sakai. At first glance it
> looks like it would easy to add
> kernel-util/src/main/java/org/sakaiproject/util/ResourceLoaderMessageSource.java.
> It doesn't depend upon anything else in Sakai, just a couple of
> Java core classes and one Spring class.
> >
> > If this is the only problem with 2.7, I should probably make a
> copy of the file and put it locally in Lesson Builder. But I'm not
> sure whether I'll be able to test that before the code freeze.
> >
> > On Sep 12, 2011, at 8:34 AM, Walters, Cynthia (cmw6s) wrote:
> >
> >> Hi Charles,
> >> Thank you for your reply. I18N work is important, so I would
> not think you should back this out for LB 1.3. If there are
> isolated SVN revisions that we might examine which added it, we
> may attempt to remove it locally, but would be interested in your
> opinion here. I can take a look to see if I can identify
> revisions that addressed I18N work.
> >>
> >> Or, it may be best for us to use LB 1.2.3 (the latest) with our
> 2.7.1 production environment, and pick up LB 1.3 when we move to
> Sakai 2.8 (we typically upgrade once a year, in the spring).
> >>
> >> So at this point, LB 1.3 does not appear to support Sakai 2.7.
> >>
> >> Thanks,
> >> Cynthia Gast Walters @ UVa
> >>
> >> ________________________________________
> >> From: Hedrick Charles [hedrick at rutgers.edu
> <mailto:hedrick at rutgers.edu>]
> >> Sent: Friday, September 09, 2011 11:31 PM
> >> 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
> >>
> >> ugh. The current recommended approach for internationalization
> uses ResourceLoaderMessageSource. That's apparently not present in
> 2.7. I'm not sure how complex it would be to back out of the
> internationalization work done for 1.3.
> >>
> >> On Sep 9, 2011, at 5:05:11 PM, Walters, Cynthia (cmw6s) wrote:
> >>
> >>> Hello:
> >>>
> >>> Thanks to the recent changes made for Lesson Builder (esp. the
> popAdvisor() change), I'm now able to get the latest Lesson
> Builder 1.3.x to compile and build with our 2.7.1 code. I deleted
> all former lessonbuilder artifacts from our tomcat installation
> before building and deploying. Unfortunately, when restarting
> tomcat (with auto.ddl=true), we see an error resulting in a
> stacktrace, partially copied below, and LB fails to run ("Unable
> to find registered context for tool with ID
> sakai.lessonbuildertool"). I wonder if anyone has built LB 1.3.x
> with Sakai 2.7.1 and is successfully running it?
> >>>
> >>> Any guidance on this issue is appreciated, maybe I missed
> something. Note that we do have LB 1.2.2 running successfully
> with Sakai 2.7.1 (for evaluation).
> >>>
> >>> I should also note (in case it is pertinent), we append ".uva"
> to each version number to ensure we run with the versions we build
> locally, so all LB pom files are adjusted to use
> version=1.3.1.uva, and our uva versions for dependent tools. For
> the main LB pom, these versions are in place:
> >>>
> >>> <parent>
> >>> <groupId>org.sakaiproject.purepoms</groupId>
> >>> <artifactId>sakai-edu-tool</artifactId>
> >>> - <version>2.9-SNAPSHOT</version>
> >>> + <version>2.7.10.uva</version> <!-- UVa pure-poms with
> >>> + Sakai 2.7.1 -->
> >>> <!-- <version>2.8.1</version> --> <!-- purepom deployed with
> sakai-2.8.0 -->
> >>> </parent>
> >>>
> >>> <name>sakai-lessonbuildertool base pom</name>
> >>> <groupId>org.sakaiproject.lessonbuilder</groupId>
> >>> <artifactId>sakai-lessonbuildertool-tool-base</artifactId>
> >>> - <version>1.3-SNAPSHOT</version>
> >>> + <version>1.3.1.uva</version> <!-- note, uva making this 1.3.1
> >>> + anticipating next tag from 1.3.x -->
> >>> <packaging>pom</packaging>
> >>>
> >>> <profile>
> >>> <id>sakai-2.8</id>
> >>> + <activation>
> >>> + <activeByDefault>true</activeByDefault>
> >>> + </activation>
> >>>
> >>>
> >>> + <!--
> <sakai.assignment.version>2.8.0</sakai.assignment.version> -->
> >>> + <sakai.assignment.version>2.7.1.uva</sakai.assignment.version>
> >>> + <!--
> <sakai.entitybroker.version>1.4.1</sakai.entitybroker.version> -->
> >>> +
> <sakai.entitybroker.version>1.3.17.uva</sakai.entitybroker.version>
> >>> + <!-- <sakai.msgcntr.version>2.8.0</sakai.msgcntr.version> -->
> >>> + <sakai.msgcntr.version>2.7.4.uva</sakai.msgcntr.version>
> >>> + <!-- <sakai.samigo.version>2.8.0</sakai.samigo.version> -->
> >>> +
> >>> + <sakai.samigo.version>2.7.1.uva</sakai.samigo.version>
> >>>
> >>> ... and in the 2 'rsf-sakai/*' pom files, set 'master' and
> 'entitybroker' versions as follows:
> >>>
> >>> <parent>
> >>> <artifactId>master</artifactId>
> >>> <groupId>org.sakaiproject</groupId>
> >>> - <version>2.5.2</version>
> >>> + <version>2.7.1.uva</version>
> >>> <relativePath>../master/pom.xml</relativePath>
> >>> </parent>
> >>>
> >>> <dependency>
> >>> <groupId>org.sakaiproject.entitybroker</groupId>
> >>> <artifactId>entitybroker-api</artifactId>
> >>> - <version>1.3.3</version>
> >>> + <version>${sakai.entitybroker.version}</version>
> >>> <type>jar</type>
> >>>
> >>>
> >>> Here is the partial stack trace from catalina.out:
> >>>
> >>> 2011-09-09 15:36:23,137 INFO main
> >>> org.apache.catalina.startup.HostConfig - Deploying web application
> >>> archive sakai-lessonbuildertool-tool.war
> >>> 2011-09-09 15:36:23,161 INFO main
> >>> org.sakaiproject.util.ToolListener - registering tools from
> >>> resource: /tools/sakai.lessonbuildertool.xml
> >>> 2011-09-09 15:36:23,163 INFO main
> >>>
> org.apache.catalina.core.ContainerBase.[Catalina].[localhost].[/saka
> >>> i-lessonbuildertool-tool] - Initializing Spring root
> >>> WebApplicationContext
> >>> 179.522: [GC [PSYoungGen: 423794K->34022K(428608K)]
> >>> 544002K->165057K(600128K), 0.0781780 secs] [Times: user=0.14
> >>> sys=0.01, real=0.08 secs]
> >>> 2011-09-09 15:36:23,395 ERROR main
> >>> org.springframework.web.context.ContextLoader - Context
> >>> initialization failed
> >>>
> org.springframework.beans.factory.CannotLoadBeanClassException:
> Cannot find class
> [org.sakaiproject.util.ResourceLoaderMessageSource] for bean with
> name 'messageSource' defined in ServletContext resource
> [/WEB-INF/applicationContext.xml]; nested exception is
> java.lang.ClassNotFoundException:
> org.sakaiproject.util.ResourceLoaderMessageSource
> >>> at
> org.springframework.beans.factory.support.AbstractBeanFactory.resolveBeanClass(AbstractBeanFactory.java:1141)
> >>> at
> org.springframework.beans.factory.support.AbstractBeanFactory.resolveBeanClass(AbstractBeanFactory.java:1105)
> >>> at
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory$1.run(AbstractAutowireCapableBeanFactory.java:386)
> >>> at java.security.AccessController.doPrivileged(Native Method)
> >>> at
> >>>
> org.springframework.beans.factory.support.AbstractAutowireCapableBea
> >>> nFactory.createBean(AbstractAutowireCapableBeanFactory.java:380)
> >>> [...]
> >>>
> >>>
> >>>
> >>> Thanks for any advice,
> >>> Cynthia Gast Walters @ UVa
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>
> >>> From: Walters, Cynthia (cmw6s)
> >>> Sent: Wednesday, September 07, 2011 11:01 AM
> >>> To: Charles Hedrick
> >>> 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
> >>>
> >>> 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
> <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
> Charles
> >>> Hedrick [hedrick at rutgers.edu <mailto:hedrick at rutgers.edu>]
> >>> Sent: Tuesday, September 06, 2011 4:57 PM
> >>> 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
> >>>
> >>> 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/ja
> >>>>>>>
> va/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/ja
> >>>>>>>
> va/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/ja
> >>>>>>>
> va/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/ja
> >>>>>>>
> va/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/ja
> >>>>>>>
> va/org/sakaiproject/lessonbuildertool/service/LessonBuilderAcces
> >>>>>>> sService.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/ja
> >>>>>>>
> va/org/sakaiproject/lessonbuildertool/service/LessonBuilderAcces
> >>>>>>> sService.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/ja
> >>>>>>>
> va/org/sakaiproject/lessonbuildertool/service/LessonBuilderAcces
> >>>>>>> sService.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"
> >>>>>>
> >>>>>
> >>>>>
> >>>>
> >>>>
> >>>
> >>>
> >>
> >
> > _______________________________________________
> > 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
> 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"
--
==================================
Adrian Fish
Software Engineer
B66 Management School
Lancaster University
Lancaster
LA1 4YW
http://www.sakaiproject.org
http://confluence.sakaiproject.org/display/YAFT/Yaft
http://confluence.sakaiproject.org/display/CLOG/Home
http://confluence.sakaiproject.org/display/BBB/Home
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20110922/922c3f7b/attachment.html
More information about the sakai-dev
mailing list