You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "ben (JIRA)" <ji...@apache.org> on 2012/06/19 01:40:43 UTC

[jira] [Commented] (JCR-2) Mavenize Project

    [ https://issues.apache.org/jira/browse/JCR-2?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13396366#comment-13396366 ] 

ben commented on JCR-2:
-----------------------

For general guidance on using maven on a project:
http://i-proving.com/2007/04/25/how-to-use-maven-on-your-project/ 
or to split your project into smaller ones with Maven:
http://i-proving.com/2007/03/29/split-your-project-into-sub-projects/ 
                
> Mavenize Project
> ----------------
>
>                 Key: JCR-2
>                 URL: https://issues.apache.org/jira/browse/JCR-2
>             Project: Jackrabbit Content Repository
>          Issue Type: Task
>          Components: maven
>            Reporter: Tim Reilly
>            Assignee: Tim Reilly
>            Priority: Minor
>         Attachments: jcrri.zip
>
>
> Mavenize project pending mailing list feedback.
> I'm attaching an out-dated zip that has some useful "stuff" to review or build upon.
> Proposed flow:
> 1) Review the maven specific elements in the zip:
> - project.xml, header.txt, license.txt, notice.txt, checkstyle.xml, project.properties, xdocs directory. NOTE: I know the license.txt and maybe header.txt are not correct per earlier discussions.
> 2) Once new package layout/code is in svn - we can refactor this and move the maven related files into place.
> Thoughts,
>   a) One of the artifacts generated is the bat file and supporting directory with the jar to run the sample app - could use some ideas on how maven should generate this.
>   b) How the local maven repo gets the jcr-api.jar? My current thinking is 'same as any non-redistributable artifact'. The user is responsible for downloading it to a local repository.

--
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