[eclipse-poky] [PATCH 00/23] Enable maven build system
Tim Orling
timothy.t.orling at linux.intel.com
Mon Feb 12 11:20:28 PST 2018
> On Feb 12, 2018, at 10:57 AM, Lewis, ScottX <scottx.lewis at intel.com> wrote:
>
> Hi Tim,
>
> I was just trying out the github repo at: https://github.com/crops/eclipse-poky
>
> I'm able to pull, import, set target and build fine. I created a branch (just to try out and test the process) called slewis/projectsetfile ...that includes changes to the existing project set files (to point to master instead of timo/maven at eclipse-poky-contrib), and adds a new project set file: github-pokywithrse.psf in with the other project set files...so just non-source/dev stuff for this test.
>
> Created and committed to local branch slewis/projectsetfile, but can't push as it gives error (for user scottslewis @ github): Can't connect to any URI: https://github.com/crops/eclipse-poky.git (https://github.com/crops/eclipse-poky.git: git-receive-pack not permitted on 'https://github.com/crops/eclipse-poky.git’
Fork GitHub/crops/eclipse-poky and set it as a different remote:
‘git remote add GitHub <your ssh url for github>’
push to that remote:
‘git push github’
>
> Is this a permissions error for https://github.com/crops/eclipse-poky.git?
No one has permission to push to github/crops/eclipse-poky, it is only a mirror of yp.org/eclipse-poky. Instead, fork github/crops/eclipse-poky and create a pull request from your personal GitHub account to github/eclipse-poky “master”. That should kick off a Travis CI build. I can then create a mailing list patch bomb from your branch/PR.
>
> What I was planning to do was to push new slewis/projectsetfile branch to this github repo, and then submit a pull request...which I think will trigger travis builder. I know I can also create branch at eclipse-poky-contrib but I wanted to try this path first.
>
Just push to your personal GitHub repo, not github/crops/eclipse-poky and post the link to it here.
> Thanks for any info/help.
>
> Scott
>
>
> -----Original Message-----
> From: eclipse-poky-bounces at yoctoproject.org [mailto:eclipse-poky-bounces at yoctoproject.org] On Behalf Of Tim Orling
> Sent: Sunday, February 11, 2018 4:43 PM
> To: Tim Orling <timothy.t.orling at linux.intel.com>
> Cc: Scott Lewis <slewis at composent.com>; eclipse-poky at yoctoproject.org
> Subject: Re: [eclipse-poky] [PATCH 00/23] Enable maven build system
>
> Merged to eclipse-poky/master and eclipse-poky-contrib/master and auto synced to github/crops/eclipse-poky
>
> Travis build is automatically triggered by the merge and is at:
> https://travis-ci.org/crops/eclipse-poky/builds/340296657
>
> The merge window is now open for new development on master.
>
> Preferably maintain your work on feature branches on eclipse-poky-contrib or GitHub. And announce progress on this mailing list. Pull requests on Github will automatically trigger a Travis CI build for any branch that has a .travis.yml (such as anything based on today’s master). Please add tests if that makes sense and you know how.
>
> Patches must be sent to this mailing list before merge, but we can work through that process one way or another. There already exists recommended tooling for creating patchsets [1] and sending them to mailing list [2].
>
> Please announce any already staged work as soon as you can.
>
> —Tim
>
> [1] http://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/scripts/create-pull-request
> [2] http://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/scripts/send-pull-request
>
>
>> On Feb 8, 2018, at 11:17 PM, Tim Orling <timothy.t.orling at linux.intel.com> wrote:
>>
>> The shell scripts (scripts/setup.sh and scripts/build.sh) are hard to
>> maintain and very different from how most Eclipse Foundation projects
>> are built. The most commonly used build system is an Eclipse tool
>> called "Tycho" which is a series of plugins for "maven".
>>
>> From our experiences with eclipse-crops, we know that "maven" can be
>> easily run on cloud CI (Travis CI or AppVeyor for instance), the
>> command line and within the Eclipse IDE for the plugin developer. In
>> addition, the UI test framework RCPTT is known to be easily integrated
>> with maven so that the UI tests are run with the build. Implementation
>> of the maven build system on AutoBuilder is in active development and
>> will be ready well before our 2.6 M1 target date for the new plugin transition.
>>
>> The following changes since commit fbb91e5c5ad06470cd50ce1daa407a5f7d13c6ca:
>>
>> org.yocto.sdk.remotetools: remove YoctoBSPWizard java classes
>> (2018-02-07 07:53:14 -0800)
>>
>> are available in the git repository at:
>>
>> git://push.yoctoproject.org/eclipse-poky-contrib timo/maven
>>
>> Scott Lewis (4):
>> Added org.yocto.sdk.releng project in releng directory Removed
>> references to RSE Addtions and small changes to .target, .psf and
>> added prefs files Update to pokywithrse.target file to eliminate
>> unnecessary
>> dependencies
>>
>> Tim Orling (19):
>> Add initial pom files for parent and releng/target Add README.maven
>> to document usage, tips and tricks Add org.yocto.sdk.ide maven
>> support Add org.yocto.sdk.ide.doc.user maven support Add
>> org.yocto.cmake.managedbuilder maven support Add
>> org.yocto.remote-utils maven support Add org.yocto.sdk.remotetools
>> maven support Add org.yocto.doc.user maven support Add initial
>> .travis.yml for TravisCI integration Add initial AppVeyor CI
>> integration Add org.yocto.sdk.feature.group maven support Add
>> org.yocto.utilities.feature.group maven support Add
>> org.yocto.doc.feature.group maven support
>> .travis.yaml: add dependencies to build docs Copy
>> targets/pokywithrse.target to releng/poky.target
>> org.yocto.sdk.releng: change target to be pokywithrse
>> org.yocto.sdk.releng: move poky.target to root of project
>> README.dev: minor changes
>> README.dev: add m2e/Tycho content
>>
>> .gitignore | 17 +
>> .project | 17 +
>> .settings/org.eclipse.m2e.core.prefs | 4 +
>> .travis.yml | 30 ++
>> README.dev | 152 ++++++
>> README.maven | 43 ++
>> appveyor.yml | 31 ++
>> features/org.yocto.doc/.project | 6 +
>> .../.settings/org.eclipse.m2e.core.prefs | 4 +
>> features/org.yocto.doc/pom.xml | 14 +
>> features/org.yocto.sdk/.project | 6 +
>> .../.settings/org.eclipse.m2e.core.prefs | 4 +
>> features/org.yocto.sdk/feature.xml | 3 +-
>> features/org.yocto.sdk/pom.xml | 14 +
>> features/org.yocto.utils/.project | 23 +
>> .../.settings/org.eclipse.m2e.core.prefs | 4 +
>> features/org.yocto.utils/pom.xml | 14 +
>> plugins/org.yocto.bc.ui/META-INF/MANIFEST.MF | 6 +-
>> .../src/org/yocto/bc/bitbake/ShellSession.java | 2 -
>> .../yocto/bc/ui/filesystem/CustomLocalFile.java | 14 -
>> .../yocto/bc/ui/wizards/install/InstallWizard.java | 115 +----
>> plugins/org.yocto.cmake.managedbuilder/.classpath | 2 +-
>> plugins/org.yocto.cmake.managedbuilder/.project | 6 +
>> .../.settings/org.eclipse.m2e.core.prefs | 4 +
>> plugins/org.yocto.cmake.managedbuilder/pom.xml | 14 +
>> plugins/org.yocto.doc.user/.classpath | 2 +-
>> plugins/org.yocto.doc.user/.project | 6 +
>> .../.settings/org.eclipse.jdt.core.prefs | 7 +
>> .../.settings/org.eclipse.m2e.core.prefs | 4 +
>> plugins/org.yocto.doc.user/pom.xml | 61 +++
>> plugins/org.yocto.remote.utils/.classpath | 2 +-
>> plugins/org.yocto.remote.utils/.project | 6 +
>> .../.settings/org.eclipse.m2e.core.prefs | 4 +
>> plugins/org.yocto.remote.utils/pom.xml | 14 +
>> plugins/org.yocto.sdk.ide.doc.user/.classpath | 2 +-
>> plugins/org.yocto.sdk.ide.doc.user/.project | 6 +
>> .../.settings/org.eclipse.m2e.core.prefs | 4 +
>> plugins/org.yocto.sdk.ide.doc.user/pom.xml | 14 +
>> plugins/org.yocto.sdk.ide/.classpath | 2 +-
>> plugins/org.yocto.sdk.ide/.project | 6 +
>> .../.settings/org.eclipse.m2e.core.prefs | 4 +
>> plugins/org.yocto.sdk.ide/pom.xml | 14 +
>> plugins/org.yocto.sdk.remotetools/.classpath | 6 +-
>> plugins/org.yocto.sdk.remotetools/.project | 6 +
>> .../.settings/org.eclipse.m2e.core.prefs | 4 +
>> .../.settings/org.eclipse.core.resources.prefs | 2 +
>> plugins/org.yocto.sdk.remotetools/pom.xml | 14 +
>> pom.xml | 573 +++++++++++++++++++++
>> releng/org.yocto.sdk.releng/.classpath | 7 +
>> releng/org.yocto.sdk.releng/.project | 34 ++
>> .../.settings/org.eclipse.jdt.core.prefs | 7 +
>> .../.settings/org.eclipse.m2e.core.prefs | 4 +
>> releng/org.yocto.sdk.releng/META-INF/MANIFEST.MF | 7 +
>> releng/org.yocto.sdk.releng/build.properties | 4 +
>> releng/org.yocto.sdk.releng/launches/poky.launch | 29 ++
>> releng/org.yocto.sdk.releng/poky.target | 66 +++
>> releng/org.yocto.sdk.releng/pokywithrse.target | 85 +++
>> releng/org.yocto.sdk.releng/pom.xml | 45 ++
>> releng/org.yocto.sdk.releng/projectsets/poky.psf | 25 +
>> .../projectsets/pokywithrse.psf | 29 ++
>> releng/org.yocto.sdk.releng/src/empty.txt | 0
>> 61 files changed, 1510 insertions(+), 144 deletions(-) create mode
>> 100644 .project create mode 100644
>> .settings/org.eclipse.m2e.core.prefs
>> create mode 100755 .travis.yml
>> create mode 100644 README.dev
>> create mode 100644 README.maven
>> create mode 100755 appveyor.yml
>> create mode 100644
>> features/org.yocto.doc/.settings/org.eclipse.m2e.core.prefs
>> create mode 100755 features/org.yocto.doc/pom.xml create mode 100644
>> features/org.yocto.sdk/.settings/org.eclipse.m2e.core.prefs
>> create mode 100755 features/org.yocto.sdk/pom.xml create mode 100644
>> features/org.yocto.utils/.project create mode 100644
>> features/org.yocto.utils/.settings/org.eclipse.m2e.core.prefs
>> create mode 100755 features/org.yocto.utils/pom.xml delete mode 100644
>> plugins/org.yocto.bc.ui/src/org/yocto/bc/ui/filesystem/CustomLocalFile
>> .java create mode 100644
>> plugins/org.yocto.cmake.managedbuilder/.settings/org.eclipse.m2e.core.
>> prefs create mode 100755
>> plugins/org.yocto.cmake.managedbuilder/pom.xml
>> create mode 100644
>> plugins/org.yocto.doc.user/.settings/org.eclipse.jdt.core.prefs
>> create mode 100644
>> plugins/org.yocto.doc.user/.settings/org.eclipse.m2e.core.prefs
>> create mode 100755 plugins/org.yocto.doc.user/pom.xml
>> create mode 100644
>> plugins/org.yocto.remote.utils/.settings/org.eclipse.m2e.core.prefs
>> create mode 100755 plugins/org.yocto.remote.utils/pom.xml
>> create mode 100644
>> plugins/org.yocto.sdk.ide.doc.user/.settings/org.eclipse.m2e.core.pref
>> s create mode 100755 plugins/org.yocto.sdk.ide.doc.user/pom.xml
>> create mode 100644
>> plugins/org.yocto.sdk.ide/.settings/org.eclipse.m2e.core.prefs
>> create mode 100755 plugins/org.yocto.sdk.ide/pom.xml create mode
>> 100644
>> plugins/org.yocto.sdk.remotetools/.settings/org.eclipse.m2e.core.prefs
>> create mode 100644
>> plugins/org.yocto.sdk.remotetools/META-INF/maven/com.googlecode.json-s
>> imple/json-simple/.settings/org.eclipse.core.resources.prefs
>> create mode 100755 plugins/org.yocto.sdk.remotetools/pom.xml
>> create mode 100755 pom.xml
>> create mode 100644 releng/org.yocto.sdk.releng/.classpath
>> create mode 100644 releng/org.yocto.sdk.releng/.project
>> create mode 100644
>> releng/org.yocto.sdk.releng/.settings/org.eclipse.jdt.core.prefs
>> create mode 100644
>> releng/org.yocto.sdk.releng/.settings/org.eclipse.m2e.core.prefs
>> create mode 100644 releng/org.yocto.sdk.releng/META-INF/MANIFEST.MF
>> create mode 100644 releng/org.yocto.sdk.releng/build.properties
>> create mode 100644 releng/org.yocto.sdk.releng/launches/poky.launch
>> create mode 100644 releng/org.yocto.sdk.releng/poky.target
>> create mode 100644 releng/org.yocto.sdk.releng/pokywithrse.target
>> create mode 100755 releng/org.yocto.sdk.releng/pom.xml
>> create mode 100644 releng/org.yocto.sdk.releng/projectsets/poky.psf
>> create mode 100644
>> releng/org.yocto.sdk.releng/projectsets/pokywithrse.psf
>> create mode 100644 releng/org.yocto.sdk.releng/src/empty.txt
>>
>> --
>> 2.13.6
>>
>
> _______________________________________________
> eclipse-poky mailing list
> eclipse-poky at yoctoproject.org
> https://lists.yoctoproject.org/listinfo/eclipse-poky
More information about the eclipse-yocto
mailing list