I think we should not add more dependency to UIMA.
The standard java.util.logging is good since it is included in every Java
runtime.
But, we should try to find some way for users to customize the logging
package to something else like Log4J. if they want to.
- Tong
On 2/6/07, Greg Holmberg (JI
Work well with Apache logging (Log4J)
-
Key: UIMA-282
URL: https://issues.apache.org/jira/browse/UIMA-282
Project: UIMA
Issue Type: Wish
Reporter: Greg Holmberg
Priority: Minor
UI
We've never gotten review / approval for including the docbook stuff.
I think if we include it in the distr, I think it will raise some
discussion which might go on for a while. Basically, several folks in
Apache who manage "risk" would need to get comfortable with what we're
doing. I'm gues
[
https://issues.apache.org/jira/browse/UIMA-281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lev Kozakov updated UIMA-281:
-
Attachment: UIMAUtil.patch
The code is modified to use xmlDescUri instead of xmlDescFile in exception
hand
org.apache.uima.pear.util.UIMAUtil.identifyUimaComponentCategory method may
throw NullPointerException
--
Key: UIMA-281
URL: https://issues.apache.org/jira/browse/
Michael Baessler wrote:
Hi,
for all the are interested. I have written a tool, LevelIssueAnalyzer,
that analyzes the commit logs messages based on the last level name
and revision information and extract all Jira issue keys that are part
of the commit messages. So the tool can show all Jira i
[
https://issues.apache.org/jira/browse/UIMA-224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thilo Goetz closed UIMA-224.
Resolution: Fixed
Info added. Close for now, improve later with a new issue.
> Add release signing and veri
[
https://issues.apache.org/jira/browse/UIMA-251?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thilo Goetz closed UIMA-251.
Resolution: Fixed
> CVD should not use a banner
> ---
>
> Key: UIMA-2
Thilo Goetz wrote:
Release test level uimaj-2.1.0-003 will shortly be available on people
in /home/twgoetz/uima-distributions/2.1.0/003.
--Thilo
The level contains the following JIRA issues:
https://issues.apache.org/jira/browse/UIMA-259: [#UIMA-259] add an
overview HTML document with links
Hi,
for all the are interested. I have written a tool, LevelIssueAnalyzer,
that analyzes the commit logs messages based on the last level name and
revision information and extract all Jira issue keys that are part of
the commit messages. So the tool can show all Jira issues that have been
fix
[
https://issues.apache.org/jira/browse/UIMA-280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Baessler closed UIMA-280.
-
Resolution: Fixed
> add uimaj-internal-tools project and add tooling to detect jira issues for an
Jörn Kottmann wrote:
Hello,
thank you all for accepting my contribution.
First we should rename the tool as mentioned to CAS Editor.
What must I do to get access to the svn repository to checkin
the project ?
Hi Jörn -
We've drafted some project guidelines here:
http://incubator.apache.org/u
I thought I tried that...
Marshall Schor wrote:
Thilo Goetz wrote:
Right, that was the second thing I tried. And no, it doesn't work. I
agree it should, but it didn't. The only way I could get it to work
was to explicitly specify the docs directory as external class folder,
which doesn't h
Thilo Goetz wrote:
Right, that was the second thing I tried. And no, it doesn't work. I
agree it should, but it didn't. The only way I could get it to work
was to explicitly specify the docs directory as external class folder,
which doesn't help. If you find another way that works, let me k
add uimaj-internal-tools project and add tooling to detect jira issues for an
UIMA level.
-
Key: UIMA-280
URL: https://issues.apache.org/jira/browse/UIMA-280
Proj
[
https://issues.apache.org/jira/browse/UIMA-272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thilo Goetz closed UIMA-272.
Resolution: Fixed
Fix Version/s: 2.1
> CVD manual & help missing?
> ---
>
>
16 matches
Mail list logo
