You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by Dennis Lundberg <de...@apache.org> on 2007/03/03 00:57:01 UTC
Releasing JXR 1.1
Hi
I'd like to release JXR 1.1. All issues scheduled for that version has
been solved. Before I start a vote I thought I'd ask if someone needs
any of the remaining unscheduled issues [1] solved in version 1.1. None
of the remaining bugs seem very dangerous.
[1]
http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&mode=hide&sorter/order=DESC&sorter/field=priority&resolution=-1&pid=11085&fixfor=-1
--
Dennis Lundberg
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Releasing JXR 1.1
Posted by Dennis Lundberg <de...@apache.org>.
Arnaud HERITIER wrote:
> On 3/5/07, Brett Porter <br...@apache.org> wrote:
>>
>>
>> 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?
>
>
> If we can build the JXR plugin for maven 1 with maven 2, let's go for it
> ;-)
> We'll just deprecate our code and we'll update our plugins list descriptor
> to bundle it in the next release.
> It's not in our interest to duplicate a plugin. We have enough work with
> all
> the others.
>
> Arnaud
I'll try to see if I can get this to work, starting with a temporary
copy of the Maven 1 plugin. If I get that working, I'll get back and we
can discuss how to best do the subversion migration and plugin-bundling
in Maven 1.
<snip/>
--
Dennis Lundberg
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Releasing JXR 1.1
Posted by Arnaud HERITIER <ah...@gmail.com>.
On 3/5/07, Brett Porter <br...@apache.org> wrote:
>
>
> 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?
If we can build the JXR plugin for maven 1 with maven 2, let's go for it ;-)
We'll just deprecate our code and we'll update our plugins list descriptor
to bundle it in the next release.
It's not in our interest to duplicate a plugin. We have enough work with all
the others.
Arnaud
>
> > 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: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
Re: Releasing JXR 1.1
Posted by Brett Porter <br...@apache.org>.
On 11/03/2007, at 3:20 PM, Dennis Lundberg wrote:
> I'm just about done with moving stuff in SVN and adjusting the poms
> accordingly. I did not change the groupId for either jxr or the jxr-
> plugin. Let me know if I should.
Should be fine.
>
> The sites for jxr and jxr-plugin looks good, but I want to do some
> more checking, then I'll publish the one for jxr.
Sounds good.
>
> When it comes to adjusting continuum, I'm gonna need some help. I
> don't know what to change and where to do it :(
Actually, it's still down, I haven't had any time to recover the
database.
- Brett
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Releasing JXR 1.1
Posted by Dennis Lundberg <de...@apache.org>.
I'm just about done with moving stuff in SVN and adjusting the poms
accordingly. I did not change the groupId for either jxr or the
jxr-plugin. Let me know if I should.
The sites for jxr and jxr-plugin looks good, but I want to do some more
checking, then I'll publish the one for jxr.
When it comes to adjusting continuum, I'm gonna need some help. I don't
know what to change and where to do it :(
Brett Porter wrote:
>
> 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: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
--
Dennis Lundberg
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Releasing JXR 1.1
Posted by Brett Porter <br...@apache.org>.
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: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Releasing JXR 1.1
Posted by Dennis Lundberg <de...@apache.org>.
Brett Porter wrote:
> Is the patch on -16 any good? That's the only one I'd move to fix.
It was already fixed in SVN.
> -14 can probably be closed - it's either a findbugs problem, or a
> duplicate of -11.
-14 and -11 were similar. I have fixed both of them.
> The rest are feature requests, so I'd leave them for the future.
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.
> 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).
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. 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.
> From there, it's just the usual license stuff to check at release and I
> think it's good.
>
> Thanks for working on it!
>
> - Brett
>
> On 03/03/2007, at 7:57 AM, Dennis Lundberg wrote:
>
>> Hi
>>
>> I'd like to release JXR 1.1. All issues scheduled for that version has
>> been solved. Before I start a vote I thought I'd ask if someone needs
>> any of the remaining unscheduled issues [1] solved in version 1.1.
>> None of the remaining bugs seem very dangerous.
>>
>> [1]
>> http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&mode=hide&sorter/order=DESC&sorter/field=priority&resolution=-1&pid=11085&fixfor=-1
>>
>>
>> --Dennis Lundberg
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
--
Dennis Lundberg
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Releasing JXR 1.1
Posted by Brett Porter <br...@apache.org>.
Is the patch on -16 any good? That's the only one I'd move to fix.
-14 can probably be closed - it's either a findbugs problem, or a
duplicate of -11.
The rest are feature requests, so I'd leave them for the future.
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?
From there, it's just the usual license stuff to check at release
and I think it's good.
Thanks for working on it!
- Brett
On 03/03/2007, at 7:57 AM, Dennis Lundberg wrote:
> Hi
>
> I'd like to release JXR 1.1. All issues scheduled for that version
> has been solved. Before I start a vote I thought I'd ask if someone
> needs any of the remaining unscheduled issues [1] solved in version
> 1.1. None of the remaining bugs seem very dangerous.
>
> [1] http://jira.codehaus.org/secure/IssueNavigator.jspa?
> reset=true&mode=hide&sorter/order=DESC&sorter/
> field=priority&resolution=-1&pid=11085&fixfor=-1
>
> --
> Dennis Lundberg
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org