mahout-core is the one that I am seeing the problem with. On Sun, Sep 19, 2010 at 6:25 PM, Benson Margulies <[email protected]>wrote:
> It's not so easy to make maven make the names collide. > > What module builds the job jar? > > On Sun, Sep 19, 2010 at 8:40 PM, Ted Dunning <[email protected]> > wrote: > > It looks to me like we have a problem publishing our snapshots to the > apache > > repo. > > > > When I look here > > > https://repository.apache.org/index.html#nexus-search;gav~org.apache.mahout~mahout-core~~~~kw,versionexpand > > > > I see that we have a mahout-core test jar for 0.4-SNAPSHOT the seems all > in > > order. In addition, we have what purports to be the mahout-core jar > itself, > > but > > in fact is the job file. > > > > This means that if I point at this repository from a maven build on a > > machine that hasn't had mahout installed on it, I get an unsatisfied > > external reference. If I compile and install mahout from source on that > > machine, the dependency is satisfied. I never noticed this until > > now because machines I was always compiling on had a version of mahout > > compiled and installed already. > > > > I think that the problem is that the job jar name collides with that of > the > > actual jar so that the job jar overwrites the ordinary jar. > > > > Is this correct? > > > > Can we rename the job jar to avoid this? > > > > If this is correct, then I expect the same problem to manifest for the > > examples. > > >
