[
http://jira.codehaus.org/browse/MEV-550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_111395
]
Paul King commented on MEV-550:
-------------------------------
I will own up to adding the groovy 1.0 pom. I extracted the pom from version
control that we used to build the 1.0 jar and placed that in the correct place
to be sync'd - no new dependencies were added. I presume we received a warning
about the missing dependency when we built the jar at the time.
Having a look at the openejb source history, it looks like they added a
dependency to a non-existing artifact in Sept 2005 and kept that dependency
that way at least for 6 months:
http://fisheye.codehaus.org/changelog/openejb/?cs=2173
I couldn't find evidence that the artifact was deleted but it appears some
snapshot artifacts related to castor possibly were deleted. Perhaps the openejb
project (and maybe even the Groovy project) pointed to an additional snapshot
repository at one point.
Carlos, I would appreciate your advice here. I just "hacked" the Groovy pom to
have an explicit dependency to castor:castor:0.9.9 and the openejb-related
tests work fine. It appears to be the first release they made after the
0.9.9.0-pre SNAPSHOT release. It doesn't feel right to add in this hack though
- it really is openejb:openejb:core that needs this fix. Should we look at
fixing that? Or is there a better solution? Let me know if it needs a separate
issue. Thanks, Paul.
> Missing castor version or incorrect groovy/openejb dependencies
> ---------------------------------------------------------------
>
> Key: MEV-550
> URL: http://jira.codehaus.org/browse/MEV-550
> Project: Maven Evangelism
> Issue Type: Bug
> Components: Dependencies
> Reporter: Nicolas Kyriazopoulos-Panagiotopoulos
>
> We have a problem of dependencies:
> [INFO] Path to dependency:
> [INFO] 1) [OUR PROJECT]
> [INFO] 2) groovy:groovy:jar:1.0
> [INFO] 3) openejb:openejb-loader:jar:1.0
> [INFO] 4) openejb:openejb-core:jar:1.0
> [INFO] 5) castor:castor:jar:0.9.9.0-pre
> The problem is new (we are using groovy for almost a year) . It seems that
> someone very recently erased this version of the castor jar and grovy cannot
> work without it (unless the problem is caused by newly changed poms). Finding
> this particular version of castor on the web seems very difficult.
> This is VERY URGENT: there is no newer stable version of groovy so we have
> no alternative, and the problem makes new application deployments impossible
> (unless we do kung fu with the downloaded poms to refer to other versions,
> which is impractical and dangerous).
> Thanks in advance!
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
