OK. As you've probably already figured out, this need not be a blocker for you, if you have overridden this in your textmarker parent pom, as I think you've already done :-)
When we release the next set of parent-pom changes, then those overrides can come out of the local parent poms. Other changes to the parent pom that probably ought to be done include supporting the latest m2e eclipse plugin release. Any volunteers? -Marshall On 1/9/2013 10:50 AM, Peter Klügl (JIRA) wrote: > [ > https://issues.apache.org/jira/browse/UIMA-2558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13548592#comment-13548592 > ] > > Peter Klügl commented on UIMA-2558: > ----------------------------------- > > I fixed the pom and tested it. > > However, this is probably not the only thing that needs to be done. If I > understand the process correctly, then the properties need to be adapted and > the artifacts need to be released. Can please someone else take care of this > as I am new to the release process (and I still trying to get a hang of it > with the TextMarker release). > >> builds broken - the auto generation of issues fixed is broken >> ------------------------------------------------------------- >> >> Key: UIMA-2558 >> URL: https://issues.apache.org/jira/browse/UIMA-2558 >> Project: UIMA >> Issue Type: Bug >> Components: Build, Packaging and Test >> Affects Versions: parent-pom-4 >> Reporter: Marshall Schor >> Assignee: Peter Klügl >> >> Running build with the parent-pom switches set to include generating the >> list of issues changed, etc., is broken. This is possibly due to the >> upgrades to JIRA. Errors are produced whereby the data sent from the Jira >> query cannot be parsed by the plugin. >> It may be that only the plugin needs to be upgraded? > -- > 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 >
