[cle-release-team] Kernel terracotta module?

[Matthew Jones]

Getting it up is really super easy, I've always got stuck at what to put in
the settings.xml to make it proxy stuff correctly. Everyone would have to
put that in to use it, or we'd have to distribute that in the master pom.

It feels like it's something like:

<mirrors>
  <mirror>
      <id>central-internal-repository</id>
      <name>Maven Repository Manager proxy</name>
      <url>http://nexusserver/content/repositories/central/</url>
      <mirrorOf>central</mirrorOf>
    </mirror>
    <mirror>
        <id>sakai-internal-repository</id>
        <name>Maven Repository Manager proxy</name>
        <url>http://nexusserver/content/repositories/sakai-proxy</url>
        <mirrorOf>sakai-maven</mirrorOf>
    </mirror>
</mirrors>

And you have to set up each repository mirror individually in the nexus
proxy and it has to exactly overlap what's in the repositories section.

And you have to have the proxy setup *before* the thing you want to proxy
actually becomes unavailable. :)


On Fri, Jan 25, 2013 at 1:56 PM, Noah Botimer <botimer at umich.edu> wrote:

> Naive question: have we ever tried to get Nexus or Artifactory up as a
> cache/proxy? We mirror a lot of third party jars and so on manually, which
> is a pain. It seems that we would gain from having a repository manager
> rather than a raw directory [1]. As I say -- this may be naive or just too
> much work.
>
>
> http://www.sonatype.com/people/2012/07/wait-you-dont-have-a-repository-manager/
>
> Thanks,
> -Noah
>
> On Jan 4, 2013, at 10:50 AM, Cris J Holdorph wrote:
>
> It would be better to be moved to a special profile to not build by
> default.  I would not characterize it as dead, at least from the
> perspective of non-functional.  It did work.  You could characterize it
> as "not used" if you wish.
>
> The page Seth pointed out really only describes one REALLY big problem
> that was not overcome.  That was with JSF component trees.  This problem
> only affects JSF tools.  Using Terracotta, individual tools have to be
> 'terracotta enabled' on a per tool basis.  So this problem essentially
> means most JSF tools would not be terracotta-enabled or at least it
> would be difficult.
>
> This functionality does give Sakai a very very slight answer to
> clustering/fail over.  If it's completely removed then we're back to no
> answer whatsoever.
>
> I have personally experienced the Terracotta repos being missing, so I
> completely understand that problem in how it impacts builds.  I think
> moving the kernel-tim module out to a different profile will help with
> this problem while retaining the code.
>
> ---- Cris J H
>
> On 01/04/2013 08:17 AM, Maurer, Christopher Wayne wrote:
>
> I'm in favor of at least either removing the repo, or removing that
>
> module from kernel's pom so it doesn't build.  Maybe put it in a profile
>
> or something?  The nightly build has been going for about an hour and
>
> it's still in kernel cause it's trying to get lots of artifacts from
>
> that terracotta repo.
>
>
>  Chris
>
>
> From: Matthew Jones <matthew at longsight.com <mailto:matthew at longsight.com<matthew at longsight.com>
> >>
>
> Date: Friday, January 4, 2013 9:41 AM
>
> To: Seth Theriault <slt at columbia.edu <mailto:slt at columbia.edu<slt at columbia.edu>
> >>
>
> Cc: Chris Maurer <chmaurer at iupui.edu <mailto:chmaurer at iupui.edu<chmaurer at iupui.edu>>>,
> Cris
>
> J Holdorph <holdorph at unicon.net <mailto:holdorph at unicon.net<holdorph at unicon.net>
> >>,
>
> "dmccallum at unicon.net <mailto:dmccallum at unicon.net <dmccallum at unicon.net>
> >"
>
> <dmccallum at unicon.net <mailto:dmccallum at unicon.net <dmccallum at unicon.net>
> >>,
>
> "cle-release-team at collab.sakaiproject.org
>
> <mailto:cle-release-team at collab.sakaiproject.org<cle-release-team at collab.sakaiproject.org>
> >"
>
> <cle-release-team at collab.sakaiproject.org
>
> <mailto:cle-release-team at collab.sakaiproject.org<cle-release-team at collab.sakaiproject.org>
> >>
>
> Subject: Re: [cle-release-team] Kernel terracotta module?
>
>
> From what I can see, kernel-tim was an example for how to Terracotta
>
> enable classes. However nothing was really ever set up to run with
>
> Terracotta, at least nothing I can see committed back to trunk for over
>
> 4 years.
>
>
> All this module does is pack a terracotta.xml file into a jar. I don't
>
> see any other dependencies to terracotta in the poms, and by default the
>
> functionality is disabled. I believe with the unreliability of this
>
> repository and the fact that it's not used that this module can either
>
> be commented out or put into a special profile.
>
>
>
> On Fri, Jan 4, 2013 at 9:34 AM, Seth Theriault <slt at columbia.edu
>
> <mailto:slt at columbia.edu <slt at columbia.edu>>> wrote:
>
>
>    Hello,
>
>
>    I thought the Terracotta stuff was dead based on these problems:
>
>
>
> https://confluence.sakaiproject.org/display/TERRA/Sakai+Session+Clustering+Problems+and+Ideas
>
>
>    (previously discussed in a TCC thread)
>
>
>    Perhaps Chris Holdorph or Dan McCallum can shed some light on this, so
>
>    I have cc'd them.
>
>
>    Seth
>
>
>    On Fri, Jan 4, 2013 at 9:28 AM, Maurer, Christopher Wayne
>
>    <chmaurer at iupui.edu <mailto:chmaurer at iupui.edu <chmaurer at iupui.edu>>>
> wrote:
>
> Anyone know if the terracotta stuff is being used at all? (kernel-tim
> module
>
> inside kernel)
>
> The terracotta maven repo seems to be down and has jacked up the nightly
>
> builds for a while.  I added the stuff to sakai's maven repo, but it's
> still
>
> checking that repo and has to wait for it to timeout.  That led me down the
>
> path of wondering if we need to build that module at all.  Any thoughts?
>
>
> Chris
>
>
> _______________________________________________
>
> cle-release-team mailing list
>
> cle-release-team at collab.sakaiproject.org
>
>    <mailto:cle-release-team at collab.sakaiproject.org<cle-release-team at collab.sakaiproject.org>
> >
>
> http://collab.sakaiproject.org/mailman/listinfo/cle-release-team
>
>
>    _______________________________________________
>
>    cle-release-team mailing list
>
>    cle-release-team at collab.sakaiproject.org
>
>    <mailto:cle-release-team at collab.sakaiproject.org<cle-release-team at collab.sakaiproject.org>
> >
>
>    http://collab.sakaiproject.org/mailman/listinfo/cle-release-team
>
>
>
> _______________________________________________
> cle-release-team mailing list
> cle-release-team at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/cle-release-team
>
>
>
> _______________________________________________
> cle-release-team mailing list
> cle-release-team at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/cle-release-team
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/cle-release-team/attachments/20130125/7738f9b7/attachment-0006.html