If I re-generate a new application with andromdapp:generate and then
replace all ${maven.src.dir}/.. with ${basedir} in the root maven.xml
then the deploy works on Linux.
-Tim
On Thu, 2005-03-31 at 11:51 -0800, Tim Dysinger wrote:
> I was just doing that... The src directory does not exist. I am on
> Linux and this path doesn't work. See below:
>
> ls /home/tim/work/test/src/../app/project.xml
> ls: /home/tim/work/test/src/../app/project.xml:
> No such file or directory
>
> but if you take the src/.. off it works fine. It's because
> ${basedir}/src doesn't exist not because the project.xml file doesn't
> exist.
>
> ls /home/tim/work/test/app/project.xml
> /home/tim/work/test/app/project.xml
>
> >From my 3.0M3 project [/maven.xml]
>
> <goal name="deploy">
> <maven:maven
> descriptor="${maven.src.dir}/../app/project.xml"
> goals="deploy"/>
> </goal>
>
> I am not setting my maven.src.dir anywhere so it is the default
> '/home/tim/work/test/src'. It blows up because that directory doesn't
> exist in my multiproject setup. My 'test' project's base directory just
> has common, core, web, app, etc. This is exactly as it is generated - I
> haven't touched a thing.
>
> ==============================STACK=============================
>
> BUILD FAILED
> org.apache.maven.MavenException: Error parsing project.xml
> '/home/tim/work/test/src/../app/project.xml'
> at
> org.apache.maven.MavenUtils.getNonJellyProject(MavenUtils.java:207)
> at org.apache.maven.MavenUtils.getProject(MavenUtils.java:143)
> at org.apache.maven.MavenUtils.getProject(MavenUtils.java:122)
> at
> org.apache.maven.jelly.tags.maven.MavenTag.doTag(MavenTag.java:71)
> at
> org.apache.commons.jelly.impl.TagScript.run(TagScript.java:279)
> at
> org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:135)
> at
> org.apache.maven.jelly.tags.werkz.MavenGoalTag.runBodyTag(MavenGoalTag.java:79)
> at org.apache.maven.jelly.tags.werkz.MavenGoalTag
> $MavenGoalAction.performAction(MavenGoalTag.java:110)
> at com.werken.werkz.Goal.fire(Goal.java:639)
> at com.werken.werkz.Goal.attain(Goal.java:575)
> at
> org.apache.maven.plugin.PluginManager.attainGoals(PluginManager.java:671)
> at
> org.apache.maven.MavenSession.attainGoals(MavenSession.java:263)
> at org.apache.maven.cli.App.doMain(App.java:488)
> at org.apache.maven.cli.App.main(App.java:1239)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:324)
> at com.werken.forehead.Forehead.run(Forehead.java:551)
> at com.werken.forehead.Forehead.main(Forehead.java:581)
> --- Nested Exception ---
> java.io.FileNotFoundException: /home/tim/work/test/src/../app/project.xml (No
> such file or directory)
> at java.io.FileInputStream.open(Native Method)
> at java.io.FileInputStream.<init>(FileInputStream.java:106)
> at
> org.apache.commons.digester.Digester.parse(Digester.java:1525)
> at
> org.apache.maven.MavenUtils.getNonJellyProject(MavenUtils.java:203)
> at org.apache.maven.MavenUtils.getProject(MavenUtils.java:143)
> at org.apache.maven.MavenUtils.getProject(MavenUtils.java:122)
> at
> org.apache.maven.jelly.tags.maven.MavenTag.doTag(MavenTag.java:71)
> at
> org.apache.commons.jelly.impl.TagScript.run(TagScript.java:279)
> at
> org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:135)
> at
> org.apache.maven.jelly.tags.werkz.MavenGoalTag.runBodyTag(MavenGoalTag.java:79)
> at org.apache.maven.jelly.tags.werkz.MavenGoalTag
> $MavenGoalAction.performAction(MavenGoalTag.java:110)
> at com.werken.werkz.Goal.fire(Goal.java:639)
> at com.werken.werkz.Goal.attain(Goal.java:575)
> at
> org.apache.maven.plugin.PluginManager.attainGoals(PluginManager.java:671)
> at
> org.apache.maven.MavenSession.attainGoals(MavenSession.java:263)
> at org.apache.maven.cli.App.doMain(App.java:488)
> at org.apache.maven.cli.App.main(App.java:1239)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:324)
> at com.werken.forehead.Forehead.run(Forehead.java:551)
> at com.werken.forehead.Forehead.main(Forehead.java:581)
> File...... /home/tim/work/test/maven.xml
> Element... maven:maven
> Line...... 36
> Column.... 29
> Error parsing project.xml '/home/tim/work/test/src/../app/project.xml'
>
>
> On Thu, 2005-03-31 at 12:39 -0700, Chad Brandon wrote:
> > Tim Dysinger wrote:
> >
> > >I don't understand it. I rebuilt my Maven plugins from CVS this
> > >morning. My repository is up to date too. ???
> > >
> > >I am using Maven 1.0.2 and JDK 1.4.2_07 with nothing special installed.
> > >
> > >
> > Try running deploy with -e and see if it gives you any more useful
> > information.
> >
> > >-Tim
> > >
> > >
> > >
> > >
> >
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by Demarc:
> A global provider of Threat Management Solutions.
> Download our HomeAdmin security software for free today!
> http://www.demarc.com/Info/Sentarus/hamr30
> _______________________________________________
> Andromda-user mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/andromda-user
-------------------------------------------------------
This SF.net email is sponsored by Demarc:
A global provider of Threat Management Solutions.
Download our HomeAdmin security software for free today!
http://www.demarc.com/Info/Sentarus/hamr30
_______________________________________________
Andromda-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/andromda-user
