I've updated the dependencies page with the latest status of the RPMs.
https://fedorahosted.org/candlepin/wiki/Dependencies
The One's that I am building are at the bottom under MySpecs. They are all checked into a huge ugly project on github:
http://github.com/admiyo/MySpecs
There are a couple there that can be removed: aopalliance is covered by JPackage, I think, and the asm3 is covered by objectweb-asm.
Once I get all of them built, the real fun starts: trying to make this whole thing work together.
One quick check I plan on doing is gathering the jars from these files, and comparing to a list of the files composed in the jars inside of candlepin/WEB_INF/lib. I know that some of the test classes aren't there, as some projects use som rfairly archaic tools for testing, like Acme.Serve.Serve. Yes, that is a fully qualified java class name.
There have been a few additional deps that have been added in order to build some of these.
Let me state for the record that Java not having Header files is a bigger pain than I ever realized.
Of the ones I have left: teh two rest-easy ones should be easy to medium, as I think I've gotten most of the resteasy deps knowcked out. jta Is probably pretty easy, as I have the sources for it. I haven't looked at the The Jackson jars at all.
I did a quick stab at Hibernate-tools this morning. Lots of Binary dependencies. It is probably going to be the worst one.
On 04/08/2010 09:39 PM, Adam Young wrote:
I've updated the dependencies page with the latest status of the RPMs.
https://fedorahosted.org/candlepin/wiki/Dependencies
The One's that I am building are at the bottom under MySpecs. They are all checked into a huge ugly project on github:
http://github.com/admiyo/MySpecs
There are a couple there that can be removed: aopalliance is covered by JPackage, I think, and the asm3 is covered by objectweb-asm.
Once I get all of them built, the real fun starts: trying to make this whole thing work together.
Is the model build against maven (which buildr brings in), and run against RPM? Or, is the thinking a custom reliazer from builder to look local?
One quick check I plan on doing is gathering the jars from these files, and comparing to a list of the files composed in the jars inside of candlepin/WEB_INF/lib. I know that some of the test classes aren't there, as some projects use som rfairly archaic tools for testing, like Acme.Serve.Serve. Yes, that is a fully qualified java class name.
Yes, Coyote needs it.
There have been a few additional deps that have been added in order to build some of these.
Let me state for the record that Java not having Header files is a bigger pain than I ever realized.
Of the ones I have left: teh two rest-easy ones should be easy to medium, as I think I've gotten most of the resteasy deps knowcked out. jta Is probably pretty easy, as I have the sources for it. I haven't looked at the The Jackson jars at all.
I did a quick stab at Hibernate-tools this morning. Lots of Binary dependencies. It is probably going to be the worst one.
-- bk
On Fri, Apr 9, 2010 at 8:04 AM, Bryan Kearney bkearney@redhat.com wrote:
On 04/08/2010 09:39 PM, Adam Young wrote:
I've updated the dependencies page with the latest status of the RPMs.
https://fedorahosted.org/candlepin/wiki/Dependencies
The One's that I am building are at the bottom under MySpecs. They are all checked into a huge ugly project on github:
http://github.com/admiyo/MySpecs
There are a couple there that can be removed: aopalliance is covered by JPackage, I think, and the asm3 is covered by objectweb-asm.
Once I get all of them built, the real fun starts: trying to make this whole thing work together.
Is the model build against maven (which buildr brings in), and run against RPM? Or, is the thinking a custom reliazer from builder to look local?
IMO once the deps are *all* done, we would make them BuildRequires or Requires, then two things need to happen
1) find where the .m2 directory is in the buildroot and simulate a local repo for the BuildRequires deps. 1.1) unless there's a way to setup local maven repos using jars in /usr/share/java which might be the case 2) the Requires will be symlinked into WEB-INF/lib during deployment
I prefer we do this magic stuff in the spec file vs in the buildr buildfile. That way the specific rpm wizardry stays hidden.
One quick check I plan on doing is gathering the jars from these files, and comparing to a list of the files composed in the jars inside of candlepin/WEB_INF/lib. I know that some of the test classes aren't there, as some projects use som rfairly archaic tools for testing, like Acme.Serve.Serve. Yes, that is a fully qualified java class name.
Yes, Coyote needs it.
There have been a few additional deps that have been added in order to build some of these.
Let me state for the record that Java not having Header files is a bigger pain than I ever realized.
HAHAHA :)
Of the ones I have left: teh two rest-easy ones should be easy to medium, as I think I've gotten most of the resteasy deps knowcked out. jta Is probably pretty easy, as I have the sources for it. I haven't looked at the The Jackson jars at all.
I did a quick stab at Hibernate-tools this morning. Lots of Binary dependencies. It is probably going to be the worst one.
Yeah usually hibernate related ones are quite gnarly.
jesus
candlepin@lists.fedorahosted.org