You are viewing a plain text version of this content. The canonical link for it is here.
Posted to general@gump.apache.org by "Adam R. B. Jack" <aj...@trysybase.com> on 2004/06/10 01:55:03 UTC
Fw: [GUMP@brutus]: jakarta-commons-codec-11/commons-codec-11 failed
Hmm, this is annoying.
> BUILD FAILED
> /usr/local/gump/public/workspace/jakarta-commons-codec-11/build.xml:110:
Warning: Could not find file /usr/local/gump/public/workspace/LICENSE to
copy.
There is a hard coded usage of ../LICENSE, so when I put this out of the
jakarta-commons module into it's own, It fails.
<target name="dist" depends="compile,javadoc"
description="Create binary distribution">
<mkdir dir="${dist.home}"/>
<copy file="../LICENSE"
todir="${dist.home}"/>
<copy file="${basedir}/RELEASE-NOTES.txt"
todir="${dist.home}"/>
<antcall target="jar"/>
</target>
Any thoughts?
I really need to be able to produce this in order to get xmlrpc, inorder to
get cocoon...
regards,
Adam
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@gump.apache.org
For additional commands, e-mail: general-help@gump.apache.org
Re: Fw: [GUMP@brutus]: jakarta-commons-codec-11/commons-codec-11 failed
Posted by "Adam R. B. Jack" <aj...@trysybase.com>.
> >This is an historic (tagged) version I am trying to
> >construct, 'cos WS-XMLRPC can't built against head, and won't move up.
> >
> If it is tagged and never going to change, you could simply create a
> packaged project.
Ah, of course. Staring me in the face. Thank you. :)
> I wonder, is there a way to create a message digest
> of a tagged cvs repository? As long as the digest of the cvs continues
> to match the stored digest, all is well (use packaged project), else
> cause build to fail.
I think this is cleaver, but perhaps going to far to cope w/ folks doing
stuff (changing a release) that folks really probably don't ever do. We'd
burn a lot of cycles and catch a glitch once in a blue moon. That said, it
is an interesting idea. :)
regards
Adam
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@gump.apache.org
For additional commands, e-mail: general-help@gump.apache.org
Re: Fw: [GUMP@brutus]: jakarta-commons-codec-11/commons-codec-11
failed
Posted by Michael Davey <Mi...@coderage.org>.
Adam R. B. Jack wrote:
>
>This is an historic (tagged) version I am trying to
>construct, 'cos WS-XMLRPC can't built against head, and won't move up.
>
If it is tagged and never going to change, you could simply create a
packaged project. I wonder, is there a way to create a message digest
of a tagged cvs repository? As long as the digest of the cvs continues
to match the stored digest, all is well (use packaged project), else
cause build to fail.
--
Michael
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@gump.apache.org
For additional commands, e-mail: general-help@gump.apache.org
Re: Fw: [GUMP@brutus]: jakarta-commons-codec-11/commons-codec-11 failed
Posted by "Adam R. B. Jack" <aj...@trysybase.com>.
> >Just to clarify. The commons-codec HEAD build works fine within
> >jakarta-commons. This is an historic (tagged) version I am trying to
> >construct, 'cos WS-XMLRPC can't built against head, and won't move up.
> >
> Ah, okay. Why won't they move up?
They just don't want to move up, they are like the Sloth (in the kid's book
by Eric Carle), they are content to move 'slowly slowly slowly...'. Gump
really doesn't have a right/need to judge, we aren't trying to promote
change (instability), just detect issues.
> Does
> Gump implement some kind of pre-target and post-target execution?
Hmm, it does do some pre/post build work, but nothing (yet) customizable.
The pre-build includes allowing <mkdir and <delete , and the post-build
includes publishing to a repository. Customization is worth considering one
day.
regards
Adam
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@gump.apache.org
For additional commands, e-mail: general-help@gump.apache.org
Re: Fw: [GUMP@brutus]: jakarta-commons-codec-11/commons-codec-11
failed
Posted by Michael Davey <Mi...@coderage.org>.
Adam R. B. Jack wrote:
>
>Just to clarify. The commons-codec HEAD build works fine within
>jakarta-commons. This is an historic (tagged) version I am trying to
>construct, 'cos WS-XMLRPC can't built against head, and won't move up.
>
Ah, okay. Why won't they move up?
>I
>don't think I can (or would) nag anybody to change a tagged release.
>
>
>
:)
>I am tempted to (temporarily) put a LICENSE file in the workspace root.
>Crappy, but practical. Better ideas?
>
>
I think any solution would be a kludge. I guess you could write your
own dist target or build.xml file; or put the license file in the
workspace route just before the build and remove it just after. Does
Gump implement some kind of pre-target and post-target execution?
--
Michael Davey
Collabra Ltd - networking people, processes & technology
http://collabra.ltd.uk/
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@gump.apache.org
For additional commands, e-mail: general-help@gump.apache.org
Re: Fw: [GUMP@brutus]: jakarta-commons-codec-11/commons-codec-11 failed
Posted by "Adam R. B. Jack" <aj...@trysybase.com>.
> Make jakarta-commons-codec-11 depend upon commons-build. Get the
> license file from commons-build. Send a patch to the codec crew. Nag
> them 'til they commit.
>
> Probably not what you wanted to hear.
Just to clarify. The commons-codec HEAD build works fine within
jakarta-commons. This is an historic (tagged) version I am trying to
construct, 'cos WS-XMLRPC can't built against head, and won't move up. I
don't think I can (or would) nag anybody to change a tagged release.
I am tempted to (temporarily) put a LICENSE file in the workspace root.
Crappy, but practical. Better ideas?
regards,
Adam
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@gump.apache.org
For additional commands, e-mail: general-help@gump.apache.org
Re: Fw: [GUMP@brutus]: jakarta-commons-codec-11/commons-codec-11
failed
Posted by Michael Davey <Mi...@coderage.org>.
Adam R. B. Jack wrote:
>Hmm, this is annoying.
>
>
>
>>BUILD FAILED
>>/usr/local/gump/public/workspace/jakarta-commons-codec-11/build.xml:110:
>>
>>
>Warning: Could not find file /usr/local/gump/public/workspace/LICENSE to
>copy.
>
>There is a hard coded usage of ../LICENSE, so when I put this out of the
>jakarta-commons module into it's own, It fails.
>
>
>Any thoughts?
>
>
Make jakarta-commons-codec-11 depend upon commons-build. Get the
license file from commons-build. Send a patch to the codec crew. Nag
them 'til they commit.
Probably not what you wanted to hear.
--
Michael
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@gump.apache.org
For additional commands, e-mail: general-help@gump.apache.org