[
https://issues.apache.org/jira/browse/UIMA-3501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marshall Schor resolved UIMA-3501.
----------------------------------
Resolution: Fixed
> Eclipse update site build fails without "clean" sometimes
> ---------------------------------------------------------
>
> Key: UIMA-3501
> URL: https://issues.apache.org/jira/browse/UIMA-3501
> Project: UIMA
> Issue Type: Improvement
> Components: Build, Packaging and Test
> Affects Versions: parent-pom-7
> Reporter: Marshall Schor
> Assignee: Marshall Schor
> Priority: Minor
> Fix For: parent-pom-8
>
>
> If you run the eclipse-update-site build 2x, not in -Papache-release mode, it
> doesn't clear out the target eclipse-update-site/subsite (on purpose - to
> avoid getting the older versions of things, in case you're testing that...).
> The step where it runs the Eclipse FeaturesAndBundlesPublisher seems to
> notice that older versions of things are in the target repository, with the
> same version #s, and it won't update them. But it doesn't report any issues.
> So if you forget to do "mvn clean install" and just do "mvn install" it
> looks like it makes an updated site, but actually, it doesn't...
> Fix this with a silly workaround (because I don't know how else to do it in
> Ant): have the FeaturesAndBundlesPublisher write to a temp directory, which
> is always erased just before it runs, and then have another ant step copy
> these over the older ones.
> * tried this, and many other variations; couldn't get them to work. It
> seems the features & bundles publisher does some kind of fancy reading of the
> xml in the artifacts.xml and contents.xml and uses that information rather
> than seeing what files are actually there. So, do something simpler and more
> fail-safe.
--
This message was sent by Atlassian JIRA
(v6.1.4#6159)
