Conflict

2016-11-21 Thread Oulds, Jonathan
Hello there, Is it possible to define a conflict manager only for a specific configuration? When building a module we resolve the "build" configuration of our module, this works fine. However, once the module has been built we sometimes perform some post build steps that perform

Easyant - Plugin conflict management

2013-08-03 Thread Jean-Louis Boudart
module.ant if users has complex needs Additionnal there is two "alliases" for this task to import plugins and buildtype. If organisation attribute is not specified on aliases default one will be used. It does the job but it doesn't handle conflict between plugins. Some pl

Re: Easyant - Plugin conflict management

2013-08-17 Thread Nicolas Lalevée
sk to import plugins and > buildtype. > > > If organisation attribute is not specified on aliases default one will be > used. > > It does the job but it doesn't handle conflict between plugins. > > Some plugins relies on abstract ones. > Exemple: > pa

Re: Easyant - Plugin conflict management

2013-08-20 Thread Jean-Louis Boudart
; > * invoked in module.ant if users has complex needs > > > > Additionnal there is two "alliases" for this task to import plugins and > > buildtype. > > > > > > If organisation attribute is not specified on aliases default one will > be > >

Re: Easyant - Plugin conflict management

2013-08-20 Thread Nicolas Lalevée
t;> hood) >>> >>> This task is currently used : >>> * dynamically by easyant to load system plugins (skeletons for example) >>> * dynamically by easyant when you specify or tags >>> in module.ivy files >>> * invoked in plugin ant file itselfs >&

Re: Easyant - Plugin conflict management

2013-08-26 Thread Dridi Boukelmoune
gt; * import the real ant file (invoke the importTask from ant core under the >>>> hood) >>>> >>>> This task is currently used : >>>> * dynamically by easyant to load system plugins (skeletons for example) >>>> * dynamically by easyant whe

RE: Easyant - Plugin conflict management

2013-08-26 Thread Martin Gainty
e sujets à la manipulation, nous ne pouvons accepter aucune responsabilité pour le contenu fourni. > From: dridi.boukelmo...@zenika.com > Date: Mon, 26 Aug 2013 20:31:32 +0200 > Subject: Re: Easyant - Plugin conflict management > To: dev@ant.apache.org > > Hi, > > This i

Re: Easyant - Plugin conflict management

2013-08-26 Thread Dridi Boukelmoune
on non autorisée ou la copie de ceci > est interdite. Ce message sert à l'information seulement et n'aura pas > n'importe quel effet légalement obligatoire. Étant donné que les email > peuvent facilement être sujets à la manipulation, nous ne pouvons accepter >

Re: Easyant - Plugin conflict management

2013-08-27 Thread Dridi Boukelmoune
of >>> >>>> plugins (including themself others abstract-plugins). What bugs me, is the fact that changing package-jar's version could change my compile-java's version. This is just a caricature, but for me the former creates a zip while the latter invokes javac ;

Re: Easyant - Plugin conflict management

2013-08-28 Thread Jean-Louis Boudart
My answers below 2013/8/26 Dridi Boukelmoune > >> Point 2 : Even if there is no much activity, i suggest to keep backward > >> compatibility > > > > fine for me. > > Not necessary from my point of view. My only advice is to avoid legacy > (or technical debt ;) at such early time. > > I was sugg

Re: Easyant - Plugin conflict management

2013-08-28 Thread Dridi Boukelmoune
On Wed, Aug 28, 2013 at 11:19 AM, Jean-Louis Boudart wrote: > My answers below > > > 2013/8/26 Dridi Boukelmoune > >> >> Point 2 : Even if there is no much activity, i suggest to keep backward >> >> compatibility >> > >> > fine for me. >> >> Not necessary from my point of view. My only advice is

patch (ivy): log conflict results at verbose

2009-01-01 Thread Robey Pointer
o a source of confusion/worry. This patch fixes the log level of these messages so that "conflict" messages aren't displayed in quiet mode. Thanks! robey Index: src/java/org/apache/ivy/core/retrieve/RetrieveEngine.java

Re: patch (ivy): log conflict results at verbose

2009-01-06 Thread Maarten Coene
I'm not convinced that this is the proper way to solve your problem. If they are not conflicts, they shouldn't get logged as conflict. Could you give us more info and an example of your log? Maarten - Original Message From: Robey Pointer To: dev@ant.apache.org Sent: Frida

Re: patch (ivy): log conflict results at verbose

2009-01-06 Thread Robey Pointer
On 6 Jan 2009, at 12:14, Maarten Coene wrote: I'm not convinced that this is the proper way to solve your problem. If they are not conflicts, they shouldn't get logged as conflict. Could you give us more info and an example of your log? I agree, since they aren't conflicts

Re: patch (ivy): log conflict results at verbose

2009-01-07 Thread Maarten Coene
, January 7, 2009 5:29:01 AM Subject: Re: patch (ivy): log conflict results at verbose On 6 Jan 2009, at 12:14, Maarten Coene wrote: > I'm not convinced that this is the proper way to solve your problem. > If they are not conflicts, they shouldn't get logged as conflict. Could you > gi

Re: patch (ivy): log conflict results at verbose

2009-01-08 Thread Xavier Hanin
These log messages are confusing, beacause they are not resolve time conflicts, but retrieve time conflicts: when Ivy retrieves a set of artifact, if it has to retrieve two artifacts to the same location, it complains about a conflict. For instance if you have a dependency on acme#foo;1.0 in conf

Re: patch (ivy): log conflict results at verbose

2009-01-09 Thread Robey Pointer
On 8 Jan 2009, at 08:12, Xavier Hanin wrote: These log messages are confusing, beacause they are not resolve time conflicts, but retrieve time conflicts: when Ivy retrieves a set of artifact, if it has to retrieve two artifacts to the same location, it complains about a conflict. For instance

DO NOT REPLY [Bug 34458] - and sometimes conflict with each other

2005-04-14 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 34458] - and sometimes conflict with each other

2005-04-14 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 34458] New: - and sometimes conflict with each other

2005-04-14 Thread bugzilla
gzilla/show_bug.cgi?id=34458 Summary: and sometimes conflict with each other Product: Ant Version: 1.6.3beta1 Platform: PC OS/Version: Linux Status: NEW Severity: major Priority: P2 Component: Core Assi

DO NOT REPLY [Bug 34458] - with an embedded reference and <*ant*> conflict

2005-04-15 Thread bugzilla
gzilla/show_bug.cgi?id=34458 [EMAIL PROTECTED] changed: What|Removed |Added Summary| and | with an embedded |sometimes conflict with each|reference and

DO NOT REPLY [Bug 34458] - with an embedded reference and <*ant*> conflict

2005-04-15 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 34458] - with an embedded reference and <*ant*> conflict

2005-04-15 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 34458] - with an embedded reference and <*ant*> conflict

2005-04-15 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 34458] - with an embedded reference and <*ant*> conflict

2005-07-13 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 34458] - with an embedded reference and <*ant*> conflict

2005-07-19 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 34458] - with an embedded reference and <*ant*> conflict

2005-08-18 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 34458] - with an embedded reference and <*ant*> conflict

2005-08-18 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 34458] - with an embedded reference and <*ant*> conflict

2006-10-06 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 34458] - with an embedded reference and <*ant*> conflict

2006-10-09 Thread bugzilla
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu