On 04/03/2007, at 4:05 PM, Dennis Lundberg wrote:
I found a couple of other bugs while testing, that I also fixed. I
feel pretty much done now. Snapshots have been deployed so that'll
give it some testing.
cool, thanks for this!
How about moving the plugin into the same source tree and
releasing a unified version, as we are doing with all the others
like surefire?
Sure that can be done. That'd be a unified version of 2.1 I guess,
since that is the largest version of the two (jxr is at 1.1-
SNAPSHOT and jxr-plugin is at 2.1-SNAPSHOT).
Yeah - though it raises the question of what to do with the maven1
plugin. We could pull that in too, build it with the maven-one-
plugin, and give it a version of 2.1 as well, using group ID to
differentiate. Not sure how Arnaud and Lukas feel about that?
There are a few things that I have stumbled on lately that needs to
be addressed when doing such a move, pom-wise, but I think I've got
it covered.
Cool. Basically, just the different distribution management for the
plugin site and adjustments to the parent pom since the plugin will
no longer inherit from the maven-plugins one.
What would be a good structure for it? Something like this perhaps:
jxr
|
+-- maven-jxr
|
+-- maven-jxr-plugin
I haven't done a lot of svn moving so I'd appreciate some help with
this.
That looks about right. The tricky thing is that you are basically
moving jxr/trunk to jxr/trunk/maven-jxr (ie, under itself), so you'll
need to do it in a few stages, say:
1) create jxr/new-trunk
2) mv jxr/trunk to jxr/new-trunk/maven-jxr
3) mv plugins/maven-jxr-plugin to jxr/new-trunk/maven-jxr-plugin
4) mv new-trunk to trunk
these can all be done server side (using 2 URLs) to make it faster.
Then update locally and adjust the poms. And continuum :)
- Brett
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
