pom changes for basic hibernate project
---------------------------------------
Key: MNG-387
URL: http://jira.codehaus.org/browse/MNG-387
Project: m2
Type: Bug
Components: repository-tools
Reporter: Ryan Sonnek
it seems as if the current m2 repository has some invalid poms. I'm assuming
this is because the m2 pom's were automatically generated from the m1 pom's.
Here is a list of changes that were required in my local repository to get a
very basic hibernate project up and going.
change dom4j-1.6.pom stax dependencies to these:
<dependency>
<groupId>stax</groupId>
<artifactId>stax-api</artifactId>
<version>1.0</version>
</dependency>
<dependency>
<groupId>stax</groupId>
<artifactId>stax</artifactId>
<version>1.1-dev</version>
</dependency>
remove this dependency from stax-1.1-dev.pom:
<dependency>
<groupId>xmlbeans-jsr173-api</groupId>
<artifactId>xmlbeans-jsr173-api</artifactId>
<version>2.0-dev</version>
</dependency>
manually install geronimo servlet-api as servlet api
remove two dependencies from xom-1.0b3.pom:
<dependency>
<groupId>icu4j</groupId>
<artifactId>icu4j</artifactId>
<version>2.6.1</version>
</dependency>
<dependency>
<groupId>tagsoup</groupId>
<artifactId>tagsoup</artifactId>
<version>0.9.7</version>
</dependency>
manually install empty jdbc-2.0.jar
can these pom's be scrubbed, or move these dependencies to the m2 repository?
--
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
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
