I apologize for my tone.  If I'm misinformed or uninformed, I beg you to
take me to task.  I am a new user, going mainly by the available
documentation.  A clear error in my previous emails is that I said
"task" when I meant "target," I'm sure there are others.

If user error resulted in the errors I saw (with the exception of the
"OutOfMemory" which was known, well documented, and easily fixed), I'd
love to know how I can avoid them.

Again, I am quire thankful for the help I have received Mr. Porter.
Since my tone grates, I will try to fix that.  It does seem unlikely
that I'll figure out exactly what I'm doing wrong since I don't even
think I used sarcasm.  But I'll try.

-----Original Message-----
From: Jason van Zyl [mailto:[EMAIL PROTECTED] 
Sent: Thursday, November 06, 2003 12:52 AM
To: Maven Users List
Subject: RE: Building Maven


On Wed, 2003-11-05 at 23:52, Horn, Cameron wrote:
> As previously stated, the error was an "OutOfMemory" error that was 
> resolved as suggested in the build directions, by setting MAVEN_OPTS.

> I don't blame maven for the error (well, if it needs it often, perhaps

> it should be the default), but I do blame maven for not handling it 
> correctly.  Unless it was an optional bit, in which case I should be 
> told that an optional bit failed, but it's continuing anyways.  But 
> you led me to believe that it continued not by design, but by error.
> 
> Not handling build failures is a serious problem.  Full stop.
> 
> Not providing summaries of warnings and errors is just annoying.
> 
> CVS is a wonderful system for handling version control.  In addition 
> to that primary function, it ensures that you have the correct files, 
> keeps logs on activity, and provides access control.  I fail to see 
> what the problem with using it, even for storing JARs.  HTTP is 
> brittle (as seen previously) and almost wholly unsuited to this task.
> 
> Now, if you're talking about the dangers of storing multiple copies of

> dependencies, or other such mix-ups, that's a different issue.  One 
> which is unrelated to the use of a CVS repository.  Would you be 
> happier if I refreshed my HTTP server from CVS?
> 
> I'm still not sure what the ASCII portraits (banners?) mean.  Is it 
> bigger and therefore more important?  Makes it difficult to search a 
> log when T H I N G S  A R E  W R I T T E N  L I K E  T H I S.
> 
> You have my need exactly right with your commons-logging example.  Not

> only is dependency control beyond the scope of maven, maven actively 
> circumvents it.  In my opinion, dependency control is a requirement of

> a complete build solution.
> 
> As to building from CVS not being a requirement for most, agreed.  
> However, I see no reason why a project devoted to building software 
> should not have a good, informitive, correct, and trouble-free build.

> If the authors of the tool can't do it, who the heck can?

Here is the last automated build:

http://www.mail-archive.com/dev%40maven.apache.org/msg06230.html

It runs on a daily basis and has been fine for sometime. So in addition
to the developers being able to build it our simple minded automaton can
build it. Albeit this is from HEAD but shows there is no difficulty
building Maven. Almost always it is user error.

Additionally you would do well to heed some common open source courtesy.
This is a volunteer effort and you can certainly raise the issues you
see without the sarcasm and entirely uninformed comments. Some of the
issues you raise certainly need to be addressed and you are certainly
lucky Brett is patient enough to deal with you. But the tone used in
your messages will in general illicit no responses to your queries.

-- 
jvz.

Jason van Zyl
[EMAIL PROTECTED]
http://tambora.zenplex.org

In short, man creates for himself a new religion of a rational and
technical order to justify his work and to be justified in it.
  
  -- Jacques Ellul, The Technological Society


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to