[
http://jira.codehaus.org/browse/MEV-550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_111293
]
Carlos Sanchez commented on MEV-550:
------------------------------------
nobody wiped any groovy artifacts, what seems to have happened is that they
added a pom for groovy 1.0 that never had one.
You should NOT have released anything that depends on something without pom as
it can be added later adding new dependencies, that's why you get WARNINGS at
build time
You can still tweak your pom with includes/excludes
> 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
