We faced the same issue and have taken similar approach as yours. We maintain a internal maven repository. I dont think maven related queries get enough attention on this forum.
-Shailesh Now Test Management <http://www.getzephyr.com> is a breeze. --- In [email protected], VELO <[EMAIL PROTECTED]> wrote: > > Hi, > > At work we are using maven for all, compile flex (thanks israfil), > compile java, build war and build ear. > > To build war we have a dependency to LCDS 2.5 flex.war > To compile java we have several dependencies to flex-*.jar > (flex-messaging.jar, flex-messaging-common.jar, depends of situation) > To compile flex we put charts, fds dependencies. > > We are using an internal name definition for the groupID and artifactID. > Have adobe made some oficial groupID/artifactID for maven users? > > Something like this: > http://maven.apache.org/guides/mini/guide-coping-with-sun-jars.html > > Or any planning for Coping with Adobe JARs/SWCs ? > > > VELO >
