Sounds OK to me. I have a branch for contract tests using Jena3, though I need to change the names to have the _CT ending on the suite class names. (or perhaps a _CS).
Are you available in the evenings EU time? I would like to chat with you online to see if we can come up with a strategy to make this all work cleanly. On Mon, Apr 27, 2015 at 10:57 AM, Bruno P. Kinoshita <[email protected]> wrote: > Not really. It contains some changes that would have to be undone before > merging with Jena 3. > > Maybe you could create a new branch for JENA-380, and we'll use it for > working on the issue. The old JENA-380 branch can be left there as > reference to what was done, and what should be avoided. > What do you think? > Bruno > > From: Claude Warren <[email protected]> > To: [email protected] > Sent: Monday, April 27, 2015 9:43 PM > Subject: Re: jena3 branch ready for merging into master > > Bruno, > > is branch JENA-380 now working against the jena3 package names? > > Claude > > > > On Mon, Apr 27, 2015 at 10:39 AM, Andy Seaborne <[email protected]> wrote: > > > On 26/04/15 22:33, Bruno P. Kinoshita wrote: > > > >> Andy > >> Would it be possible to set up a job in Jenkins pointing to a new branch > >> for JENA-380? > >> > >> We could fire it manually once to get the number of tests, and then > build > >> it with each commit to compare the number of tests and if any is broken. > >> > >> What do you think? > >> > > > > Sure - go ahead and add a job. Jenkins has no magic to get the code > (it's > > doign a read-only clone like any(thing|one) else). The only "magic" for > > Jenkins is that it can deploy artifacts to the Apache maven repos. > > > > Andy > > > > > > > >> Bruno > >> > >> From: Andy Seaborne <[email protected]> > >> To: [email protected] > >> Sent: Monday, April 27, 2015 5:57 AM > >> Subject: Re: jena3 branch ready for merging into master > >> > >> Jena3 is up and running and git cleaned up. > >> > >> Jenkins jobs running ; snapshots deployed. > >> > >> We have: > >> > >> Jena_Development_Test > >> Polls every 15 mins git for pushes and runs "mvn clean verify" > >> Jena_Development_Deploy > >> Runs daily to deploy new SNAPSHOTs if git has changed > >> Jena_Deploy_Jena2 > >> Runs weekly to deploy new SNAPSHOTs if branch "jena2" has changed > >> Jena_Development_Test_Windows > >> Runs daily, executes "mvn clean verify -Pdev" on Windows if changes > >> > >> > >> Andy > >> > >> > >> > >> On 26/04/15 11:43, Andy Seaborne wrote: > >> > >>> The master branch is now the Jena3 codebase. > >>> > >>> Branch jena2 for the old world. > >>> > >>> Now setting up the jenkins test and deployment jobs. > >>> > >>> Andy > >>> > >>> On 24/04/15 20:03, Andy Seaborne wrote: > >>> > >>>> OK - I'm about ready to put jena3 onto master. > >>>> > >>>> This is now the 24-48 (ish) hour slot for anyone who wants to inspect > >>>> the jena3 branch, which would be great. > >>>> > >>>> If you have something you really want to check and don't have time, > >>>> please say so. > >>>> > >>>> I'll check for any pushes to master and jena3, merging as necessary > then > >>>> merge jena3 back into master. > >>>> > >>>> ** Then master is jena3 and there is a jena2 branch. > >>>> > >>>> Andy > >>>> > >>> > >>> > >> > >> > >> > >> > >> > > > > > -- > I like: Like Like - The likeliest place on the web > <http://like-like.xenei.com> > LinkedIn: http://www.linkedin.com/in/claudewarren > > > > -- I like: Like Like - The likeliest place on the web <http://like-like.xenei.com> LinkedIn: http://www.linkedin.com/in/claudewarren
