to
figure a way to use a remote file)
Regards,
P.K.
On Wednesday, October 26, 2016 at 4:19:54 PM UTC+3, Pantelis Karamolegkos
wrote:
>
> When performing an ant update after an mvn clean install, the following
> error appears during execution of the test_database target
>
>
also?
Thanks,
P.K.
why is that?
On Wednesday, October 26, 2016 at 4:19:54 PM UTC+3, Pantelis Karamolegkos
wrote:
>
> When performing an ant update after an mvn clean install, the following
> error appears during execution of the test_database target
>
>
The same error seems to prevent a proper tomcat8 restart.
On Wednesday, October 26, 2016 at 4:19:54 PM UTC+3, Pantelis Karamolegkos
wrote:
>
> When performing an ant update after an mvn clean install, the following
> error appears during execution of the test_database target
>
>
When performing an ant update after an mvn clean install, the following
error appears during execution of the test_database target
[java] Caused by: org.springframework.beans.factory.BeanCreationException:
Error creating bean with name
Thanks Claudia.
In any case we are not considering about removing any of the existing
schemas, just adding a (couple of) new one(s).
Best,
Pantelis
On Wednesday, October 19, 2016 at 3:23:10 PM UTC+3, Pantelis Karamolegkos
wrote:
>
> In order to declare and use a new metadata schema
If a previously added field needs to be removed, what is the recommended
way to remove it from the database?
(I assume either way it has to be removed from input-forms.xml)
On Friday, July 8, 2016 at 5:07:17 PM UTC+3, Pantelis Karamolegkos wrote:
>
> When adding a new metadata field t
In my case I carried out the first 2 steps, and the field was indeed
added...I just wanted to know how the db migration will take place so
someone who checks out my code has the new field in his db instance)
Thanks,
P.K.
On Friday, July 8, 2016 at 5:07:17 PM UTC+3, Pantelis Karamolegkos wrote:
>
When adding a new metadata field through the respective admin form (in an
existing schema. e.g. dc), do we also have to manually add the respective
flyway migration script under org.dspace.storage.sqlmigration. ?
Otherwise how will the new field be added to the database of someone who
checks
ten caused us to hit the Travis
> CI memory usage limit (at which point Travis *kills* your tests, and they
> all result in failures). Splitting them up helps us remain under that
> limit.
>
> - Tim
>
> On 6/30/2016 5:49 AM, Pantelis Karamolegkos wrote:
>
> In the .travis.
After successful build, when changing directory to
[dspace-src]/dspace/target/dspace-installer and executing ant
test_database, I get the following error which I am unable to understand.
https://gist.github.com/anonymous/3e5b5a52b32ea1698dc6d39015a93294
Any suggestions?
Many thanks,
P.K.
--
PM UTC+3, Pantelis Karamolegkos wrote:
>
> Assuming someone wants to fork and proceed with heavy DSpace
> customization, what is the recommended testing strategy?
> i.e. which of the tests should be kept in a CI environment like travis?
> (apart from our own custom tests we may set
UTC+3, Pantelis Karamolegkos wrote:
>
> When trying to upload a file (i.e. in the 'Upload' step) I get the
> following error:
>
> https://gist.github.com/pkaramol/ba72dc37541114b31d13397057153498
>
> any suggestions?
>
--
You received this message because you are subscri
I forgot to mention that I am using the latest build as it comes out of the
master branch.
(working on Ubuntu 14.04 with Tomcat 8.0.23 and Postgresql 9.5)
On Tuesday, June 14, 2016 at 2:51:23 PM UTC+3, Pantelis Karamolegkos wrote:
>
> When trying to upload a file (i.e. in the 'Upload' s
When trying to upload a file (i.e. in the 'Upload' step) I get the
following error:
https://gist.github.com/pkaramol/ba72dc37541114b31d13397057153498
any suggestions?
--
You received this message because you are subscribed to the Google Groups
"DSpace Technical Support" group.
To unsubscribe
Assuming someone wants to fork and proceed with heavy DSpace customization,
what is the recommended testing strategy?
i.e. which of the tests should be kept in a CI environment like travis?
(apart from our own custom tests we may set up)
(note: 99% of the customization will most likely take
Came across this link:
https://wiki.duraspace.org/display/DSDOC3x/Rebuild+DSpace
There seem to be specific instructions for versions =< 3.
What is the case for versions 4, 5 and 6?
Does the above link (for v3) apply to them as well?
--
You received this message because you are subscribed to the
DSpace6 based on checkout from the master branch, on Ubuntu 16.04, using
Tomcat8 and Java8.
On a fresh install, after creating admin account, the following exception
appears on the dspace.log when hitting the 'Upload a logo ' button while
trying to add a 'top level community)
Admin Home Page
it explicitly in the value of the
allow parameter of the Valve element which now looks sth like this
On Tuesday, May 24, 2016 at 6:01:29 PM UTC+3, Pantelis Karamolegkos wrote:
>
> I just installed dspace from the master branch source.
> I am however getting an "Internal System Error&q
:59 PM UTC+3, Pantelis Karamolegkos wrote:
>
> After running fresh_install, a file literally named ${log.dir} is created
> in dspace_installer folder.
> It seems no parameter substitution takes place when running the ant target.
> Where are the folder names taken from, i.e. ${
Resolved it was an issue of failed installation of pgcrypto.
On Sunday, May 22, 2016 at 6:59:05 PM UTC+3, Pantelis Karamolegkos wrote:
>
> The above target fails with the following output:
>
> [java] 2016-05-22 18:56:33,108 INFO
> org.dspace.services.caching.CachingServic
also had to manually create the log dir in the above path and also
grant rwx permissions to tomcat8 user (via setfacl)
On Sunday, May 22, 2016 at 6:53:59 PM UTC+3, Pantelis Karamolegkos wrote:
>
> After running fresh_install, a file literally named ${log.dir} is created
> in dspace_
On Sunday, May 22, 2016 at 6:53:59 PM UTC+3, Pantelis Karamolegkos wrote:
>
> After running fresh_install, a *folder* literally named ${log.dir} is
> created in dspace_installer folder.
> It seems no parameter substitution takes place when running the ant target.
> Where are t
The above target fails with the following output:
[java] 2016-05-22 18:56:33,108 INFO
org.dspace.services.caching.CachingServiceImpl @ destroy()
[java] 2016-05-22 18:56:33,109 INFO
org.springframework.cache.ehcache.EhCacheManagerFactoryBean @ Shutting
down EhCache CacheManager
23 matches
Mail list logo
