Mailing-List: contact users-help@maven.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Maven Users List" <users@maven.apache.org>
Received-SPF: pass (hermes.apache.org: local policy)
Mime-Version: 1.0 (Apple Message framework v619)
In-Reply-To: <00a001c4f99d$f7de4fe0$500312ac@sagunto>
References: <00a001c4f99d$f7de4fe0$500312ac@sagunto>
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <3C4E2C68-65D6-11D9-8AF5-000A95CFE5AA@roderickmann.org>
Content-Transfer-Encoding: 7bit
From: Rick Mann <rmann@roderickmann.org>
Subject: Re: Maven help for building 2 versions for a component build
Date: Thu, 13 Jan 2005 18:44:39 -0800
To: "Maven Users List" <users@maven.apache.org>


On Jan 13, 2005, at 10:30, Eric Pugh wrote:

> You could, I guess..  Really though, what makes the two projects
> different?

Well, I don't know about the original poster's situation, but we have 
an API in a JAR file that we give out for public use and that we use 
internally. However, the internal JAR includes a couple of additional 
class files that we don't want to distribute outside.

I haven't yet built this API with maven, and am not sure how I will. I 
guess the "right" way is to put the additional files in a new, separate 
project (meaning separate, parallel directory structure), and build it 
with a dependency on the public API. Just seems like a lot of work for 
a couple of classes...

-- 
Rick


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org