Hi Berin,
>
> Unico Hommes wrote:
>
> > Hi,
> >
> > I was trying to build some components in excalibur that
> seem to have
> > proper project descriptors to build using maven. But am not having
> > much success. Using maven beta9 I get:
> >
> > File...... null
> > Element... property
> > Line...... 14
> > Column.... 65
> > You must specify file, resource or environment when not
> using the name
> > attribute
> >
> > Anybody have an idea how to get this working?
>
>
> We have just started converting the Excalibur components to
> Maven. We are not done with it yet, so for the time being we
> still have to use ANT.
>
Ah OK, in that case I found two minor issues in avalon buildsystem I'd
like to share:
<patch>
Index: maven.xml
===================================================================
RCS file: /home/cvspublic/avalon/buildsystem/maven.xml,v
retrieving revision 1.7
diff -u -r1.7 maven.xml
--- maven.xml 17 Jun 2003 17:25:51 -0000 1.7
+++ maven.xml 10 Jul 2003 12:43:19 -0000
@@ -322,7 +322,7 @@
</j:if>
<!-- argument defaults -->
- <j:if test="${empty(use.forrest)}">
+ <j:if test="empty(use.forrest)">
<j:set var="use.forrest" value="true"/>
</j:if>
@@ -424,7 +424,7 @@
maven.repo.remote =
http://lsd.student.utwente.nl/repository,http://www.apache.org/dist/aval
on,http://www.ibiblio.org/maven
# location of the build system
-avalon.buildsystem = $${basedir}/../avalon-buildsystem
+avalon.buildsystem = $${basedir}/../buildsystem
# gump integration
project.name=${component.id}
</patch>
There will still be a problem with generation of the project.properties
file on Windows because it will print something like:
# location of the build system
avalon.buildsystem = e:\apache\avalon\buildsystem/../buildsystem
... Wich when read in by ant will resolve to
e:apacheavalonbuildsystem/../buildsystem . I don't know how to fix this
though.
Regards,
Unico
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
