> 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.

I think I last time asked about your JVM settings, as a "problem starting
the modern compiler" is unusual. I'm thinking maybe your java executable is
a JRE (no compiler installed) instead of a JDK. Check %JAVA_HOME%.

> Again, I am quire thankful for the help I have received Mr. 
> Porter. 

[Brett looks around for his father] Who? :)

> 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.

I only just received the reply that Jason quoted - seems our mail system is
a bit screwy. Perhaps you should re-read it. To me (and this is just how I
interpret it - it may not have been your intention), it sounded as though
you knew better than everyone else here about how things should work.
There's not an open source project in the world that let's that fly. Mostly
this was because statements were misinformed, exaggerated or abrupt.

Without wanting to descend into any sort of flame war, let me identify the
particular comments that triggered that.

"Not handling build failures is a serious problem.  Full stop."

I admitted we needed to look at that, but that it wasn't a high priority. As
Jason explained, it works for us and the robots that automatically build the
stuff with a correctly configured environment. It is not a serious problem,
as it builds correctly when used appropriately, and I think
overdramatisation of it makes it sound worse. You should be aware that this
is not a standard Maven build problem - errors are always end the build
process, but a problem for wrapping Maven in something else (in this case
ant to bootstrap it). If Maven used on other projects didn't report errors,
yes it would be a serious problem.

"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."

CVS wasn't ever that great at binary files. A HTTP repository stores JARs
with the version number in the filename for version control and retains old
versions. This is important when it comes to distributing a product so
end-users can see the versions of JARs you are using easily. You can use
basic auth or whatever network access controls you want to grant permissions
on files. You can read your web server access logs. It does everything you
said just as well, and in a way more easily distributable to other sources.
Think about the converse: is it easier to configure anonymous pserver access
or HTTP for an end user?

As for HTTP brittleness, there are already alternative deployment protocols
for artifacts, and I imagine retrieving them by these protocols is not far
away.

"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."

Actively circumvents it? Hardly. No matter what you use, developers could
download the JAR in question and put it in WEB-INF/lib and use it. But you
could use whatever access control mentioned earlier to do this under maven
if you had to . Dependency control in terms of access permissions sounds so
crazy to me and not a part of a "complete build solution" that I think I've
misunderstood you. Perhaps we could discuss that more off-list. I really
don't see your use case.

"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? "

Again, the exaggerated and incorrect nature of this statement is probably
what grates.

Anyway, enough said. Hope this helps.

Cheers,
Brett

Reply via email to