I can't duplicate the error. I did the same on fedora-client master:
rm -rf ~/.m2/repository/org/kathrynhuxtable && mvn compile
and I see wagon-gitsite-0.3.1a download, and the build is successful.
It shouldn't be that the DuraSpace repo needs to be listed in both places: that
would defe
The logging stuff is working now.
Also, on the trippi maven branch, if I "rm -rf
~/.m2/repository/org/kathrynhuxtable && mvn compile", things work fine (and
the 0.3.1a artifact is downloaded locally).
However, if I run the exact same commands as above on the latest rev of the
fedora-client master
Well, I pushed 0.3.1a to the DuraSpace third-party repo for now and added it as
a plugin repo to both trippi and fedora-client. I can push to gh-pages with the
vanilla 0.3.1, but the site gets fubared.
If the logging related changes I pushed earlier today aren't helping your
build/tests I'll ba
On Sun, Feb 12, 2012 at 4:01 AM, Edwin Shin wrote:
> Maybe I'll just stick a release of 0.4-SNAPSHOT on the DuraSpace m2 repo
> for now. I still can't get wagon-gitsite to work with the last released
> version anymore.
>
Weird that 0.3.1 seems to have worked for me on fcrepo-misc. Anyway,
long-te
Maybe I'll just stick a release of 0.4-SNAPSHOT on the DuraSpace m2 repo for
now. I still can't get wagon-gitsite to work with the last released version
anymore.
The tests all pass for me and I'm not seeing classpath wonkiness.
But, regarding log classpath wonkiness--I was having problems getti
