Created attachment 1251910 [details]
build.log

Created attachment 1251911 [details]
root.log

Created attachment 1251912 [details]
state.log

This bug appears to have been reported against 'rawhide' during the Fedora 26 development cycle.
Changing version to '26'.

*** Bug 1331185 has been marked as a duplicate of this bug. ***

I've been trying to build a new version, however the eclipse plugin guidelines appear to be out of date. They haven't been updated much in over 5 years, and they do not work any more.

https://fedoraproject.org/wiki/Packaging:EclipsePlugins


I'm blocked on this until I can get some help with how to build plugins now.

Eclipse plugins are built with maven these days, so I mostly recommend using the normal java guidelines. Usually the only thing extra you need is to add a BR on tycho (special maven extensions for building Eclipse plugins)

As always, there are plenty of good examples in existing spec files. Here are a couple of simpler eclipse plugin packages that might be instructive:

http://pkgs.fedoraproject.org/cgit/rpms/eclipse-egit-github.git/tree/eclipse-egit-github.spec

http://pkgs.fedoraproject.org/cgit/rpms/eclipse-emf-validation.git/tree/eclipse-emf-validation.spec

Don't hesitate to ask if you have any more specific questions :-)

I had spent some time looking, and it seemed like the tycho/maven builds required a bit of metadata in the source itself, which this plugin doesn't seem to have. Would I have to manually create this?

It's been years since I've touched this stuff, and the plugin source/community doesn't seem to be all that big on documenting build steps, so I'm just throwing darts in the dark here.

I just took a look at the upstream and yeah, no "pom.xml" files for a maven build.

Fortunately we have a tool to generate poms automatically for Eclipse plug-in projects, provided by tycho.

For example, see this spec file:

http://pkgs.fedoraproject.org/cgit/rpms/eclipse-epic.git/tree/eclipse-epic.spec#n63

Where we invoke the generate-poms goal of the tycho-pomgenerator-plugin maven plugin.

Thanks, I'll take a look at that.

In the mean time, could something be done about the existing packaging guidelines? They reference a tool (pdebuild) that doesn't seem to exist any more. I couldn't find it anywhere.

(In reply to Jesse Keating from comment #10)
> Thanks, I'll take a look at that.
> 
> In the mean time, could something be done about the existing packaging
> guidelines? They reference a tool (pdebuild) that doesn't seem to exist any
> more. I couldn't find it anywhere.

Sure, I'll bump the priority of doing that. It's been on my to-do list for a while, but the audience for it for a long time was just me :-)

PDEBuild was deprecated and removed a while ago; packaging Eclipse plug-in should in theory now be as "easy" as packaging any other Java project.

This message is a reminder that Fedora 26 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 26. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '26'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 26 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Fedora 26 changed to end-of-life (EOL) status on 2018-05-29. Fedora 26
is no longer maintained, which means that it will not receive any
further security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.