Thanks for the quick response. I'll check out JIRA when I come up for air. The other issues that lead me to constantly rebuild have already had issues created, I believe. I've been able to get the patch code from the mailing lists in one case and dealt with it myself in the other. I'll double-check again, though.
As for the build issues, your suggestions are helpful, and I understand about the temp issue. I'm more than happy to help contribute in most cases, it's just that the build files are something I'm terrified to touch. On 12/7/05, Leonardo Quijano Vincenzi <[EMAIL PROTECTED]> wrote: > > Drew McAuliffe wrote: > > Maybe this is just a hole in the documentation? I hope so because for > each > > new release, I'm forced to rebuild both hivemind and tapestry due to 2 > > errors that have been mentioned on the list frequently in the past but > never > > actually addressed (jndi lookup problems with oc4j and the fact that you > > can't easily make table column headers align to the left without editing > the > > html in the contrib library). > > > > Drew > As with any open source library, your problems would get solved out > faster if you provide patches. You seem a little mad because Tapestry is > not living up to your expectations of how it should work ^o)? > > Go ahead, and get involved. For the problems that you mention above, are > they active JIRA issues? If not, then please submit the issue request. > Maybe a small e-mail to the devel list telling Tapestry committers to > please look-up the issues - preferably with a fix already investigated, > would be nice? (I just submitted an e-mail of that kind myself, and it > was promptly fixed in the 4.0 branch - thanks Howard!) > > As for the temporary build problems, I think Howard moved the target to > a temp directory due to the large amount of code / docs / files > generated in the project workspace. That clutters up Eclipse (seems like > it can't handle large amount of files). Of course, suggestions are > welcome. Based on your e-mail, I'd guess they are as following: > > 1. Make the temp directory versioned. Instead of "jakarta-tapestry" > let's use "jakarta-tapestry-4.0". That would solve conflicts. > 2. Build in the temp directory but provide JARs and compiled ZIPs to the > main project workspace. Maybe a dist directory could help. I second > that: I just don't like going to the temp directory to get a ZIP. > > As with the other frameworks issue, well, any OS project will ask you to > provide patches, fixes for documentation, etc. ;) > > Thanks for the suggestions, though. > > -- > Ing. Leonardo Quijano Vincenzi > DTQ Software > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
