commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Henri Yandell" <flame...@gmail.com>
Subject Re: [all] maven2 pom.xml files of commons
Date Thu, 13 Jul 2006 07:19:01 GMT
On 7/12/06, Nicolas De Loof <nicolas.deloof@capgemini.com> wrote:
>
>
> > Commons does not have pom.xml for its components. Them pom files you
> > find at the repositories (i.e. ibiblio) are converted by a piece of
> > software from our (Maven 1) project.xml files. This conversion is made
> > automatically. We are able to add some comments in our project.xml
> > files to fix some of the conversion problems.
> >
> > So a couple of examples would be nice. Then I can check to see what
> > the problems might be and if/how we can solve them.
> >
> Maybe the maven project.xml 2 pom.xml converter may consider maven1
> properties that have a direct equivalent in maven2 ?
> For example, if junit is refered as :
> <dependency>
>    <id>junit</id>
>    <version>3.8.1</version>
>    <properties><scope>test</scope></properties>
> </dependency>
>
> this <scope> property has no effect on maven1 but is valid and adds
> documentation to dependency use. It can be converted to the <scope>
> element in a maven2 pom.
>
> This can be a way to "help" the converter when a project is aware of
> beeing used by maven2 users but doesn't use it itself.

Afaik, it does. Just need to add it to all the project.xml's.

Hen

---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org


Mime
View raw message