[Building Sakai] sakai-2.9.x-all build broken

[Matthew Jones]

Also for 2.9, Aaron did quite a bit of work to turn *most* of kernel-util
into a service, so that if you modified kernel you don't have to re-build
everything. There are still classes in kernel-util but they
aren't implementations anymore so they should be changed MUCH less often
(like never in a major release)

https://jira.sakaiproject.org/browse/KNL-861

For instance FormattedText in 2.9 (over in kernel-impl now)
https://source.sakaiproject.org/svn/kernel/branches/kernel-1.3.x/kernel-util/src/main/java/org/sakaiproject/util/FormattedText.java

In 2.8
https://source.sakaiproject.org/svn/kernel/branches/kernel-1.2.x/kernel-util/src/main/java/org/sakaiproject/util/FormattedText.java

On Thu, Nov 15, 2012 at 3:12 PM, David Adams <da1 at vt.edu> wrote:

> Steve Swinsburg wrote:
> > This is an interesting discussion as it directly relates to the
> > usefulness of the indies projects. A question, why do you want
> > to build the source of all indies? Unless you've modified them,
> > you can just let Sakai deploy the binaries and then updates are
> > as easy as changing the version in the master pom.
>
> We do modify several of the indies, however, more importantly, we modify
> the kernel, which I believe requires us to build everything that includes
> the kernel-util jar (ie, everything). But I don't claim to understand the
> build and deploy process very well. Delivery of elements of Sakai as
> overlay zipfiles can also cause other problems for people who need to do
> any customization to Tomcat's directory structure.
>
> As for updating the version of indies in the master pom and redeploying,
> isn't that going to introduce other version conflicts? Seems to me that to
> upgrade a particular subproject, updating the source URL in the
> svn:externals property, updating, and rebuilding is far safer.
>
> In general I personally don't understand why all of these core projects
> are being moved to "indie" releases. Is it to shorten compile times? When I
> download the source code for an open source project, I don't expect that
> over half of it will be delivered at deploy time as prebuilt zipfile
> overlays from remote servers over which I have no control. If we wanted the
> binary distribution, we would download the binary distribution.
>
> Finally, if there's no benefit to providing all of the source code, then
> why is there a sakai-2.9.x-all branch available? If sakai-2.9.x-all has a
> purpose, then -all tags surely do as well.
>
> -dave
> --
> David Adams
> Director, Learning Systems Integration and Support
> Virginia Tech Learning Technologies
> _______________________________________________
> 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/20121115/a7a318f9/attachment.html