You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by fa...@mpsa.com on 2005/07/29 16:54:27 UTC
[m2] Weird dependency behaviour...
I've figured out that the lib that causes the trouble is "
commons-jelly-tags-jsl"...
But I just can't see why.
Best Regards / Cordialement,
Fabrice BELLINGARD
DINQ/DSIN/INSI/EATE/IDVS/AIDV
(+33) (01 61) 45 15 91 - fabrice.belingard@mpsa.com
----- Réacheminé par FABRICE BELLINGARD - E222731/users/PSA le 29/07/2005
16:50 -----
FABRICE
BELLINGARD -
E222731/users/PSA Pour
Maven Users List
29/07/2005 15:30 <us...@maven.apache.org>
cc
Objet
Weird dependency behaviour...
Hi Maveners,
I observe a strange behaviour when building the plugin I'm developing. Here
are the dependencies for which the build is OK :
<dependency>
<groupId>org.apache.maven.reporting</groupId>
<artifactId>maven-reporting-api</artifactId>
<version>2.0-alpha-3</version>
</dependency>
<dependency>
<groupId>org.apache.maven</groupId>
<artifactId>maven-plugin-api</artifactId>
<version>2.0-alpha-3</version>
</dependency>
<dependency>
<groupId>oro</groupId>
<artifactId>oro</artifactId>
<version>2.0.7</version>
</dependency>
<dependency>
<groupId>commons-lang</groupId>
<artifactId>commons-lang</artifactId>
<version>2.0</version>
</dependency>
<dependency>
<groupId>commons-jelly</groupId>
<artifactId>commons-jelly</artifactId>
<version>1.0-beta-4</version>
</dependency>
<dependency>
<groupId>ant</groupId>
<artifactId>ant</artifactId>
<version>1.6.5</version>
</dependency>
<dependency>
<groupId>dom4j</groupId>
<artifactId>dom4j</artifactId>
<version>1.4</version>
</dependency>
The plugin is compiled and installed, but can't run because it requires
other lib at runtime. So I add the following dependencies to make it work:
<dependency>
<groupId>commons-beanutils</groupId>
<artifactId>commons-beanutils</artifactId>
<version>1.7.0</version>
<scope>runtime</scope>
</dependency>
<dependency>
<groupId>commons-jexl</groupId>
<artifactId>commons-jexl</artifactId>
<version>1.0</version>
<scope>runtime</scope>
</dependency>
<dependency>
<groupId>commons-jelly</groupId>
<artifactId>commons-jelly-tags-jsl</artifactId>
<version>1.0</version>
<scope>runtime</scope>
</dependency>
<dependency>
<groupId>commons-jelly</groupId>
<artifactId>commons-jelly-tags-xml</artifactId>
<version>1.1</version>
<scope>runtime</scope>
</dependency>
I build again (the Java sources are not compiled this time because none has
been changed): the plugin is installed and runs perfectly.
However, if I clean my project (i.e. the generated classes are deleted),
and build again, then I get the following stacktrace :
Compiling 15 source files to
C:\fabM2\workspace\maven-jxr-plugin\target\classes
[INFO]
-------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO]
-------------------------------------------------------------------------
[INFO] Reason: Compilation failure
[INFO]
-------------------------------------------------------------------------
[INFO] no more tokens - could not parse error message:
C:\fabM2\workspace\maven-
jxr-plugin\src\main\java\org\apache\maven\plugin\jxr\JXR.java:26: package
org.ap
ache.maven.plugin.logging does not exist
import org.apache.maven.plugin.logging.Log;
^
C:\fabM2\workspace\maven-jxr-plugin\src\main\java\org\apache\maven\plugin\jxr\JX
R.java:[37,12] cannot resolve symbol
symbol : class Log
location: class org.apache.maven.plugin.jxr.JXR
no more tokens - could not parse error message:
C:\fabM2\workspace\maven-jxr-plu
gin\src\main\java\org\apache\maven\plugin\jxr\pacman\PackageManager.java:25:
pac
kage org.apache.maven.plugin.logging does not exist
import org.apache.maven.plugin.logging.Log;
^
C:\fabM2\workspace\maven-jxr-plugin\src\main\java\org\apache\maven\plugin\jxr\pa
cman\PackageManager.java:[35,12] cannot resolve symbol
symbol : class Log
location: class org.apache.maven.plugin.jxr.pacman.PackageManager
C:\fabM2\workspace\maven-jxr-plugin\src\main\java\org\apache\maven\plugin\jxr\pa
cman\PackageManager.java:[53,26] cannot resolve symbol
symbol : class Log
location: class org.apache.maven.plugin.jxr.pacman.PackageManager
C:\fabM2\workspace\maven-jxr-plugin\src\main\java\org\apache\maven\plugin\jxr\JX
R.java:[87,78] cannot resolve symbol
symbol : class Log
location: class org.apache.maven.plugin.jxr.JXR
The package "org.apache.maven.plugin.logging" seems to be missing this
time! How come?
I don't see where the problem comes from, as I only added dependencies for
runtime, and as those dependencies are not linked to other maven libs...
Any idea where this problem might come from?
Thanks!
Best Regards / Cordialement,
Fabrice BELLINGARD
DINQ/DSIN/INSI/EATE/IDVS/AIDV
(+33) (01 61) 45 15 91 - fabrice.belingard@mpsa.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: [ m2 ] stack trace printed in log when dependency not found?
Posted by Stephane Nicoll <st...@gmail.com>.
FYI:
I have the same and I do not use -e or -X.
Cheers,
Stéphane
On 8/25/05, Kenney Westerhof <fo...@neonics.com> wrote:
> On Thu, 25 Aug 2005 fabrice.belingard@mpsa.com wrote:
>
> You didn't run m2 with -e or -X by any chance?
>
> Btw, it doesn't try to download the artifact itself, but the pom:
>
> [INFO] commons-dbcp: updating metadata due to status of 'none'
>
> That's a 'new' feature: it checks poms with certain status each day to see
> if they're updated (possible pom statusses are 'deployed', 'converted',
> 'verified' (and none)).
>
> It shouldn't print a stacktrace when neither -X or -e has been supplied,
> though.
>
> -- Kenney
>
> >
> >
> >
> >
> > Hi guys,
> >
> > I'm using of the latest m2 builds (20050824.111500).
> > I've just discovered that when m2 tries to download a dependency and can't
> > find it on any remote repository, it prints a stack trace (see below) in
> > the log. In my case, the dependency exists in the local repository, so the
> > buld is successful.
> >
> > So my question is: should that stack trace be printed in the log?
> >
> > Cheers,
> > Fabrice.
> >
> > ------------- PART OF THE LOG -------------
> >
> > [INFO] commons-dbcp: updating metadata due to status of 'none'
> > Downloading:
> > http://repo1.maven.org/maven2/commons-dbcp/commons-dbcp/1.1-dev/com
> > mons-dbcp-1.1-dev.pom
> > [WARNING] Unable to get resource from repository
> > http://repo1.maven.org/maven2
> > Downloading: /commons-dbcp/commons-dbcp/1.1-dev/commons-dbcp-1.1-dev.pom
> > [WARNING] Unable to get resource from repository
> > [WARNING] Error updating POM - using existing version
> > org.apache.maven.artifact.resolver.ArtifactResolutionException: Unable to
> > download the artifact from any repository
> > commons-dbcp:commons-dbcp:1.1-dev:pom from the specified remote
> > repositories: http://repo1.maven.org/maven2,
> > at
> > org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:127)
> > at
> > org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveAlways(DefaultArtifactResolver.java:69)
> > at
> > org.apache.maven.project.DefaultMavenProjectBuilder.findModelFromRepository(DefaultMavenProjectBuilder.java:351)
> > at
> > org.apache.maven.project.DefaultMavenProjectBuilder.buildFromRepository(DefaultMavenProjectBuilder.java:306)
> > at
> > org.apache.maven.project.artifact.MavenMetadataSource.retrieve(MavenMetadataSource.java:84)
> > at
> > org.apache.maven.artifact.resolver.DefaultArtifactCollector.recurse(DefaultArtifactCollector.java:186)
> > at
> > org.apache.maven.artifact.resolver.DefaultArtifactCollector.collect(DefaultArtifactCollector.java:70)
> > at
> > org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:192)
> > at
> > org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:180)
> > at
> > org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:151)
> > at
> > org.apache.maven.plugin.DefaultPluginManager.resolveTransitiveDependencies(DefaultPluginManager.java:1182)
> > at
> > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:312)
> > at
> > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:478)
> > at
> > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:451)
> > at
> > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:437)
> > at
> > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:273)
> > at
> > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:131)
> > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:186)
> > at org.apache.maven.cli.MavenCli.main(MavenCli.java:316)
> > 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.wagon.ResourceDoesNotExistException: Unable to
> > download the artifact from any repository
> > at
> > org.apache.maven.artifact.manager.DefaultWagonManager.getArtifact(DefaultWagonManager.java:233)
> > at
> > org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:110)
> > ... 26 more
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > For additional commands, e-mail: users-help@maven.apache.org
> >
>
> --
> Kenney Westerhof
> http://www.neonics.com
> GPG public key: http://www.gods.nl/~forge/kenneyw.key
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
--
.::You're welcome ::.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Réf. : Re: [ m2 ] stack trace printed in log when dependency not found?
Posted by fa...@mpsa.com.
Hi Kenney,
For the 'none', I better understand now. That's because I added JARs to my
m2 repo manually (as they were not on the web). So where do I need to
specify the status of the JARs I put in my local repo?
As for the stack trace, I don't run m2 with -e nor -X, so that's why I find
it weird to see it in the log...
Thanks for help!
Best Regards / Cordialement,
Fabrice BELLINGARD
DINQ/DSIN/INSI/EATE/IDVS/AIDV
(+33) (01 61) 45 15 91 - fabrice.belingard@mpsa.com
Kenney Westerhof
<forge@neonics.c
om> Pour
Maven Users List
25/08/2005 10:59 <us...@maven.apache.org>
cc
Veuillez Objet
répondre à Re: [ m2 ] stack trace printed in
Maven Users List log when dependency not found?
<users@maven.apa
che.org>
On Thu, 25 Aug 2005 fabrice.belingard@mpsa.com wrote:
You didn't run m2 with -e or -X by any chance?
Btw, it doesn't try to download the artifact itself, but the pom:
[INFO] commons-dbcp: updating metadata due to status of 'none'
That's a 'new' feature: it checks poms with certain status each day to see
if they're updated (possible pom statusses are 'deployed', 'converted',
'verified' (and none)).
It shouldn't print a stacktrace when neither -X or -e has been supplied,
though.
-- Kenney
>
>
>
>
> Hi guys,
>
> I'm using of the latest m2 builds (20050824.111500).
> I've just discovered that when m2 tries to download a dependency and
can't
> find it on any remote repository, it prints a stack trace (see below) in
> the log. In my case, the dependency exists in the local repository, so
the
> buld is successful.
>
> So my question is: should that stack trace be printed in the log?
>
> Cheers,
> Fabrice.
>
> ------------- PART OF THE LOG -------------
>
> [INFO] commons-dbcp: updating metadata due to status of 'none'
> Downloading:
> http://repo1.maven.org/maven2/commons-dbcp/commons-dbcp/1.1-dev/com
> mons-dbcp-1.1-dev.pom
> [WARNING] Unable to get resource from repository
> http://repo1.maven.org/maven2
> Downloading: /commons-dbcp/commons-dbcp/1.1-dev/commons-dbcp-1.1-dev.pom
> [WARNING] Unable to get resource from repository
> [WARNING] Error updating POM - using existing version
> org.apache.maven.artifact.resolver.ArtifactResolutionException: Unable to
> download the artifact from any repository
> commons-dbcp:commons-dbcp:1.1-dev:pom from the specified remote
> repositories: http://repo1.maven.org/maven2,
> at
>
org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:127)
> at
>
org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveAlways(DefaultArtifactResolver.java:69)
> at
>
org.apache.maven.project.DefaultMavenProjectBuilder.findModelFromRepository(DefaultMavenProjectBuilder.java:351)
> at
>
org.apache.maven.project.DefaultMavenProjectBuilder.buildFromRepository(DefaultMavenProjectBuilder.java:306)
> at
>
org.apache.maven.project.artifact.MavenMetadataSource.retrieve(MavenMetadataSource.java:84)
> at
>
org.apache.maven.artifact.resolver.DefaultArtifactCollector.recurse(DefaultArtifactCollector.java:186)
> at
>
org.apache.maven.artifact.resolver.DefaultArtifactCollector.collect(DefaultArtifactCollector.java:70)
> at
>
org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:192)
> at
>
org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:180)
> at
>
org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:151)
> at
>
org.apache.maven.plugin.DefaultPluginManager.resolveTransitiveDependencies(DefaultPluginManager.java:1182)
> at
>
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:312)
> at
>
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:478)
> at
>
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:451)
> at
>
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:437)
> at
>
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:273)
> at
>
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:131)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:186)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:316)
> 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.wagon.ResourceDoesNotExistException: Unable
to
> download the artifact from any repository
> at
>
org.apache.maven.artifact.manager.DefaultWagonManager.getArtifact(DefaultWagonManager.java:233)
> at
>
org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:110)
> ... 26 more
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
--
Kenney Westerhof
http://www.neonics.com
GPG public key: http://www.gods.nl/~forge/kenneyw.key
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: [m2] Error in a POM on M2 official repo
Posted by Brett Porter <br...@gmail.com>.
Correct. I think I've seen type test more than once, maybe repoclean
needs a new rule.
I'll probably turn off the autoupdate of released poms by default for
the beta-1 release as its too annoying right now. You can do that in
your settings by redefining the repository with
<releases><updatePolicy>never</updatePolicy></releases>.
- Brett
On 8/26/05, Kenney Westerhof <fo...@neonics.com> wrote:
> On Fri, 26 Aug 2005 fabrice.belingard@mpsa.com wrote:
>
> Hi,
>
> Add
>
> <distributionManagement>
> <status>verified</status>
> </distributionManagement>
>
> just before the following line:
>
> </project>
>
> However, the whole idea of pom updating is so buggy poms like these
> can be fixed automatically. Brett, can you comment on this?
>
> -- Kenney
> >
> >
> > Hi guys,
> >
> > I'm using a library that depends on struts-menu 2.3. The problem is that
> > the POM of the latter contains an error in its depedencies (the last one
> > actually):
> >
> > ...
> > <dependency>
> > <groupId>junit</groupId>
> > <artifactId>junit</artifactId>
> > <version>3.8.1</version>
> > <type>test</type>
> > </dependency>
> > ...
> >
> > "type" shouldn't be here, but "scope" instead.
> >
> > So apart from the fact that the author (or someone else...) has to correct
> > this error that on M2 repo, how can I tell Maven 2 not to update the POMs?
> > (or only this very special POM if possible) Because I don't want to modify
> > my local copy every day! ;)
> >
> > Thanks for your help!
> >
> > Best Regards / Cordialement,
> > Fabrice BELLINGARD
> > DINQ/DSIN/INSI/EATE/IDVS/AIDV
> > (+33) (01 61) 45 15 91 - fabrice.belingard@mpsa.com
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > For additional commands, e-mail: users-help@maven.apache.org
> >
>
> --
> Kenney Westerhof
> http://www.neonics.com
> GPG public key: http://www.gods.nl/~forge/kenneyw.key
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: [m2] Error in a POM on M2 official repo
Posted by Kenney Westerhof <fo...@neonics.com>.
On Fri, 26 Aug 2005 fabrice.belingard@mpsa.com wrote:
Hi,
Add
<distributionManagement>
<status>verified</status>
</distributionManagement>
just before the following line:
</project>
However, the whole idea of pom updating is so buggy poms like these
can be fixed automatically. Brett, can you comment on this?
-- Kenney
>
>
> Hi guys,
>
> I'm using a library that depends on struts-menu 2.3. The problem is that
> the POM of the latter contains an error in its depedencies (the last one
> actually):
>
> ...
> <dependency>
> <groupId>junit</groupId>
> <artifactId>junit</artifactId>
> <version>3.8.1</version>
> <type>test</type>
> </dependency>
> ...
>
> "type" shouldn't be here, but "scope" instead.
>
> So apart from the fact that the author (or someone else...) has to correct
> this error that on M2 repo, how can I tell Maven 2 not to update the POMs?
> (or only this very special POM if possible) Because I don't want to modify
> my local copy every day! ;)
>
> Thanks for your help!
>
> Best Regards / Cordialement,
> Fabrice BELLINGARD
> DINQ/DSIN/INSI/EATE/IDVS/AIDV
> (+33) (01 61) 45 15 91 - fabrice.belingard@mpsa.com
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
--
Kenney Westerhof
http://www.neonics.com
GPG public key: http://www.gods.nl/~forge/kenneyw.key
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: [m2] Error in a POM on M2 official repo
Posted by Edwin Punzalan <ep...@exist.com>.
It would have already been downloaded into your local repo... so just
edit the junit/junit/3.8.1/junit-3.8.1.pom in your local repository and
change type to scope. :D
fabrice.belingard@mpsa.com wrote:
>
>
>Hi guys,
>
>I'm using a library that depends on struts-menu 2.3. The problem is that
>the POM of the latter contains an error in its depedencies (the last one
>actually):
>
>...
> <dependency>
> <groupId>junit</groupId>
> <artifactId>junit</artifactId>
> <version>3.8.1</version>
> <type>test</type>
> </dependency>
>...
>
>"type" shouldn't be here, but "scope" instead.
>
>So apart from the fact that the author (or someone else...) has to correct
>this error that on M2 repo, how can I tell Maven 2 not to update the POMs?
>(or only this very special POM if possible) Because I don't want to modify
>my local copy every day! ;)
>
>Thanks for your help!
>
>Best Regards / Cordialement,
>Fabrice BELLINGARD
>DINQ/DSIN/INSI/EATE/IDVS/AIDV
>(+33) (01 61) 45 15 91 - fabrice.belingard@mpsa.com
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>For additional commands, e-mail: users-help@maven.apache.org
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
[m2] Error in a POM on M2 official repo
Posted by fa...@mpsa.com.
Hi guys,
I'm using a library that depends on struts-menu 2.3. The problem is that
the POM of the latter contains an error in its depedencies (the last one
actually):
...
<dependency>
<groupId>junit</groupId>
<artifactId>junit</artifactId>
<version>3.8.1</version>
<type>test</type>
</dependency>
...
"type" shouldn't be here, but "scope" instead.
So apart from the fact that the author (or someone else...) has to correct
this error that on M2 repo, how can I tell Maven 2 not to update the POMs?
(or only this very special POM if possible) Because I don't want to modify
my local copy every day! ;)
Thanks for your help!
Best Regards / Cordialement,
Fabrice BELLINGARD
DINQ/DSIN/INSI/EATE/IDVS/AIDV
(+33) (01 61) 45 15 91 - fabrice.belingard@mpsa.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: [ m2 ] stack trace printed in log when dependency not found?
Posted by Kenney Westerhof <fo...@neonics.com>.
On Thu, 25 Aug 2005 fabrice.belingard@mpsa.com wrote:
You didn't run m2 with -e or -X by any chance?
Btw, it doesn't try to download the artifact itself, but the pom:
[INFO] commons-dbcp: updating metadata due to status of 'none'
That's a 'new' feature: it checks poms with certain status each day to see
if they're updated (possible pom statusses are 'deployed', 'converted',
'verified' (and none)).
It shouldn't print a stacktrace when neither -X or -e has been supplied,
though.
-- Kenney
>
>
>
>
> Hi guys,
>
> I'm using of the latest m2 builds (20050824.111500).
> I've just discovered that when m2 tries to download a dependency and can't
> find it on any remote repository, it prints a stack trace (see below) in
> the log. In my case, the dependency exists in the local repository, so the
> buld is successful.
>
> So my question is: should that stack trace be printed in the log?
>
> Cheers,
> Fabrice.
>
> ------------- PART OF THE LOG -------------
>
> [INFO] commons-dbcp: updating metadata due to status of 'none'
> Downloading:
> http://repo1.maven.org/maven2/commons-dbcp/commons-dbcp/1.1-dev/com
> mons-dbcp-1.1-dev.pom
> [WARNING] Unable to get resource from repository
> http://repo1.maven.org/maven2
> Downloading: /commons-dbcp/commons-dbcp/1.1-dev/commons-dbcp-1.1-dev.pom
> [WARNING] Unable to get resource from repository
> [WARNING] Error updating POM - using existing version
> org.apache.maven.artifact.resolver.ArtifactResolutionException: Unable to
> download the artifact from any repository
> commons-dbcp:commons-dbcp:1.1-dev:pom from the specified remote
> repositories: http://repo1.maven.org/maven2,
> at
> org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:127)
> at
> org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveAlways(DefaultArtifactResolver.java:69)
> at
> org.apache.maven.project.DefaultMavenProjectBuilder.findModelFromRepository(DefaultMavenProjectBuilder.java:351)
> at
> org.apache.maven.project.DefaultMavenProjectBuilder.buildFromRepository(DefaultMavenProjectBuilder.java:306)
> at
> org.apache.maven.project.artifact.MavenMetadataSource.retrieve(MavenMetadataSource.java:84)
> at
> org.apache.maven.artifact.resolver.DefaultArtifactCollector.recurse(DefaultArtifactCollector.java:186)
> at
> org.apache.maven.artifact.resolver.DefaultArtifactCollector.collect(DefaultArtifactCollector.java:70)
> at
> org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:192)
> at
> org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:180)
> at
> org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:151)
> at
> org.apache.maven.plugin.DefaultPluginManager.resolveTransitiveDependencies(DefaultPluginManager.java:1182)
> at
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:312)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:478)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:451)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:437)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:273)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:131)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:186)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:316)
> 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.wagon.ResourceDoesNotExistException: Unable to
> download the artifact from any repository
> at
> org.apache.maven.artifact.manager.DefaultWagonManager.getArtifact(DefaultWagonManager.java:233)
> at
> org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:110)
> ... 26 more
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
--
Kenney Westerhof
http://www.neonics.com
GPG public key: http://www.gods.nl/~forge/kenneyw.key
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
[ m2 ] stack trace printed in log when dependency not found?
Posted by fa...@mpsa.com.
Hi guys,
I'm using of the latest m2 builds (20050824.111500).
I've just discovered that when m2 tries to download a dependency and can't
find it on any remote repository, it prints a stack trace (see below) in
the log. In my case, the dependency exists in the local repository, so the
buld is successful.
So my question is: should that stack trace be printed in the log?
Cheers,
Fabrice.
------------- PART OF THE LOG -------------
[INFO] commons-dbcp: updating metadata due to status of 'none'
Downloading:
http://repo1.maven.org/maven2/commons-dbcp/commons-dbcp/1.1-dev/com
mons-dbcp-1.1-dev.pom
[WARNING] Unable to get resource from repository
http://repo1.maven.org/maven2
Downloading: /commons-dbcp/commons-dbcp/1.1-dev/commons-dbcp-1.1-dev.pom
[WARNING] Unable to get resource from repository
[WARNING] Error updating POM - using existing version
org.apache.maven.artifact.resolver.ArtifactResolutionException: Unable to
download the artifact from any repository
commons-dbcp:commons-dbcp:1.1-dev:pom from the specified remote
repositories: http://repo1.maven.org/maven2,
at
org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:127)
at
org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveAlways(DefaultArtifactResolver.java:69)
at
org.apache.maven.project.DefaultMavenProjectBuilder.findModelFromRepository(DefaultMavenProjectBuilder.java:351)
at
org.apache.maven.project.DefaultMavenProjectBuilder.buildFromRepository(DefaultMavenProjectBuilder.java:306)
at
org.apache.maven.project.artifact.MavenMetadataSource.retrieve(MavenMetadataSource.java:84)
at
org.apache.maven.artifact.resolver.DefaultArtifactCollector.recurse(DefaultArtifactCollector.java:186)
at
org.apache.maven.artifact.resolver.DefaultArtifactCollector.collect(DefaultArtifactCollector.java:70)
at
org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:192)
at
org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:180)
at
org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:151)
at
org.apache.maven.plugin.DefaultPluginManager.resolveTransitiveDependencies(DefaultPluginManager.java:1182)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:312)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:478)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:451)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:437)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:273)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:131)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:186)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:316)
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.wagon.ResourceDoesNotExistException: Unable to
download the artifact from any repository
at
org.apache.maven.artifact.manager.DefaultWagonManager.getArtifact(DefaultWagonManager.java:233)
at
org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:110)
... 26 more
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: [m2] Weird dependency behaviour...
Posted by Brett Porter <br...@gmail.com>.
Very strange - the plugin API provides that dependency.
However, you shouldn't have a need for any of the Jelly, Jexl or Ant
dependencies above. If the code uses them in any way, it needs to be
removed.
Cheers,
Brett
On 7/30/05, fabrice.belingard@mpsa.com <fa...@mpsa.com> wrote:
>
>
>
>
> I've figured out that the lib that causes the trouble is "
> commons-jelly-tags-jsl"...
> But I just can't see why.
>
> Best Regards / Cordialement,
> Fabrice BELLINGARD
> DINQ/DSIN/INSI/EATE/IDVS/AIDV
> (+33) (01 61) 45 15 91 - fabrice.belingard@mpsa.com
>
> ----- Réacheminé par FABRICE BELLINGARD - E222731/users/PSA le 29/07/2005
> 16:50 -----
>
> FABRICE
> BELLINGARD -
> E222731/users/PSA Pour
> Maven Users List
> 29/07/2005 15:30 <us...@maven.apache.org>
> cc
>
> Objet
> Weird dependency behaviour...
>
>
>
>
>
>
>
>
>
> Hi Maveners,
>
> I observe a strange behaviour when building the plugin I'm developing. Here
> are the dependencies for which the build is OK :
>
> <dependency>
> <groupId>org.apache.maven.reporting</groupId>
> <artifactId>maven-reporting-api</artifactId>
> <version>2.0-alpha-3</version>
> </dependency>
> <dependency>
> <groupId>org.apache.maven</groupId>
> <artifactId>maven-plugin-api</artifactId>
> <version>2.0-alpha-3</version>
> </dependency>
> <dependency>
> <groupId>oro</groupId>
> <artifactId>oro</artifactId>
> <version>2.0.7</version>
> </dependency>
> <dependency>
> <groupId>commons-lang</groupId>
> <artifactId>commons-lang</artifactId>
> <version>2.0</version>
> </dependency>
> <dependency>
> <groupId>commons-jelly</groupId>
> <artifactId>commons-jelly</artifactId>
> <version>1.0-beta-4</version>
> </dependency>
> <dependency>
> <groupId>ant</groupId>
> <artifactId>ant</artifactId>
> <version>1.6.5</version>
> </dependency>
> <dependency>
> <groupId>dom4j</groupId>
> <artifactId>dom4j</artifactId>
> <version>1.4</version>
> </dependency>
>
> The plugin is compiled and installed, but can't run because it requires
> other lib at runtime. So I add the following dependencies to make it work:
>
> <dependency>
> <groupId>commons-beanutils</groupId>
> <artifactId>commons-beanutils</artifactId>
> <version>1.7.0</version>
> <scope>runtime</scope>
> </dependency>
> <dependency>
> <groupId>commons-jexl</groupId>
> <artifactId>commons-jexl</artifactId>
> <version>1.0</version>
> <scope>runtime</scope>
> </dependency>
> <dependency>
> <groupId>commons-jelly</groupId>
> <artifactId>commons-jelly-tags-jsl</artifactId>
> <version>1.0</version>
> <scope>runtime</scope>
> </dependency>
> <dependency>
> <groupId>commons-jelly</groupId>
> <artifactId>commons-jelly-tags-xml</artifactId>
> <version>1.1</version>
> <scope>runtime</scope>
> </dependency>
>
> I build again (the Java sources are not compiled this time because none has
> been changed): the plugin is installed and runs perfectly.
>
> However, if I clean my project (i.e. the generated classes are deleted),
> and build again, then I get the following stacktrace :
>
>
> Compiling 15 source files to
> C:\fabM2\workspace\maven-jxr-plugin\target\classes
> [INFO]
> -------------------------------------------------------------------------
> [INFO] BUILD FAILURE
> [INFO]
> -------------------------------------------------------------------------
> [INFO] Reason: Compilation failure
> [INFO]
> -------------------------------------------------------------------------
> [INFO] no more tokens - could not parse error message:
> C:\fabM2\workspace\maven-
> jxr-plugin\src\main\java\org\apache\maven\plugin\jxr\JXR.java:26: package
> org.ap
> ache.maven.plugin.logging does not exist
> import org.apache.maven.plugin.logging.Log;
> ^
>
> C:\fabM2\workspace\maven-jxr-plugin\src\main\java\org\apache\maven\plugin\jxr\JX
> R.java:[37,12] cannot resolve symbol
> symbol : class Log
> location: class org.apache.maven.plugin.jxr.JXR
> no more tokens - could not parse error message:
> C:\fabM2\workspace\maven-jxr-plu
> gin\src\main\java\org\apache\maven\plugin\jxr\pacman\PackageManager.java:25:
> pac
> kage org.apache.maven.plugin.logging does not exist
> import org.apache.maven.plugin.logging.Log;
> ^
>
> C:\fabM2\workspace\maven-jxr-plugin\src\main\java\org\apache\maven\plugin\jxr\pa
> cman\PackageManager.java:[35,12] cannot resolve symbol
> symbol : class Log
> location: class org.apache.maven.plugin.jxr.pacman.PackageManager
> C:\fabM2\workspace\maven-jxr-plugin\src\main\java\org\apache\maven\plugin\jxr\pa
> cman\PackageManager.java:[53,26] cannot resolve symbol
> symbol : class Log
> location: class org.apache.maven.plugin.jxr.pacman.PackageManager
> C:\fabM2\workspace\maven-jxr-plugin\src\main\java\org\apache\maven\plugin\jxr\JX
> R.java:[87,78] cannot resolve symbol
> symbol : class Log
> location: class org.apache.maven.plugin.jxr.JXR
>
>
> The package "org.apache.maven.plugin.logging" seems to be missing this
> time! How come?
> I don't see where the problem comes from, as I only added dependencies for
> runtime, and as those dependencies are not linked to other maven libs...
>
> Any idea where this problem might come from?
>
> Thanks!
>
> Best Regards / Cordialement,
> Fabrice BELLINGARD
> DINQ/DSIN/INSI/EATE/IDVS/AIDV
> (+33) (01 61) 45 15 91 - fabrice.belingard@mpsa.com
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org