| Key: |
XMLBEANS-277
|
| Type: |
New Feature
|
| Status: |
Resolved
|
| Resolution: |
Fixed
|
| Priority: |
Major
|
| Assignee: |
Unassigned
|
| Reporter: |
David Jencks
|
| Votes: |
4
|
| Watchers: |
4
|
|
If you were logged in you would be able to see more operations.
|
|
|
|
File Attachments:
|
| |
Size |
|
m2-repo.jar |
2006-06-29 06:37 AM |
David Jencks |
11 kB |
|
|
| Resolution Date: |
06/Jun/07 03:01 PM
|
|
xmlbeans needs accurate maven 2 metadata to ease its use in maven2 built projects. The metadata (pom files) currently published for xmlbeans is inaccurate. I think this would be a good opportunity to also switch the "groupId" for xmlbeans to the maven 2 standard format org.apache.xmlbeans.
I'll attach some preliminary metadata files in a jar. If xmlbeans team members could check at least one pom file for accuracy in urls, mailing lists, team members, etc, I'd appreciate it. I'm asking the maven team about some details on how to handle the xmlpublic jar and the xbean_xpath jar, and also trying to get some testing going to make sure this is reasonably accurate.
|
|
Description
|
xmlbeans needs accurate maven 2 metadata to ease its use in maven2 built projects. The metadata (pom files) currently published for xmlbeans is inaccurate. I think this would be a good opportunity to also switch the "groupId" for xmlbeans to the maven 2 standard format org.apache.xmlbeans.
I'll attach some preliminary metadata files in a jar. If xmlbeans team members could check at least one pom file for accuracy in urls, mailing lists, team members, etc, I'd appreciate it. I'm asking the maven team about some details on how to handle the xmlpublic jar and the xbean_xpath jar, and also trying to get some testing going to make sure this is reasonably accurate. |
Show » |
|
Maven 2 metadata for xmlbeans jars
So far the main effect is that the groupId is now org.apache.xmlbeans rather than xmlbeans and you don't need a stax-api dependency since xmlbeans includes it.