Michael Baessler wrote:
Marshall Schor wrote:
One other issue I just remembered - this artifact is not signed. I
don't have the time right
now due to other pressing things, so this looks like it will slip
into next week.
I absolutely agree with Thilo, we should fix and tag this in the 2.1.0
The CDE fix in Jira: http://issues.apache.org/jira/browse/UIMA-364 has
been packaged into a hotfix.
The hotfix consists only of one Eclipse Plugin project; this project
(uimaj-ep-configurator) was tagged in SVN:
+1
Makes sense to me to get this out as a hotfix.
Eddie
Marshall Schor wrote:
The CDE fix in Jira: http://issues.apache.org/jira/browse/UIMA-364 has
been packaged into a hotfix.
The hotfix consists only of one Eclipse Plugin project; this project
(uimaj-ep-configurator) was tagged in SVN:
On 3/30/07, Marshall Schor [EMAIL PROTECTED] wrote:
The CDE fix in Jira: http://issues.apache.org/jira/browse/UIMA-364 has
been packaged into a hotfix.
The hotfix consists only of one Eclipse Plugin project; this project
(uimaj-ep-configurator) was tagged in SVN:
On 3/30/07, Thilo Goetz [EMAIL PROTECTED] wrote:
I'm concerned that we didn't create this hotfix from the 2.1.0 branch in
subversion, but from trunk. I'm sorry I didn't catch this earlier, but
I only just noticed it. I think we need to build the hotfix from the
2.1.0 branch, to make sure
Adam Lally wrote:
On 3/30/07, Thilo Goetz [EMAIL PROTECTED] wrote:
I'm concerned that we didn't create this hotfix from the 2.1.0 branch in
subversion, but from trunk. I'm sorry I didn't catch this earlier, but
I only just noticed it. I think we need to build the hotfix from the
2.1.0 branch,
Adam Lally wrote:
On 3/30/07, Thilo Goetz [EMAIL PROTECTED] wrote:
I'm concerned that we didn't create this hotfix from the 2.1.0 branch in
subversion, but from trunk. I'm sorry I didn't catch this earlier, but
I only just noticed it. I think we need to build the hotfix from the
2.1.0 branch,
