On Tue, 2005-11-08 at 09:36 -0600, Ruel Loehr wrote: > Whoops. Hit send too fast....
I created a JIRA issue for an ejb client guide. I'll see if I can get to it later on today. > Existing source tree can be seen here: > > http://anoncvs.forge.jboss.com:8080/viewrep/JBoss/jboss-common/src > > Ruel Loehr > JBoss QA > > ----------------------------- > 512-626-2782 > Yahoo: ruelloehr > Skype: ruelloehr > AOL: dokoruel > > -----Original Message----- > From: Ruel Loehr > Sent: Tuesday, November 08, 2005 9:36 AM > To: 'Maven Users List' > Subject: RE: [M2] single source tree - multiple artifacts - summary > ofoptions > > > >What are the artifacts that you want to produce? > > The first use case is as follows. > > I have a single source tree from which 5 jars are produced. > > Jboss-common.jar - primary source jar > Jboss-common-client.jar - a subset of the primary source jar > Namespace.jar - some javax/xml/namespace classes (this could easily be > split out into a sub project) > Testsuite-support.jar - logging junk > Jboss-archive-browsing.jar - a tiny tiny subset of primary source jar > > The actual source structure can be seen here (our anoncvs is pretty slow > though): > > > >We do support secondary or attached artifacts and an example of that is > >creating an ejb client JAR along with the full ejb jar. > > Exactly this. Is there a guide or an example? I am currently looking > at a multi-project example I pulled from a jira issue located here: > > http://jira.codehaus.org/browse/ARCHETYPE-8 > > > > >We also generally recommend decomposing your build in separate builds > if > >you required multiple source trees. But I can't recommend anything > >without knowing what you're trying to accomplish. > > Agreed. And this is the path I will pursue when necessary, but if there > is a way of creating the client jars, I want to check it out as well. > > In a multi-proj setup how do I get a class from a "common" tree into the > jar of another sub proj? > > > > I realize that my #1 option is to split the tree (this is in fact that > > path I will pursue), but I also want to be able to defend my position > > and state something like, > > > > "I split the source tree due to the fact that there are no workarounds > > in maven2 for producing multiple artifacts from a single source tree." > > >> That's not entirely true. We frown up producing multiple primary > >> artifacts for example trying to build both the client, server and > common > >> code from a single build. > > Again, if you could point me to an example, or maybe an area of code to > look at, that would help. I'm happy to record my findings in a > tutorial doc. > > > > > > > > > Ruel Loehr > > JBoss QA > > > > ----------------------------- > > 512-626-2782 > > Yahoo: ruelloehr > > Skype: ruelloehr > > AOL: dokoruel > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > -- jvz. Jason van Zyl jason at maven.org http://maven.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
