It should work but your project's version should be something like 1.0-SNAPSHOT, not 1.0.
That being said, it could be a thing as simple as a typo so posting your project somewhere would help. S. On Fri, Sep 17, 2010 at 11:46 PM, Jon Paynter <[email protected]> wrote: > Hi -- ive been tasked with looking to see if maven will work to replace our > current ant build. > > Since our company makes extensive use of j2ee and OC4J components, that was > one of the first thigns I tackled after getting some basic modules to > compile. > > In keeping with our existing ant build structure I setup the following tree > structure: > OC4J pom.xml > | > |--- OC4J.ear > | > |--- OC4J.rar > | > |--- OC4J.war > > The ear is setup with a dependancy on the war file. > If goto the top level folder and run: mvn compile -- all is fine. no > errors. > > but when I goto the top level folder and run: mvn package > I get an error when building the ear file saying it cant find the war file: > > [ERROR] Failed to execute goal on project OC4J.ear: Could not resolve > dependencies for project cdrive:OC4J.ear:ear:1.0: The following artifacts > could not be resolved: cdrive:OC4J.war:war:1.0: Failure to find > cdrive:OC4J.war:war:1.0 in http://repo1.maven.org/maven2 was cached in the > local repository. Resolution will not be reattempted until the update > interval of central has elapsed or updates are forced. -> [Help 1] > > > I started this endevor using maven 2.2.1 but I had the same problems with > ear generation. searching led me to a post back from 2007 where somebody > had the exact same problem, but there was no resolution posted. I was > hoping maven 3.0 would fix the issue, but it just gives different error > messages. > > > So my questions are as follows: > > 1) Is there a better way to do this? -- if so it needs to scale well, the > project has about 20 OC4J components. > 2) if not, how do I fix the dependancies so this will work? > 3) if neither... will this be fixed in maven 3.0? >
