Mailing-List: contact user-help@uima.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@uima.apache.org
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
Subject: Re: Developing UIMA Ruta Rules in Maven Projects
From: Richard Eckart de Castilho <rec@apache.org>
In-Reply-To: <551AF598.8050506@uni-wuerzburg.de>
Date: Wed, 1 Apr 2015 15:43:36 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <410CFC14-EF83-4A6A-B3C8-A0BC2E95AB50@apache.org>
References: <551965A5.8000401@averbis.com>
 <D9538476-103C-43BE-A81E-7876707719CC@apache.org>
 <551AF598.8050506@uni-wuerzburg.de>
To: user@uima.apache.org

On 31.03.2015, at 21:29, Peter Kl=FCgl <pkluegl@uni-wuerzburg.de> wrote:

> My first investigations for a m2e project configurator haven't been =
really successful. If someone has experience in this field... any help =
is welcome ;-)

You are talking about a connector that configures the ruta workbench =
based on settings made in the POM or on a maven-plugin that does =
something during a maven-based build?

> I intent to support src/main/ruta by default, but also other source =
folders since I can think of users that rather interpet ruta files as =
resources than as program code. Thus, they want to place it somewhere =
under src/main/resources. Complete support has maybe to wait for the =
release after next.

Well, ruta is a script-based language. So I would expect that ruta files =
are copied verbatim from whatever folder they are in to target/classes =
anyway.

It is probably a good best practice to let ruta scripts live in packages =
(cf. Java packages), so they should probably merge nicely into the =
classpath - as ruta files, which would effectively be resources. Mind =
that you can even consider ".class" files as resources.

The distinction into src/main/java and src/main/resources was imho made =
mainly to separate (Java-)code from non-code. Ruta is definitely code, =
so src/main/ruta makes a lot of sense to me.
For other languages, we have e.g. src/main/groovy (and there are =
probably src/main/scala or src/main/flex, etc.). This makes it easier =
for language-specific Maven plugins to locate the code they are supposed =
to operate on.

In which case would you prefer to store stuff in src/main/resources?

Cheers,

-- Richard