You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Michael Delaney <md...@upromise.com> on 2008/05/27 22:41:13 UTC
Upgrading Maven 2.0.5 -> 2.0.9
All,
I am testing out upgrading from Maven 2.0.5 to 2.0.9, I was reading
documentation that said that there were some dependency sanity checks
one should do before upgrading to the latest version of Maven from 2.0.6
or earlier (the page I am referring to is located at
http://maven.apache.org/plugins/maven-dependency-plugin/examples/prepari
ng-dependencies.html).
On the page pasted above, it says to run the Maven dependency analyzer
to check that everything is okay with how your dependencies are being
referenced. After building my project, I ran the command as per the
example but the ouput was a little confusing to me. It said there were
errors but didn't list what errors were there. So to try to get more
information, I tried a few things: 1) Added "-Dverbose=true" to the
command, no additional output; 2) Edited the top-level pom.xml file to
include the XML element below ... again with no output.
Could something please help me understand what I am doing wrong?
[ POM.XML Elements ]
<build>
<plugins>
<plugin>
<artifactId>maven-dependency-plugin</artifactId>
<configuration>
<verbose>true</verbose>
</configuration>
</plugin>
... ... ...
</plugins>
</build>
[ Ouput ]
[INFO] cactus-support:cactus:jar:1.7.2:compile
[INFO] xerces:xercesImpl:jar:2.8.0:compile
[WARNING] Potential problems discovered.
[INFO] Found Resolved Dependency / DependencyManagement mismatches:
[INFO] Nothing in DepMgt.
[INFO]
------------------------------------------------------------------------
[INFO] BUILD SUCCESSFUL
[INFO]
------------------------------------------------------------------------
[INFO] Total time: 19 seconds
[INFO] Finished at: Tue May 27 16:19:35 EDT 2008
[INFO] Final Memory: 17M/127M
[INFO]
------------------------------------------------------------------------
Re: Upgrading Maven 2.0.5 -> 2.0.9
Posted by Brian Fox <br...@reply.infinity.nu>.
There appear to be no mismatches in the depmgt section, which is the
part of the tool focused on the 2.0.5 upgrade.
There are some other dependency issues you can deal with
separately..there is an explaination in chapter 8: http://www.sonatype.com/book
Sent from my iPhone
On May 28, 2008, at 10:47 AM, "Michael Delaney"
<md...@upromise.com> wrote:
> Brian,
>
> Sure ... please see the text below.
>
> [INFO] Scanning for projects...
> [INFO] Searching repository for plugin with prefix: 'dependency'.
> [INFO]
> ---
> ---------------------------------------------------------------------
> ----
> [INFO] Building Content Administrator APP
> [INFO] task-segment: [dependency:analyze]
> [INFO]
> ---
> ---------------------------------------------------------------------
> ----
> [INFO] Preparing dependency:analyze
> [INFO] artifact org.apache.maven.plugins:maven-clean-plugin: checking
> for updates from <REPO>
> [INFO] artifact org.apache.maven.plugins:maven-clean-plugin: checking
> for updates from maven-repo1
> [INFO] Ignoring available plugin update: 2.2 as it requires Maven
> version 2.0.6
> [INFO] Ignoring available plugin update: 2.4 as it requires Maven
> version 2.0.8
> [INFO] Ignoring available plugin update: 2.3 as it requires Maven
> version 2.0.6
> [WARNING]
> Artifact findbugs:annotations:jar:1.1.0-rc5:provided retains
> local scope 'provided' overriding broader scope 'compile'
> given by a dependency. If this is not intended, modify or
> remove
> the local scope.
>
> [INFO] [dependency:unpack-dependencies {execution: unpack}]
> [INFO] Expanding: <JAR_FILES>
> [INFO] [resources:resources]
> [INFO] Using default encoding to copy filtered resources.
> [INFO] [compiler:compile]
> [INFO] Nothing to compile - all classes are up to date
> [INFO] [resources:testResources]
> [INFO] Using default encoding to copy filtered resources.
> [INFO] [compiler:testCompile]
> [INFO] Nothing to compile - all classes are up to date
> [INFO] [dependency:analyze]
> [INFO] Used declared dependencies:
> [INFO] atg:dss-classes:jar:2006.3:provided
> [INFO] lty:lty-utils:jar:3.0.1.2:compile
> [INFO] atg.publishing:base:jar:2006.3.P2:compile
> [INFO] taglibs:standard:jar:1.1.2:provided
> [INFO] atg:webui-classes:jar:2006.3.P2:compile
> [INFO] junit:junit:jar:4.0:compile
> [INFO] jboss:system:jar:3.2:compile
> [INFO] jboss:common:jar:1.0:compile
> [INFO] atg:das-servlet:jar:2006.3:provided
> [INFO] atg:pubportlet-classes:jar:2006.3.P2:compile
> [INFO] apache:axis:jar:1.4:compile
> [INFO] jboss:jboss-j2ee:jar:4.0.4.GA:provided
> [INFO] atg:dps-classes:jar:2006.3.P2:provided
> [INFO] atg:das-classes:jar:2006.3.P2:provided
> [INFO] atg:bizui-classes:jar:2006.3.P2:compile
> [INFO] jboss:jmx:jar:1.0:compile
> [INFO] Used undeclared dependencies:
> [WARNING] commons-fileupload:commons-fileupload:jar:1.0:provided
> [INFO] Unused declared dependencies:
> [INFO] jakarta-poi:jakarta-poi:jar:1.5.1:compile
> [INFO] commons-discovery:commons-discovery:jar:0.2:compile
> [INFO] oracle:aq:jar:1.0:compile
> [INFO] gnu:regexp:jar:x:compile
> [INFO] oracle:jdbc:jar:10.0:compile
> [INFO] lty:lty-utils-resources:jar:1.0.0.16:compile
> [INFO] jcaptcha:jcaptcha-all:jar:RC2.0.1:compile
> [INFO] velocity:velocity:jar:1.2:compile
> [INFO] castor:castor_xml:jar:0.9.4.3:compile
> [INFO] jboss:deploy:jar:1.0:compile
> [INFO] org.apache:axis:jar:1.4:compile
> [INFO] castor:castor:jar:0.9.4.3:compile
> [INFO] geophile:jdbcwrapper:jar:1.0:compile
> [INFO] aspectwerkz:aspectwerkz:jar:1.1:compile
> [INFO] cactus-support:aspectjrt:jar:1.2.1:compile
> [INFO] lty:capi:jar:1.2.0.27:compile
> [INFO] xalan:xalan:jar:2.7.0:compile
> [INFO] commons-net:commons-net:jar:1.3.0:compile
> [INFO] com:oroinc:jar:1.0:compile
> [INFO] commons-validator:commons-validator:jar:1.1.4:compile
> [INFO] cactus-support:cactus:jar:1.7.2:compile
> [INFO] xerces:xercesImpl:jar:2.8.0:compile
> [WARNING] Potential problems discovered.
> [INFO] Found Resolved Dependency / DependencyManagement mismatches:
> [INFO] Nothing in DepMgt.
> [INFO]
> ---
> ---------------------------------------------------------------------
> [INFO] BUILD SUCCESSFUL
> [INFO]
> ---
> ---------------------------------------------------------------------
> [INFO] Total time: 5 minutes 2 seconds
> [INFO] Finished at: Wed May 28 10:38:46 EDT 2008
> [INFO] Final Memory: 17M/127M
> [INFO]
> ---
> ---------------------------------------------------------------------
>
> C:\work\up-svcs\lty\rel\LTY-R63.0\frontoffice\caApp>
> -----Original Message-----
> From: Brian E. Fox [mailto:brianf@reply.infinity.nu]
> Sent: Tuesday, May 27, 2008 5:57 PM
> To: Maven Users List
> Subject: RE: Upgrading Maven 2.0.5 -> 2.0.9
>
> Can you show the full output of running the command from the CLI?
>
> -----Original Message-----
> From: Michael Delaney [mailto:mdelaney@upromise.com]
> Sent: Tuesday, May 27, 2008 4:41 PM
> To: Maven Users List
> Subject: Upgrading Maven 2.0.5 -> 2.0.9
>
> All,
>
>
>
> I am testing out upgrading from Maven 2.0.5 to 2.0.9, I was reading
> documentation that said that there were some dependency sanity checks
> one should do before upgrading to the latest version of Maven from
> 2.0.6
> or earlier (the page I am referring to is located at
> http://maven.apache.org/plugins/maven-dependency-plugin/examples/prepari
> ng-dependencies.html).
>
>
>
> On the page pasted above, it says to run the Maven dependency analyzer
> to check that everything is okay with how your dependencies are being
> referenced. After building my project, I ran the command as per the
> example but the ouput was a little confusing to me. It said there were
> errors but didn't list what errors were there. So to try to get more
> information, I tried a few things: 1) Added "-Dverbose=true" to the
> command, no additional output; 2) Edited the top-level pom.xml file to
> include the XML element below ... again with no output.
>
>
>
> Could something please help me understand what I am doing wrong?
>
>
>
> [ POM.XML Elements ]
>
> <build>
>
> <plugins>
>
> <plugin>
>
> <artifactId>maven-dependency-plugin</artifactId>
>
> <configuration>
>
> <verbose>true</verbose>
>
> </configuration>
>
> </plugin>
>
> ... ... ...
>
> </plugins>
>
> </build>
>
>
>
>
>
> [ Ouput ]
>
> [INFO] cactus-support:cactus:jar:1.7.2:compile
>
> [INFO] xerces:xercesImpl:jar:2.8.0:compile
>
> [WARNING] Potential problems discovered.
>
> [INFO] Found Resolved Dependency / DependencyManagement mismatches:
>
> [INFO] Nothing in DepMgt.
>
> [INFO]
> ---
> ---------------------------------------------------------------------
>
> [INFO] BUILD SUCCESSFUL
>
> [INFO]
> ---
> ---------------------------------------------------------------------
>
> [INFO] Total time: 19 seconds
>
> [INFO] Finished at: Tue May 27 16:19:35 EDT 2008
>
> [INFO] Final Memory: 17M/127M
>
> [INFO]
> ---
> ---------------------------------------------------------------------
>
>
> ---------------------------------------------------------------------
> 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: Upgrading Maven 2.0.5 -> 2.0.9
Posted by Brian Fox <br...@reply.infinity.nu>.
Yes, the other part is clean
Sent from my iPhone
On May 28, 2008, at 11:22 AM, "Michael Delaney"
<md...@upromise.com> wrote:
> I was basing my findings on the output where Maven stated "Potential
> problems discovered". Is Maven just referring to the "Used undeclared
> dependencies" and "Unused declared dependencies" sections?
>
>
> -----Original Message-----
> From: simon.kitching@chello.at [mailto:simon.kitching@chello.at]
> Sent: Wednesday, May 28, 2008 11:03 AM
> To: Maven Users List
> Subject: Re: Upgrading Maven 2.0.5 -> 2.0.9
>
> I don't see any "errors" here. What "errors" do you mean?
>
> There are a few libs you have a dependency on but don't appear to be
> using. So you could reduce the size of your app by getting rid of
> these
> (as long as you aren't using Class.forName or META-INF/services or
> similar to load them by reflection, which this tool obviously can't
> detect). So you are warned to look into this.
>
> And there is the findbugs:annotations issue, where some dependency
> wants
> that jar bundled with the app, but you (or some other dependency) has
> said that the jar will be "provided" at runtime. If the system into
> which you deploy this code *really* has that already in the classpath,
> then fine. Otherwise you need to fix the declaration that is forcing
> its
> scope to provided. So you are warned to look into this.
>
> Neither is *definitely* a problem, and neither seems to be a *change*
> that upgrading maven will introduce. Instead they appear to be issues
> that your code has always had.
>
> Regards,
> Simon
>
> Michael Delaney schrieb:
> > Brian,
> >
> > Sure ... please see the text below.
> >
> > [INFO] Scanning for projects...
> > [INFO] Searching repository for plugin with prefix: 'dependency'.
> > [INFO]
> >
> ---
> ---------------------------------------------------------------------
> > ----
> > [INFO] Building Content Administrator APP
> > [INFO] task-segment: [dependency:analyze]
> > [INFO]
> >
> ---
> ---------------------------------------------------------------------
> > ----
> > [INFO] Preparing dependency:analyze
> > [INFO] artifact org.apache.maven.plugins:maven-clean-plugin:
> checking
> > for updates from <REPO>
> > [INFO] artifact org.apache.maven.plugins:maven-clean-plugin:
> checking
> > for updates from maven-repo1
> > [INFO] Ignoring available plugin update: 2.2 as it requires Maven
> > version 2.0.6
> > [INFO] Ignoring available plugin update: 2.4 as it requires Maven
> > version 2.0.8
> > [INFO] Ignoring available plugin update: 2.3 as it requires Maven
> > version 2.0.6
> > [WARNING]
> > Artifact findbugs:annotations:jar:1.1.0-rc5:provided retains
> > local scope 'provided' overriding broader scope 'compile'
> > given by a dependency. If this is not intended, modify or
> remove
> > the local scope.
> >
> > [INFO] [dependency:unpack-dependencies {execution: unpack}]
> > [INFO] Expanding: <JAR_FILES>
> > [INFO] [resources:resources]
> > [INFO] Using default encoding to copy filtered resources.
> > [INFO] [compiler:compile]
> > [INFO] Nothing to compile - all classes are up to date
> > [INFO] [resources:testResources]
> > [INFO] Using default encoding to copy filtered resources.
> > [INFO] [compiler:testCompile]
> > [INFO] Nothing to compile - all classes are up to date
> > [INFO] [dependency:analyze]
> > [INFO] Used declared dependencies:
> > [INFO] atg:dss-classes:jar:2006.3:provided
> > [INFO] lty:lty-utils:jar:3.0.1.2:compile
> > [INFO] atg.publishing:base:jar:2006.3.P2:compile
> > [INFO] taglibs:standard:jar:1.1.2:provided
> > [INFO] atg:webui-classes:jar:2006.3.P2:compile
> > [INFO] junit:junit:jar:4.0:compile
> > [INFO] jboss:system:jar:3.2:compile
> > [INFO] jboss:common:jar:1.0:compile
> > [INFO] atg:das-servlet:jar:2006.3:provided
> > [INFO] atg:pubportlet-classes:jar:2006.3.P2:compile
> > [INFO] apache:axis:jar:1.4:compile
> > [INFO] jboss:jboss-j2ee:jar:4.0.4.GA:provided
> > [INFO] atg:dps-classes:jar:2006.3.P2:provided
> > [INFO] atg:das-classes:jar:2006.3.P2:provided
> > [INFO] atg:bizui-classes:jar:2006.3.P2:compile
> > [INFO] jboss:jmx:jar:1.0:compile
> > [INFO] Used undeclared dependencies:
> > [WARNING] commons-fileupload:commons-fileupload:jar:1.0:provided
> > [INFO] Unused declared dependencies:
> > [INFO] jakarta-poi:jakarta-poi:jar:1.5.1:compile
> > [INFO] commons-discovery:commons-discovery:jar:0.2:compile
> > [INFO] oracle:aq:jar:1.0:compile
> > [INFO] gnu:regexp:jar:x:compile
> > [INFO] oracle:jdbc:jar:10.0:compile
> > [INFO] lty:lty-utils-resources:jar:1.0.0.16:compile
> > [INFO] jcaptcha:jcaptcha-all:jar:RC2.0.1:compile
> > [INFO] velocity:velocity:jar:1.2:compile
> > [INFO] castor:castor_xml:jar:0.9.4.3:compile
> > [INFO] jboss:deploy:jar:1.0:compile
> > [INFO] org.apache:axis:jar:1.4:compile
> > [INFO] castor:castor:jar:0.9.4.3:compile
> > [INFO] geophile:jdbcwrapper:jar:1.0:compile
> > [INFO] aspectwerkz:aspectwerkz:jar:1.1:compile
> > [INFO] cactus-support:aspectjrt:jar:1.2.1:compile
> > [INFO] lty:capi:jar:1.2.0.27:compile
> > [INFO] xalan:xalan:jar:2.7.0:compile
> > [INFO] commons-net:commons-net:jar:1.3.0:compile
> > [INFO] com:oroinc:jar:1.0:compile
> > [INFO] commons-validator:commons-validator:jar:1.1.4:compile
> > [INFO] cactus-support:cactus:jar:1.7.2:compile
> > [INFO] xerces:xercesImpl:jar:2.8.0:compile
> > [WARNING] Potential problems discovered.
> > [INFO] Found Resolved Dependency / DependencyManagement mismatches:
> > [INFO] Nothing in DepMgt.
> > [INFO]
> >
> ---
> ---------------------------------------------------------------------
> > [INFO] BUILD SUCCESSFUL
> > [INFO]
> >
> ---
> ---------------------------------------------------------------------
> > [INFO] Total time: 5 minutes 2 seconds
> > [INFO] Finished at: Wed May 28 10:38:46 EDT 2008
> > [INFO] Final Memory: 17M/127M
> > [INFO]
> >
> ---
> ---------------------------------------------------------------------
> >
> > C:\work\up-svcs\lty\rel\LTY-R63.0\frontoffice\caApp>
> > -----Original Message-----
> > From: Brian E. Fox [mailto:brianf@reply.infinity.nu]
> > Sent: Tuesday, May 27, 2008 5:57 PM
> > To: Maven Users List
> > Subject: RE: Upgrading Maven 2.0.5 -> 2.0.9
> >
> > Can you show the full output of running the command from the CLI?
> >
> > -----Original Message-----
> > From: Michael Delaney [mailto:mdelaney@upromise.com]
> > Sent: Tuesday, May 27, 2008 4:41 PM
> > To: Maven Users List
> > Subject: Upgrading Maven 2.0.5 -> 2.0.9
> >
> > All,
> >
> >
> >
> > I am testing out upgrading from Maven 2.0.5 to 2.0.9, I was reading
> > documentation that said that there were some dependency sanity
> checks
> > one should do before upgrading to the latest version of Maven from
> 2.0.6
> > or earlier (the page I am referring to is located at
> >
> http://maven.apache.org/plugins/maven-dependency-plugin/examples/prepari
> > ng-dependencies.html).
> >
> >
> >
> > On the page pasted above, it says to run the Maven dependency
> analyzer
> > to check that everything is okay with how your dependencies are
> being
> > referenced. After building my project, I ran the command as per the
> > example but the ouput was a little confusing to me. It said there
> were
> > errors but didn't list what errors were there. So to try to get more
> > information, I tried a few things: 1) Added "-Dverbose=true" to the
> > command, no additional output; 2) Edited the top-level pom.xml
> file to
> > include the XML element below ... again with no output.
> >
> >
> >
> > Could something please help me understand what I am doing wrong?
> >
> >
> >
> > [ POM.XML Elements ]
> >
> > <build>
> >
> > <plugins>
> >
> > <plugin>
> >
> > <artifactId>maven-dependency-plugin</artifactId>
> >
> > <configuration>
> >
> > <verbose>true</verbose>
> >
> > </configuration>
> >
> > </plugin>
> >
> > ... ... ...
> >
> > </plugins>
> >
> > </build>
> >
> >
> >
> >
> >
> > [ Ouput ]
> >
> > [INFO] cactus-support:cactus:jar:1.7.2:compile
> >
> > [INFO] xerces:xercesImpl:jar:2.8.0:compile
> >
> > [WARNING] Potential problems discovered.
> >
> > [INFO] Found Resolved Dependency / DependencyManagement mismatches:
> >
> > [INFO] Nothing in DepMgt.
> >
> > [INFO]
> >
> ---
> ---------------------------------------------------------------------
> >
> > [INFO] BUILD SUCCESSFUL
> >
> > [INFO]
> >
> ---
> ---------------------------------------------------------------------
> >
> > [INFO] Total time: 19 seconds
> >
> > [INFO] Finished at: Tue May 27 16:19:35 EDT 2008
> >
> > [INFO] Final Memory: 17M/127M
> >
> > [INFO]
> >
> ---
> ---------------------------------------------------------------------
> >
> >
> >
> ---------------------------------------------------------------------
> > 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
> >
> >
> >
>
>
> ---------------------------------------------------------------------
> 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: Upgrading Maven 2.0.5 -> 2.0.9
Posted by Michael Delaney <md...@upromise.com>.
I was basing my findings on the output where Maven stated "Potential
problems discovered". Is Maven just referring to the "Used undeclared
dependencies" and "Unused declared dependencies" sections?
-----Original Message-----
From: simon.kitching@chello.at [mailto:simon.kitching@chello.at]
Sent: Wednesday, May 28, 2008 11:03 AM
To: Maven Users List
Subject: Re: Upgrading Maven 2.0.5 -> 2.0.9
I don't see any "errors" here. What "errors" do you mean?
There are a few libs you have a dependency on but don't appear to be
using. So you could reduce the size of your app by getting rid of these
(as long as you aren't using Class.forName or META-INF/services or
similar to load them by reflection, which this tool obviously can't
detect). So you are warned to look into this.
And there is the findbugs:annotations issue, where some dependency wants
that jar bundled with the app, but you (or some other dependency) has
said that the jar will be "provided" at runtime. If the system into
which you deploy this code *really* has that already in the classpath,
then fine. Otherwise you need to fix the declaration that is forcing its
scope to provided. So you are warned to look into this.
Neither is *definitely* a problem, and neither seems to be a *change*
that upgrading maven will introduce. Instead they appear to be issues
that your code has always had.
Regards,
Simon
Michael Delaney schrieb:
> Brian,
>
> Sure ... please see the text below.
>
> [INFO] Scanning for projects...
> [INFO] Searching repository for plugin with prefix: 'dependency'.
> [INFO]
>
------------------------------------------------------------------------
> ----
> [INFO] Building Content Administrator APP
> [INFO] task-segment: [dependency:analyze]
> [INFO]
>
------------------------------------------------------------------------
> ----
> [INFO] Preparing dependency:analyze
> [INFO] artifact org.apache.maven.plugins:maven-clean-plugin: checking
> for updates from <REPO>
> [INFO] artifact org.apache.maven.plugins:maven-clean-plugin: checking
> for updates from maven-repo1
> [INFO] Ignoring available plugin update: 2.2 as it requires Maven
> version 2.0.6
> [INFO] Ignoring available plugin update: 2.4 as it requires Maven
> version 2.0.8
> [INFO] Ignoring available plugin update: 2.3 as it requires Maven
> version 2.0.6
> [WARNING]
> Artifact findbugs:annotations:jar:1.1.0-rc5:provided retains
> local scope 'provided' overriding broader scope 'compile'
> given by a dependency. If this is not intended, modify or
remove
> the local scope.
>
> [INFO] [dependency:unpack-dependencies {execution: unpack}]
> [INFO] Expanding: <JAR_FILES>
> [INFO] [resources:resources]
> [INFO] Using default encoding to copy filtered resources.
> [INFO] [compiler:compile]
> [INFO] Nothing to compile - all classes are up to date
> [INFO] [resources:testResources]
> [INFO] Using default encoding to copy filtered resources.
> [INFO] [compiler:testCompile]
> [INFO] Nothing to compile - all classes are up to date
> [INFO] [dependency:analyze]
> [INFO] Used declared dependencies:
> [INFO] atg:dss-classes:jar:2006.3:provided
> [INFO] lty:lty-utils:jar:3.0.1.2:compile
> [INFO] atg.publishing:base:jar:2006.3.P2:compile
> [INFO] taglibs:standard:jar:1.1.2:provided
> [INFO] atg:webui-classes:jar:2006.3.P2:compile
> [INFO] junit:junit:jar:4.0:compile
> [INFO] jboss:system:jar:3.2:compile
> [INFO] jboss:common:jar:1.0:compile
> [INFO] atg:das-servlet:jar:2006.3:provided
> [INFO] atg:pubportlet-classes:jar:2006.3.P2:compile
> [INFO] apache:axis:jar:1.4:compile
> [INFO] jboss:jboss-j2ee:jar:4.0.4.GA:provided
> [INFO] atg:dps-classes:jar:2006.3.P2:provided
> [INFO] atg:das-classes:jar:2006.3.P2:provided
> [INFO] atg:bizui-classes:jar:2006.3.P2:compile
> [INFO] jboss:jmx:jar:1.0:compile
> [INFO] Used undeclared dependencies:
> [WARNING] commons-fileupload:commons-fileupload:jar:1.0:provided
> [INFO] Unused declared dependencies:
> [INFO] jakarta-poi:jakarta-poi:jar:1.5.1:compile
> [INFO] commons-discovery:commons-discovery:jar:0.2:compile
> [INFO] oracle:aq:jar:1.0:compile
> [INFO] gnu:regexp:jar:x:compile
> [INFO] oracle:jdbc:jar:10.0:compile
> [INFO] lty:lty-utils-resources:jar:1.0.0.16:compile
> [INFO] jcaptcha:jcaptcha-all:jar:RC2.0.1:compile
> [INFO] velocity:velocity:jar:1.2:compile
> [INFO] castor:castor_xml:jar:0.9.4.3:compile
> [INFO] jboss:deploy:jar:1.0:compile
> [INFO] org.apache:axis:jar:1.4:compile
> [INFO] castor:castor:jar:0.9.4.3:compile
> [INFO] geophile:jdbcwrapper:jar:1.0:compile
> [INFO] aspectwerkz:aspectwerkz:jar:1.1:compile
> [INFO] cactus-support:aspectjrt:jar:1.2.1:compile
> [INFO] lty:capi:jar:1.2.0.27:compile
> [INFO] xalan:xalan:jar:2.7.0:compile
> [INFO] commons-net:commons-net:jar:1.3.0:compile
> [INFO] com:oroinc:jar:1.0:compile
> [INFO] commons-validator:commons-validator:jar:1.1.4:compile
> [INFO] cactus-support:cactus:jar:1.7.2:compile
> [INFO] xerces:xercesImpl:jar:2.8.0:compile
> [WARNING] Potential problems discovered.
> [INFO] Found Resolved Dependency / DependencyManagement mismatches:
> [INFO] Nothing in DepMgt.
> [INFO]
>
------------------------------------------------------------------------
> [INFO] BUILD SUCCESSFUL
> [INFO]
>
------------------------------------------------------------------------
> [INFO] Total time: 5 minutes 2 seconds
> [INFO] Finished at: Wed May 28 10:38:46 EDT 2008
> [INFO] Final Memory: 17M/127M
> [INFO]
>
------------------------------------------------------------------------
>
> C:\work\up-svcs\lty\rel\LTY-R63.0\frontoffice\caApp>
> -----Original Message-----
> From: Brian E. Fox [mailto:brianf@reply.infinity.nu]
> Sent: Tuesday, May 27, 2008 5:57 PM
> To: Maven Users List
> Subject: RE: Upgrading Maven 2.0.5 -> 2.0.9
>
> Can you show the full output of running the command from the CLI?
>
> -----Original Message-----
> From: Michael Delaney [mailto:mdelaney@upromise.com]
> Sent: Tuesday, May 27, 2008 4:41 PM
> To: Maven Users List
> Subject: Upgrading Maven 2.0.5 -> 2.0.9
>
> All,
>
>
>
> I am testing out upgrading from Maven 2.0.5 to 2.0.9, I was reading
> documentation that said that there were some dependency sanity checks
> one should do before upgrading to the latest version of Maven from
2.0.6
> or earlier (the page I am referring to is located at
>
http://maven.apache.org/plugins/maven-dependency-plugin/examples/prepari
> ng-dependencies.html).
>
>
>
> On the page pasted above, it says to run the Maven dependency analyzer
> to check that everything is okay with how your dependencies are being
> referenced. After building my project, I ran the command as per the
> example but the ouput was a little confusing to me. It said there were
> errors but didn't list what errors were there. So to try to get more
> information, I tried a few things: 1) Added "-Dverbose=true" to the
> command, no additional output; 2) Edited the top-level pom.xml file to
> include the XML element below ... again with no output.
>
>
>
> Could something please help me understand what I am doing wrong?
>
>
>
> [ POM.XML Elements ]
>
> <build>
>
> <plugins>
>
> <plugin>
>
> <artifactId>maven-dependency-plugin</artifactId>
>
> <configuration>
>
> <verbose>true</verbose>
>
> </configuration>
>
> </plugin>
>
> ... ... ...
>
> </plugins>
>
> </build>
>
>
>
>
>
> [ Ouput ]
>
> [INFO] cactus-support:cactus:jar:1.7.2:compile
>
> [INFO] xerces:xercesImpl:jar:2.8.0:compile
>
> [WARNING] Potential problems discovered.
>
> [INFO] Found Resolved Dependency / DependencyManagement mismatches:
>
> [INFO] Nothing in DepMgt.
>
> [INFO]
>
------------------------------------------------------------------------
>
> [INFO] BUILD SUCCESSFUL
>
> [INFO]
>
------------------------------------------------------------------------
>
> [INFO] Total time: 19 seconds
>
> [INFO] Finished at: Tue May 27 16:19:35 EDT 2008
>
> [INFO] Final Memory: 17M/127M
>
> [INFO]
>
------------------------------------------------------------------------
>
>
> ---------------------------------------------------------------------
> 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
>
>
>
---------------------------------------------------------------------
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: Upgrading Maven 2.0.5 -> 2.0.9
Posted by "simon.kitching@chello.at" <si...@chello.at>.
I don't see any "errors" here. What "errors" do you mean?
There are a few libs you have a dependency on but don't appear to be
using. So you could reduce the size of your app by getting rid of these
(as long as you aren't using Class.forName or META-INF/services or
similar to load them by reflection, which this tool obviously can't
detect). So you are warned to look into this.
And there is the findbugs:annotations issue, where some dependency wants
that jar bundled with the app, but you (or some other dependency) has
said that the jar will be "provided" at runtime. If the system into
which you deploy this code *really* has that already in the classpath,
then fine. Otherwise you need to fix the declaration that is forcing its
scope to provided. So you are warned to look into this.
Neither is *definitely* a problem, and neither seems to be a *change*
that upgrading maven will introduce. Instead they appear to be issues
that your code has always had.
Regards,
Simon
Michael Delaney schrieb:
> Brian,
>
> Sure ... please see the text below.
>
> [INFO] Scanning for projects...
> [INFO] Searching repository for plugin with prefix: 'dependency'.
> [INFO]
> ------------------------------------------------------------------------
> ----
> [INFO] Building Content Administrator APP
> [INFO] task-segment: [dependency:analyze]
> [INFO]
> ------------------------------------------------------------------------
> ----
> [INFO] Preparing dependency:analyze
> [INFO] artifact org.apache.maven.plugins:maven-clean-plugin: checking
> for updates from <REPO>
> [INFO] artifact org.apache.maven.plugins:maven-clean-plugin: checking
> for updates from maven-repo1
> [INFO] Ignoring available plugin update: 2.2 as it requires Maven
> version 2.0.6
> [INFO] Ignoring available plugin update: 2.4 as it requires Maven
> version 2.0.8
> [INFO] Ignoring available plugin update: 2.3 as it requires Maven
> version 2.0.6
> [WARNING]
> Artifact findbugs:annotations:jar:1.1.0-rc5:provided retains
> local scope 'provided' overriding broader scope 'compile'
> given by a dependency. If this is not intended, modify or remove
> the local scope.
>
> [INFO] [dependency:unpack-dependencies {execution: unpack}]
> [INFO] Expanding: <JAR_FILES>
> [INFO] [resources:resources]
> [INFO] Using default encoding to copy filtered resources.
> [INFO] [compiler:compile]
> [INFO] Nothing to compile - all classes are up to date
> [INFO] [resources:testResources]
> [INFO] Using default encoding to copy filtered resources.
> [INFO] [compiler:testCompile]
> [INFO] Nothing to compile - all classes are up to date
> [INFO] [dependency:analyze]
> [INFO] Used declared dependencies:
> [INFO] atg:dss-classes:jar:2006.3:provided
> [INFO] lty:lty-utils:jar:3.0.1.2:compile
> [INFO] atg.publishing:base:jar:2006.3.P2:compile
> [INFO] taglibs:standard:jar:1.1.2:provided
> [INFO] atg:webui-classes:jar:2006.3.P2:compile
> [INFO] junit:junit:jar:4.0:compile
> [INFO] jboss:system:jar:3.2:compile
> [INFO] jboss:common:jar:1.0:compile
> [INFO] atg:das-servlet:jar:2006.3:provided
> [INFO] atg:pubportlet-classes:jar:2006.3.P2:compile
> [INFO] apache:axis:jar:1.4:compile
> [INFO] jboss:jboss-j2ee:jar:4.0.4.GA:provided
> [INFO] atg:dps-classes:jar:2006.3.P2:provided
> [INFO] atg:das-classes:jar:2006.3.P2:provided
> [INFO] atg:bizui-classes:jar:2006.3.P2:compile
> [INFO] jboss:jmx:jar:1.0:compile
> [INFO] Used undeclared dependencies:
> [WARNING] commons-fileupload:commons-fileupload:jar:1.0:provided
> [INFO] Unused declared dependencies:
> [INFO] jakarta-poi:jakarta-poi:jar:1.5.1:compile
> [INFO] commons-discovery:commons-discovery:jar:0.2:compile
> [INFO] oracle:aq:jar:1.0:compile
> [INFO] gnu:regexp:jar:x:compile
> [INFO] oracle:jdbc:jar:10.0:compile
> [INFO] lty:lty-utils-resources:jar:1.0.0.16:compile
> [INFO] jcaptcha:jcaptcha-all:jar:RC2.0.1:compile
> [INFO] velocity:velocity:jar:1.2:compile
> [INFO] castor:castor_xml:jar:0.9.4.3:compile
> [INFO] jboss:deploy:jar:1.0:compile
> [INFO] org.apache:axis:jar:1.4:compile
> [INFO] castor:castor:jar:0.9.4.3:compile
> [INFO] geophile:jdbcwrapper:jar:1.0:compile
> [INFO] aspectwerkz:aspectwerkz:jar:1.1:compile
> [INFO] cactus-support:aspectjrt:jar:1.2.1:compile
> [INFO] lty:capi:jar:1.2.0.27:compile
> [INFO] xalan:xalan:jar:2.7.0:compile
> [INFO] commons-net:commons-net:jar:1.3.0:compile
> [INFO] com:oroinc:jar:1.0:compile
> [INFO] commons-validator:commons-validator:jar:1.1.4:compile
> [INFO] cactus-support:cactus:jar:1.7.2:compile
> [INFO] xerces:xercesImpl:jar:2.8.0:compile
> [WARNING] Potential problems discovered.
> [INFO] Found Resolved Dependency / DependencyManagement mismatches:
> [INFO] Nothing in DepMgt.
> [INFO]
> ------------------------------------------------------------------------
> [INFO] BUILD SUCCESSFUL
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Total time: 5 minutes 2 seconds
> [INFO] Finished at: Wed May 28 10:38:46 EDT 2008
> [INFO] Final Memory: 17M/127M
> [INFO]
> ------------------------------------------------------------------------
>
> C:\work\up-svcs\lty\rel\LTY-R63.0\frontoffice\caApp>
> -----Original Message-----
> From: Brian E. Fox [mailto:brianf@reply.infinity.nu]
> Sent: Tuesday, May 27, 2008 5:57 PM
> To: Maven Users List
> Subject: RE: Upgrading Maven 2.0.5 -> 2.0.9
>
> Can you show the full output of running the command from the CLI?
>
> -----Original Message-----
> From: Michael Delaney [mailto:mdelaney@upromise.com]
> Sent: Tuesday, May 27, 2008 4:41 PM
> To: Maven Users List
> Subject: Upgrading Maven 2.0.5 -> 2.0.9
>
> All,
>
>
>
> I am testing out upgrading from Maven 2.0.5 to 2.0.9, I was reading
> documentation that said that there were some dependency sanity checks
> one should do before upgrading to the latest version of Maven from 2.0.6
> or earlier (the page I am referring to is located at
> http://maven.apache.org/plugins/maven-dependency-plugin/examples/prepari
> ng-dependencies.html).
>
>
>
> On the page pasted above, it says to run the Maven dependency analyzer
> to check that everything is okay with how your dependencies are being
> referenced. After building my project, I ran the command as per the
> example but the ouput was a little confusing to me. It said there were
> errors but didn't list what errors were there. So to try to get more
> information, I tried a few things: 1) Added "-Dverbose=true" to the
> command, no additional output; 2) Edited the top-level pom.xml file to
> include the XML element below ... again with no output.
>
>
>
> Could something please help me understand what I am doing wrong?
>
>
>
> [ POM.XML Elements ]
>
> <build>
>
> <plugins>
>
> <plugin>
>
> <artifactId>maven-dependency-plugin</artifactId>
>
> <configuration>
>
> <verbose>true</verbose>
>
> </configuration>
>
> </plugin>
>
> ... ... ...
>
> </plugins>
>
> </build>
>
>
>
>
>
> [ Ouput ]
>
> [INFO] cactus-support:cactus:jar:1.7.2:compile
>
> [INFO] xerces:xercesImpl:jar:2.8.0:compile
>
> [WARNING] Potential problems discovered.
>
> [INFO] Found Resolved Dependency / DependencyManagement mismatches:
>
> [INFO] Nothing in DepMgt.
>
> [INFO]
> ------------------------------------------------------------------------
>
> [INFO] BUILD SUCCESSFUL
>
> [INFO]
> ------------------------------------------------------------------------
>
> [INFO] Total time: 19 seconds
>
> [INFO] Finished at: Tue May 27 16:19:35 EDT 2008
>
> [INFO] Final Memory: 17M/127M
>
> [INFO]
> ------------------------------------------------------------------------
>
>
> ---------------------------------------------------------------------
> 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
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
RE: Upgrading Maven 2.0.5 -> 2.0.9
Posted by Michael Delaney <md...@upromise.com>.
Brian,
Sure ... please see the text below.
[INFO] Scanning for projects...
[INFO] Searching repository for plugin with prefix: 'dependency'.
[INFO]
------------------------------------------------------------------------
----
[INFO] Building Content Administrator APP
[INFO] task-segment: [dependency:analyze]
[INFO]
------------------------------------------------------------------------
----
[INFO] Preparing dependency:analyze
[INFO] artifact org.apache.maven.plugins:maven-clean-plugin: checking
for updates from <REPO>
[INFO] artifact org.apache.maven.plugins:maven-clean-plugin: checking
for updates from maven-repo1
[INFO] Ignoring available plugin update: 2.2 as it requires Maven
version 2.0.6
[INFO] Ignoring available plugin update: 2.4 as it requires Maven
version 2.0.8
[INFO] Ignoring available plugin update: 2.3 as it requires Maven
version 2.0.6
[WARNING]
Artifact findbugs:annotations:jar:1.1.0-rc5:provided retains
local scope 'provided' overriding broader scope 'compile'
given by a dependency. If this is not intended, modify or remove
the local scope.
[INFO] [dependency:unpack-dependencies {execution: unpack}]
[INFO] Expanding: <JAR_FILES>
[INFO] [resources:resources]
[INFO] Using default encoding to copy filtered resources.
[INFO] [compiler:compile]
[INFO] Nothing to compile - all classes are up to date
[INFO] [resources:testResources]
[INFO] Using default encoding to copy filtered resources.
[INFO] [compiler:testCompile]
[INFO] Nothing to compile - all classes are up to date
[INFO] [dependency:analyze]
[INFO] Used declared dependencies:
[INFO] atg:dss-classes:jar:2006.3:provided
[INFO] lty:lty-utils:jar:3.0.1.2:compile
[INFO] atg.publishing:base:jar:2006.3.P2:compile
[INFO] taglibs:standard:jar:1.1.2:provided
[INFO] atg:webui-classes:jar:2006.3.P2:compile
[INFO] junit:junit:jar:4.0:compile
[INFO] jboss:system:jar:3.2:compile
[INFO] jboss:common:jar:1.0:compile
[INFO] atg:das-servlet:jar:2006.3:provided
[INFO] atg:pubportlet-classes:jar:2006.3.P2:compile
[INFO] apache:axis:jar:1.4:compile
[INFO] jboss:jboss-j2ee:jar:4.0.4.GA:provided
[INFO] atg:dps-classes:jar:2006.3.P2:provided
[INFO] atg:das-classes:jar:2006.3.P2:provided
[INFO] atg:bizui-classes:jar:2006.3.P2:compile
[INFO] jboss:jmx:jar:1.0:compile
[INFO] Used undeclared dependencies:
[WARNING] commons-fileupload:commons-fileupload:jar:1.0:provided
[INFO] Unused declared dependencies:
[INFO] jakarta-poi:jakarta-poi:jar:1.5.1:compile
[INFO] commons-discovery:commons-discovery:jar:0.2:compile
[INFO] oracle:aq:jar:1.0:compile
[INFO] gnu:regexp:jar:x:compile
[INFO] oracle:jdbc:jar:10.0:compile
[INFO] lty:lty-utils-resources:jar:1.0.0.16:compile
[INFO] jcaptcha:jcaptcha-all:jar:RC2.0.1:compile
[INFO] velocity:velocity:jar:1.2:compile
[INFO] castor:castor_xml:jar:0.9.4.3:compile
[INFO] jboss:deploy:jar:1.0:compile
[INFO] org.apache:axis:jar:1.4:compile
[INFO] castor:castor:jar:0.9.4.3:compile
[INFO] geophile:jdbcwrapper:jar:1.0:compile
[INFO] aspectwerkz:aspectwerkz:jar:1.1:compile
[INFO] cactus-support:aspectjrt:jar:1.2.1:compile
[INFO] lty:capi:jar:1.2.0.27:compile
[INFO] xalan:xalan:jar:2.7.0:compile
[INFO] commons-net:commons-net:jar:1.3.0:compile
[INFO] com:oroinc:jar:1.0:compile
[INFO] commons-validator:commons-validator:jar:1.1.4:compile
[INFO] cactus-support:cactus:jar:1.7.2:compile
[INFO] xerces:xercesImpl:jar:2.8.0:compile
[WARNING] Potential problems discovered.
[INFO] Found Resolved Dependency / DependencyManagement mismatches:
[INFO] Nothing in DepMgt.
[INFO]
------------------------------------------------------------------------
[INFO] BUILD SUCCESSFUL
[INFO]
------------------------------------------------------------------------
[INFO] Total time: 5 minutes 2 seconds
[INFO] Finished at: Wed May 28 10:38:46 EDT 2008
[INFO] Final Memory: 17M/127M
[INFO]
------------------------------------------------------------------------
C:\work\up-svcs\lty\rel\LTY-R63.0\frontoffice\caApp>
-----Original Message-----
From: Brian E. Fox [mailto:brianf@reply.infinity.nu]
Sent: Tuesday, May 27, 2008 5:57 PM
To: Maven Users List
Subject: RE: Upgrading Maven 2.0.5 -> 2.0.9
Can you show the full output of running the command from the CLI?
-----Original Message-----
From: Michael Delaney [mailto:mdelaney@upromise.com]
Sent: Tuesday, May 27, 2008 4:41 PM
To: Maven Users List
Subject: Upgrading Maven 2.0.5 -> 2.0.9
All,
I am testing out upgrading from Maven 2.0.5 to 2.0.9, I was reading
documentation that said that there were some dependency sanity checks
one should do before upgrading to the latest version of Maven from 2.0.6
or earlier (the page I am referring to is located at
http://maven.apache.org/plugins/maven-dependency-plugin/examples/prepari
ng-dependencies.html).
On the page pasted above, it says to run the Maven dependency analyzer
to check that everything is okay with how your dependencies are being
referenced. After building my project, I ran the command as per the
example but the ouput was a little confusing to me. It said there were
errors but didn't list what errors were there. So to try to get more
information, I tried a few things: 1) Added "-Dverbose=true" to the
command, no additional output; 2) Edited the top-level pom.xml file to
include the XML element below ... again with no output.
Could something please help me understand what I am doing wrong?
[ POM.XML Elements ]
<build>
<plugins>
<plugin>
<artifactId>maven-dependency-plugin</artifactId>
<configuration>
<verbose>true</verbose>
</configuration>
</plugin>
... ... ...
</plugins>
</build>
[ Ouput ]
[INFO] cactus-support:cactus:jar:1.7.2:compile
[INFO] xerces:xercesImpl:jar:2.8.0:compile
[WARNING] Potential problems discovered.
[INFO] Found Resolved Dependency / DependencyManagement mismatches:
[INFO] Nothing in DepMgt.
[INFO]
------------------------------------------------------------------------
[INFO] BUILD SUCCESSFUL
[INFO]
------------------------------------------------------------------------
[INFO] Total time: 19 seconds
[INFO] Finished at: Tue May 27 16:19:35 EDT 2008
[INFO] Final Memory: 17M/127M
[INFO]
------------------------------------------------------------------------
---------------------------------------------------------------------
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: Upgrading Maven 2.0.5 -> 2.0.9
Posted by "Brian E. Fox" <br...@reply.infinity.nu>.
Can you show the full output of running the command from the CLI?
-----Original Message-----
From: Michael Delaney [mailto:mdelaney@upromise.com]
Sent: Tuesday, May 27, 2008 4:41 PM
To: Maven Users List
Subject: Upgrading Maven 2.0.5 -> 2.0.9
All,
I am testing out upgrading from Maven 2.0.5 to 2.0.9, I was reading
documentation that said that there were some dependency sanity checks
one should do before upgrading to the latest version of Maven from 2.0.6
or earlier (the page I am referring to is located at
http://maven.apache.org/plugins/maven-dependency-plugin/examples/prepari
ng-dependencies.html).
On the page pasted above, it says to run the Maven dependency analyzer
to check that everything is okay with how your dependencies are being
referenced. After building my project, I ran the command as per the
example but the ouput was a little confusing to me. It said there were
errors but didn't list what errors were there. So to try to get more
information, I tried a few things: 1) Added "-Dverbose=true" to the
command, no additional output; 2) Edited the top-level pom.xml file to
include the XML element below ... again with no output.
Could something please help me understand what I am doing wrong?
[ POM.XML Elements ]
<build>
<plugins>
<plugin>
<artifactId>maven-dependency-plugin</artifactId>
<configuration>
<verbose>true</verbose>
</configuration>
</plugin>
... ... ...
</plugins>
</build>
[ Ouput ]
[INFO] cactus-support:cactus:jar:1.7.2:compile
[INFO] xerces:xercesImpl:jar:2.8.0:compile
[WARNING] Potential problems discovered.
[INFO] Found Resolved Dependency / DependencyManagement mismatches:
[INFO] Nothing in DepMgt.
[INFO]
------------------------------------------------------------------------
[INFO] BUILD SUCCESSFUL
[INFO]
------------------------------------------------------------------------
[INFO] Total time: 19 seconds
[INFO] Finished at: Tue May 27 16:19:35 EDT 2008
[INFO] Final Memory: 17M/127M
[INFO]
------------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org