> -----Original Message-----
> From: Rob Moore [mailto:[EMAIL PROTECTED]
> Sent: Thursday, January 15, 2004 12:29 PM
> To: Maven Users List
> Subject: Re: single artifact mantra and ejb projects
> 
> Sonnek, Ryan wrote:
> 
> > You have to make sure all the properties files contain no extra space
> after
> > the value.  Clear those out and you won't have a problem (ie: change
> > maven.multiproject.type=jar_ to maven.multiproject.type=jar).
> 
> D'oh! I forgot about checking the maven.multiproject.type line for a
> trailing space. Sorry about that...
> 
> >
> > The jboss plugin is version 1.2b4 because the final 1.2 module is not on
> > ibiblio.  I've put in a JIRA request for it to be uploaded, but it
> hasn't
> > been done yet.  I don't know if there was a reason it was not put on
> > ibiblio, or if it was just accidentally overlooked.
> 
> Ah, yes. I set up my own repository just for that reason.
> 
> >
> > If I knew how to attach a zip file of the sample to the wiki I certainly
> > would!  I have never done that before, so if there's a way, let me know
> and
> > I'll put it up there.
> 
> Down at the very bottom of the page is an action called "Attach File".
> Easy to miss.
> 
> >
> > The eclipse dependency is used to "map" the EJB classes to their
> interfaces.
> > In my example, I package the EJB interfaces and Data Objects (or value
> > objects), into the ejb-client.  IMO, this is the easiest way for 3rd
> party
> > apps to gain access to your application.  They only need this one jar
> file
> > and they're good to go.  Because the data objects are in the ejb-client
> > subproject, and the data objects are used within the signatures of the
> ejb
> > java code, there is a dependency between the two.  You'll notice that in
> the
> > ejb's maven.xml, I intentionally delete the interfaces and data objects
> > after they are generated to avoid duplicate classes existing.
> 
> Okay, so the Java files that are used by the EJB project are really in
> the client project. In other words, these 'shared' files don't live in
> the parent project at all. Is that correct?

Right on.  I wouldn't really call the EJB project the "parent", but yes, the
interfaces and data classes ONLY exist in the ejb-client project.  

> 
> Thanks again,
> 
> Rob
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to