The simplest approach is:
1.) yes, your item-submission and other configuration should go under
[dspace-src]/dspace/config
2.) Place your submit code into
[dspace-src]/dspace/modules/jspui/src/main/java/your/package/name/YourStep.java
3.) place your messages.properties in
[dspace-src]/dspace/modules/jspui/src/main/resources/Message.properties
If any of your code needs to be available from cli apps as well, you will want
to make a new module project (for example)
cd [dspace-src]/dspace/modules
mvn archetype:generate -DarchetypeArtifactId=maven-archetype-quickstart
-DarchetypeGroupId=org.apache.maven.archetypes
-DarchetypeGroupId=org.apache.maven.archetypes -DgroupId=org.dspace.modules
-DartifactId=api -Dversion=1.7.1
and add it as a dependency to the other modules like dspace/jspui/pom.xml and
to dspace/pom.xml
<dependencies>
<dependency>
<artifactId>api</artifactId>
<groupId>org.dspace.modules</groupId>
<version>1.7.1</version>
</dependency>
</dependencies>
You may then completely remove the all the [dspace-src]/dspace-xxxxx projects
from your code so that your not having to repeatedly build them every-time you
want to deploy your instance.
Use a tool like Intellij IDEA to manage your project, it will guide validate
the poms and if you follow the IDEA guide you can learn how to debug your
changes on the fly via IDEA and manage your changes to the codebase.
https://wiki.duraspace.org/display/DSPACE/IDE+Integration+-+DSpace+and+IDEA
Best,
Mark Diggory
On May 12, 2011, at 4:09 PM, Wei Li wrote:
> hi,
>
> I am currently adding a step to the submission process to implement an
> additional future on top of DSpace-1.7.1. Currently the way I am doing
> this is very messy, i.e. all my code are mixed with the dspace base
> code, including:
> 1) new classes in dspace-api/submit,
> 2) dspace-jsp-api/submit,
> 3) new jsps in dspace-jsp-webapp,
> 4)some customizations on jspui,
> 5)changes on config/item-submission.xml
> 6)changes on Message.properties
> 7) a couple of new config files in the dspace/config directory .
>
> So I want to have a clean separation of the code(changes) I added and
> the dspace base code so that I can update them independently.
> Therefore, I am wondering how I could accomplish this nicely or
> whether there is a guildline about this.
>
> Thank you very much!
>
> Sincerely,
> Wei
>
> ------------------------------------------------------------------------------
> Achieve unprecedented app performance and reliability
> What every C/C++ and Fortran developer should know.
> Learn how Intel has extended the reach of its next-generation tools
> to help boost performance applications - inlcuding clusters.
> http://p.sf.net/sfu/intel-dev2devmay
> _______________________________________________
> DSpace-tech mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/dspace-tech
------------------------------------------------------------------------------
Achieve unprecedented app performance and reliability
What every C/C++ and Fortran developer should know.
Learn how Intel has extended the reach of its next-generation tools
to help boost performance applications - inlcuding clusters.
http://p.sf.net/sfu/intel-dev2devmay
_______________________________________________
DSpace-tech mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-tech
