Re: Bundling ActiveMQ version 5.x in RPM
Fernando Nasser <[email protected]>
| Newsgroups | gmane.linux.jpackage.general |
|---|---|
| Message-ID | <[email protected]> |
On 11-02-21 2:19 PM, Nico Kadel-Garcia wrote: > On Mon, Feb 21, 2011 at 12:50 AM, David Walluck<[email protected]> wrote: >> On 02/20/2011 08:07 PM, Nico Kadel-Garcia wrote: >>> installable .zip. I've taken some steps with the old activemq4.spec >>> file and re-written it to simply install the .zip contents. Is this >>> unreasonble? If I can verify it, should I work with this or is there >>> any policy to build from source if at all possible (which will be one >>> heck of a lot more work). >> JPackage has a policy that it should be built from source, but it might >> work for your personal needs. > That seems a reasonable policy. It's clearly not enforced fo the > "non-free" packages, but I see those are handled rather differently. These had non-distributable licenses. It was mostly the JDK, which we now have OpenJDK for anyway. > Unfortunately, I see that the current ActiveMQ release build with > Maven, and the Apache published .pod for it has a maven 2.0.9 > dependency built right into it, Just patch it to 2.0.8 -- we built lots of things that siad 2.0.9 with 2.0.8 (well, sometimes we had to make small adjustments). > and goes out to the Internet at large > to grab losts of different components when running "mvn install" on Use mvn-jpp Look at some other package that build with maven (some simple one) and just adapt what is done there. > it. The result is is, to my mind fragile because it's grabbing > components from offsite and of unknown provenance, just as Perl's CPAN > utilities tend to grab components which may not be compatible with the > existing environment. Well, the Maven we have will ignore version differences. If the coordinate is a bit difference (different groupId) you can add a depmap to the build. For the things we don't have you will get missing artifact errors. Initially you can just add those as binary files, just drop them into your local maven repo before mvn-jpp is called. You can grab them from whatever repo they live in. Then go replacing these with real builds that provide them. Regards, Fernando > The results are troublesome. > _______________________________________________ > JPackage-discuss mailing list > [email protected] > https://www.zarb.org/mailman/listinfo/jpackage-discuss >