Ok, I just decided to use the maven jar plugin to generate a client and server jar to simplify things. Now, I just have to figure out how to make each of the bundle executions act on each of those.
Brendan Haverlock -----Original Message----- From: Allen Lau [mailto:[email protected]] Sent: Friday, May 15, 2009 1:05 PM To: [email protected] Subject: Re: Maven bundle plugin - building multiple bundles in one project Hi, Not sure if this will help, but if you want to run the bundle-plugin twice, I think you can accomplish this by specifying multiple <execution> with separate <configuration> options. For example: <artifactId>maven-bundle-plugin</artifactId> <executions> <execution> <id>bundle-manifest</id> <phase>process-classes</phase> <goals> <goal>manifest</goal> </goals> <configuration>... </configuration> </execution> <execution> <id> other-job</id> <configuration>...</configuration> </execution> </executions> Allen On Fri, May 15, 2009 at 12:39 PM, Brendan Haverlock <[email protected]>wrote: > Hi all, > > > > I have a bunch of maven modules, each of which has its own logical client, > server, and common packages (shared between the client and server). I want > to make both a client and a server bundle within this project, yet I don't > get how we can separate the two in the maven bundle plugin. I tried > including the classes of just the client and common in an > <Include-Resource> > tag, but that didn't have an effect because it still included all the class > files from the project. > > > > I also am in a pickle because I would need to run two of the bundle > plugins, > which I don't think is supported under the <build> tag. > > > > Does anyone have any insight on either of these issues? Any help would be > appreciated. Also, I don't want to split up each project into 3 individual > projects because then I'd have 50+ projects with a huge web of > dependencies. > > > > Thanks! > > > > Brendan Haverlock > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
