Everybody has this problem, once they get to the first release of their
application.
You can find lots of discussions about this in the forum archives.
Google is your friend as well.
Profiles are not the way to handle this.
Separate the code from environment.
Make A, B C and "something that uses the data store" without environment
stuff.
Make a separate project for Dev that contains the Dev environment
configuration and depends on "something that uses the data store".jar
that includes A, B and C.
Same for the rest(test, production, etc.)
These will have no code and just configuration files.
Use JNDI or some other method of communicating environment variables.
http://blog.artifact-software.com/tech/?p=150
http://blog.artifact-software.com/tech/?p=58
Ron
On 20/07/2012 11:08 AM, Jeff Sawatzky wrote:
I have multiple projects, lets call them A, B, and C. A is a util project, B is
the data store layer, and C and something that uses the data store. So, A
depends on nothing, B depends on A, and C depends on B. I am also trying to
create multiple builds for different environments, dev, test, production, and
have created related profiles in each project for each build and specify the
dependencies in those profiles. For instance, B-dev-SNAPSHOP depends on
A-dev-SNAPSHOT, and C-dev-SNAPSHOT depends on B-dev-SNAPSHOT. And I specify the
environment through a system property.
The problem I am running into is that when I build C, it includes the dev
profile and adds B-dev-SNAPSHOT as a dependency, but the environment system
property doesn't seem to get passed to the pom of B-dev-SNAPSHOT and therefore
the A-dev-SNAPSHOT dependency isn't included.
Am I going about this the wrong way?
Thanks,
Jeff.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
--
Ron Wheeler
President
Artifact Software Inc
email: [email protected]
skype: ronaldmwheeler
phone: 866-970-2435, ext 102
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
