In the past plugins such as the dependency plugin didn't have a way to
affect the reactor build order without having the user add a real dependency
(say test scope) to the module using the plugin (or having the plugin
programatically do the same) just to ensure proper build ordering. I assume
I am building a maven plugin whose output is a directory structure with
various files. As part of an integration test (driven by the shitty
plugin), I would like to compare the output structure/files to those of an
expected structure. I could probably build this up with DirectoryScanner,
but I'm
Creating aggregate reports in maven has historically been a little awkward.
To this end i remember chatter about revamping the reporting framework to
support registering listeners to reports. Has any of this changed?
Will these listeners be provided with the necessary references (Stream,
etc.) to support artifact transformation? In other words, is this a
super-set of the filtering functionality I described?
On Fri, Sep 5, 2008 at 5:15 PM, Oleg Gusakov
[EMAIL PROTECTED]wrote:
Shane Isbell wrote:
Introduction:
What mechanism can be used to store artifacts in the repository which are
sensitive to having versions in the filename? This is a concern for certain
artifacts such as .NET assemblies (particularly closed source 3rd party
assemblies) which contain internal meta-data which is aware
, not presuming anything about where and why the File is.
Mercury is not in the trunk yet, but it's aiming to gradually make there in
not too distant a future.
Thanks,
Oleg
James Carpenter wrote:
Introduction:
What mechanism can be used to store artifacts in the repository which are
sensitive
weeks away. Thanks for all your efforts.
Sincerely,
James Carpenter
email: [EMAIL PROTECTED]
On Fri, Sep 5, 2008 at 12:06 PM, Oleg Gusakov
[EMAIL PROTECTED]wrote:
James Carpenter wrote:
Sounds like good news to me.
Can you please define not too distant a future? Are you talking days,
weeks
I have a plugin which resolves a specified artifact, expands it into a
work area within target and then runs a code generator against contents
within the expanded artifact.
{Specifically the resolved artifact contains an XML-Schema, and the tool
being executed is a csharp xsd tool (similar to
Questions are at the bottom.
==
Summary:
I am considering trying to build a rather large multiproject maven
build in a distributed fashion. I am looking for guidance on how to
best achieve this with a minimal amount of effort. In particular I am
looking for
. If not
then it is apparent I will have to write it if I want to get parallel
distributed builds working. Of course to do that I need to know
exactly what werken distribution maven is using.
I continue to need any guidance the reader can provide.
On Apr 10, 2005 7:04 PM, James Carpenter [EMAIL PROTECTED] wrote
10 matches
Mail list logo