On 26 Aug 2016, at 22:07, Tibor Digana wrote:
> One or two years ago I watched mvn dev hangouts videos with Jason and
Were they really that long ago? Wow. I was actually thinking about them the
other day, wondering when/why they petered out, I ended up having to stop
joining due to timezone
On Fri, Aug 26, 2016, at 12:51 AM, Michael Osipov wrote:
> Am 2016-08-25 um 23:20 schrieb Hervé BOUTEMY:
> > ok, we can change groupId
> >
> > everybody ok for:
> > - name: "Artifact Resolver"
>
> Not Maven Artifact Resolver?
>
> > - groupId: org.apache.maven.resolver
> > - artifactId:
Hi,
We solved 16 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317820=12331169=Text
There are still a couple of issues left in JIRA:
>>How can I submit a patch
Just push you commit and in the webpage https://github.com//maven-plugins
you will see a hint to open pull request.
Name it "[MCHANGES-373] ".
Done.
>>and integrate it
The ASF PMC and committers will integrate it.
>> and test it
You should run :
mvn -Prun-its verify
everybody ok for:
- name: "Artifact Resolver"
- groupId: org.apache.maven.resolver
- artifactId: resolver(-*)
Why not more formal like:
-name: Maven Artifact Resolver
-groupId: org.apache.maven.[artifact | resolver]
-artifactId: artifact-resolver
-- barthel
Hi,
We are trying to use 2.12 of this plugin.
I notice that the filter that we set in not applied at all.
I found the following bug report:
MCHANGES-373: It is not possible to use "filter" parameter
I checked code and I can see that the jql query is missing the filter parameter
to be set in
One or two years ago I watched mvn dev hangouts videos with Jason and
Karl and others and there we mentioned the need for BOM. I understood
that BOM is similar to dependencyManagement different from typical
POM. In the video they wanted to solve some problem with dependencies
resolutions.
Do we
