Yes, tags are cheap so can be kept until no longer useful.
If there are a lot of stale tags it can get difficult to navigate the
tags directory, so it makes sense to delete all but the successful tag
once the vote has completed.
There should be no need to keep failed tags once the vote is complete.
Sounds a good idea for me (probably until someone else complain :-) ).
And if that stop discussions and move people to working on code/fixing
issues (i.e something very important for users) that will be great!
2013/6/27 Mirko Friedenhagen :
> Hello there,
>
> when. respinning a release it would o
On 26 June 2013 23:54, wrote:
> Author: olamy
> Date: Wed Jun 26 22:54:24 2013
> New Revision: 1497151
>
> URL: http://svn.apache.org/r1497151
> Log:
> add a link to sources to get a bit of peace (I hope at least for few days :-))
-1
wrong URL.
> Modified:
> maven/site/trunk/content/xdoc/d
Hello there,
when. respinning a release it would of help IMO instead of deleting the tag
to rename it to e.g. maven-javadoc-plugin-2.9-rc1 using "svn mv".
By means of this you are able to easily diff between e.g. released 2.8 and
the final 2.9 as well as between 2.9-rc1 and the final 2.9.
Regard
I will resurrect the performance framework that Igor build long ago. I should
be running it when major changes are made. I'll report back later this week. I
need to find an old, crappy machine to run them on to gauge the difference
accurately.
On Jun 26, 2013, at 8:23 AM, Jörg Schaible wrote:
On Wednesday, 26 June 2013, Barrie Treloar wrote:
> On 26 June 2013 18:44, sebb > wrote:
> > Howewer the ASF releases source.
> > If you don't provide a download link to the source how are users
> > supposed to find it?
> >
> > I agree that most people are not going to want to download the origina
Oops. It appears the standard heap dump toosl don't really dump
permgen, so that's not going to get us anywhere.
I usually do this in jprofiler, maybe someone else has a suggestion :)
Kristian
2013/6/26 Kristian Rosenvold :
> Funny in a sort of ironic way, permgen is noticeably better in 3.1
Funny in a sort of ironic way, permgen is noticeably better in 3.1 for
my usecases :)
The simplest way to get (my) attention to this issue is to create 2
heap dumps of your maven process, one after "some time" and the other
just before it runs out of permgen.
("some time" is supposed to be well i
Are you able to provide standalone example project that demonstrates the
problem?
--
Regards,
Igor
On 2013-06-26 4:23 PM, Jörg Schaible wrote:
Hi Jason,
Jason van Zyl wrote:
Doesn't see to be a whole lot of activity around the 3.1.0-alpha-1 so I
plan to cut the 3.1.0-beta-1 this weekend if t
Hi Jason,
Jason van Zyl wrote:
> Doesn't see to be a whole lot of activity around the 3.1.0-alpha-1 so I
> plan to cut the 3.1.0-beta-1 this weekend if there are no objections.
Apart from the reported bogus build with snapshots (MNG-5207) it seems M31
has a major problem with PermGen space leak
On 26 June 2013 18:44, sebb wrote:
> Howewer the ASF releases source.
> If you don't provide a download link to the source how are users
> supposed to find it?
>
> I agree that most people are not going to want to download the original
> source.
> But that does not mean it should be left unlinked
On 26 June 2013 10:56, Chris Graham wrote:
> On Wed, Jun 26, 2013 at 7:06 PM, sebb wrote:
>
>> I meant: if the pom is created with the correct final URLs in the
>> first place, it won't have to be changed.
>>
>>
> They are. If you'd used the release plugin, then you would have seen this.
>
I was
On 26 June 2013 02:59, Barrie Treloar wrote:
>>> Then replace
>>> cd target/checkout && mvn clean deploy -Papache-release
>>> with
>>> delete target/checkout
>>> svn co to target/checkout
>>> mvn clean deploy -Papache-release
>>>
>>> Since it was mvn release:perform that created target/checkout i
On Wed, Jun 26, 2013 at 7:06 PM, sebb wrote:
> I meant: if the pom is created with the correct final URLs in the
> first place, it won't have to be changed.
>
>
They are. If you'd used the release plugin, then you would have seen this.
> It might need a tweak to the appropriate plugin, but it's
On 26 June 2013 02:48, Barrie Treloar wrote:
> On 26 June 2013 10:48, sebb wrote:
>> The point is that the ASF release source, and it must be provided for
>> download via the ASF mirrors.
>>
>> See:
>>
>> http://www.apache.org/dev/release.html#host-GA
>>
>> If you don't point users to the source,
I meant: if the pom is created with the correct final URLs in the
first place, it won't have to be changed.
It might need a tweak to the appropriate plugin, but it's not
impossible to achieve.
The same process would work with the system used by Lucene.
On 26 June 2013 06:48, Hervé BOUTEMY wrote
On Tue, 25 Jun 2013 22:23:13 +0200
"Robert Scholte" wrote:
+1,
tony.
> Hi,
>
> We solved 15 issues:
> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11530&version=19011
>
> There are still a couple of issues left in JIRA:
> http://jira.codehaus.org/secure/IssueNavigator.jspa?reset
On Tue, 25 Jun 2013 22:52:31 +0200
"Robert Scholte" wrote:
+1
tony.
> +1
>
> Op Tue, 25 Jun 2013 08:46:21 +0200 schreef Ralph Goers
> :
>
> > KEYS file - http://svn.apache.org/repos/asf/maven/project/KEYS
> >
> > svn tag -
> > http://svn.apache.org/repos/asf/maven/plugins/tags/maven-javad
18 matches
Mail list logo
