Right. The question is whether we should consider also putting the pom metatype information along with the jar files in the repository and if that would be useful.
In certain "controlled" environments Maven might be configured with a specific set of remote repositories so that the artifacts are always pulled from the right locations (therefore having a good control over the what versions of the artifacts or snapshots are used). Jarek On Tue, Sep 20, 2011 at 1:37 PM, Forrest Xia <[email protected]> wrote: > GERONIMO_HOME/repository as a remote repository? I think > GERONIMO_HOME/repository is lack of maven repo metadata information, doubt > if it could be a remote repository. > > On the other hand, if there are snapshot dependencies in user's and geronimo > project, maven will always pull something newest from online, that will > cause the intent of using exact same binaries failed to achieve. > > Just a cent for discussion. > > Forrest > > On Wed, Sep 21, 2011 at 1:14 AM, Jarek Gawor <[email protected]> wrote: >> >> Hi, >> >> I'm curious about using $GERONIMO_HOME/repository as remote Maven >> repository. We are not very religious (or at least we haven't been in >> the past) about publishing snapshots of Geronimo (and other related) >> code. So if somebody wants to build their own code against the same >> exact versions of the dependencies as their Geronimo binary (snapshot) >> uses that can be very difficult. So what about using >> $GERONIMO_HOME/repository directly as a Maven repository? Would that >> work (if we put the pom files in the repository/ dir? Especially for >> snapshot dependencies? >> >> Thanks, >> Jarek > >
