Hi Todd! maven-scm defines a SPI + a few plugins for various SCMs. But although the name of the project is maven-scm it is not only intended to be used with maven only. There are other projecs (e.g. continuum) which use maven-scm for accessing SCMs without maven.
The maven-scm-plugin on the other side is really a maven-plugin! And maven-scm-plugin uses maven-scm to access the SCM you are using. That's the reason why maven-scm-plugin uses the common parent pom used for all maven-plugins (see maven-plugin-plugin for more details) and maven-scm doesn't. LieGrue, strub --- Todd Thiessen <thies...@nortel.com> schrieb am Di, 13.1.2009: > Von: Todd Thiessen <thies...@nortel.com> > Betreff: RE: SCM plugin project > An: scm-...@maven.apache.org > CC: "Maven Users List" <users@maven.apache.org> > Datum: Dienstag, 13. Januar 2009, 18:47 > I haven't gotten a response from an SCM plugin > development person. > Perhaps someone on the Maven list could guide me in the > right direction. > I would like contribute a fix to the SCM plugin. I am > trying to build > the project but I have questions/issues. Who can I talk to > regarding > these? > > Thanks all. And sorry for creating some noise on the Maven > list. > > --- > Todd Thiessen > > > > -----Original Message----- > > From: Thiessen, Todd (BVW:9T16) > > Sent: Friday, January 09, 2009 5:13 PM > > To: 'scm-...@maven.apache.org' > > Cc: 'Maven Users List' > > Subject: SCM plugin project > > > > I have downloaded the source for this project have and > have a > > number questions/concerns. > > > > Most of the code seems be under the scm directory. ie: > > > > http://svn.apache.org/repos/asf/maven/scm > > > > There is a POM at the highest level, with an artifact > ID of > > maven-scm, which indicates many sub-directories as > sub-modules. > > > > However, there is one sub-module that confuses me: > > maven-scm-plugin. You would normally expect the parent > for > > this pom to be the parent in the higher directory. > > > > However, this isn't the case. Its parent is > maven-plugins > > which is a different artifact altogether. This really > seems > > to make building and versioning of the entire project > confusing. > > > > Do you release the maven-scm project or the > maven-scm-plugin > > project? I naturally expected to release the maven-scm > > > project but the maven-scm-plugin stands out in that it > > > doesn't define maven-scm as the parent and it also > includes > > all the maven-scm submodule projects as dependancies > by > > explicitly specifying their version. How are the > version > > numbers of all these dependencies incremented when a > new > > version of the plugin is released? > > > > --- > > Todd Thiessen > > > > --------------------------------------------------------------------- > 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
