Doxia being a generic lib, able to be used in any context and not just maven-
site-plugin, we need to make our own choice on how flexible we want to be
regarding how this API is used in Doxia Sitetools for a site rendering, the
value is set with static value (false) on each source file parsing
w
The tools jar is an old standby, do you need someone to fix a pom to
have the right profile?
On Tue, Jan 26, 2016 at 3:34 PM, Arnaud Héritier wrote:
> No feedback guys ?
>
> On Thu, Jan 21, 2016 at 11:02 PM, Arnaud Héritier
> wrote:
>
>> Build (install -Prun-its) of the PR:
>> Ok with Java 7 an
No feedback guys ?
On Thu, Jan 21, 2016 at 11:02 PM, Arnaud Héritier
wrote:
> Build (install -Prun-its) of the PR:
> Ok with Java 7 and Maven 3.3.9 on MacOS X
> Ko with Java 6 and Maven 3.2.5 on MacOS X
>
> [INFO] Building: MSHADE-185/pom.xml
> [INFO] ..FAILED (1.4 s)
>
> Could not find artifact
Hi Hervé,
based on only the interface it is possible that the Parser implementation
is a singleton.
Is the emitComments meant to be a per-Parser setting or a per-file setting?
thanks,
Robert
Op Sat, 23 Jan 2016 16:48:08 +0100 schreef :
Author: hboutemy
Date: Sat Jan 23 15:48:07 2016
New Re
Am 2016-01-26 um 12:05 schrieb Adrien Rivard:
Hi,
My opinon on that is that you do not need to build actual wars(neither jar
btw) at all when you are developping within Eclipse.
Jetty and tomcat can run on exploded was strucure, and most others servers
have some eclipse tooling.
With a combina
I'm more curious of the growth of "skip" parameters of plugins. Do they
exist really to skip the plugin, or are they really representative of the
desire to skip an entire phase?
On Jan 25, 2016 7:24 PM, "Christopher" wrote:
> On Mon, Jan 25, 2016 at 2:51 PM, Robert Scholte
> wrote:
> > Hi,
> >
>
Hi,
My opinon on that is that you do not need to build actual wars(neither jar
btw) at all when you are developping within Eclipse.
Jetty and tomcat can run on exploded was strucure, and most others servers
have some eclipse tooling.
With a combination of eclipse configuration mecanism,(launch c
Seems 'maven.test.tmpdir' needs to be set for those build jobs. I do not
have permissions to look at the configuration of those build jobs. Using
'/tmp/bootstrap/stderr.log' will not work as multiple jobs running
concurrently would use the same file and run into issues, I guess.
Am 01/26/16 u
