Sorry, yes. Ralph
On Wed, Aug 17, 2011 at 1:33 PM, Luc Maisonobe <luc.maison...@free.fr>wrote: > Le 17/08/2011 22:13, ralph.goers @dslextreme.com a écrit : > > OK. I will take care of this, the MD5 issue and do something with the >> README >> in a few hours after I get home from work and send out another release >> vote. >> > > Was this vote offocially cancelled ? > > Luc > > > In the meantime, if there are any other problems that should be corrected >> I'd appreciate the feedback. >> >> Ralph >> >> On Wed, Aug 17, 2011 at 1:05 PM, Phil Steitz<phil.ste...@gmail.com> >> wrote: >> >> On 8/17/11 12:43 PM, ralph.goers @dslextreme.com wrote: >>> >>>> The sandbox question I can't answer very well. The sandbox stuff was >>>> >>> there >>> >>>> long before I arrived to work on VFS, although I rewrote the webdav >>>> stuff >>>> and moved it to core. The only real description is on the web site under >>>> "File Systems" where it says they under in development (not by me :-) ). >>>> >>>> None of the sandbox stuff appears to have been distributed with the 1.0 >>>> release, including in the source distribution. I don't know of a way I >>>> >>> can >>> >>>> stop Maven from deploying it to the staging repo, but I can certainly >>>> >>> delete >>> >>>> it from there just like I did the distribution zips. If desired, I'd >>>> have >>>> >>> to >>> >>>> do another release to remove that source from the release. It would >>>> also >>>> stay on the web site. >>>> >>> >>> Staying on the web site is fine. Releasing code and jars that we do >>> not intend to support is not, so I am -1 on this release. We used >>> to have an /experimental tree in [math] that we omitted from source >>> and binary releases. In the source assembly descriptor, this kind >>> of thing at least used to work: >>> >>> <fileSet> >>> <directory>src</directory> >>> <excludes> >>> <exclude>**/mantissa/**</**exclude> >>> <exclude>**/experimental/**</**exclude> >>> </excludes> >>> </fileset> >>> >>> Phil >>> >>>> >>>> Ralph >>>> >>>> >>>> On Wed, Aug 17, 2011 at 12:27 PM, Phil Steitz<phil.ste...@gmail.com> >>>> >>> wrote: >>> >>>> >>>> On 8/17/11 11:32 AM, ralph.goers @dslextreme.com wrote: >>>>> >>>>>> What do you mean "It did not work"? This is a multi-project site so >>>>>> in >>>>>> general mvn site is useless. You have to run mvn site:stage-deply >>>>>> -DstagingSiteURL="file url where I want the site to go". I suppose I >>>>>> >>>>> could >>>>> >>>>>> add that to the readme, but it is documented pretty well on the maven >>>>>> >>>>> site >>>>> >>>>>> plugin web site. >>>>>> >>>>>> In a prior release candidate I wasn't generating the release notes and >>>>>> >>>>> I >>> >>>> had >>>>> >>>>>> the comment in the README. The release was vetoed due to the lack of >>>>>> release notes. I simply forgot to delete the README. >>>>>> >>>>>> Did you run announcement-generate from the core directory? That only >>>>>> >>>>> works >>>>> >>>>>> at the project root. >>>>>> >>>>>> The build instructions consist of: >>>>>> >>>>>> mvn clean install >>>>>> >>>>> Those instructions appear on the "Download and Build" paged linked >>>>> in the main site menu, so I don't see this as a a blocker. >>>>> Instructions on how to build the site are nice to have, but not >>>>> showstoppers, IMO - especially since they generally stop working as >>>>> incompatible plugin and / or maven versions change. >>>>> >>>>> One question I have and I apologize if this has already been >>>>> discussed is are we sure we want to release the "sandbox" stuff? >>>>> There is no disclaimer of any kind on the web site or in the release >>>>> notes. If the contents of that jar are being released as normal >>>>> artifacts, why is it called "sandbox"? If not, why no explanation >>>>> anywhere of what "sandbox" means? >>>>> >>>>> Phil >>>>> >>>>>> Ralph >>>>>> >>>>>> On Wed, Aug 17, 2011 at 8:13 AM, Gary Gregory<garydgreg...@gmail.com >>>>>> wrote: >>>>>> >>>>>> Hi All: >>>>>>> >>>>>>> I am not sure if I am building correctly, but here is what I found. >>>>>>> >>>>>> Some >>> >>>> build instructions in the readme.txt file would help. >>>>>>> >>>>>>> Downloaded source zip from >>>>>>> http://people.apache.org/~**rgoers/commons-vfs/staged/<http://people.apache.org/~rgoers/commons-vfs/staged/> >>>>>>> >>>>>>> From the root I ran "mvn site" which did not work. Fine, starting to >>>>>>> >>>>>> poke >>>>> >>>>>> around. >>>>>>> >>>>>>> From the "dist" directory I ran "mvn site" which did not work: >>>>>>> >>>>>>> [INFO] Generating "Dependency Management" report --- >>>>>>> maven-project-info-reports-**plugin:2.3.1 >>>>>>> Downloading: >>>>>>> >>>>>>> >>>>>>> >>>>> http://repo1.maven.org/maven2/**org/apache/commons/commons-** >>> vfs-examples/2.0/commons-vfs-**examples-2.0.pom<http://repo1.maven.org/maven2/org/apache/commons/commons-vfs-examples/2.0/commons-vfs-examples-2.0.pom> >>> >>>> [WARNING] Unable to create Maven project from repository. >>>>>>> org.apache.maven.project.**ProjectBuildingException: Error resolving >>>>>>> >>>>>> project >>>>> >>>>>> artifact: Failure to find >>>>>>> >>>>>> org.apache.commons:commons-**vfs-examples:pom:2.0 >>>>> >>>>>> in >>>>>>> http://r >>>>>>> epo1.maven.org/maven2 was cached in the local repository, resolution >>>>>>> >>>>>> will >>>>> >>>>>> not be reattempted until the update interval of central has elapsed or >>>>>>> updates are for >>>>>>> ced for project org.apache.commons:commons-**vfs-examples:pom:2.0 >>>>>>> at >>>>>>> >>>>>>> >>>>>>> >>>>> org.apache.maven.project.**DefaultProjectBuilder.build(** >>> DefaultProjectBuilder.java:**272) >>> >>>> at >>>>>>> >>>>>>> >>>>>>> >>>>> org.apache.maven.project.**DefaultMavenProjectBuilder.** >>> buildFromRepository(**DefaultMavenProjectBuilder.**java:237) >>> >>>> at >>>>>>> >>>>>>> >>>>>>> >>>>> org.apache.maven.project.**DefaultMavenProjectBuilder.** >>> buildFromRepository(**DefaultMavenProjectBuilder.**java:252) >>> >>>> Why would building the site require an installed VFS2? >>>>>>> >>>>>>> The README.txt says to run "mvn changes:announcement-generate" to get >>>>>>> release notes but there is a RELEASE-NOTES.txt file in the same dir. >>>>>>> >>>>>> Why >>> >>>> do >>>>> >>>>>> we need two? >>>>>>> >>>>>>> When I do run "mvn changes:announcement-generate"**, I get: >>>>>>> >>>>>>> [INFO] --- maven-changes-plugin:2.4:**announcement-generate >>>>>>> >>>>>> (default-cli) >>> >>>> @ >>>>> >>>>>> commons-vfs2 --- >>>>>>> [WARNING] changes.xml file >>>>>>> C:\test\commons-vfs-2.0\core\**src\changes\changes.xml does not >>>>>>> exist. >>>>>>> >>>>>>> There is no such file. >>>>>>> >>>>>>> I do not know if I should -1 this because there are no build >>>>>>> >>>>>> instructions, >>>>> >>>>>> or if there are, they are located in some non-obvious spot. >>>>>>> >>>>>>> Gary >>>>>>> >>>>>>> On Wed, Aug 17, 2011 at 1:44 AM, Ralph Goers< >>>>>>> >>>>>> ralph.go...@dslextreme.com >>>>> >>>>>> wrote: >>>>>>>> This is a vote to release Apache Commons VFS 2.0. >>>>>>>> >>>>>>>> Changes made since the last candidate: >>>>>>>> >>>>>>>> * Fixed the manifest error that was causing the build to fail. >>>>>>>> * Changed the copyright date in the Notice file from 2010 to 2011. >>>>>>>> * Removed the references to javamail from the Notice file. >>>>>>>> * Removed all the @version tags >>>>>>>> * Fixed the EOL issues with README.txt, RELEASE-NOTES.txt, and >>>>>>>> src/changes/announcement.vm (osgi/MANIFEST.MF has been removed). >>>>>>>> * Modified the release notes to mention the code is not source >>>>>>>> >>>>>>> compatible >>>>> >>>>>> with VFS 1.x and that the package name changed. >>>>>>>> * Fixed the WARNING for the use of the deprecated tasks element. >>>>>>>> * Fixed the WARNING for the use of the deprecated systemProperties >>>>>>>> >>>>>>> element. >>>>>>> >>>>>>>> * Made sure all jars have NOTICE.txt and LICENSE.txt >>>>>>>> >>>>>>>> The build message >>>>>>>> [WARNING] Ignoring project type pom - supportedProjectTypes = [jar, >>>>>>>> >>>>>>> bundle] >>>>>>> >>>>>>>> was not fixed as that is due to commons parent causing the >>>>>>>> >>>>>>> maven-bundle >>> >>>> plugin to run on all subprojects, including those that don't generate >>>>>>>> bundles or jars. >>>>>>>> >>>>>>>> I have also removed files that shouldn't be present in the Maven >>>>>>>> >>>>>>> repository >>>>>>> >>>>>>>> from the staging repo. >>>>>>>> >>>>>>>> [ ] +1 release it >>>>>>>> [ ] +0 go ahead I don't care >>>>>>>> [ ] -1 no, do not release it because. >>>>>>>> >>>>>>>> Ralph >>>>>>>> >>>>>>>> >>>>>>>> Tag: >>>>>>>> >>>>>>>> >>>>> https://svn.apache.org/repos/**asf/commons/proper/vfs/tags/** >>> commons-vfs2-project-2.0/(**revision1158401)<https://svn.apache.org/repos/asf/commons/proper/vfs/tags/commons-vfs2-project-2.0/(revision1158401)> >>> . >>> >>>> Site: >>>> http://people.apache.org/~**rgoers/commons-vfs/site/<http://people.apache.org/~rgoers/commons-vfs/site/> >>>>>>>> >>>>>>>> Binaries: >>>>>>>> http://people.apache.org/~**rgoers/commons-vfs/staged/<http://people.apache.org/~rgoers/commons-vfs/staged/> >>>>>>>> >>>>>>>> The following artifacts have been staged to the >>>>>>>> >>>>>>> org.apache.commons-045 >>> >>>> (u:rgoers, a:208.29.163.248) repository. >>>>>>>> >>>>>>>> The Maven artifacts are at: >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>> https://repository.apache.org/**content/groups/staging/org/** >>> apache/commons/commons-vfs2/<https://repository.apache.org/content/groups/staging/org/apache/commons/commons-vfs2/> >>> >>>> >>>>> https://repository.apache.org/**content/groups/staging/org/** >>> apache/commons/commons-vfs2-**examples/<https://repository.apache.org/content/groups/staging/org/apache/commons/commons-vfs2-examples/> >>> >>>> >>>>> https://repository.apache.org/**content/groups/staging/org/** >>> apache/commons/commons-vfs2-**project/<https://repository.apache.org/content/groups/staging/org/apache/commons/commons-vfs2-project/> >>> >>>> >>>>> https://repository.apache.org/**content/groups/staging/org/** >>> apache/commons/commons-vfs2-**sandbox/<https://repository.apache.org/content/groups/staging/org/apache/commons/commons-vfs2-sandbox/> >>> >>>> and consist of >>>>>>>> >>>>>>>> archetype-catalog.xml >>>>>>>> commons-vfs2-examples-2.0-**javadoc.jar >>>>>>>> commons-vfs2-examples-2.0-**sources.jar.asc >>>>>>>> commons-vfs2-examples-2.0.pom >>>>>>>> commons-vfs2-examples-2.0-**tests.jar >>>>>>>> commons-vfs2-examples-2.0-**tests.jar.asc >>>>>>>> commons-vfs2-examples-2.0.jar.**asc >>>>>>>> commons-vfs2-examples-2.0.pom.**asc >>>>>>>> commons-vfs2-examples-2.0-**javadoc.jar.asc >>>>>>>> commons-vfs2-examples-2.0.jar >>>>>>>> commons-vfs2-examples-2.0-**sources.jar >>>>>>>> commons-vfs2-project-2.0.pom.**asc >>>>>>>> commons-vfs2-project-2.0.pom >>>>>>>> commons-vfs2-sandbox-2.0.pom.**asc >>>>>>>> commons-vfs2-sandbox-2.0-**sources.jar.asc >>>>>>>> commons-vfs2-sandbox-2.0-test-**sources.jar.asc >>>>>>>> commons-vfs2-sandbox-2.0.jar >>>>>>>> commons-vfs2-sandbox-2.0-**javadoc.jar >>>>>>>> commons-vfs2-sandbox-2.0-test-**sources.jar >>>>>>>> commons-vfs2-sandbox-2.0.jar.**asc >>>>>>>> commons-vfs2-sandbox-2.0-**sources.jar >>>>>>>> commons-vfs2-sandbox-2.0-**javadoc.jar.asc >>>>>>>> commons-vfs2-sandbox-2.0-**tests.jar.asc >>>>>>>> commons-vfs2-sandbox-2.0-**tests.jar >>>>>>>> commons-vfs2-sandbox-2.0.pom >>>>>>>> commons-vfs2-2.0.pom.asc >>>>>>>> commons-vfs2-2.0-javadoc.jar >>>>>>>> commons-vfs2-2.0-tests.jar.asc >>>>>>>> commons-vfs2-2.0-tests.jar >>>>>>>> commons-vfs2-2.0.pom >>>>>>>> commons-vfs2-2.0.jar >>>>>>>> commons-vfs2-2.0-sources.jar.**asc >>>>>>>> commons-vfs2-2.0-test-sources.**jar.asc >>>>>>>> commons-vfs2-2.0.jar.asc >>>>>>>> commons-vfs2-2.0-sources.jar >>>>>>>> commons-vfs2-2.0-test-sources.**jar >>>>>>>> commons-vfs2-2.0-javadoc.jar.**asc >>>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> Thank you, >>>>>>> Gary >>>>>>> >>>>>>> http://garygregory.wordpress.**com/<http://garygregory.wordpress.com/> >>>>>>> http://garygregory.com/ >>>>>>> http://people.apache.org/~**ggregory/<http://people.apache.org/~ggregory/> >>>>>>> http://twitter.com/GaryGregory >>>>>>> >>>>>>> >>>>> ------------------------------**------------------------------** >>>>> --------- >>>>> To unsubscribe, e-mail: >>>>> dev-unsubscribe@commons.**apache.org<dev-unsubscr...@commons.apache.org> >>>>> For additional commands, e-mail: dev-h...@commons.apache.org >>>>> >>>>> >>>>> >>> >>> ------------------------------**------------------------------** >>> --------- >>> To unsubscribe, e-mail: >>> dev-unsubscribe@commons.**apache.org<dev-unsubscr...@commons.apache.org> >>> For additional commands, e-mail: dev-h...@commons.apache.org >>> >>> >>> >> > > ------------------------------**------------------------------**--------- > To unsubscribe, e-mail: > dev-unsubscribe@commons.**apache.org<dev-unsubscr...@commons.apache.org> > For additional commands, e-mail: dev-h...@commons.apache.org > >
