That is true, but the way the repository is setup is that it will only download them if they are actually requested - so them missing from features/ and plugin/ is implying there never have been requested. That would be correct since I haven't manually installed the visible 1.1.1 release since I'm trying to fix 'check for updates' to work.
So with the artifacts.xml and content.xml sorted, it should be all proper. Here are some screenshots of what Eclipse is seeing:
![](pnggJz4yNRmNX.png)
![](pngOo6gTWykwm.png)
![](pngM8bANtOVbl.png)
> However the features/ and plugin/ folders only list the jars for the
> previous (and currently installed) version 1.1.0. I'm not entirely
> certain if this is a problem as I don't know the p2 layout yet and
> it is setup in a bit of a complicated fashion using maven, nexus,
> and proxied repositories.
Do you mean that the jars for the new version are not present in the repository? That would be a problem and could explain why the update isn’t being detected...
Do you have a matching feature that wraps this plugin, is already installed and there is a new version in the repo to go along with the new version of the plugin? The install and update wizards in Eclipse only display and process features. The p2 command line utilities can handle stand-alone bundles as well.
Yep, the plugin is wrapped in a feature and is available in the repo (as far as I can tell[1] - I'm new to this).
[1] - I upped the version number on the feature and the plugin and deployed them. artifacts.xml in my repository correctly lists the new feature and plugin:
<artifact id="au.gov.nehta.mdht.uml.cda.feature" classifier="org.eclipse.update.feature" version="1.1.1">
<property name="artifact.size" value="4920"/>
<property name="download.size" value="4920"/>
<property name="download.md5" value="7bd8ad8f6266eb4cee4ee4a05992ead4"/>
<property name="repositoryPath" value="au/gov/nehta/mdht/features/au.gov.nehta.mdht.uml.cda.feature/1.1.1/au.gov.nehta.mdht.uml.cda.feature-1.1.1.jar"/>
</artifact>
<artifact id="au.gov.nehta.mdht.uml.cda.ui" classifier="osgi.bundle" version="1.1.1">
<properties size="4">
<property name="artifact.size" value="20079"/>
<property name="download.size" value="20079"/>
<property name="download.md5" value="fd6b9811b5f0259749abbf403daf086e"/>
<property name="repositoryPath" value="au/gov/nehta/mdht/plugins/au.gov.nehta.mdht.uml.cda.ui/1.1.1/au.gov.nehta.mdht.uml.cda.ui-1.1.1.jar"/>
</properties>
</artifact>
So does content.xml:
<unit id="au.gov.nehta.mdht.uml.cda.feature.feature.group" singleton="false" version="1.1.1">...</unit>
<unit id="au.gov.nehta.mdht.uml.cda.feature.source.feature.group" singleton="false" version="1.1.1">...</unit>
<unit id="au.gov.nehta.mdht.uml.cda.feature.feature.jar" version="1.1.1">...</unit>
<unit id="au.gov.nehta.mdht.uml.cda.ui" version="1.1.1">...</unit>
<unit id="au.gov.nehta.mdht.uml.cda.feature.source.feature.jar" version="1.1.1">...</unit>
<unit id="au.gov.nehta.mdht.uml.cda.ui.source" singleton="false" version="1.1.1">...</unit>
However the features/ and plugin/ folders only list the jars for the previous (and currently installed) version 1.1.0. I'm not entirely certain if this is a problem as I don't know the p2 layout yet and it is setup in a bit of a complicated fashion using maven, nexus, and proxied repositories.
The information contained in this e-mail message and any accompanying files is or may be privileged or confidential. If you are not the intended recipient, any use, dissemination, reliance, forwarding, printing or copying of this e-mail or any attached files is unauthorised. This e-mail and any attachments may be subject to copyright. Copyright material should not be reproduced, adapted or communicated without the written consent of the copyright owner. If you have received this e-mail in error please advise the sender immediately by return e-mail or telephone and delete all copies. NEHTA does not make any representations or give any guarantees in respect of the accuracy or completeness of any information contained in this e-mail or attached files. Internet communications are not secure, therefore NEHTA does not accept any liability for the contents of this message or attached files.