Some Maven Eclipse Questions

[Sony Antony]

1. Noticed that even when I use the EMBEDDED maven inside m2e, it is
creating a new JVM - different from the JVM running Eclipse - for
maven install ( even for cleam ). Is this always the case ?
( Im trying to see if this happened because of some issues with my setup )

2.  I have a multip project. ( A maven pom.xml that has a bunch of
s which in turn has a bunch of s and so on ). I
Imported only the top level pom.xml into eclipse(  on which I do the
install.). Is there any way to automatically include all src/main/java
folders from all nested modules into Eclipse project's Source Folder
list ?

3. Is there any way to automatically include all dependencies ( jar
files ) to the project 's Library ? ( So that I can use source
completion/syntax checking etc. )

4. I already had a maven project outside Eclipse, which had many
levels of nested  in its pom.xml files. I Imported only the
top level pom into Eclipse as 'Existing Maven Projects'. Is this the
right way to do this ? Im able to maven install from Eclipse.

Thank you
sony

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Possible to disable maven central ( repo1 ) ?

[Sony Antony]

Hi :
We have an http internal repository to which, I would like all developers to
point for their local builds.
But I dont want them to go to repo1.maven.org
Looks like if I switch maven to online ( false ), it will
attempt to go to repo1 ( in addition to the repositories specified under
settings.xml )
Is it possible to change this behavior

--sony

Re: Maven build order

[Sony Antony]

Thanks
This Project starts their build at a pom which pulls in many other pins
though  statements
Which in turns pulls in even more poms
Some of these are dependencies of others
Some are parents of others
Some are launched as modules of others
In this scenario should it be expected that maven reactor  will figure out
the correct build order and will follow that ( I mean it will make sure that
parents are built first. And similarly that dependencies are built first )
--sony

On Saturday, July 23, 2011, Jeff Jensen 
wrote:
> The parent and dependencies must exist, either in a repo (heavily
> preferred) or via a specified relative path.  It does not "build"
> parent or a dependency, as with a module (or itself).
>
> However, if module A is a dependency of module B and both are listed
> as modules of a common parent, when you run a build of the parent,
> Maven will build them in the correct order: A, B.
>
>
> On Sat, Jul 23, 2011 at 11:08 AM, Sony Antony 
wrote:
>> We have a fairly large project, that uses teh following 3 constructs in
>> various pom files
>> 
>> 
>> 
>>
>>
>> Given that, will maven reactor come out with the correct order after
>> considering all of these ?
>> I inherited this project recently from somebody else.
>> I havent completed my investigation. but it appeared that it doesnt
consider
>>  clause while deciding teh build order. Could this be true ?
>>
>> --sony
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>

Maven build order

[Sony Antony]

We have a fairly large project, that uses teh following 3 constructs in
various pom files





Given that, will maven reactor come out with the correct order after
considering all of these ?
I inherited this project recently from somebody else.
I havent completed my investigation. but it appeared that it doesnt consider
 clause while deciding teh build order. Could this be true ?

--sony

Re: Excluding Jars from EAR packaging

[Sony Antony]

Assuming you are using the maven-ear-plugin, did you try
*earSourceExcludes*

--sony

On Tue, Apr 26, 2011 at 7:18 AM, vaskikamal  wrote:

> Hi Anders,
>  My project is dependent on many thirdparty jars. These jars internally
> maintain thier own pom.xml.
>
>  I applied your suggestion and change the scope to "provided" for below
> mentioned dependency.
>
>  For example, consider the below dependency:
> 
>com.fairisaac.fidms.ThirdParty
>dom4j
>1.6.1
>provided
>
>
> Logically, it should have been excluded from EAR packaging. But, it was
> not.
>
> I am unable to understand why its not working.
>
> Can some one please guide me in resolving the issue.
>
> Regards
> Vaski
>
> --
> View this message in context:
> http://maven.40175.n5.nabble.com/Excluding-Jars-from-EAR-packaging-tp4340264p4340680.html
> Sent from the Maven - Users mailing list archive at Nabble.com.
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>

Re: Variables interpolated on the command-line

[Sony Antony]

what will happen if you put it under quotes '-Dprop1=${prop2}' ?
--sony

On Fri, Apr 22, 2011 at 10:40 PM, Phillip Hellewell wrote:

> I appreciate the two responses, but no one seems to be grasping what
> I'm talking about.
>
> Erase from your mind anything about %dos_env_vars% or $unix_env_vars.
> My question has exactly 0 to do with env vars.
>
> My question is about maven properties.  In a pom file I can set a
> property to the value of another property by writing
> ${prop2}, or if I want to set it to the literal value
> "${prop2}" I can write $${prop2}.  The extra $ escapes
> it and keeps it from getting interpolated.
>
> However, on the command-line, I cannot find any way to accomplish the
> same thing.  If I write mvn blah -Dprop1=${prop2} Maven sets prop1 to
> null.  If I write mvn blah -Dprop1=$${prop2} it sets prop1 to $null.
> The only way I have found to keep it from interpolating is by
> appending text.
>
> Is this by design or a bug?  I'd say it is a bug because if it's going
> to interpolate at all it ought to be consistent and should work the
> same way as when inside a pom file.
>
> Phillip
>
> On Thu, Apr 21, 2011 at 6:16 PM, Sony Antony 
> wrote:
> > I think %myvar2% will result in windows shell doing teh substitution
> > I dont think maven will use system variables set using -D as pom
> variables (
> > maybe I m wrong )
> > --sony
> > On Thu, Apr 21, 2011 at 7:24 PM, Phillip Hellewell 
> wrote:
> >
> >> This is on Windows from a command prompt, not Linux.
> >>
> >> Phillip
> >>
> >> On Thu, Apr 21, 2011 at 12:21 PM, Jörg Schaible 
> >> wrote:
> >> > Phillip Hellewell wrote:
> >> >
> >> >> Oh, I just thought of something shorter that will work:
> >> >>
> >> >> -Dmyvar1=c:\test\${myvar2}\.
> >> >>
> >> >> Still seems kinda crazy though.  Anyone want to shed some light on
> why
> >> >> it works this way?  This is with Maven 3.0.1.
> >> >
> >> > Maybe you should have a look into the bash manual instead ?
> >> >
> >> > - Jörg
> >> >
> >> >
> >> > -
> >> > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> >> > For additional commands, e-mail: users-h...@maven.apache.org
> >> >
> >> >
> >>
> >> -
> >> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> >> For additional commands, e-mail: users-h...@maven.apache.org
> >>
> >>
> >
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>

Re: Advantages of using a Repository Manager

[Sony Antony]

;
> Again, situation might differ for you and this is not intended to be a
> sales pitch for Nexus - I'm sure other Repository Managers have similar
> functionality as well - just sharing our experiences.
>
> Hope it helps.
>
> Dave Bruley
> Lead Technical Analyst
> CoreLink Administrative Solutions
>
> -Original Message-
> From: Sony Antony [mailto:sony.ant...@gmail.com]
> Sent: Wednesday, April 20, 2011 8:03 AM
> To: Maven Users List
> Subject: Re: Advantages of using a Repository Manager
>
> Thank you for the link.
> I had looked at this section from teh book around a year back.
> I couldnt find any clear advantage since we have a  pre approved and pre
> decided list of plugins and dependencies.
>
> Currently we have a master repository which is populated only when project
> decides to add a new dependency or plugin.
> At teh initial hudson setup, this repository is copied to a private
> location, and hudson is pointed to this private location ( this is one time
> only and is not done with each build ).
> Build is done in the offline maven mode.
>
> Given this scenario, Im trying to see if repository managers can provide
> any
> advantage over what we already have.
>
>
> --sony
>
> 2011/4/20 Tamás Cservenák 
>
> > See here for reasons:
> >
> >
> >
> http://www.sonatype.com/books/nexus-book/reference/sect-repoman-reasons.html
> >
> >
> > Thanks,
> > ~t~
> >
> > On Wed, Apr 20, 2011 at 2:23 PM, Sony Antony 
> > wrote:
> >
> > > Im trying to evaluate whether we should use a repository manager.
> > >
> > > Will somebody post at least a few of the advantages here
> > > Our project uses a list of pre approved ( and pre downloaded )
> > dependencies
> > > and plugins.
> > >
> > > --sony
> > >
> >
>
> Confidentiality Notice: This communication and any attachments are for the
> sole use of the intended recipient(s) and may contain confidential and
> privileged information. Any unauthorized review, use, disclosure,
> distribution or copying is prohibited. If you are not the intended
> recipient(s), please contact the sender by replying to this e-mail and
> destroy/delete all copies of this e-mail message.
>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>

Re: Variables interpolated on the command-line

[Sony Antony]

I think %myvar2% will result in windows shell doing teh substitution
I dont think maven will use system variables set using -D as pom variables (
maybe I m wrong )
--sony
On Thu, Apr 21, 2011 at 7:24 PM, Phillip Hellewell  wrote:

> This is on Windows from a command prompt, not Linux.
>
> Phillip
>
> On Thu, Apr 21, 2011 at 12:21 PM, Jörg Schaible 
> wrote:
> > Phillip Hellewell wrote:
> >
> >> Oh, I just thought of something shorter that will work:
> >>
> >> -Dmyvar1=c:\test\${myvar2}\.
> >>
> >> Still seems kinda crazy though.  Anyone want to shed some light on why
> >> it works this way?  This is with Maven 3.0.1.
> >
> > Maybe you should have a look into the bash manual instead ?
> >
> > - Jörg
> >
> >
> > -
> > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> > For additional commands, e-mail: users-h...@maven.apache.org
> >
> >
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>

Can you make an http server, the local repository ?

[Sony Antony]

Assuming this is an internal web server with write permission ( PUT
allowed ), is it possible to point to a web server for the local
repository ?
2. Is there any scenario at all wherein something gets written to the
remote repository ( if you use the file:// type URL for remote
repository, which I found would work )
--sony

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: Advantages of using a Repository Manager

[Sony Antony]

Thank you for the link.
I had looked at this section from teh book around a year back.
I couldnt find any clear advantage since we have a  pre approved and pre
decided list of plugins and dependencies.

Currently we have a master repository which is populated only when project
decides to add a new dependency or plugin.
At teh initial hudson setup, this repository is copied to a private
location, and hudson is pointed to this private location ( this is one time
only and is not done with each build ).
Build is done in the offline maven mode.

Given this scenario, Im trying to see if repository managers can provide any
advantage over what we already have.


--sony

2011/4/20 Tamás Cservenák 

> See here for reasons:
>
>
> http://www.sonatype.com/books/nexus-book/reference/sect-repoman-reasons.html
>
>
> Thanks,
> ~t~
>
> On Wed, Apr 20, 2011 at 2:23 PM, Sony Antony 
> wrote:
>
> > Im trying to evaluate whether we should use a repository manager.
> >
> > Will somebody post at least a few of the advantages here
> > Our project uses a list of pre approved ( and pre downloaded )
> dependencies
> > and plugins.
> >
> > --sony
> >
>

Advantages of using a Repository Manager

[Sony Antony]

Im trying to evaluate whether we should use a repository manager.

Will somebody post at least a few of the advantages here
Our project uses a list of pre approved ( and pre downloaded ) dependencies
and plugins.

--sony

Re: Is maven3 repository safe for concurrent access

[Sony Antony]

Did some experiment :
For some reason -Dmaven.repo.remote=file:/// doesnt have any effect at all (
in maven 3.0 )
However the same can be given in settings.xml

However, it wont result in a read-only local repository, as the artifact
gets copied from teh file:/// location to teh location designated as local
repository ( But since it is a file to file copy, it is fast )


But thats fine, since the real problem is about the local repository being
unsafe for concurrent access. So thanks for that.


--sony



On Fri, Apr 15, 2011 at 4:06 PM, Sony Antony  wrote:

> Thanks a real lot James :
> I was not aware of maven.repo.local ( although I was aware of teh
> setting.xml optio to specify the local repository ). We have decided to use
> this.
>
> 1. "which gives other benefits other than just its safe"
> Do you mind explaining some of the other benefits we might reap with
> seperate local repo.
>
> 2. While looking up the maven.repo.local, you mentioned, I came across
> maven.repo.remote, which takes multiple comma seperated URLs. I was
> wondering if I could use a file:/// style URL on this. So that we can have
> a single read-only secondary local repository, hosting all teh third party
> software and plugins ( without having to host them in a internal corporate
> web server )
>
> ( different maven.repo.local for each instances will require teh same
> thirdparty software/plugins to be duplicated in multiple places )
>
>
> --sony
>
>
>
>
> On Fri, Apr 15, 2011 at 3:44 PM, Nord, James  wrote:
>
>> Hi Sony,
>>
>> You can just configure a separate local repo for each CI job (which gives
>> other benefits other than just its safe).
>>
>> Hudson/Jenkins can do this for you (use private repository option)
>>
>> Otherwise use "mvn  -Dmaven.repo.local=/path/to/job/specific/repo
>> "
>> Or set it in your settings file (which you can then specify also per job
>> with -s)
>>
>> /james
>>
>>
>> -Original Message-
>> From: Sony Antony [mailto:sony.ant...@gmail.com]
>> Sent: 15 April 2011 20:31
>> To: Maven Users List
>> Subject: Re: Is maven3 repository safe for concurrent access
>>
>> You are correct. My interest is in knowing if I can use maven under a
>> CI/hudson  environment ( with multiple seperate instances of maven running
>> ).
>> If there is a patch for this, can somebody please post its reference here
>>
>> --sony
>>
>> On Fri, Apr 15, 2011 at 3:23 PM, Mirko Friedenhagen <
>> mfriedenha...@gmail.com
>> > wrote:
>>
>> > On Fri, Apr 15, 2011 at 19:39, Kristian Rosenvold
>> >  wrote:
>> > >
>> > > fr., 15.04.2011 kl. 11.54 -0400, skrev Sony Antony:
>> > >> Thank you Jason :
>> > >> If 3.x local repository is not safe for concurrent access, how does
>> > maven3
>> > >>  implement parallel builds ( -T switch ) ( maybe they decide on teh
>> > >> parallelism by making sure that there is no concurrent read/write
>> > >> access on teh repository *for the same* artifacts
>> > ? )
>> > >>
>> > >
>> > > The first half you got right, there is no concurrent writes of the
>> > > each individual artifact "by design".
>> > >
>> > > When it comes to downloading from remote repositories it's all
>> > > handled by a common (singleton) service anyway.
>> >
>> > This is only correct for one single instance of maven running, where
>> > multiple threads are downloading artifacts, isn't it? I guess the OP
>> > wanted to know wether it is safe to use Maven3 in a CI, where multiple
>> > processes download dependencies. To my understanding it is not safe,
>> > there was a patch for Maven2, if I remember right.
>> >
>> > Regards
>> > Mirko
>> > --
>> > http://illegalstateexception.blogspot.com/
>> > https://github.com/mfriedenhagen/
>> > https://bitbucket.org/mfriedenhagen/
>> >
>> > -
>> > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
>> > For additional commands, e-mail: users-h...@maven.apache.org
>> >
>> >
>>
>>
>>
>> **
>> This message is confidential and intended only for the addressee. If you
>> have received this message in error, please immediately notify the
>> postmas...@nds.com and delete it from your system as well as any copies.
>> The content of e-mails as well as traffic data may be monitored by NDS for
>> employment and security purposes. To protect the environment please do not
>> print this e-mail unless necessary.
>>
>> NDS Limited. Registered Office: One London Road, Staines, Middlesex, TW18
>> 4EX, United Kingdom. A company registered in England and Wales. Registered
>> no. 3080780. VAT no. GB 603 8808 40-00
>>
>> **
>>
>> -
>> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
>> For additional commands, e-mail: users-h...@maven.apache.org
>>
>>
>

Re: Is maven3 repository safe for concurrent access

[Sony Antony]

Thanks a real lot James :
I was not aware of maven.repo.local ( although I was aware of teh
setting.xml optio to specify the local repository ). We have decided to use
this.

1. "which gives other benefits other than just its safe"
Do you mind explaining some of the other benefits we might reap with
seperate local repo.

2. While looking up the maven.repo.local, you mentioned, I came across
maven.repo.remote, which takes multiple comma seperated URLs. I was
wondering if I could use a file:/// style URL on this. So that we can have a
single read-only secondary local repository, hosting all teh third party
software and plugins ( without having to host them in a internal corporate
web server )

( different maven.repo.local for each instances will require teh same
thirdparty software/plugins to be duplicated in multiple places )


--sony




On Fri, Apr 15, 2011 at 3:44 PM, Nord, James  wrote:

> Hi Sony,
>
> You can just configure a separate local repo for each CI job (which gives
> other benefits other than just its safe).
>
> Hudson/Jenkins can do this for you (use private repository option)
>
> Otherwise use "mvn  -Dmaven.repo.local=/path/to/job/specific/repo
> "
> Or set it in your settings file (which you can then specify also per job
> with -s)
>
> /james
>
>
> -Original Message-
> From: Sony Antony [mailto:sony.ant...@gmail.com]
> Sent: 15 April 2011 20:31
> To: Maven Users List
> Subject: Re: Is maven3 repository safe for concurrent access
>
> You are correct. My interest is in knowing if I can use maven under a
> CI/hudson  environment ( with multiple seperate instances of maven running
> ).
> If there is a patch for this, can somebody please post its reference here
>
> --sony
>
> On Fri, Apr 15, 2011 at 3:23 PM, Mirko Friedenhagen <
> mfriedenha...@gmail.com
> > wrote:
>
> > On Fri, Apr 15, 2011 at 19:39, Kristian Rosenvold
> >  wrote:
> > >
> > > fr., 15.04.2011 kl. 11.54 -0400, skrev Sony Antony:
> > >> Thank you Jason :
> > >> If 3.x local repository is not safe for concurrent access, how does
> > maven3
> > >>  implement parallel builds ( -T switch ) ( maybe they decide on teh
> > >> parallelism by making sure that there is no concurrent read/write
> > >> access on teh repository *for the same* artifacts
> > ? )
> > >>
> > >
> > > The first half you got right, there is no concurrent writes of the
> > > each individual artifact "by design".
> > >
> > > When it comes to downloading from remote repositories it's all
> > > handled by a common (singleton) service anyway.
> >
> > This is only correct for one single instance of maven running, where
> > multiple threads are downloading artifacts, isn't it? I guess the OP
> > wanted to know wether it is safe to use Maven3 in a CI, where multiple
> > processes download dependencies. To my understanding it is not safe,
> > there was a patch for Maven2, if I remember right.
> >
> > Regards
> > Mirko
> > --
> > http://illegalstateexception.blogspot.com/
> > https://github.com/mfriedenhagen/
> > https://bitbucket.org/mfriedenhagen/
> >
> > -
> > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> > For additional commands, e-mail: users-h...@maven.apache.org
> >
> >
>
>
>
> **
> This message is confidential and intended only for the addressee. If you
> have received this message in error, please immediately notify the
> postmas...@nds.com and delete it from your system as well as any copies.
> The content of e-mails as well as traffic data may be monitored by NDS for
> employment and security purposes. To protect the environment please do not
> print this e-mail unless necessary.
>
> NDS Limited. Registered Office: One London Road, Staines, Middlesex, TW18
> 4EX, United Kingdom. A company registered in England and Wales. Registered
> no. 3080780. VAT no. GB 603 8808 40-00
>
> **
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>

Re: Is maven3 repository safe for concurrent access

[Sony Antony]

You are correct. My interest is in knowing if I can use maven under a
CI/hudson  environment ( with multiple seperate instances of maven running
).
If there is a patch for this, can somebody please post its reference here

--sony

On Fri, Apr 15, 2011 at 3:23 PM, Mirko Friedenhagen  wrote:

> On Fri, Apr 15, 2011 at 19:39, Kristian Rosenvold
>  wrote:
> >
> > fr., 15.04.2011 kl. 11.54 -0400, skrev Sony Antony:
> >> Thank you Jason :
> >> If 3.x local repository is not safe for concurrent access, how does
> maven3
> >>  implement parallel builds ( -T switch )
> >> ( maybe they decide on teh parallelism by making sure that there is no
> >> concurrent read/write access on teh repository *for the same* artifacts
> ? )
> >>
> >
> > The first half you got right, there is no concurrent writes of the each
> > individual artifact "by design".
> >
> > When it comes to downloading from remote repositories it's all handled
> > by a common (singleton) service anyway.
>
> This is only correct for one single instance of maven running, where
> multiple threads are downloading artifacts, isn't it? I guess the OP
> wanted to know wether it is safe to use Maven3 in a CI, where multiple
> processes download dependencies. To my understanding it is not safe,
> there was a patch for Maven2, if I remember right.
>
> Regards
> Mirko
> --
> http://illegalstateexception.blogspot.com/
> https://github.com/mfriedenhagen/
> https://bitbucket.org/mfriedenhagen/
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>

Re: Is maven3 repository safe for concurrent access

[Sony Antony]

Thank you Jason :
If 3.x local repository is not safe for concurrent access, how does maven3
 implement parallel builds ( -T switch )
( maybe they decide on teh parallelism by making sure that there is no
concurrent read/write access on teh repository *for the same* artifacts ? )

--sony

On Fri, Apr 15, 2011 at 11:28 AM, Jason van Zyl  wrote:

> Apache Maven 3.x does not have a local repository implementation that is
> safe for concurrent access.
>
> Maven 3.x is intended to be compatible with Maven 2.x in all respects. A
> Maven 2.x build should just work in Maven 3.x
>
> On Apr 15, 2011, at 11:13 AM, Sony Antony wrote:
>
> > I read somewhere that during maven 2, teh repository was not safe for
> > concurrent access.
> > ( If multiple maven builds access teh same repository, it might end up
> being
> > corrupt )
> >
> > However, Im not sure if this unsafety arose because of teh way maven2
> > accessed teh repository or if the repository layout itself was inherently
> > flawed for concurrent access.
> >
> > Now that we are moving to maven 3, I learned ( from here ) that it still
> > uses ~/.m2 for repository.
> >
> > 1. Does that mean that maven3 also has teh same concurrency access issue
> ?
> > On teh otehr hand, maven3 supports parallel builds. If the repository is
> not
> > thread safe, how is it possible to implement concurrent access.
> >
> > 2. Is maven3 safe to use with multiple seperate builds all pointing to
> teh
> > same repository ?
> >
> > 3. Can I use maven2 repository for a maven3 build without having to
> > redownload any of the artifacts that are already there ?
> >
> > Thanks
> > --sony
>
> Thanks,
>
> Jason
>
> --
> Jason van Zyl
> Founder,  Apache Maven
> http://twitter.com/jvanzyl
> -
>
> {script:nopre:"/Users/jvanzyl/signature/signature.sh"}
>
>
>
>

Is maven3 repository safe for concurrent access

[Sony Antony]

I read somewhere that during maven 2, teh repository was not safe for
concurrent access.
( If multiple maven builds access teh same repository, it might end up being
corrupt )

However, Im not sure if this unsafety arose because of teh way maven2
accessed teh repository or if the repository layout itself was inherently
flawed for concurrent access.

Now that we are moving to maven 3, I learned ( from here ) that it still
uses ~/.m2 for repository.

1. Does that mean that maven3 also has teh same concurrency access issue ?
On teh otehr hand, maven3 supports parallel builds. If the repository is not
thread safe, how is it possible to implement concurrent access.

2. Is maven3 safe to use with multiple seperate builds all pointing to teh
same repository ?

3. Can I use maven2 repository for a maven3 build without having to
redownload any of the artifacts that are already there ?

Thanks
--sony

Re: Trying to migrate to maven 3.0.3

[Sony Antony]

Thank you for clarifying Anders :
1. "No, you should specify a version for all plugins "
When I ran a sample project, it automatically downloaded a bunch of plugins
( like maven-clean-plugin ) as specified in teh superpom version (  I didnt
specify ).
Are you saying that I should have specified the versions in my pom ?

2. Also it created the repository under ~/.m2 . I was expecting it to be
~/.m3, since I was using maven 3. ( I wanted to make sure that I didnt
wrongly run maven 3 in maven 2 mode, because my pom didnt explicitly specify
that I need the maven3 behavior )

--sony

On Fri, Apr 15, 2011 at 8:40 AM, Anders Hammar  wrote:

> > 1. Does that mean that the poms we write would look exactly same as how
> > they
> > would have looked during maven 2.x days ?
> >
>
> There are no changes to the pom. A pom that works with Maven 3.0.x should
> work with Maven 2.x (with the possible exception that some specific plugin
> might not work with some Maven version).
>
> 2. "3 will complain if you did not specify versions in the plugins"
> > I guess, this applies only to the plugins that ate *not* specified in teh
> > superpom ( core plugins ) ?
> >
>
> No, you should specify a version for all plugins (either in your pom or in
> a
> parent pom). The ones in the super-pom are just a safety net.
>
> /Anders
>
>
> >
> >
> > --sony
> >
> >
> >
> >
> >
> > On Fri, Apr 15, 2011 at 1:06 AM, Tom Eugelink
> > wrote:
> >
> > >  If you do nothing fancy in your plugins then you should be able to
> > migrate
> > > to 3 without changes to the plugin. 3.0 is mainly a refactoring of the
> 2
> > > code and tries to remain as much backwards compatible as is possible.
> So
> > no,
> > > yes, no.
> > > 3 will complain if you did not specify versions in the plugins, so that
> > is
> > > something to pick up.
> > >
> > >
> > >
> > >
> > >
> > > On 15-4-2011 04:34, Sony Antony wrote:
> > >
> > >> We have been using mvn 2.1 for a while and we have understood it
> fairly
> > >> well.
> > >> Recently we decided to move to 3.x,( mainly for teh parallel build
> > feature
> > >> with the -T switch )
> > >>
> > >> But we find teh documentation difficult to come by. Googling didnt dig
> > up
> > >> any tutorial or guides for 3.0 specific features.
> > >> Specifically, we have the following fundamental questions. Will be
> very
> > >> grateful if somebody could answer these.
> > >>
> > >> 1. I read about the changes for the pom.xml in 3.x. Does that mean
> that
> > I
> > >> should change my poms, even if I m not using any features specific to
> > 3.x.
> > >> (
> > >> Maybe I should change the namespace from
> > >> http://maven.apache.org/POM/4.0.0 to
> > >> something newer ? )
> > >> 2. When I built a simple project, all of teh plugins that got
> > >> automatically
> > >> downloaded from http://repo1.maven.org looked pretty much like the
> > >> plugins
> > >> used by maven 2.x. Does that mean that most of the plugins and
> > >> repositories
> > >> I would be using will be exactly same as maven 2.x ?
> > >> 3. Even teh super pom looks teh same in maven 3.x ( verified using
> > >> help:effective-pom ). Are we supposed to oevrride any of teh versions
> in
> > >> the
> > >> superpom for the core plugins, so as to get the ones that would work
> > with
> > >> maven 3.x ? ( probably to get the latest thread safe versions ? )
> > >>
> > >> Thank you for reading.
> > >>
> > >>
> > >>
> > >> --sony
> > >>
> > >>
> > >
> > > --
> > >
> > > *Tom Eugelink*
> > > Senior software engineer
> > > +31 (0)6 - 47 93 85 92
> > > t.eugel...@knowledgeplaza.nl <mailto:t.eugel...@knowledgeplaza.nl>
> > >*KnowledgePlaza <http://www.knowledgeplaza.nl>*
> > > Sutton 15
> > > 7327 AB Apeldoorn
> > > Tel: +31 (0)55 - 526 3887
> > > Fax: +31 (0)55 - 526 3950
> > > i...@knowledgeplaza.nl <mailto:i...@knowledgeplaza.nl>
> > > Disclaimer: The information contained in this message is for the
> intended
> > > addressee only and may contain confidential and/or privileged
> > information.
> > > If you are not the intended addressee, please delete this message and
> > notify
> > > the sender; do not copy or distribute this message or disclose its
> > contents
> > > to anyone.
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> >
>

Re: Trying to migrate to maven 3.0.3

[Sony Antony]

1. Does that mean that the poms we write would look exactly same as how they
would have looked during maven 2.x days ?


2. "3 will complain if you did not specify versions in the plugins"
I guess, this applies only to the plugins that ate *not* specified in teh
superpom ( core plugins ) ?


--sony





On Fri, Apr 15, 2011 at 1:06 AM, Tom Eugelink
wrote:

>  If you do nothing fancy in your plugins then you should be able to migrate
> to 3 without changes to the plugin. 3.0 is mainly a refactoring of the 2
> code and tries to remain as much backwards compatible as is possible. So no,
> yes, no.
> 3 will complain if you did not specify versions in the plugins, so that is
> something to pick up.
>
>
>
>
>
> On 15-4-2011 04:34, Sony Antony wrote:
>
>> We have been using mvn 2.1 for a while and we have understood it fairly
>> well.
>> Recently we decided to move to 3.x,( mainly for teh parallel build feature
>> with the -T switch )
>>
>> But we find teh documentation difficult to come by. Googling didnt dig up
>> any tutorial or guides for 3.0 specific features.
>> Specifically, we have the following fundamental questions. Will be very
>> grateful if somebody could answer these.
>>
>> 1. I read about the changes for the pom.xml in 3.x. Does that mean that I
>> should change my poms, even if I m not using any features specific to 3.x.
>> (
>> Maybe I should change the namespace from
>> http://maven.apache.org/POM/4.0.0 to
>> something newer ? )
>> 2. When I built a simple project, all of teh plugins that got
>> automatically
>> downloaded from http://repo1.maven.org looked pretty much like the
>> plugins
>> used by maven 2.x. Does that mean that most of the plugins and
>> repositories
>> I would be using will be exactly same as maven 2.x ?
>> 3. Even teh super pom looks teh same in maven 3.x ( verified using
>> help:effective-pom ). Are we supposed to oevrride any of teh versions in
>> the
>> superpom for the core plugins, so as to get the ones that would work with
>> maven 3.x ? ( probably to get the latest thread safe versions ? )
>>
>> Thank you for reading.
>>
>>
>>
>> --sony
>>
>>
>
> --
>
> *Tom Eugelink*
> Senior software engineer
> +31 (0)6 - 47 93 85 92
> t.eugel...@knowledgeplaza.nl <mailto:t.eugel...@knowledgeplaza.nl>
>*KnowledgePlaza <http://www.knowledgeplaza.nl>*
> Sutton 15
> 7327 AB Apeldoorn
> Tel: +31 (0)55 - 526 3887
> Fax: +31 (0)55 - 526 3950
> i...@knowledgeplaza.nl <mailto:i...@knowledgeplaza.nl>
> Disclaimer: The information contained in this message is for the intended
> addressee only and may contain confidential and/or privileged information.
> If you are not the intended addressee, please delete this message and notify
> the sender; do not copy or distribute this message or disclose its contents
> to anyone.
>
>
>
>
>
>
>
>
>

Trying to migrate to maven 3.0.3

[Sony Antony]

We have been using mvn 2.1 for a while and we have understood it fairly
well.
Recently we decided to move to 3.x,( mainly for teh parallel build feature
with the -T switch )

But we find teh documentation difficult to come by. Googling didnt dig up
any tutorial or guides for 3.0 specific features.
Specifically, we have the following fundamental questions. Will be very
grateful if somebody could answer these.

1. I read about the changes for the pom.xml in 3.x. Does that mean that I
should change my poms, even if I m not using any features specific to 3.x. (
Maybe I should change the namespace from http://maven.apache.org/POM/4.0.0 to
something newer ? )
2. When I built a simple project, all of teh plugins that got automatically
downloaded from http://repo1.maven.org looked pretty much like the plugins
used by maven 2.x. Does that mean that most of the plugins and repositories
I would be using will be exactly same as maven 2.x ?
3. Even teh super pom looks teh same in maven 3.x ( verified using
help:effective-pom ). Are we supposed to oevrride any of teh versions in the
superpom for the core plugins, so as to get the ones that would work with
maven 3.x ? ( probably to get the latest thread safe versions ? )

Thank you for reading.



--sony

Possible to specify version from a properties file

[Sony Antony]

We have more than 100 modules in our project.
Each pom includes teh parent pom using the cordinates including teh version
number.

Is there any way to centralize the version number, maybe in a properties
file/profile/something.
So that if the version changes, this will be the only place where we need to
change the version.
( Every pom would refer to this version number using some kind of
indirection - like ${project.version} )

We would liek to avoid having to put the version number in every pom.

--sony

Re: how to copy jar (also) to target installation dir

[Sony Antony]

It should work with the antrun plugin ( and ant's  task. )

( configure an antrun plugin execution to attach to install phase )

--sony

On Sun, Nov 22, 2009 at 8:43 AM, eyal edri  wrote:

> I want to config the pom project to copy the final jar file to an
> installation dir and bind it to the 'install' phase.
>
> meaning, when i "just" build the project, the jar will be built into the
> default target/project.jar.
>
> but when i "install" it should be also should be copied to
> /usr/local/application/project.jar.
>
> i tried adding " in the 'jar' plugin, but it just changed
> the default target.
>
> --
> Eyal Edri
>

Re: How best to deploy ( different config ) to different machines

[Sony Antony]

I was thinking of exactly teh same when I wrote it ( the name of the
particular config file to be chosen is stored in JNDI. Using the application
event listener, teh particular file is preread when app comes online )

But I wanted to ask if this is really how most well maintained projects do
it ?

Does maven have any tricks/standard way to deploy teh config file ?
--sony




On Thu, Nov 19, 2009 at 7:28 PM, Jesse Farinacci  wrote:

> Sounds like a job for JNDI.
>
> On Thu, Nov 19, 2009 at 7:23 PM, Sony Antony 
> wrote:
> > Reading the following thread brings forth this question ( Actually there
> was
> > a thread on this few weeks back. But it wasnt very detailed ) :
> >
> > We have this configuration file that contains machine/server specific
> > information.
> > Assuming my application is an ear, how do I do a build so that I dont
> have
> > to do a build specific for each target hosts.
> > 1. Should I bundle up the configuration file inside the ear file ?
> > 2. Should I bundle up all configuration files for all possible servers
> and
> > at deployment time set some kind of variable ( through teh app server
> admin
> > console ), which resolves to a specific config file ?
> >
> > In general what is teh best practice for this
> > --sony
> >
>
> -Jesse
>
> --
> There are 10 types of people in this world, those
> that can read binary and those that can not.
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>

How best to deploy ( different config ) to different machines

[Sony Antony]

Reading the following thread brings forth this question ( Actually there was
a thread on this few weeks back. But it wasnt very detailed ) :

We have this configuration file that contains machine/server specific
information.
Assuming my application is an ear, how do I do a build so that I dont have
to do a build specific for each target hosts.
1. Should I bundle up the configuration file inside the ear file ?
2. Should I bundle up all configuration files for all possible servers and
at deployment time set some kind of variable ( through teh app server admin
console ), which resolves to a specific config file ?

In general what is teh best practice for this


--sony




On Thu, Nov 19, 2009 at 6:24 PM, Wagner Santos wrote:

> Thanks! It's work (with some modifications).
>
> --
> Wagner Santos
> MSN/Gtalk: wagner.gsan...@gmail.com
> Site: http://www.geracaoelias.blog.br
> meadiciona:http://meadiciona.com/wagnergsantos/
>
>
> On Thu, Nov 19, 2009 at 1:00 AM, Wayne Fay  wrote:
>
> > > I have a webapp and two servers and a localhost with diferents
> databases
> > > configs and I'm trying to do this:
> >
> > In general, you should use profiles for this kind of thing:
> >
> >
> http://maven.apache.org/guides/mini/guide-building-for-different-environments.html
> >
> > Wayne
> >
> > -
> > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> > For additional commands, e-mail: users-h...@maven.apache.org
> >
> >
>

Creating a war from antrun

[Sony Antony]

We have to use one of the weblogic provided ant task in order to create a
war file.

How will I do this with maven.
I mean should I give the packaging as pom and then produce teh warfile using
antrun ? ( But then how will the produced war file be installed to teh local
repository )

Or should I run antrun first and then, unjar and then let the war plugin war
it up again ?

Any pointer will be appreciated
--sony

Re: antrun messes up classloader ?

[Sony Antony]

Thank you very much Wayne ( I didnt know that ) :

But in out case we explicitly specified teh jar files within the 

 
   
  
   
   





 
 



wont this result in all teh classes being reloaded again ? ( because taskdef
forced it to reload )

--sony

On Tue, Nov 17, 2009 at 10:11 AM, Wayne Fay  wrote:

> > But when this submodule is called from a parent pom ( which also calls
> other
> > submodules ), it complains about a missing class for the weblogic
> compiler.
>
> This is a known problem in M2. Maven only loads the plugin once (the
> first time it sees it) in a build, and only loads plugin dependencies
> it sees at that time.
>
> You need to collect your Antrun plugin dependencies from the various
> places you have declared it and copy them so each declaration has the
> full set of plugin deps (or figure out which one will be seen first
> and just ensure it has the full set of plugin deps).
>
> Wayne
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>

antrun messes up classloader ?

[Sony Antony]

I have a submodule that executes antrun in order to comile some webservices
files ( using weblogic web services compiler ).
This works fine when I executes maven from the submodule directory.

But when this submodule is called from a parent pom ( which also calls other
submodules ), it complains about a missing class for the weblogic compiler.

1. Is it possible that invoking maven directly from a submodule is different
from invoking it from a parent pom ( using  )

2. Does maven use a separate classloader for each invocation of antrun ? (
Is it possible that the previous invocation of antrun affected/corrupted the
classloader )

How else can this be explained.

--sony

Re: properties in settings.xml

[Sony Antony]

The ,exists> block was inside  right ?



...

${nsis.path}


 ...



--sony

On Fri, Nov 13, 2009 at 10:43 PM, James Russo  wrote:

> Hello,
>
>I have a project which uses nsis to create an installer, but NSIS
> isn't available on all of the platforms which I build the project, and I'd
> like it to skip making the NSIS when the makensis isn't available. I'd like
> to make the path to NSIS be configurable in the ~/.m2/settings.xml, so I add
> it to a "default" profile which I created having a bunch of other
> properties:
>
>
>  
>
>  default
>  
>
>  org.postgresql.Driver
>jdbc:postgresql://localhost/test
>user
>password
>http://localhost:8081/manager
> 
>manager
>password
>/
>/client
>/usr/local/nsis/nsis-2.45/bin/makensis
>
>  
>
>  
>
> So, I have a nsis.path defined in there.  However, I am trying to activate
> the profile in my pom and neither way works. I've tried to just
> activate the profile in the pom based on presence of nsis.path variable and
> that doesn't work. And then I've also tried to do:
>
> ${nsis.path}
>
> and that doesn't work either.
>
> How can I accomplish this? I could activate it manually with -P, but I'd
> rather just have everything in the settings.xml file since I need to visit
> that to setup the environment anyways.
>
> thanks!
>
> -jr
>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>

Re: SNAPSHOT comparison between local and remote repositories

[Sony Antony]

This is a big assumption, as most of the machines will have their times
differing by some amount.
( Maybe it is a good enough assumption as artifacts need not be compared
with a millisecond accuracy )

--sony

On Fri, Nov 13, 2009 at 9:58 AM, Wayne Fay  wrote:

> > Is maven comparing the some kind of timestamps ? ( If true then it has to
> > assume that the clocks of both machines are in sync )
>
> Yes, that's what happens.
>
> Wayne
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>

SNAPSHOT comparison between local and remote repositories

[Sony Antony]

I notice that every SNAPSHOt file is checked at the remote repository for
teh latest version, everytime it is given as a dependency.
( This doesnt happen when the  in settings.xml doesnt enable
 )

( My snapshots doesnt have any build number or anything ( Eg -
xx-SNAPSHOT ) )
But Im confused about how maven can make any comparison between local and
remote repositoties in order to deduce which one is teh latest.
What if I have build teh artifact locally so that my local version is newer
than the one in remote repository ?

Is maven comparing the some kind of timestamps ? ( If true then it has to
assume that the clocks of both machines are in sync )

--sony

Re: maven-dependency-plugin:unpack-dependencies doesn't always work

[Sony Antony]

yes it doesn't work of used more than once.
I came across it yesterday. I had two execution blocks, unpacking two
diff jars at two diff phases. only one of them was unpacked and there
was no error.
I ended working around it by chanding the second goal to copy. I then
unjar ed it using antrun.
--sony

On 11/9/09, Brian Fox  wrote:
> I would expect an error, I can only suggest attaching a debugger to
> the plugin and see what's going on.
>
> On Mon, Nov 9, 2009 at 9:06 AM, EJ Ciramella 
> wrote:
>> Nope - there are no markers created.  Period.
>> Good thinking though!
>>
>> Any other suggestions what may be wrong with this artifact?  It opens just
>> fine in winzip.
>>
>> -
>> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
>> For additional commands, e-mail: users-h...@maven.apache.org
>>
>>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: How to get the command "maven test:test" to delete test files before executing?

[Sony Antony]

This is one of many possible ways of doing it :

add an antrun configuration and attach it to the validate ( very first )
phase.
This antrun should do teh *.tmp deletion that you need though its 
task

Then execute maven as mvn validate test:test


--sony



On Tue, Nov 3, 2009 at 3:26 PM, laredotornado wrote:

>
> Hi,
>
> I'm using Maven 1.1 with Java 1.5 on a Mac 10.5.6.  In my test directory, I
> can run "maven test:test" to execute all of my unit tests.  I would like
> that when I type this command, the first thing that happens is that all
> files in the current directory matching "*.tmp" get deleted (in case a
> previous test run crashed).  How can I customize the "maven test:test"
> command to delete the temporary files before it starts its test run?
>
> Thanks, - Dave
>
> --
> View this message in context:
> http://old.nabble.com/How-to-get-the-command-%22maven-test%3Atest%22-to-delete-test-files-before-executing--tp26163569p26163569.html
> Sent from the Maven - Users mailing list archive at Nabble.com.
>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>

Re: tracking down jetty/tomcat dependencies

[Sony Antony]

( IIRC xalan is used for xslt transformation. xerces is teh parser )

I think the war file is supposed to be self sufficient - meaning it should
contain all teh jar files/libraries application needs.
This is is what maven's war packaging does - it puts all the dependency
artifacts inside WEB-INF/lib directory of the war file.
( make sure none of the dependencies are given provided at teh
war's pom.xml. Did you check this ?

most of the app servers I know load the library from WEB-INF/lib first and
falls back on teh app server's classpath only if the class is not found
there.


ideally I would not want any of the classpath components inherited by teh
running container ( jetty/tomcat )
But I dont think there is a way to turn off this inheritance

--sony




On Tue, Nov 3, 2009 at 5:53 AM, Benson Margulies wrote:

> I'm still wishing that someone could help me figure out just what is on the
> classpath inside of tomcat:run.
>
> To a first approximation, jetty:run and tomcat:run had the same problem.
> However, I was a able to cure it in jetty and not in tomcat. It LOOKS as if
> tomcat is depending on an old version of Xalan.
>
>
> On Fri, Oct 30, 2009 at 5:16 AM, Benson Margulies  >wrote:
>
> > I wrote it up on the mojo user list once I got a clearer picture, but
> here
> > goes again.
> >
> > The code calls DocumentBuilderFactory and SchemaFactory to parse an XML
> > file to DOM with schema validation. Run in the plugins, it fails with an
> > impossible validation error (a claim that a valid attribute is invalid).
> The
> > backtrace shows a combination of xerces and JDK classes. I have xerces in
> > the webapp's class path.
> >
> > The same code works fine, with or without xerces, run as a pojo or a
> junit
> > test.
> >
> > If I try to use 100% Xerces by referring to their implementation classes
> > (DocumentBuilderImpl and XMLSchemaFactory) it still fails in the plugins.
> >
> > The problem goes away if I use the new JAXP 1.4 APIs to force the use of
> > Xerces.
> >
> > I reason as follows: in a live copy of tomcat or jetty, the 'system'
> > classpath is whatever jars are sitting in the containers system library
> > directory. When these plugins deploy a webapp, they don't have a system
> > library directory. They instead have whatever classpath maven invokes
> them
> > with, based on their declared dependencies and the transitive closure
> that
> > reaches into plexus and such. There could easily be some ancient xml-apis
> > jar in there, or some other source of interference, which I am not
> > preempting in my webapp.
> >
> > If dependency:tree worked for a plugin classpath, then I might be able to
> > figure out the real source of the problem and fix it by tinkering with
> > dependencies on the plugin. But I can't figure out how to get a full tree
> > for maven-tomcat-plugin (e.g.).
> >
> >
> > On Thu, Oct 29, 2009 at 10:32 PM, Brett Randall  >wrote:
> >
> >> On Fri, Oct 30, 2009 at 6:45 AM, Benson Margulies <
> bimargul...@gmail.com
> >> >wrote:
> >>
> >> > I've got code that works fine when run as a pojo and fails when run in
> a
> >> > webapp, either via tomcat:run or jetty:run. I suspect, because I can't
> >> > think
> >> > of anything else, that there is detritus in the 'system' classpaths of
> >> > these
> >> > containers. However, mvn dependency:tree does not tell me much about
> the
> >> > maven-jetty-plugin. Neither does dependency:resolve-plugins.
> >> >
> >> > Is there some way to get a clearer view of this question?
> >> >
> >>
> >> What is the mode of failure?
> >>
> >> Brett
> >>
> >
> >
>

Some more maven questions

[Sony Antony]

1. Is it possible to have multiple profiles to be active at the same time ?
If true, what if two profiles - both active - define conflicting
informations ( say the same plugin is configured differently )

2. When is teh decision to activate a profiletaken . Before teh very first
phase is begun ? ( validation )
( IOW, does maven make teh decision to activate a profile, even before the
validation phase starts ? )

3. We have a module that contains a bunch of xsd schemas. We would like to
compile these only if something has changed.
I understand that I can put a  inside a profile, which is activated
only when something changes.

But I couldnt find any way to communicate to maven that the profile needs to
be activated  only had a limited things to check. ( like file
exists, OS etc. )

Can somebody suggest a solution


4. Is it possible to execute a goal more than once during teh same phase ? (
without resorting to antrun )

--sony

Some maven questions

[Sony Antony]

Im fairly new to maven.
Tried getting answers to these from books and google. Trying my luch here

1. can I add more custom phases to the 23 already defined (
http://maven.apache.org/guides/introduction/introduction-to-the-lifecycle.html#Lifecycle_Reference
 )
( - I read that phases are already hard coded in a file called
components.xml which is used at compile time. This seemed to imply that I
cannot ad/change to teh list of existing phases.
On teh other hand I read that phases can be added by using  (
needs a custom plugin/mojo to be written )

2. Is it possible to turn off a particular phase from being fired for an
already given packaging ( say jar : Can I turn off test phase - [ Im aware
of skip.test=true. My question was more general ] )
3. Is it possible to turn off a plugin from being fired for a particular
phase.


4. If I have an ant task that requires a , which is teh preferred
way to provide the class file that implements the task :
- As a plugin dependency ?

5. In general I noticed that antrun was slow. Was this something in our
environment. Or is it known to be slow in general

Thank you very much.

--sony