Re: [M2]:Maven won't work anymore

2006-02-09 Thread Joern Huxhorn

John Casey wrote:
actually, that's where offline mode is helpful. Of course, if you 
don't have all the artifacts/poms cached in your local repository, it 
won't do you much good...



That's true, -o helps a lot in this case...

I currently have the following messages whenever I try to build without -o:

Downloading: 
file:/nix/mvn_repos/saxon/saxonb-dom/8.6.1/saxonb-dom-8.6.1.pom
[WARNING] Unable to get resource from repository bpinteractive 
(file:/nix/mvn_repos)
Downloading: 
http://www.ibiblio.net/pub/packages/maven2/saxon/saxonb-dom/8.6.1/saxonb-dom-8.6.1.pom
[WARNING] Unable to get resource from repository central 
(http://repo1.maven.org/maven2)
Downloading: 
http://www.ibiblio.org/maven2/saxon/saxonb-dom/8.6.1/saxonb-dom-8.6.1.pom
[WARNING] Unable to get resource from repository mirror 
(http://www.ibiblio.org/maven2)

Downloading: file:/nix/mvn_repos/saxon/saxonb/8.6.1/saxonb-8.6.1.pom
[WARNING] Unable to get resource from repository bpinteractive 
(file:/nix/mvn_repos)
Downloading: 
http://www.ibiblio.net/pub/packages/maven2/saxon/saxonb/8.6.1/saxonb-8.6.1.pom
[WARNING] Unable to get resource from repository central 
(http://repo1.maven.org/maven2)
Downloading: 
http://www.ibiblio.org/maven2/saxon/saxonb/8.6.1/saxonb-8.6.1.pom
[WARNING] Unable to get resource from repository mirror 
(http://www.ibiblio.org/maven2)


mvn keeps looking for updates even though the artifacts in question are 
contained in both ~/.m2 and the windows server file:/nix/mvn_repos.

Problems:
- I don't understand the warning. file:/nix/mvn_repos contains a 
copy of my local ~/.m2 which is probably not enough.

- because of the warning mvn checks for updates on every build.
- if any repos-mirror has a timeout the build fails instead of using the 
already present artifact.


So while the warnings might be the result of a misconfiguration or 
something the build IMHO shouldn't fail in case of a timeout.


The artifacts in question don't have an associated pom file in the repos 
but I don't understand exactly why/what went wrong while installing 
Some other third party jars do have poms even though I think I installed 
them the same way... strange...

-john

Joern Huxhorn wrote:

[EMAIL PROTECTED] wrote:
Maven is not working anymore, I was trying to add a regular Manifest 
fil into my

jar :-(
[SNIP]
  
I've got similar problems. It seems like mvn-builds will always fail 
in case of a network timeout instead of just using the latest version 
available in .m2/repository... I sometimes even unplugged my network 
cable because of this.


Any ideas (or better yet, a fix!) would be appreciated ;)

Joern.





-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



[M2]:Maven won't work anymore

2006-02-08 Thread kaneda-java
Maven is not working anymore, I was trying to add a regular Manifest fil into my
jar :-(

It seems to be a proxy or a connection problem but even with -o option it won't
work.

I also try to re-install everything but it did not work.

--
+ Error stacktraces are turned on.
[DEBUG] Building Maven user-level plugin registry from: 'C:\Documents and
Settings\e193522\.m2\plugin-registry.xml'
[DEBUG] Building Maven global-level plugin registry from:
'C:\java\PROGRA~1\maven\202A5D~1.1\b\..\conf\plugin-registry.xml'
[INFO] Scanning for projects...
[INFO]

[INFO] Building Maven Default Project
[INFO]task-segment: [install]
[INFO]

[DEBUG] maven-resources-plugin: resolved to version 2.1 from repository central
[DEBUG] Retrieving parent-POM from the repository for project:
null:maven-resources-plugin:maven-plugin:2.1
[DEBUG] Trying repository central
Downloading:
http://www.ibiblio.net/pub/packages/maven2/org/apache/maven/plugins/maven-plugin-parent/2.0/maven-plugin-parent-2.0.pom
[INFO]

[ERROR] BUILD ERROR
[INFO]

[INFO] Error building POM (may not be this project's POM).


Project ID: org.apache.maven.plugins:maven-plugin-parent

Reason: Error getting POM for 'org.apache.maven.plugins:maven-plugin-parent'
from the repository: Error transferring file
  org.apache.maven.plugins:maven-plugin-parent:pom:2.0

from the specified remote repositories:
  central (http://repo1.maven.org/maven2)



[INFO]

[DEBUG] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: Error resolving version
for 'org.apache.maven.plugins:maven-resources-plugin': Unable to read the
metadata file for artifact
'org.apache.maven.plugins:maven-resources-plugin:pom': Error getting POM for
'org.apache.maven.plugins:maven-plugin-parent' from the repository: Error
transferring file
  org.apache.maven.plugins:maven-plugin-parent:pom:2.0

from the specified remote repositories:
  central (http://repo1.maven.org/maven2)

at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin(DefaultLifecycleExecutor.java:1183)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.getMojoDescriptor(DefaultLifecycleExecutor.java:1436)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.bindLifecycleForPackaging(DefaultLifecycleExecutor.java:975)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.constructLifecycleMappings(DefaultLifecycleExecutor.java:941)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:450)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:303)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:270)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:139)
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:249)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
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.PluginVersionResolutionException:
Error resolving version for 'org.apache.maven.plugins:maven-resources-plugin':
Unable to read the metadata file for artifact
'org.apache.maven.plugins:maven-resources-plugin:pom': Error getting POM for
'org.apache.maven.plugins:maven-plugin-parent' from the repository: Error
transferring file
  org.apache.maven.plugins:maven-plugin-parent:pom:2.0

from the specified remote repositories:
  central (http://repo1.maven.org/maven2)

at
org.apache.maven.plugin.version.DefaultPluginVersionManager.resolveMetaVersion(DefaultPluginVersionManager.java:678)
at
org.apache.maven.plugin.version.DefaultPluginVersionManager.resolvePluginVersion(DefaultPluginVersionManager.java:183)
at
org.apache.maven.plugin.version.DefaultPluginVersionManager.resolvePluginVersion(DefaultPluginVersionManager.java:87)
at

Re: [M2]:Maven won't work anymore

2006-02-08 Thread Joern Huxhorn

[EMAIL PROTECTED] wrote:

Maven is not working anymore, I was trying to add a regular Manifest fil into my
jar :-(
[SNIP]
  
I've got similar problems. It seems like mvn-builds will always fail in 
case of a network timeout instead of just using the latest version 
available in .m2/repository... I sometimes even unplugged my network 
cable because of this.


Any ideas (or better yet, a fix!) would be appreciated ;)

Joern.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: [M2]:Maven won't work anymore

2006-02-08 Thread John Casey

can you verify that the path:

org/apache/maven/plugins/maven-plugin-parent/2.0/maven-plugin-parent-2.0.pom 



exists in your local repository? If not, then -o won't help you. I 
suspect it's a problem with traffic on ibiblio, but I dunno for sure. I 
can reach the URL given in that trace below...


-john

[EMAIL PROTECTED] wrote:

Maven is not working anymore, I was trying to add a regular Manifest fil into my
jar :-(

It seems to be a proxy or a connection problem but even with -o option it won't
work.

I also try to re-install everything but it did not work.

--
+ Error stacktraces are turned on.
[DEBUG] Building Maven user-level plugin registry from: 'C:\Documents and
Settings\e193522\.m2\plugin-registry.xml'
[DEBUG] Building Maven global-level plugin registry from:
'C:\java\PROGRA~1\maven\202A5D~1.1\b\..\conf\plugin-registry.xml'
[INFO] Scanning for projects...
[INFO]

[INFO] Building Maven Default Project
[INFO]task-segment: [install]
[INFO]

[DEBUG] maven-resources-plugin: resolved to version 2.1 from repository central
[DEBUG] Retrieving parent-POM from the repository for project:
null:maven-resources-plugin:maven-plugin:2.1
[DEBUG] Trying repository central
Downloading:
http://www.ibiblio.net/pub/packages/maven2/org/apache/maven/plugins/maven-plugin-parent/2.0/maven-plugin-parent-2.0.pom
[INFO]

[ERROR] BUILD ERROR
[INFO]

[INFO] Error building POM (may not be this project's POM).


Project ID: org.apache.maven.plugins:maven-plugin-parent

Reason: Error getting POM for 'org.apache.maven.plugins:maven-plugin-parent'
from the repository: Error transferring file
  org.apache.maven.plugins:maven-plugin-parent:pom:2.0

from the specified remote repositories:
  central (http://repo1.maven.org/maven2)



[INFO]

[DEBUG] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: Error resolving version
for 'org.apache.maven.plugins:maven-resources-plugin': Unable to read the
metadata file for artifact
'org.apache.maven.plugins:maven-resources-plugin:pom': Error getting POM for
'org.apache.maven.plugins:maven-plugin-parent' from the repository: Error
transferring file
  org.apache.maven.plugins:maven-plugin-parent:pom:2.0

from the specified remote repositories:
  central (http://repo1.maven.org/maven2)

at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin(DefaultLifecycleExecutor.java:1183)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.getMojoDescriptor(DefaultLifecycleExecutor.java:1436)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.bindLifecycleForPackaging(DefaultLifecycleExecutor.java:975)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.constructLifecycleMappings(DefaultLifecycleExecutor.java:941)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:450)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:303)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:270)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:139)
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:249)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
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.PluginVersionResolutionException:
Error resolving version for 'org.apache.maven.plugins:maven-resources-plugin':
Unable to read the metadata file for artifact
'org.apache.maven.plugins:maven-resources-plugin:pom': Error getting POM for
'org.apache.maven.plugins:maven-plugin-parent' from the repository: Error
transferring file
  org.apache.maven.plugins:maven-plugin-parent:pom:2.0

from the specified remote repositories:
  central (http://repo1.maven.org/maven2)

at

Re: [M2]:Maven won't work anymore

2006-02-08 Thread John Casey
actually, that's where offline mode is helpful. Of course, if you don't 
have all the artifacts/poms cached in your local repository, it won't do 
you much good...


-john

Joern Huxhorn wrote:

[EMAIL PROTECTED] wrote:
Maven is not working anymore, I was trying to add a regular Manifest 
fil into my

jar :-(
[SNIP]
  
I've got similar problems. It seems like mvn-builds will always fail in 
case of a network timeout instead of just using the latest version 
available in .m2/repository... I sometimes even unplugged my network 
cable because of this.


Any ideas (or better yet, a fix!) would be appreciated ;)

Joern.


-
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]



Re: [M2]:Maven won't work anymore

2006-02-08 Thread Emmanuel Venisse

Do you use a proxy?

http://maven.apache.org/guides/mini/guide-proxies.html

Emmanuel

John Casey a écrit :

can you verify that the path:

org/apache/maven/plugins/maven-plugin-parent/2.0/maven-plugin-parent-2.0.pom 



exists in your local repository? If not, then -o won't help you. I 
suspect it's a problem with traffic on ibiblio, but I dunno for sure. I 
can reach the URL given in that trace below...


-john

[EMAIL PROTECTED] wrote:

Maven is not working anymore, I was trying to add a regular Manifest 
fil into my

jar :-(

It seems to be a proxy or a connection problem but even with -o option 
it won't

work.

I also try to re-install everything but it did not work.

--
+ Error stacktraces are turned on.
[DEBUG] Building Maven user-level plugin registry from: 'C:\Documents and
Settings\e193522\.m2\plugin-registry.xml'
[DEBUG] Building Maven global-level plugin registry from:
'C:\java\PROGRA~1\maven\202A5D~1.1\b\..\conf\plugin-registry.xml'
[INFO] Scanning for projects...
[INFO]
 


[INFO] Building Maven Default Project
[INFO]task-segment: [install]
[INFO]
 

[DEBUG] maven-resources-plugin: resolved to version 2.1 from 
repository central

[DEBUG] Retrieving parent-POM from the repository for project:
null:maven-resources-plugin:maven-plugin:2.1
[DEBUG] Trying repository central
Downloading:
http://www.ibiblio.net/pub/packages/maven2/org/apache/maven/plugins/maven-plugin-parent/2.0/maven-plugin-parent-2.0.pom 


[INFO]
 


[ERROR] BUILD ERROR
[INFO]
 


[INFO] Error building POM (may not be this project's POM).


Project ID: org.apache.maven.plugins:maven-plugin-parent

Reason: Error getting POM for 
'org.apache.maven.plugins:maven-plugin-parent'

from the repository: Error transferring file
  org.apache.maven.plugins:maven-plugin-parent:pom:2.0

from the specified remote repositories:
  central (http://repo1.maven.org/maven2)



[INFO]
 


[DEBUG] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: Error 
resolving version

for 'org.apache.maven.plugins:maven-resources-plugin': Unable to read the
metadata file for artifact
'org.apache.maven.plugins:maven-resources-plugin:pom': Error getting 
POM for

'org.apache.maven.plugins:maven-plugin-parent' from the repository: Error
transferring file
  org.apache.maven.plugins:maven-plugin-parent:pom:2.0

from the specified remote repositories:
  central (http://repo1.maven.org/maven2)

at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin(DefaultLifecycleExecutor.java:1183) 


at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.getMojoDescriptor(DefaultLifecycleExecutor.java:1436) 


at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.bindLifecycleForPackaging(DefaultLifecycleExecutor.java:975) 


at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.constructLifecycleMappings(DefaultLifecycleExecutor.java:941) 


at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:450) 


at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:303) 


at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:270) 


at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:139) 


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:249)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) 


at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) 


at java.lang.reflect.Method.invoke(Method.java:324)
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.PluginVersionResolutionException:
Error resolving version for 
'org.apache.maven.plugins:maven-resources-plugin':

Unable to read the metadata file for artifact
'org.apache.maven.plugins:maven-resources-plugin:pom': Error getting 
POM for

'org.apache.maven.plugins:maven-plugin-parent' from the repository: Error
transferring file
  org.apache.maven.plugins:maven-plugin-parent:pom:2.0

from the specified remote repositories:
  central