01. I hope I have not misspoke by using a legal term -- distribute. All I can say is that if I do a checkout of the trunk, under the buildtime directory I can find the two jar files -- activation and mail -- that are needed in order to be able to perform successful ant builds when working under the /apps/weblogger branch of the tree.
02. As I have not yet tried to use the mail notification features,
I am not aware of whatever problems may exist from building with
the Sun sources.
03. I probably did misspeak in my comment about maven.
What I should have said is that whatever took place when the
discussions were taking place over maven versus ant, the
result was that simple ant builds that don't seem to work as simply
as simple ant builds. Whoever owns 'pom' files and 'xmlf'
files, probably has a nightly build process that works, but if all
one wants to do is insert a log.debug ("Well, we must have come
here.) statement into whatever he suspects is an early part of
the process of handling an HTMLRequest inside the roller black
box as a way to start turning it from black to gray, a few changes
to the build.xml and build.properties files were necessary --
including moving the two jar files into /tools.
----- Original Message -----
From: "David Jencks" <[email protected]>
To: <[email protected]> Sent: March 09, 2009 09:19 AM Subject: Re: Build Problems Beyond My Ken
1. I'm surprised to read roller is redistributing the sun activation and javamail jar files. I thought we did not have licensing to do that. Maybe I misunderstood or they are not redistributed from apache? Or maybe the license changed?2. You could use the geronimo activation spec jar and javamail implementation, at least for the build. While I would not claim the geronimo javamail implementation is bug free, at least it has different bugs than the sun implementation :-)3. Is there really a maven build? I've been subscribed to the dev list for well over a year and the last mention of maven I can see is a "it would be great to have maven" post from June 15 2008. The roller- geronimo integration kind of fell down due to lack of a maven build for roller and I would have found some time to resurrect it if I'd seen that there was a maven build available.thanks david jencks On Mar 7, 2009, at 10:31 PM, Terry Corbet wrote:Thanks for following up. When I had had no reply to that request, I unsubscribed here and subscribed to the dev mail list -- not sure where I needed to be. So, just to close this out this thread for whatever value it may provide for others: a. Instead of taking my source from svn trunk, I went to the download package that you provide. b. The substantial -- more than mere refactoring -- differences between the two sets of code, nominally only a couple of weeks apart, lead me to believe that I was in no way prepared for whatever degree of dynamic changes are on-going. c. Maybe -- even probably -- the build problem I was reporting, was due to cockpit errors on my part. d. As reported on the dev mail list, I am able to get reliable 'rebuilds' out of the downloaded package -- after fixing the problems concerning the activation and mail jar files. I note that in other email threads, you have replied that those two are problematic because 'you are not permitted to distribute them'. Actually I think the build problem became problematic when the decision was taken to base builds on maven rather than just plain old simple ant. I am sure that those of you working in maven have no problem with activation and mail and, in fact, both jar files are found in the tools lib that you package for download to us. I think a couple of minutes of testing the use of what you provide in the source tar with plain old simple ant would reveal the problem and then you could fix it for what I imagine to be a very large audience of folks who have no desire to buy off on maven, and thereby you could overcome any initial dismay that a potential user of Roller may get from not being able to use the tools that s/he uses with almost any other open source pacakge s/he may be trying to use to build an application solution. The subsequent development issues I have belong on that list, but here, I think I should add the problem of mail that gets rejected to this list with this notice:= = = = = = = ======================================================================This message was created automatically by mail delivery software. A message that you sent could not be delivered to one or more of itsrecipients. This is a permanent error. The following address(es) failed:[email protected] SMTP error from remote mail server after end of data: host mx1.eu.apache.org [192.87.106.230]: 552 spam score (5.6) exceeded threshold= = = = = = = ======================================================================Whatever sort of 'spam scoring' is being done, it certainly isn't helping me engage in helpful dialogs dealing with Roller. I am resending this via Gmail's editor rather than Outloo Express's editor -- which is the third time I have encountered that reject notice on this mail list.
