Protege Project › Protege Developer

BUILD FAILURE...could not resolve depedencies

Classic

List

Threaded

4 messages Options

OntoBLW

BUILD FAILURE...could not resolve depedencies

Hi,
I am developing a plugin. All was working fine until a build failure was raised. Is it related to a network problem? how can I fix it? In what follows the message appended in my IDE:
------------------------------------------------------------------------
Building OWLChanges 1.0.1-SNAPSHOT
------------------------------------------------------------------------
The metadata C:\Users\g50\.m2\repository\org\eclipse\equinox\common\maven-metadata-central.xml is invalid: attribute value must start with quotation or apostrophe not C (position: TEXT seen <html><head>\n<meta http-equiv=C... @2:19)
------------------------------------------------------------------------
BUILD FAILURE
------------------------------------------------------------------------
Total time: 1.798s
Finished at: Mon Feb 06 17:37:22 GMT+01:00 2017
Final Memory: 6M/15M
------------------------------------------------------------------------
Failed to execute goal on project protege.plugin.owlchanges: Could not resolve dependencies for project edu.stanford.protege:protege.plugin.owlchanges:bundle:1.0.1-SNAPSHOT: Failure to find org.eclipse.equinox:common:jar:3.3.0-v20070426 in https://repository.sonatype.org/content/groups/forge/ was cached in the local repository, resolution will not be reattempted until the update interval of sonatype-forge has elapsed or updates are forced -> [Help 1]

To see the full stack trace of the errors, re-run Maven with the -e switch.
Re-run Maven using the -X switch to enable full debug logging.

For more information about the errors and possible solutions, please read the following articles:
[Help 1] http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException

Josef Hardi

Re: BUILD FAILURE...could not resolve depedencies

Hi,

please check if this solution may work for you

http://stackoverflow.com/questions/4701532/force-maven-update

Best,

Josef

On Feb 6, 2017, at 9:08 AM, OntoBLW <[hidden email]> wrote:

Hi,
I am developing a plugin. All was working fine until a build failure was
raised. Is it related to a network problem? how can I fix it? In what
follows the message appended in my IDE:
------------------------------------------------------------------------
Building OWLChanges 1.0.1-SNAPSHOT
------------------------------------------------------------------------
The metadata
C:\Users\g50\.m2\repository\org\eclipse\equinox\common\maven-metadata-central.xml
is invalid: attribute value must start with quotation or apostrophe not C
(position: TEXT seen <html><head>\n<meta http-equiv=C... @2:19)
------------------------------------------------------------------------
BUILD FAILURE
------------------------------------------------------------------------
Total time: 1.798s
Finished at: Mon Feb 06 17:37:22 GMT+01:00 2017
Final Memory: 6M/15M
------------------------------------------------------------------------
Failed to execute goal on project protege.plugin.owlchanges: Could not
resolve dependencies for project
edu.stanford.protege:protege.plugin.owlchanges:bundle:1.0.1-SNAPSHOT:
Failure to find org.eclipse.equinox:common:jar:3.3.0-v20070426 in
https://repository.sonatype.org/content/groups/forge/ was cached in the
local repository, resolution will not be reattempted until the update
interval of sonatype-forge has elapsed or updates are forced -> [Help 1]

To see the full stack trace of the errors, re-run Maven with the -e switch.
Re-run Maven using the -X switch to enable full debug logging.

For more information about the errors and possible solutions, please read
the following articles:
[Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException

--
View this message in context: http://protege-project.136.n4.nabble.com/BUILD-FAILURE-could-not-resolve-depedencies-tp4667439.html
Sent from the Protege Developer mailing list archive at Nabble.com.
_______________________________________________
protege-dev mailing list
[hidden email]
https://mailman.stanford.edu/mailman/listinfo/protege-dev

_______________________________________________
protege-dev mailing list
[hidden email]
https://mailman.stanford.edu/mailman/listinfo/protege-dev

Simon Spero-2

Re: BUILD FAILURE...could not resolve depedencies

In reply to this post by OntoBLW

On Mon, Feb 6, 2017 at 12:08 PM, OntoBLW <[hidden email]> wrote:

------------------------------------------------------------------------
Building OWLChanges 1.0.1-SNAPSHOT
------------------------------------------------------------------------
The metadata
C:\Users\g50\.m2\repository\org\eclipse\equinox\common\maven-metadata-central.xml
is invalid: attribute value must start with quotation or apostrophe not C
(position: TEXT seen <html><head>\n<meta http-equiv=C... @2:19)

Let's break this down: you are attempting to resolve the artifact 'org.eclipse.equinox:common:jar:3.3.0-v20070426'

That breaks down to group: "org.eclipse.equinox", name: "common" , version: "3.3.0-v20070426"

The error message suggests a problem in a fetch from maven central, since the content looks like html.

Had this been the actual maven-metadata.xml file from central, it would have looked like this:

<metadata>
<groupId>org.eclipse.equinox</groupId>
<artifactId>common</artifactId>
<versioning>
<latest>3.6.200-v20130402-1505</latest>
<release>3.6.200-v20130402-1505</release>
<versions>
<version>3.6.200-v20130402-1505</version>
</versions>
<lastUpdated>20131105141827</lastUpdated>
</versioning>
</metadata>

Note that the versions listed here don't include any 3.3.0 version (although the contents do exist). That usually indicates a disfavored version.

his

3.2.0-v20060603/                                   2007-11-27 03:03                    -
3.3.0-v20070426/                                   2007-11-27 03:03                    -
3.6.200-v20130402-1505/                            2014-08-01 09:15                    -
maven-metadata.xml                                 2014-08-01 09:15                  383
maven-metadata.xml.md5                             2014-08-01 09:15                   32
maven-metadata.xml.sha1                            2014-08-01 09:15                   40

This dependency has been part of many different maven groups, with different artifact names .

// https://mvnrepository.com/artifact/org.eclipse.equinox/org.eclipse.equinox.common

compile group: 'org.eclipse.equinox', name: 'org.eclipse.equinox.common', version: '3.6.0.v20100503'

(which is, oddly, older than the version listed above

The current version is 3.8.0

This is available at:

<groupId>org.eclipse.platform</groupId>

<artifactId>org.eclipse.equinox.common</artifactId>

</dependency>

However, the official groupId found in the equinox SDK bundle is "org.eclipse.equinox"

Simon

------------------------------------------------------------------------
Failed to execute goal on project protege.plugin.owlchanges: Could not
resolve dependencies for project
edu.stanford.protege:protege.plugin.owlchanges:bundle:1.0.1-SNAPSHOT:
Failure to find org.eclipse.equinox:common:jar:3.3.0-v20070426 in
https://repository.sonatype.org/content/groups/forge/ was cached in the
local repository, resolution will not be reattempted until the update
interval of sonatype-forge has elapsed or updates are forced -> [Help 1]

To see the full stack trace of the errors, re-run Maven with the -e switch.
Re-run Maven using the -X switch to enable full debug logging.

For more information about the errors and possible solutions, please read
the following articles:
[Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException

--
View this message in context: http://protege-project.136.n4.nabble.com/BUILD-FAILURE-could-not-resolve-depedencies-tp4667439.html
Sent from the Protege Developer mailing list archive at Nabble.com.
_______________________________________________
protege-dev mailing list
[hidden email]
https://mailman.stanford.edu/mailman/listinfo/protege-dev

_______________________________________________
protege-dev mailing list
[hidden email]
https://mailman.stanford.edu/mailman/listinfo/protege-dev

OntoBLW

Re: BUILD FAILURE...could not resolve depedencies

Hi,
Thanks all.
Today, the error disappeared without doing any efforts. Could I do any solution to prevent this failure next time (all my yesterday was spent on just trying resolving this error)?
Thanks in advance.