[Building Sakai] Assemblies

[Adrian Fish]

Thanks Aaron.

Don't assemblies have some use outside of the full Sakai build scenario,
though? I just find them useful for building a zip that can be overlaid
onto a production server, and the idea of the tool maintainer maintaining
the list of files that goes into that zip, via the assembly, seems sound.
So, nothing to do with indies, or full builds, just making it a bit easier
to do individual tool upgrades to production machines without needing the
source or dev tools to be on that machine.

Cheers,
Adrian.


On 12 November 2013 12:21, Aaron Zeckoski <azeckoski at unicon.net> wrote:

> I think this was best covered in this email thread (snippet below) but
> as part of https://jira.sakaiproject.org/browse/SAK-23907 the
> assemblies were deleted from all core code in trunk and generally
> speaking, contrib projects should follow this practice (though nothing
> says they have to, there just won't be any community support for an
> assembly style build).
>
> -AZ
>
> On Thu, Sep 12, 2013 at 3:45 PM, Aaron Zeckoski <azeckoski at unicon.net>
> wrote:
> > This is a "heads up" (warning) for all developers and contrib tool
> authors.
> >
> > With the completion of https://jira.sakaiproject.org/browse/SAK-23907
> > we will have removed all indies (projects which were versioned
> > separately from the main Sakai version and downloaded as a binary
> > instead of built during regular builds) and all indie project versions
> > (e.g. sakai.jsf.version) from the corporate POM (a.k.a. master). This
> > change includes the kernel. This has been committed to trunk as of
> > today and should be working for all core projects.
> >
> > Any contrib tools which referenced older versions manually (e.g.
> > 1.4.0-SNAPSHOT for kernel) or used the project versions will fail to
> > build against trunk after today. All non-core code should use the
> > Sakai master pom as parent and should not reference versions directly
> > but should instead exclude the version for all Sakai dependencies and
> > all maven dependency management to handle the versioning.
> >
> > Look at the projects in the core for examples of the right way to do
> this.
> >
> > Let me know if you have any questions.
> > -AZ
>
>
> On Tue, Nov 12, 2013 at 6:52 AM, Adrian Fish <adrian.r.fish at gmail.com>
> wrote:
> > I know there was recently discussion involving removing the assemblies
> from
> > tools, since they don't make sense outside the context of independent
> > builds. Was a decision reached on that?
> >
> > Cheers,
> > Adrian.
> >
> > _______________________________________________
> > 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"
>
>
>
> --
> Aaron Zeckoski - Software Architect - http://tinyurl.com/azprofile
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20131112/d2dcf623/attachment.html