Yeah, I switched the <pluginRepository> from file to http (I am running
apache 2 to make these fils available via http).
But, it just can't find what it's looking for (even though things _do_
exist up there):
E:\work\up-svcs\lty\proj\LTY-P000039>mvn -e -Dmaven.test.skip=true
install
+ Error stacktraces are turned on.
[INFO] Scanning for projects...
[INFO] Reactor build order:
[INFO] Unnamed - lty:app:pom:1.0-SNAPSHOT
[INFO] Lty Utils
[INFO] Lty Crypto(Client)
[INFO] LtyModel
[INFO] LtyDataGen
[INFO] Crypto Server
[INFO] Upromise.com Site
[INFO]
------------------------------------------------------------------------
----
[INFO] Building Unnamed - lty:app:pom:1.0-SNAPSHOT
[INFO] task-segment: [install]
[INFO]
------------------------------------------------------------------------
----
[INFO]
------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO]
------------------------------------------------------------------------
[INFO] The plugin 'org.apache.maven.plugins:maven-site-plugin' does not
exist or no valid version could be found
[INFO]
------------------------------------------------------------------------
[INFO] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: The plugin
'org.apache.maven.plugins:maven-site-plugin' does not exist or no valid
versio
n could be found
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin(Default
LifecycleExecutor.java:1281)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.getMojoDescriptor(De
faultLifecycleExecutor.java:1517)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.bindLifecycleForPack
aging(DefaultLifecycleExecutor.java:1011)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.constructLifecycleMa
ppings(DefaultLifecycleExecutor.java:975)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultL
ifecycleExecutor.java:453)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandle
Failures(DefaultLifecycleExecutor.java:306)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(
DefaultLifecycleExecutor.java:273)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifec
ycleExecutor.java:140)
at
org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:256)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav
a:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor
Impl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at
org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at
org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Caused by:
org.apache.maven.plugin.version.PluginVersionNotFoundException: The
plugin 'org.apache.maven.plugins:maven-site-plugin' does not exist
or no valid version could be found
at
org.apache.maven.plugin.version.DefaultPluginVersionManager.resolvePlugi
nVersion(DefaultPluginVersionManager.java:225)
at
org.apache.maven.plugin.version.DefaultPluginVersionManager.resolvePlugi
nVersion(DefaultPluginVersionManager.java:87)
at
org.apache.maven.plugin.DefaultPluginManager.verifyPlugin(DefaultPluginM
anager.java:158)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin(Default
LifecycleExecutor.java:1252)
... 18 more
[INFO]
------------------------------------------------------------------------
[INFO] Total time: < 1 second
[INFO] Finished at: Mon Jul 10 14:15:21 EDT 2006
[INFO] Final Memory: 1M/3M
[INFO]
------------------------------------------------------------------------
Why is this?
-----Original Message-----
From: Tim Kettler [mailto:[EMAIL PROTECTED]
Sent: Monday, July 10, 2006 2:04 PM
To: Maven Users List
Subject: Re: Interrnal remote repository
Hi,
I don't think the file url given in your <pluginRepository> definition
is valid. Shouldn't
it be something like 'file:///C:/PATH/TO/REPOSITORY' for windows or
'file:///PATH/TO/REPOSITORY' for unix style os's? Or you need to change
the 'file://' to
'http://'.
Regarding your other mail and the ibiblio problems:
It is known that the load on ibiblio is high at some times. It's best to
configure a
mirror for it [1].
-Tim
[1] http://maven.apache.org/guides/mini/guide-mirror-settings.html
EJ Ciramella schrieb:
> I have the following two entries in my pom.xml:
>
> <repositories>
> <repository>
> <id>central</id>
> <name>Upromise Local Repository</name>
> <layout>default</layout>
>
> <url>http://build.corp.upromise.com/mavenrepository</url>
> </repository>
> </repositories>
>
> <pluginRepositories>
> <pluginRepository>
> <id>local-central</id>
> <name>main</name>
> <layout>default</layout>
>
> <url>file://build.corp.upromise.com/mavenrepository</url>
> </pluginRepository>
> </pluginRepositories>
>
> Is this wrong?
>
> -----Original Message-----
> From: Tim Kettler [mailto:[EMAIL PROTECTED]
> Sent: Monday, July 10, 2006 10:52 AM
> To: Maven Users List
> Subject: Re: Interrnal remote repository
>
> Did you specify your internal repo as a plugin repository in your
> settings.xml/pom.xml?
>
> EJ Ciramella schrieb:
>> Can someone tell me please if this is how I should be installing?
>>
>> Taking jars/poms from my .m2 directory and using the following
command
> to install them into the remote repository?
>> If so, why maven 2 builds going to repo1 still for all kinds of
> plugins (scroll down)?
>> -----Original Message-----
>> From: EJ Ciramella [mailto:[EMAIL PROTECTED]
>> Sent: Saturday, July 08, 2006 10:37 PM
>> To: Maven Users List
>> Subject: RE: Interrnal remote repository
>>
>> I'm using the following syntax;
>>
>> mvn deploy:deploy-file -DgroupId=<gid> -DartifactId=<aid>
> -Dversion=<version> -Dpackaging=<pkgtype> -Dfile=<file>
> -DrepositoryId=central -Durl=<url>
>> This is how I'm installing to my internal remote repository.
>>
>> Doesn't this generate all the metadata info?
>>
>> -----Original Message-----
>> From: Arnaud Bailly [mailto:[EMAIL PROTECTED]
>> Sent: Saturday, July 08, 2006 2:03 PM
>> To: Maven Users List
>> Subject: Re: Interrnal remote repository
>>
>> "EJ Ciramella" <[EMAIL PROTECTED]> writes:
>>
>>> Could you elaborate? I'm kinda a maven noob.
>>>
>> Information about plugins is kept in metadata files in the repo so
>> that they can be resolved. Not sure in your particular case but:
>> - check your local repository (maybe try removing the artefact that
>> cannot be resolved)
>> - check metadata files in the remote repository (in the group
>> directory I think
>> - BTW, the correct (I think) groupId syntax is dot-separated
>>
>> In my case, I had the problem because I did not understood the
>> difference between install and deploy (the metadata files seems to be
>> different): I kept building a plugin and "install"ing, then manually
>> copying the files. Everything ran fine on the machine that did the
>> install but for other users on different machine, thy kept having the
>> same error than yours.
>>
>> HTH, not sure I am very clear not very precise.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
