jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From j...@apache.org
Subject [jira] Closed: (JCR-2) Mavenize Project
Date Sat, 25 Sep 2004 09:07:32 GMT

   The following issue has been closed.

   Resolver: Tim Reilly
       Date: Sat, 25 Sep 2004 2:06 AM

Initial mavenization complete.

(change & update as needed on an ongoing basis)
View the issue:

Here is an overview of the issue:
        Key: JCR-2
    Summary: Mavenize Project
       Type: Task

     Status: Closed
   Priority: Minor
 Resolution: FIXED

    Project: Jackrabbit

   Assignee: Tim Reilly
   Reporter: Tim Reilly

    Created: Wed, 15 Sep 2004 8:45 PM
    Updated: Sat, 25 Sep 2004 2:06 AM

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.

  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 contact one of the administrators:

If you want more information on JIRA, or have a bug to report see:

View raw message