[jira] [Resolved] (OPENJPA-2113) Warning on openjpa-maven-plugin execution

["Francesco Chicchiriccò (Resolved JIRA)" <ji...@apache.org>]

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

Francesco Chicchiriccò resolved OPENJPA-2113.
---------------------------------------------

       Resolution: Invalid
    Fix Version/s: 2.2.0

Once moved from 2.2.0-SNAPSHOT to 2.2.0, this issue disappeared.
                
> Warning on openjpa-maven-plugin execution
> -----------------------------------------
>
>                 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
>             Fix For: 2.2.0
>
>         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