Yes, that's how to do it. Maven is based around the concept of convention over configuration. If you don't specify the package type, it defaults to 'jar'. That's the behavior you're experiencing. If you want a pom project, you MUST specify 'pom' as package type.
What you're trying to do is what sometimes referred to grouped dependencies. Read more about there here and please understand the drawbacks: http://www.sonatype.com/people/2009/10/maven-tips-and-tricks-grouping-dependencies/ /Anders On Sat, Jan 30, 2010 at 09:14, eyal edri <[email protected]> wrote: > what about setting the packaing to "pom" instead of "jar" ? > > On Sat, Jan 30, 2010 at 8:38 AM, tbee <[email protected]> wrote: > > > > > I have uploaded a swing look-and-feel to our internal repository. The LaF > > contains a main jar plus a separate jar for each skin. In order to > minimize > > the end result, each skin is uploaded separately with its own pom > referring > > to the main jar. > > > > But sometimes I want it all skins, so I figured I create a pom with > refers > > to all skins (which in turn refer to the main), but does not contain any > > artifacts itself. > > > > I can upload the pom without problems, leaving out the packaging. But > when > > refering to it, it tries to download "xxx-all.jar", so it assumes a > default > > packaging. > > > > Is there any way to create such a artifact-less pom? > > -- > > View this message in context: > > http://old.nabble.com/pom-without-artifacts--tp27381618p27381618.html > > Sent from the Maven - Users mailing list archive at Nabble.com. > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [email protected] > > For additional commands, e-mail: [email protected] > > > > > > > -- > Eyal Edri >
