OFBiz Maven2 Repository is available now.

[Shi Yusen]

I deployed the OFBiz 09.04 jars and sources.jars to
http://maven2.langhua.org/public/ofbiz/

If you find anything wrong or missing, please feedback to me.

Have a nice weekend,

Shi Yusen/Beijing Langhua Ltd.

[Jacques Le Roux]

What would this be helpful for ?
Have you an idea in mind ?

Jacques

From: "Shi Yusen" <[hidden email]>

>I deployed the OFBiz 09.04 jars and sources.jars to
> http://maven2.langhua.org/public/ofbiz/
>
> If you find anything wrong or missing, please feedback to me.
>
> Have a nice weekend,
>
> Shi Yusen/Beijing Langhua Ltd.
>
>

[Ashish Vijaywargiya]

I am also interested to know few details about doing this.
Thanks Shi for taking initiative of this.

--
Ashish

On Fri, May 15, 2009 at 2:24 PM, Jacques Le Roux <
[hidden email]> wrote:

> What would this be helpful for ? Have you an idea in mind ?
>
> Jacques
>
> From: "Shi Yusen" <[hidden email]>
>
>  I deployed the OFBiz 09.04 jars and sources.jars to
>> http://maven2.langhua.org/public/ofbiz/
>>
>> If you find anything wrong or missing, please feedback to me.
>>
>> Have a nice weekend,
>>
>> Shi Yusen/Beijing Langhua Ltd.
>>
>>
>>
>

[Brett]

I'm jumping on this thread to ask some more questions about maven.  We
are looking at maven to help with our custom deployments.  Here are
some of our objectives:

1.  We use ofbiz in all our applications.  We like the component
structure and are not interested in creating specific war and ear
files for our applications (a feature the maven is very good at).

2.  We would like to use the existing ofbiz ant targets to handle all
build and data loading tasks.  In other words, we don't want to
rewrite working solutions or move away from ofbiz standards.

3.  Our applications use various open source projects such as ofbiz,
dojo, and selenium.  We would like to use maven to handle the
dependencies between these projects.  For example, we want our
developers to just type 'mvn install' to get their system setup with
the correct versions of all the software.  We run into problems when
developer A is using version X of ofbiz while another developer is
using version Y.  I believe maven would be good for this kind of task.

4.  We don't change a lot of ofbiz code, but we do change
configuration files (e.g. various ofbiz-component.xml files,
debug.properties, mail server settings, etc).  We would like maven to
allow us to change configuration settings more easily.  Currently, we
have to make the changes manually which takes time and is error prone.
 We would like to hide these details from the system admins and
developers so all they have to run is some thing like 'mvn install
development'  or 'mvn install production'.

Would maven help us achieve these types of objectives?  We know we
could do the same with ant but it looks like maven would be better
suited for these types of tasks.

Any thoughts on this subject is greatly appreciated.



Brett

On Wed, May 20, 2009 at 7:51 AM, Ashish Vijaywargiya
<[hidden email]> wrote:

> I am also interested to know few details about doing this.
> Thanks Shi for taking initiative of this.
>
> --
> Ashish
>
> On Fri, May 15, 2009 at 2:24 PM, Jacques Le Roux <
> [hidden email]> wrote:
>
>> What would this be helpful for ? Have you an idea in mind ?
>>
>> Jacques
>>
>> From: "Shi Yusen" <[hidden email]>
>>
>>  I deployed the OFBiz 09.04 jars and sources.jars to
>>> http://maven2.langhua.org/public/ofbiz/
>>>
>>> If you find anything wrong or missing, please feedback to me.
>>>
>>> Have a nice weekend,
>>>
>>> Shi Yusen/Beijing Langhua Ltd.
>>>
>>>
>>>
>>
>

[Jacopo Cappellato-4]

Hi Brett,

On May 20, 2009, at 4:56 PM, Brett Palmer wrote:

> 4.  We don't change a lot of ofbiz code, but we do change
> configuration files (e.g. various ofbiz-component.xml files,
> debug.properties, mail server settings, etc).  We would like maven to
> allow us to change configuration settings more easily.  Currently, we
> have to make the changes manually which takes time and is error prone.
> We would like to hide these details from the system admins and
> developers so all they have to run is some thing like 'mvn install
> development'  or 'mvn install production'.

I'd suggest you to have a look at the ant targets with names *-ofbiz-
patches: they are useful to manage (create/apply/revert) patches for  
changes to the standard components (applications and framework), e.g.  
changes to configuration files
we have also recently added similar ant tasks to the build file for  
the hot-deploy component that is automatically created when you run  
the "create-component" target.
All this stuff is intended to help following this strategy for OFBiz  
customizations:

1) instead of changing code in the standard OFBiz distribution, create  
your own hot-deploy component and use it to override/extend the  
applications (ui), services, entities
2) when you really need to change the standard code (ideally this  
should be limited to config files), then follow this approach:
2.a) do the changes
2.b) create a patch file (using the proper ant target) and save it in  
your custom component
2.c) everytime you rebuild your custom component, ant will take care  
of reverting the changes (if any) and reapplying the patches

In this way in your project svn you will only commit the custom hot-
deploy component, and you'll get the standard OFBiz from the public svn.

A developer's box could be setup following, for example, these  
directives:

a) check out from OFBiz svn the rev. 123456 (i.e. one that you have  
choosen for your project) or a realease version
b) check out from your private svn the hot-deploy component inside of  
the hot-deploy folder of OFBiz
c) run "ant run-install" (or similar): when the build script of the  
hot-deploy folder will be executed, the patches will be applied as well

Hope it helps,

Jacopo

[Adam Heath-2]

Shi Yusen wrote:
> I deployed the OFBiz 09.04 jars and sources.jars to
> http://maven2.langhua.org/public/ofbiz/
>
> If you find anything wrong or missing, please feedback to me.
>
> Have a nice weekend,
>
> Shi Yusen/Beijing Langhua Ltd.

Inter-component dependencies are not set anywhere.  So if some
external program just referenced ofbiz-service, they won't get
ofbiz-base, ofbiz-entity, etc.

But other than that, this makes me happy in my special place.  Except
that I don't fully grok maven, but get the gist of it.

[BJ Freeman]

thanks for the tools.
really appreciated.

Jacopo Cappellato sent the following on 5/20/2009 10:54 AM:

> Hi Brett,
>
> On May 20, 2009, at 4:56 PM, Brett Palmer wrote:
>
>> 4.  We don't change a lot of ofbiz code, but we do change
>> configuration files (e.g. various ofbiz-component.xml files,
>> debug.properties, mail server settings, etc).  We would like maven to
>> allow us to change configuration settings more easily.  Currently, we
>> have to make the changes manually which takes time and is error prone.
>> We would like to hide these details from the system admins and
>> developers so all they have to run is some thing like 'mvn install
>> development'  or 'mvn install production'.
>
> I'd suggest you to have a look at the ant targets with names
> *-ofbiz-patches: they are useful to manage (create/apply/revert) patches
> for changes to the standard components (applications and framework),
> e.g. changes to configuration files
> we have also recently added similar ant tasks to the build file for the
> hot-deploy component that is automatically created when you run the
> "create-component" target.
> All this stuff is intended to help following this strategy for OFBiz
> customizations:
>
> 1) instead of changing code in the standard OFBiz distribution, create
> your own hot-deploy component and use it to override/extend the
> applications (ui), services, entities
> 2) when you really need to change the standard code (ideally this should
> be limited to config files), then follow this approach:
> 2.a) do the changes
> 2.b) create a patch file (using the proper ant target) and save it in
> your custom component
> 2.c) everytime you rebuild your custom component, ant will take care of
> reverting the changes (if any) and reapplying the patches
>
> In this way in your project svn you will only commit the custom
> hot-deploy component, and you'll get the standard OFBiz from the public
> svn.
>
> A developer's box could be setup following, for example, these directives:
>
> a) check out from OFBiz svn the rev. 123456 (i.e. one that you have
> choosen for your project) or a realease version
> b) check out from your private svn the hot-deploy component inside of
> the hot-deploy folder of OFBiz
> c) run "ant run-install" (or similar): when the build script of the
> hot-deploy folder will be executed, the patches will be applied as well
>
> Hope it helps,
>
> Jacopo

--
BJ Freeman
http://www.businessesnetwork.com/automation
http://bjfreeman.elance.com
http://www.linkedin.com/profile?viewProfile=&key=1237480&locale=en_US&trk=tab_pro
Systems Integrator.

[Jacques Le Roux]

Yes thanks Jacopo to share,

And more than a tool : a philosophy. Outside of this way are all the problems...

Jacques

From: "BJ Freeman" <[hidden email]>

> thanks for the tools.
> really appreciated.
>
> Jacopo Cappellato sent the following on 5/20/2009 10:54 AM:
>> Hi Brett,
>>
>> On May 20, 2009, at 4:56 PM, Brett Palmer wrote:
>>
>>> 4.  We don't change a lot of ofbiz code, but we do change
>>> configuration files (e.g. various ofbiz-component.xml files,
>>> debug.properties, mail server settings, etc).  We would like maven to
>>> allow us to change configuration settings more easily.  Currently, we
>>> have to make the changes manually which takes time and is error prone.
>>> We would like to hide these details from the system admins and
>>> developers so all they have to run is some thing like 'mvn install
>>> development'  or 'mvn install production'.
>>
>> I'd suggest you to have a look at the ant targets with names
>> *-ofbiz-patches: they are useful to manage (create/apply/revert) patches
>> for changes to the standard components (applications and framework),
>> e.g. changes to configuration files
>> we have also recently added similar ant tasks to the build file for the
>> hot-deploy component that is automatically created when you run the
>> "create-component" target.
>> All this stuff is intended to help following this strategy for OFBiz
>> customizations:
>>
>> 1) instead of changing code in the standard OFBiz distribution, create
>> your own hot-deploy component and use it to override/extend the
>> applications (ui), services, entities
>> 2) when you really need to change the standard code (ideally this should
>> be limited to config files), then follow this approach:
>> 2.a) do the changes
>> 2.b) create a patch file (using the proper ant target) and save it in
>> your custom component
>> 2.c) everytime you rebuild your custom component, ant will take care of
>> reverting the changes (if any) and reapplying the patches
>>
>> In this way in your project svn you will only commit the custom
>> hot-deploy component, and you'll get the standard OFBiz from the public
>> svn.
>>
>> A developer's box could be setup following, for example, these directives:
>>
>> a) check out from OFBiz svn the rev. 123456 (i.e. one that you have
>> choosen for your project) or a realease version
>> b) check out from your private svn the hot-deploy component inside of
>> the hot-deploy folder of OFBiz
>> c) run "ant run-install" (or similar): when the build script of the
>> hot-deploy folder will be executed, the patches will be applied as well
>>
>> Hope it helps,
>>
>> Jacopo
>
> --
> BJ Freeman
> http://www.businessesnetwork.com/automation
> http://bjfreeman.elance.com
> http://www.linkedin.com/profile?viewProfile=&key=1237480&locale=en_US&trk=tab_pro
> Systems Integrator.
>

[Jacques Le Roux]

From: "Adam Heath" <[hidden email]>

> Shi Yusen wrote:
>> I deployed the OFBiz 09.04 jars and sources.jars to
>> http://maven2.langhua.org/public/ofbiz/
>>
>> If you find anything wrong or missing, please feedback to me.
>>
>> Have a nice weekend,
>>
>> Shi Yusen/Beijing Langhua Ltd.
>
> Inter-component dependencies are not set anywhere.  So if some
> external program just referenced ofbiz-service, they won't get
> ofbiz-base, ofbiz-entity, etc.
>
> But other than that, this makes me happy in my special place.  Except
> that I don't fully grok maven, but get the gist of it.

And Shi was asking for a foreigners's understandable english
Actually I like it, and I have learned some slang since I follow this ML  :D

Jacques

[Ashish Vijaywargiya]

 >> And Shi was asking for a foreigners's understandable english
>> Actually I like it, and I have learned some slang since I follow this ML
 :D

:-)

--
Ashish


On Thu, May 21, 2009 at 3:35 AM, Jacques Le Roux <
[hidden email]> wrote:

> From: "Adam Heath" <[hidden email]>
>
>  Shi Yusen wrote:
>>
>>> I deployed the OFBiz 09.04 jars and sources.jars to
>>> http://maven2.langhua.org/public/ofbiz/
>>>
>>> If you find anything wrong or missing, please feedback to me.
>>>
>>> Have a nice weekend,
>>>
>>> Shi Yusen/Beijing Langhua Ltd.
>>>
>>
>> Inter-component dependencies are not set anywhere.  So if some
>> external program just referenced ofbiz-service, they won't get
>> ofbiz-base, ofbiz-entity, etc.
>>
>> But other than that, this makes me happy in my special place.  Except
>> that I don't fully grok maven, but get the gist of it.
>>
>
> And Shi was asking for a foreigners's understandable english
> Actually I like it, and I have learned some slang since I follow this ML
>  :D
>
> Jacques
>
>
>

[Brett]

Jacopo,

Thanks for the tips.

Brett

On Wed, May 20, 2009 at 11:54 AM, Jacopo Cappellato
<[hidden email]> wrote:

> Hi Brett,
>
> On May 20, 2009, at 4:56 PM, Brett Palmer wrote:
>
>> 4.  We don't change a lot of ofbiz code, but we do change
>> configuration files (e.g. various ofbiz-component.xml files,
>> debug.properties, mail server settings, etc).  We would like maven to
>> allow us to change configuration settings more easily.  Currently, we
>> have to make the changes manually which takes time and is error prone.
>> We would like to hide these details from the system admins and
>> developers so all they have to run is some thing like 'mvn install
>> development'  or 'mvn install production'.
>
> I'd suggest you to have a look at the ant targets with names
> *-ofbiz-patches: they are useful to manage (create/apply/revert) patches for
> changes to the standard components (applications and framework), e.g.
> changes to configuration files
> we have also recently added similar ant tasks to the build file for the
> hot-deploy component that is automatically created when you run the
> "create-component" target.
> All this stuff is intended to help following this strategy for OFBiz
> customizations:
>
> 1) instead of changing code in the standard OFBiz distribution, create your
> own hot-deploy component and use it to override/extend the applications
> (ui), services, entities
> 2) when you really need to change the standard code (ideally this should be
> limited to config files), then follow this approach:
> 2.a) do the changes
> 2.b) create a patch file (using the proper ant target) and save it in your
> custom component
> 2.c) everytime you rebuild your custom component, ant will take care of
> reverting the changes (if any) and reapplying the patches
>
> In this way in your project svn you will only commit the custom hot-deploy
> component, and you'll get the standard OFBiz from the public svn.
>
> A developer's box could be setup following, for example, these directives:
>
> a) check out from OFBiz svn the rev. 123456 (i.e. one that you have choosen
> for your project) or a realease version
> b) check out from your private svn the hot-deploy component inside of the
> hot-deploy folder of OFBiz
> c) run "ant run-install" (or similar): when the build script of the
> hot-deploy folder will be executed, the patches will be applied as well
>
> Hope it helps,
>
> Jacopo

[Shi Yusen]

Thanks Jacques!

I really puzzled on the meaning of "grok" and "gist".

Why maven?
Currently, our requirements on deliveries between two positions are
vague. I think maven is the right tool to support our new development
procedure. Ant too can do it, but this is not ant born for.

Here is the desired procedure after maven introduced:
For component designers:
I plan to develop a OFBiz-maven plugin in this year or next year to make
ofbiz component development more productively. A designer can create an
OFBiz project and input the release version, then typical files such as
pom.xml, ofbiz-component.xml are ready. And then he/she can create some
interface java files and entity definitions, upload the project to svn.

Currently we use typical component projects for OFBiz 4.0 and OFBiz
09.04.


For programmers:
Download a project from svn and continue the development or fix bugs,
build snapshot jars and war, upload them to maven snapshot repository.


For SQAs:
Download a snapshot war from maven snapshot repository and deploy it in
hot-deploy, check results and typical UI.

Release sources-jars, jars and war in maven release repository.


For deployers:
Download wars from maven release repository and deploy them in customers
environments.


Regards,

Shi Yusen/Beijing Langhua Ltd.



在 2009-05-21四的 00:05 +0200，Jacques Le Roux写道：

> From: "Adam Heath" <[hidden email]>
> > Shi Yusen wrote:
> >> I deployed the OFBiz 09.04 jars and sources.jars to
> >> http://maven2.langhua.org/public/ofbiz/
> >>
> >> If you find anything wrong or missing, please feedback to me.
> >>
> >> Have a nice weekend,
> >>
> >> Shi Yusen/Beijing Langhua Ltd.
> >
> > Inter-component dependencies are not set anywhere.  So if some
> > external program just referenced ofbiz-service, they won't get
> > ofbiz-base, ofbiz-entity, etc.
> >
> > But other than that, this makes me happy in my special place.  Except
> > that I don't fully grok maven, but get the gist of it.
>
> And Shi was asking for a foreigners's understandable english
> Actually I like it, and I have learned some slang since I follow this ML  :D
>
> Jacques
>
>