On Thu, 2002-10-31 at 15:06, Jason Dillon wrote: > > 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. > > Where did I go? Where did I leave my absence anyways? > > > > 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 > > The script or the request? > > > > 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 > > Who said anything about alteration? > > > > 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 > > So, why the fuck do you even bothering responding? Did you have a bad > night? Not get any from the misses and now you need to vent? > > The point is to have a consistent location for bits in our thirdparty > repository and to provide licensing details for all of the external > software which JBoss makes use 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." > > Okay, now I am bending over... why don't you kiss my ass mother fucker! > The "proverbial SMD". > > All you bitches out there complain and complain about the build system, > but no one steps forward with a solution, a plan or even constructive > comments on how to resolve the phantom issues that you morons have with > using the JBoss build system. > > > > 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 > > Like the fucking email said. It was a simple task for someone looking > to "help" not someone looking to passive-aggressively flame the task or > the build system. > > If you are looking for help you sure have a fucked up way of going about > it. > > > > 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. > > The build system was not designed to be run from any IDE. It was > designed to be run from the command-line. Only recently has the build > system been able to be used by external Ant installations. > > * * * > > The bottom line, is why don't you stop wining like a little bitch and be > constructive or at least pleasant. > > --jason
Ok. I can patch the doc with the content of my last mailing "How to get it to build." But I will need a cvs account to do that. Ben > > > > ------------------------------------------------------- > 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 ------------------------------------------------------- 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
