Hi Mike,
Agreed that its painful at first.
Since 1.2 is about to go out then I'd say for sure that its a bad
time to start this on Cayenne proper.
As has already been said its probably best to use m2 on something new
to start with like JPA.
I'll try to get a patch together RSN so anyone that is interested can
give it a go.
TTFN,
Bill Dudney
MyFaces - myfaces.apache.org
Wadi - incubator.apache.org/wadi
On Feb 23, 2006, at 9:53 AM, Mike Kienenberger wrote:
> As an end-user, I find using maven 2 is really painless.
>
> As a developer, I find using maven to be another huge learning curve
> that I don't have time for right now.
>
> The MyFaces reorg basically locked me out of MyFaces source until it
> stabilzed due to lack of time to learn Maven.
>
> Now that it's done (Is it? It seems like it's being tweaked
> constantly!), it's not so bad. It's not COMPLETELY compatible with
> Eclipse, but it's pretty close! (You have to check out the code to a
> "workspace-level" location, run "mvn eclipse:eclipse" and then import
> all of the newly-created projects (11 at last count for MyFaces) into
> Eclipse. As far as I can tell, that's all fairly painless to work on
> once it's done.
>
> However, Cayenne would need someone who's a maven 2 expert in order to
> make the conversion.
>
> On 2/23/06, Andrus Adamchik <andru..bjectstyle.org> wrote:
>> [I am forwarding this message to cayenne-devel with my comment. Bill,
>> I see you are subscribed to it already.]
>>
>> A few months ago we went through a big reorg of the build scripts to
>> better handle multiple subprojects (back then the driving force was
>> to be able to develop 1.4 and 1.5 builds in parallel). I am very
>> satisfied with what we have now, but I do realize that scaling it to
>> a larger number of subprojects can be tough.
>>
>> While we maybe looking for alternatives, my current concerns/
>> questions (many coming from total ignorance about maven) are the
>> following:
>>
>> 1. Unit tests DB switching. Will it be possible with Maven?
>>
>> http://objectstyle.org/confluence/display/CAY/Running+Unit+Tests
>>
>> 2. Ant scripts are optimized to do things incrementally, so if I need
>> to run just a single test, I don't have to do the entire build (maybe
>> this concern will go away once I upgrade to the new Apple
>> MacBook? :-))
>>
>> 3. Web site. While our current site may need improvement (see the
>> whole CMS thread - http://www.objectstyle.org/cayenne/lists/cayenne-
>> user/2005/10/0157.html ), I'd like to preserve the "branded" site,
>> just make it more flexible. Wouldn't switching to Maven-built site
>> take us further away from that goal?
>>
>> 4. (showing my ignorance here) If dependencies are downloaded during
>> the build, how do we setup Eclipse to use the right dependencies.
>> Corollary to that - if we don't want to use the latest version of
>> some dependency package (e.g. cause it is not widely deployed out
>> there yet and is not fully backwards compatible), can Maven handle
>> that?
>>
>> 5. If there is something Maven does not support is there a way to
>> plugin an Ant script in the build process?
>>
>> As you see all of these concerns are about loosing flexibility that
>> Ant presently gives us. So maybe lets try Maven with cayenne-jpa to
>> get a feel of what it is, but I'd postpone the discussion of
>> migration of the main Cayenne build system till at least after 1.2.
>>
>> Right now cayenne-jpa project has no consistent build system. I was
>> going to write an Ant-based script very soon (CAY-459 task). So Bill,
>> would it be possible to set up something Maven-based quickly for the
>> JPA work?
>>
>> Andrus
>>
>>
>>
>> On Feb 23, 2006, at 7:29 AM, Bill Dudney wrote:
>>> Hi All,
>>>
>>> I wanted to start a thread on this topic.
>>>
>>> I was wondering what the dev community interest is on moving to m2
>>> for at least the cayenne jpa stuff.
>>>
>>> I have been involved in a couple of m2 moves and would be glad to
>>> help out with this on Cayenne.
>>>
>>> Benefits as I see them;
>>> 1) automated build without reliance on properties files
>>> 2) easy to package various builds in one invocation (i.e. linux,
>>> windows, osx builds in one invocation of m2)
>>> 3) Simplified site building and deploying
>>> 4) makes it much easier to get an m2 repository for people to use
>>> maven with Cayenne
>>>
>>> Downside:
>>> 1) directory layout should match the m2 expected dir structure for
>>> maximum benifit
>>> 2) m2 is not as familiar so some people that want to download and
>>> build cayenne themselves might be turned off
>>> 3) the ibiblio repo can be very slow and make maven very slow
>>>
>>> There are probably lots of others on both the + and - side.
>>>
>>> Thoughts?
>>>
>>> Bill Dudney
>>> MyFaces - myfaces.apache.org
>>> Wadi - incubator.apache.org/wadi
>>
>>
This archive was generated by hypermail 2.0.0 : Thu Feb 23 2006 - 14:25:16 EST