Re: Essential Dependencies Only
I am swimming around in Maven this morning and I am bouncing around like a steel ball in a pinball machine! We use a homegrown tool with all the warts and bumps. I am trying to run mvn dependency:tree over struts2-core-2.1.8.pom to see if the analysis might help me with the forest/tree problem. When I run it I am getting the following trace. A Google search revealed some dependency changes in Maven and requested I delete my local repo from my ../.m2 which I did. The problem is the same. Here is the output from mvn -v. Another potential clue is the 'cmd' is not recognized as an internal or external command, message I get often. Do you have any suggestions? C:\maven\scott\struts2-core>mvn -v Apache Maven 2.2.1 (r801777; 2009-08-06 14:16:01-0500) Java version: 1.6.0_12 Java home: C:\Program Files\Java\jdk1.6.0_12\jre Default locale: en_US, platform encoding: Cp1252 OS name: "windows xp" version: "5.1" arch: "x86" Family: "windows" 'cmd' is not recognized as an internal or external command, operable program or batch file. C:\maven\scott\struts2-core> - C:\maven\scott\struts2-core>mvn dependency:tree -e + Error stacktraces are turned on. [INFO] Scanning for projects... [INFO] [ERROR] BUILD FAILURE [INFO] [INFO] Required goal not found: dependency:tree in org.apache.maven.plugins:maven-dependency-plugin:2.0-alpha-4 [INFO] [INFO] Trace org.apache.maven.BuildFailureException: Required goal not found: dependency:tree in org.apache.maven.plugins:maven-dependency-plugin:2.0-alpha-4 at org.apache.maven.lifecycle.DefaultLifecycleExecutor.getMojoDescriptor(DefaultLifecycleExecutor.java:1867) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.segmentTaskListByAggregationNeeds(DefaultLifecycleExecutor.java:462) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:175) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138) at org.apache.maven.cli.MavenCli.main(MavenCli.java:362) at org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60) 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:597) 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) [INFO] [INFO] Total time: < 1 second [INFO] Finished at: Wed Dec 16 10:14:47 CST 2009 [INFO] Final Memory: 4M/9M [INFO] 'cmd' is not recognized as an internal or external command, operable program or batch file. C:\maven\scott\struts2-core>mvn dependency:tree Musachy Barroso wrote: > > yeah I know, so do we ;), right now grep is all I got > > On Tue, Dec 15, 2009 at 10:09 AM, wrote: >> Thanks brother. Actually it's not our projects we analyze; it's the open >> source projects. We *do not* simply download/dump the OS project and >> begin >> to use it. We factor each project into as many constituent OS projects >> as >> it made from and then recursively walk down the tree doing this at each >> node. It is a big PITA! >> >> On Tue, Dec 15, 2009 at 12:03 PM, Musachy Barroso >> wrote: >> >>> mvn dependency:tree will give you all the dependencies nicely. I also >>> have to help with this task in my company, and we haven't found any >>> decent tool that does what you described. If all your projects use >>> maven, then there is probably a plugin for that, but that's not the >>> case for us. >>> >>> On Tue, Dec 15, 2009 at 9:58 AM, wrote: >>> > Thanks Wes -- >>> > >>> > Have you or others discovered any software that could be used to >>> "decompose" >>> > an open source product into its constituent parts and then further >>> decompose >>> > each of those in turn. Looking at a single POM rarely answers the >>> "real" >>> > questions. The dependency/version graph is wicked to deal with by >>> hand >>> and >>> > the licenses therein complicate matters even further. I struggle when >>> > thinking how many shops are each doing this over-and-over with each >>> new >>> > version release and it seems like a missing piece of the FOSS/le
Re: Essential Dependencies Only
yeah I know, so do we ;), right now grep is all I got On Tue, Dec 15, 2009 at 10:09 AM, wrote: > Thanks brother. Actually it's not our projects we analyze; it's the open > source projects. We *do not* simply download/dump the OS project and begin > to use it. We factor each project into as many constituent OS projects as > it made from and then recursively walk down the tree doing this at each > node. It is a big PITA! > > On Tue, Dec 15, 2009 at 12:03 PM, Musachy Barroso wrote: > >> mvn dependency:tree will give you all the dependencies nicely. I also >> have to help with this task in my company, and we haven't found any >> decent tool that does what you described. If all your projects use >> maven, then there is probably a plugin for that, but that's not the >> case for us. >> >> On Tue, Dec 15, 2009 at 9:58 AM, wrote: >> > Thanks Wes -- >> > >> > Have you or others discovered any software that could be used to >> "decompose" >> > an open source product into its constituent parts and then further >> decompose >> > each of those in turn. Looking at a single POM rarely answers the "real" >> > questions. The dependency/version graph is wicked to deal with by hand >> and >> > the licenses therein complicate matters even further. I struggle when >> > thinking how many shops are each doing this over-and-over with each new >> > version release and it seems like a missing piece of the FOSS/legal >> puzzle. >> > >> > Peace, >> > Scott >> > >> > >> > On Mon, Dec 14, 2009 at 10:44 AM, Wes Wannemacher >> wrote: >> > >> >> Scott, take a look at the mailreader and blank apps. You can also read >> >> through the struts2-core pom (annotated and easier to read here - >> >> >> >> >> http://jarvana.com/jarvana/inspect-pom/org/apache/struts/struts2-core/2.1.8/struts2-core-2.1.8.pom >> >> , >> >> that points to 2.1.8, they haven't indexed 2.1.8.1 yet, but there is >> >> no differences in dependencies). >> >> >> >> If you just want to cut to the chase, the "essentials" would be - >> >> >> >> struts2-core 2.1.8.1 >> >> xwork-core 2.1.6 >> >> freemarker 2.3.15 >> >> ognl 2.7.3 >> >> >> >> -Wes >> >> >> >> On Mon, Dec 14, 2009 at 10:36 AM, stanlick wrote: >> >> > >> >> > Greetings and Happy Holidays -- >> >> > >> >> > I am sitting down to unwind the Essential Dependencies Only jar >> >> > (struts-2.1.8.1-lib.zip) in preparation for the litany of questions >> the >> >> > lawyers are going to ask before accepting the Struts 2.1.8.1 upgrade >> in >> >> > house. Now either I have a different understanding of the word >> >> essential, >> >> > or this version of our new Struts has really spread her arms. There >> are >> >> > seventy-one jars in the lib folder of the *essential dependencies only >> >> jar* >> >> > and a quick glance suggests they are *not* all essential. So does >> >> essential >> >> > != core or required? Is there a resource where an analysis can be >> made >> >> to >> >> > determine compile, testing, run-time dependencies? Untangling this >> ball >> >> of >> >> > yarn by hand is going to burn up hours and lead an analyst down many >> >> rabbit >> >> > holes. Is there a POM that could save the man hours? >> >> > >> >> > Peace, >> >> > Scott >> >> > -- >> >> > View this message in context: >> >> >> http://old.nabble.com/Essential-Dependencies-Only-tp26779724p26779724.html >> >> > Sent from the Struts - User mailing list archive at Nabble.com. >> >> > >> >> > >> >> > - >> >> > To unsubscribe, e-mail: user-unsubscr...@struts.apache.org >> >> > For additional commands, e-mail: user-h...@struts.apache.org >> >> > >> >> > >> >> >> >> >> >> >> >> -- >> >> Wes Wannemacher >> >> >> >> Head Engineer, WanTii, Inc. >> >> Need Training? Struts, Spring, Maven, Tomcat... >> >> Ask me for a quote! >> >> >> >> - >> >> To unsubscribe, e-mail: user-unsubscr...@struts.apache.org >> >> For additional commands, e-mail: user-h...@struts.apache.org >> >> >> >> >> > >> >> - >> To unsubscribe, e-mail: user-unsubscr...@struts.apache.org >> For additional commands, e-mail: user-h...@struts.apache.org >> >> > - To unsubscribe, e-mail: user-unsubscr...@struts.apache.org For additional commands, e-mail: user-h...@struts.apache.org
Re: Essential Dependencies Only
Thanks brother. Actually it's not our projects we analyze; it's the open source projects. We *do not* simply download/dump the OS project and begin to use it. We factor each project into as many constituent OS projects as it made from and then recursively walk down the tree doing this at each node. It is a big PITA! On Tue, Dec 15, 2009 at 12:03 PM, Musachy Barroso wrote: > mvn dependency:tree will give you all the dependencies nicely. I also > have to help with this task in my company, and we haven't found any > decent tool that does what you described. If all your projects use > maven, then there is probably a plugin for that, but that's not the > case for us. > > On Tue, Dec 15, 2009 at 9:58 AM, wrote: > > Thanks Wes -- > > > > Have you or others discovered any software that could be used to > "decompose" > > an open source product into its constituent parts and then further > decompose > > each of those in turn. Looking at a single POM rarely answers the "real" > > questions. The dependency/version graph is wicked to deal with by hand > and > > the licenses therein complicate matters even further. I struggle when > > thinking how many shops are each doing this over-and-over with each new > > version release and it seems like a missing piece of the FOSS/legal > puzzle. > > > > Peace, > > Scott > > > > > > On Mon, Dec 14, 2009 at 10:44 AM, Wes Wannemacher > wrote: > > > >> Scott, take a look at the mailreader and blank apps. You can also read > >> through the struts2-core pom (annotated and easier to read here - > >> > >> > http://jarvana.com/jarvana/inspect-pom/org/apache/struts/struts2-core/2.1.8/struts2-core-2.1.8.pom > >> , > >> that points to 2.1.8, they haven't indexed 2.1.8.1 yet, but there is > >> no differences in dependencies). > >> > >> If you just want to cut to the chase, the "essentials" would be - > >> > >> struts2-core 2.1.8.1 > >> xwork-core 2.1.6 > >> freemarker 2.3.15 > >> ognl 2.7.3 > >> > >> -Wes > >> > >> On Mon, Dec 14, 2009 at 10:36 AM, stanlick wrote: > >> > > >> > Greetings and Happy Holidays -- > >> > > >> > I am sitting down to unwind the Essential Dependencies Only jar > >> > (struts-2.1.8.1-lib.zip) in preparation for the litany of questions > the > >> > lawyers are going to ask before accepting the Struts 2.1.8.1 upgrade > in > >> > house. Now either I have a different understanding of the word > >> essential, > >> > or this version of our new Struts has really spread her arms. There > are > >> > seventy-one jars in the lib folder of the *essential dependencies only > >> jar* > >> > and a quick glance suggests they are *not* all essential. So does > >> essential > >> > != core or required? Is there a resource where an analysis can be > made > >> to > >> > determine compile, testing, run-time dependencies? Untangling this > ball > >> of > >> > yarn by hand is going to burn up hours and lead an analyst down many > >> rabbit > >> > holes. Is there a POM that could save the man hours? > >> > > >> > Peace, > >> > Scott > >> > -- > >> > View this message in context: > >> > http://old.nabble.com/Essential-Dependencies-Only-tp26779724p26779724.html > >> > Sent from the Struts - User mailing list archive at Nabble.com. > >> > > >> > > >> > - > >> > To unsubscribe, e-mail: user-unsubscr...@struts.apache.org > >> > For additional commands, e-mail: user-h...@struts.apache.org > >> > > >> > > >> > >> > >> > >> -- > >> Wes Wannemacher > >> > >> Head Engineer, WanTii, Inc. > >> Need Training? Struts, Spring, Maven, Tomcat... > >> Ask me for a quote! > >> > >> - > >> To unsubscribe, e-mail: user-unsubscr...@struts.apache.org > >> For additional commands, e-mail: user-h...@struts.apache.org > >> > >> > > > > - > To unsubscribe, e-mail: user-unsubscr...@struts.apache.org > For additional commands, e-mail: user-h...@struts.apache.org > >
Re: Essential Dependencies Only
mvn dependency:tree will give you all the dependencies nicely. I also have to help with this task in my company, and we haven't found any decent tool that does what you described. If all your projects use maven, then there is probably a plugin for that, but that's not the case for us. On Tue, Dec 15, 2009 at 9:58 AM, wrote: > Thanks Wes -- > > Have you or others discovered any software that could be used to "decompose" > an open source product into its constituent parts and then further decompose > each of those in turn. Looking at a single POM rarely answers the "real" > questions. The dependency/version graph is wicked to deal with by hand and > the licenses therein complicate matters even further. I struggle when > thinking how many shops are each doing this over-and-over with each new > version release and it seems like a missing piece of the FOSS/legal puzzle. > > Peace, > Scott > > > On Mon, Dec 14, 2009 at 10:44 AM, Wes Wannemacher wrote: > >> Scott, take a look at the mailreader and blank apps. You can also read >> through the struts2-core pom (annotated and easier to read here - >> >> http://jarvana.com/jarvana/inspect-pom/org/apache/struts/struts2-core/2.1.8/struts2-core-2.1.8.pom >> , >> that points to 2.1.8, they haven't indexed 2.1.8.1 yet, but there is >> no differences in dependencies). >> >> If you just want to cut to the chase, the "essentials" would be - >> >> struts2-core 2.1.8.1 >> xwork-core 2.1.6 >> freemarker 2.3.15 >> ognl 2.7.3 >> >> -Wes >> >> On Mon, Dec 14, 2009 at 10:36 AM, stanlick wrote: >> > >> > Greetings and Happy Holidays -- >> > >> > I am sitting down to unwind the Essential Dependencies Only jar >> > (struts-2.1.8.1-lib.zip) in preparation for the litany of questions the >> > lawyers are going to ask before accepting the Struts 2.1.8.1 upgrade in >> > house. Now either I have a different understanding of the word >> essential, >> > or this version of our new Struts has really spread her arms. There are >> > seventy-one jars in the lib folder of the *essential dependencies only >> jar* >> > and a quick glance suggests they are *not* all essential. So does >> essential >> > != core or required? Is there a resource where an analysis can be made >> to >> > determine compile, testing, run-time dependencies? Untangling this ball >> of >> > yarn by hand is going to burn up hours and lead an analyst down many >> rabbit >> > holes. Is there a POM that could save the man hours? >> > >> > Peace, >> > Scott >> > -- >> > View this message in context: >> http://old.nabble.com/Essential-Dependencies-Only-tp26779724p26779724.html >> > Sent from the Struts - User mailing list archive at Nabble.com. >> > >> > >> > - >> > To unsubscribe, e-mail: user-unsubscr...@struts.apache.org >> > For additional commands, e-mail: user-h...@struts.apache.org >> > >> > >> >> >> >> -- >> Wes Wannemacher >> >> Head Engineer, WanTii, Inc. >> Need Training? Struts, Spring, Maven, Tomcat... >> Ask me for a quote! >> >> - >> To unsubscribe, e-mail: user-unsubscr...@struts.apache.org >> For additional commands, e-mail: user-h...@struts.apache.org >> >> > - To unsubscribe, e-mail: user-unsubscr...@struts.apache.org For additional commands, e-mail: user-h...@struts.apache.org
Re: Essential Dependencies Only
Thanks Wes -- Have you or others discovered any software that could be used to "decompose" an open source product into its constituent parts and then further decompose each of those in turn. Looking at a single POM rarely answers the "real" questions. The dependency/version graph is wicked to deal with by hand and the licenses therein complicate matters even further. I struggle when thinking how many shops are each doing this over-and-over with each new version release and it seems like a missing piece of the FOSS/legal puzzle. Peace, Scott On Mon, Dec 14, 2009 at 10:44 AM, Wes Wannemacher wrote: > Scott, take a look at the mailreader and blank apps. You can also read > through the struts2-core pom (annotated and easier to read here - > > http://jarvana.com/jarvana/inspect-pom/org/apache/struts/struts2-core/2.1.8/struts2-core-2.1.8.pom > , > that points to 2.1.8, they haven't indexed 2.1.8.1 yet, but there is > no differences in dependencies). > > If you just want to cut to the chase, the "essentials" would be - > > struts2-core 2.1.8.1 > xwork-core 2.1.6 > freemarker 2.3.15 > ognl 2.7.3 > > -Wes > > On Mon, Dec 14, 2009 at 10:36 AM, stanlick wrote: > > > > Greetings and Happy Holidays -- > > > > I am sitting down to unwind the Essential Dependencies Only jar > > (struts-2.1.8.1-lib.zip) in preparation for the litany of questions the > > lawyers are going to ask before accepting the Struts 2.1.8.1 upgrade in > > house. Now either I have a different understanding of the word > essential, > > or this version of our new Struts has really spread her arms. There are > > seventy-one jars in the lib folder of the *essential dependencies only > jar* > > and a quick glance suggests they are *not* all essential. So does > essential > > != core or required? Is there a resource where an analysis can be made > to > > determine compile, testing, run-time dependencies? Untangling this ball > of > > yarn by hand is going to burn up hours and lead an analyst down many > rabbit > > holes. Is there a POM that could save the man hours? > > > > Peace, > > Scott > > -- > > View this message in context: > http://old.nabble.com/Essential-Dependencies-Only-tp26779724p26779724.html > > Sent from the Struts - User mailing list archive at Nabble.com. > > > > > > - > > To unsubscribe, e-mail: user-unsubscr...@struts.apache.org > > For additional commands, e-mail: user-h...@struts.apache.org > > > > > > > > -- > Wes Wannemacher > > Head Engineer, WanTii, Inc. > Need Training? Struts, Spring, Maven, Tomcat... > Ask me for a quote! > > - > To unsubscribe, e-mail: user-unsubscr...@struts.apache.org > For additional commands, e-mail: user-h...@struts.apache.org > >
Re: Essential Dependencies Only
Scott, take a look at the mailreader and blank apps. You can also read through the struts2-core pom (annotated and easier to read here - http://jarvana.com/jarvana/inspect-pom/org/apache/struts/struts2-core/2.1.8/struts2-core-2.1.8.pom, that points to 2.1.8, they haven't indexed 2.1.8.1 yet, but there is no differences in dependencies). If you just want to cut to the chase, the "essentials" would be - struts2-core 2.1.8.1 xwork-core 2.1.6 freemarker 2.3.15 ognl 2.7.3 -Wes On Mon, Dec 14, 2009 at 10:36 AM, stanlick wrote: > > Greetings and Happy Holidays -- > > I am sitting down to unwind the Essential Dependencies Only jar > (struts-2.1.8.1-lib.zip) in preparation for the litany of questions the > lawyers are going to ask before accepting the Struts 2.1.8.1 upgrade in > house. Now either I have a different understanding of the word essential, > or this version of our new Struts has really spread her arms. There are > seventy-one jars in the lib folder of the *essential dependencies only jar* > and a quick glance suggests they are *not* all essential. So does essential > != core or required? Is there a resource where an analysis can be made to > determine compile, testing, run-time dependencies? Untangling this ball of > yarn by hand is going to burn up hours and lead an analyst down many rabbit > holes. Is there a POM that could save the man hours? > > Peace, > Scott > -- > View this message in context: > http://old.nabble.com/Essential-Dependencies-Only-tp26779724p26779724.html > Sent from the Struts - User mailing list archive at Nabble.com. > > > - > To unsubscribe, e-mail: user-unsubscr...@struts.apache.org > For additional commands, e-mail: user-h...@struts.apache.org > > -- Wes Wannemacher Head Engineer, WanTii, Inc. Need Training? Struts, Spring, Maven, Tomcat... Ask me for a quote! - To unsubscribe, e-mail: user-unsubscr...@struts.apache.org For additional commands, e-mail: user-h...@struts.apache.org
