Re: [uportal-dev] maven project structure for GAP

[Eric Dalquist]

Sounds good Dan. I'll go check out the GAP project so I can provide some more feedback as your work progresses. As always the IRC channel http://www.ja-sig.org/wiki/display/UPC/IRC+Channels is a great way for me at least to chat and help out with this stuff during the day. There are also a few more Maven experienced folks that are usually on there.

-Eric

Dan Ellentuck wrote:

Hi Eric,



    Dan

Eric Dalquist wrote:

I like your idea and will be working with it the next few days. Up to this point, I've just been working locally.

Any thoughts on these suggestions Dan?

-Eric

Eric Dalquist wrote:

I'd actually like to suggest a 3rd arrangement. The maven project structure I think would work best initially would be:

gap-parent
+-gap-api
+-gap-impl
+-gap-uPortal2-api





-Eric

Dan Ellentuck wrote:

I'm actually working on doing the api/impl split on person directory right now and I think that will open up some more options for making these services available to portlets and other applications. For GAP the -api module would contain all of the public APIs a GAPs client would need to use to access the system. Hopefully it would completely or mostly be interfaces and all of the implementation code and group service code ends up in -impl. I can provide some direct help doing this via the IRC channel, do you have a branch in SVN where this work is happening?

Hi Eric, et. al.,





    gap-full.jar (does not contain uportal2 api)
    gap-common.jar
    gap-groupsCore.jar
    gap-groupServices.jar
    gap-permissions.jar
    gap-uportal2-api.jar



    gap
      gap-core
      gap-uPortal2-api



Thanks for your help,

   Dan

I've spent quite a few hours experimenting with various maven project structures for GAP and have come up with 2 options: . a single project containing all the code, with a custom packaging phase to create the individual jars we want: . a parent project with 2 sub-projects, one for all of the org.jasig.gap code (with a custom packaging phase) and one for the uPortal2 api: I'd like your opinion. I suspect that a single project is clearest and easiest to work with, but using a parent project with 2 sub-projects removes the uPortal2 dependency from GAP, and this seems desirable.

smime.p7s
Description: S/MIME Cryptographic Signature