i) This one is correct, the groupId is the company, and possibly a sub-department
<groupId>com.mycompany</groupId> <artifactId>ProjectA</artifactId> <version>1.2</version> By default, the ProjectA-1.2.jar artifact will be created in \ProjectA\target. iii) How should I declare the dependency in my project B? The groupId, artifactid, and version should be the same in the dependency as when it is declared in project A's pom.xml. <dependencies> <dependency> <groupId>com.mycompany</groupId> <artifactId>ProjectA</artifactId> <version>1.2</version> </dependency> </dependencies> iv) Do I need to include the following in Project B's pom.xml? If both projects are built from source at the same time then you do not need to do this, simply create a third parent pom which references these two and builds them both thus project B gets its reference to project A from the local repository. As for #2, are you talking about deploying to your own repository? You should typically not need your own repository to get a build to work unless you need to reference 3rd party artifacts that are not hosted on any public repos. -- View this message in context: http://www.nabble.com/Questions-about-dependencies-and-artifact-publication-tp25300769p25351654.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]
