I created a branch here:
https://svn.apache.org/repos/asf/uima/sandbox/ruta/branches/UIMA-3272
If you want to give it a try, you have to search for 130926_1852 and
replace it with your timestamp.
Peter
On 26.09.2013 22:43, Peter Klügl wrote:
> Am 26.09.2013 20:31, schrieb Marshall Schor:
>> ok, another spot to check:
>>
>> The ruta-eclipse-update-site has an xml spec in
>> src/main/resources/category.xml,
>> with refs to the "feature", which I think you had a time-stamp
>> version of.
>>
>> Did you change the line:
>>
>> feature
>> url="features/org.apache.uima.ruta.feature_${parsedVersion.osgiVersion}.jar"
>>
>> id="org.apache.uima.ruta.feature"
>> version="${parsedVersion.osgiVersion}">
>> <category name="apache-uima-ruta"/>
>> </feature>
>>
>> to include the timestamp?
>
> Yes, I have changed it. This has also caused problems, but different
> ones.
>
> Peter
>
>> -Marshall
>> On 9/26/2013 2:13 PM, Peter Klügl wrote:
>>> Am 26.09.2013 19:55, schrieb Marshall Schor:
>>>> Yeah, having changing names for jars with each rebuild breaks code
>>>> which is
>>>> referring to the jars. In this case,
>>>> I think the feature (UIMA Ruta Workbench), has a list of the
>>>> plugins that go
>>>> with the feature, using this naming style, in the
>>>> src/main/resources/feature.xml
>>>> file:
>>>>
>>>> <plugin
>>>> id="org.apache.uima.ruta.addons"
>>>> download-size="0"
>>>> install-size="0"
>>>> version="${parsedVersion.osgiVersion}"
>>>> unpack="false"/>
>>>>
>>>> <plugin
>>>> id="org.apache.uima.ruta.caseditor"
>>>> download-size="0"
>>>> install-size="0"
>>>> version="${parsedVersion.osgiVersion}"
>>>> unpack="false"/>
>>>>
>>>> etc.
>>>>
>>>> So each of these would need to somehow be modified with every build...
>>> Yes and I also adapted those versions. I also checked the update
>>> site metadata
>>> (content,artifacts), but could not find the requirement.
>>>
>>> Maybe I should create a branch for my changes to the ruta plugins...
>>>
>>> Peter
>>>
>>>> -Marshall
>>>>
>>>> On 9/26/2013 1:21 PM, Peter Klügl (JIRA) wrote:
>>>>> [
>>>>> https://issues.apache.org/jira/browse/UIMA-3272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13778988#comment-13778988
>>>>>
>>>>> ]
>>>>>
>>>>> Peter Klügl commented on UIMA-3272:
>>>>> -----------------------------------
>>>>>
>>>>> I was able to build a Ruta update site with timestamps with a few
>>>>> manual
>>>>> edits because maven has not replaced ${maven.build.timestamp}.
>>>>> However, I
>>>>> was not able to install the feature, because of:
>>>>>
>>>>> {noformat}
>>>>> Cannot complete the install because one or more required items
>>>>> could not be
>>>>> found.
>>>>> Software being installed: UIMA Ruta Workbench
>>>>> 2.1.1.SNAPSHOT-130926_1852
>>>>> (org.apache.uima.ruta.feature.feature.group
>>>>> 2.1.1.SNAPSHOT-130926_1852)
>>>>> Missing requirement: UIMA Ruta Workbench
>>>>> 2.1.1.SNAPSHOT-130926_1852
>>>>> (org.apache.uima.ruta.feature.feature.group
>>>>> 2.1.1.SNAPSHOT-130926_1852)
>>>>> requires 'org.apache.uima.ruta.addons [2.1.1.SNAPSHOT]' but it
>>>>> could not be
>>>>> found
>>>>> {noformat}
>>>>>
>>>>> No idea where this requirement comes from...
>>>>>
>>>>>
>>>>>> Add timestamp to Eclipse plugin versions
>>>>>> ----------------------------------------
>>>>>>
>>>>>> Key: UIMA-3272
>>>>>> URL:
>>>>>> https://issues.apache.org/jira/browse/UIMA-3272
>>>>>> Project: UIMA
>>>>>> Issue Type: Improvement
>>>>>> Components: Eclipse plugins, ruta
>>>>>> Reporter: Richard Eckart de Castilho
>>>>>>
>>>>>> When we do release candidates, we can currently not upgrade an
>>>>>> Eclipse from
>>>>>> one candidate to the next one from the update site, because the
>>>>>> version
>>>>>> does not change. Many Eclipse bundles bear an additional
>>>>>> timestamp after
>>>>>> the version. It would be great to have this as well for our
>>>>>> plugin to
>>>>>> facilitate RC testing.
>>>>> --
>>>>> 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
>>>>>
>>>
>
