You are viewing a plain text version of this content. The canonical link for it is here.
Posted to fop-dev@xmlgraphics.apache.org by Stefan Bodewig <bo...@apache.org> on 2001/12/13 18:03:24 UTC
Re: [GUMP] Build Failure - FOP
I'm currently not subscribed to fop-dev and responding to a post I've
picked up from the archives, sorry, please keep ant-dev in the CC.
Keiron Liddle <ke...@aftexsw.com> wrote:
> We can update the FOP build to use the core ant manifest task and a
> new ant. This is no real problem.
I don't see Ant's next release before February, most probably even
later, so I'd rather recommend to use the <manifest> nested into <jar>
approach, which is going to work with Ant 1.4 and 1.4.1.
> The only thing that our task does that is different is a "BUILD-ID"
> it has "Date-Time (user@host [os])".
You should be able to emulate that using property expansion, something
like
<tstamp>
<pattern property="ts" format="yyyyMMdd-HHmmss-z" />
</tstamp>
<jar ...>
<manifest>
<attribute name="Build-Id" value="${ts} (${user.name} ...)" />
</manifest>
</jar>
you get the idea. Hostname would be the only tricky part.
> How stable are these tasks and any other new tasks.
The manifest task itself is just a wrapper around the nested
<manifest> element of <jar>, which has been around for some time (and
even has JUnit testcases).
I think it is quite stable, but still hasn't been tested by that many
people. I'm not aware of any other tasks - but we should talk about
adding the things that make your <xslt> task the preferred choice over
<style> to Ant's core task so that people outside the FOP community
can benefit from it as well 8-)
Cheers
Stefan
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-dev-unsubscribe@xml.apache.org
For additional commands, email: fop-dev-help@xml.apache.org
Re: [GUMP] Build Failure - FOP
Posted by Stefan Bodewig <bo...@apache.org>.
On Fri, 14 Dec 2001, Keiron Liddle <ke...@aftexsw.com> wrote:
> Thanks, I have updated the build file to use the manifest under jar,
> works fine.
Great!
> Looking at the hostname I think that it is better left out, it may
> cause computers to attempt to connect to the internet when resolving
> the hostname.
As the original task would have done before.
I guess my response to your commit message hasn't made it to fop-dev
yet. As Diane pointed out, you can get the hostname from the
environment (at least on Windows and Unix systems), see
<http://marc.theaimsgroup.com/?l=ant-user&m=100802855231701&w=2> for
example.
> I don't know much about xslt apart from - it works.
So you know more than me.
> What sort of things need to be done/added?
> Will it become a core task or optional?
There is a built-in Ant task named <style> that has been built-in for
a long time. It performs XSLT transformations, so it seems to be in
the same area as <xslt>. I haven't looked at the code of FOP's task,
but I assume that it must be doing something better than <style> does
and therefore I would love to see <style> improved.
Stefan
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-dev-unsubscribe@xml.apache.org
For additional commands, email: fop-dev-help@xml.apache.org
Re: [GUMP] Build Failure - FOP
Posted by Stefan Bodewig <bo...@apache.org>.
On Fri, 14 Dec 2001, Keiron Liddle <ke...@aftexsw.com> wrote:
> Thanks, I have updated the build file to use the manifest under jar,
> works fine.
Great!
> Looking at the hostname I think that it is better left out, it may
> cause computers to attempt to connect to the internet when resolving
> the hostname.
As the original task would have done before.
I guess my response to your commit message hasn't made it to fop-dev
yet. As Diane pointed out, you can get the hostname from the
environment (at least on Windows and Unix systems), see
<http://marc.theaimsgroup.com/?l=ant-user&m=100802855231701&w=2> for
example.
> I don't know much about xslt apart from - it works.
So you know more than me.
> What sort of things need to be done/added?
> Will it become a core task or optional?
There is a built-in Ant task named <style> that has been built-in for
a long time. It performs XSLT transformations, so it seems to be in
the same area as <xslt>. I haven't looked at the code of FOP's task,
but I assume that it must be doing something better than <style> does
and therefore I would love to see <style> improved.
Stefan
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: [GUMP] Build Failure - FOP
Posted by Keiron Liddle <ke...@aftexsw.com>.
Thanks, I have updated the build file to use the manifest under jar, works
fine. Looking at the hostname I think that it is better left out, it may
cause computers to attempt to connect to the internet when resolving the
hostname.
I don't know much about xslt apart from - it works.
What sort of things need to be done/added?
Will it become a core task or optional?
On 2001.12.13 18:03 Stefan Bodewig wrote:
> I'm currently not subscribed to fop-dev and responding to a post I've
> picked up from the archives, sorry, please keep ant-dev in the CC.
>
> Keiron Liddle <ke...@aftexsw.com> wrote:
>
> > We can update the FOP build to use the core ant manifest task and a
> > new ant. This is no real problem.
>
> I don't see Ant's next release before February, most probably even
> later, so I'd rather recommend to use the <manifest> nested into <jar>
> approach, which is going to work with Ant 1.4 and 1.4.1.
>
> > The only thing that our task does that is different is a "BUILD-ID"
> > it has "Date-Time (user@host [os])".
>
> You should be able to emulate that using property expansion, something
> like
>
> <tstamp>
> <pattern property="ts" format="yyyyMMdd-HHmmss-z" />
> </tstamp>
> <jar ...>
> <manifest>
> <attribute name="Build-Id" value="${ts} (${user.name} ...)" />
> </manifest>
> </jar>
>
> you get the idea. Hostname would be the only tricky part.
>
> > How stable are these tasks and any other new tasks.
>
> The manifest task itself is just a wrapper around the nested
> <manifest> element of <jar>, which has been around for some time (and
> even has JUnit testcases).
>
> I think it is quite stable, but still hasn't been tested by that many
> people. I'm not aware of any other tasks - but we should talk about
> adding the things that make your <xslt> task the preferred choice over
> <style> to Ant's core task so that people outside the FOP community
> can benefit from it as well 8-)
>
> Cheers
>
> Stefan
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: [GUMP] Build Failure - FOP
Posted by Keiron Liddle <ke...@aftexsw.com>.
Thanks, I have updated the build file to use the manifest under jar, works
fine. Looking at the hostname I think that it is better left out, it may
cause computers to attempt to connect to the internet when resolving the
hostname.
I don't know much about xslt apart from - it works.
What sort of things need to be done/added?
Will it become a core task or optional?
On 2001.12.13 18:03 Stefan Bodewig wrote:
> I'm currently not subscribed to fop-dev and responding to a post I've
> picked up from the archives, sorry, please keep ant-dev in the CC.
>
> Keiron Liddle <ke...@aftexsw.com> wrote:
>
> > We can update the FOP build to use the core ant manifest task and a
> > new ant. This is no real problem.
>
> I don't see Ant's next release before February, most probably even
> later, so I'd rather recommend to use the <manifest> nested into <jar>
> approach, which is going to work with Ant 1.4 and 1.4.1.
>
> > The only thing that our task does that is different is a "BUILD-ID"
> > it has "Date-Time (user@host [os])".
>
> You should be able to emulate that using property expansion, something
> like
>
> <tstamp>
> <pattern property="ts" format="yyyyMMdd-HHmmss-z" />
> </tstamp>
> <jar ...>
> <manifest>
> <attribute name="Build-Id" value="${ts} (${user.name} ...)" />
> </manifest>
> </jar>
>
> you get the idea. Hostname would be the only tricky part.
>
> > How stable are these tasks and any other new tasks.
>
> The manifest task itself is just a wrapper around the nested
> <manifest> element of <jar>, which has been around for some time (and
> even has JUnit testcases).
>
> I think it is quite stable, but still hasn't been tested by that many
> people. I'm not aware of any other tasks - but we should talk about
> adding the things that make your <xslt> task the preferred choice over
> <style> to Ant's core task so that people outside the FOP community
> can benefit from it as well 8-)
>
> Cheers
>
> Stefan
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-dev-unsubscribe@xml.apache.org
For additional commands, email: fop-dev-help@xml.apache.org
Re: [GUMP] Build Failure - FOP
Posted by Stefan Bodewig <bo...@apache.org>.
On Thu, 13 Dec 2001, Diane Holt <ho...@yahoo.com> wrote:
> --- Stefan Bodewig <bo...@apache.org> wrote:
>> Hostname would be the only tricky part.
>
> Can't you get it from the environment -- HOSTNAME on *nix,
> COMPUTERNAME on Win* (or is COMPUTERNAME only an NT thing)?
I said tricky, not impossible 8-)
I think Erik showed the same way you suggest on ant-user two days ago.
Stefan
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: [GUMP] Build Failure - FOP
Posted by Diane Holt <ho...@yahoo.com>.
--- Stefan Bodewig <bo...@apache.org> wrote:
> Hostname would be the only tricky part.
Can't you get it from the environment -- HOSTNAME on *nix, COMPUTERNAME on
Win* (or is COMPUTERNAME only an NT thing)?
Diane
=====
(holtdl@yahoo.com)
__________________________________________________
Do You Yahoo!?
Check out Yahoo! Shopping and Yahoo! Auctions for all of
your unique holiday gifts! Buy at http://shopping.yahoo.com
or bid at http://auctions.yahoo.com
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: [GUMP] Build Failure - FOP
Posted by Diane Holt <ho...@yahoo.com>.
--- Stefan Bodewig <bo...@apache.org> wrote:
> Hostname would be the only tricky part.
Can't you get it from the environment -- HOSTNAME on *nix, COMPUTERNAME on
Win* (or is COMPUTERNAME only an NT thing)?
Diane
=====
(holtdl@yahoo.com)
__________________________________________________
Do You Yahoo!?
Check out Yahoo! Shopping and Yahoo! Auctions for all of
your unique holiday gifts! Buy at http://shopping.yahoo.com
or bid at http://auctions.yahoo.com
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-dev-unsubscribe@xml.apache.org
For additional commands, email: fop-dev-help@xml.apache.org