On Saturday, 11 October 2014, Michael Osipov wrote:
> Am 2014-10-11 um 21:28 schrieb Robert Munteanu:
>
>> On Sat, Oct 11, 2014 at 10:23 PM, Michael Osipov
>> wrote:
>>
>>>
>>> Well said...
>>> I guess it is all about the order of the words: Maven X Plugin. It simply
>>> implies that is provided
GitHub user Tibor17 opened a pull request:
https://github.com/apache/maven-surefire/pull/57
[SUREFIRE-1105] Surefire build should check Java 1.5 API signatures with
JDK version > 5
The Maven Surefire project should use animal-sniffer-maven-plugin to check
Java 1.5 API signatures.
Hi,
On 10/11/14 10:00 PM, Michael Osipov wrote:
Am 2014-10-11 um 21:51 schrieb Robert Scholte:
[...]
maven/site/trunk/content/apt/guides/plugin/guide-java-plugin-development.apt
(original)
+++
maven/site/trunk/content/apt/guides/plugin/guide-java-plugin-development.apt
Sat Oct 11 18:31:32 20
Am 2014-10-11 um 21:51 schrieb Robert Scholte:
[...]
maven/site/trunk/content/apt/guides/plugin/guide-java-plugin-development.apt
(original)
+++
maven/site/trunk/content/apt/guides/plugin/guide-java-plugin-development.apt
Sat Oct 11 18:31:32 2014
@@ -508,6 +508,44 @@ mvn archetype:generate \
Hi Robert,
> Hi Karl-Heinz,
did you use the cms[1][2] to change this?
I'd like to change 'rot' to 'red' so all colors are non-german ;)
Sure it should be non-german ...Thanks for finding this...
Fixed in SVN...
Kind regards
Karl-Heinz marbaise
thanks,
Robert
[1] https://cms.apache.org/ma
Hi Karl-Heinz,
did you use the cms[1][2] to change this?
I'd like to change 'rot' to 'red' so all colors are non-german ;)
thanks,
Robert
[1] https://cms.apache.org/maven/
[2] http://maven.apache.org/developers/website/deploy-maven-website.html
Op Sat, 11 Oct 2014 20:31:33 +0200 schreef :
Au
Am 2014-10-11 um 21:28 schrieb Robert Munteanu:
On Sat, Oct 11, 2014 at 10:23 PM, Michael Osipov wrote:
Well said...
I guess it is all about the order of the words: Maven X Plugin. It simply
implies that is provided by the Maven team. Which is not.
But is the order relevant in the artifactId
On Sat, Oct 11, 2014 at 10:23 PM, Michael Osipov wrote:
>
> Well said...
> I guess it is all about the order of the words: Maven X Plugin. It simply
> implies that is provided by the Maven team. Which is not.
But is the order relevant in the artifactId or in the public display
name? I think it's
Am 2014-10-11 um 21:03 schrieb Benson Margulies:
I am very tempted to reopen the trademark question here. It seems to
me that this whole business ignores the groupId component of the name,
which distinguishes pretty clearly, and I would argue is enough to
avoid trademark dillution.
Well said...
I am very tempted to reopen the trademark question here. It seems to
me that this whole business ignores the groupId component of the name,
which distinguishes pretty clearly, and I would argue is enough to
avoid trademark dillution.
On Sat, Oct 11, 2014 at 2:57 PM, Michael Osipov wrote:
> I'd l
Hi,
On 10/11/14 7:08 PM, Kristian Rosenvold wrote:
Excellent work Karl ! I particularly like the "3" bump in version numbers.
We'll resume the "java6" discussion (and 3.0.5 minimum...?) once all
this is landed.
Yes of course we should do so...
I just bumped everything in surefire to 2.2.1
I'd like to sum up the consensus we have hopefully reached already:
1. Make maven-plugin-plugin fail the build if the plugin being build
does not adhere to our convention (next minor version).
2. Warn a user when a build is performed with a plugin which violates
the naming convention, just like
Am 2014-10-11 um 18:39 schrieb Karl Heinz Marbaise:
Hi,
i want to summarize the current state of the maven plugins which can be
found here: http://maven.apache.org/plugins/ which are currently
at the Maven 2.2.1 minimum prerequesites state and which are not.
The following list of plugins do no
Piñata encodes as NFC on my mac, which is correct. I am not sure if
the NFD issue is for older macs, but at least it looks good here.
Kristian
2014-10-10 18:22 GMT+02:00 Stefan Bodewig :
> On 2014-10-10, Kristian Rosenvold wrote:
>
>> I will investigate some modern windows. I suppose this may co
Excellent work Karl ! I particularly like the "3" bump in version numbers.
We'll resume the "java6" discussion (and 3.0.5 minimum...?) once all
this is landed.
I just bumped everything in surefire to 2.2.1, there's a release "in
progress" there.
Kristian
2014-10-11 18:39 GMT+02:00 Karl Heinz
I would be perfectly happy to fail the builds of plugin owners as a first
step. Make it so.
I just want an additional JIRA created to emit a warning in core, to be
scheduled in some future release (even as far out as 4.0), least we lose
track of the next step.
On Oct 11, 2014 1:30 AM, "Hervé BOUTE
Hi,
i want to summarize the current state of the maven plugins which can be
found here: http://maven.apache.org/plugins/ which are currently
at the Maven 2.2.1 minimum prerequesites state and which are not.
The following list of plugins do not have a Maven 2.2.1 prerequisites
they have the p
Hi,
I need one more binding vote...
On 10/8/14 7:36 PM, Karl Heinz Marbaise wrote:
Hi,
We solved 15 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11150&version=19421
There are still a couple of issues left in JIRA:
http://jira.codehaus.org/issues/?jql=project%20%3D%20MW
The Apache Maven team is pleased to announce the release of the
Apache Maven Linkcheck Plugin, version 1.2
This plug-in allows you to generate a Linkcheck report of your project's
documentation using the Doxia Linkcheck Tool.
http://maven.apache.org/plugins/maven-linkcheck-plugin/
You should sp
Hi,
The vote has passed with the following result:
+1 (binding): Robert Scholte, Karl Heinz Marbaise, Hervé Boutemy
+1 (non binding): none.
I will promote the artifacts to the central repo.
Kind regards
Karl Heinz Marbaise
-
Hi,
here is my +1.
On 10/8/14 7:36 PM, Karl Heinz Marbaise wrote:
Hi,
We solved 15 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11150&version=19421
There are still a couple of issues left in JIRA:
http://jira.codehaus.org/issues/?jql=project%20%3D%20MWAR%20AND%20status
The Apache Maven team is pleased to announce the release of the
Apache Maven Source Plugin, version 2.4
The Resources Plugin handles the copying of project resources to the output
directory.
http://maven.apache.org/plugins/maven-source-plugin/
You should specify the version in your project's p
Hi,
The vote has passed with the following result:
+1 (binding):
Kristian Rosenvold,
Stephen Connoly,
Hervé Boutemy,
Karl Heinz Marbaise
+1 (non binding): none
I will promote the artifacts to the central repo.
Kind regards
Karl Heinz Marbaise
--
Hi Hervé,
On 10/11/14 9:00 AM, Hervé BOUTEMY wrote:
Log:
- Fixed several Checkstyle errors.
notice that these are errors *reported by* Checkstyle, not really Checkstyle
errors
Checkstyle should add "don't shoot the messenger" disclaimer ;)
I don't shoot the messagernever..already fi
Github user asfgit closed the pull request at:
https://github.com/apache/maven-surefire/pull/56
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature
GitHub user llebegue opened a pull request:
https://github.com/apache/maven-scm/pull/23
SCM-764 : Fix password displayed in cl.toString()
Fixes SCM-764 by subclassing Plexus CommandLine in order to implement a
toString() method that won't display the password.
You can merge this pu
Github user llebegue closed the pull request at:
https://github.com/apache/maven-scm/pull/22
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is
+1
--
Olivier
On 9 Oct 2014 04:03, "John Casey" wrote:
> Hi,
>
> We solved 5 issues:
>
> http://jira.codehaus.org/secure/ReleaseNote.jspa?
> projectId=11130&version=19091
>
> There are still plenty of issues left in JIRA:
>
> http://jira.codehaus.org/secure/IssueNavigator.jspa?
> reset=true&pid=
> Log:
> - Fixed several Checkstyle errors.
>
notice that these are errors *reported by* Checkstyle, not really Checkstyle
errors
Checkstyle should add "don't shoot the messenger" disclaimer ;)
I report here because next maven-parent version will enable Checkstyle check
on every build: we mus
29 matches
Mail list logo
