Re: Maven (was: WO 5.4 Linux Deployment)
Re: Maven (was: WO 5.4 Linux Deployment)
- Subject: Re: Maven (was: WO 5.4 Linux Deployment)
- From: Jake MacMullin <email@hidden>
- Date: Tue, 25 Mar 2008 23:02:32 -0700
I guess this would work. A Maven repository is just a network-addressable (scp / http / etc) collection of directories and files - so I can't see any technical reason these files can't be in your subversion repository (I'm assuming you have http access to it?)
Cheers,
Jake
On Tuesday, March 25, 2008, at 10:49PM, "Lachlan Deck" <email@hidden> wrote:
>Hi again,
>
>On 26/03/2008, at 4:24 PM, Jake MacMullin wrote:
>> Ok - I think I know what you mean about a 'shared environment'. I
>> think the easiest way to handle this (if I understand what you're
>> trying to achieve) is to list the repositories you want to use in
>> your projects' poms and make sure they are visible to anyone who
>> needs to build the application.
>>
>> For example, we've got an internal repository at the BBC containing
>> the WebObjects jars and some other libraries needed to build our
>> applications and the parent-pom for our projects references this
>> repository. This way we just check the pom.xml in to our source
>> control and for a developer to build our WO applications on a new
>> machine all they need to do is make sure Java and Maven are
>> installed, then check out the source code and execute the 'mvn
>> package' goal.
>
>Sure. But apart from having svn/maven/java I was hoping to avoid, if
>possible, requiring that an internal repository be set up on our
>network. That might prove to be a harder barrow to push ;-)
>
>So, if it's possible to have a repository sitting within the svn
>source-code (e.g., trunk/mvn-repo) then this could possibly work?
>
>Of course the other thing that needs to work is WOLips/Entity Modeler
>when linked to jars. e.g.,
>http://issues.objectstyle.org/jira/browse/WOL-762
>
>> Maven will then download the WO jars (and other libraries) from our
>> local Maven repository.
>>
>> As for your other question about how to handle WOComponents,
>> EOModels etc. when building a WO framework as a jar, it is really
>> quite simple. As I said I just use the standard Maven 'package'
>> goal. There are only really two 'special' things you need to do to
>> make sure WebObjects recognises the .jar as a framework:
>>
>> 1. WebObjects expects to find any resources (Components, EOModels
>> etc) in a directory at the top level of the .jar called
>> 'Resources' (note the capital 'R'). Maven will merge anything
>> contained in '/src/main/resources' (note the lowercase 'r') to the
>> top of the .jar (along-side the complied classes) - so to get Maven
>> to do the right thing, put your resources in '/src/main/resources/
>> Resources'.
>>
>> 2. WebObjects expects to find an Info.plist - so make sure to
>> include one (just copy one from an existing framework project) in
>> the 'Resources' directory.
>>
>> That's it. If you build a .jar in this way it magically becomes a
>> 'framework' as far as WebObjects is concerned.
>
>Okay great. Thanks for that.
>
>with regards,
>--
>
>Lachlan Deck
>
>
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden