Amjad, Your development practices are really up to you. We generally recommend developers put edited copies into dspace/modules (just cause it allows you to more easily determine what files you've changed, and manage your modifications separate from the DSpace codebase). But, some developers choose to manage their changes in different ways.
So, you should determine what way works best for you and then use the appropriate build command to meet your needs. - Tim On 6/26/2012 10:26 AM, AMJAD USMAN wrote: > Hi Tim, > Yes absolutely you are right. I am running Quick Build command. And i am > not copying the edited files to modules. > I am making changes in the files and save them. > > By the way if i need customization in submission forms and their > respective pages, where should i put my edited files: > in dspace/modules > > or should i run full build command. > > Regards > amjad > > > > Date: Tue, 26 Jun 2012 10:12:30 -0500 > > From: tdono...@duraspace.org > > To: amjad...@hotmail.com > > CC: heli...@centrum.sk; dspace-tech@lists.sourceforge.net > > Subject: Re: [Dspace-tech] Build error dspace 1.8.2 > > > > Hi Amjad, > > > > I'm guessing here, but it's possible you are running 'mvn package' from > > the wrong location. > > > > Starting in DSpace 1.8.0, there are now two different build options: > > > > 1. Full Build (recompiles *everything*) - run from root [dspace-source] > > directory (In NetBeans the project is named "DSpace Parent Project") > > > > 2. Quick Build (just recompiles Maven Overlays) - run from > > [dspace-source]/dspace/ directory (in NetBeans, the project is named > > "DSpace Assembly & Configuration") > > > > These build options are described in more detail in the Documentation > > at: https://wiki.duraspace.org/display/DSDOC18/Advanced+Customisation > > > > What this all means is that, if you are using the #2 build option (which > > I'm guessing you are), the *only code* that gets recompiled/applied is > > code in the directories under [dspace-source]/dspace/modules/. But, if > > you use the #1 build option, then other changes will be > > recompiled/applied successfully. > > > > The reason for these two build options is that a full build can take a > > long time, so we wanted a way to offer a quick build option and also > > encourage folks to use Maven Overlays to better separate their code > > customizations from out-of-the-box DSpace (again see docs link above for > > more info). > > > > I hope that helps! > > > > - Tim > > > > > > On 6/26/2012 9:49 AM, AMJAD USMAN wrote: > > > Hi Tim, > > > It worked. Thanks for the explanation. > > > > > > one more question: > > > i am trying to customize submission and its workflow. > > > when i modify any thing in source then i do > > > mvn package > > > ant update > > > restart tomcat server > > > > > > but it does not reflect the changes i made in source. > > > > > > can you guide in this regard? > > > > > > regards > > > amjad > > > > > > > Date: Tue, 26 Jun 2012 09:31:28 -0500 > > > > From: tdono...@duraspace.org > > > > To: amjad...@hotmail.com > > > > CC: heli...@centrum.sk; dspace-tech@lists.sourceforge.net > > > > Subject: Re: [Dspace-tech] Build error dspace 1.8.2 > > > > > > > > Hi Amjad, > > > > > > > > Part of the issue here is that, by default, NetBeans will *always* > > > > attempt to check all file license headers (by running 'mvn install' > > > > instead of 'mvn package'). For most developers, you really don't need > > > > this to occur (as DSpace is released with proper license headers). > > > > > > > > So, one way you can fix this is by customizing what the NetBeans > "Build" > > > > option runs, so that it uses "package" *instead* of "install" (and > > > > therefore does not attempt to check any license headers). > > > > > > > > Here's how you can do that in NetBeans: > > > > 1. Right click on the project you are attempting to Build (e.g. > "DSpace > > > > Assembly and Configuration"), and select "Properties" > > > > 2. Go to the "Actions" category on the left > > > > 3. Select the "Build project" action. > > > > 4. In the "Execute goals" change "install" to "package" > > > > 5. Now select the "Clean and Build Project" action > > > > 6. In the "Execute goals" change "clean install" to "clean package" > > > > 7. Finally, select the "Build with Dependencies" action > > > > 8. In the "Execute goals" change "install" to "package" > > > > > > > > Now, for that project, each time you run any of the 3 build commands > > > > (Build, Clean & Build, or Build with Dependencies) NetBeans will > use the > > > > Maven 'package' command instead of the 'install' command. You'd > have to > > > > do this customization for any NetBeans project that you want to build > > > > using those commands. > > > > > > > > As an alternative, you could also create your own custom NetBeans > > > > commands (which can be run across any/all projects) by doing the > > > following: > > > > 1. Right click on *any* project. > > > > 2. Select "Custom -> Goals..." > > > > 3. In the "Goals:" field type "package" > > > > 4. Select "Remember as:" (at bottom) and enter in "Package" (or some > > > > name you will remember) > > > > 5. Click OK > > > > Now, you can right click on any project, and go to "Custom -> > Package" > > > > to run a Maven "package" of that project. > > > > > > > > I hope that helps. > > > > > > > > - Tim > > > > > > > > > > > > On 6/26/2012 2:42 AM, AMJAD USMAN wrote: > > > > > Dear Helix, > > > > > > > > > > I dont know the reason, why it is behaving like this. > > > > > i have checked my jdk, (1.7), maven (3) and also proxy > parameters are > > > > > set according. > > > > > > > > > > When i build it through command prompt, it gives no errors. but it > > > gives > > > > > errors in building through netbeans. > > > > > > > > > > Is there no netbean developer in the community ? > > > > > > > > > > regards > > > > > amjad > > > > > > > > > > > > > > > > From: heli...@centrum.sk > > > > > > Date: Tue, 26 Jun 2012 09:22:38 +0200 > > > > > > Subject: Re: [Dspace-tech] Build error dspace 1.8.2 > > > > > > To: amjad...@hotmail.com > > > > > > CC: dspace-tech@lists.sourceforge.net > > > > > > > > > > > > 1) If this is really a connection issue - try disabling your > firewall > > > > > > to determine if it's the cause; if you're using a proxy to > connect to > > > > > > internet, read this: > > > > > > > > > > > > > > > > > > > > > https://wiki.duraspace.org/display/DSPACE/Set+Maven+Web+Proxy+Server+Settings > > > > > > > > > > > > 2) Is NetBeans set up to use the same JDK as from the command > line? > > > > > > You can check the command-line version by running java -version. > > > > > > > > > > > > Regards, > > > > > > ~~helix84 > > > > > > > > > > > > > > > > > > > ------------------------------------------------------------------------------ > > > > > Live Security Virtual Conference > > > > > Exclusive live event will cover all the ways today's security and > > > > > threat landscape has changed and how IT managers can respond. > > > Discussions > > > > > will include endpoint security, mobile security and the latest in > > > malware > > > > > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > > > > > > > > > > > > > > > > > > > > _______________________________________________ > > > > > DSpace-tech mailing list > > > > > DSpace-tech@lists.sourceforge.net > > > > > https://lists.sourceforge.net/lists/listinfo/dspace-tech > > > > > > > > > > > ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
