[ http://jira.codehaus.org/browse/MEV-392?page=comments#action_65394 ] 

Dennis Lundberg commented on MEV-392:
-------------------------------------

The pom you are seeing in the repo must be something that is automatically 
converted from the M1 POM that we have in commons-logging. I'm not sure how 
that works exactly, but I'm sure that Carlos can tell you more. Commons-logging 
does not have an M2 POM itself yet.

Now to your questions about the dependencies. The current build for 
commons-logging is based on Ant. There are several reasons for that, that I 
will not go into detail about. But one of the reasons is that commons-logging 
does not follow the design guidelines set up by Maven and therefor it is not 
easy to Mavenize. The rule that we don't follow is that of one module - one 
artifact. There are several artifacts that form commons-logging:
- commons-logging (includes everything)
- commons-logging-adapters
- commons-logging-api

These artifacts have different dependencies because they contain different 
classes. This makes it difficult to create one POM to rule them all, without 
putting everything in there. Log4j, avalon-framework, logkit and servlet-api 
are required to compile commons-logging and commons-logging-adapters. The 
artifact that most people should use as a dependency in their own products is 
commons-logging-api which doesn't require these dependencies, but there is no 
POM for that.

I will disuss this on commons-dev with the rest of the team to see what the 
best approach would be.

> bad dependencies in commons-logging-1.1.pom
> -------------------------------------------
>
>          Key: MEV-392
>          URL: http://jira.codehaus.org/browse/MEV-392
>      Project: Maven Evangelism
>         Type: Bug

>   Components: Dependencies
>     Reporter: Olivier Lamy

>
>
> Hi,
> I have trouble concerning dependencies in commons-logging 1.1
>     <dependency>
>       <groupId>javax.servlet</groupId>
>       <artifactId>servlet-api</artifactId>
>       <version>2.3</version>
>     </dependency>
> scope must be provided
>     <dependency>
>       <groupId>avalon-framework</groupId>
>       <artifactId>avalon-framework</artifactId>
>       <version>4.1.3</version>
>     </dependency>
> as 1.0.4 scope must be optionnal
>     <dependency>
>       <groupId>logkit</groupId>
>       <artifactId>logkit</artifactId>
>       <version>1.0.1</version>
>     </dependency>
> as 1.0.4 scope must be optionnal

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

Reply via email to