The -bin archive doesnt have a top level pom because it is the -bin archive. It doesnt contain the full build, just the client+dependency jars and a subdir with copy of the examples tree. The -src archive has the full build and thus top level pom to build it all.
The examples dir in the -bin archive has a pom and is its own build, which anyone running after it is released will find just works without doing anything else first, as it will retrieve the 'parent' pom along with all the other dependencies needed from Maven Central. However, prior to release, these bits dont yet exist in a public repo that the build looks at, and so the build will fail if not taking steps to make them available to it some other way. E.g. by adding the staging repository using the details in the original mail (which contains the pre-built bits that will actually be on Central upon actual release), so the parent pom and client deps can be found there (temporarily) for testing that they work before releasing them. You can either add the staging repo details to the examples pom itself, or alternatively to an active profile within the maven settings.xml file (making it available to builds, without modifying them). Alternatively, and what I guess you may have done before, you could build and install the needed bits yourself to the maven local repo by "mvn install" from the source archive first, before ever trying to run the examples build. Maven would then find your locally-built installed copy of the bits needed and use that, without needing to know about the staging repo. Though then strictly speaking you aren't running against specifically what most people will probably end up using once it is actually released (the staged bits already built), just an equivalent you have built yourself from the same sources. On Thu, 26 May 2022 at 11:03, Gordon Sim <g...@redhat.com> wrote: > > +1, built from source including all tests and ran example against router > > (My usual approach here did not work as the > apache-qpid-protonj2-1.0.0-M6-bin.tar.gz tarball which I 'install' > from after building did not have a top level maven project file, so > running maven against the examples failed. However I just used the > examples as built in the main source tree to run. Most likely this is > my stupidity with regard to maven, just mentioning incase something is > not as expected). > > On Tue, May 24, 2022 at 2:18 PM Robbie Gemmell <robbie.gemm...@gmail.com> > wrote: > > > > On Mon, 23 May 2022 at 17:24, Timothy Bish <tabish...@gmail.com> wrote: > > > > > > Hi folks, > > > > > > I have put together a release candidate for a 1.0.0-M6 Qpid ProtonJ2 > > > release, > > > please give it a test out and vote accordingly. > > > > > > The source and binary archives can be grabbed from: > > > https://dist.apache.org/repos/dist/dev/qpid/protonj2/1.0.0-M6-rc1/ > > > > > > The maven artifacts are also staged for now at: > > > https://repository.apache.org/content/repositories/orgapacheqpid-1240 > > > > > > The JIRAs assigned are: > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12313720&version=12351559 > > > > > > Regards > > > > > > P.S. If you want to test it out using maven (e.g with the examples > > > src, or your own things), you can temporarily add this to your poms to > > > access the staging repo: > > > > > > <repositories> > > > <repository> > > > <id>staging</id> > > > <url>https://repository.apache.org/content/repositories/orgapacheqpid-1240</url> > > > </repository> > > > </repositories> > > > > > > The dependency for the protocol engine or the client itself would then be: > > > > > > <dependency> > > > <groupId>org.apache.qpid</groupId> > > > <artifactId>protonj2</artifactId> > > > <version>1.0.0-M6</version> > > > </dependency> > > > <dependency> > > > <groupId>org.apache.qpid</groupId> > > > <artifactId>protonj2-client</artifactId> > > > <version>1.0.0-M6</version> > > > </dependency> > > > > > > -- > > > Tim Bish > > > > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org > > > For additional commands, e-mail: users-h...@qpid.apache.org > > > > > > > +1 > > > > I checked things out as follows: > > - Verified the signature + checksum files. > > - Checked for LICENCE + NOTICE files in the archives. > > - Used "mvn apache-rat:check" to verify headers in the source archive. > > - Ran the source build and tests. > > - Ran HelloWorld example against Qpid Dispatch 1.19.0 and ActiveMQ > > Artemis 2.22.0 using staged client bits. > > > > Robbie > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org > > For additional commands, e-mail: users-h...@qpid.apache.org > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org > For additional commands, e-mail: users-h...@qpid.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional commands, e-mail: users-h...@qpid.apache.org
