Benson Margulies wrote:
Hi,
We solved 1 issues:
** Improvement
* [MPOM-12] - Update maven-plugins to new org.apache.maven:maven-parent:20
The jira for MPOM is now at apache, so in case anybody else is looking
for it at codehaus, here's the link:
https://issues.apache.org/jira/browse/M
Benson Margulies wrote:
Hi,
The vote has passed with the following result :
+1 (binding):Stephen Connolly, Olivier Lamy,
Kristian Rosenvold, Lukas Theussl,
Dennis Lundberg, John Casey
+1 (not binding): Benson Margulies, Mark Struberg,
For the record: my vote is not binding, but Mark's is
Hi,
We solved 1 issues:
** Improvement
* [MPOM-12] - Update maven-plugins to new org.apache.maven:maven-parent:20
There are no open JIRAs against the maven-plugins parent.
http://svn.apache.org/viewvc/maven/pom/trunk/maven/pom.xml?r1=1135900&r2=1135901&diff_format=h
Staging repo:
https://re
Hi,
The vote has passed with the following result :
+1 (binding):Stephen Connolly, Olivier Lamy,
Kristian Rosenvold, Lukas Theussl,
Dennis Lundberg, John Casey
+1 (not binding): Benson Margulies, Mark Struberg,
I will promote the artifacts to the central repo.
-
Looks like 8*+1, and nothing else. So the vote to release
org.apache.maven:maven-parent version 20 passes.
On Tue, Jun 14, 2011 at 3:41 PM, John Casey wrote:
> +1
>
> On 6/13/11 4:07 AM, Stephen Connolly wrote:
>>
>> it is custom to include the viewcvs diff link when voting on the
>> release of o
Hi,
I assume that this is only a problem based on the sync...but on the page:
http://people.apache.org/~brianf/enforcer-stage/plugins/maven-enforcer-plugin/plugin-info.html
the link "Standard rules" contains a link which produces an "Not found!"...
Also the "Custom Rules" -> "Writing a custom r
Hi,
Staging repo:
https://repository.apache.org/content/repositories/maven-011/
Staging site: (Sync pending)
http://people.apache.org/~brianf/enforcer-stage/plugins/maven-enforcer-plugin/
I assume that this is only a problem based on the sync...but on the page:
http://people.apache.org/~brian
Hi,
We solved 17 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10541&version=17312
There are still a couple of issues left in JIRA:
http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&mode=hide&jqlQuery=project+%3D+SUREFIRE+AND+resolution+%3D+Unresolved+ORDER+BY+up
Hi,
We solved/improved quite a few things. Issue tracking does not seem to
be actively used for this project, svn log attached below
Staging repo:
https://repository.apache.org/content/repositories/maven-012/
Staging site: (Sync pending)
http://maven.apache.org/shared/maven-verifier-1.3/
Guid
Hi,
We solved 1 issue:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11391&version=17198
There are still 2 issues left in JIRA:
http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&mode=hide&jqlQuery=project+%3D+MRRESOURCES+AND+resolution+%3D+Unresolved+ORDER+BY+updated+DES
Hi,
We solved 2 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11530&version=16879
There are still a couple of issues left in JIRA:
http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&mode=hide&jqlQuery=project+%3D+MENFORCER+AND+resolution+%3D+Unresolved+ORDER+BY+up
+1
On 6/13/11 4:07 AM, Stephen Connolly wrote:
it is custom to include the viewcvs diff link when voting on the
release of one of the parent poms.
In this case here is the link:
http://svn.apache.org/viewvc/maven/pom/trunk/maven/pom.xml?r1=1134934&r2=1069626&diff_format=h
On 12 June 2011 16:3
+1
To avoid confusion in the future, please don't use the word "shared"
when releasing maven-parent. We have a parent for our shared components
as well...
On 2011-06-12 17:31, Benson Margulies wrote:
> Hi,
>
> We solved 1 issues:
>
> ** Improvement
> * [MPOM-11] - Update to compile with/for
Mark, without being a lawyer, my guess is that you mean "no one can
sue you successfully", as opposed to "no one can sue you". And I'm
sure that any reasonable person would try to avoid even the former.
Jochen
On Tue, Jun 14, 2011 at 9:58 AM, Mark Struberg wrote:
> No Robert!
>
> Even in the U
I asked the author about this. His response is below. I propose to
just copy the source into the bridge. It's an acceptable license small
quantity inclusion (the friendly BSD version). Clean-rooming a new
version with the same bugs does not strike me as reasonable.
Hi,
CachedMap was provided in ol
(Apoligies for allowing this to drifting off topic after I failed to
make my main point)
IMHO bait-and-switch licensing isn't something to panic about today
but better license management is something that Maven should think
about enabling. This would offer users protection from similar tactics
in
No Robert!
Even in the UK after enforcing a few cracy things recently, no one can sue you
for downloading something in good faith.
Of course they can force you to not use it in the future - like everywhere else.
LieGrue,
strub
--- On Tue, 6/14/11, Robert Burrell Donkin
wrote:
> From: Robert
On Mon, Jun 13, 2011 at 3:09 PM, Benson Margulies wrote:
> The legal risk involved in downloading and using a jar of code pushed
> to central under false pretenses is very small.
I live in the UK. That's now untrue here.
Robert
---
Hi,
The vote has passed with the following result :
+1 (binding): Mark Struberg, Hervé Boutemy, Olivier Lamy, Brett Porter
+1 (non binding): Jesse Glick, Brian Demers, Damian Bradicich
I will promote the artifacts to the central repo.
Thanks,
~t~
-
19 matches
Mail list logo