Mailing-List: contact dev-help@asterixdb.incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@asterixdb.incubator.apache.org
MIME-Version: 1.0
In-Reply-To: <B4B3B405-BD35-4CA9-91C8-5FE600E481B7@apache.org>
References: 
 <CAN_YF5zDS18qjfXstYoe7LC8REvUR+7sCxiUJ5NzW7qBvysirQ@mail.gmail.com>
 <CADGJP81Ntc7_RoGnnOC9dGtKut7f-8gbBC3d1k91UQRLYSJ9sg@mail.gmail.com>
 <CAN_YF5yEaOFP0srwcG9wr_rcUUi3++jWLSb+ukYbiCD9ejwGxw@mail.gmail.com>
 <B4B3B405-BD35-4CA9-91C8-5FE600E481B7@apache.org>
From: Ian Maxon <imaxon@uci.edu>
Date: Wed, 13 May 2015 02:57:35 -0700
Message-ID: 
 <CAN_YF5z0BZyUxvo=YwAjpNx_09onSert07KTHM7BUFhXcDZ96Q@mail.gmail.com>
Subject: Re: Switching Maven Repositories?
To: dev@asterixdb.incubator.apache.org
Content-Type: multipart/alternative; boundary=bcaec51b9adb259c320515f3a543

--bcaec51b9adb259c320515f3a543
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

RAT just checks that we use an Apache compatible license- which we do
already, however it's not the proper ASF license header. It still assigns
the copyright to the Regents, not the ASF.
For repackaging, I hope that Eclipse's or IntelliJ's refactoring
capabilities will do the trick, however I'm not at all certain. I think
you're right though that sed should just work, I think
s/edu.uci.ics/org.apache/g would cover 99.9% of the necessary changes.

- Ian

On Tue, May 12, 2015 at 8:33 PM, Till Westmann <tillw@apache.org> wrote:

> I think that there=E2=80=99s a tool that does that for you. And I think t=
hat it=E2=80=99s
> RAT, isn=E2=80=99t it?
> So then that should be easy.
> Do you know if there=E2=80=99s also a tool for repackaging?
> But actually, sed is probably fine as we probably don=E2=80=99t have a lo=
t of UCI
> dependencies that are not part of Hyracks.
> Is that right?
>
> Cheers,
> Till
>
>
> > On May 12, 2015, at 7:24 PM, Ian Maxon <imaxon@uci.edu> wrote:
> >
> > That all seems reasonable. Also agreed about it being part of the first
> > Apache release. Another thing along those lines that came to mind while
> > trying to get the RAT plugin to work is that we need to modify all of o=
ur
> > source headers too...
> >
> > - Ian
> >
> > On Tue, May 12, 2015 at 7:15 PM, Till Westmann <tillw@apache.org> wrote=
:
> >
> >> I think that we should. And I think that we should do it in the contex=
t
> of
> >> producing our first Apache-release.
> >>
> >> Maybe we can start by releasing the current Hyracks version?
> >>
> >> I think that there are a number of things that we need to do to be abl=
e
> to
> >> do that.
> >> One thing the comes to mind is the repackaging to org.apache.* package=
s.
> >> And then we'll need to make sure that our artifact conform to the
> release
> >> policy [1] (it also contains a link to a document that discusses the
> >> publishing of maven artifacts [2]).
> >>
> >> Does this make sense?
> >>
> >> Cheers,
> >> Till
> >>
> >> [1] http://www.apache.org/dev/release.html
> >> [2] http://www.apache.org/dev/publishing-maven-artifacts.html
> >>
> >>
> >>
> >>
> >> On Tue, May 12, 2015 at 6:49 PM, Ian Maxon <imaxon@uci.edu> wrote:
> >>
> >>> Hi all,
> >>> Right now we store our artifacts on a build server running Nexus (
> >>> obelix.ics.uci.edu). Should we instead now, be using an Apache
> >>> infrastructure provided repository for our Maven artifacts (releases,
> >> etc)?
> >>>
> >>> Thanks
> >>> - Ian
> >>>
> >>
>
>

--bcaec51b9adb259c320515f3a543--