+1
Regards,
Hervé
Le mardi 7 janvier 2014 19:22:38 domi a écrit :
> Hi,
>
> We fixed 11 issues. The new feature is the jgit provider (based on jgit).
> Details:
> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10527&version=187
> 83
>
> Staging repository:
> https://repository.apac
+1
On 8 January 2014 05:22, domi wrote:
> Hi,
>
> We fixed 11 issues. The new feature is the jgit provider (based on jgit).
> Details:
> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10527&version=18783
>
> Staging repository:
> https://repository.apache.org/content/repositories/mave
I like "Nike" style issues (just commit it)
On Tuesday, 7 January 2014, Michael Osipov wrote:
> Am 2014-01-07 22:38, schrieb Stephen Connolly:
>
>> Add it if you promise to implement it, otherwise put it against 3.2.x for
>> the patch releases.
>>
>
> That is not going to be a problem because I h
Done, as well as updating the board report
Robert
Op Tue, 07 Jan 2014 11:04:53 +0100 schreef Tony Chemit
:
On Mon, 6 Jan 2014 21:17:03 +0100
Tony Chemit wrote:
Could a PCM update the release board for those two releases.
Thanks.
tony.
Hi,
The vote has passed with the following result
Am 2014-01-07 22:38, schrieb Stephen Connolly:
Add it if you promise to implement it, otherwise put it against 3.2.x for
the patch releases.
That is not going to be a problem because I have a patch and can commit
right away.
On Tuesday, 7 January 2014, Michael Osipov wrote:
Am 2014-01-07
Add it if you promise to implement it, otherwise put it against 3.2.x for
the patch releases.
On Tuesday, 7 January 2014, Michael Osipov wrote:
> Am 2014-01-07 16:25, schrieb Stephen Connolly:
>
>> OK we are now at 38 open issues anyone else feel like scrubbing some
>> more?
>>
>
> I'd like t
Am 2014-01-07 16:25, schrieb Stephen Connolly:
OK we are now at 38 open issues anyone else feel like scrubbing some
more?
I'd like to add another issue to 3.2:
https://jira.codehaus.org/browse/MNG-5176 Print build times in an ISO
8601-style manner
It adds readability to the time output.
For the last surefire releases, I just created a tar.gz from the local
site, uploaded it to people.a.o via SCP and did the commit from there. Was
a matter of minutes instead of hours. It's cumbersome, though...
A pretty large part of the files is the Javadoc. And I don't know about you
guys, but I
+1
2014/1/7 domi
> Hi,
>
> We fixed 11 issues. The new feature is the jgit provider (based on jgit).
> Details:
>
> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10527&version=18783
>
> Staging repository:
> https://repository.apache.org/content/repositories/maven-009/
>
> Staged s
Doxia was at least 1.5hr for me, so 2h wouldn't surprise me at all.
On Tuesday, 7 January 2014, Dominik Bartholdi wrote:
> Thanks Oliver!
> It just hanged for more then two hours, then I just stopped it - sorry if
> this was too short, I did not expect it to take as long.
> /Domi
>
> On 07.01.201
Thanks Oliver!
It just hanged for more then two hours, then I just stopped it - sorry if this
was too short, I did not expect it to take as long.
/Domi
On 07.01.2014, at 08:28, Hervé BOUTEMY wrote:
> in the short term, Olivier did the publication: job done
>
> but let's understand what "does n
Hi,
We fixed 11 issues. The new feature is the jgit provider (based on jgit).
Details:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10527&version=18783
Staging repository:
https://repository.apache.org/content/repositories/maven-009/
Staged site: http://maven.apache.org/scm-archive
For everything that is not claimed in a couple days can move to 3.2.x and that
gets it out of the 3.2.0 bucket, and from there you can percolate up to 4.x.
On Jan 7, 2014, at 11:47 AM, Stephen Connolly
wrote:
> * http://jira.codehaus.org/browse/MNG-656 lazily resolve extensions
>
>Not sur
* http://jira.codehaus.org/browse/MNG-656 lazily resolve extensions
Not sure that this is a reasonable ask. Moving to 4.x anyway
* http://jira.codehaus.org/browse/MNG-4508 No way to avoid adding
artifactId to site urls
I think this is a 4.x candidate... objections?
* http://jira.codehau
* http://jira.codehaus.org/browse/MNG-5185 Improve "missing dependency"
error message when _maven.repositories/_remote.repositories contains other
repository ids than requested
The attached patch does not address the real issue, namely being able
to define specific repo id's as offline. I woul
I'm going to work on the couple issues have assigned to me, and possibly work
on one issue with Robert. Most likely be wrapped up by the end of the week. I'm
going to wait until Aether 1.0.0 before I update it again.
On Jan 7, 2014, at 11:02 AM, Stephen Connolly
wrote:
> * http://jira.codehau
>
> * http://jira.codehaus.org/browse/MNG-5356 Make encrypt/decrypt logic
> pluggable
>
> Seems like something that could be in scope. Any takers?
>
We already have a (I think) working fix for this in the git repo linked to
in the comments. However, jvz suggested moving this to a separate comp
* http://jira.codehaus.org/browse/MNG-5378 Use m-s-u in core
ACTION: krosenv to provide status update
* http://jira.codehaus.org/browse/MNG-5353 Ignore pre-releases in exclusive
upper bound [lw,up)
ACTION: jvzyl will we be upping Aether to M4, in which case that will
expose an alternativ
On 7 Jan 2014, at 15:39, Stephen Connolly
wrote:
> * http://jira.codehaus.org/browse/MNG-4171 The XML resulting from a property
> of java.util.Properties is a lot more clumsy than that for Map
>
>Unsure what the ask is here... seems like it's really a plexus
> compatibility layer issue
F
I stepped up big time and moved MNG-5356 (Make encrypt/decrypt logic
pluggable) to the 4.x list. :-)
/Anders
On Tue, Jan 7, 2014 at 4:25 PM, Stephen Connolly <
stephen.alan.conno...@gmail.com> wrote:
> OK we are now at 38 open issues anyone else feel like scrubbing some
> more?
>
>
>
> On 7
* http://jira.codehaus.org/browse/MNG-3695 Allow dependencies' scopes to be
managed without explicit versions
This does not affect the pom schema, but potentially affects other POM
parsers. My instinct is that this is for 4.x not 3.2
* http://jira.codehaus.org/browse/MNG-3321 Skip plugin and/
* http://jira.codehaus.org/browse/MNG-2478 add filtered resource
directories to super POM
Moved to 4.x bucket as requires pom model change
* http://jira.codehaus.org/browse/MNG-426 create "maxmem" setting for all
plugins to refer to
I think this is now out of scope for core... but I woul
* http://jira.codehaus.org/browse/MNG-2381 Improved control over the
repositories in the POM
Unsure what the ask is here
* http://jira.codehaus.org/browse/MNG-4506 Split site deployment URLs into
release vs. snapshot, just like artifacts
Moved to 4.x bucket as requires pom model change
I will scrub throughout the day, I have removed all issues assigned to me I'm
not planning on working on.
On Jan 7, 2014, at 10:25 AM, Stephen Connolly
wrote:
> OK we are now at 38 open issues anyone else feel like scrubbing some
> more?
>
>
>
> On 7 January 2014 15:25, Stephen Connolly
OK we are now at 38 open issues anyone else feel like scrubbing some
more?
On 7 January 2014 15:25, Stephen Connolly
wrote:
> Done
>
>
> On 7 January 2014 14:43, Jason van Zyl wrote:
>
>> Seems reasonable. Go for it.
>>
>> On Jan 7, 2014, at 7:43 AM, Stephen Connolly <
>> stephen.alan.conn
On 7 January 2014 12:43, Stephen Connolly
wrote:
> AFAIU this is the current list of bugs:
> http://jira.codehaus.org/issues/?jql=project%20%3D%20MNG%20AND%20fixVersion%20%3D%20%223.2%22%20AND%20(status%20%3D%20Open%20OR%20status%20%3D%20%22In%20Progress%22%20or%20status%3DReopened)%20ORDER%20BY%2
Done
On 7 January 2014 14:43, Jason van Zyl wrote:
> Seems reasonable. Go for it.
>
> On Jan 7, 2014, at 7:43 AM, Stephen Connolly <
> stephen.alan.conno...@gmail.com> wrote:
>
> > AFAIU this is the current list of bugs:
> >
> http://jira.codehaus.org/issues/?jql=project%20%3D%20MNG%20AND%20fix
Sounds good to me.
/Anders
On Tue, Jan 7, 2014 at 1:43 PM, Stephen Connolly <
stephen.alan.conno...@gmail.com> wrote:
> AFAIU this is the current list of bugs:
>
> http://jira.codehaus.org/issues/?jql=project%20%3D%20MNG%20AND%20fixVersion%20%3D%20%223.2%22%20AND%20(status%20%3D%20Open%20OR%20s
Seems reasonable. Go for it.
On Jan 7, 2014, at 7:43 AM, Stephen Connolly
wrote:
> AFAIU this is the current list of bugs:
> http://jira.codehaus.org/issues/?jql=project%20%3D%20MNG%20AND%20fixVersion%20%3D%20%223.2%22%20AND%20(status%20%3D%20Open%20OR%20status%20%3D%20%22In%20Progress%22%20or%
AFAIU this is the current list of bugs:
http://jira.codehaus.org/issues/?jql=project%20%3D%20MNG%20AND%20fixVersion%20%3D%20%223.2%22%20AND%20(status%20%3D%20Open%20OR%20status%20%3D%20%22In%20Progress%22%20or%20status%3DReopened)%20ORDER%20BY%20priority%20DESC
I propose that the following issues
On Mon, 6 Jan 2014 21:17:03 +0100
Tony Chemit wrote:
Could a PCM update the release board for those two releases.
Thanks.
tony.
> Hi,
>
> The vote has passed with the following result:
>
> +1 (binding): Hervé BOUTEMY, Olivier Lamy, Stephen Connolly
> +1 (non binding): Karl Heinz Marbaise, T
31 matches
Mail list logo
