Thanks Ricky. Yep I think I need to add in the pushpull special repo (the nasty
Iplanet one) to solve this.

Cheers,
Chris

On Dec 1, 2011, at 2:36 PM, Nguyen, Ricky wrote:

> Also, cas-protocol-ftp can't resolve "org.globus:cog-jglobus:jar:1.8.0"
> 
> 
> [INFO] 
> ------------------------------------------------------------------------
> [INFO] Building Common Utilities 0.4-SNAPSHOT
> [INFO] 
> ------------------------------------------------------------------------
> [INFO]
> [INFO] --- maven-dependency-plugin:2.1:tree (default-cli) @ oodt-commons ---
> [INFO] org.apache.oodt:oodt-commons:jar:0.4-SNAPSHOT
> [INFO] +- commons-dbcp:commons-dbcp:jar:1.2.1:compile
> [INFO] |  \- xml-apis:xml-apis:jar:1.0.b2:compile
> [INFO] +- commons-collections:commons-collections:jar:2.1:compile
> [INFO] +- commons-pool:commons-pool:jar:1.2:compile
> [INFO] +- commons-lang:commons-lang:jar:2.3:compile
> [INFO] +- commons-logging:commons-logging:jar:1.0.3:compile
> [INFO] +- org.springframework:spring-core:jar:2.5.4:compile
> [INFO] +- org.springframework:spring-hibernate3:jar:2.0.8:compile
> [INFO] |  +- aopalliance:aopalliance:jar:1.0:compile
> [INFO] |  +- org.hibernate:hibernate:jar:3.2.5.ga:compile
> [INFO] |  |  +- net.sf.ehcache:ehcache:jar:1.2.3:compile
> [INFO] |  |  +- javax.transaction:jta:jar:1.0.1B:compile
> [INFO] |  |  +- asm:asm-attrs:jar:1.5.3:compile
> [INFO] |  |  +- dom4j:dom4j:jar:1.6.1:compile
> [INFO] |  |  +- antlr:antlr:jar:2.7.6:compile
> [INFO] |  |  +- cglib:cglib:jar:2.1_3:compile
> [INFO] |  |  \- asm:asm:jar:1.5.3:compile
> [INFO] |  +- org.springframework:spring-beans:jar:2.0.8:compile
> [INFO] |  +- org.springframework:spring-context:jar:2.0.8:compile
> [INFO] |  +- org.springframework:spring-dao:jar:2.0.8:compile
> [INFO] |  \- org.springframework:spring-jdbc:jar:2.0.8:compile
> [INFO] +- xmlrpc:xmlrpc:jar:2.0.1:compile
> [INFO] +- junit:junit:jar:3.8.2:compile
> [INFO] \- xerces:xercesImpl:jar:2.9.1:compile
> [INFO] 
> ------------------------------------------------------------------------
> [INFO] BUILD SUCCESS
> [INFO] 
> ------------------------------------------------------------------------
> [INFO] Total time: 1.869s
> [INFO] Finished at: Thu Dec 01 14:02:41 PST 2011
> [INFO] Final Memory: 8M/81M
> [INFO] 
> ------------------------------------------------------------------------
> 
> On Dec 1, 2011, at 1:51 PM, Mattmann, Chris A (388J) wrote:
> 
> Hey Ricky,
> 
> Interesting.
> 
> Should we process the jar dependency on jta as an exclusion? I updated the
> super pom a week or so ago while working on OODT-157, removing any dependency
> on non-Central repositories (Maven Central is phasing out external repo
> deps, see here [1]).
> 
> I don't think any of our stuff requires jta, so maybe we can just exclude it. 
> Can you
> do a mvn dependency:tree to isolate where the dep is coming from?
> 
> Cheers,
> Chris
> 
> [1] 
> http://www.sonatype.com/people/2010/03/why-external-repos-are-being-phased-out-of-central/
> On Dec 1, 2011, at 12:45 PM, Nguyen, Ricky wrote:
> 
> Hi all,
> 
> I'm getting this error with a fresh checkout of oodt/trunk:
> 
> [ERROR] Failed to execute goal on project oodt-commons: Could not resolve 
> dependencies for project org.apache.oodt:oodt-commons:jar:0.4-SNAPSHOT: Could 
> not find artifact javax.transaction:jta:jar:1.0.1B in central 
> (http://repo1.maven.org/maven2) -> [Help 1]
> 
> Googled it. Jta is needed by the following dependencies:
> spring-hibernate3 2.0.8 -> org.hibernate 3.2.5ga -> jta 1.0.1B
> 
> Here is the workaround:
> http://maven.apache.org/guides/mini/guide-coping-with-sun-jars.html
> 
> I've attached a patch to include the java.net<http://java.net> maven2 repo 
> into the oodt super pom. I'm not sure if this patch is needed, since the 
> jenkins build seems to be unaffected. It is strange that my local build 
> worked previously, but only today I ran into this problem. Any ideas what 
> happened?
> 
> -Ricky
> 
> 
> 
> 
> ---------------------------------------------------------------------
> CONFIDENTIALITY NOTICE: This e-mail message, including any attachments,
> is for the sole use of the intended recipient(s) and may contain confidential
> or legally privileged information. Any unauthorized review, use, disclosure
> or distribution is prohibited. If you are not the intended recipient, please
> contact the sender by reply e-mail and destroy all copies of this original 
> message.
> 
> ---------------------------------------------------------------------
> 
> 
> 
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> Chris Mattmann, Ph.D.
> Senior Computer Scientist
> NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
> Office: 171-266B, Mailstop: 171-246
> Email: [email protected]<mailto:[email protected]>
> WWW:   http://sunset.usc.edu/~mattmann/
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> Adjunct Assistant Professor, Computer Science Department
> University of Southern California, Los Angeles, CA 90089 USA
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> 
> 
> 
> 
> ---------------------------------------------------------------------
> CONFIDENTIALITY NOTICE: This e-mail message, including any attachments, 
> is for the sole use of the intended recipient(s) and may contain confidential
> or legally privileged information. Any unauthorized review, use, disclosure
> or distribution is prohibited. If you are not the intended recipient, please
> contact the sender by reply e-mail and destroy all copies of this original 
> message.  
> 
> ---------------------------------------------------------------------
> 


++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Chris Mattmann, Ph.D.
Senior Computer Scientist
NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
Office: 171-266B, Mailstop: 171-246
Email: [email protected]
WWW:   http://sunset.usc.edu/~mattmann/
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Adjunct Assistant Professor, Computer Science Department
University of Southern California, Los Angeles, CA 90089 USA
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Reply via email to