On Wed, Dec 21, 2011 at 4:29 PM, Vijayaratha Vijayasingam
<rat...@wso2.com>wrote:
> My trunk root pom defines "securevault.version" as;
>
> <securevault.version>1.0.0</securevault.version>
>
> and my trunk/dependencies/securevault contains
> "org.wso2.securevault-1.0.0.jar"..hope then version is right..but
> service-stub build fails..(online offline both)
> -ratha
>
>
Then, may be it's an issue in your M2 repo. Can you go to the relevant
location of securevault in your repo, and remove unnecessary files (like
*lastUpdated, resolver_status.properties etc.), and retry? That has been
bugging me as well last week for another artifact.
I confirm AmilaM. I also don't see securevault dep in the said pom.
--KasunG
>
> On 21 December 2011 16:26, Amila Maha Arachchi <ami...@wso2.com> wrote:
>
>> Hi Ratha,
>>
>> this builds fine for me. I dont see any dependencies defined for
>> secure.vault in this service stub pom.
>>
>> AmilaM.
>>
>> On Wed, Dec 21, 2011 at 4:02 PM, Vijayaratha Vijayasingam <
>> rat...@wso2.com> wrote:
>>
>>> Hi,
>>> Im getting following issue..
>>> [INFO]
>>> ------------------------------------------------------------------------
>>> [INFO] BUILD FAILURE
>>> [INFO]
>>> ------------------------------------------------------------------------
>>> [INFO] Total time: 3.625s
>>> [INFO] Finished at: Wed Dec 21 16:01:15 IST 2011
>>> [INFO] Final Memory: 20M/247M
>>> [INFO]
>>> ------------------------------------------------------------------------
>>> [ERROR] Failed to execute goal on project
>>> org.wso2.carbon.stratos.common.stub: Could not resolve dependencies for
>>> project org.wso2.carbon:org.wso2.car
>>> bon.stratos.common.stub:bundle:3.2.0-SNAPSHOT: Failure to find
>>> org.wso2.securevault:org.wso2.securevault:jar:${securevault.version} in
>>> http://maven.ws
>>> o2.org/nexus/content/groups/wso2-public/ was cached in the local
>>> repository, resolution will not be reattempted until the update interval of
>>> wso2-nexu
>>> s has elapsed or updates are forced -> [Help 1]
>>> [ERROR]
>>> [ERROR] To see the full stack trace of the errors, re-run Maven with the
>>> -e switch.
>>> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
>>> [ERROR]
>>> [ERROR] For more information about the errors and possible solutions,
>>> please read the following articles:
>>>
>>> Where should i check? i took up today
>>>
>>> -ratha
>>>
>>>
>>> _______________________________________________
>>> Carbon-dev mailing list
>>> Carbon-dev@wso2.org
>>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>>
>>>
>>
>>
>> --
>> *Amila Maharachchi*
>> Senior Software Engineer; WSO2, Inc.; http://wso2.com
>>
>> Blog: http://maharachchi.blogspot.com
>> Mobile: +94719371446
>>
>>
>>
>> _______________________________________________
>> Carbon-dev mailing list
>> Carbon-dev@wso2.org
>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>>
>>
>
> _______________________________________________
> Carbon-dev mailing list
> Carbon-dev@wso2.org
> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
>
>
--
*Kasun Gajasinghe*
Software Engineer; WSO2 Inc.; http://wso2.com
,
*email: **kasung AT spamfree wso2.com** cell: **+94 (77) 678-0813*
*blog: **http://blog.kasunbg.org* <http://blog.kasunbg.org>
*
twitter: **http://twitter.com/kasunbg* <http://twitter.com/kasunbg>
*
*
_______________________________________________
Carbon-dev mailing list
Carbon-dev@wso2.org
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
