I misspoke... That should be JIRA MEV component... Maven Evangelism.

Wayne

On 5/9/06, Wayne Fay <[EMAIL PROTECTED]> wrote:
This is probably one of those poms that were created a few months ago
"automatically" in an effort to create poms for all jars that didn't
have any.

This was only done for a short while before the Maven developers
realized it was probably a bad idea in the long run, so they quit
doing it.

To "fix" this "bad" pom, you can create a good pom, create a new bug
in JIRA MVN component, and then attach your good pom to the bug.

Wayne

On 5/9/06, David Smiley <[EMAIL PROTECTED]> wrote:
> Hello everyone.  I've just started using Maven 2; I was using Maven 1
> before.  It's pretty cool, especially the transitive dependencies.
>
> In my Maven 1 project that used Axis web services, I had to specify a
> litany of dependencies.  Here's a bit of my old project.xml:
>          <dependency>
>              <groupId>commons-logging</groupId>
>              <artifactId>commons-logging</artifactId>
>              <version>1.0.4</version>
>          </dependency>
>          <dependency>
>              <groupId>log4j</groupId>
>              <artifactId>log4j</artifactId>
>              <version>1.2.8</version>
>          </dependency>
>          <dependency>
>              <groupId>axis</groupId>
>              <artifactId>axis</artifactId>
>              <version>1.1</version>
>          </dependency>
>          <dependency>
>              <groupId>axis</groupId>
>              <artifactId>jaxrpc</artifactId>
>              <version>1.1</version>
>          </dependency>
>          <dependency>
>              <groupId>axis</groupId>
>              <artifactId>saaj</artifactId>
>              <version>1.1</version>
>          </dependency>
>          <dependency>
>              <groupId>commons-discovery</groupId>
>              <artifactId>commons-discovery</artifactId>
>              <version>0.2</version>
>          </dependency>
>          <dependency>
>              <groupId>wsdl4j</groupId>
>              <artifactId>wsdl4j</artifactId>
>              <version>1.4</version>
>          </dependency>
>          <dependency>
>              <groupId>classworlds</groupId>
>              <artifactId>classworlds</artifactId>
>              <version>1.0</version>
>          </dependency>
>
> Perhaps one or two of those aren't actually needed via axis but any way
> it sure is a bunch--making a perfect candidate to take advantage of the
> Maven 2 dependency system.
>
> I would expect that for axis in Maven 2, there would be a pom (or
> whatever) in the repository with these dependencies registered
> (including "scope" entries as appropriate).  BUT, the pom here:
> http://www.ibiblio.org/maven2/axis/axis/1.1/axis-1.1.pom
> Lists no dependencies at all.  Am I looking in the wrong place or
> perhaps I don't quite get the concept or perhaps axis's pom is
> deficient.  If it's the last one then who do I prod to correct this?
>
> ~ David Smiley
>
>

Reply via email to