Uploaded image for project: 'JBoss Enterprise Application Platform 4 and 5'
  1. JBoss Enterprise Application Platform 4 and 5
  2. JBPAPP-8938

Manual excludes from the maven repository zip should also fix the metadata

XMLWordPrintable

    • Icon: Feature Request Feature Request
    • Resolution: Obsolete
    • Icon: Optional Optional
    • EAP No Release
    • None
    • Maven Repository
    • None
    • NEW

      When we manually exclude the hibernate 3 jars from the maven repository, the metadata still lists the 3.x version. If possible the exclude should update the metadata in addition to removing the version.

      Also the current hibernate 3 exclude is basically a hack which tricks the script into thinking that the artifactId is 3.6.5.Final-redhat-1.

      org.hibernate.hibernate-core:3.6.5.Final-redhat-1:
      

      Maybe as part of this fix we need to have a better way to exclude specific versions of artifacts. Something like this?

      org.hibernate:hibernate-core:3.6.5.Final-redhat-1
      

              vdosoudi@redhat.com Vladimir Dosoudil
              pgier@redhat.com Paul Gier (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: