Hi François,
If you have control over report generation, what you can do is add xml
processing instructions into your pom files that your plugin can later
parse out of the xml without interfering with existing pom model.
M2Eclipse uses that approach to add some metadata to plugin executions.
In the past I've used decentxml as a lightweight reader/writer which
retains everything as-is.
https://bitbucket.org/digulla/decentxml/wiki/Home
пт, 30 нояб. 2018 г. в 02:47, Chris Barlock :
> SInce it is XML, you could use the Java DOM or Sax parsers.
>
> Chris
>
>
>
>
> From: Marc Rohlfs
Yeah, that could work as well.
On Tue, 14 Jun 2016, 21:05 Christian Schulte, wrote:
> http://git-wip-us.apache.org/repos/asf/maven/commit/ded1379e
>
>
> -
> To unsubscribe, e-mail:
format is.
On Tue, 14 Jun 2016, 20:37 Christian Schulte, <c...@schulte.it> wrote:
> Am 06/14/16 um 18:46 schrieb Anton Tanasenko:
> > Christian? Anyone?
> >
> > 2016-06-13 1:19 GMT+03:00 Anton Tanasenko <atg.sleepl...@gmail.com>:
> >
> >> I've t
Christian? Anyone?
2016-06-13 1:19 GMT+03:00 Anton Tanasenko <atg.sleepl...@gmail.com>:
> I've tried running m2eclipse tests with 3.4.0-SNAPSHOT maven. There are
> several failures.
>
> 1. src/x/resources-filtered addition, which we will need to adhere to when
> 3.4.0
I've tried running m2eclipse tests with 3.4.0-SNAPSHOT maven. There are
several failures.
1. src/x/resources-filtered addition, which we will need to adhere to when
3.4.0 gets released.
2.
It would be great if there was a way to enable/disable color using a
separate option or system property.
Adding -B could disable color by default, but explicitly enabling it might
prove useful in, say, Jenkins with AnsiColor plugin.
2016-06-12 23:39 GMT+03:00 Baptiste Mathus :
>
Hi,
There is a commit for MNG-2478 which I think could cause problems for
projects that are authored using 3.4.0 and the new resources-filtered
source folder is used (provided it was not configured in the project as
such before). Those projects will not be buildable with prior maven
versions.
This
With eclipse we do autocompletion for nested elements using reflection, if
type information is available (e.g. generics are used for List and Map
elements) in almost the same as in Maven (almost - because maven takes
config and tries to apply each separate value, while from the editor we
need to
Just on a side note, eclipse m2e pom editor does have an autocomplete for
plugin configuration based on the plugin descriptor and the classes that
are used.
+1 to namespace support though, since it could be used to provide
autocomplete for parts that cannot be deduced by looking at the model
This is weird indeed.
iText changed license/package starting from 5 and onwards.
4.2.0 wasn't officially released but sources are there and they are still
under MPL/LGPL and anyone can always build the jar himself [1] and I guess
nothing disallows one to distribute such jar, right?
Someone must've
Hi,
I did some research not so long ago to find out the way managed dependency
versions are resolved and ended up with a following logical lookup
algorithm:
Whichever is encountered first:
1. for each pom up the hierarchy:
a. concrete dependency
b. managed dependency
2. for each pom up the
I observe this happening from time to time when both maven2 and maven3
builds are using the same local repository. Maven2 seems to modify metadata
files in a way that maven3 fails to work with.
Cleaning bogus artifacts from local repo makes the problem go away.
2015-11-09 12:31 GMT+02:00
Hi,
If you remove all traces of jruby-engine from your local repo, you will see
that in second case maven will try to download both pom (which is missing,
more on that below) and the classified jar.
It does not try to download the jar in the first case because it is
referred to from a dependency
schrieb Anton Tanasenko:
Hi,
If you remove all traces of jruby-engine from your local repo, you will
see
that in second case maven will try to download both pom (which is missing,
more on that below) and the classified jar.
It does not try to download the jar in the first case because
goalsgoalunpack/goal/goals
configuration.../configuration
/execution
/executions
/plugin
See, no phase.
2015-06-02 20:16 GMT+03:00 Thomas Meyer tho...@m3y3r.de:
Am 02.06.2015 6:58 nachm. schrieb Anton Tanasenko atg.sleepl...@gmail.com
:
Hi, you probably missed
Hi, you probably missed the previous section:
If you intend to configure this mojo for execution on the command line
using:
mvn dependency:copy
you must not put the configuration inside the executions tag. Your
configuration should look like this:
...
2015-06-02 19:36 GMT+03:00 Thomas Meyer
Hi,
@Parameter annotations are only supported in the mojo itself, not in any
nested parameter beans.
2015-05-23 11:22 GMT+03:00 Karl Heinz Marbaise khmarba...@gmx.de:
Hi,
On 5/23/15 12:32 AM, Cristiano Gavião wrote:
Hello,
I'm facing a problem and would like a help to figure it out.
Shade plugin should pick up reactor dependencies just fine, as long as the
shading module (3 in your case) references the root project (containing
other dependencies) correctly in the parent section.
2015-04-08 21:14 GMT+03:00 Eric Kolotyluk eric.koloty...@gmail.com:
Adrien, while this would
I meant (containing other modules) of course.
2015-04-08 22:17 GMT+03:00 Anton Tanasenko atg.sleepl...@gmail.com:
Shade plugin should pick up reactor dependencies just fine, as long as the
shading module (3 in your case) references the root project (containing
other dependencies) correctly
There's usually a poll on how to name each release. Next after Mars should
be Neptune.
https://www.eclipse.org/mars/planning/poll.php
On Sun, 29 Mar 2015 14:47 Martin Gainty mgai...@hotmail.com wrote:
eclipse had agreed to name released versions of eclipse after moons of
Jupiter (notably
21 matches
Mail list logo