Re: POM problems in trunk?
Ahh, your right. I'm doing this within eclipse and for some reason was just assuming I was getting all of trunk. But I think I'm just updating all the projects, not updating the root. Now that you mention it, I'm sure it will work. Thanks! On 10/30/07, Martijn Dashorst <[EMAIL PROTECTED]> wrote: > Do a install from the root > > your parent pom is not up to date in the local repo > > Martijn > > On 10/30/07, Tauren Mills <[EMAIL PROTECTED]> wrote: > > I just updated from svn again and I'm still having this problem. I've > > checked out the entire wicket trunk including jdk-1.4 and jdk-1.5. I > > just updated and did the following: > > > > cd wicket/jdk-1.4/wicket > > mvn install -Dmaven.test.skip=true > > > > But this complains of dependencies missing versions. It works fine if > > I add versions to portlet-api and portals-bridges-common. > > > > Perhaps I'm not doing something I need to do with maven. I am fairly new to > > it. > > > > I've got it working by editing the POM to include versions. But it > > would be nice to not have to do this. How do others make this work? > > Any suggestions? > > > > Tauren > > > > > > On 10/11/07, John Patterson <[EMAIL PROTECTED]> wrote: > > > Have you checked out the entire wicket source tree - that contains > > > jdk14, jdk15 etc? If not then maybe the individual poms cannot find > > > the parent pom that defines those version variables. > > > > > > On 11 Oct 2007, at 22:46, Tauren Mills wrote: > > > > > > > I just updated wicket, wicket-extensions and wicket-examples from > > > > trunk. When I tried to run mvn install eclipse:eclpise, I got errors > > > > stating that there were dependencies missing versions. So I added > > > > versions to the pom.xml for wicket and wicket-examples. Now mvn runs. > > > > > > > > Am I doing something wrong, or do the pom.xml files in trunk need > > > > versions? Changing them to contain version params did the trick, but > > > > should it work without them? > > > > > > > > wicket/pom.xml: > > > > > > > > > > > > javax.portlet > > > > portlet-api > > > > 1.0 > > > > provided > > > > true > > > > > > > > > > > > org.apache.portals.bridges > > > > portals-bridges-common > > > > 1.0.3 > > > > provided > > > > true > > > > > > > > > > > > wicket-examples/pom.xml: > > > > > > > > > > > > javax.portlet > > > > portlet-api > > > > 1.0 > > > > provided > > > > > > > > > > > > - > > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > > > > - > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > - > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > -- > Buy Wicket in Action: http://manning.com/dashorst > Apache Wicket 1.3.0-beta4 is released > Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.0-beta4/ > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: POM problems in trunk?
Do a install from the root your parent pom is not up to date in the local repo Martijn On 10/30/07, Tauren Mills <[EMAIL PROTECTED]> wrote: > I just updated from svn again and I'm still having this problem. I've > checked out the entire wicket trunk including jdk-1.4 and jdk-1.5. I > just updated and did the following: > > cd wicket/jdk-1.4/wicket > mvn install -Dmaven.test.skip=true > > But this complains of dependencies missing versions. It works fine if > I add versions to portlet-api and portals-bridges-common. > > Perhaps I'm not doing something I need to do with maven. I am fairly new to > it. > > I've got it working by editing the POM to include versions. But it > would be nice to not have to do this. How do others make this work? > Any suggestions? > > Tauren > > > On 10/11/07, John Patterson <[EMAIL PROTECTED]> wrote: > > Have you checked out the entire wicket source tree - that contains > > jdk14, jdk15 etc? If not then maybe the individual poms cannot find > > the parent pom that defines those version variables. > > > > On 11 Oct 2007, at 22:46, Tauren Mills wrote: > > > > > I just updated wicket, wicket-extensions and wicket-examples from > > > trunk. When I tried to run mvn install eclipse:eclpise, I got errors > > > stating that there were dependencies missing versions. So I added > > > versions to the pom.xml for wicket and wicket-examples. Now mvn runs. > > > > > > Am I doing something wrong, or do the pom.xml files in trunk need > > > versions? Changing them to contain version params did the trick, but > > > should it work without them? > > > > > > wicket/pom.xml: > > > > > > > > > javax.portlet > > > portlet-api > > > 1.0 > > > provided > > > true > > > > > > > > > org.apache.portals.bridges > > > portals-bridges-common > > > 1.0.3 > > > provided > > > true > > > > > > > > > wicket-examples/pom.xml: > > > > > > > > > javax.portlet > > > portlet-api > > > 1.0 > > > provided > > > > > > > > > - > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > - > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Buy Wicket in Action: http://manning.com/dashorst Apache Wicket 1.3.0-beta4 is released Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.0-beta4/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: POM problems in trunk?
I just updated from svn again and I'm still having this problem. I've checked out the entire wicket trunk including jdk-1.4 and jdk-1.5. I just updated and did the following: cd wicket/jdk-1.4/wicket mvn install -Dmaven.test.skip=true But this complains of dependencies missing versions. It works fine if I add versions to portlet-api and portals-bridges-common. Perhaps I'm not doing something I need to do with maven. I am fairly new to it. I've got it working by editing the POM to include versions. But it would be nice to not have to do this. How do others make this work? Any suggestions? Tauren On 10/11/07, John Patterson <[EMAIL PROTECTED]> wrote: > Have you checked out the entire wicket source tree - that contains > jdk14, jdk15 etc? If not then maybe the individual poms cannot find > the parent pom that defines those version variables. > > On 11 Oct 2007, at 22:46, Tauren Mills wrote: > > > I just updated wicket, wicket-extensions and wicket-examples from > > trunk. When I tried to run mvn install eclipse:eclpise, I got errors > > stating that there were dependencies missing versions. So I added > > versions to the pom.xml for wicket and wicket-examples. Now mvn runs. > > > > Am I doing something wrong, or do the pom.xml files in trunk need > > versions? Changing them to contain version params did the trick, but > > should it work without them? > > > > wicket/pom.xml: > > > > > > javax.portlet > > portlet-api > > 1.0 > > provided > > true > > > > > > org.apache.portals.bridges > > portals-bridges-common > > 1.0.3 > > provided > > true > > > > > > wicket-examples/pom.xml: > > > > > > javax.portlet > > portlet-api > > 1.0 > > provided > > > > > > - > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: POM problems in trunk?
Have you checked out the entire wicket source tree - that contains jdk14, jdk15 etc? If not then maybe the individual poms cannot find the parent pom that defines those version variables. On 11 Oct 2007, at 22:46, Tauren Mills wrote: I just updated wicket, wicket-extensions and wicket-examples from trunk. When I tried to run mvn install eclipse:eclpise, I got errors stating that there were dependencies missing versions. So I added versions to the pom.xml for wicket and wicket-examples. Now mvn runs. Am I doing something wrong, or do the pom.xml files in trunk need versions? Changing them to contain version params did the trick, but should it work without them? wicket/pom.xml: javax.portlet portlet-api 1.0 provided true org.apache.portals.bridges portals-bridges-common 1.0.3 provided true wicket-examples/pom.xml: javax.portlet portlet-api 1.0 provided - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
POM problems in trunk?
I just updated wicket, wicket-extensions and wicket-examples from trunk. When I tried to run mvn install eclipse:eclpise, I got errors stating that there were dependencies missing versions. So I added versions to the pom.xml for wicket and wicket-examples. Now mvn runs. Am I doing something wrong, or do the pom.xml files in trunk need versions? Changing them to contain version params did the trick, but should it work without them? wicket/pom.xml: javax.portlet portlet-api 1.0 provided true org.apache.portals.bridges portals-bridges-common 1.0.3 provided true wicket-examples/pom.xml: javax.portlet portlet-api 1.0 provided - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
