Am 2017-02-13 um 21:36 schrieb Tibor Digana:
I am working with Michael on FreeBSD issues.
I will try to fix one IT today and I will analyse the logs with next two
ITs.
Did we change something regarding SITE in Maven 3.5.0-SNAPSHOT ?
I was able to tackle the constant failure of
I am working with Michael on FreeBSD issues.
I will try to fix one IT today and I will analyse the logs with next two
ITs.
Did we change something regarding SITE in Maven 3.5.0-SNAPSHOT ?
On Mon, Feb 13, 2017 at 6:32 PM, Tibor Digana-2 [via Maven] <
ml-node+s40175n5898532...@n5.nabble.com> wrote:
Github user asfgit closed the pull request at:
https://github.com/apache/maven-surefire/pull/142
---
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 Tibor17 commented on the issue:
https://github.com/apache/maven-surefire/pull/142
@britter
@marcphilipp
Done. We are preparing a new release version of Maven and Surefire was
examined last days. We still investigate some issues.
---
If your project is set up
Hi Michael,
If you will run the build again, this test should not fail. At least I hope
so, because it's ok on my side
Am 02/13/17 um 17:47 schrieb Guo Yunhe:
>> Don't. Don't do the same as done here:
>> https://www.rpmfind.net/linux/RPM/fedora/25/s390x/m/maven-3.3.9-6.fc25.noarch.html
>>
>> The completely disassembled your tarball and build Maven theirselves. This
>> is a non-canoncial build which we are likely
I view this as a must fix
On 13 February 2017 at 10:34, Stuart McCulloch wrote:
> I’ve logged the change in precedence as https://issues.apache.org/
> jira/browse/MNG-6172 since this has the potential to break CI builds
> which relied on the previous last-one-wins behaviour
>
Hi guys,
I'm writing here to ask what I have found is a bug or not. I have a project
and I want to create an archetype out of it. So I use the following command:
mvn archetype:create-from-project
-Darchetype.properties=src/main/resources/archetype.properties
It used to work fine with
> Don't. Don't do the same as done here:
> https://www.rpmfind.net/linux/RPM/fedora/25/s390x/m/maven-3.3.9-6.fc25.noarch.html
>
> The completely disassembled your tarball and build Maven theirselves. This is
> a non-canoncial build which we are likely not going to support! The
> modifications
Hi, I am a contributor of openSUSE Linux. I am packaging maven package.
Building maven from source requires internet connection and downloads extra
packages. However, the openSUSE build server doesn't allow any downloads from
internet while building. So I want to ask if I can build maven
I will push branch SUREFIRE-1322 which has a fix for freebsd.
On Mon, Feb 13, 2017 at 4:49 PM, Michael Osipov <1983-01...@gmx.net> wrote:
> I am currently running a patched version of Maven with the offensive
> commit reverted against Surefire master on FreeBSD 10.3-STABLE. I'll see
> wether
I am currently running a patched version of Maven with the offensive commit
reverted against Surefire master on FreeBSD 10.3-STABLE. I'll see wether this
is the cause in an hour or so.
Michael
> I’ve logged the change in precedence as
> https://issues.apache.org/jira/browse/MNG-6172 since
> Hi, I am a contributor of openSUSE Linux. I am packaging maven package.
>
> Building maven from source requires internet connection and downloads extra
> packages. However, the openSUSE build server doesn't allow any downloads from
> internet while building. So I want to ask if I can build
Michael, can you please connect to IRC mvn dev?
I would like to discuss regarding FreeBSD.
Thx
On Mon, Feb 13, 2017 at 4:49 PM, Michael Osipov <1983-01...@gmx.net> wrote:
> I am currently running a patched version of Maven with the offensive
> commit reverted against Surefire master on FreeBSD
The HEAD in Surefire has a Jira fix 1322 which is using the same IT which
failed on FreeBSD. So I simply included FreeBSD fix in the test
Surefire141PluggableProvidersIT.
I hope you will be happy with that.
The only last IT which fails and I did not have time to investigate is
Am 2017-02-13 um 17:47 schrieb Guo Yunhe:
Don't. Don't do the same as done here:
https://www.rpmfind.net/linux/RPM/fedora/25/s390x/m/maven-3.3.9-6.fc25.noarch.html
The completely disassembled your tarball and build Maven theirselves. This is a
non-canoncial build which we are likely not going
Then don't include it in the distro. Packaging non-standard, possibly
broken, versions in distros is not doing anyone any favors. Users are
better off just downloading for themselves.
On Mon, Feb 13, 2017 at 8:47 AM, Guo Yunhe wrote:
>> Don't. Don't do the same as done
I’ve logged the change in precedence as
https://issues.apache.org/jira/browse/MNG-6172 since this has the potential to
break CI builds which relied on the previous last-one-wins behaviour
On Monday, 13 February 2017 at 06:54, Tibor Digana wrote:
> Exactly this is the problem - forkMode and
Hi Peter,
I would consider this as a Maven Archetype issue.
Regarding the properties, the MavenSession has a deprecated method
getExecutionProperties(), which is split up into getSystemProperties() and
getUserProperties(). When using the Invoker it doesn't make sense to add
19 matches
Mail list logo