To whom it may concern,
Here is a script that ***points vaguely*** in the direction of the
janitorial task that Jason outlined immediately prior to his evident
leave of absence. All it does is gather (by copying - not moving) the
collection of somewhat divergently named and distributed README and
LICENSE files (or any set of files under a common directory you care to
specify via a regular expression) into a single location for ease of
review and comparison. If this isn't a complete joke, I'd appreciate
some feedback, because it does seem to me to be a somewhat asinine idea
- i.e. renaming, moving, and possibly ALTERING the content of README
and, in particular, LICENSE. Who gives a flying &^*&@ about these files
anyway? Certainly not the customer. I mean, come on, no one who is too
stupid to find/apprehend such files unless they are placed in a
standardized location and somehow formalized is ever going to so much as
**begin** to get off the ground running JBoss. The whole idea of
touching these files in the first place is one that I find highly
suspect, especially in light of the plethora of bugs and unresolved
issues that remain outstanding, not the least of which is the glaring
inadequacy of the BUILD SYSTEM, regarding which obtaining the secret
combination of key ***strokes*** that is apparently required to get the
&*@)#! THING to build would appear to be the "open source" corporation's
equivalent of acquiring the key to the proverbial "executive lavatory",
a phenomenon for which, I venture to add, the technical term
"repository" in the present case strikes me as a decidedly lame
euphemism, aside from the fact that it just happens to rhyme with
"suppository."
Having said that, I turn now to the aforementioned difficulties relating
to the aforementioned problem of obtaining a workable main trunk or
branch release, which I have not been able to do since 3.0.3. Below is
the output from the latest of my extensive history of attempts to build
either jboss-head or jboss-3.2. If someone can convince me that the
"request for help" it addresses was sincere, I will consider following
through on this. The bottom line is I just want to be able to do the
builds so that I can run JBoss in a debugger (preferably eclipse, which
I have set up,as well as Forte One CE) as a prerequisite to getting
started on some real work. My use of the plural "builds" in this
connection should not he overlooked. When I say "do the builds" I don't
just mean the one build (or two builds, to be exact) mentioned in this
paragraph. What I am talking about is not a "quick fix" solution, but
rather a reliable, repeatable way of keeping my personal copy of the
latest sources up to date without having constantly to worry about
stalling out in a broken build - because if I can't build it I can't
work with it at all. This should be obvious to anyone who knows anything
about the development of complex software in a collaborative
environment.
#!/bin/bash
# Find all files belonging to a subdirectory of <top>
# with names satisfying <test> and matching <pattern>.
# Flatten all pathnames to file names by replacing '/'
# with <flat_sep>, then copy each file to its "flat" equivalent
# in <out_dir>. If <out_dir> is omitted, all matching files
# will be copied to the current directory.
#
# The concatenation: find <top> <test> <pattern> must produce a
# valid invocation of the unix 'find' command.
#
# WARNING: This is a "quick and dirty" way of consolidating like-named
# files into a single directory. In particular, if the original file
# name contains <flat_sep>, then name clashes are possible.
# <flat_sep> should be a single non-alphanumeric character and should
# not be part of any matching file name. Thus an unusual character such
# as '#' is recommended.
# author: Ben Tompkins
# email: [EMAIL PROTECTED]
if [ $# -lt 4 ]; then
echo "Usage: gather <top> <test> <pattern> <flat_sep>
[<out_dir>]"
echo 'E.g., gather ~/somedir -iregex ".*readme.*" \#'
exit 1
fi
WDIR=`pwd`
TOP="$1"
if [ ! -d "$TOP" ]; then
echo "$OUT_DIR does not exist."
exit 1
fi
shift
TEST="$1"
shift
PATTERN="$1"
shift
FLAT_SEP="$1"
if [ ${#FLAT_SEP} -ne 1 ]; then
echo "<flat_sep> must be a single character."
exit 1
elif [[ $FLAT_SEP == [0-9A-Za-z] ]]; then
echo "<flat_sep> cannot be alphanumeric."
exit 1
fi
shift
OUT_DIR="$1"
if [ "x$OUT_DIR" = "x" ]; then
OUT_DIR=`pwd`
elif [ ! -d "$OUT_DIR" ]; then
echo "$OUT_DIR does not exist."
exit 1
fi
if [[ "$OUT_DIR" != /* ]]; then
cd "$OUT_DIR"
OUT_DIR=`pwd`
cd $WDIR
fi
# cd to the specified directory.
# The 'find' command will be executed
# from here.
cd "$TOP"
for _FILE_NAME in `find . $TEST $PATTERN ` ; do
_FLAT_NAME=`echo $_FILE_NAME | sed -e 's/\(^\.\/\)\(.*\)/\2/' | tr
'/' "$FLAT_SEP" `
cp $_FILE_NAME "${OUT_DIR}/${_FLAT_NAME}"
done
cd $WDIR
##################################################
BUILD FAILED
file:/home/ben/source/jboss-head/common/../tools/etc/buildfragments/targets.ent:31:
Could not create task or type of type: depend.
##########################################################
Buildfile: /home/ben/source/jboss-3.2/build/build.xml
BUILD FAILED
Error reading project file: unknown protocol: resource
######################################################
-------------------------------------------------------
This sf.net email is sponsored by: Influence the future
of Java(TM) technology. Join the Java Community
Process(SM) (JCP(SM)) program now.
http://ads.sourceforge.net/cgi-bin/redirect.pl?sunm0004en
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
