openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Francesco Chicchiriccò (Updated) (JIRA) <j...@apache.org>
Subject [jira] [Updated] (OPENJPA-2113) Warning
Date Wed, 18 Jan 2012 11:13:42 GMT

     [ https://issues.apache.org/jira/browse/OPENJPA-2113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Francesco Chicchiriccò updated OPENJPA-2113:
--------------------------------------------

    Attachment: redeclareRepository.patch
    
> Warning 
> --------
>
>                 Key: OPENJPA-2113
>                 URL: https://issues.apache.org/jira/browse/OPENJPA-2113
>             Project: OpenJPA
>          Issue Type: Bug
>          Components: integration
>    Affects Versions: 2.2.0
>            Reporter: Francesco Chicchiriccò
>              Labels: maven
>         Attachments: redeclareRepository.patch
>
>
> Everry time that openjpa-maven-plugin is run, it shows the following warning:
> [INFO] --- openjpa-maven-plugin:2.2.0-SNAPSHOT:sql (default-cli) @
> syncope-core ---
> Downloading:
> file://${basedir}/internal-repository/org/apache/openjpa/openjpa-lib/2.2.0-SNAPSHOT/maven-metadata.xml
> [WARNING] Could not transfer metadata
> org.apache.openjpa:openjpa-lib:2.2.0-SNAPSHOT/maven-metadata.xml from/to
> openjpa-internal (file://${basedir}/internal-repository): Repository
> path /internal-repository does not exist, and cannot be created.
> I've found that this is happening because of an internal-only repository declared in
openjpa-kernel's POM.
> In the attached patch I just overwrite such repository declaration: I guess there could
be a more elegant way to achieve this, anyway...

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

Mime
View raw message