You are viewing a plain text version of this content. The canonical link for it is here.
Posted to alexandria-dev@jakarta.apache.org by Joe Gaffey <Jo...@gradient.ie> on 2001/08/14 12:59:33 UTC
problems with build, changelog and blamelog
Hi all,
I have been trying to get alexandria going as my build mechanism as an
interface for our intranet. I think it is a great tool but have been having
a lot of problems. I am sending it to this mailing list as the user one
seems to be inactive.
I am doing all my work on Linux using Ant 1.3 and either JDK1.2.2 or JDK1.3
Firstly I had a problem with building, that after much pain found that there
was a problem with the classpath definition in build.build.xml, in that it
expected tools.jar to be at '${java.home}/../lib/tools.jar' whereas in my
system it is at '${java.home}/lib/tools.jar'. Have I set up something wrong
in my system? If this is the way that it should be then I would like to
submit this as a bug fix. How do I do this?
Secondly I had a problem with blamelog. It just produced blank blames. After
investigation I realised that the extraction of the info from the initial
file produced by blog was the problem, ie the intermediate file was produced
OK but the extraction of what we needed using blame.kull.xsl was not
functioning. With my limited xsl/xml experience I looked at the file. I am
not certain how it was supposed to work but found that if I put in place an
extra template match for 'msg', and modified the build template match that
this solved the problem:
<xsl:template match="build">
<xsl:if test="position()<$limit+1">
<xsl:copy>
<xsl:apply-templates select="@*"/>
<xsl:apply-templates select="msg"/>
</xsl:copy>
</xsl:if>
</xsl:template>
<xsl:template match="msg">
<xsl:copy>
<xsl:apply-templates select="@*"/>
</xsl:copy>
</xsl:template>
Again, this works for me, but should it always be dome like this? If so then
I would like to submit this!
Finally I have another problem, which unfortunately I have not yet found the
solution to. This involves the Changelog part of Alexandria. Firstly,
after some frustration I got it working on my development machine, by
editing /usr/local/ant/bin/antRun, to remove the DOS style ^M characters.
However this solution did not work on my test machine. After looking at
source code etc I realised that the way that the command launcher for CVS
log works depends on the version of java present. My test machine uses JDK
1.3, whereas my development machine has only 1.2.2. Installing JDK 1.3 on
my test machine breaks the building of the changelog. It just produces an
empty log. Using ant -debug the command line seems to be: cvs log (which
works fine if I run it by hand). Does this work for anybody with jdk 1.3?
If so, have I done something silly possibly? If not, has anybody any
wonderful suggestions.
Any help/suggestions appreciated a lot,
Joe.
Joe Gaffey
Software Developer
Gradient - a Sabre Company
Ormonde House Tel: + 353 1 2400 500
12 Lower Leeson Street Fax: + 353 1 2400 501
Dublin 2 Email: joe.gaffey@gradient.ie
Ireland
Web: www.gradient.ie
www.sabre.com
---------------------------------------------------------------------
To unsubscribe, e-mail: alexandria-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: alexandria-dev-help@jakarta.apache.org
RE: problems with build, changelog and blamelog
Posted by Joe Gaffey <Jo...@gradient.ie>.
Hi again,
I just found out why the third problem below exists. It is because the cvs
log command was not taking place from the correct directory. This is
because I could not get the cvs command to work correctly in getting it to
checkout files to the correct directory - it always put them in the current
directory for me - so I just copy them to where alexandria expects them. It
worked fine until this happened. I just changed the clog basedir parameter
to suit this and all is fine. The jdk version was just a red herring, the
fact that the older version ran the command with antRun, whereas the later
one didn't, hid the problem.
Thanks, and sorry about the silly mistake.
Joe.
PS, I would still like to hear comments on the other two issues below
:)...... thanks
-----Original Message-----
From: Joe Gaffey [mailto:Joe.Gaffey@gradient.ie]
Sent: Tuesday, August 14, 2001 12:00 PM
To: alexandria-dev@jakarta.apache.org
Subject: problems with build, changelog and blamelog
Hi all,
I have been trying to get alexandria going as my build mechanism as an
interface for our intranet. I think it is a great tool but have been having
a lot of problems. I am sending it to this mailing list as the user one
seems to be inactive.
I am doing all my work on Linux using Ant 1.3 and either JDK1.2.2 or JDK1.3
Firstly I had a problem with building, that after much pain found that there
was a problem with the classpath definition in build.build.xml, in that it
expected tools.jar to be at '${java.home}/../lib/tools.jar' whereas in my
system it is at '${java.home}/lib/tools.jar'. Have I set up something wrong
in my system? If this is the way that it should be then I would like to
submit this as a bug fix. How do I do this?
Secondly I had a problem with blamelog. It just produced blank blames. After
investigation I realised that the extraction of the info from the initial
file produced by blog was the problem, ie the intermediate file was produced
OK but the extraction of what we needed using blame.kull.xsl was not
functioning. With my limited xsl/xml experience I looked at the file. I am
not certain how it was supposed to work but found that if I put in place an
extra template match for 'msg', and modified the build template match that
this solved the problem:
<xsl:template match="build">
<xsl:if test="position()<$limit+1">
<xsl:copy>
<xsl:apply-templates select="@*"/>
<xsl:apply-templates select="msg"/>
</xsl:copy>
</xsl:if>
</xsl:template>
<xsl:template match="msg">
<xsl:copy>
<xsl:apply-templates select="@*"/>
</xsl:copy>
</xsl:template>
Again, this works for me, but should it always be dome like this? If so then
I would like to submit this!
Finally I have another problem, which unfortunately I have not yet found the
solution to. This involves the Changelog part of Alexandria. Firstly,
after some frustration I got it working on my development machine, by
editing /usr/local/ant/bin/antRun, to remove the DOS style ^M characters.
However this solution did not work on my test machine. After looking at
source code etc I realised that the way that the command launcher for CVS
log works depends on the version of java present. My test machine uses JDK
1.3, whereas my development machine has only 1.2.2. Installing JDK 1.3 on
my test machine breaks the building of the changelog. It just produces an
empty log. Using ant -debug the command line seems to be: cvs log (which
works fine if I run it by hand). Does this work for anybody with jdk 1.3?
If so, have I done something silly possibly? If not, has anybody any
wonderful suggestions.
Any help/suggestions appreciated a lot,
Joe.
Joe Gaffey
Software Developer
Gradient - a Sabre Company
Ormonde House Tel: + 353 1 2400 500
12 Lower Leeson Street Fax: + 353 1 2400 501
Dublin 2 Email: joe.gaffey@gradient.ie
Ireland
Web: www.gradient.ie
www.sabre.com
---------------------------------------------------------------------
To unsubscribe, e-mail: alexandria-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: alexandria-dev-help@jakarta.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: alexandria-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: alexandria-dev-help@jakarta.apache.org