Re: Archiva vs. Nexus

[Rajesh Koilpillai]

They are competing and Apache Archiva works just fine with minimal
configuration.

On Sun, Jul 17, 2011 at 3:55 AM, Stephen Connolly <
stephen.alan.conno...@gmail.com> wrote:

> competing
>
> - Stephen
>
> ---
> Sent from my Android phone, so random spelling mistakes, random nonsense
> words and other nonsense are a direct result of using swype to type on the
> screen
> On 16 Jul 2011 17:51, "Eric Kolotyluk"  wrote:
> > Are archiva and nexus competing or complementary products?
> >
> > Cheers, Eric
> >
> > -
> > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> > For additional commands, e-mail: users-h...@maven.apache.org
> >
>



-- 
Thanks,
- Rajesh Koilpillai

What does reloading a plugin container mean in maven?

[Rajesh Koilpillai]

What does reloading a plug-in container mean in maven? This happens in just
a single machine, every other machine seems to be fine. How do I fix this
issue?

[INFO] Reloading plugin container for: org.apache.maven.plugins:m
aven-clean-plugin:2.4.1. The plugin artifact has changed.
[INFO] [clean:clean {execution: default-clean}]
[INFO] Reloading plugin container for: org.codehaus.mojo:versions
-maven-plugin:1.2. The plugin artifact has changed.
[INFO] Reloading plugin container for: org.apache.maven.plugins:m
aven-compiler-plugin:2.3.1. The plugin artifact has changed.
[INFO] Reloading plugin container for: org.apache.maven.plugins:m
aven-jar-plugin:2.3.1. The plugin artifact has changed.
[INFO] Reloading plugin container for: org.apache.maven.plugins:m
aven-clean-plugin:2.4.1. The plugin artifact has changed.
[INFO] Reloading plugin container for: org.apache.maven.plugins:m
aven-site-plugin:2.1.1. The plugin artifact has changed.
[INFO] Reloading plugin container for: org.apache.maven.plugins:m

aven-install-plugin:2.3.1. The plugin artifact has changed.
[INFO] [site:attach-descriptor {execution: default-attach-descrip...


-- 
Thanks,
- Rajesh Koilpillai

mvn javadoc:fix doesn't understand custom source locations

[Rajesh Koilpillai]

Hi,

mvn javadoc:fix doesn't understand custom source locations. My source code
is available under c:\project\ejb\src\model. Any idea on how to add custom
directories, I couldn't locate this in the plug-in documentation though.

[WARNING]
[WARNING] WARRANTY DISCLAIMER
[WARNING]
[WARNING] All warranties with regard to this Maven goal are disclaimed!
[WARNING] The changes will be done directly in the source code.
[WARNING] The Maven Team strongly recommends the use of a SCM software BEFO
RE executing this goal.
[WARNING]
[INFO] Are you sure to proceed? [Y]es [N]o
Y
[INFO] OK, let's proceed...
[WARNING] No previous artifact has been deployed, Clirr is ignored.
[WARNING] c:\project\ejb\src\main\java doesn't exist. Ignored it.


How do you add custom source locations?

-- 
Thanks,
- Rajesh Koilpillai