[
https://issues.apache.org/jira/browse/UIMA-2475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steven Bethard updated UIMA-2475:
---------------------------------
Attachment: uimaj-eclipse-update-site.zip
Attached is the uimaj-eclipse-update-site after following the instructions I
gave above.
> what is our actual update site? The project
> itself or target/eclipse-update-site
In my setup, target/eclipse-update-site is the source for the
FeaturesAndBundlesPublisher, and the project itself is the final update site.
> Steven, I suppose that you only used
> dependencies defined in the manifest, right?
My connector dependencies (in the manifest) only depended on
org.apache.uima.runtime (of all the UIMA bundles) and looked like:
Require-Bundle: org.eclipse.core.resources;bundle-version="3.4.0",
org.eclipse.core.runtime;bundle-version="3.4.0",
org.eclipse.m2e.jdt;bundle-version="[1.0.0,2.0.0)",
org.eclipse.m2e.core;bundle-version="[1.0.0,2.0.0)",
org.eclipse.m2e.maven.runtime;bundle-version="[1.0.0,2.0.0)",
org.apache.uima.runtime;bundle-version="[2.4.0,3.0.0)"
> Why did you have to replace the output
> directory "/work/plugins"
This was crucial to get things working. Otherwise, only the features, and not
the plugins, are copied to target/eclipse-update-site. Consequently, when you
run FeaturesAndBundlesPublisher, it will only publish metadata for features and
not plugins, so even if you copy the plugins over later, the metadata will be
missing and Tycho won't be able to resolve any of the bundle dependencies.
Basically, you have to give FeaturesAndBundlesPublisher everything or it will
generate incomplete metadata. You can't copy stuff over later.
> I suppose that I also could have used
> UpdateSitePublisher
This definitely won't work - I got stuck by this several times. You have to use
FeaturesAndBundlesPublisher or you won't get the metadata. See my StackOverflow
question and the answers here:
http://stackoverflow.com/questions/12771851/getting-tycho-to-resolve-dependencies-from-old-style-eclipse-update-site
> org.eclipse.update.core.siteOptimizer
Note that this is deprecated in Eclipse 3.X, and doesn't even exist anymore in
Eclipse 4.X. So anything that depends on org.eclipse.update.core.siteOptimizer
probably needs to be rewritten since it's going to start failing as soon as
anyone downloads a newer Eclipse.
> we will have to think carefully about how
> this influences our current build process
> and the historical versions of the features.
Right. If you want to get all the correct metadata for all the old versions, I
think you'll have to run FeaturesAndBundlesPublisher on the complete repository
at www.apache.org/dist/uima/eclipse-update-site.
If you go the composite repository route, then as long as you run
FeaturesAndBundlesPublisher on each of the newer sub-repositories, and you keep
the list of repository children up to date, then I think the metadata should be
okay. But I've never worked with composite repositories personally, so I'm not
100% sure.
If you have a test repository you'd like me to try, point me at it, and I'll
see if Tycho resolves things for me from it.
> eclipse p2 update site instead of old-style update site
> -------------------------------------------------------
>
> Key: UIMA-2475
> URL: https://issues.apache.org/jira/browse/UIMA-2475
> Project: UIMA
> Issue Type: Bug
> Components: Eclipse plugins
> Reporter: Steven Bethard
> Assignee: Peter Klügl
> Attachments: uimaj-eclipse-update-site.zip
>
>
> The UIMA Eclipse update site (www.apache.org/dist/uima/eclipse-update-site)
> is an Eclipse 3.3 (or older) update site. Since Eclipse 3.4, the recommended
> update site layout is p2:
> http://wiki.eclipse.org/Equinox_p2_Getting_Started_for_Releng#Why_should_I_make_changes_to_adopt_p2.3F
> I've been bitten by this update site issue because old-style update sites
> make it impossible to resolve build-time dependencies when building Eclipse
> plugins:
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=380438#c3
> Could the UIMA update site be modernized to the p2 layout?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
