Depend on this project's classes during its build vs. its artifact during other builds??

2005-03-28 Thread Jubenville, Russ
We have a project, "ProjectA", that contains some JUnit tests, where those tests require our database to be initialized with data. We have a goal called initdb that loads that data, but it needs to use our java classes within ProjectA to accomplish its task. The problem occurs when we need to run

Re: Depend on this project's classes during its build vs. its artifact during other builds??

2005-03-28 Thread dan tran
http://maven.apache.org/using/bestpractices.html#Refactor_Your_Build -D On Mon, 28 Mar 2005 18:02:44 -0500, Jubenville, Russ <[EMAIL PROTECTED]> wrote: > We have a project, "ProjectA", that contains some JUnit tests, where > those tests require our database to be initialized with data. We have

Re: Depend on this project's classes during its build vs. its artifact during other builds??

2005-03-29 Thread Ha ryon
else you could have initdb depend on a property, that you would set in projectA to ${maven.build.dest} and in projectB project.properties you would change it to something else. would it work ? If initbd is called from projectB probably. On Mon, 28 Mar 2005 15:20:50 -0800, dan tran <[EMAIL PROTECT