<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Extentions and the Build Harness in Alfresco Archive</title>
    <link>https://connect.hyland.com/t5/alfresco-archive/extentions-and-the-build-harness/m-p/30284#M15542</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;It seems like the build harness if fairly intuitive for adding extentions. with about two minutes of digging I found where to add my stuff to get it build my exntion.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;What is less intuitive to me is how to get the webclient build to include my extention components.&amp;nbsp; I looked around for a bit in the build, searched the forums and dug in the wiki for a bit.&amp;nbsp; I know I can MAKE it work but I thought I'd ask for the best practices.&amp;nbsp; &lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Just as I need a way to make extentions to the afresco source so I can upgrade without fear (or upgrade with less fear) and re-work; I need the same capability from the build harness itself and from the harness of individual components.&amp;nbsp; &lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;That is unless you are headed in the direction of making extentions deployable units themselves.&amp;nbsp; That is not the direction i see looking at the current state of affairs.&amp;nbsp; I assume not.&amp;nbsp; The reason to look for something like that is, I may not want to, or may not be able to recompile, repackage my extention every time i build alfresco.&amp;nbsp; I am not keen on forcing reqression tests even with the support of JUNIT an other tools.&amp;nbsp; Every time I do a checkout and build I have to wonder is something slipped through the process and polluted my branch/tag/whatever.&amp;nbsp; In this way I think of compiled packages as wines.&amp;nbsp; Guard against bit rot with your nightly/continuous builds.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Sun, 16 Apr 2006 07:59:10 GMT</pubDate>
    <dc:creator>rdanner</dc:creator>
    <dc:date>2006-04-16T07:59:10Z</dc:date>
    <item>
      <title>Extentions and the Build Harness</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/extentions-and-the-build-harness/m-p/30284#M15542</link>
      <description>It seems like the build harness if fairly intuitive for adding extentions. with about two minutes of digging I found where to add my stuff to get it build my exntion.What is less intuitive to me is how to get the webclient build to include my extention components.&amp;nbsp; I looked around for a bit in the b</description>
      <pubDate>Sun, 16 Apr 2006 07:59:10 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/extentions-and-the-build-harness/m-p/30284#M15542</guid>
      <dc:creator>rdanner</dc:creator>
      <dc:date>2006-04-16T07:59:10Z</dc:date>
    </item>
    <item>
      <title>Re: Extentions and the Build Harness</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/extentions-and-the-build-harness/m-p/30285#M15543</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Yes, although there isn't a lot of evidence to support it we are working towards being able to make extentions deployable, there are a few things we still need to do to realise this but hopefully it will make it into the 1.3 release.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;In the meantime, any JAR file in 3rd-party/lib not on the excluded list will get pulled into the WAR file (in WEB-INF/lib) so you could always get your extension to build and copy it there.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 19 Apr 2006 22:21:13 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/extentions-and-the-build-harness/m-p/30285#M15543</guid>
      <dc:creator>gavinc</dc:creator>
      <dc:date>2006-04-19T22:21:13Z</dc:date>
    </item>
    <item>
      <title>Re: Extentions and the Build Harness</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/extentions-and-the-build-harness/m-p/30286#M15544</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;BLOCKQUOTE class="jive-quote"&gt;Yes, although there isn't a lot of evidence to support it we are working towards being able to make extentions deployable, there are a few things we still need to do to realise this but hopefully it will make it into the 1.3 release.&lt;BR /&gt;&lt;BR /&gt;In the meantime, any JAR file in 3rd-party/lib not on the excluded list will get pulled into the WAR file (in WEB-INF/lib) so you could always get your extension to build and copy it there.&lt;/BLOCKQUOTE&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;I think what has been done so far is great, I'm just one of those whiners &lt;img id="smileyhappy" class="emoticon emoticon-smileyhappy" src="https://connect.hyland.com/i/smilies/16x16_smiley-happy.png" alt="Smiley Happy" title="Smiley Happy" /&gt; Is there a Official Road Map for this?&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 20 Apr 2006 01:49:01 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/extentions-and-the-build-harness/m-p/30286#M15544</guid>
      <dc:creator>rdanner</dc:creator>
      <dc:date>2006-04-20T01:49:01Z</dc:date>
    </item>
  </channel>
</rss>

