Removed 3.0.2 artifacts from the dist/dev tree. I pulled the zips from the Jenkins build artifacts, and then repackaged them to *.tgz as well. The build.xml has been heavily modified since 3.0.2, so perhaps some things got lost along the way, as well as renamed. This is the first new release since the reworking of the XMLBeans build.
If the package artifacts should be named differently, that should go in build.xml, not manual steps after. I don't know XMLBeans at all, so I have no frame of reference other than previous builds to know what was intentional and what was accidental in the modifications since October. I can update the README if we want, but I'd be doing so without a good sense of where the project stands, as I've never used it outside of a POI dependency. On Thu, Mar 21, 2019 at 12:14 AM Dominik Stadler <dominik.stad...@gmx.at> wrote: > Can you remove the 3.0.2 files from > https://dist.apache.org/repos/dist/dev/poi/xmlbeans/, they are available > as > official release anyway. > > File names are slightly different now, not sure if this is intended or will > cause issues: xmlbeans-3.0.2-src.tgz > < > https://dist.apache.org/repos/dist/dev/poi/xmlbeans/src/xmlbeans-3.0.2-src.tgz > > > vs. xmlbeans-src-3.0.3.tgz > < > https://dist.apache.org/repos/dist/dev/poi/xmlbeans/src/xmlbeans-src-3.0.3.tgz > >, > similar for bin: xmlbeans-3.0.2.tgz > < > https://dist.apache.org/repos/dist/dev/poi/xmlbeans/bin/xmlbeans-3.0.2.tgz > > > vs. xmlbeans-bin-3.0.3.tgz > < > https://dist.apache.org/repos/dist/dev/poi/xmlbeans/bin/xmlbeans-bin-3.0.3.tgz > > > > Inside the files I found the following differences compared to 3.0.2: > > * In the bin-files, the folder docs/reference is missing, this included > javadoc in 3.0.2 > * jar-files in the bin-tgz are now called xmlbeans-3.0.3.jar compared to > just xmlbeans.jar before. files for javadoc and src jars are new in the > bin-tgz > * in the bin-tgz, lib/xmlbean_xpath.jar and xmlpublic.jar are missing. Not > sure what they were used for, though > * in the bin-tgz, the README is not updated, it actually still states > 2.5.0, so it was not updated in a long time > * The content of the src-tgz/zip is fairly different, libs are moved > around, the folder "bin" with scripts is missing, ... most of it will be > on-purpose, but we should check, I don't know XMLBeans well enough to be > sure > * We should exclude file "build.javacheck.xml" in the packaging, it is used > by CI jobs, but not useful to include > > > Dominik. > > On Thu, Mar 21, 2019 at 12:00 AM Greg Woolsey <greg.wool...@gmail.com> > wrote: > > > I have pushed xmlbeans 3.0.3 release candidate to: > > > > > > > https://repository.apache.org/content/repositories/staging/org/apache/xmlbeans/xmlbeans/3.0.3/ > > > > https://dist.apache.org/repos/dist/dev/poi/xmlbeans/bin > > https://dist.apache.org/repos/dist/dev/poi/xmlbeans/src > > > > If those look good to folks, what do I do to "release" from staging in > the > > repository? Do I just click the "Release" button in the web interface, > > perhaps selecting "Public Repositories" if there is a prompt? > > > > I assume I then modify site docs like site.xml, modifying 3.0.2 to 3.0.3, > > then running forrest and committing. It's my understanding we don't need > > to do anything special to release the site changes? > > > > Any other steps? I'm thinking I should also commit what I've done in a > > build instructions file so this thread and the previous one aren't the > > source for future releases. > > > > Maybe also mentioning the AdblockPlus Chrome and Firefox extensions break > > nexus uploads unless you exclude the repository domain. That cost me a > bit > > of time. > > >
