commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bhowmik, Bindul" <bindulbhow...@gmail.com>
Subject [JCS] Re: JCS 2.0 eclipse setup issues
Date Wed, 18 Jan 2017 19:12:34 GMT
Tim,

On Wed, Jan 18, 2017 at 11:55 AM, Tim Cronin <tim@outboundengine.com> wrote:
> I'm running
> eclipse neon.2 4.6.2
> m2e 1.3.1
>
> I've imported as a maven project via svn and did the following to cleanup
> the
> livecycle issues
>
> https://mahichir.wordpress.com/2014/05/14/solving-the-plugin-execution-not-covered-by-lifecycle-configuration-error-in-eclipse/
>
> but now getting the following errors:
>
> Project build error: Non-resolvable parent POM for
> org.apache.commons:commons-jcs-sandbox:[unknown-version]: Could not find
> artifact org.apache.commons:commons-jcs:pom:2.0-SNAPSHOT and
> 'parent.relativePath' points at wrong local POM    pom.xml
> /commons-jcs-filecache    line 1    Maven pom Loading Problem
> Project build error: Non-resolvable parent POM for
> org.apache.commons:commons-jcs-sandbox:[unknown-version]: Could not find
> artifact org.apache.commons:commons-jcs:pom:2.0-SNAPSHOT and
> 'parent.relativePath' points at wrong local POM    pom.xml
> /commons-jcs-sandbox    line 24    Maven pom Loading Problem
> Project build error: Non-resolvable parent POM for
> org.apache.commons:commons-jcs-sandbox:[unknown-version]: Could not find
> artifact org.apache.commons:commons-jcs:pom:2.0-SNAPSHOT and
> 'parent.relativePath' points at wrong local POM    pom.xml
> /commons-jcs-yajcache    line 1    Maven pom Loading Problem

Looking at JCS trunk [1], it looks like a mis-configuration of the
commons-jcs-sandbox module (and its children), the parent version has
not been updated from 2.0-SNAPSHOT to 2.1-SNAPSHOT.

Now, commons-jcs-sandbox is not defined as a module in the parent POM
[2], so, the commons-release-plugin would not have automatically
updated the version when it prepared for the next release.

As I see it, your options at this time are:
1. Exclude that module (and its two children) from your workspace (you
can simply delete the project without deleting it from disk) - that is
unless you are interested in one of those modules.
2. Update the parent version in that module (and its children) to
2.1-SNAPSHOT locally (and perhaps send in a patch).

Someone with commit rights might want to update the parent version in SVN trunk.

Regards,
Bindul

[1] https://svn.apache.org/repos/asf/commons/proper/jcs/trunk/
[2] http://svn.apache.org/viewvc/commons/proper/jcs/tags/commons-jcs-2.0/pom.xml?revision=1776032&view=markup#l145

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org


Mime
View raw message