[jira] Closed: (JCR-432) change jcr api groupId and upload to the main maven repository

["Roy T. Fielding (JIRA)" <ji...@apache.org>]

     [ http://issues.apache.org/jira/browse/JCR-432?page=all ]
     
Roy T. Fielding closed JCR-432:
-------------------------------

    Resolution: Invalid

This is not a Jackrabbit issue.  The API jar file is covered by a specification license.
If you want Day to publish a pom for jcr on ibiblio, you should send the instructions
to one of the folks at Day.  It should look like the other javax.* poms.


> change jcr api groupId and upload to the main maven repository
> --------------------------------------------------------------
>
>          Key: JCR-432
>          URL: http://issues.apache.org/jira/browse/JCR-432
>      Project: Jackrabbit
>         Type: Wish

>     Reporter: fabrizio giustina
>     Assignee: Roy T. Fielding

>
> (this issue should be better addressed by the spec leads for JCR API, but probably jackrabbit is a good place to ask)
> jcr api should be uploaded to the main maven repository, with binary jar _if allowed by the license_ or at least with a pom and a javadoc jar. Since jackrabbit uses maven for its build and many users uses maven in their projects a jcr jar in the main repo would be nice: forcing everyone to link the day repo direclty is not a good solution and they only have a maven 1 repo.
> Before doing this, the groupid for jsr170:jcr 1.0 should also be changed to "javax.jcr" according to the maven guidelines (and the jackrabbit poms needs to be updated)
> I could take care of making the upload request to the maven repo (for jcr 1.0 and 1.0.1) and fixing the above things, if somebody could clarify what we are allowed to upload (poms only or jars).
> thanks

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira