Hi Mark,
As far as I'm aware, if we actually modified a dependency, it should be
in our DSpace GitHub.com acct (e.g. dspace-solr, or
dspace-cocoon-servlet-service-impl are examples where we released a
modified version of a dependency):
https://github.com/DSpace
Since I don't see a repo for "j
On Fri, Dec 20, 2013 at 07:26:04PM -0500, Mark H. Wood wrote:
> It looks as though the jmockit team posted their 0.999.4 to Maven
> Central about a month after DSpace posted its own. If there's no
> difference, we can (and IMHO should) scrap ours and use theirs
> (mockit:jmockit:0.999.4). We migh
The reason I've been seeing these dependency issues is that I'm trying
to make the declared dependencies more nearly match the code. After
that, I think that the start of a major release cycle is the proper
time to review the versions of dependencies and tools. But first I'd
like to weed out unus
Sure, that's what we should do.
On Dec 21, 2013 5:04 PM, "Pottinger, Hardy J."
wrote:
> Ok, then, how about we update master but don't backport to the 4.x
> branch?
>
> --Hardy
>
> Sent from my iPad
>
> On Dec 21, 2013, at 8:59 AM, "helix84" wrote:
>
> Certainly not 4.1, that is a bugfix-on
Ok, then, how about we update master but don't backport to the 4.x branch?
--Hardy
Sent from my iPad
On Dec 21, 2013, at 8:59 AM, "helix84"
mailto:heli...@centrum.sk>> wrote:
Certainly not 4.1, that is a bugfix-only release. We don't want risk that our
dependencies change behaviour when we d
Certainly not 4.1, that is a bugfix-only release. We don't want risk that
our dependencies change behaviour when we don't expect it to change. That
might even discourage people to upgrade, defeating thw purpose of bugfix
releases. For 5.0 - sure.
On Dec 21, 2013 3:14 AM, "Pottinger, Hardy J."
wro
I wonder if it would be "ok" to update all of our dependency versions as part
of 4.1? Assuming there *is* a 4.1.
--Hardy
Sent from my iPad
> On Dec 20, 2013, at 6:26 PM, "Mark H. Wood" wrote:
>
> It looks as though the jmockit team posted their 0.999.4 to Maven
> Central about a month after D
It looks as though the jmockit team posted their 0.999.4 to Maven
Central about a month after DSpace posted its own. If there's no
difference, we can (and IMHO should) scrap ours and use theirs
(mockit:jmockit:0.999.4). We might even want to upgrade to
com.googlecode.jmockit:jmockit:1.5 or so.
W
