You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@opennlp.apache.org by "Fergal Monaghan (JIRA)" <ji...@apache.org> on 2012/05/22 14:49:41 UTC
[jira] [Created] (OPENNLP-510) Maven dependency on jwnl is broken
Fergal Monaghan created OPENNLP-510:
---------------------------------------
Summary: Maven dependency on jwnl is broken
Key: OPENNLP-510
URL: https://issues.apache.org/jira/browse/OPENNLP-510
Project: OpenNLP
Issue Type: Bug
Components: Build, Packaging and Test
Affects Versions: tools-1.5.2-incubating, tools-1.5.3
Reporter: Fergal Monaghan
Priority: Blocker
Dependency in tools pom for jwnl has groupID and version of a no-longer available version of jwnl. The attached patch fixes this.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (OPENNLP-510) Maven dependency on jwnl is broken
Posted by "James Kosin (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OPENNLP-510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13511058#comment-13511058 ]
James Kosin commented on OPENNLP-510:
-------------------------------------
Added:
I've been using 1.4_rc3 for some time now. They have a few fixes in this release that address a few minor details; but, the group never got the release formally finalized. They have since moved on to a newer framework... but, kept the legacy project available.
> Maven dependency on jwnl is broken
> ----------------------------------
>
> Key: OPENNLP-510
> URL: https://issues.apache.org/jira/browse/OPENNLP-510
> Project: OpenNLP
> Issue Type: Bug
> Components: Build, Packaging and Test
> Affects Versions: tools-1.5.2-incubating, tools-1.5.3
> Reporter: Fergal Monaghan
> Priority: Blocker
> Attachments: pom.xml.patch
>
> Original Estimate: 1m
> Remaining Estimate: 1m
>
> Dependency in tools pom for jwnl has groupID and version of a no-longer available version of jwnl. An individual developer may be able to sidestep this with manual fixes to the local Maven repositroy, but this completely breaks continuous integration/build servers etc.. The attached patch fixes this by simply updating the dependency to the latest groupID and version for jwnl.
--
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
[jira] [Commented] (OPENNLP-510) Maven dependency on jwnl is broken
Posted by "Joern Kottmann (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OPENNLP-510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13402604#comment-13402604 ]
Joern Kottmann commented on OPENNLP-510:
----------------------------------------
Thanks for your answer. We need to test the coreference component when we update that, so it will take a bit time to do that.
> Maven dependency on jwnl is broken
> ----------------------------------
>
> Key: OPENNLP-510
> URL: https://issues.apache.org/jira/browse/OPENNLP-510
> Project: OpenNLP
> Issue Type: Bug
> Components: Build, Packaging and Test
> Affects Versions: tools-1.5.2-incubating, tools-1.5.3
> Reporter: Fergal Monaghan
> Priority: Blocker
> Attachments: pom.xml.patch
>
> Original Estimate: 1m
> Remaining Estimate: 1m
>
> Dependency in tools pom for jwnl has groupID and version of a no-longer available version of jwnl. An individual developer may be able to sidestep this with manual fixes to the local Maven repositroy, but this completely breaks continuous integration/build servers etc.. The attached patch fixes this by simply updating the dependency to the latest groupID and version for jwnl.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (OPENNLP-510) Maven dependency on jwnl is broken
Posted by "Fergal Monaghan (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OPENNLP-510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13434944#comment-13434944 ]
Fergal Monaghan commented on OPENNLP-510:
-----------------------------------------
Testing
> Maven dependency on jwnl is broken
> ----------------------------------
>
> Key: OPENNLP-510
> URL: https://issues.apache.org/jira/browse/OPENNLP-510
> Project: OpenNLP
> Issue Type: Bug
> Components: Build, Packaging and Test
> Affects Versions: tools-1.5.2-incubating, tools-1.5.3
> Reporter: Fergal Monaghan
> Priority: Blocker
> Attachments: pom.xml.patch
>
> Original Estimate: 1m
> Remaining Estimate: 1m
>
> Dependency in tools pom for jwnl has groupID and version of a no-longer available version of jwnl. An individual developer may be able to sidestep this with manual fixes to the local Maven repositroy, but this completely breaks continuous integration/build servers etc.. The attached patch fixes this by simply updating the dependency to the latest groupID and version for jwnl.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (OPENNLP-510) Maven dependency on jwnl is broken
Posted by "Fergal Monaghan (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OPENNLP-510?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Fergal Monaghan updated OPENNLP-510:
------------------------------------
Attachment: pom.xml.patch
> Maven dependency on jwnl is broken
> ----------------------------------
>
> Key: OPENNLP-510
> URL: https://issues.apache.org/jira/browse/OPENNLP-510
> Project: OpenNLP
> Issue Type: Bug
> Components: Build, Packaging and Test
> Affects Versions: tools-1.5.2-incubating, tools-1.5.3
> Reporter: Fergal Monaghan
> Priority: Blocker
> Attachments: pom.xml.patch
>
> Original Estimate: 1m
> Remaining Estimate: 1m
>
> Dependency in tools pom for jwnl has groupID and version of a no-longer available version of jwnl. An individual developer may be able to sidestep this with manual fixes to the local Maven repositroy, but this completely breaks continuous integration/build servers etc.. The attached patch fixes this by simply updating the dependency to the latest groupID and version for jwnl.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (OPENNLP-510) Maven dependency on jwnl is broken
Posted by "Joern Kottmann (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OPENNLP-510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13400436#comment-13400436 ]
Joern Kottmann commented on OPENNLP-510:
----------------------------------------
>From which repository does this new version come?
> Maven dependency on jwnl is broken
> ----------------------------------
>
> Key: OPENNLP-510
> URL: https://issues.apache.org/jira/browse/OPENNLP-510
> Project: OpenNLP
> Issue Type: Bug
> Components: Build, Packaging and Test
> Affects Versions: tools-1.5.2-incubating, tools-1.5.3
> Reporter: Fergal Monaghan
> Priority: Blocker
> Attachments: pom.xml.patch
>
> Original Estimate: 1m
> Remaining Estimate: 1m
>
> Dependency in tools pom for jwnl has groupID and version of a no-longer available version of jwnl. An individual developer may be able to sidestep this with manual fixes to the local Maven repositroy, but this completely breaks continuous integration/build servers etc.. The attached patch fixes this by simply updating the dependency to the latest groupID and version for jwnl.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (OPENNLP-510) Maven dependency on jwnl is broken
Posted by "James Kosin (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OPENNLP-510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13511056#comment-13511056 ]
James Kosin commented on OPENNLP-510:
-------------------------------------
Jorn,
Yeah, the older version 1.3.3 doesn't seem to work anymore. I've been working with the sources locally; since, it contains path information you have to specify for some of the functionality I'm using.
The server or repo that is delivering 1.3.3 seems to have a corrupted version of the release... so, it fails the build due to this.
There are some servers that do still have 1.3.3 available, just search for "jwnl" and 1.3.3 and you should get a few hits.
> Maven dependency on jwnl is broken
> ----------------------------------
>
> Key: OPENNLP-510
> URL: https://issues.apache.org/jira/browse/OPENNLP-510
> Project: OpenNLP
> Issue Type: Bug
> Components: Build, Packaging and Test
> Affects Versions: tools-1.5.2-incubating, tools-1.5.3
> Reporter: Fergal Monaghan
> Priority: Blocker
> Attachments: pom.xml.patch
>
> Original Estimate: 1m
> Remaining Estimate: 1m
>
> Dependency in tools pom for jwnl has groupID and version of a no-longer available version of jwnl. An individual developer may be able to sidestep this with manual fixes to the local Maven repositroy, but this completely breaks continuous integration/build servers etc.. The attached patch fixes this by simply updating the dependency to the latest groupID and version for jwnl.
--
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
[jira] [Commented] (OPENNLP-510) Maven dependency on jwnl is broken
Posted by "Anuj Dutta (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OPENNLP-510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13503500#comment-13503500 ]
Anuj Dutta commented on OPENNLP-510:
------------------------------------
Any news on this? This is still broken.
> Maven dependency on jwnl is broken
> ----------------------------------
>
> Key: OPENNLP-510
> URL: https://issues.apache.org/jira/browse/OPENNLP-510
> Project: OpenNLP
> Issue Type: Bug
> Components: Build, Packaging and Test
> Affects Versions: tools-1.5.2-incubating, tools-1.5.3
> Reporter: Fergal Monaghan
> Priority: Blocker
> Attachments: pom.xml.patch
>
> Original Estimate: 1m
> Remaining Estimate: 1m
>
> Dependency in tools pom for jwnl has groupID and version of a no-longer available version of jwnl. An individual developer may be able to sidestep this with manual fixes to the local Maven repositroy, but this completely breaks continuous integration/build servers etc.. The attached patch fixes this by simply updating the dependency to the latest groupID and version for jwnl.
--
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
[jira] [Updated] (OPENNLP-510) Maven dependency on jwnl is broken
Posted by "Fergal Monaghan (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OPENNLP-510?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Fergal Monaghan updated OPENNLP-510:
------------------------------------
Description: Dependency in tools pom for jwnl has groupID and version of a no-longer available version of jwnl. An individual developer may be able to sidestep this with manual fixes to the local Maven repositroy, but this completely breaks continuous integration/build servers etc.. The attached patch fixes this by simply updating the dependency to the latest groupID and version for jwnl. (was: Dependency in tools pom for jwnl has groupID and version of a no-longer available version of jwnl. The attached patch fixes this.)
> Maven dependency on jwnl is broken
> ----------------------------------
>
> Key: OPENNLP-510
> URL: https://issues.apache.org/jira/browse/OPENNLP-510
> Project: OpenNLP
> Issue Type: Bug
> Components: Build, Packaging and Test
> Affects Versions: tools-1.5.2-incubating, tools-1.5.3
> Reporter: Fergal Monaghan
> Priority: Blocker
> Original Estimate: 1m
> Remaining Estimate: 1m
>
> Dependency in tools pom for jwnl has groupID and version of a no-longer available version of jwnl. An individual developer may be able to sidestep this with manual fixes to the local Maven repositroy, but this completely breaks continuous integration/build servers etc.. The attached patch fixes this by simply updating the dependency to the latest groupID and version for jwnl.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (OPENNLP-510) Maven dependency on jwnl is broken
Posted by "Joern Kottmann (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OPENNLP-510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13511227#comment-13511227 ]
Joern Kottmann commented on OPENNLP-510:
----------------------------------------
We have control over the sourceforge page hosting our current repository, but it seems that the page is producing to much traffic, then we get blocked for two hours or so until we produce too much traffic again.
> Maven dependency on jwnl is broken
> ----------------------------------
>
> Key: OPENNLP-510
> URL: https://issues.apache.org/jira/browse/OPENNLP-510
> Project: OpenNLP
> Issue Type: Bug
> Components: Build, Packaging and Test
> Affects Versions: tools-1.5.2-incubating, tools-1.5.3
> Reporter: Fergal Monaghan
> Priority: Blocker
> Attachments: pom.xml.patch
>
> Original Estimate: 1m
> Remaining Estimate: 1m
>
> Dependency in tools pom for jwnl has groupID and version of a no-longer available version of jwnl. An individual developer may be able to sidestep this with manual fixes to the local Maven repositroy, but this completely breaks continuous integration/build servers etc.. The attached patch fixes this by simply updating the dependency to the latest groupID and version for jwnl.
--
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
[jira] [Comment Edited] (OPENNLP-510) Maven dependency on jwnl is
broken
Posted by "Fergal Monaghan (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OPENNLP-510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13503716#comment-13503716 ]
Fergal Monaghan edited comment on OPENNLP-510 at 11/26/12 10:41 AM:
--------------------------------------------------------------------
Anuj, I don't know if this workaround helps your situation, but it works in my case (I don't need coreference resolution yet): I have sinced switched from using the opennlp-tools Maven dependency directly to using cleartk-opennlp-tools, which still depends indirectly on opennlp-tools and therefore jwnl. This means I use cleartk's typesystem (cleartk-type-system) and not OpenNLP's, which means that it is transparent which e.g. Tokeniser, Parser etc. I'm using under the hood (i.e. I could switch OpenNLP out for another library but keep my data and typesystem the same). However, cleartk does not wrap OpenNLP's coreference resolution (yet), which apparently is all jwnl is needed for. This is not a problem for me as I do not require coreference resolution from OpenNLP (yet).
The cleartk guys include this dependency exclusion for the broken jwnl dependency in the POM file of cleartk-opennlp-tools:
<dependency>
<groupId>org.apache.opennlp</groupId>
<artifactId>opennlp-tools</artifactId>
<version>1.5.2-incubating</version>
<exclusions>
<!-- only needed for coreference, which we don't wrap yet -->
<exclusion>
<groupId>jwnl</groupId>
<artifactId>jwnl</artifactId>
</exclusion>
</exclusions>
</dependency>
Now *assuming* you also do not need coreference for your application, you have 2 options. You could *either* (a) include this exclusion in your own POM file, or (b) you could switch from depending directly on opennlp-tools to depending on cleartk-opennlp-tools and just reuse their exclusion transparently. I started off using (a) but have since switched to (b) and never looked back. Pros of (a) = you can immediately move forward with no changes to your typesystem or data. Cons of (a) = if jwnl gets fixed and you want to use coreference, you will have to be aware of this and remove the exclusion manually yourself. Pros of (b) = you don't have to care when its fixed, cleartk guys will take care of that, plus you now have an implementation-agnostic typesystem for lots of analysis applications. Cons of (b) = you have the once-off cost of having to switch your typesystem, plus re-process your data with it.
was (Author: fergalmonaghan):
Anuj, I don't know if this workaround helps your situation, but it works in my case (I don't need coreference resolution yet): I have sinced switched from using the opennlp-tools Maven dependency directly to using cleartk-opennlp-tools, which still depends indirectly on opennlp-tools and therefore jwnl. This means I use cleartk's typesystem (cleartk-type-system) and not OpenNLP's, which means that it is transparent which e.g. Tokeniser, Parser etc. I'm using under the hood (i.e. I could switch OpenNLP out for another library but keep my data and typesystem the same). However, cleartk does not wrap OpenNLP's coreference resolution (yet), which apparently is all jwnl is needed for. This is not a problem for me as I do not require coreference resolution from OpenNLP (yet).
The cleartk guys include this dependency exclusion for the broken jwnl dependency in the POM file of cleartk-opennlp-tools:
<dependency>
<groupId>org.apache.opennlp</groupId>
<artifactId>opennlp-tools</artifactId>
<version>1.5.2-incubating</version>
<exclusions>
<!-- only needed for coreference, which we don't wrap yet -->
<exclusion>
<groupId>jwnl</groupId>
<artifactId>jwnl</artifactId>
</exclusion>
</exclusions>
</dependency>
Now *assuming* you also do not need coreference for your application, you have 2 options. You could *either* (a) include this exclusion in your own POM file, or (b) you could switch from depending directly on opennlp-tools to depending on cleartk-opennlp-tools and just reuse their exclusion transparently. Pros of (a) = you can immediately move forward with no changes to your typesystem or data. Cons of (a) = if jwnl gets fixed and you want to use coreference, you will have to be aware of this and remove the exclusion manually yourself. Pros of (b) = you don't have to care when its fixed, cleartk guys will take care of that, plus you now have an implementation-agnostic typesystem for lots of analysis applications. Cons of (b) = you have the once-off cost of having to switch your typesystem, plus re-process your data with it.
> Maven dependency on jwnl is broken
> ----------------------------------
>
> Key: OPENNLP-510
> URL: https://issues.apache.org/jira/browse/OPENNLP-510
> Project: OpenNLP
> Issue Type: Bug
> Components: Build, Packaging and Test
> Affects Versions: tools-1.5.2-incubating, tools-1.5.3
> Reporter: Fergal Monaghan
> Priority: Blocker
> Attachments: pom.xml.patch
>
> Original Estimate: 1m
> Remaining Estimate: 1m
>
> Dependency in tools pom for jwnl has groupID and version of a no-longer available version of jwnl. An individual developer may be able to sidestep this with manual fixes to the local Maven repositroy, but this completely breaks continuous integration/build servers etc.. The attached patch fixes this by simply updating the dependency to the latest groupID and version for jwnl.
--
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
[jira] [Commented] (OPENNLP-510) Maven dependency on jwnl is broken
Posted by "Fergal Monaghan (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OPENNLP-510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13402625#comment-13402625 ]
Fergal Monaghan commented on OPENNLP-510:
-----------------------------------------
Cool, thanks! All the best, Ferg.
> Maven dependency on jwnl is broken
> ----------------------------------
>
> Key: OPENNLP-510
> URL: https://issues.apache.org/jira/browse/OPENNLP-510
> Project: OpenNLP
> Issue Type: Bug
> Components: Build, Packaging and Test
> Affects Versions: tools-1.5.2-incubating, tools-1.5.3
> Reporter: Fergal Monaghan
> Priority: Blocker
> Attachments: pom.xml.patch
>
> Original Estimate: 1m
> Remaining Estimate: 1m
>
> Dependency in tools pom for jwnl has groupID and version of a no-longer available version of jwnl. An individual developer may be able to sidestep this with manual fixes to the local Maven repositroy, but this completely breaks continuous integration/build servers etc.. The attached patch fixes this by simply updating the dependency to the latest groupID and version for jwnl.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (OPENNLP-510) Maven dependency on jwnl is broken
Posted by "Fergal Monaghan (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OPENNLP-510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13402601#comment-13402601 ]
Fergal Monaghan commented on OPENNLP-510:
-----------------------------------------
I suppose to clarify/extend Erik's question: is there a general resource where we can keep track of when a new versionof OpenNLP (e.g. 1.5.3 is estimated to be released)? And if not, do you have any idea when version 1.5.3 (specifically) might be released? Thanks, Ferg.
> Maven dependency on jwnl is broken
> ----------------------------------
>
> Key: OPENNLP-510
> URL: https://issues.apache.org/jira/browse/OPENNLP-510
> Project: OpenNLP
> Issue Type: Bug
> Components: Build, Packaging and Test
> Affects Versions: tools-1.5.2-incubating, tools-1.5.3
> Reporter: Fergal Monaghan
> Priority: Blocker
> Attachments: pom.xml.patch
>
> Original Estimate: 1m
> Remaining Estimate: 1m
>
> Dependency in tools pom for jwnl has groupID and version of a no-longer available version of jwnl. An individual developer may be able to sidestep this with manual fixes to the local Maven repositroy, but this completely breaks continuous integration/build servers etc.. The attached patch fixes this by simply updating the dependency to the latest groupID and version for jwnl.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (OPENNLP-510) Maven dependency on jwnl is broken
Posted by "Erik Faessler (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OPENNLP-510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13400433#comment-13400433 ]
Erik Faessler commented on OPENNLP-510:
---------------------------------------
Is someone on this? I just came over this little but annoying problem. A quick fix would be appreciated.
> Maven dependency on jwnl is broken
> ----------------------------------
>
> Key: OPENNLP-510
> URL: https://issues.apache.org/jira/browse/OPENNLP-510
> Project: OpenNLP
> Issue Type: Bug
> Components: Build, Packaging and Test
> Affects Versions: tools-1.5.2-incubating, tools-1.5.3
> Reporter: Fergal Monaghan
> Priority: Blocker
> Attachments: pom.xml.patch
>
> Original Estimate: 1m
> Remaining Estimate: 1m
>
> Dependency in tools pom for jwnl has groupID and version of a no-longer available version of jwnl. An individual developer may be able to sidestep this with manual fixes to the local Maven repositroy, but this completely breaks continuous integration/build servers etc.. The attached patch fixes this by simply updating the dependency to the latest groupID and version for jwnl.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (OPENNLP-510) Maven dependency on jwnl is broken
Posted by "Joern Kottmann (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OPENNLP-510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13511224#comment-13511224 ]
Joern Kottmann commented on OPENNLP-510:
----------------------------------------
We can replace the repository with another one which also contains the 1.3.3 version, updating to 1.4_rc3 is not really an option without testing the coref component on it.
Any suggestions for a repository which contains 1.3.3? Otherwise we might want to get it into maven central.
> Maven dependency on jwnl is broken
> ----------------------------------
>
> Key: OPENNLP-510
> URL: https://issues.apache.org/jira/browse/OPENNLP-510
> Project: OpenNLP
> Issue Type: Bug
> Components: Build, Packaging and Test
> Affects Versions: tools-1.5.2-incubating, tools-1.5.3
> Reporter: Fergal Monaghan
> Priority: Blocker
> Attachments: pom.xml.patch
>
> Original Estimate: 1m
> Remaining Estimate: 1m
>
> Dependency in tools pom for jwnl has groupID and version of a no-longer available version of jwnl. An individual developer may be able to sidestep this with manual fixes to the local Maven repositroy, but this completely breaks continuous integration/build servers etc.. The attached patch fixes this by simply updating the dependency to the latest groupID and version for jwnl.
--
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
[jira] [Commented] (OPENNLP-510) Maven dependency on jwnl is broken
Posted by "Fergal Monaghan (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OPENNLP-510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13402599#comment-13402599 ]
Fergal Monaghan commented on OPENNLP-510:
-----------------------------------------
Hi Joern,
in your question, I presume you are asking which repository holds jwnl version 1.4_rc3: as far as I am aware, this is at least in the central Maven repository (repo1) since September 2011:
http://search.maven.org/#search|ga|1|jwnl
So there shouldn't need to be any custom POM configuration to include a new repository or anything: using Maven's defaults and supplying the correct group and artifact IDs will do the trick.
> Maven dependency on jwnl is broken
> ----------------------------------
>
> Key: OPENNLP-510
> URL: https://issues.apache.org/jira/browse/OPENNLP-510
> Project: OpenNLP
> Issue Type: Bug
> Components: Build, Packaging and Test
> Affects Versions: tools-1.5.2-incubating, tools-1.5.3
> Reporter: Fergal Monaghan
> Priority: Blocker
> Attachments: pom.xml.patch
>
> Original Estimate: 1m
> Remaining Estimate: 1m
>
> Dependency in tools pom for jwnl has groupID and version of a no-longer available version of jwnl. An individual developer may be able to sidestep this with manual fixes to the local Maven repositroy, but this completely breaks continuous integration/build servers etc.. The attached patch fixes this by simply updating the dependency to the latest groupID and version for jwnl.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (OPENNLP-510) Maven dependency on jwnl is broken
Posted by "Joern Kottmann (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OPENNLP-510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13400437#comment-13400437 ]
Joern Kottmann commented on OPENNLP-510:
----------------------------------------
We need to restore the old repo to get the build of 1.5.2-incubating working again (since we cannot modify the release), so this patch can only fix 1.5.3.
> Maven dependency on jwnl is broken
> ----------------------------------
>
> Key: OPENNLP-510
> URL: https://issues.apache.org/jira/browse/OPENNLP-510
> Project: OpenNLP
> Issue Type: Bug
> Components: Build, Packaging and Test
> Affects Versions: tools-1.5.2-incubating, tools-1.5.3
> Reporter: Fergal Monaghan
> Priority: Blocker
> Attachments: pom.xml.patch
>
> Original Estimate: 1m
> Remaining Estimate: 1m
>
> Dependency in tools pom for jwnl has groupID and version of a no-longer available version of jwnl. An individual developer may be able to sidestep this with manual fixes to the local Maven repositroy, but this completely breaks continuous integration/build servers etc.. The attached patch fixes this by simply updating the dependency to the latest groupID and version for jwnl.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (OPENNLP-510) Maven dependency on jwnl is broken
Posted by "Joern Kottmann (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OPENNLP-510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13402606#comment-13402606 ]
Joern Kottmann commented on OPENNLP-510:
----------------------------------------
We do not have a schedule yet for the release. First thing is to decide who is Release Manager for 1.5.3. If no one is available I will of course do it myself, but it can easily take 2 - 3 month from then to get everything fixed and in a good shape for a release.
> Maven dependency on jwnl is broken
> ----------------------------------
>
> Key: OPENNLP-510
> URL: https://issues.apache.org/jira/browse/OPENNLP-510
> Project: OpenNLP
> Issue Type: Bug
> Components: Build, Packaging and Test
> Affects Versions: tools-1.5.2-incubating, tools-1.5.3
> Reporter: Fergal Monaghan
> Priority: Blocker
> Attachments: pom.xml.patch
>
> Original Estimate: 1m
> Remaining Estimate: 1m
>
> Dependency in tools pom for jwnl has groupID and version of a no-longer available version of jwnl. An individual developer may be able to sidestep this with manual fixes to the local Maven repositroy, but this completely breaks continuous integration/build servers etc.. The attached patch fixes this by simply updating the dependency to the latest groupID and version for jwnl.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (OPENNLP-510) Maven dependency on jwnl is broken
Posted by "Fergal Monaghan (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OPENNLP-510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13503716#comment-13503716 ]
Fergal Monaghan commented on OPENNLP-510:
-----------------------------------------
Anuj, I don't know if this workaround helps your situation, but it works in my case (I don't need coreference resolution yet): I have sinced switched from using the opennlp-tools Maven dependency directly to using cleartk-opennlp-tools, which still depends indirectly on opennlp-tools and therefore jwnl. This means I use cleartk's typesystem (cleartk-type-system) and not OpenNLP's, which means that it is transparent which e.g. Tokeniser, Parser etc. I'm using under the hood (i.e. I could switch OpenNLP out for another library but keep my data and typesystem the same). However, cleartk does not wrap OpenNLP's coreference resolution (yet), which apparently is all jwnl is needed for. This is not a problem for me as I do not require coreference resolution from OpenNLP (yet).
The cleartk guys include this dependency exclusion for the broken jwnl dependency in the POM file of cleartk-opennlp-tools:
<dependency>
<groupId>org.apache.opennlp</groupId>
<artifactId>opennlp-tools</artifactId>
<version>1.5.2-incubating</version>
<exclusions>
<!-- only needed for coreference, which we don't wrap yet -->
<exclusion>
<groupId>jwnl</groupId>
<artifactId>jwnl</artifactId>
</exclusion>
</exclusions>
</dependency>
Now *assuming* you also do not need coreference for your application, you have 2 options. You could *either* (a) include this exclusion in your own POM file, or (b) you could switch from depending directly on opennlp-tools to depending on cleartk-opennlp-tools and just reuse their exclusion transparently. Pros of (a) = you can immediately move forward with no changes to your typesystem or data. Cons of (a) = if jwnl gets fixed and you want to use coreference, you will have to be aware of this and remove the exclusion manually yourself. Pros of (b) = you don't have to care when its fixed, cleartk guys will take care of that, plus you now have an implementation-agnostic typesystem for lots of analysis applications. Cons of (b) = you have the once-off cost of having to switch your typesystem, plus re-process your data with it.
> Maven dependency on jwnl is broken
> ----------------------------------
>
> Key: OPENNLP-510
> URL: https://issues.apache.org/jira/browse/OPENNLP-510
> Project: OpenNLP
> Issue Type: Bug
> Components: Build, Packaging and Test
> Affects Versions: tools-1.5.2-incubating, tools-1.5.3
> Reporter: Fergal Monaghan
> Priority: Blocker
> Attachments: pom.xml.patch
>
> Original Estimate: 1m
> Remaining Estimate: 1m
>
> Dependency in tools pom for jwnl has groupID and version of a no-longer available version of jwnl. An individual developer may be able to sidestep this with manual fixes to the local Maven repositroy, but this completely breaks continuous integration/build servers etc.. The attached patch fixes this by simply updating the dependency to the latest groupID and version for jwnl.
--
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