I am not sure what you mean by releases support ... Publication of 
projects/modules (in integration, milestone, release status) is able to do in 
Ivy easy.
 
The question is if support in Maven2 is so great that I can not do it in other 
way with less time. I think that if I want to do something little different 
that Maven2 supports out of box without special configuration I will loose more 
time then I would spend using specialized tools for that purpose - project web 
site, docmentation, dependency management, publication of project artifacts in 
repositories ...
 
Thats what I think (but may be I am wrong :)
 
Tapestry, Spring ... is using Maven2. Is it so great ? There will be (or was) 
so much trouble with that ...
 
P.

________________________________

From: Jesse Kuhnert [mailto:[EMAIL PROTECTED]
Sent: pi 24. 11. 2006 20:20
To: Tapestry development
Subject: Re: Maven feedback ?



If you're going to comment in here then I guess you're asking for it ;)

If all I wanted to do was dependency management I might very well
think Ivy is a great tool. Sadly we need to do a lot more than that.
Like documentation  / releases / etc. I'm not feeling like Ivy is
going to help me there.

In a perfect world I'd like to have maven2 using the "advertised" Ivy
dependency management logic. Have you guys considered donating that
logic back ?

On 11/24/06, Blšták Peter <[EMAIL PROTECTED]> wrote:
> Hi all, forget Maven :)
> for depndency management I suggest Ivy (and IvyDE Eclipse plugin).
> It is easy and does exactly what it is desired to do.
>
> http://www.jayasoft.org/ivy
> http://www.jayasoft.org/ivyde
>
> moving to apache ...
> http://incubator.apache.org/projects/ivy.html
> http://wiki.apache.org/ivy/FrontPage
>
> Peter
>
> ________________________________
>
> From: Howard Lewis Ship [mailto:[EMAIL PROTECTED]
> Sent: št 23. 11. 2006 16:23
> To: Tapestry development
> Cc: [EMAIL PROTECTED]
> Subject: Re: Maven feedback ?
>
>
>
> I've found that Maven does exactly what I want at least 80% of the time, but
> the remaining 20% of the time ends up involving a lot of experimentation and
> head scratching.
>
> Jesse is braver than me ... he was able to turn the existing source layout
> for Tapestry 4 into a Maven build. I tried that and failed at least once
> (the first time, using Maven 1).
>
> For Tapestry 5, I've started from scratch and have been careful to lay
> things out the way Maven needs them to be.  I've found that as you deviate
> from its desired structure, i.e., src/main/java etc., things slowly start to
> fail (I suspect because of Maven plugins taking incorrect shortcuts).
>
> I would definately suggest creating a throw-away branch or two, to
> experiment with it all before trying it on your trunk.   Be prepared to move
> a bunch of files around.
>
> At the end of the day, it is valuable. Making it easy to build your code
> from scratch encourages early adopters, which is critical. I can't tell you
> how many out-of-date documents existing about building Tapestry 1 through 4
> ... now that documentation just says "mvn install". I can tell you that for
> many reasons, including Maven, I'm getting early feedback on Tapestry 5 that
> I've never gotten before.
>
> We'll be setting up Continuous Integration soon, and Maven will be critical
> to the success of that.
>
> On 11/23/06, Marnie McCormack <[EMAIL PROTECTED]> wrote:
> >
> > Re-sending as I couldn't spot this post on the archives. Apologies if I've
> > missed it.
> >
> > Any views/input would be appreciated.
> >
> > Thanks very much,
> > Marnie
> >
> >
> > On 11/21/06, Marnie McCormack <[EMAIL PROTECTED]> wrote:
> > >
> > >  Hi All,
> > >
> > > I work on the Apache Incubator project Qpid. We are currently mid
> > > transition to maven for build/release.
> > >
> > > We've encountered a few issues along the way (snapshots, directory
> > > structures etc). I wondered if you could give me some feedback on your
> > > project's experiences with maven please ? Would you recommend it for use
> > ?
> > >
> > > Thanks in advance,
> > > Marnie
> > >
> >
> >
>
>
> --
> Howard M. Lewis Ship
> TWD Consulting, Inc.
> Independent J2EE / Open-Source Java Consultant
> Creator and PMC Chair, Apache Tapestry
> Creator, Apache HiveMind
>
> Professional Tapestry training, mentoring, support
> and project work.  http://howardlewisship.com <http://howardlewisship.com/>  
> <http://howardlewisship.com/>
>
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>


--
Jesse Kuhnert
Tapestry/Dojo/(and a dash of TestNG), team member/developer

Open source based consulting work centered around
dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com 
<http://blog.opencomponentry.com/> 

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to