"Bennett, Timothy (JIS - Applications)" <[EMAIL PROTECTED]> wrote on 08/26/2005 12:04:15 PM:
> > -----Original Message----- > Slow and deliberate is good. I'm not avocating that we have all these > questions answered by the weekend, or even at a pace that the community > is uncomfortable with. I didn't mean to come across as trying to force > a breakneck pace. I think I've just got my head into Maven2 a lot > lately, and while I'm in here, I'm finding I've got a lot of questions. > I'm getting up to speed on Maven2 just like anyone else who is looking > to move from Ant or Maven1. > > While I'm elbows deep in Maven2, it's a natural time for me to > experiment with building Felix using Maven2. What I may have failed to > recognize is that it's not a natural time for the rest of the community. > And that's cool. While you are on a M2 kick, it would be interested to know what it would mean to build Eclipse with M2. From what I have seen of the the M2 OSGi plugin, it looks like much of what would normally go in the manifest.mf of a bundle is to be put in a maven POM file and then the build generates the manifest? So what would a M2 POM for say the org.eclipse.osgi and org.eclipse.runtime bundles look like? How are additional (non-standard) headers handled? How are the dependencies managed and compile-time classpaths computed? For example, the org.eclipse.pde.ui bundle directly or indirectly requires about 40 bundles on its compile-time classpath. What is the M2 structure for this? How are platform/JRE dependencies handled? I guess what I am proposing is that you use the Eclipse projects/bundles as a test case for what will come in Felix. As there are more and more people interested in using and building on top of Felix, the build infrastructure you put in place has to scale (both in terms of build performance and usability). Presumably there will be some people who want to use the Eclipse tooling for developing bundles (for Felix or otherwise). Their output should be buildable using your structure. If there are things that can be done in the Eclipse tooling to make that easier, we'd be happy to look at that. Summary: The Eclipse project structure is simple, mostly regular and known. It may be a fine subject for your M2 OSGi experimentation. We could talk about this here or at [EMAIL PROTECTED] Jeff
