Move -util.net / -util. criteria into -core?

[Cantor, Scott]

On 6/13/13 5:44 PM, "Brent Putman" <putmanb at georgetown.edu> wrote:
>
>I ported over the .net stuff there recently from v2, to deal with
>deficiencies in some of the java-support net classes.  I actually
>initially wanted to put them in java-support's net package.  The only
>reason I didn't was because I was trying to stick to the letter of the
>versioning and branching policy (Chad's), which would dictate that
>adding new API's means we need to branch the current java-support
>release, etc.  I just wasn't feeling like doing all that at the time,
>but did have plans to eventually move that code there.  I've since
>realized we've probably been violating that otherwise.  Since we can
>branch from a historical revision anyway, we should probably just go
>ahead and move that stuff to java-support.

I actually forgot that we did a release of that code, that's why I hadn't
branched it at all. I think the reason for doing the branch is that POMs
depending on 1.0-SNAPSHOT won't pick up the new APIs.

>The criteria stuff: to me clearly goes in java-support's .resolver
>package.  I think the only reason Chad didn't move it was b/c he thought
>that code was going away, which is why he marked as deprecated.  I
>didn't and don't have any current plans to get rid of it, so I'd say
>also move that stuff to java-support's .resolver package.

I forgot it was in two places, so that seems obvious, yes.

I'll take care of moving things, and will branch the 1.0.0 java-support
tag (and update trunk to 1.1-SNAPSHOT) if there's no objection.

-- Scott