Re: svn commit: r664427 - /ofbiz/trunk/applications/humanres/build.xml

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
5 messages Options
Reply | Threaded
Open this post in threaded view
|

Re: svn commit: r664427 - /ofbiz/trunk/applications/humanres/build.xml

Jacques Le Roux
Administrator
Impressive, I did not notice that. Any java file in Humanres ! Proof that the Framework is really mature (if a proof was needed) or
that Humanres still need some work ? :o)

Jacques

> Author: ruppert
> Date: Sat Jun  7 20:39:32 2008
> New Revision: 664427
>
> URL: http://svn.apache.org/viewvc?rev=664427&view=rev
> Log:
> Removed the building of the humanres javadoc since there are no java files at this point and it's causing a build error during
> generation
>
> Modified:
>    ofbiz/trunk/applications/humanres/build.xml
>
> Modified: ofbiz/trunk/applications/humanres/build.xml
> URL: http://svn.apache.org/viewvc/ofbiz/trunk/applications/humanres/build.xml?rev=664427&r1=664426&r2=664427&view=diff
> ==============================================================================
> --- ofbiz/trunk/applications/humanres/build.xml (original)
> +++ ofbiz/trunk/applications/humanres/build.xml Sat Jun  7 20:39:32 2008
> @@ -108,12 +108,15 @@
>     <!-- ================================================================== -->
>
>     <target name="docs" depends="prepare-docs,classpath">
> +        <!-- Commented out since there are no java files in this package at this time -->
> +        <!--
>         <javadoc packagenames="org.ofbiz.humanres.*"
>                  classpathref="local.class.path"
>                  destdir="${build.dir}/javadocs"
>                  Windowtitle="Open for Business - ${desc}">
>             <sourcepath path="${src.dir}"/>
>         </javadoc>
> +        -->
>     </target>
>
>     <target name="all" depends="jar,docs"/>
>
>

Reply | Threaded
Open this post in threaded view
|

Re: svn commit: r664427 - /ofbiz/trunk/applications/humanres/build.xml

Ashish Vijaywargiya
Jacques,

I am thinking to integrate following components  in HR module :-

WorkEffort (For Task and Time Sheet management of Employee)
Contentmgr (For content management like Resume , Training)
Report Module :- I am thinking what kind of reports can be of help in HR
(Some of them are in my mind are like Part Time Employee , Full Time
Employee , Manager etc).
It may happen that some Java files may come up in picture while working with
Reports.

When all above things will be finalized in my mind then I will write down
some writeup's on JIRA issue then we can start working on that.
If somebody has good thoughts in their mind for the above topic then I
request them to share those thoughts :-)

--
Ashish


On Sun, Jun 8, 2008 at 5:26 AM, Jacques Le Roux <
[hidden email]> wrote:

> Impressive, I did not notice that. Any java file in Humanres ! Proof that
> the Framework is really mature (if a proof was needed) or that Humanres
> still need some work ? :o)
>
> Jacques
>
>
>  Author: ruppert
>> Date: Sat Jun  7 20:39:32 2008
>> New Revision: 664427
>>
>> URL: http://svn.apache.org/viewvc?rev=664427&view=rev
>> Log:
>> Removed the building of the humanres javadoc since there are no java files
>> at this point and it's causing a build error during generation
>>
>> Modified:
>>   ofbiz/trunk/applications/humanres/build.xml
>>
>> Modified: ofbiz/trunk/applications/humanres/build.xml
>> URL:
>> http://svn.apache.org/viewvc/ofbiz/trunk/applications/humanres/build.xml?rev=664427&r1=664426&r2=664427&view=diff
>>
>> ==============================================================================
>> --- ofbiz/trunk/applications/humanres/build.xml (original)
>> +++ ofbiz/trunk/applications/humanres/build.xml Sat Jun  7 20:39:32 2008
>> @@ -108,12 +108,15 @@
>>    <!-- ==================================================================
>> -->
>>
>>    <target name="docs" depends="prepare-docs,classpath">
>> +        <!-- Commented out since there are no java files in this package
>> at this time -->
>> +        <!--
>>        <javadoc packagenames="org.ofbiz.humanres.*"
>>                 classpathref="local.class.path"
>>                 destdir="${build.dir}/javadocs"
>>                 Windowtitle="Open for Business - ${desc}">
>>            <sourcepath path="${src.dir}"/>
>>        </javadoc>
>> +        -->
>>    </target>
>>
>>    <target name="all" depends="jar,docs"/>
>>
>>
>>
>
Reply | Threaded
Open this post in threaded view
|

HR Application (was Re: svn commit: r664427 - /ofbiz/trunk/applications/humanres/build.xml)

David E Jones

Ashish,

When considering what to put in the HR application please keep in mind  
the general pattern for the OFBiz base applications: they are meant to  
be generic user interfaces that are mostly organized around the data  
and not around a process or role and with minimal redundancy around  
that data. The specialpurpose components are more for applications  
that are meant for a certain role or process, and in many cases the  
point of using OFBiz is to start with these generic application  
artifacts (entities, services, screens, forms, etc) and reuse them to  
create applications organized around business processes and roles/
actors in those processes to more directly address the needs of a  
given business.

For the HR application that means have it stick to HR stuff, and not  
try to duplicate or even reuse functionality in the WorkEffort  
application. For plain base application use if someone wants to track  
time or tasks or calendar events, then they should hop over to the  
WorkEffort app, and then if they want to do more with positions and  
skills and so on they should hop back to the HR app.

For Content stuff the general content functionality is in the Content  
Manager, but if you want to have content associated with a particular  
entity in HR then having a quick upload form or something that does  
that, perhaps along with a link to the actual content screen in the  
content manager, might be a good way to go (basically what we do with  
the ProductContent stuff in the Catalog Manager).

-David


On Jun 9, 2008, at 12:41 AM, Ashish Vijaywargiya wrote:

> Jacques,
>
> I am thinking to integrate following components  in HR module :-
>
> WorkEffort (For Task and Time Sheet management of Employee)
> Contentmgr (For content management like Resume , Training)
> Report Module :- I am thinking what kind of reports can be of help  
> in HR
> (Some of them are in my mind are like Part Time Employee , Full Time
> Employee , Manager etc).
> It may happen that some Java files may come up in picture while  
> working with
> Reports.
>
> When all above things will be finalized in my mind then I will write  
> down
> some writeup's on JIRA issue then we can start working on that.
> If somebody has good thoughts in their mind for the above topic then I
> request them to share those thoughts :-)
>
> --
> Ashish
>
>
> On Sun, Jun 8, 2008 at 5:26 AM, Jacques Le Roux <
> [hidden email]> wrote:
>
>> Impressive, I did not notice that. Any java file in Humanres !  
>> Proof that
>> the Framework is really mature (if a proof was needed) or that  
>> Humanres
>> still need some work ? :o)
>>
>> Jacques
>>
>>
>> Author: ruppert
>>> Date: Sat Jun  7 20:39:32 2008
>>> New Revision: 664427
>>>
>>> URL: http://svn.apache.org/viewvc?rev=664427&view=rev
>>> Log:
>>> Removed the building of the humanres javadoc since there are no  
>>> java files
>>> at this point and it's causing a build error during generation
>>>
>>> Modified:
>>> ofbiz/trunk/applications/humanres/build.xml
>>>
>>> Modified: ofbiz/trunk/applications/humanres/build.xml
>>> URL:
>>> http://svn.apache.org/viewvc/ofbiz/trunk/applications/humanres/build.xml?rev=664427&r1=664426&r2=664427&view=diff
>>>
>>> =
>>> =
>>> =
>>> =
>>> =
>>> =
>>> =
>>> =
>>> =
>>> =
>>> ====================================================================
>>> --- ofbiz/trunk/applications/humanres/build.xml (original)
>>> +++ ofbiz/trunk/applications/humanres/build.xml Sat Jun  7  
>>> 20:39:32 2008
>>> @@ -108,12 +108,15 @@
>>>  <!--  
>>> ==================================================================
>>> -->
>>>
>>>  <target name="docs" depends="prepare-docs,classpath">
>>> +        <!-- Commented out since there are no java files in this  
>>> package
>>> at this time -->
>>> +        <!--
>>>      <javadoc packagenames="org.ofbiz.humanres.*"
>>>               classpathref="local.class.path"
>>>               destdir="${build.dir}/javadocs"
>>>               Windowtitle="Open for Business - ${desc}">
>>>          <sourcepath path="${src.dir}"/>
>>>      </javadoc>
>>> +        -->
>>>  </target>
>>>
>>>  <target name="all" depends="jar,docs"/>
>>>
>>>
>>>
>>

Reply | Threaded
Open this post in threaded view
|

Re: HR Application (was Re: svn commit: r664427 - /ofbiz/trunk/applications/humanres/build.xml)

Jacques Le Roux
Administrator
Ashish, David,

I have not the same assurance than David and I would not have been able to make a such complete reply but that was my filling also
when I 1st wrote your message.
As an OO concept I guess this one is relevant here http://en.wikipedia.org/wiki/Cohesion_%28computer_science%29

Jacques

From: "David E Jones" <[hidden email]>

>
> Ashish,
>
> When considering what to put in the HR application please keep in mind  the general pattern for the OFBiz base applications: they
> are meant to  be generic user interfaces that are mostly organized around the data  and not around a process or role and with
> minimal redundancy around  that data. The specialpurpose components are more for applications  that are meant for a certain role
> or process, and in many cases the  point of using OFBiz is to start with these generic application  artifacts (entities, services,
> screens, forms, etc) and reuse them to  create applications organized around business processes and roles/ actors in those
> processes to more directly address the needs of a  given business.
>
> For the HR application that means have it stick to HR stuff, and not  try to duplicate or even reuse functionality in the
> WorkEffort  application. For plain base application use if someone wants to track  time or tasks or calendar events, then they
> should hop over to the  WorkEffort app, and then if they want to do more with positions and  skills and so on they should hop back
> to the HR app.
>
> For Content stuff the general content functionality is in the Content  Manager, but if you want to have content associated with a
> particular  entity in HR then having a quick upload form or something that does  that, perhaps along with a link to the actual
> content screen in the  content manager, might be a good way to go (basically what we do with  the ProductContent stuff in the
> Catalog Manager).
>
> -David
>
>
> On Jun 9, 2008, at 12:41 AM, Ashish Vijaywargiya wrote:
>
>> Jacques,
>>
>> I am thinking to integrate following components  in HR module :-
>>
>> WorkEffort (For Task and Time Sheet management of Employee)
>> Contentmgr (For content management like Resume , Training)
>> Report Module :- I am thinking what kind of reports can be of help  in HR
>> (Some of them are in my mind are like Part Time Employee , Full Time
>> Employee , Manager etc).
>> It may happen that some Java files may come up in picture while  working with
>> Reports.
>>
>> When all above things will be finalized in my mind then I will write  down
>> some writeup's on JIRA issue then we can start working on that.
>> If somebody has good thoughts in their mind for the above topic then I
>> request them to share those thoughts :-)
>>
>> --
>> Ashish
>>
>>
>> On Sun, Jun 8, 2008 at 5:26 AM, Jacques Le Roux <
>> [hidden email]> wrote:
>>
>>> Impressive, I did not notice that. Any java file in Humanres !  Proof that
>>> the Framework is really mature (if a proof was needed) or that  Humanres
>>> still need some work ? :o)
>>>
>>> Jacques
>>>
>>>
>>> Author: ruppert
>>>> Date: Sat Jun  7 20:39:32 2008
>>>> New Revision: 664427
>>>>
>>>> URL: http://svn.apache.org/viewvc?rev=664427&view=rev
>>>> Log:
>>>> Removed the building of the humanres javadoc since there are no  java files
>>>> at this point and it's causing a build error during generation
>>>>
>>>> Modified:
>>>> ofbiz/trunk/applications/humanres/build.xml
>>>>
>>>> Modified: ofbiz/trunk/applications/humanres/build.xml
>>>> URL:
>>>> http://svn.apache.org/viewvc/ofbiz/trunk/applications/humanres/build.xml?rev=664427&r1=664426&r2=664427&view=diff
>>>>
>>>> = = = = = = = = = = ====================================================================
>>>> --- ofbiz/trunk/applications/humanres/build.xml (original)
>>>> +++ ofbiz/trunk/applications/humanres/build.xml Sat Jun  7  20:39:32 2008
>>>> @@ -108,12 +108,15 @@
>>>>  <!--  ==================================================================
>>>> -->
>>>>
>>>>  <target name="docs" depends="prepare-docs,classpath">
>>>> +        <!-- Commented out since there are no java files in this  package
>>>> at this time -->
>>>> +        <!--
>>>>      <javadoc packagenames="org.ofbiz.humanres.*"
>>>>               classpathref="local.class.path"
>>>>               destdir="${build.dir}/javadocs"
>>>>               Windowtitle="Open for Business - ${desc}">
>>>>          <sourcepath path="${src.dir}"/>
>>>>      </javadoc>
>>>> +        -->
>>>>  </target>
>>>>
>>>>  <target name="all" depends="jar,docs"/>
>>>>
>>>>
>>>>
>>>
>

Reply | Threaded
Open this post in threaded view
|

Re: HR Application (was Re: svn commit: r664427 - /ofbiz/trunk/applications/humanres/build.xml)

Ashish Vijaywargiya
In reply to this post by David E Jones
David,

Thanks for the useful guidelines.
I will keep those things in my mind.

--
Ashish


On Mon, Jun 9, 2008 at 11:03 AM, David E Jones <[hidden email]>
wrote:

>
> Ashish,
>
> When considering what to put in the HR application please keep in mind the
> general pattern for the OFBiz base applications: they are meant to be
> generic user interfaces that are mostly organized around the data and not
> around a process or role and with minimal redundancy around that data. The
> specialpurpose components are more for applications that are meant for a
> certain role or process, and in many cases the point of using OFBiz is to
> start with these generic application artifacts (entities, services, screens,
> forms, etc) and reuse them to create applications organized around business
> processes and roles/actors in those processes to more directly address the
> needs of a given business.
>
> For the HR application that means have it stick to HR stuff, and not try to
> duplicate or even reuse functionality in the WorkEffort application. For
> plain base application use if someone wants to track time or tasks or
> calendar events, then they should hop over to the WorkEffort app, and then
> if they want to do more with positions and skills and so on they should hop
> back to the HR app.
>
> For Content stuff the general content functionality is in the Content
> Manager, but if you want to have content associated with a particular entity
> in HR then having a quick upload form or something that does that, perhaps
> along with a link to the actual content screen in the content manager, might
> be a good way to go (basically what we do with the ProductContent stuff in
> the Catalog Manager).
>
> -David
>
>
> On Jun 9, 2008, at 12:41 AM, Ashish Vijaywargiya wrote:
>
>  Jacques,
>>
>> I am thinking to integrate following components  in HR module :-
>>
>> WorkEffort (For Task and Time Sheet management of Employee)
>> Contentmgr (For content management like Resume , Training)
>> Report Module :- I am thinking what kind of reports can be of help in HR
>> (Some of them are in my mind are like Part Time Employee , Full Time
>> Employee , Manager etc).
>> It may happen that some Java files may come up in picture while working
>> with
>> Reports.
>>
>> When all above things will be finalized in my mind then I will write down
>> some writeup's on JIRA issue then we can start working on that.
>> If somebody has good thoughts in their mind for the above topic then I
>> request them to share those thoughts :-)
>>
>> --
>> Ashish
>>
>>
>> On Sun, Jun 8, 2008 at 5:26 AM, Jacques Le Roux <
>> [hidden email]> wrote:
>>
>>  Impressive, I did not notice that. Any java file in Humanres ! Proof that
>>> the Framework is really mature (if a proof was needed) or that Humanres
>>> still need some work ? :o)
>>>
>>> Jacques
>>>
>>>
>>> Author: ruppert
>>>
>>>> Date: Sat Jun  7 20:39:32 2008
>>>> New Revision: 664427
>>>>
>>>> URL: http://svn.apache.org/viewvc?rev=664427&view=rev
>>>> Log:
>>>> Removed the building of the humanres javadoc since there are no java
>>>> files
>>>> at this point and it's causing a build error during generation
>>>>
>>>> Modified:
>>>> ofbiz/trunk/applications/humanres/build.xml
>>>>
>>>> Modified: ofbiz/trunk/applications/humanres/build.xml
>>>> URL:
>>>>
>>>> http://svn.apache.org/viewvc/ofbiz/trunk/applications/humanres/build.xml?rev=664427&r1=664426&r2=664427&view=diff
>>>>
>>>>
>>>> ==============================================================================
>>>> --- ofbiz/trunk/applications/humanres/build.xml (original)
>>>> +++ ofbiz/trunk/applications/humanres/build.xml Sat Jun  7 20:39:32 2008
>>>> @@ -108,12 +108,15 @@
>>>>  <!-- ==================================================================
>>>> -->
>>>>
>>>>  <target name="docs" depends="prepare-docs,classpath">
>>>> +        <!-- Commented out since there are no java files in this
>>>> package
>>>> at this time -->
>>>> +        <!--
>>>>     <javadoc packagenames="org.ofbiz.humanres.*"
>>>>              classpathref="local.class.path"
>>>>              destdir="${build.dir}/javadocs"
>>>>              Windowtitle="Open for Business - ${desc}">
>>>>         <sourcepath path="${src.dir}"/>
>>>>     </javadoc>
>>>> +        -->
>>>>  </target>
>>>>
>>>>  <target name="all" depends="jar,docs"/>
>>>>
>>>>
>>>>
>>>>
>>>
>