Re: [ease-dev] Oomph Setup failed

[Raphael Geissler <raphael.geissler@xxxxxxxxx>]

Hi Christian,

so I takes some time, but in the end I pushed the changes successful
to gerrit (https://git.eclipse.org/r/#/c/88456/).

One remark: One test is not running on my (Windows) machine, but seems
to run fine on the Hudson. Should I open a ticket for that?

Raphael

2017-01-11 8:12 GMT+01:00  <Christian.Pontesegger@xxxxxxxxxxxx>:
>>I added a new test plug-in, so I will add/change the pom files. Which
> command can I use to trigger a full build?
>
> Please use fragments instead of plugins for tests. Name it
> <original.plugin>.test. Then use the exact same package names as in the
> original plugin and create your test files for it. For a template see the
> o.e.ease.ui.test fragment.
> For each new plugin/fragment you create, please copy over the .settings
> folder from one of the other projects. It makes sure all code formatter
> settings and compile switches are the same for all projects. Test fragments
> should be located in the test folder of the git repo.
>
> The pom file for test plugins looks slightly different from normal plugins.
> Take one from another test plugin as template. Then locate the
> releng/pom.xml and scroll down to the test section around line 350. There
> you need to reference your test plugin.
>
> You can test it locally using maven and run
> Mvn clean install -p test
> In the root of the git repo.
>
> ... or you leave that to the automatic build that gets triggered on each
> push you do. That's what I typically do, so if you don't like there is no
> need to run maven locally.
> To simply execute your tests run your test class as an "eclipse plugin test"
> from the launch configuration or the context menu of the test file.
>
> Christian
>
> _______________________________________________
> ease-dev mailing list
> ease-dev@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or unsubscribe from this list, visit
> https://dev.eclipse.org/mailman/listinfo/ease-dev