Kenney Westerhof wrote: >Hi there, > >Just tried to bootstrap m2 HEAD (r170983) (with clean repo) and it failed. >Didn't want to make this a JIRA issue (yet).. Below a description, >and a question about m2 versioning. Sorry if this is supposed to be posted >to the users@ list.. > > Nope, this is correct.
>First the compilation error: >maven-site-plugin depends on maven-reporting-api 2.0-alpha-2, >which does not have 2 methods defined in MavenReportConfiguration; >the output (see http://rafb.net/paste/results/N8VhdB30.html) >didn't clarify much - only after loading it in eclipse the error >became evident (probably an issue on it's own :)). >After updating the version to 2.0-SNAPSHOT it compiled fine. > > This seems to have been an error during the last change - as you'll see the CI build failed because of this too. >Now for my question: >I've asked this before on #maven, but never got a straight answer: >How do you approach the versioning of modules in m2? > >The current versioning of modules is unclear to me: plugins have >the following versions: > >1.0-alpha-2-SNAPSHOT >1.0-SNAPSHOT >2.0-alpha-2-SNAPSHOT >2.0-alpha-3-SNAPSHOT > >whereas for example maven-reporting(-api) lack versions and use the >2.0-SNAPSHOT version defined in the parent pom. > > The use of 2.0-SNAPSHOT in our POMs is because I've been lazy. I've agreed to update this after the next release (but right now, it'd just be busy work...). So the policy is "XXX-SNAPSHOT means development progressing towards version XXX". So, Maven should have version 2.0-alpha-3-SNAPSHOT right now. After the next release, it will be 2.0-beta-1-SNAPSHOT. >Maven-site-plugin depends on maven-reporting-api 2.0-alpha-2, >and I can't find that that version was ever assigned to that module >in the svn history. > It's there: http://svn.apache.org/repos/asf/maven/components/tags/maven-2.0-alpha-2 I made the version change as I did the svn copy. In hindsight, this is confusing, so I won't do it again. >- How did maven-reporting-api 2.0-alpha-2 get on ibiblio when all I can >find is versioning 2.0 in the source tree? > > see above. >- If you want to separate plugin development from the core development, >why not use separate repositories? Doing so prevents programming against >api's in the current checkout, which does not match the version the module >depends on.. > > will do (there is a JIRA to shuffle things around) >- If not, why not use SNAPSHOT everywhere? > > As you guessed abve, its because the plugins aren't tied to the Maven release. >- Why are there different versions used througout the repository (and I'm >not only talking about core/plugin separation). > > > the versions are ok - each plugin can have a different one. I'm just not following our own conventions with 2.0-SNAPSHOT. >Either you guys make a mess of versions in the repository, or I'm >completely missing something here.. > > Bit of both :) >I know it's not really my concern (I should just stick to whatever you >officially release) but i'd like to learn about how a big project like >this is organized.. > > Not at all, its great to see you taking this level of interest. Cheers, Brett --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
