[
https://issues.apache.org/jira/browse/UIMA-476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thilo Goetz closed UIMA-476.
Other than my reservations about the whole multiple-references-not-allowed
business, fine with me.
FSArray
[
https://issues.apache.org/jira/browse/UIMA-522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12518374
]
Thilo Goetz commented on UIMA-522:
--
Adam, is this fixed with your changes to 476? Can we close this as duplicate?
Adam Lally wrote:
On 8/7/07, Adam Lally [EMAIL PROTECTED] wrote:
Maven automatically generates sources jar files (check your local
Maven repository). Unfortunately these don't have the DISCLAIMER,
LICENSE, NOTICES. I will see if I can figure out how to get those to
be added.
I've fixed
Reviewed, but not sure if we need to do something about
UIMA-522. See my Jira comment on that issue.
--Thilo
Adam Lally wrote:
On 8/7/07, Eddie Epstein [EMAIL PROTECTED] wrote:
There appears to be a problem in casCompleteSerialization associated
with multivalued properties and FS references.
[
https://issues.apache.org/jira/browse/UIMA-282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12518383
]
Michael Baessler commented on UIMA-282:
---
Thanks for contributing the log4j logger implementation. Since we are
We found more issues, cancelling vote.
--Thilo
Adam Lally wrote:
On 8/7/07, Eddie Epstein [EMAIL PROTECTED] wrote:
There appears to be a problem in casCompleteSerialization associated
with multivalued properties and FS references. This was just found
late yesterday. Please let us track this
Thilo Goetz wrote:
Hi all,
I'm wondering if it's time to move to Java 1.5 after this
release. While there are still people out there who use
Java 1.4, their numbers are shrinking rapidly. I'm guessing
that by the time we do our next release, the need for
Java 1.4 compatibility will have gone.
[
https://issues.apache.org/jira/browse/UIMA-522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adam Lally resolved UIMA-522.
-
Resolution: Fixed
Fixed. I will close once I re-test on the next release candidate.
XMI Serialization
Thilo Goetz commented on UIMA-522:
--
Adam, is this fixed with your changes to 476? Can we close this as
duplicate? Thanks.
Oops, sorry I meant to resolve UIMA-522 yesterday as well. It's not a
duplicate and has its own subversion commits.
-Adam
On 8/8/07, Marshall Schor [EMAIL PROTECTED] wrote:
Reading the above link - it specifies requirements for the pom file
for things going into
the Maven repository, which our POM doesn't have. 2 I found missing
were the
license and the scm elements.
Good catch - I will add these right away.
On 8/8/07, Thilo Goetz [EMAIL PROTECTED] wrote:
Adam Lally wrote:
This page describes how to create bundles to upload to a repository:
http://maven.apache.org/guides/mini/guide-central-repository-upload.html
Sorry, but I'm not sure how we're going to proceed now. What
exactly are the
Prepare for distribution of UIMA artifacts in Maven repository
--
Key: UIMA-524
URL: https://issues.apache.org/jira/browse/UIMA-524
Project: UIMA
Issue Type: Task
In the uimaj project's pom, the parent element points to itself. Why
is this done, and
where is the documentation in Maven which describes what this means?
Also, there are two elements defining the javadoc plugin - is this
intentional, or should/can
these be merged?
If we are heading toward
Sorry that it did not had time to respond to this mail.
I was quite busy the last few days.
What do you think is missing for the PEAR package? With the latest
fix in the CasEditor you can run an installed pear package.
Additionally with less programming effort, it will also be no
problem
On 8/8/07, Thilo Goetz [EMAIL PROTECTED] wrote:
Sure, that would be good. I'm currently building a new level, I'll
create the maven artifacts manually for this one.
I'm actually having some trouble at the moment... For one thing mvn
repository:bundle-create fails when I run it on the root
Adam Lally wrote:
On 8/8/07, Thilo Goetz [EMAIL PROTECTED] wrote:
Adam Lally wrote:
This page describes how to create bundles to upload to a repository:
http://maven.apache.org/guides/mini/guide-central-repository-upload.html
Sorry, but I'm not sure how we're going to proceed now. What
Next problem is that mvn repository:bundle-create complains about a
missing LICENSE.txt file. What's that about!?
Looking in incubator general for other projects that asked the IPMC to
ratify their maven artifacts, it looks like the preferred approach is
to set up a staging repository in
Jörn Kottmann wrote:
Sorry that it did not had time to respond to this mail.
I was quite busy the last few days.
What do you think is missing for the PEAR package? With the latest
fix in the CasEditor you can run an installed pear package.
Additionally with less programming effort, it will
On 8/8/07, Marshall Schor [EMAIL PROTECTED] wrote:
In the uimaj project's pom, the parent element points to itself.
I don't see any parent element in the uimaj project's pom.
Also, there are two elements defining the javadoc plugin - is this
intentional, or should/can
these be merged?
They
For uimaj-2.2.0 I created a directory, and collected all the
various release candidate tags under it. For 2.1.0, we
didn't do that, and it's a bit disorganized. Anybody mind
if I retroactively create a uimaj-2.1.0 dir and move all
2.1 tags under it? It's not going to affect our SVN history
in
To work around this issue, you can add a PEAR file to your cas
editor project and install it on demand and then check if the PEAR
file is already installed or not. When doing this, you can also
check if the installation location for your PEAR has changed (if
the workspace has been moved to
OK, I think I've gotten deployment of our Maven artifacts to a
staging repository to work. I committed a change to the uimaj
pom.xml:
distributionManagement
repository
idstaging-repository/id
url
On 8/8/07, Thilo Goetz [EMAIL PROTECTED] wrote:
For uimaj-2.2.0 I created a directory, and collected all the
various release candidate tags under it. For 2.1.0, we
didn't do that, and it's a bit disorganized. Anybody mind
if I retroactively create a uimaj-2.1.0 dir and move all
2.1 tags
Thilo Goetz wrote:
For uimaj-2.2.0 I created a directory, and collected all the
various release candidate tags under it. For 2.1.0, we
didn't do that, and it's a bit disorganized. Anybody mind
if I retroactively create a uimaj-2.1.0 dir and move all
2.1 tags under it? It's not going to affect
Jörn Kottmann wrote:
To work around this issue, you can add a PEAR file to your cas editor
project and install it on demand and then check if the PEAR file is
already installed or not. When doing this, you can also check if the
installation location for your PEAR has changed (if the workspace
I think the installation location should be in a temp directory or
at least outside the workspace. If its already there
he PEAR installation is reused.
You are right local changes might be a problem here, maybe the user
can be ask what to do in that case (reinstall or not) and ask him
to
Adam Lally wrote:
On 8/8/07, Marshall Schor [EMAIL PROTECTED] wrote:
In the uimaj project's pom, the parent element points to itself.
I don't see any parent element in the uimaj project's pom.
right - my oops - I was looking at the uimaj-distr pom, not the uimaj pom.
Also,
Thilo Goetz wrote:
For uimaj-2.2.0 I created a directory, and collected all the
various release candidate tags under it. For 2.1.0, we
didn't do that, and it's a bit disorganized. Anybody mind
if I retroactively create a uimaj-2.1.0 dir and move all
2.1 tags under it? It's not going to affect
[
https://issues.apache.org/jira/browse/UIMA-524?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adam Lally closed UIMA-524.
---
Resolution: Fixed
fixed
Prepare for distribution of UIMA artifacts in Maven repository
On 8/8/07, Adam Lally [EMAIL PROTECTED] wrote:
I will try to add a -deploy option to extractAndBuild script which
will execute this, and I plan to (eventually) put this information on
the Wiki Instructions for Committers page.
Done and done. Instructions are here:
Adam Lally wrote:
On 8/8/07, Thilo Goetz [EMAIL PROTECTED] wrote:
Sure, that would be good. I'm currently building a new level, I'll
create the maven artifacts manually for this one.
I'm actually having some trouble at the moment... For one thing mvn
repository:bundle-create fails
Move 2.1 SVN tags under a common directory
--
Key: UIMA-525
URL: https://issues.apache.org/jira/browse/UIMA-525
Project: UIMA
Issue Type: Improvement
Reporter: Thilo Goetz
32 matches
Mail list logo
