My experience has consistently been that if I adapt my projects to Maven instead of vice-versa, life is just peachy. Have yet to come across a circumstance in Maven that hasn't already been solved for. Just go with it.
On Fri, May 28, 2010 at 2:04 PM, Greg Akins <[email protected]> wrote: > On Fri, May 28, 2010 at 1:43 PM, Steve Francolla <[email protected]> > wrote: > > My advice is to fit your needs into Maven's standard directory layout > > (project structure). > > > http://maven.apache.org/guides/introduction/introduction-to-the-standard-directory-layout.html > > Your main source and junit source will fit well there. Unsure how your > > helper classes fit in but it seems to me that the case can probably be > made > > for that to be packaged within the test source branch as well. > > > > That seems like it might work better for my team. I think I'll have a > bit more of a fight if I have to create a separate project. And truth > is, I don't even think these tests get executed anymore. I just need > to keep them intact until I can replace them with something better. > > -- > Greg Akins > > http://insomnia-consulting.org > http://www.pghcodingdojo.org > http://pittjug.dev.java.net > http://twitter.com/akinsgre > http://www.linkedin.com/in/akinsgre >
