To sum it up. I've asked the very same question a few weeks ago. That
has lead to creating that maven-3.x-next branch. A few weeks later I get
a different answer and that branch becomes obsolete and all JIRA issues
for version 3.5.0 need updating and the branch can be deleted, because
it became mea
Am 11/16/16 um 00:42 schrieb Christian Schulte:
> tracked with. Can we please line up all of this with everyone and with
> whatever changes others have in mind.
By this I mean the following. If the import scope behaviour cannot be
changed to what was done for MNG-5971 in any Maven 3.x version and
Am 11/15/16 um 23:41 schrieb Jason van Zyl:
>
> You obviously don’t work with anyone who has a system with any number of
> users. No one has said the system cannot change, but you repeatedly keep
> changing stuff that potentially has huge impacts on users and it doesn’t
> bother you at all. I j
> On Nov 15, 2016, at 12:31 PM, Christian Schulte wrote:
>
> Am 11/15/16 um 17:17 schrieb Jason van Zyl:
>> -1
>>
>> No one has likely to have read the information
>
> The reporter of the issue clearly has ;-)
>
>> and you’re reasoning is illogical.
>
> Making Maven behave as advertised and
Am 11/15/16 um 17:17 schrieb Jason van Zyl:
> -1
>
> No one has likely to have read the information
The reporter of the issue clearly has ;-)
> and you’re reasoning is illogical.
Making Maven behave as advertised and as requested isn't that illogical,
IMHO.
> Repeatedly you seem not to care if
-1
No one has likely to have read the information and you’re reasoning is
illogical. Repeatedly you seem not to care if you’re going to break a users
build because of lack of adherence to what you think is right.
What’s “right” is the way it currently works within this minor version.
> On Nov
+1
On 13 November 2016 at 10:23, wrote:
> Hi,
>
> We solved 14 issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> projectId=12317923&version=12335570&styleName=Text
>
> There are still a couple of issues left in JIRA:
> https://issues.apache.org/jira/issues/?jql=project%20%
> 3D
here is my +1
Regards,
Hervé
- Mail original -
De: "herve boutemy"
À: "Maven Developers List"
Envoyé: Dimanche 13 Novembre 2016 00:23:50
Objet: [VOTE] Release Apache Maven Site Plugin version 3.6
Hi,
We solved 14 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectI
I like the new description
What I still don't understand is "Since they are replaced, dependencies with a
scope of <<>> do not actually participate in limiting the transitivity
of a dependency.": what's the intent with this?
Regards,
Hervé
- Mail original -
De: schu...@apache.org
À: co
Github user hboutemy commented on the issue:
https://github.com/apache/maven/pull/94
yes: now that ASF Jenkins shows me it works not only on my Linux box but
also on ASF Linux and on Windows, I just closed the Jira issue
---
If your project is set up for it, you can reply to this ema
Github user michael-o commented on the issue:
https://github.com/apache/maven/pull/94
@hboutemy Are you waiting for the Jenkins build to close the JIRA issue?
@rpatrick00 Thank you for the contribution.
---
If your project is set up for it, you can reply to this email and have your
r
Github user stdweird commented on the issue:
https://github.com/apache/maven-surefire/pull/110
@Tibor17 i almost don't dare to ask, but is there any release coming up
with this fix?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub
12 matches
Mail list logo
