You are viewing a plain text version of this content. The canonical link for it is here.
Posted to cvs@avalon.apache.org by le...@apache.org on 2003/06/07 18:43:52 UTC
cvs commit: avalon-excalibur/configuration maven.xml project.properties project.xml
leosimons 2003/06/07 09:43:52
Added: configuration maven.xml project.properties project.xml
Log:
maven buildfiles
Revision Changes Path
1.1 avalon-excalibur/configuration/maven.xml
Index: maven.xml
===================================================================
<?xml version="1.0"?>
<project default="java:jar"
xmlns:j="jelly:core"
xmlns:ant="jelly:ant">
<!-- include the excalibur-wide custom project properties -->
<property file="${basedir}/project.properties"/>
<property file="${basedir}/../project.properties"/>
<property file="${basedir}/../../project.properties"/>
<property file="${basedir}/../../../project.properties"/>
<property file="${basedir}/../../../../project.properties"/>
<!-- include the excalibur-wide custom goal decorators from maven-common.xml -->
<j:import file="${basedir}/../maven-common.xml" inherit="true"/>
<!-- copy additional test resources -->
<postGoal name="test:prepare-filesystem">
<echo>
copy additional unit test resources
from ${pom.build.unitTestSourceDirectory}
to ${maven.test.dest}
</echo>
<copy todir="${maven.build.dir}/test-classes">
<fileset dir="${pom.build.unitTestSourceDirectory}">
<exclude name="**/*.java"/>
<exclude name="**/package.html"/>
</fileset>
</copy>
</postGoal>
</project>
1.1 avalon-excalibur/configuration/project.properties
Index: project.properties
===================================================================
# -------------------------------------------------------------------
# P R O J E C T P R O P E R T I E S
# -------------------------------------------------------------------
maven.repo.remote = http://lsd.student.utwente.nl/repository,http://www.apache.org/dist/avalon,http://www.ibiblio.org/maven
1.1 avalon-excalibur/configuration/project.xml
Index: project.xml
===================================================================
<?xml version="1.0" encoding="UTF-8"?>
<project>
<extend>${basedir}/../project-common.xml</extend>
<name>Configuration</name>
<id>excalibur-configuration</id>
<currentVersion>1.1-dev</currentVersion>
<inceptionYear>2003</inceptionYear>
<shortDescription>Excalibur's Configuration component</shortDescription>
<description>
The Configuration package contains extensions to the Avalon Framework
supporting configuration management.
</description>
<dependencies>
<dependency>
<id>avalon-framework</id>
<version>4.1.4</version>
<groupId>framework</groupId>
</dependency>
<!-- todo, get one from ibiblio! -->
<dependency>
<id>jing</id>
<version>20020724</version>
<groupId>forrest</groupId>
</dependency>
<dependency>
<id>isorelax</id>
<version>20030108</version>
</dependency>
</dependencies>
</project>
---------------------------------------------------------------------
To unsubscribe, e-mail: cvs-unsubscribe@avalon.apache.org
For additional commands, e-mail: cvs-help@avalon.apache.org
Re: building excalibur using maven
Posted by Leo Simons <le...@apache.org>.
Leo Simons wrote:
> = Converting excalibur to maven =
>
> I'm making reasonable progress (lack of docs really is the major thing
> slowing me down, but the maven plugins contain plenty examples). Just
> about everything is starting to work like it should. Try 'maven
> excalibur:info' inside the avalon-excalibur directory for details.
The system has been updated to output build.xml files and gump descriptors.
- LSD
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org
Re: building excalibur using maven
Posted by Leo Simons <le...@apache.org>.
for those wondering what my plan is here...
After looking at cornerstone, I've figured that excalibur actually needs
less attention, so I'll leave the excalibur -> maven conversion dangling
in the middle for a little.
Also, I get annoyed with all the existing cruft and taking into account
the existing build system while restructuring directory layouts so I
want to do that in a new repo.
That doesn't mean it is not a good idea to start writing those maven
POMs, though, or that no-one should make other plans ;)
Leo Simons wrote:
> Hi gang!
>
> = Converting excalibur to maven =
g'night!
- LSD
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org
Re: building excalibur using maven
Posted by Stephen McConnell <mc...@apache.org>.
Leo:
I have maven based builds already running for the following Excalibur
projects:
configuration
event
extension
i18n
instrument
thread
They need to be updated to work with the avalon repository scheme but
aside from that they are working. I'm more than happy to comit them as
a starting point to get things working.
Cheers, Steve.
Leo Simons wrote:
> Hi gang!
>
> the below is also up on the wiki @
>
> http://nagoya.apache.org/wiki/apachewiki.cgi?AvalonExcaliburBuildRefactoring
>
>
> = Converting excalibur to maven =
>
> I'm making reasonable progress (lack of docs really is the major thing
> slowing me down, but the maven plugins contain plenty examples). Just
> about everything is starting to work like it should. Try 'maven
> excalibur:info' inside the avalon-excalibur directory for details.
>
> Now is the time for feature requests if you have any besides those
> documented :D
>
> What I need now is people to help with writing maven POMs. Here's how:
>
>
> == How to Convert components to build with maven ==
>
> # to cvs
> cd ~/cvs/avalon-excalibur
>
> # seed new project
> maven excalibur:seed -Dcomponent.dir=event \
> -Dcomponent.name=Event -Dcomponent.id=excalibur-event
>
> cd event
>
> # add <dependencies/> to project.xml; figure out this
> # information from the classpaths defined in build.xml
> # and/or the gump descriptors. Figure out <id/> and
> # <version/> by browsing www.apache.org/dist/avalon/
> emacs project.xml
>
> # build jar, run tests, make sure things work
> maven java:jar
>
> # customize maven.xml to build 'special' stuff
> emacs maven.xml
>
> cvs add maven.xml project.properties project.xml
> cvs commit -m 'maven buildfiles' maven.xml project.properties \
> project.xml
>
>
> == Things To Do ==
>
> - get the maven-forrest-plugin into cvs and all fixed up (see
> forrest-dev for info)
>
> - add maven.xml, project.xml, project.properties for all components as
> described above
>
> - perform some more tests on the 'excalibur:deploy' target and then
> make it talk to the 'live' repo
>
>
> cheers!
>
> - Leo
>
> leosimons@apache.org wrote:
>
>> leosimons 2003/06/07 09:43:52
>>
>> Added: configuration maven.xml project.properties project.xml
>> Log:
>> maven buildfiles
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
> For additional commands, e-mail: dev-help@avalon.apache.org
>
>
>
--
Stephen J. McConnell
mailto:mcconnell@apache.org
http://www.osm.net
Sent via James running under Merlin as an NT service.
http://avalon.apache.org/sandbox/merlin
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org
building excalibur using maven (was: Re: cvs commit: maven.xml project.properties
project.xml)
Posted by Leo Simons <le...@apache.org>.
Hi gang!
the below is also up on the wiki @
http://nagoya.apache.org/wiki/apachewiki.cgi?AvalonExcaliburBuildRefactoring
= Converting excalibur to maven =
I'm making reasonable progress (lack of docs really is the major thing
slowing me down, but the maven plugins contain plenty examples). Just
about everything is starting to work like it should. Try 'maven
excalibur:info' inside the avalon-excalibur directory for details.
Now is the time for feature requests if you have any besides those
documented :D
What I need now is people to help with writing maven POMs. Here's how:
== How to Convert components to build with maven ==
# to cvs
cd ~/cvs/avalon-excalibur
# seed new project
maven excalibur:seed -Dcomponent.dir=event \
-Dcomponent.name=Event -Dcomponent.id=excalibur-event
cd event
# add <dependencies/> to project.xml; figure out this
# information from the classpaths defined in build.xml
# and/or the gump descriptors. Figure out <id/> and
# <version/> by browsing www.apache.org/dist/avalon/
emacs project.xml
# build jar, run tests, make sure things work
maven java:jar
# customize maven.xml to build 'special' stuff
emacs maven.xml
cvs add maven.xml project.properties project.xml
cvs commit -m 'maven buildfiles' maven.xml project.properties \
project.xml
== Things To Do ==
- get the maven-forrest-plugin into cvs and all fixed up (see
forrest-dev for info)
- add maven.xml, project.xml, project.properties for all components as
described above
- perform some more tests on the 'excalibur:deploy' target and then make
it talk to the 'live' repo
cheers!
- Leo
leosimons@apache.org wrote:
> leosimons 2003/06/07 09:43:52
>
> Added: configuration maven.xml project.properties project.xml
> Log:
> maven buildfiles
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org