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
branch. I think we shoul
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.
-Marshall
Adam Lally wrote:
On 3/30/07, Thilo Goetz <[EMAIL PROTECTED]> wrote:
I don't understand what the big rus
On 3/27/07, Jörn Kottmann <[EMAIL PROTECTED]> wrote:
> Maybe you could attach to the JIRA issue a zip containing these four
> files in their entirety.
Ok
> Also, there are dependencies in your POM on version 2.2.0-incubating
> and 2.2.0-incubating-SNAPSHOT, which both need to be changed to
> 2.
Rename plugin directories from x.version to _version
Key: UIMA-366
URL: https://issues.apache.org/jira/browse/UIMA-366
Project: UIMA
Issue Type: Improvement
Compo
On 3/30/07, Thilo Goetz <[EMAIL PROTECTED]> wrote:
I don't understand what the big rush is. It's a bug in one of our GUI
tools, that's hardly a major break. Why not take the additional hour or
whatever it takes to redo this from the 2.1 branch so everything is
clean in subversion?
Basically
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
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 noth
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:
http://svn.apache.org/repos/as
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:
http://svn.apache.org/repos/asf/incubator/uima/uimaj/tags/u
+1
Makes sense to me to get this out as a hotfix.
Eddie
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:
http://svn.apache.org/repos/asf/incubator/uima/uimaj/tags/uimaj-ep-configurator-2.
On 3/29/07, Marshall Schor <[EMAIL PROTECTED]> wrote:
I fixed a bug in the CDE (see
http://issues.apache.org/jira/browse/UIMA-364 ). I'd like to get this
fix out to users quickly, since
it's making the CDE fail for some simple actions like adding a new type
to the type system.
I asked mentor Ke
[
https://issues.apache.org/jira/browse/UIMA-360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jörn Kottmann updated UIMA-360:
---
Attachment: images.zip
> Add CAS change notifications
>
>
>
[
https://issues.apache.org/jira/browse/UIMA-360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jörn Kottmann updated UIMA-360:
---
Attachment: cas editor doc.txt
CAS Editor Documentation patch for the docbook project.
Note: This patc
15 matches
Mail list logo
