Hi,
As told in INFRA-16467 thread, I'll do parent POMs releases soon.
Please update parent POMs as you want the release to be done: I'll start by
Apache parent in a few days: see the diff against Apache 19 [1]
and the site https://maven.apache.org/pom-archives/asf-LATEST/
Once Apache parent 20
just tested the full component documentation lifecycle for Maven [1] and Doxia
[2]: works like a charm
*IMPORTANT NOTICE: you'll have to delete your ~/maven-sites cache*
since the cache contains svn checkouts to the old location, that will be
updated: you need to delete to make the checkouts
+1 tested on my projects and mojo and all is green :)
Le mar. 19 juin 2018 07:01, Karl Heinz Marbaise a
écrit :
> Hi,
>
> here is my +1
>
> Tested on several projects without any issue...
>
> Kind regards
> Karl Heinz Marbaise
> On 17/06/18 22:44, Stephen Connolly wrote:
> > Hi,
> >
> > We
Hi,
here is my +1
Tested on several projects without any issue...
Kind regards
Karl Heinz Marbaise
On 17/06/18 22:44, Stephen Connolly wrote:
Hi,
We solved 16 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12342826=Text=12316922
There are 356 issues left in JIRA for
Hi,
As you may have noticed from a load of commits, the location for html
publication of components documentation is switching from CMS space to ASF
repo, as requested by INFRA when working on site migration from svn to Git.
see https://issues.apache.org/jira/browse/INFRA-16467
Please wait a
+1 (non-binding) tested on windows/linux using a large multi-module build
with Takari's smart builder and verified the Jansi multi-threaded fix for
Windows
-D
On Mon, Jun 18, 2018 at 10:32 AM, Sylwester Lachiewicz <
slachiew...@gmail.com> wrote:
> +1 (non binding)
> Sylwester
>
> pon., 18 cze
+1 (non binding)
Sylwester
pon., 18 cze 2018 o 11:02 użytkownik Enrico Olivelli
napisał:
> +1 (non binding)
>
> checked signatures and hash of staged artifacts
> I have used the staged binary artifacts to build a bunch of projects on
> Linux (Fedora 26), all ok
>
> We could also consider not to
Il lun 18 giu 2018, 11:24 Stephen Connolly
ha scritto:
> On Mon, 18 Jun 2018 at 10:02, Enrico Olivelli wrote:
>
> > +1 (non binding)
> >
> > checked signatures and hash of staged artifacts
> > I have used the staged binary artifacts to build a bunch of projects on
> > Linux (Fedora 26), all ok
comtention commented on issue #11: Propagate exceptions to caller
URL: https://github.com/apache/maven-doxia/pull/11#issuecomment-398056960
I have exactly the same issue, it is really blocking for me.
This is an automated
On Mon, 18 Jun 2018 at 10:02, Enrico Olivelli wrote:
> +1 (non binding)
>
> checked signatures and hash of staged artifacts
> I have used the staged binary artifacts to build a bunch of projects on
> Linux (Fedora 26), all ok
>
> We could also consider not to deliver md5 hash anymore (
>
+1 (non binding)
checked signatures and hash of staged artifacts
I have used the staged binary artifacts to build a bunch of projects on
Linux (Fedora 26), all ok
We could also consider not to deliver md5 hash anymore (
https://www.apache.org/dev/release-signing.html)
Enrico
Il giorno dom 17
Hi Tibor,
Thanks.
Kind regards
Karl Heinz Marbaise
On 18/06/18 09:30, Tibor Digana wrote:
Hi Karl,
yes the JUnit5 provider should work with Failsafe too.
T
On Sun, Jun 17, 2018 at 9:05 PM, Karl Heinz Marbaise
wrote:
Hi Tibor,
I have a short question:
My assumption is that in
Hi Karl,
yes the JUnit5 provider should work with Failsafe too.
T
On Sun, Jun 17, 2018 at 9:05 PM, Karl Heinz Marbaise
wrote:
> Hi Tibor,
>
> I have a short question:
>
> My assumption is that in maven-failsafe the Junit 5 provider/plattform
> will be enabled the same way as in
13 matches
Mail list logo
