Re: Next release

2013-02-19 Thread Aliaksandr Autayeu
On 12/19/2012 12:17 PM, Jörn Kottmann wrote:

  Lets start to get the release done, are there any issues expect the two
 open
 ones which need to go into this release ?

 Open issues are:
 OPENNLP-541 Improve ADChunkSampleStream
 OPENNLP-402 CLI tools and formats refactored

 Jörn, can you remind me what remains there? I've seen you commit on the
simplification you proposed and although I didn't agree earlier, after I
saw what you did - it does make sense.

Aliaksandr


Re: Next release

2013-02-19 Thread Jörn Kottmann

On 02/19/2013 11:55 AM, Aliaksandr Autayeu wrote:

  Lets start to get the release done, are there any issues expect the two

open
ones which need to go into this release ?

Open issues are:
OPENNLP-541 Improve ADChunkSampleStream
OPENNLP-402 CLI tools and formats refactored


Jörn, can you remind me what remains there? I've seen you commit on the

simplification you proposed and although I didn't agree earlier, after I
saw what you did - it does make sense.



On OPENNLP-402 I assumed lazy consensus, and fixed the two concerns I 
stated on the issue,

anyway should something be changed, or is it fine how it is now?

The whole command line interface refactoring is a big step forward, 
especially the possibility

to train directly on a corpus without converting it first manually.

Jörn




Re: Next release

2013-02-19 Thread William Colen
Should we try to upload it to Central Repo using jwnl as groupid? What do
you think?


On Mon, Feb 18, 2013 at 3:03 PM, Benson Margulies bimargul...@gmail.comwrote:

 upload to central via ossrh.

 On Feb 18, 2013, at 12:46 PM, William Colen william.co...@gmail.com
 wrote:

  We are using jwnl as groupid, I don't know if we can upload using this
  groupid. The best would be to reflect the Java package, which is
  net.didion.jwnl, or to follow the one used by 14. rc3, which
  is net.sf.jwordnet.jwnl.
  But changing the groupid would not help the already released OpenNLP
  versions.
 
 
  On Mon, Feb 18, 2013 at 12:07 PM, Jörn Kottmann kottm...@gmail.com
 wrote:
 
  On 02/18/2013 03:17 PM, William Colen wrote:
 
  I suppose we can't use opennlp.apache.org to host it, can we?
  We probably could somehow distribute it from Apache servers, but if we
  can get it into the central maven repository it would also fix the issue
  for the already
  released OpenNLP versions as far as I know.
 
  Here is a guide which explains the process:
  https://docs.sonatype.org/**display/Repository/Uploading+**
  3rd-party+Artifacts+to+The+**Central+Repository
 https://docs.sonatype.org/display/Repository/Uploading+3rd-party+Artifacts+to+The+Central+Repository
 
 
  Jörn
 



Re: Next release

2013-02-19 Thread Jörn Kottmann

On 02/19/2013 02:37 PM, William Colen wrote:

Should we try to upload it to Central Repo using jwnl as groupid? What do
you think?


+1, if that is possible it would be preferable for us, if they want to 
use another group id we

can just update our pom to the new group id.

Jörn


Re: Next release

2013-02-19 Thread Benson Margulies
yes, ossrh will do that

On Feb 19, 2013, at 8:38 AM, William Colen william.co...@gmail.com wrote:

 Should we try to upload it to Central Repo using jwnl as groupid? What do
 you think?


 On Mon, Feb 18, 2013 at 3:03 PM, Benson Margulies 
 bimargul...@gmail.comwrote:

 upload to central via ossrh.

 On Feb 18, 2013, at 12:46 PM, William Colen william.co...@gmail.com
 wrote:

 We are using jwnl as groupid, I don't know if we can upload using this
 groupid. The best would be to reflect the Java package, which is
 net.didion.jwnl, or to follow the one used by 14. rc3, which
 is net.sf.jwordnet.jwnl.
 But changing the groupid would not help the already released OpenNLP
 versions.


 On Mon, Feb 18, 2013 at 12:07 PM, Jörn Kottmann kottm...@gmail.com
 wrote:

 On 02/18/2013 03:17 PM, William Colen wrote:

 I suppose we can't use opennlp.apache.org to host it, can we?
 We probably could somehow distribute it from Apache servers, but if we
 can get it into the central maven repository it would also fix the issue
 for the already
 released OpenNLP versions as far as I know.

 Here is a guide which explains the process:
 https://docs.sonatype.org/**display/Repository/Uploading+**
 3rd-party+Artifacts+to+The+**Central+Repository
 https://docs.sonatype.org/display/Repository/Uploading+3rd-party+Artifacts+to+The+Central+Repository


 Jörn



Uploading JWNL to Maven Central Repo

2013-02-19 Thread William Colen
Hi,

I changed the topic so we can focus on this issue.

To upload JWNL to the Central Repo we need to bundle the Source and JavaDoc.

We don't have it at http://opennlp.sourceforge.net/maven2/jwnl/jwnl/1.3.3/

So, I tried to get the JavaDoc and Source from the JWNL website.

I downloaded all jars from 1.3 releases of JWNL from here:
http://sourceforge.net/projects/jwordnet/files/jwnl/JWNL%201.3/


None of them matched the SHA1 of the one we are using. Apparently someone
built the JWNL we are using from the source.

Do you know if we are safe to use the SourceCode and JavaDoc of the release
1.3 rc3 they distribute?

Thank you,
William


On Tue, Feb 19, 2013 at 11:09 AM, Benson Margulies bimargul...@gmail.comwrote:

 yes, ossrh will do that

 On Feb 19, 2013, at 8:38 AM, William Colen william.co...@gmail.com
 wrote:

  Should we try to upload it to Central Repo using jwnl as groupid? What
 do
  you think?
 
 
  On Mon, Feb 18, 2013 at 3:03 PM, Benson Margulies bimargul...@gmail.com
 wrote:
 
  upload to central via ossrh.
 
  On Feb 18, 2013, at 12:46 PM, William Colen william.co...@gmail.com
  wrote:
 
  We are using jwnl as groupid, I don't know if we can upload using
 this
  groupid. The best would be to reflect the Java package, which is
  net.didion.jwnl, or to follow the one used by 14. rc3, which
  is net.sf.jwordnet.jwnl.
  But changing the groupid would not help the already released OpenNLP
  versions.
 
 
  On Mon, Feb 18, 2013 at 12:07 PM, Jörn Kottmann kottm...@gmail.com
  wrote:
 
  On 02/18/2013 03:17 PM, William Colen wrote:
 
  I suppose we can't use opennlp.apache.org to host it, can we?
  We probably could somehow distribute it from Apache servers, but if we
  can get it into the central maven repository it would also fix the
 issue
  for the already
  released OpenNLP versions as far as I know.
 
  Here is a guide which explains the process:
  https://docs.sonatype.org/**display/Repository/Uploading+**
  3rd-party+Artifacts+to+The+**Central+Repository
 
 https://docs.sonatype.org/display/Repository/Uploading+3rd-party+Artifacts+to+The+Central+Repository
 
 
  Jörn