[Architecture] Release dates in product documents
Afkham Azeez
azeez at wso2.com
Wed Sep 16 02:49:51 EDT 2009
Yes, you have to do this
<copy todir="src/site" overwrite="false" includeemptydirs="false">
<fileset dir="../../docs">
<exclude name="**/images/*.*"/>
</fileset>
<filterset>
<filter token="buildNumber"
value="${buildNumber}"/>
</filterset>
</copy>
<copy todir="src/site" overwrite="false"
includeemptydirs="false">
<fileset dir="../../docs">
<include name="**/images/*.*"/>
</fileset>
</copy>
On Wed, Sep 16, 2009 at 6:18 AM, Tyrell Perera <tyrell at wso2.com> wrote:
> Adding this filter breaks .png files? Can someone verify please?
>
>
> Tyrell
>
> On Wed, Sep 16, 2009 at 11:24 AM, Afkham Azeez <azeez at wso2.com> wrote:
> > There is a small problem in creating the docs release since that is done
> > primarilly through ant. So you will have to do the following:
> > 1. Locate the following XML segment in the distribution's POM.xml file
> > <copy todir="src/site" overwrite="false" includeemptydirs="false">
> > <fileset dir="../../docs"/>
> > </copy>
> > 2. Replace it with
> > <copy todir="src/site" overwrite="false" includeemptydirs="false">
> > <fileset dir="../../docs"/>
> > <filterset>
> > <filter token="buildNumber"
> > value="${buildNumber}"/>
> > </filterset>
> > </copy>
> > 3. In the release_notes.xml file, you should specify the variable as
> > @buildNumber@ since Ant looks for that pattern when filtering.
> > --
> > Azeez
> > On Wed, Sep 16, 2009 at 1:09 AM, Ruwan Linton <ruwan at wso2.com> wrote:
> >>
> >> Hi Azeez/Senaka,
> >>
> >> It is a good tool, thanks for pointing this out. We have been using the
> >> maven filtering for the release version any way, but this will be a more
> >> elegant approach.
> >>
> >> Thanks,
> >> Ruwan
> >>
> >> Senaka Fernando wrote:
> >> > Hi all,
> >> >
> >> > Using the latest version of this plugin, you can specify both the
> >> > release version and the release date, as follows.
> >> >
> >> > <plugin>
> >> > <groupId>org.codehaus.mojo</groupId>
> >> > <artifactId>buildnumber-maven-plugin</artifactId>
> >> > <version>1.0-beta-3</version>
> >> > <configuration>
> >> >
> >> > <buildNumberPropertyName>product.version</buildNumberPropertyName>
> >> > <timestampFormat>{0, date, dd MMM
> >> > yyyy}</timestampFormat>
> >> > <format>{1}</format>
> >> > <items>
> >> > <item>timestamp</item>
> >> > <item>${pom.version}</item>
> >> > </items>
> >> > <doCheck>false</doCheck>
> >> > <doUpdate>false</doUpdate>
> >> > </configuration>
> >> > <executions>
> >> > <execution>
> >> > <phase>validate</phase>
> >> > <goals>
> >> > <goal>create</goal>
> >> > </goals>
> >> > </execution>
> >> > </executions>
> >> > </plugin>
> >> >
> >> > $product.version will give you the product version and $timestamp will
> >> > give you the release date. You need to use the following plugin
> >> > repository.
> >> >
> >> > <pluginRepository>
> >> > <id>codehaus</id>
> >> > <name>Codehaus Repository</name>
> >> > <url>http://repository.codehaus.org</url>
> >> > </pluginRepository>
> >> >
> >> > Having this done, you only need to set the product version in the
> >> > relevant pom files.
> >> >
> >> > Thanks,
> >> > Senaka.
> >> >
> >> > On Tue, Sep 15, 2009 at 2:04 PM, Senaka Fernando <senaka at wso2.com
> >> > <mailto:senaka at wso2.com>> wrote:
> >> >
> >> > +1,
> >> >
> >> > Integrated to G-Reg as well.
> >> >
> >> > Thanks,
> >> > Senaka.
> >> >
> >> >
> >> > On Tue, Sep 15, 2009 at 1:41 PM, Tyrell Perera <tyrell at wso2.com
> >> > <mailto:tyrell at wso2.com>> wrote:
> >> >
> >> > +1
> >> >
> >> > Integrated to the MS build.
> >> >
> >> > Tyrell
> >> >
> >> > On Tue, Sep 15, 2009 at 1:28 PM, sumedha <sumedha at wso2.com
> >> > <mailto:sumedha at wso2.com>> wrote:
> >> > > This is great !!!. saves lot of trouble..
> >> > > /sumedha
> >> > >
> >> > > Afkham Azeez wrote:
> >> > >> Hi Folks,
> >> > >> We have been manually changing the release dates in the
> >> > release notes.
> >> > >> Many times, we have missed changing the release date. Today
> >> > I was able
> >> > >> to find a better way of doing this using the Maven
> >> > build-number
> >> > >> plugin. I have integrated this with WSAS. Here is how you
> >> > do it.
> >> > >>
> >> > >> 1. Add the plugin repository
> >> > >>
> >> > >> <pluginRepositories>
> >> > >> <pluginRepository>
> >> > >> <id>tlc</id>
> >> > >> <name>TLC Repository</name>
> >> > >> <url>http://commons.ucalgary.ca/pub/m2</url>
> >> > >> </pluginRepository>
> >> > >> </pluginRepositories>
> >> > >>
> >> > >> 2. Add the plugin to the product distributions POM
> >> > >>
> >> > >> <plugin>
> >> > >> <groupId>org.codehaus.mojo</groupId>
> >> > >>
> >> > <artifactId>maven-buildnumber-plugin</artifactId>
> >> > >> <version>0.9.4</version>
> >> > >> <configuration>
> >> > >> <format>{0,date,dd MMM yyyy}</format>
> >> > >> <items>
> >> > >> <item>timestamp</item>
> >> > >> </items>
> >> > >> <doCheck>false</doCheck>
> >> > >> <doUpdate>false</doUpdate>
> >> > >> </configuration>
> >> > >> <executions>
> >> > >> <execution>
> >> > >> <phase>validate</phase>
> >> > >> <goals>
> >> > >> <goal>create</goal>
> >> > >> </goals>
> >> > >> </execution>
> >> > >> </executions>
> >> > >> </plugin>
> >> > >>
> >> > >> 3. Where ever you use the release date, use the
> >> > ${buildNumber} property
> >> > >>
> >> > >> 4. That is it!
> >> > >>
> >> > >> Please integrate this with the other products as well,
> >> > before we cut
> >> > >> today's release.
> >> > >>
> >> > >> --
> >> > >> --
> >> > >> Afkham Azeez
> >> > >> azeez at wso2.com <mailto:azeez at wso2.com>
> >> > <mailto:azeez at wso2.com <mailto:azeez at wso2.com>>
> >> > >> WSO2 Inc. http://wso2.com
> >> > >> Blog: http://afkham.org
> >> > >>
> >> > >>
> >> >
> >> >
> ------------------------------------------------------------------------
> >> > >>
> >> > >> _______________________________________________
> >> > >> Architecture mailing list
> >> > >> Architecture at wso2.org <mailto:Architecture at wso2.org>
> >> > >>
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
> >> > >
> >> > >
> >> > > _______________________________________________
> >> > > Architecture mailing list
> >> > > Architecture at wso2.org <mailto:Architecture at wso2.org>
> >> > > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
> >> > >
> >> >
> >> >
> >> >
> >> > --
> >> > Tyrell Perera
> >> > WSO2, Inc.; http://www.wso2.com/
> >> > "The Open Source SOA Company"
> >> >
> >> > http://www.linkedin.com/in/tyrell
> >> > http://tyrellperera.blogspot.com
> >> > http://twitter.com/tyrellperera
> >> >
> >> > _______________________________________________
> >> > Architecture mailing list
> >> > Architecture at wso2.org <mailto:Architecture at wso2.org>
> >> > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
> >> >
> >> >
> >> >
> >> >
> ------------------------------------------------------------------------
> >> >
> >> > _______________________________________________
> >> > Architecture mailing list
> >> > Architecture at wso2.org
> >> > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
> >> >
> >>
> >>
> >> --
> >> Ruwan Linton
> >> Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb
> >> WSO2 Inc.; http://wso2.org
> >> email: ruwan at wso2.com; cell: +94 77 341 3097
> >> blog: http://blog.ruwan.org
> >>
> >>
> >>
> >> _______________________________________________
> >> Architecture mailing list
> >> Architecture at wso2.org
> >> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
> >
> >
> >
> > --
> > --
> > Afkham Azeez
> > azeez at wso2.com
> > WSO2 Inc. http://wso2.com
> > Blog: http://afkham.org
> >
> > _______________________________________________
> > Architecture mailing list
> > Architecture at wso2.org
> > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
> >
> >
>
>
>
> --
> Tyrell Perera
> WSO2, Inc.; http://www.wso2.com/
> "The Open Source SOA Company"
>
> http://www.linkedin.com/in/tyrell
> http://tyrellperera.blogspot.com
> http://twitter.com/tyrellperera
>
> _______________________________________________
> Architecture mailing list
> Architecture at wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
--
--
Afkham Azeez
azeez at wso2.com
WSO2 Inc. http://wso2.com
Blog: http://afkham.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.wso2.org/pipermail/architecture/attachments/20090916/9df2535a/attachment.html>
More information about the Architecture
mailing list