Am 2016-10-16 um 11:16 schrieb Andreas Dangel:
Hi,
I'm currently in the process of publishing m-pmd-p 3.7 - and for some
steps, I need support:
* "Copy the source release to the Apache Distribution Area" - I guess,
this always needs to be done by a PMC member. It's already synced to
central
Am 2016-10-16 um 11:16 schrieb Andreas Dangel:
Hi,
I'm currently in the process of publishing m-pmd-p 3.7 - and for some
steps, I need support:
* "Copy the source release to the Apache Distribution Area" - I guess,
this always needs to be done by a PMC member. It's already synced to
central
Le dimanche 16 octobre 2016 14:55:12 Michael Osipov a écrit :
> Am 2016-10-16 um 11:16 schrieb Andreas Dangel:
> > Hi,
> >
> > I'm currently in the process of publishing m-pmd-p 3.7 - and for some
> > steps, I need support:
> >
> > * "Copy the source release to the Apache Distribution Area" -
The Maven team is pleased to announce the release of the Apache Maven
PMD Plugin, version 3.7
A Maven plugin for the PMD toolkit, that produces a report on both code
rule violations and detected copy and paste
fragments, as well as being able to fail the build based on these metrics.
Thanks! I just sent out the annoucement. The cms.a.o publish action was
indeed the bit, I missed.
Michael updated Jira for me, so everything is in place now.
Cheers,
Andreas
Am 16.10.2016 um 15:16 schrieb Hervé BOUTEMY:
> Le dimanche 16 octobre 2016 14:55:12 Michael Osipov a écrit :
>> Am
this event will happen on November 16-18:
http://events.linuxfoundation.org/events/apachecon-europe
Robert will do a talk (and I'll help him as I can):
http://sched.co/8ULK
I just updated Wiki page for the event:
https://cwiki.apache.org/confluence/display/MAVEN/Meetups
Who will attend in
Github user asfgit closed the pull request at:
https://github.com/apache/maven-plugins/pull/20
---
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
Hi,
The vote has passed with the following result:
+1 : Olivier Lamy, Hervé Boutemy, Arnaud Héritier
PMC quorum: reached
I will promote the artifacts to the central repo.
Am 10.10.2016 um 20:15 schrieb Andreas Dangel:
> Hi,
>
> We solved 11 issues:
>
Github user asfgit closed the pull request at:
https://github.com/apache/maven/pull/86
---
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
Adding a section to the wiki to help track this
https://cwiki.apache.org/confluence/display/MAVEN/POM+Model+Version+5.0.0
On 16 October 2016 at 04:12, Christian Schulte wrote:
> Am 10/16/16 um 02:03 schrieb Stephen Connolly:
> >> On 16 Oct 2016, at 00:07, Christian Schulte
Let us know your cwiki username and we can grant permission to edit
On Sunday 16 October 2016, Christofer Dutz
wrote:
> Hi guys,
>
>
> I just wanted to add one thing to the list:
>
> https://issues.apache.org/jira/browse/MNG-6107
>
> But I can't edit or comment on the
Hi Stephen,
My Username is "cdutz".
Chris
Von: Stephen Connolly
Gesendet: Sonntag, 16. Oktober 2016 13:49:39
An: Maven Developers List
Betreff: Re: Some thoughts on Maven 5
Let us know your cwiki username and we can grant
Hi guys,
I just wanted to add one thing to the list:
https://issues.apache.org/jira/browse/MNG-6107
But I can't edit or comment on the page:
https://cwiki.apache.org/confluence/display/MAVEN/POM+Model+Version+5.0.0
Chris
Von: Stephen Connolly
Hi,
I'm currently in the process of publishing m-pmd-p 3.7 - and for some
steps, I need support:
* "Copy the source release to the Apache Distribution Area" - I guess,
this always needs to be done by a PMC member. It's already synced to
central [1].
* "Update the version tracking in JIRA" -
I'm kind of against includes and import... I favour mix-ins as the solution
to that set of problems...
Additionally I see all the "hacks" people have evolved as been
significantly less relevant with PDTs including both ranges and hints as
well as the provides and supports declarations... but yes
Karl/John can you give permissions to edit (or at least comment) to
Christofer
Also perhaps we should add all the PMC as owners of the space
On Sunday 16 October 2016, Christofer Dutz
wrote:
> Hi Stephen,
>
>
> My Username is "cdutz".
>
>
> Chris
>
>
Hi,
I've updated Java9/Jigsaw confluence page[1].
A new chapter has been added: a list of third party libraries where our
projects depend on (though most are related to integration tests,
compile-time is still looking fine), starting with the causes of failing
integration tests of the
Hi folks,
are we going to incorporate v 1.2 of Resolver into Maven 3.4? I've seen
that Christian done some fixing required by some MNGs as well as our
rebranding of the project. Some dependencies need to be updated to match
Maven's but it would be a good test having it in 3.4-0-rc-1.
WDYT?
+1
On Sun, 16 Oct 2016 21:13:53 +0200, Stephen Connolly
wrote:
http://wilderness.apache.org/
Just found out about this... should we request to get this setup for our
two IRC channels on freenode?
My vote is yes
Sent from my iPhone
Btw: Do you know why and where system properties are being removed?
Am 10/16/16 um 01:40 schrieb gb...@apache.org:
> Repository: maven
> Updated Branches:
> refs/heads/master f7c1359cf -> ace448158
>
>
> [MNG-6105] properties.internal.SystemProperties.addSystemProperties() is
> not really
Am 2016-10-16 um 18:39 schrieb Christian Schulte:
Btw: Do you know why and where system properties are being removed?
This is still the question and I would like to have an answer for.
Am 10/16/16 um 01:40 schrieb gb...@apache.org:
Repository: maven
Updated Branches:
refs/heads/master
Hi,
with the introduction of the module-info something interesting is
happening. Up until now the scope of a Java project was limited to the
compilation of the classes. In case of Maven the end-user was in full
control regarding the classpath and the order of entries. With the order
of
http://wilderness.apache.org/
Just found out about this... should we request to get this setup for our two
IRC channels on freenode?
My vote is yes
Sent from my iPhone
-
To unsubscribe, e-mail:
Hi,
There is an issue on Plexus Archiver about that when
ZipArchiver.setUpdateMode() is set to true, the original archive is
overridden instead of updated -
https://github.com/codehaus-plexus/plexus-archiver/issues/2 As the issue
is over an year old and it did not receive much attention I
INFRA-12772
On 16 October 2016 at 20:43, Robert Scholte wrote:
> +1
>
>
> On Sun, 16 Oct 2016 21:13:53 +0200, Stephen Connolly <
> stephen.alan.conno...@gmail.com> wrote:
>
>
>> http://wilderness.apache.org/
>>
>> Just found out about this... should we request to get this
Am 10/16/16 um 22:51 schrieb Michael Osipov:
> Am 2016-10-16 um 22:48 schrieb Christian Schulte:
>> Will the resolver be upgraded to Java 7? I would use 'java.util.Objects'
>> then.
>
> I have the very same idea. I wouldn't mind using j.u.Objects instead of
> o.a.c.l4.Validate.
>
> Is there any
Github user asfgit closed the pull request at:
https://github.com/apache/maven-plugins/pull/17
---
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 gmcdonald closed the pull request at:
https://github.com/apache/maven-plugins/pull/29
---
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
Github user gmcdonald closed the pull request at:
https://github.com/apache/maven-plugins/pull/26
---
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
Github user gmcdonald closed the pull request at:
https://github.com/apache/maven-plugins/pull/37
---
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
Github user gmcdonald closed the pull request at:
https://github.com/apache/maven/pull/66
---
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
Am 2016-10-16 um 22:48 schrieb Christian Schulte:
Will the resolver be upgraded to Java 7? I would use 'java.util.Objects'
then.
I have the very same idea. I wouldn't mind using j.u.Objects instead of
o.a.c.l4.Validate.
Is there any compelling reason not to switch to Java 7? NIO2 and
Github user gmcdonald closed the pull request at:
https://github.com/apache/maven-plugins/pull/75
---
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
Github user gmcdonald closed the pull request at:
https://github.com/apache/maven-plugins/pull/65
---
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
Github user gmcdonald closed the pull request at:
https://github.com/apache/maven-plugins/pull/84
---
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
Github user gmcdonald closed the pull request at:
https://github.com/apache/maven-plugins/pull/60
---
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
Github user gmcdonald closed the pull request at:
https://github.com/apache/maven-plugins/pull/1
---
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
Will the resolver be upgraded to Java 7? I would use 'java.util.Objects'
then.
Am 10/16/16 um 22:30 schrieb Michael Osipov (JIRA):
> Michael Osipov created MRESOLVER-4:
> --
>
> Summary: Use Commons Lang's Validate to intercept invalid input
>
Let's just go for Java 7... this is linked to core... if you are stuck on
an older Java likely you can't upgrade Maven anyway
On Sunday 16 October 2016, Christian Schulte wrote:
> Am 10/16/16 um 22:51 schrieb Michael Osipov:
> > Am 2016-10-16 um 22:48 schrieb Christian Schulte:
GitHub user lbreuss reopened a pull request:
https://github.com/apache/maven-plugins/pull/29
MPDF-66 maven-pdf-plugin puts project.properties into Velocity context.
It works. Are there any side effects to be expected by putting all
project.properties into the renderer context?
You
Github user gmcdonald closed the pull request at:
https://github.com/apache/maven-plugins/pull/29
---
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
Github user gmcdonald closed the pull request at:
https://github.com/apache/maven-plugins/pull/76
---
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
Github user gmcdonald closed the pull request at:
https://github.com/apache/maven-shared/pull/11
---
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
Github user gmcdonald closed the pull request at:
https://github.com/apache/maven-doxia-sitetools/pull/3
---
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
Github user asfgit closed the pull request at:
https://github.com/apache/maven-plugins/pull/69
---
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
Am 10/16/16 um 21:43 schrieb Michael Osipov:
> Hi folks,
>
> are we going to incorporate v 1.2 of Resolver into Maven 3.4? I've seen
> that Christian done some fixing required by some MNGs as well as our
> rebranding of the project. Some dependencies need to be updated to match
> Maven's but
Am 10/16/16 um 23:51 schrieb Stephen Connolly:
> Let's just go for Java 7... this is linked to core... if you are stuck on
> an older Java likely you can't upgrade Maven anyway
+1
-
To unsubscribe, e-mail:
Am 10/15/16 um 16:26 schrieb Stephen Connolly:
> Thinking out loud... perhaps something like
>
> [version="..."] packaging="...">
> [ [relativePath="...']/>
>
> []
> []
> ...
> []
Looking at this from a syntax point of view only, we will run into those
"XML element declaration order
Am 10/15/16 um 15:20 schrieb Stephen Connolly:
> * Pom doesn't need to be XML any more... (maybe we want to keep XML though...
> just a less verbose form)
Maybe XML really isn't the way to go. Whenever I look at an XML file, it
appears to be a mixture of meta-data, data and behaviour/logic. Last
Am 10/15/16 um 19:32 schrieb Stephen Connolly:
> I'm thinking that we still want a dependency management section
I think dependency management is a must have. That's a build tool
feature to allow overriding dependency details from the consumed PDT.
What is different here is that instead of having
Hello Hervé,
I would like a simple approach here. If I understand it correctly, gossip
was chosen because of its color capability. If we could have this without
switching the log provider it would be a good thing IMO. Gossip seems to be
unconfigurable by means of system properties, which is a
51 matches
Mail list logo