Am 2013-12-16 23:35, schrieb Stephen Connolly:
I have been playing with reworking our front page...[image: Inline images 1]
I think the fluido skin is a big improvement, I would like to switch to
that...
Only problem I see is that our current logo(s) are very tied to the old
look and feel...
Hi PMCs,
please reply to my promotion in
https://issues.apache.org/jira/browse/INFRA-7120. I'd like to manage
release just like on Codehaus JIRA.
I need to release Maven Skins Parent 8.
Thanks,
Michael
-
To unsubscribe, e-
The Apache Maven team is pleased to announce the release of the Maven
Skins Parent version 8
http://maven.apache.org/pom/skins/
You should specify the version in your project's configuration:
org.apache.maven.skins
maven-skins
8
Enjoy,
-The Apache Maven team
--
The Apache Maven team is pleased to announce the release of the Maven
Fluido Skin, version 1.3.1
http://maven.apache.org/skins/maven-fluido-skin/
You should specify the version in your project's site configuration:
org.apache.maven.skins
maven-fluido-skin
1.3.1
Release Notes - Maven F
Hi,
The vote has passed with the following result:
+1 (binding): Olivier Lamy, Hervé Boutemy, Kristian Rosenvold
+1 (non-binding): Maarten Storm
I will promote the artifacts to the central repo.
PMCs please promote the source release ZIP file and add this release the
board report.
--
The Apache Maven team is pleased to announce the release of the Apache
Maven JXR, version 2.4
This module generates browsable HTML pages from Java source code.
http://maven.apache.org/jxr/
You should specify the version in your project's plugin configuration:
org.apache.maven.plugins
mav
I don't think this is eclipse-specific, but IBM did analysis of
java-based API evolution and documented the results at eclipse [1].
The document is quite thorough and I usually use it as a reference when
I need to develop API for long-term maintenance.
The "2 Convention" is explained in the part
Sure, it'll take time, but the good news is Java8's default methods are
certainly going to progressively cause deprecation of that
convention/naming convention.
2013/12/20 Igor Fedorenko
> I don't think this is eclipse-specific, but IBM did analysis of
> java-based API evolution and documented
Java 8 isn't out yet... Maven is still limited java 5... so yeah, we'll
get there... eventually... around 2023 or so.
Please excuse my sarcasm, I just couldn't resist :-)
--
Regards,
Igor
On 12/20/2013, 9:40, Baptiste Mathus wrote:
Sure, it'll take time, but the good news is Java8's default me
Well, Maven is already voted to go onto Java6 from now on ;-).
Anyway, as I say, I know this isn't for tomorrow. But there's another
thing, there was not a lot of exciting features attracting developers
between Java 5 and 7 (Coin was too small to really be a major reason for a
mainstream migration
So I introduced MojoExecutionEvent and ProjectExecutionEvent [1].
As I already explained, this makes it somewhat hard(er) to know what
parameters each of the callback methods gets. Anyone who implements
these interfaces will have to look inside maven core to see what gets
passed in.
[1]
https:/
I would move the Raven closer to the word Maven but otherwise this looks
good imho. Of course I am not sure if everyone would recognize it as a
raven ..
manfred
> http://people.apache.org/~stephenc/maven-logo-contest/maven-6.png
>
> http://people.apache.org/~stephenc/maven-logo-contest/maven-7.pn
On Dec 20, 2013, at 1:01 PM, Manfred Moser wrote:
> I would move the Raven closer to the word Maven but otherwise this looks
> good imho. Of course I am not sure if everyone would recognize it as a
> raven ..
That’s my problem…. doesn’t look like a raven to me at all.
When I first looked at i
>
> On Dec 20, 2013, at 1:01 PM, Manfred Moser
> wrote:
>
>> I would move the Raven closer to the word Maven but otherwise this looks
>> good imho. Of course I am not sure if everyone would recognize it as a
>> raven ..
>
> Thats my problem
. doesnt look like a raven to me at all.
>
> When I fi
Github user hgschmie closed the pull request at:
https://github.com/apache/maven-surefire/pull/30
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
I think we can't go with the raven
http://www.prweb.com/releases/2012/3/prweb9334175.htm
Given that a different non-competing user of the name is using a raven in
their logo
On Friday, 20 December 2013, Manfred Moser wrote:
> >
> > On Dec 20, 2013, at 1:01 PM, Manfred Moser
> >
> >
> > wr
Now that's a nice logo, bummer they beat us.
http://thewatchers.adorraeli.com/2013/03/27/maven-gets-magnetometers-to-study-the-red-planets-magnetic-field/
And another cool logo gone.
Robert
Op Fri, 20 Dec 2013 22:28:19 +0100 schreef Stephen Connolly
:
I think we can't go with the raven
Yep.. you are probably right. We could ask but I doubt they would allow it
...
manfred
> I think we can't go with the raven
>
> http://www.prweb.com/releases/2012/3/prweb9334175.htm
>
> Given that a different non-competing user of the name is using a raven in
> their logo
>
> On Friday, 20 De
I think we can't go with the raven
http://www.prweb.com/releases/2012/3/prweb9334175.htm
Given that a different non-competing user of the name is using a raven in
their logo
On Friday, 20 December 2013, Manfred Moser wrote:
> >
> > On Dec 20, 2013, at 1:01 PM, Manfred Moser
> >
> >
> > wr
GitHub user ctubbsii opened a pull request:
https://github.com/apache/maven/pull/11
MNG-4226 Detect JAVA_HOME on newer Mac OS X
This patch falls back on the system configured JVM for the current
user, only when no prior methods for detecting JAVA_HOME succeed.
If one of
> Date: Fri, 20 Dec 2013 13:01:54 -0500
> Subject: Re: New logo?
> From: manf...@simpligility.com
> To: dev@maven.apache.org
> CC: manf...@simpligility.com
>
> I would move the Raven closer to the word Maven but otherwise this looks
> good imho. Of course I am not sure if everyone would recogni
21 matches
Mail list logo
