[VOTE] Release Apache ManifoldCF 0.1
Hi, The Apache ManifoldCF community has voted to release our first set of artifacts and now would like an Incubator vote. Since this is our first release, extra attention to detail is appreciated. You can find the artifacts at http://people.apache.org/~kwright/ Thanks, Grant - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Apache ManifoldCF 0.1
Hi Grant, Is this a source or binary release? How are you guys making the release? Using Ant or Maven? Can you guys provide a KEYS and CHANGES.txt file as part of the release artifacts? Cheers, Chris On Jan 6, 2011, at 5:12 AM, Grant Ingersoll wrote: Hi, The Apache ManifoldCF community has voted to release our first set of artifacts and now would like an Incubator vote. Since this is our first release, extra attention to detail is appreciated. You can find the artifacts at http://people.apache.org/~kwright/ Thanks, Grant - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org ++ Chris Mattmann, Ph.D. Senior Computer Scientist NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA Office: 171-266B, Mailstop: 171-246 Email: chris.a.mattm...@nasa.gov WWW: http://sunset.usc.edu/~mattmann/ ++ Adjunct Assistant Professor, Computer Science Department University of Southern California, Los Angeles, CA 90089 USA ++ - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Apache ManifoldCF 0.1
Answering on Grant's behalf, the ManifoldCF artifact contains both source and binary, and the KEYS and CHANGES.txt files are within the artifact, as seems to be standard Apache practice. You just need to untar/unzip it. Karl On Thu, Jan 6, 2011 at 10:09 AM, Mattmann, Chris A (388J) chris.a.mattm...@jpl.nasa.gov wrote: Hi Grant, Is this a source or binary release? How are you guys making the release? Using Ant or Maven? Can you guys provide a KEYS and CHANGES.txt file as part of the release artifacts? Cheers, Chris On Jan 6, 2011, at 5:12 AM, Grant Ingersoll wrote: Hi, The Apache ManifoldCF community has voted to release our first set of artifacts and now would like an Incubator vote. Since this is our first release, extra attention to detail is appreciated. You can find the artifacts at http://people.apache.org/~kwright/ Thanks, Grant - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org ++ Chris Mattmann, Ph.D. Senior Computer Scientist NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA Office: 171-266B, Mailstop: 171-246 Email: chris.a.mattm...@nasa.gov WWW: http://sunset.usc.edu/~mattmann/ ++ Adjunct Assistant Professor, Computer Science Department University of Southern California, Los Angeles, CA 90089 USA ++ - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Apache ManifoldCF 0.1
Hi Karl, On Jan 6, 2011, at 7:14 AM, Karl Wright wrote: Answering on Grant's behalf, the ManifoldCF artifact contains both source and binary, and the KEYS and CHANGES.txt files are within the artifact, as seems to be standard Apache practice. Well I won't say it's standard Apache practice in my experience. I've made probably over a dozen releases in about 3+ different Apache projects so far (Nutch, Tika, SIS) and I've always put out a plain-text version of CHANGES.txt and KEYS alongside the release artifacts. The advantage of doing so is that I don't have to download a 140 MB file before I can check what changes are part of the release. Also one of the things that Clutch checks in the Incubator is that there is a KEYS file in the distribution area, separate of the release artifacts. So, I would say it should be there. You just need to untar/unzip it. Thanks for the pointer. I'd like to see the source and binary tarballs separated. Strictly speaking, you really only need a source release, but it's up to you guys I think if you want to provide a binary one too. The advantage is that the source release is likely much smaller I'm guessing than the binary. Cheers, Chris On Thu, Jan 6, 2011 at 10:09 AM, Mattmann, Chris A (388J) chris.a.mattm...@jpl.nasa.gov wrote: Hi Grant, Is this a source or binary release? How are you guys making the release? Using Ant or Maven? Can you guys provide a KEYS and CHANGES.txt file as part of the release artifacts? Cheers, Chris On Jan 6, 2011, at 5:12 AM, Grant Ingersoll wrote: Hi, The Apache ManifoldCF community has voted to release our first set of artifacts and now would like an Incubator vote. Since this is our first release, extra attention to detail is appreciated. You can find the artifacts at http://people.apache.org/~kwright/ Thanks, Grant - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org ++ Chris Mattmann, Ph.D. Senior Computer Scientist NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA Office: 171-266B, Mailstop: 171-246 Email: chris.a.mattm...@nasa.gov WWW: http://sunset.usc.edu/~mattmann/ ++ Adjunct Assistant Professor, Computer Science Department University of Southern California, Los Angeles, CA 90089 USA ++ - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org ++ Chris Mattmann, Ph.D. Senior Computer Scientist NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA Office: 171-266B, Mailstop: 171-246 Email: chris.a.mattm...@nasa.gov WWW: http://sunset.usc.edu/~mattmann/ ++ Adjunct Assistant Professor, Computer Science Department University of Southern California, Los Angeles, CA 90089 USA ++ - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Apache ManifoldCF 0.1
I am happy to provide clear-text versions of KEYS and CHANGES.txt if that is what you require. I've just never seen any other Apache project that did that. As for whether there should be separate source and binary distributions, bear in mind that a binary-only distribution of ManifoldCF makes little sense. ManifoldCF is unusual in that it distributes a number of connectors which require third-party libraries in order to compile. We do not distribute those libraries for licensing reasons. Conditional compilation is used to build those connectors for which you supply the right bits. The binary part thus includes only the framework, and those connectors which depend only on open-source code. This is relatively limited but makes it faster and easier for someone to start things up right out of the box. So, effectively, you are asking us to not have a binary distribution in order to save on space. Is this a firm request, or is this just unhappiness at the download time? FWIW, I personally don't think such a build will save a great deal tar/zip space, but I can certainly check and get back to you. Karl On Thu, Jan 6, 2011 at 10:28 AM, Mattmann, Chris A (388J) chris.a.mattm...@jpl.nasa.gov wrote: Hi Karl, On Jan 6, 2011, at 7:14 AM, Karl Wright wrote: Answering on Grant's behalf, the ManifoldCF artifact contains both source and binary, and the KEYS and CHANGES.txt files are within the artifact, as seems to be standard Apache practice. Well I won't say it's standard Apache practice in my experience. I've made probably over a dozen releases in about 3+ different Apache projects so far (Nutch, Tika, SIS) and I've always put out a plain-text version of CHANGES.txt and KEYS alongside the release artifacts. The advantage of doing so is that I don't have to download a 140 MB file before I can check what changes are part of the release. Also one of the things that Clutch checks in the Incubator is that there is a KEYS file in the distribution area, separate of the release artifacts. So, I would say it should be there. You just need to untar/unzip it. Thanks for the pointer. I'd like to see the source and binary tarballs separated. Strictly speaking, you really only need a source release, but it's up to you guys I think if you want to provide a binary one too. The advantage is that the source release is likely much smaller I'm guessing than the binary. Cheers, Chris On Thu, Jan 6, 2011 at 10:09 AM, Mattmann, Chris A (388J) chris.a.mattm...@jpl.nasa.gov wrote: Hi Grant, Is this a source or binary release? How are you guys making the release? Using Ant or Maven? Can you guys provide a KEYS and CHANGES.txt file as part of the release artifacts? Cheers, Chris On Jan 6, 2011, at 5:12 AM, Grant Ingersoll wrote: Hi, The Apache ManifoldCF community has voted to release our first set of artifacts and now would like an Incubator vote. Since this is our first release, extra attention to detail is appreciated. You can find the artifacts at http://people.apache.org/~kwright/ Thanks, Grant - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org ++ Chris Mattmann, Ph.D. Senior Computer Scientist NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA Office: 171-266B, Mailstop: 171-246 Email: chris.a.mattm...@nasa.gov WWW: http://sunset.usc.edu/~mattmann/ ++ Adjunct Assistant Professor, Computer Science Department University of Southern California, Los Angeles, CA 90089 USA ++ - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org ++ Chris Mattmann, Ph.D. Senior Computer Scientist NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA Office: 171-266B, Mailstop: 171-246 Email: chris.a.mattm...@nasa.gov WWW: http://sunset.usc.edu/~mattmann/ ++ Adjunct Assistant Professor, Computer Science Department University of Southern California, Los Angeles, CA 90089 USA ++ - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail:
Re: [VOTE] Release Apache ManifoldCF 0.1
The download size of sources alone is about 32M for each .zip/.tar.gz. I can't upload CHANGES.txt or KEYS to people.apache.org right now because of a firewall restriction, so I've attached the files for your convenience. Karl On Thu, Jan 6, 2011 at 11:10 AM, Karl Wright daddy...@gmail.com wrote: I am happy to provide clear-text versions of KEYS and CHANGES.txt if that is what you require. I've just never seen any other Apache project that did that. As for whether there should be separate source and binary distributions, bear in mind that a binary-only distribution of ManifoldCF makes little sense. ManifoldCF is unusual in that it distributes a number of connectors which require third-party libraries in order to compile. We do not distribute those libraries for licensing reasons. Conditional compilation is used to build those connectors for which you supply the right bits. The binary part thus includes only the framework, and those connectors which depend only on open-source code. This is relatively limited but makes it faster and easier for someone to start things up right out of the box. So, effectively, you are asking us to not have a binary distribution in order to save on space. Is this a firm request, or is this just unhappiness at the download time? FWIW, I personally don't think such a build will save a great deal tar/zip space, but I can certainly check and get back to you. Karl On Thu, Jan 6, 2011 at 10:28 AM, Mattmann, Chris A (388J) chris.a.mattm...@jpl.nasa.gov wrote: Hi Karl, On Jan 6, 2011, at 7:14 AM, Karl Wright wrote: Answering on Grant's behalf, the ManifoldCF artifact contains both source and binary, and the KEYS and CHANGES.txt files are within the artifact, as seems to be standard Apache practice. Well I won't say it's standard Apache practice in my experience. I've made probably over a dozen releases in about 3+ different Apache projects so far (Nutch, Tika, SIS) and I've always put out a plain-text version of CHANGES.txt and KEYS alongside the release artifacts. The advantage of doing so is that I don't have to download a 140 MB file before I can check what changes are part of the release. Also one of the things that Clutch checks in the Incubator is that there is a KEYS file in the distribution area, separate of the release artifacts. So, I would say it should be there. You just need to untar/unzip it. Thanks for the pointer. I'd like to see the source and binary tarballs separated. Strictly speaking, you really only need a source release, but it's up to you guys I think if you want to provide a binary one too. The advantage is that the source release is likely much smaller I'm guessing than the binary. Cheers, Chris On Thu, Jan 6, 2011 at 10:09 AM, Mattmann, Chris A (388J) chris.a.mattm...@jpl.nasa.gov wrote: Hi Grant, Is this a source or binary release? How are you guys making the release? Using Ant or Maven? Can you guys provide a KEYS and CHANGES.txt file as part of the release artifacts? Cheers, Chris On Jan 6, 2011, at 5:12 AM, Grant Ingersoll wrote: Hi, The Apache ManifoldCF community has voted to release our first set of artifacts and now would like an Incubator vote. Since this is our first release, extra attention to detail is appreciated. You can find the artifacts at http://people.apache.org/~kwright/ Thanks, Grant - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org ++ Chris Mattmann, Ph.D. Senior Computer Scientist NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA Office: 171-266B, Mailstop: 171-246 Email: chris.a.mattm...@nasa.gov WWW: http://sunset.usc.edu/~mattmann/ ++ Adjunct Assistant Professor, Computer Science Department University of Southern California, Los Angeles, CA 90089 USA ++ - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org ++ Chris Mattmann, Ph.D. Senior Computer Scientist NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA Office: 171-266B, Mailstop: 171-246 Email: chris.a.mattm...@nasa.gov WWW: http://sunset.usc.edu/~mattmann/ ++ Adjunct Assistant Professor, Computer Science
Re: [VOTE] Release Apache ManifoldCF 0.1
On 6 January 2011 16:10, Karl Wright daddy...@gmail.com wrote: I am happy to provide clear-text versions of KEYS and CHANGES.txt if that is what you require. I've just never seen any other Apache project that did that. All Apache releases require pgp signatures, and the KEYS file must contain the key necessary to validate the signature. The KEYS file should be referenced from the download page, alongside the sig and hash files. For example: http://httpd.apache.org/download.cgi The key should also be added to a pgp key server. As for whether there should be separate source and binary distributions, bear in mind that a binary-only distribution of ManifoldCF makes little sense. ManifoldCF is unusual in that it distributes a number of connectors which require third-party libraries in order to compile. We do not distribute those libraries for licensing reasons. Conditional compilation is used to build those connectors for which you supply the right bits. The binary part thus includes only the framework, and those connectors which depend only on open-source code. This is relatively limited but makes it faster and easier for someone to start things up right out of the box. So, effectively, you are asking us to not have a binary distribution in order to save on space. Is this a firm request, or is this just unhappiness at the download time? FWIW, I personally don't think such a build will save a great deal tar/zip space, but I can certainly check and get back to you. AIUI there must be a source distribution; the binary distribution is optional. The consumer should not be forced to download the binary distribution in order to get the source. Karl On Thu, Jan 6, 2011 at 10:28 AM, Mattmann, Chris A (388J) chris.a.mattm...@jpl.nasa.gov wrote: Hi Karl, On Jan 6, 2011, at 7:14 AM, Karl Wright wrote: Answering on Grant's behalf, the ManifoldCF artifact contains both source and binary, and the KEYS and CHANGES.txt files are within the artifact, as seems to be standard Apache practice. Well I won't say it's standard Apache practice in my experience. I've made probably over a dozen releases in about 3+ different Apache projects so far (Nutch, Tika, SIS) and I've always put out a plain-text version of CHANGES.txt and KEYS alongside the release artifacts. The advantage of doing so is that I don't have to download a 140 MB file before I can check what changes are part of the release. Also one of the things that Clutch checks in the Incubator is that there is a KEYS file in the distribution area, separate of the release artifacts. So, I would say it should be there. You just need to untar/unzip it. Thanks for the pointer. I'd like to see the source and binary tarballs separated. Strictly speaking, you really only need a source release, but it's up to you guys I think if you want to provide a binary one too. The advantage is that the source release is likely much smaller I'm guessing than the binary. Cheers, Chris On Thu, Jan 6, 2011 at 10:09 AM, Mattmann, Chris A (388J) chris.a.mattm...@jpl.nasa.gov wrote: Hi Grant, Is this a source or binary release? How are you guys making the release? Using Ant or Maven? Can you guys provide a KEYS and CHANGES.txt file as part of the release artifacts? Cheers, Chris On Jan 6, 2011, at 5:12 AM, Grant Ingersoll wrote: Hi, The Apache ManifoldCF community has voted to release our first set of artifacts and now would like an Incubator vote. Since this is our first release, extra attention to detail is appreciated. You can find the artifacts at http://people.apache.org/~kwright/ Thanks, Grant - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org ++ Chris Mattmann, Ph.D. Senior Computer Scientist NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA Office: 171-266B, Mailstop: 171-246 Email: chris.a.mattm...@nasa.gov WWW: http://sunset.usc.edu/~mattmann/ ++ Adjunct Assistant Professor, Computer Science Department University of Southern California, Los Angeles, CA 90089 USA ++ - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org ++ Chris Mattmann, Ph.D. Senior Computer Scientist NASA Jet Propulsion
Re: [VOTE] Release Apache ManifoldCF 0.1
The key should also be added to a pgp key server. The key has already been added to the MIT web of trust - I presume that is what you meant? AIUI there must be a source distribution; the binary distribution is optional. The consumer should not be forced to download the binary distribution in order to get the source. Very well; we will discontinue all binary distributions. One major problem will therefore be that we rely on Apache Forrest to build the documentation pages. Forrest requires Java 1.5. The availability of documentation in the release will therefore depend on the availability of Java 1.5 to the person building it. Is this acceptable? Karl - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Apache ManifoldCF 0.1
On 6 January 2011 13:12, Grant Ingersoll gsing...@apache.org wrote: Hi, The Apache ManifoldCF community has voted to release our first set of artifacts and now would like an Incubator vote. Since this is our first release, extra attention to detail is appreciated. You can find the artifacts at http://people.apache.org/~kwright/ The md5 hash file has an odd syntax, which makes it harder to use with automated checking tools. apache-manifoldcf-0.1-incubator.zip: A3 3E 0A 9F 58 94 DC 64 F7 B3 ED DB 63 2E CB EF The standard format is a33e0a9f5894dc64f7b3eddb632ecbef *apache-manifoldcf-0.1-incubator.zip (upper case hex also valid) Thanks, Grant - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Apache ManifoldCF 0.1
On 6 January 2011 17:34, Karl Wright daddy...@gmail.com wrote: The key should also be added to a pgp key server. The key has already been added to the MIT web of trust - I presume that is what you meant? Yes, I meant that the key should be retrievable from a pgp key server - which it is (just checked). [BTW, the web of trust is something different; neither key in the KEYS file is part of any web of trust] AIUI there must be a source distribution; the binary distribution is optional. The consumer should not be forced to download the binary distribution in order to get the source. Very well; we will discontinue all binary distributions. That's not what I said. You can have a binary distribution if you wish, but there must be a source distribution. One major problem will therefore be that we rely on Apache Forrest to build the documentation pages. Forrest requires Java 1.5. The availability of documentation in the release will therefore depend on the availability of Java 1.5 to the person building it. Is this acceptable? Karl - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Apache ManifoldCF 0.1
On 6 January 2011 18:03, sebb seb...@gmail.com wrote: On 6 January 2011 13:12, Grant Ingersoll gsing...@apache.org wrote: Hi, The Apache ManifoldCF community has voted to release our first set of artifacts and now would like an Incubator vote. Since this is our first release, extra attention to detail is appreciated. You can find the artifacts at http://people.apache.org/~kwright/ The md5 hash file has an odd syntax, which makes it harder to use with automated checking tools. apache-manifoldcf-0.1-incubator.zip: A3 3E 0A 9F 58 94 DC 64 F7 B3 ED DB 63 2E CB EF The standard format is a33e0a9f5894dc64f7b3eddb632ecbef *apache-manifoldcf-0.1-incubator.zip (upper case hex also valid) Also, the NOTICE and LICENSE files don't seem to be quite right. The NOTICE file is for required notices only; so for example there is no need to mention other ASF projects. The LICENSE file references JUnit, which does not need to be distributed, so is not needed in the LICENSE. Thanks, Grant - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Apache ManifoldCF 0.1
Very well; we will discontinue all binary distributions. That's not what I said. You can have a binary distribution if you wish, but there must be a source distribution. As I said before, it makes no sense to distribute ManifoldCF binaries without complete sources. So we could (I suppose) have a source distribution AND a source+binary distribution. But we could not simply have a binary distribution and a source distribution. Karl - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Apache ManifoldCF 0.1
Also, the NOTICE and LICENSE files don't seem to be quite right. The NOTICE file is for required notices only; so for example there is no need to mention other ASF projects. The LICENSE file references JUnit, which does not need to be distributed, so is not needed in the LICENSE. These are based on what was done for Solr and Lucene. Solr and Lucene distribute JUnit, so that you may run the Solr and Lucene tests. ManifoldCF does the same. If you want us to remove JUnit from the distribution, then you cannot test the connectors you build, which is definitely a problem. I don't think you'd really have a valid release if you did that. Similarly, the Solr and Lucene NOTICE files include references to all included Apache jars as well, and Grant was pretty insistent that I include those. I'm not sure why. Karl - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Apache ManifoldCF 0.1
The md5 hash file has an odd syntax, which makes it harder to use with automated checking tools. apache-manifoldcf-0.1-incubator.zip: A3 3E 0A 9F 58 94 DC 64 F7 B3 ED DB 63 2E CB EF The standard format is a33e0a9f5894dc64f7b3eddb632ecbef *apache-manifoldcf-0.1-incubator.zip (upper case hex also valid) The signature was generated with OpenPGP. I must not be using the right switches or something; I'll do some research and change my script accordingly. Karl - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Apache ManifoldCF 0.1
On 6 January 2011 18:23, Karl Wright daddy...@gmail.com wrote: Very well; we will discontinue all binary distributions. That's not what I said. You can have a binary distribution if you wish, but there must be a source distribution. As I said before, it makes no sense to distribute ManifoldCF binaries without complete sources. So we could (I suppose) have a source distribution AND a source+binary distribution. That would be fine. But we could not simply have a binary distribution and a source distribution. That would also work, but would require binary users to download both archives. == On a separate matter, I question whether the current packaging is optimal. There appear to be 3 copies of every jar in the binary zip file - no wonder the file is so large! Also, many of the included jars are commonly used elsewhere, so the consumer may well already have a copy. Generally, the binary jar consists of the compiled source files only. Some projects provide additional bundles which include all the required dependencies; that might be the way to go here. Karl - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Apache ManifoldCF 0.1
The whole question of ease-of-use is what drove this packaging arrangement. I was told it was unacceptable to not have a working example out of the box that could be executed in a single line. Build and execution Instructions which involve obtaining a couple of dozen jars from other places do not fulfill this criterion. The three copies of the dependent jars occur because of the following: - There is one copy of the jar that is used by the build - There are two distinct execution environments, one single-process, and one multi-process, that are built - Each execution environment has its own subtree that it executes from If the built environments are no longer distributed, then there will be one copy of each dependent jar included. I'm leaning towards just having this minimum distribution since size is apparently a huge issue here. I still want to know if the source distribution should have the forrest-built docs or not, though, or whether it should be up to the user to build their own docs using Forrest themselves. I would prefer the former because Forrest is somewhat idiosyncratic, but you guys are the bosses. Karl On Thu, Jan 6, 2011 at 1:39 PM, sebb seb...@gmail.com wrote: On 6 January 2011 18:23, Karl Wright daddy...@gmail.com wrote: Very well; we will discontinue all binary distributions. That's not what I said. You can have a binary distribution if you wish, but there must be a source distribution. As I said before, it makes no sense to distribute ManifoldCF binaries without complete sources. So we could (I suppose) have a source distribution AND a source+binary distribution. That would be fine. But we could not simply have a binary distribution and a source distribution. That would also work, but would require binary users to download both archives. == On a separate matter, I question whether the current packaging is optimal. There appear to be 3 copies of every jar in the binary zip file - no wonder the file is so large! Also, many of the included jars are commonly used elsewhere, so the consumer may well already have a copy. Generally, the binary jar consists of the compiled source files only. Some projects provide additional bundles which include all the required dependencies; that might be the way to go here. Karl - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Apache ManifoldCF 0.1
Hi Karl, On Jan 6, 2011, at 10:49 AM, Karl Wright wrote: The whole question of ease-of-use is what drove this packaging arrangement. I was told it was unacceptable to not have a working example out of the box that could be executed in a single line. Build and execution Instructions which involve obtaining a couple of dozen jars from other places do not fulfill this criterion. It's unacceptable to not release software according to Apache guidelines. There's some flexibility in those guidelines (whether to include a binary release or not, whether to include jar files in a distro or use Maven, etc.), and then there's not (must include a source release; must have a KEYS file; etc.etc.) Including a working out of the box example might be something that ManifoldCF as a community deems absolutely required for a ManifoldCF release, but it's not absolutely required for an Apache release. Of course, not doing it has its own implications (users won't care about the software; will find it too difficult), but that's another subject. The three copies of the dependent jars occur because of the following: - There is one copy of the jar that is used by the build - There are two distinct execution environments, one single-process, and one multi-process, that are built - Each execution environment has its own subtree that it executes from Are all of these Jars simply copies of an original Jar, or are they separately licensed? If the built environments are no longer distributed, then there will be one copy of each dependent jar included. I'm leaning towards just having this minimum distribution since size is apparently a huge issue here. It's a huge issue everywhere. Your release will be mirrored around the world using Apache's mirroring system. Beyond that it will be likely replicated N times at M companies who are using it. Size *is* a big issue, not just *here*. I still want to know if the source distribution should have the forrest-built docs or not, though, or whether it should be up to the user to build their own docs using Forrest themselves. I would prefer the former because Forrest is somewhat idiosyncratic, but you guys are the bosses. Eh, either way is fine with me, and I don't think anyone here should legislate on this. It should be a ManifoldCF community decision IMHO. Cheers, Chris Karl On Thu, Jan 6, 2011 at 1:39 PM, sebb seb...@gmail.com wrote: On 6 January 2011 18:23, Karl Wright daddy...@gmail.com wrote: Very well; we will discontinue all binary distributions. That's not what I said. You can have a binary distribution if you wish, but there must be a source distribution. As I said before, it makes no sense to distribute ManifoldCF binaries without complete sources. So we could (I suppose) have a source distribution AND a source+binary distribution. That would be fine. But we could not simply have a binary distribution and a source distribution. That would also work, but would require binary users to download both archives. == On a separate matter, I question whether the current packaging is optimal. There appear to be 3 copies of every jar in the binary zip file - no wonder the file is so large! Also, many of the included jars are commonly used elsewhere, so the consumer may well already have a copy. Generally, the binary jar consists of the compiled source files only. Some projects provide additional bundles which include all the required dependencies; that might be the way to go here. Karl - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org ++ Chris Mattmann, Ph.D. Senior Computer Scientist NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA Office: 171-266B, Mailstop: 171-246 Email: chris.a.mattm...@nasa.gov WWW: http://sunset.usc.edu/~mattmann/ ++ Adjunct Assistant Professor, Computer Science Department University of Southern California, Los Angeles, CA 90089 USA ++ - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Apache ManifoldCF 0.1
It's unacceptable to not release software according to Apache guidelines. There's some flexibility in those guidelines (whether to include a binary release or not, whether to include jar files in a distro or use Maven, etc.), and then there's not (must include a source release; must have a KEYS file; etc.etc.) I'm not arguing; I've accepted the conclusion that there will be no binary distribution. The three copies of the dependent jars occur because of the following: - There is one copy of the jar that is used by the build - There are two distinct execution environments, one single-process, and one multi-process, that are built - Each execution environment has its own subtree that it executes from Are all of these Jars simply copies of an original Jar, or are they separately licensed? It's all the same license. The dependent jars are copied into the appropriate target locations by the build process. So without the build, you have one copy of each dependent jar. If the built environments are no longer distributed, then there will be one copy of each dependent jar included. I'm leaning towards just having this minimum distribution since size is apparently a huge issue here. It's a huge issue everywhere. Your release will be mirrored around the world using Apache's mirroring system. Beyond that it will be likely replicated N times at M companies who are using it. Size *is* a big issue, not just *here*. This was not obvious to me in the era of 1Tb disks costing $50. Builds of this size have not been considered problematic in any place I've worked for at least a decade. But I will accept your restrictions. Eh, either way is fine with me, and I don't think anyone here should legislate on this. It should be a ManifoldCF community decision IMHO. If you are flexible, I will recommend we include the built docs. It will increase the size of the distribution somewhat (from 32M to 45M per tar.gz/zip), but it gives the user much more environmental flexibility. Karl - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Apache ManifoldCF 0.1
On Thu, Jan 6, 2011 at 1:12 PM, Grant Ingersoll gsing...@apache.org wrote: Hi, The Apache ManifoldCF community has voted to release our first set of artifacts and now would like an Incubator vote. Since this is our first release, extra attention to detail is appreciated. You can find the artifacts at http://people.apache.org/~kwright/ Thanks, Grant I've reviewed this and think it mostly fine. The NOTICE file does include some unnecessary things, i don't think thats technically a blocking issue but as this is the first RC of the first release it should probably be cleaned up and another RC done. The NOTICE file should only include required notices that other text if its really needed could go in a README file, see http://www.apache.org/legal/src-headers.html#notice I think this current source+binary distribution is fine. The rule is that you can only release binary artifacts which also have the source released, but there are no rules saying the source distribution must not include any binary artifacts, so if this is what the project thinks works best then its fine. It is missing the Incubating disclaimer text which should be included in the README or a DISCLAIMER file, see http://incubator.apache.org/guides/branding.html#disclaimers I tried building it with ant build and that failed, don't know if that my environment or something else: BUILD FAILED C:\ASF\manifoldcf\apache-manifoldcf-0.1-incubator\build.xml:353: The following error occurred while executing this line: C:\ASF\manifoldcf\apache-manifoldcf-0.1-incubator\connectors\jdbc\build.xml:52: C:\ASF\manifoldcf\apache-manifoldcf-0.1-incubator\co nnectors\jdbc\jdbc-drivers does not exist. Other than that it looks ok to me. Its big and inlcudes some duplicate stuff but if thats what the project thinks is the best approach then its fine, there are plenty of other big projects being distributed. ..ant - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Apache ManifoldCF 0.1
Hi Karl, It's all the same license. The dependent jars are copied into the appropriate target locations by the build process. So without the build, you have one copy of each dependent jar. Cool, thanks. It's a huge issue everywhere. Your release will be mirrored around the world using Apache's mirroring system. Beyond that it will be likely replicated N times at M companies who are using it. Size *is* a big issue, not just *here*. This was not obvious to me in the era of 1Tb disks costing $50. Builds of this size have not been considered problematic in any place I've worked for at least a decade. But I will accept your restrictions. Apache is a non-profit organization. Not saying they don't have the money to buy $50 disks as you say for mirroring, or that the companies that releases get mirrored to don't have it but if we can cut their expenses down that's always nice. Apache has over 80+ top level projects that are all making releases and so forth, and a ton of Incubator projects too, and a ton of Labs projects, so it's important to be good citizens. I wouldn't say these are my restrictions either -- I've seen a number of other people over the years on these lists make the same comment, so I'm just passing it along. If you are flexible, I will recommend we include the built docs. It will increase the size of the distribution somewhat (from 32M to 45M per tar.gz/zip), but it gives the user much more environmental flexibility. Fine by me, but I can't speak for the others :) Thanks for taking the time to address my comments/questions. Cheers, Chris ++ Chris Mattmann, Ph.D. Senior Computer Scientist NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA Office: 171-266B, Mailstop: 171-246 Email: chris.a.mattm...@nasa.gov WWW: http://sunset.usc.edu/~mattmann/ ++ Adjunct Assistant Professor, Computer Science Department University of Southern California, Los Angeles, CA 90089 USA ++ - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Apache ManifoldCF 0.1
Where is the SVN tag for the release? On 6 January 2011 13:12, Grant Ingersoll gsing...@apache.org wrote: Hi, The Apache ManifoldCF community has voted to release our first set of artifacts and now would like an Incubator vote. Since this is our first release, extra attention to detail is appreciated. You can find the artifacts at http://people.apache.org/~kwright/ Thanks, Grant - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Apache ManifoldCF 0.1
Since this is a release candidate, and the release has not yet been signed off, the tag has not yet been created. There is, however, a release branch, from which the release candidates get built. When the sign off occurs, the tag will be created from that branch. Karl On Thu, Jan 6, 2011 at 3:03 PM, sebb seb...@gmail.com wrote: Where is the SVN tag for the release? On 6 January 2011 13:12, Grant Ingersoll gsing...@apache.org wrote: Hi, The Apache ManifoldCF community has voted to release our first set of artifacts and now would like an Incubator vote. Since this is our first release, extra attention to detail is appreciated. You can find the artifacts at http://people.apache.org/~kwright/ Thanks, Grant - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Confusing naming of Manifold Connector Framework resources
It's quite difficult finding the resources for the Manifold Connector Framework. The Incubator web-site is at: http://incubator.apache.org/connectors/ SVN appears to be at: http://svn.apache.org/repos/asf/incubator/lcf/ The Java package is org.apache.manifoldcf So the project currently uses the following 3 ids: connectors lcf manifoldcf in different namespaces. This is going to be very confusing when the project graduates; normally the Java package, SVN tree, website and PMC share the same id. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Apache ManifoldCF 0.1
On 6 January 2011 20:06, Karl Wright daddy...@gmail.com wrote: Since this is a release candidate, and the release has not yet been signed off, the tag has not yet been created. There is, however, a release branch, from which the release candidates get built. When the sign off occurs, the tag will be created from that branch. I see. I assume you are referring to: http://svn.apache.org/repos/asf/incubator/lcf/branches/release-0.1-branch/ == Another way to do this is to create a tag (with an RCn suffix) and built the RC from that. If the RC succeeds, rename the tag to remove the RCn suffix. If the RC fails, fix the code, create RCn+1 and repeat. The RCn tag can be deleted later when the release has been made or abandoned. That way, there is a fixed tag that is used to create the RC which reviewers can also use. The RCn tags are also useful for reviewers to be able to quickly check exactly what has changed between RCs. Karl On Thu, Jan 6, 2011 at 3:03 PM, sebb seb...@gmail.com wrote: Where is the SVN tag for the release? On 6 January 2011 13:12, Grant Ingersoll gsing...@apache.org wrote: Hi, The Apache ManifoldCF community has voted to release our first set of artifacts and now would like an Incubator vote. Since this is our first release, extra attention to detail is appreciated. You can find the artifacts at http://people.apache.org/~kwright/ Thanks, Grant - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Confusing naming of Manifold Connector Framework resources
The official name of the project has changed repeatedly. The current official name is ManifoldCF. The community expects to change both the SVN root and the web-site root upon incubation in any case, which is why we have not changed either of these yet. A bigger area of concern is the prefix used for ManifoldCF tickets in Jira, which is CONNECTORS-xxx. This is apparently very difficult to change without losing a project's old tickets. I am hoping that change will not be needed. Karl On Thu, Jan 6, 2011 at 3:17 PM, sebb seb...@gmail.com wrote: It's quite difficult finding the resources for the Manifold Connector Framework. The Incubator web-site is at: http://incubator.apache.org/connectors/ SVN appears to be at: http://svn.apache.org/repos/asf/incubator/lcf/ The Java package is org.apache.manifoldcf So the project currently uses the following 3 ids: connectors lcf manifoldcf in different namespaces. This is going to be very confusing when the project graduates; normally the Java package, SVN tree, website and PMC share the same id. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Apache ManifoldCF 0.1
Yes, that is the correct branch. If there is an official Apache tagging strategy, I'm fine with that. Heretofore I've been using the MetaCarta release tagging strategy, which was partly gated on a restriction in the MetaCarta svn setup that prevented tags from being renamed or deleted. Your proposal sounds perfectly reasonable, though - I can begin to do it that way on the next RC (which will actually be RC4). Karl On Thu, Jan 6, 2011 at 3:25 PM, sebb seb...@gmail.com wrote: On 6 January 2011 20:06, Karl Wright daddy...@gmail.com wrote: Since this is a release candidate, and the release has not yet been signed off, the tag has not yet been created. There is, however, a release branch, from which the release candidates get built. When the sign off occurs, the tag will be created from that branch. I see. I assume you are referring to: http://svn.apache.org/repos/asf/incubator/lcf/branches/release-0.1-branch/ == Another way to do this is to create a tag (with an RCn suffix) and built the RC from that. If the RC succeeds, rename the tag to remove the RCn suffix. If the RC fails, fix the code, create RCn+1 and repeat. The RCn tag can be deleted later when the release has been made or abandoned. That way, there is a fixed tag that is used to create the RC which reviewers can also use. The RCn tags are also useful for reviewers to be able to quickly check exactly what has changed between RCs. Karl On Thu, Jan 6, 2011 at 3:03 PM, sebb seb...@gmail.com wrote: Where is the SVN tag for the release? On 6 January 2011 13:12, Grant Ingersoll gsing...@apache.org wrote: Hi, The Apache ManifoldCF community has voted to release our first set of artifacts and now would like an Incubator vote. Since this is our first release, extra attention to detail is appreciated. You can find the artifacts at http://people.apache.org/~kwright/ Thanks, Grant - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Apache ManifoldCF 0.1
The failure to build occurs because the directory it is complaining about doesn't seem to exist after the zip is unpacked. The directory is empty at the time of the build. It's not clear whether the problem is the built zip itself or the way you are unpacking it. I'll need to look into this more tonight. Karl On Thu, Jan 6, 2011 at 2:26 PM, ant elder ant.el...@gmail.com wrote: On Thu, Jan 6, 2011 at 1:12 PM, Grant Ingersoll gsing...@apache.org wrote: Hi, The Apache ManifoldCF community has voted to release our first set of artifacts and now would like an Incubator vote. Since this is our first release, extra attention to detail is appreciated. You can find the artifacts at http://people.apache.org/~kwright/ Thanks, Grant I've reviewed this and think it mostly fine. The NOTICE file does include some unnecessary things, i don't think thats technically a blocking issue but as this is the first RC of the first release it should probably be cleaned up and another RC done. The NOTICE file should only include required notices that other text if its really needed could go in a README file, see http://www.apache.org/legal/src-headers.html#notice I think this current source+binary distribution is fine. The rule is that you can only release binary artifacts which also have the source released, but there are no rules saying the source distribution must not include any binary artifacts, so if this is what the project thinks works best then its fine. It is missing the Incubating disclaimer text which should be included in the README or a DISCLAIMER file, see http://incubator.apache.org/guides/branding.html#disclaimers I tried building it with ant build and that failed, don't know if that my environment or something else: BUILD FAILED C:\ASF\manifoldcf\apache-manifoldcf-0.1-incubator\build.xml:353: The following error occurred while executing this line: C:\ASF\manifoldcf\apache-manifoldcf-0.1-incubator\connectors\jdbc\build.xml:52: C:\ASF\manifoldcf\apache-manifoldcf-0.1-incubator\co nnectors\jdbc\jdbc-drivers does not exist. Other than that it looks ok to me. Its big and inlcudes some duplicate stuff but if thats what the project thinks is the best approach then its fine, there are plenty of other big projects being distributed. ..ant - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Confusing naming of Manifold Connector Framework resources
On 6 January 2011 20:29, Karl Wright daddy...@gmail.com wrote: The official name of the project has changed repeatedly. The current official name is ManifoldCF. The community expects to change both the SVN root and the web-site root upon incubation in any case, which is why we have not changed either of these yet. OK, I see. A bigger area of concern is the prefix used for ManifoldCF tickets in Jira, which is CONNECTORS-xxx. This is apparently very difficult to change without losing a project's old tickets. I am hoping that change will not be needed. The Java package name hopefully won't need to be changed either ... Karl On Thu, Jan 6, 2011 at 3:17 PM, sebb seb...@gmail.com wrote: It's quite difficult finding the resources for the Manifold Connector Framework. The Incubator web-site is at: http://incubator.apache.org/connectors/ SVN appears to be at: http://svn.apache.org/repos/asf/incubator/lcf/ The Java package is org.apache.manifoldcf So the project currently uses the following 3 ids: connectors lcf manifoldcf in different namespaces. This is going to be very confusing when the project graduates; normally the Java package, SVN tree, website and PMC share the same id. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Apache ManifoldCF 0.1
On 6 January 2011 20:41, Karl Wright daddy...@gmail.com wrote: The failure to build occurs because the directory it is complaining about doesn't seem to exist after the zip is unpacked. The directory is empty at the time of the build. It's not clear whether the problem is the built zip itself or the way you are unpacking it. I'll need to look into this more tonight. Not all archive types store empty directories. Either have the build script create the directory or add a marker file to the directory. Karl On Thu, Jan 6, 2011 at 2:26 PM, ant elder ant.el...@gmail.com wrote: On Thu, Jan 6, 2011 at 1:12 PM, Grant Ingersoll gsing...@apache.org wrote: Hi, The Apache ManifoldCF community has voted to release our first set of artifacts and now would like an Incubator vote. Since this is our first release, extra attention to detail is appreciated. You can find the artifacts at http://people.apache.org/~kwright/ Thanks, Grant I've reviewed this and think it mostly fine. The NOTICE file does include some unnecessary things, i don't think thats technically a blocking issue but as this is the first RC of the first release it should probably be cleaned up and another RC done. The NOTICE file should only include required notices that other text if its really needed could go in a README file, see http://www.apache.org/legal/src-headers.html#notice I think this current source+binary distribution is fine. The rule is that you can only release binary artifacts which also have the source released, but there are no rules saying the source distribution must not include any binary artifacts, so if this is what the project thinks works best then its fine. It is missing the Incubating disclaimer text which should be included in the README or a DISCLAIMER file, see http://incubator.apache.org/guides/branding.html#disclaimers I tried building it with ant build and that failed, don't know if that my environment or something else: BUILD FAILED C:\ASF\manifoldcf\apache-manifoldcf-0.1-incubator\build.xml:353: The following error occurred while executing this line: C:\ASF\manifoldcf\apache-manifoldcf-0.1-incubator\connectors\jdbc\build.xml:52: C:\ASF\manifoldcf\apache-manifoldcf-0.1-incubator\co nnectors\jdbc\jdbc-drivers does not exist. Other than that it looks ok to me. Its big and inlcudes some duplicate stuff but if thats what the project thinks is the best approach then its fine, there are plenty of other big projects being distributed. ..ant - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Apache ManifoldCF 0.1
Just noticed that there are a lot of source files without AL headers. The RAT tool can detect these for you. Also, there should normally be a DISCLAIMER file at the top-level of archives and SVN trees. It's simpler to have this in a separate file, which can then just be deleted upon graduation. On 6 January 2011 13:12, Grant Ingersoll gsing...@apache.org wrote: Hi, The Apache ManifoldCF community has voted to release our first set of artifacts and now would like an Incubator vote. Since this is our first release, extra attention to detail is appreciated. You can find the artifacts at http://people.apache.org/~kwright/ Thanks, Grant - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Apache ManifoldCF 0.1
Karl Wright wrote: Very well; we will discontinue all binary distributions. One major problem will therefore be that we rely on Apache Forrest to build the documentation pages. Forrest requires Java 1.5. The availability of documentation in the release will therefore depend on the availability of Java 1.5 to the person building it. Is this acceptable? It is a tiny isolated problem. There are two simple workarounds. People do not need to stick with Java 1.5 http://forrest.apache.org/faq.html#oldjing -David - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Apache ManifoldCF 0.1
We've been using the RAT tool. The files without headers are in part Microsoft project files, which cannot have headers added without breaking them. Also, we build JSON sources, which are licensed with an accepted JSON license that RAT does not recognize. I've captured a lot of these exceptions in the ant target rat-sources. Karl If you have specific concerns, let's discuss them. On Thu, Jan 6, 2011 at 4:03 PM, sebb seb...@gmail.com wrote: Just noticed that there are a lot of source files without AL headers. The RAT tool can detect these for you. Also, there should normally be a DISCLAIMER file at the top-level of archives and SVN trees. It's simpler to have this in a separate file, which can then just be deleted upon graduation. On 6 January 2011 13:12, Grant Ingersoll gsing...@apache.org wrote: Hi, The Apache ManifoldCF community has voted to release our first set of artifacts and now would like an Incubator vote. Since this is our first release, extra attention to detail is appreciated. You can find the artifacts at http://people.apache.org/~kwright/ Thanks, Grant - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Apache ManifoldCF 0.1
On 6 January 2011 22:38, Karl Wright daddy...@gmail.com wrote: We've been using the RAT tool. In which case it would be helpful to provide the RAT report(s). The files without headers are in part Microsoft project files, which cannot have headers added without breaking them. Also, we build JSON sources, which are licensed with an accepted JSON license that RAT does not recognize. I've captured a lot of these exceptions in the ant target rat-sources. Karl If you have specific concerns, let's discuss them. The following sources don't appear to be JSON files, yet they don't have AL headers: framework/crawler-ui/src/main/webapp/WEB-INF/jsp/x.tld framework/crawler-ui/src/main/webapp/WEB-INF/jsp/sql.tld framework/crawler-ui/src/main/webapp/WEB-INF/jsp/fmt.tld framework/crawler-ui/src/main/webapp/WEB-INF/jsp/c.tld connectors/sharepoint/webservice/Web References/SPPermissionsService/Reference.map connectors/sharepoint/webservice/Properties/Settings.settings connectors/sharepoint/webservice/Properties/AssemblyInfo.cs connectors/meridio/webservice/Test Harness/source code/TestHarness.cs AFAICT these are not excluded by the Ant target. BTW some of the .cs files appear to have BOM markers - not sure whether that is intentional. On Thu, Jan 6, 2011 at 4:03 PM, sebb seb...@gmail.com wrote: Just noticed that there are a lot of source files without AL headers. The RAT tool can detect these for you. Also, there should normally be a DISCLAIMER file at the top-level of archives and SVN trees. It's simpler to have this in a separate file, which can then just be deleted upon graduation. On 6 January 2011 13:12, Grant Ingersoll gsing...@apache.org wrote: Hi, The Apache ManifoldCF community has voted to release our first set of artifacts and now would like an Incubator vote. Since this is our first release, extra attention to detail is appreciated. You can find the artifacts at http://people.apache.org/~kwright/ Thanks, Grant - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Apache ManifoldCF 0.1
The .cs files are maintained by Visual Studio and you cannot change the format if you want them to keep working. Same with the .map file. I will add them to exclusions for the rat target The .tld's were taken from Apache Tomcat, but did not include Apache headers. I am not sure what I should do with those, which is why I left them as is. What is your recommendation? Karl On Thu, Jan 6, 2011 at 6:26 PM, sebb seb...@gmail.com wrote: On 6 January 2011 22:38, Karl Wright daddy...@gmail.com wrote: We've been using the RAT tool. In which case it would be helpful to provide the RAT report(s). The files without headers are in part Microsoft project files, which cannot have headers added without breaking them. Also, we build JSON sources, which are licensed with an accepted JSON license that RAT does not recognize. I've captured a lot of these exceptions in the ant target rat-sources. Karl If you have specific concerns, let's discuss them. The following sources don't appear to be JSON files, yet they don't have AL headers: framework/crawler-ui/src/main/webapp/WEB-INF/jsp/x.tld framework/crawler-ui/src/main/webapp/WEB-INF/jsp/sql.tld framework/crawler-ui/src/main/webapp/WEB-INF/jsp/fmt.tld framework/crawler-ui/src/main/webapp/WEB-INF/jsp/c.tld connectors/sharepoint/webservice/Web References/SPPermissionsService/Reference.map connectors/sharepoint/webservice/Properties/Settings.settings connectors/sharepoint/webservice/Properties/AssemblyInfo.cs connectors/meridio/webservice/Test Harness/source code/TestHarness.cs AFAICT these are not excluded by the Ant target. BTW some of the .cs files appear to have BOM markers - not sure whether that is intentional. On Thu, Jan 6, 2011 at 4:03 PM, sebb seb...@gmail.com wrote: Just noticed that there are a lot of source files without AL headers. The RAT tool can detect these for you. Also, there should normally be a DISCLAIMER file at the top-level of archives and SVN trees. It's simpler to have this in a separate file, which can then just be deleted upon graduation. On 6 January 2011 13:12, Grant Ingersoll gsing...@apache.org wrote: Hi, The Apache ManifoldCF community has voted to release our first set of artifacts and now would like an Incubator vote. Since this is our first release, extra attention to detail is appreciated. You can find the artifacts at http://people.apache.org/~kwright/ Thanks, Grant - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Apache ManifoldCF 0.1
They were downloaded from the jakarta standard taglibs 1.1.2, from this URL: http://jakarta.apache.org/site/downloads/downloads_taglibs-standard.cgi The project was folded into tomcat, but I simply used the tag libraries from the separately-bundled artifact. It turns out that the Apache headers were not on it, however, although it seems very clear that these *should* have apache headers on them. I'm happy to just go ahead and do that, unless you think it would be a mistake. Karl On Thu, Jan 6, 2011 at 8:13 PM, sebb seb...@gmail.com wrote: On 6 January 2011 23:53, Karl Wright daddy...@gmail.com wrote: The .cs files are maintained by Visual Studio and you cannot change the format if you want them to keep working. Same with the .map file. I will add them to exclusions for the rat target The .tld's were taken from Apache Tomcat, but did not include Apache headers. I am not sure what I should do with those, which is why I left them as is. What is your recommendation? Depends on the source. If they are ASF files then they should have ASF headers in Tomcat and here. If not, then they may require entries in NOTICE or LICENSE. Probably best to re-check the Tomcat sources, and if there is no header, ask why on the Tomcat list. Karl On Thu, Jan 6, 2011 at 6:26 PM, sebb seb...@gmail.com wrote: On 6 January 2011 22:38, Karl Wright daddy...@gmail.com wrote: We've been using the RAT tool. In which case it would be helpful to provide the RAT report(s). The files without headers are in part Microsoft project files, which cannot have headers added without breaking them. Also, we build JSON sources, which are licensed with an accepted JSON license that RAT does not recognize. I've captured a lot of these exceptions in the ant target rat-sources. Karl If you have specific concerns, let's discuss them. The following sources don't appear to be JSON files, yet they don't have AL headers: framework/crawler-ui/src/main/webapp/WEB-INF/jsp/x.tld framework/crawler-ui/src/main/webapp/WEB-INF/jsp/sql.tld framework/crawler-ui/src/main/webapp/WEB-INF/jsp/fmt.tld framework/crawler-ui/src/main/webapp/WEB-INF/jsp/c.tld connectors/sharepoint/webservice/Web References/SPPermissionsService/Reference.map connectors/sharepoint/webservice/Properties/Settings.settings connectors/sharepoint/webservice/Properties/AssemblyInfo.cs connectors/meridio/webservice/Test Harness/source code/TestHarness.cs AFAICT these are not excluded by the Ant target. BTW some of the .cs files appear to have BOM markers - not sure whether that is intentional. On Thu, Jan 6, 2011 at 4:03 PM, sebb seb...@gmail.com wrote: Just noticed that there are a lot of source files without AL headers. The RAT tool can detect these for you. Also, there should normally be a DISCLAIMER file at the top-level of archives and SVN trees. It's simpler to have this in a separate file, which can then just be deleted upon graduation. On 6 January 2011 13:12, Grant Ingersoll gsing...@apache.org wrote: Hi, The Apache ManifoldCF community has voted to release our first set of artifacts and now would like an Incubator vote. Since this is our first release, extra attention to detail is appreciated. You can find the artifacts at http://people.apache.org/~kwright/ Thanks, Grant - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Apache ManifoldCF 0.1
The RAT report after these changes looks good except for two files, which come from the skins in the site: [rat:report] Unapproved licenses: [rat:report] [rat:report] C:/wip/mcf-release/release-0.1-branch/site/src/documentation/skins/common/xslt/html/split.xsl [rat:report] C:/wip/mcf-release/release-0.1-branch/site/src/documentation/skins/lucene/note.txt [rat:report] [rat:report] *** One of these looks like it comes from Forrest itself (the first), and has this header: !-- This stylesheet was taken from the XSLT FAQ http://www.dpawson.co.uk/xsl/ Comments and adaption to be used without normalize-space() by forrest-...@xml.apache.org -- No idea what to do about that one. The other is merely a todo list in the Lucene skin, which I believe could simply be removed. Thoughts? Karl On Thu, Jan 6, 2011 at 8:26 PM, Karl Wright daddy...@gmail.com wrote: They were downloaded from the jakarta standard taglibs 1.1.2, from this URL: http://jakarta.apache.org/site/downloads/downloads_taglibs-standard.cgi The project was folded into tomcat, but I simply used the tag libraries from the separately-bundled artifact. It turns out that the Apache headers were not on it, however, although it seems very clear that these *should* have apache headers on them. I'm happy to just go ahead and do that, unless you think it would be a mistake. Karl On Thu, Jan 6, 2011 at 8:13 PM, sebb seb...@gmail.com wrote: On 6 January 2011 23:53, Karl Wright daddy...@gmail.com wrote: The .cs files are maintained by Visual Studio and you cannot change the format if you want them to keep working. Same with the .map file. I will add them to exclusions for the rat target The .tld's were taken from Apache Tomcat, but did not include Apache headers. I am not sure what I should do with those, which is why I left them as is. What is your recommendation? Depends on the source. If they are ASF files then they should have ASF headers in Tomcat and here. If not, then they may require entries in NOTICE or LICENSE. Probably best to re-check the Tomcat sources, and if there is no header, ask why on the Tomcat list. Karl On Thu, Jan 6, 2011 at 6:26 PM, sebb seb...@gmail.com wrote: On 6 January 2011 22:38, Karl Wright daddy...@gmail.com wrote: We've been using the RAT tool. In which case it would be helpful to provide the RAT report(s). The files without headers are in part Microsoft project files, which cannot have headers added without breaking them. Also, we build JSON sources, which are licensed with an accepted JSON license that RAT does not recognize. I've captured a lot of these exceptions in the ant target rat-sources. Karl If you have specific concerns, let's discuss them. The following sources don't appear to be JSON files, yet they don't have AL headers: framework/crawler-ui/src/main/webapp/WEB-INF/jsp/x.tld framework/crawler-ui/src/main/webapp/WEB-INF/jsp/sql.tld framework/crawler-ui/src/main/webapp/WEB-INF/jsp/fmt.tld framework/crawler-ui/src/main/webapp/WEB-INF/jsp/c.tld connectors/sharepoint/webservice/Web References/SPPermissionsService/Reference.map connectors/sharepoint/webservice/Properties/Settings.settings connectors/sharepoint/webservice/Properties/AssemblyInfo.cs connectors/meridio/webservice/Test Harness/source code/TestHarness.cs AFAICT these are not excluded by the Ant target. BTW some of the .cs files appear to have BOM markers - not sure whether that is intentional. On Thu, Jan 6, 2011 at 4:03 PM, sebb seb...@gmail.com wrote: Just noticed that there are a lot of source files without AL headers. The RAT tool can detect these for you. Also, there should normally be a DISCLAIMER file at the top-level of archives and SVN trees. It's simpler to have this in a separate file, which can then just be deleted upon graduation. On 6 January 2011 13:12, Grant Ingersoll gsing...@apache.org wrote: Hi, The Apache ManifoldCF community has voted to release our first set of artifacts and now would like an Incubator vote. Since this is our first release, extra attention to detail is appreciated. You can find the artifacts at http://people.apache.org/~kwright/ Thanks, Grant - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail:
