You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by Joerg Hohwiller <jo...@j-hohwiller.de> on 2006/07/13 00:44:25 UTC
[all] maven2 pom.xml files of commons
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi there,
I used maven2 and a lot of the maven commons in some projects.
To me it seems that there are various mistakes in the POMs of some projects of
the commons. The major one is that "junit" is added with scope "compile"
(default) instead of test. I gues this comes from the ugly maven1 world.
Actually it is kinda bad that tons of users need to fix this "bugs" by declaring
exclusions for them what makes the dependencies even more complicated.
It would be a lot easier to fix this once in the source of the problem.
Are you already working on this?
I would be very pleased if you could fix this.
If you need an exact list of all problems I discovered, please let me know...
Regards
Jörg
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFEtXtJmPuec2Dcv/8RAlGvAJ4m7t++qjPVPulkNYiK72j6xw0zDACfdzjk
10NhSaSYO68PQZHzw9BteBY=
=hu3H
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: [all] maven2 pom.xml files of commons
Posted by Henri Yandell <fl...@gmail.com>.
On 7/12/06, Nicolas De Loof <ni...@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
Re: [all] maven2 pom.xml files of commons
Posted by Nicolas De Loof <ni...@capgemini.com>.
> 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.
Just my 2 cents...
Nico.
This message contains information that may be privileged or confidential and is the property of the Capgemini Group. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message.
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: [all] maven2 pom.xml files of commons
Posted by Dennis Lundberg <de...@apache.org>.
Joerg Hohwiller wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Hi there,
>
> I used maven2 and a lot of the maven commons in some projects.
>
> To me it seems that there are various mistakes in the POMs of some projects of
> the commons. The major one is that "junit" is added with scope "compile"
> (default) instead of test. I gues this comes from the ugly maven1 world.
>
> Actually it is kinda bad that tons of users need to fix this "bugs" by declaring
> exclusions for them what makes the dependencies even more complicated.
> It would be a lot easier to fix this once in the source of the problem.
>
> Are you already working on this?
> I would be very pleased if you could fix this.
> If you need an exact list of all problems I discovered, please let me know...
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.
--
Dennis Lundberg
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org