2010/1/28 Anders Hammar <[email protected]> > Here you go: > > http://repo1.maven.org/maven2/org/apache/rampart/rampart-project/1.4/rampart-project-1.4.pom > > I didn't look closely enough. The JDK1.4 profile is active by default, do > as > you're NOT using JDK 1.5 that profile is not going to kick in. > Oh, my fault, I did not check it clearly enouth. You mean not matter which jdk I use( configed in the compile version?), as long as the version is not 1.5(for my case , it is 1.6), the jdk14 profile will be actived?
> > /Anders > > On Thu, Jan 28, 2010 at 09:30, maven apache <[email protected]> > wrote: > > > 2010/1/28 Anders Hammar <[email protected]> > > > > > You're building with JDK 1.4, not JDK 1.5. > > > > How? I did not sepcify 1.4 or .1.5. > > In the parent pom of my project I config the compile version to 1.6, and > my > > eclipse are using jdk1.6_18 > > > > > > > There are profiles in the pom of > > > > > > org.apache.rampart:rampart-policy:jar:1.4 > > > > > > (Actually, the profiles are in the parent of that project). > > > > > Yes, I know this, I have check the pom. > > > > > > > > The homepage which you refer to isn't telling the complete truth... > > > > > > /Anders > > > On Thu, Jan 28, 2010 at 09:15, maven apache <[email protected]> > > > wrote: > > > > > > > Hi: > > > > I found a strange problem, it seems that maven may download a wrong > > > version > > > > for a transitive dependency. > > > > Details can be found here : > > > > http://dpaste.com/151511/ > > > > > > > > > >
