Ah. I misunderstood. I thought you meant it wouldn't pull in dependencies. No, the repository only makes sense for things that can be dependencies, or are used in building or deploying artifacts.
My two current projects are a cross-platform look and feel for Swing, and a recipe program. The look and feel makes sense to have in a repository, but I have no intention of ever deploying the recipe program. (In fact, I'm hoping to sell it.) But it would never go into a repository if you don't install it or deploy it. Why would you do that? Why do you need an option to not put it into a repository? -K On Apr 6, 2010, at 2:52 PM, Ludwig Magnusson wrote: > Why? > I will never have a project that depends on the webapp I'm creating. That's > one reason. > I really don't understand the policy here. > You might not see the the value and the value might not be big, but is that > a reason for not adding a simple, already implemented feature? Maven can be > used by many different projects and situations might occur where > installation is not necessary. > > What is the reason for not putting the feature in? Will it lower the value > of the plugin? > /Ludwig > > -----Original Message----- > From: Kathryn Huxtable [mailto:kath...@kathrynhuxtable.org] > Sent: den 6 april 2010 21:32 > To: Maven Users List > Subject: Re: mvn install - skipping modules that only contain test code > > But why would anyone care what gets pulled into the local repository? I'm > with Wayne on this one. That's how Maven works. > > An artifact is like a point in spacetime. It has coordinates and is > immutable. You might need it later and it'll be there. And if not, so what? > > -K > > On Apr 6, 2010, at 2:28 PM, Ludwig Magnusson wrote: > >> I recently submittet a patch in JIRA that added a "skip" flag. This > skipped installation in the local repository for artifacts. >> /Ludwig >> >> -----Original Message----- >> From: Wayne Fay [mailto:wayne...@gmail.com] >> Sent: den 6 april 2010 20:59 >> To: Maven Users List >> Subject: Re: mvn install - skipping modules that only contain test code >> >>> At present the install goal copies all the test jars to the local > repository. >>> >>> Is there any way of skipping the install phase for these modules? >> >> Does it really hurt to copy them to the local repo? This is how Maven > works. >> >> Wayne >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org >> For additional commands, e-mail: users-h...@maven.apache.org >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org >> For additional commands, e-mail: users-h...@maven.apache.org >> > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
