org.apache.geronimo.cars sounds good to me. That would be the pom in geronimo/applications dir. I see the pom exists in the trunk (http://svn.apache.org/viewcvs.cgi/geronimo/trunk/applications/pom.xml?rev=390662&view=log)
If you have a pom there, do a 'mvn -N' in that dir. You shouldn't have to. But that'll get u going for now. Let me do a new top down build. Cheers Prasad On 4/5/06, anita kulshreshtha <[EMAIL PROTECTED]> wrote: > Hi All, > We need a gropuId for cars. One possibility is > org.apache.geronimo.cars. comments ? > Prasad or Jacek, I am at rev 391200. I am building with clean repo. > A pom seem to be missing. > > Thanks > Anita > > > [INFO] Scanning for projects... > [INFO] > ---------------------------------------------------------------------------- > [ERROR] FATAL ERROR > [INFO] > ---------------------------------------------------------------------------- > [INFO] Failed to resolve artifact. > > GroupId: org.apache.geronimo.applications > ArtifactId: applications-parent > Version: 1.2-SNAPSHOT > > Reason: Unable to download the artifact from any repository > > org.apache.geronimo.applications:applications-parent:pom:1.2-SNAPSHOT > > from the specified remote repositories: > central (http://repo1.maven.org/maven2) > > > --- Prasad Kashyap <[EMAIL PROTECTED]> wrote: > > > Comments inline - > > > > On 3/30/06, Jacek Laskowski <[EMAIL PROTECTED]> wrote: > > > On 3/27/06, Prasad Kashyap <[EMAIL PROTECTED]> wrote: > > > > Having hit a roadblock with the assembly-plugin (details here- > > > > http://issues.apache.org/jira/browse/GERONIMO-1737), I've moved > > on to > > > > migrating the applications now. > > > > > > Hi Prasad, > > > > Hi Jacek, > > > > > > > > I think I found a solution to this. What about keeping the list in > > > pom.xml as <property>'s? It could process the list and do what the > > > current plugin does. I'll have to give it a shot. If it doesn't > > work > > > I'll commit the already-generated-by-M1-plugin files to the repo to > > > let us move on. > > > > > > Keeping the list in the <property> won't help. There is a lot more > > information that needs to be passed to the plugin than just the name. > > At the very least, there's the destination directory. Then there's > > some special post-processing like copying schema files into a > > flattened structure. > > > > We cannot use the M1 generated plugin because it depends on tags in > > the project.xml to work on. We won't have any such in our pom.xml. > > We'll have to revisit this big time in a separate thread when the > > config changes have stabilized. > > > > > > > > Once Anita is done with the packaging plugin, we begin migrating > > configs. > > > > > > +1 > > > > Anita, how far along are you on the packaging plugin ? > > > > > -- > > > Jacek Laskowski > > > > Cheers > > Prasad > > > > > __________________________________________________ > Do You Yahoo!? > Tired of spam? Yahoo! Mail has the best spam protection around > http://mail.yahoo.com >
