[jira] Created: (TIKA-264) Getting Started: change "source directory" to "base directory" or similar

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

[jira] Created: (TIKA-264) Getting Started: change "source directory" to "base directory" or similar

JIRA jira@apache.org
Getting Started: change "source directory" to "base directory" or similar
-------------------------------------------------------------------------

                 Key: TIKA-264
                 URL: https://issues.apache.org/jira/browse/TIKA-264
             Project: Tika
          Issue Type: Improvement
          Components: documentation
    Affects Versions: 0.3
         Environment: N/A
            Reporter: Jeff Cadow
            Priority: Trivial
             Fix For: 0.4


This is a teensy suggestion for change in word choice.

On http://lucene.apache.org/tika/gettingstarted.html, under Getting and building the sources, it says "Executing the following command in the source directory will build the sources and install the resulting artifacts in your local Maven repository."

I looked at the directory structure of  the project and figured "source directory" meant apache-tika-0.4/src. Since I'm a maven newbie, it took me about an hour to figure out the meaning of the error I got when invoking "mvn install" from that directory:

    "Cannot execute mojo: resources. It requires a project with an existing pom.xml, but the build is not using one."

Now I know I gotta invoke maven in a directory that has a pom.xml file, and the root one for Tika is the one in apache-tika-0.4.

Might save other twits an hour to change the word "source" to "base" or similar in the sentence I quoted here.

P.S. - You need to mark version 0.4 as a released version in JIRA.

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply | Threaded
Open this post in threaded view
|

[jira] Updated: (TIKA-264) Getting Started: change "source directory" to "base directory" or similar

JIRA jira@apache.org

     [ https://issues.apache.org/jira/browse/TIKA-264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Chris A. Mattmann updated TIKA-264:
-----------------------------------

    Affects Version/s:     (was: 0.3)
                       0.4
        Fix Version/s:     (was: 0.4)
                       0.5

- fix version should be unreleased version
- affects version should be released version

> Getting Started: change "source directory" to "base directory" or similar
> -------------------------------------------------------------------------
>
>                 Key: TIKA-264
>                 URL: https://issues.apache.org/jira/browse/TIKA-264
>             Project: Tika
>          Issue Type: Improvement
>          Components: documentation
>    Affects Versions: 0.4
>         Environment: N/A
>            Reporter: Jeff Cadow
>            Priority: Trivial
>             Fix For: 0.5
>
>
> This is a teensy suggestion for change in word choice.
> On http://lucene.apache.org/tika/gettingstarted.html, under Getting and building the sources, it says "Executing the following command in the source directory will build the sources and install the resulting artifacts in your local Maven repository."
> I looked at the directory structure of  the project and figured "source directory" meant apache-tika-0.4/src. Since I'm a maven newbie, it took me about an hour to figure out the meaning of the error I got when invoking "mvn install" from that directory:
>     "Cannot execute mojo: resources. It requires a project with an existing pom.xml, but the build is not using one."
> Now I know I gotta invoke maven in a directory that has a pom.xml file, and the root one for Tika is the one in apache-tika-0.4.
> Might save other twits an hour to change the word "source" to "base" or similar in the sentence I quoted here.
> P.S. - You need to mark version 0.4 as a released version in JIRA.

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply | Threaded
Open this post in threaded view
|

[jira] Resolved: (TIKA-264) Getting Started: change "source directory" to "base directory" or similar

JIRA jira@apache.org
In reply to this post by JIRA jira@apache.org

     [ https://issues.apache.org/jira/browse/TIKA-264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jukka Zitting resolved TIKA-264.
--------------------------------

    Resolution: Fixed
      Assignee: Jukka Zitting

Good point! Fixed in revision 801430.

> Getting Started: change "source directory" to "base directory" or similar
> -------------------------------------------------------------------------
>
>                 Key: TIKA-264
>                 URL: https://issues.apache.org/jira/browse/TIKA-264
>             Project: Tika
>          Issue Type: Improvement
>          Components: documentation
>    Affects Versions: 0.4
>         Environment: N/A
>            Reporter: Jeff Cadow
>            Assignee: Jukka Zitting
>            Priority: Trivial
>             Fix For: 0.5
>
>
> This is a teensy suggestion for change in word choice.
> On http://lucene.apache.org/tika/gettingstarted.html, under Getting and building the sources, it says "Executing the following command in the source directory will build the sources and install the resulting artifacts in your local Maven repository."
> I looked at the directory structure of  the project and figured "source directory" meant apache-tika-0.4/src. Since I'm a maven newbie, it took me about an hour to figure out the meaning of the error I got when invoking "mvn install" from that directory:
>     "Cannot execute mojo: resources. It requires a project with an existing pom.xml, but the build is not using one."
> Now I know I gotta invoke maven in a directory that has a pom.xml file, and the root one for Tika is the one in apache-tika-0.4.
> Might save other twits an hour to change the word "source" to "base" or similar in the sentence I quoted here.
> P.S. - You need to mark version 0.4 as a released version in JIRA.

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.