| Re: [january-dev] Where to distribute forms? |
The new repo has been created so the forms branch on january should
now become the master branch on
https://github.com/eclipse/january-forms
Jay, would you like to resolve the build problem before or after we
migrate the code over?
Jonah
~~~
Jonah Graham
Kichwa Coders Ltd.
www.kichwacoders.com
On 18 April 2017 at 16:35, Jay Jay Billings <jayjaybillings@xxxxxxxxx> wrote:
> I got the following error, which is roughly equivalent to this:
> https://www.youtube.com/watch?v=BMkC_lKxrVo
>
> This is good progress though - I'll keep cracking at it and hopefully get
> some binaries out so we can finish the migration.
>
> Jay
>
> -----
>
> [ERROR] Failed to execute goal
> org.eclipse.tycho:tycho-surefire-plugin:0.24.0:test (default-test) on
> project org.eclipse.january.form.test: An unexpected error occured while
> launching the test runtime (return code 13). See log for details. -> [Help
> 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.eclipse.tycho:tycho-surefire-plugin:0.24.0:test (default-test) on
> project org.eclipse.january.form.test: An unexpected error occured while
> launching the test runtime (return code 13). See log for details.
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute( MojoExecutor.java:212)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute( MojoExecutor.java:153)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute( MojoExecutor.java:145)
> at
> org.apache.maven.lifecycle.internal. LifecycleModuleBuilder. buildProject( LifecycleModuleBuilder.java: 116)
> at
> org.apache.maven.lifecycle.internal. LifecycleModuleBuilder. buildProject( LifecycleModuleBuilder.java: 80)
> at
> org.apache.maven.lifecycle.internal.builder. singlethreaded. SingleThreadedBuilder.build( SingleThreadedBuilder.java:51)
> at
> org.apache.maven.lifecycle.internal.LifecycleStarter. execute(LifecycleStarter.java: 128)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java: 307)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java: 193)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:863)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:199)
> at sun.reflect.NativeMethodAccessorImpl. invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl. invoke( NativeMethodAccessorImpl.java: 57)
> at
> sun.reflect.DelegatingMethodAccessorImpl. invoke( DelegatingMethodAccessorImpl. java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher. launchEnhanced(Launcher.java: 289)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher. launch(Launcher.java:229)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher. mainWithExitCode(Launcher. java:415)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher. main(Launcher.java:356)
> Caused by: org.apache.maven.plugin.MojoFailureException: An unexpected error
> occured while launching the test runtime (return code 13). See log for
> details.
> at org.eclipse.tycho.surefire.TestMojo.runTest(TestMojo. java:958)
> at org.eclipse.tycho.surefire.TestMojo.execute(TestMojo. java:630)
> at
> org.apache.maven.plugin.DefaultBuildPluginManager. executeMojo( DefaultBuildPluginManager. java:134)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute( MojoExecutor.java:207)
> ... 20 more
> [ERROR]
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please
> read the following articles:
> [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/ MojoFailureException
> [ERROR]
> [ERROR] After correcting the problems, you can resume the build with the
> command
> [ERROR] mvn <goals> -rf :org.eclipse.january.form.test
> [DEBUG] Waiting for process to finish
> [DEBUG] Result: 1
>
>
> On Tue, Apr 18, 2017 at 4:25 AM, Jonah Graham <jonah@xxxxxxxxxxxxxxxx>
> wrote:
>>
>> Hi Jay,
>>
>> It looks good to me. Fire when ready.
>>
>> I have put in request for january-forms repo on GitHub:
>> https://bugs.eclipse.org/bugs/show_bug.cgi?id=515364
>>
>> Jonah
>>
>> ~~~
>> Jonah Graham
>> Kichwa Coders Ltd.
>> www.kichwacoders.com
>>
>>
>> On 17 April 2017 at 20:51, Jay Jay Billings <jayjaybillings@xxxxxxxxx>
>> wrote:
>> > Okay, I've got this ready. I'll press the build button tomorrow morning,
>> > so
>> > everyone be ready for (hopefully no) fireworks then.
>> >
>> > Jay
>> >
>> > On Fri, Apr 14, 2017 at 12:51 PM, Jonah Graham <jonah@xxxxxxxxxxxxxxxx>
>> > wrote:
>> >>
>> >> Start by duplicating the january-master job, calling it something like
>> >> january-forms. If you update, in that new config, every location that
>> >> it
>> >> says master with forms you will get a build that publishes a p2 site
>> >> automatically as documented in the job description.
>> >>
>> >> I can't recall if the tests repo is checked out on january-master, IIRC
>> >> it
>> >> is just a disabled pre-build step.
>> >>
>> >> When it comes to releases we will somehow create a combined repo, most
>> >> likely with p2's composite feature. We can create a composite repo for
>> >> latest master + latest forms too.
>> >>
>> >> Jonah
>> >>
>> >> On 14 Apr 2017 4:31 p.m., "Jay Jay Billings" <jayjaybillings@xxxxxxxxx>
>> >> wrote:
>> >>
>> >> Everyone,
>> >>
>> >> Now that the Forms code has been merged into its branch, I would like
>> >> to
>> >> get the build going so that we can move ICE and EAVP to use it as soon
>> >> as
>> >> possible. I don't want to mess up the existing p2 repo for data sets
>> >> though,
>> >> so what is the preferred way to distribute the forms p2 repo?
>> >>
>> >> I was thinking that I would just set it up so that Hudson dumps it to a
>> >> forms/ subdirectory in the main download directory.
>> >>
>> >> Jay
>> >>
>> >> _______________________________________________
>> >> january-dev mailing list
>> >> january-dev@xxxxxxxxxxx
>> >> To change your delivery options, retrieve your password, or unsubscribe
>> >> from this list, visit
>> >> https://dev.eclipse.org/mailman/listinfo/january-dev
>> >>
>> >>
>> >>
>> >> _______________________________________________
>> >> january-dev mailing list
>> >> january-dev@xxxxxxxxxxx
>> >> To change your delivery options, retrieve your password, or unsubscribe
>> >> from this list, visit
>> >> https://dev.eclipse.org/mailman/listinfo/january-dev
>> >>
>> >
>> >
>> >
>> > --
>> > Jay Jay Billings
>> > Oak Ridge National Laboratory
>> > Twitter Handle: @jayjaybillings
>> >
>> > _______________________________________________
>> > january-dev mailing list
>> > january-dev@xxxxxxxxxxx
>> > To change your delivery options, retrieve your password, or unsubscribe
>> > from
>> > this list, visit
>> > https://dev.eclipse.org/mailman/listinfo/january-dev
>> >
>> _______________________________________________
>> january-dev mailing list
>> january-dev@xxxxxxxxxxx
>> To change your delivery options, retrieve your password, or unsubscribe
>> from this list, visit
>> https://dev.eclipse.org/mailman/listinfo/january-dev
>
>
>
>
> --
> Jay Jay Billings
> Oak Ridge National Laboratory
> Twitter Handle: @jayjaybillings
>
> _______________________________________________
> january-dev mailing list
> january-dev@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or unsubscribe from
> this list, visit
> https://dev.eclipse.org/mailman/listinfo/january-dev
>
_______________________________________________
january-dev mailing list
january-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/january-dev