[
https://issues.apache.org/jira/browse/UIMA-2475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13472489#comment-13472489
]
Steven Bethard edited comment on UIMA-2475 at 10/9/12 3:59 PM:
---------------------------------------------------------------
Here's what worked for me:
(1) Fix a bug in the uimaj-eclipse-update-site/pom.xml
{code}
-
<outputDirectory>${project.build.directory}/work/plugins</outputDirectory>
+
<outputDirectory>${project.build.directory}/eclipse-update-site/plugins</outputDirectory>
{code}
(2) Run {{mvn process-sources}} to copy over features and plugins to
{{target/eclipse-update-site}}. (For some reason, the plugins directory has
svn:ignore set, so it's empty. Seems like there might be a bug where you're
putting both features and plugins in the features directory?)
(3) Run the FeaturesAndBundlesPublisher to publish the features and bundles and
add the content.xml and artifacts.xml
{code}
$ java -jar /.../eclipse/plugins/org.eclipse.equinox.launcher_*.jar \
-application org.eclipse.equinox.p2.publisher.FeaturesAndBundlesPublisher \
-metadataRepository file:/.../uimaj-eclipse-update-site/ \
-artifactRepository file:/.../uimaj-eclipse-update-site/ \
-source /.../uimaj-eclipse-update-site/target/eclipse-update-site \
-publishArtifacts
{code}
I am then able to use {{file:/.../uimaj-eclipse-update-site/}} as a p2
repository (e.g. Tycho can resolve dependencies from here).
was (Author: steven.bethard):
Here's what worked for me:
(1) Fix a bug in the uimaj-eclipse-update-site/pom.xml
{code}
-
<outputDirectory>${project.build.directory}/work/plugins</outputDirectory>
+
<outputDirectory>${project.build.directory}/eclipse-update-site/plugins</outputDirectory>
{code}
(2) Run {{mvn process-sources}} to copy over features and plugins to
{{target/eclipse-update-site}}. (For some reason, the plugins directory has
svn:ignore set, so it's empty. Seems like there might be a bug where you're
putting both features and plugins in the features directory?)
(3) Run the FeaturesAndBundlesPublisher to publish the features and bundles and
add the content.xml and artifacts.xml
{code}
$ java -jar /.../eclipse/plugins/org.eclipse.equinox.launcher_*.jar \
-application org.eclipse.equinox.p2.publisher.FeaturesAndBundlesPublisher \
-metadataRepository file:/.../uimaj-eclipse-update-site/ \
-artifactRepository file:/.../uimaj-eclipse-update-site/ \
-source /.../uimaj-eclipse-update-site/target/eclipse-update-site
-publishArtifacts
{code}
I am then able to use {{file:/.../uimaj-eclipse-update-site/}} as a p2
repository (e.g. Tycho can resolve dependencies from here).
> 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
>
> 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
