You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tapestry.apache.org by "Mark W. Shead" <mw...@gmail.com> on 2008/01/31 15:56:08 UTC

Maven Support

http://tapestryjava.blogspot.com/2007/11/maven-wont-get-fooled-again.html

After reading Howard's thoughts on using Maven for a large project,  
I'm concerned that Tapestry might drop Maven support entirely and I  
wanted to offer an end user perspective.  As far as what is used to  
build T5 for the developers, I understand if they want to switch to  
something else.  However, since most Java developers are going to be  
using Maven for something, I think it is vital to keep the capability  
of creating a T5 project from an archetype.

This lowers the barrier for people wanting to try it out.  Doing away  
with this capability would increased the real (or at least perceived)  
complexity of "trying things out" for developers who are already using  
Maven for other things.

Just my two cents.

Mark

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org


Re: Maven Support

Posted by Christian Edward Gruber <ch...@gmail.com>.
We should probably take this all offline, or to the maven users lists,  
as this isn't really directly relevant to T{3..5}.

Christian

On 31-Jan-08, at 13:42 , Michael Lake wrote:

>
> For those of you IDEA users, i did a little roundup of information  
> regarding maven2 integration:
>
> I was thinking of trying out IDEA's EAP release of 7.0.3 found here: http://www.jetbrains.net/confluence/display/IDEADEV/Selena+EAP
>
> But then I dug into the Jetbrains' JIRA for maven integration: http://www.jetbrains.net/jira/browse/IDEADEV/component/11121
> which shows quite a few bug reports with currently ZERO fixes going  
> into 7.0.3 and 25 fixes for IDEA 8.0
>
> It seems that IDEA's integration was taken from a sub-project the  
> mevenide project:
> http://mevenide.codehaus.org/m2-site/mevenide2-idea/
>
> and NetBeans' integration came from another sub-project of the  
> mevenide project:
> http://mevenide.codehaus.org/m2-site/index.html
>
> doing a little fooling around and it's true, the netbeans one does  
> work a lot better than IDEA's.
>
> The plugins appear to be from different teams. Perhaps Sun is lining  
> someone's pockets better than JetBrains? :)
>
> Hopefully 2.1 answers all our prayers and that the IDE plugin dev  
> teams can integrate successfully.
>
> -mike
>
> On Jan 31, 2008, at 12:17 PM, Christian Edward Gruber wrote:
>
>> Heh.   I've been following the maven dev list, and some of the re- 
>> thinking done for 2.1 seems to clean things out substantially,  
>> including resolving this whole issue of repeatability and making  
>> things cleaner for stamping a build environment (sets of plugins,  
>> etc.)   I'm not saying this to suggest "stick with m2", but just to  
>> validate that some news of the headaches are reaching the right  
>> people, and things are being altered to address some of the worst  
>> of this.
>>
>> BTW, I've used the maven ant tasks for dependency stuff with great  
>> success, using the dependency stuff to generate classpaths for ant  
>> tasks.  Might be the ticket for here, though I don't know if it  
>> will build maven artifacts suitable for dropping on a repository  
>> auto-magi-conveniently.
>>
>> Christian.
>>
>> On 31-Jan-08, at 11:11 , Howard Lewis Ship wrote:
>>
>>> It's quite possible to use Ant to build, but to generate Maven
>>> artifacts.  The dependencies are the good part of Maven, it's just  
>>> the
>>> build system layered on those dependencies that is atrocious.
>>>
>>> On Jan 31, 2008 6:59 AM, Christian Edward Gruber
>>> <ch...@gmail.com> wrote:
>>>> I'd like to second that, and at the very least, releasing maven
>>>> artifacts for those wanting to build T5 apps using M2 is critical.
>>>> This can be done regardless of whether T5 itself is using maven,  
>>>> but
>>>> it would be critical to easy use in most environments in which I  
>>>> have
>>>> worked or foresee working.
>>>>
>>>> Christian.
>>>>
>>>>
>>>> On 31-Jan-08, at 09:56 , Mark W. Shead wrote:
>>>>
>>>>> http://tapestryjava.blogspot.com/2007/11/maven-wont-get-fooled-again.html
>>>>>
>>>>> After reading Howard's thoughts on using Maven for a large  
>>>>> project,
>>>>> I'm concerned that Tapestry might drop Maven support entirely  
>>>>> and I
>>>>> wanted to offer an end user perspective.  As far as what is used  
>>>>> to
>>>>> build T5 for the developers, I understand if they want to switch  
>>>>> to
>>>>> something else.  However, since most Java developers are going  
>>>>> to be
>>>>> using Maven for something, I think it is vital to keep the
>>>>> capability of creating a T5 project from an archetype.
>>>>>
>>>>> This lowers the barrier for people wanting to try it out.  Doing
>>>>> away with this capability would increased the real (or at least
>>>>> perceived) complexity of "trying things out" for developers who  
>>>>> are
>>>>> already using Maven for other things.
>>>>>
>>>>> Just my two cents.
>>>>>
>>>>> Mark
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
>>>>> For additional commands, e-mail: users-help@tapestry.apache.org
>>>>>
>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
>>>> For additional commands, e-mail: users-help@tapestry.apache.org
>>>>
>>>>
>>>
>>>
>>>
>>> -- 
>>> Howard M. Lewis Ship
>>>
>>> Creator Apache Tapestry and Apache HiveMind
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
>>> For additional commands, e-mail: users-help@tapestry.apache.org
>>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
>> For additional commands, e-mail: users-help@tapestry.apache.org
>>
>


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org


Re: Maven Support

Posted by Andreas Andreou <an...@gmail.com>.
On Jan 31, 2008 8:42 PM, Michael Lake <ml...@netvue.com> wrote:
>
> The plugins appear to be from different teams. Perhaps Sun is lining
> someone's pockets better than JetBrains? :)

AFAIK, that's not the case! NB's plugin is just a 'spare-time'
project, and it's
amazing that it works so well... The problem with NB is that there's no concept
like Eclipse's nature or idea's facet. So, a maven project can't
really be a web
project, meaning that you dont get all the nice wizards and tools that
they've build
for them

>
> Hopefully 2.1 answers all our prayers and that the IDE plugin dev
> teams can integrate successfully.
>
> -mike
>
>
> On Jan 31, 2008, at 12:17 PM, Christian Edward Gruber wrote:
>
> > Heh.   I've been following the maven dev list, and some of the re-
> > thinking done for 2.1 seems to clean things out substantially,
> > including resolving this whole issue of repeatability and making
> > things cleaner for stamping a build environment (sets of plugins,
> > etc.)   I'm not saying this to suggest "stick with m2", but just to
> > validate that some news of the headaches are reaching the right
> > people, and things are being altered to address some of the worst of
> > this.
> >
> > BTW, I've used the maven ant tasks for dependency stuff with great
> > success, using the dependency stuff to generate classpaths for ant
> > tasks.  Might be the ticket for here, though I don't know if it will
> > build maven artifacts suitable for dropping on a repository auto-
> > magi-conveniently.
> >
> > Christian.
> >
> > On 31-Jan-08, at 11:11 , Howard Lewis Ship wrote:
> >
> >> It's quite possible to use Ant to build, but to generate Maven
> >> artifacts.  The dependencies are the good part of Maven, it's just
> >> the
> >> build system layered on those dependencies that is atrocious.
> >>
> >> On Jan 31, 2008 6:59 AM, Christian Edward Gruber
> >> <ch...@gmail.com> wrote:
> >>> I'd like to second that, and at the very least, releasing maven
> >>> artifacts for those wanting to build T5 apps using M2 is critical.
> >>> This can be done regardless of whether T5 itself is using maven, but
> >>> it would be critical to easy use in most environments in which I
> >>> have
> >>> worked or foresee working.
> >>>
> >>> Christian.
> >>>
> >>>
> >>> On 31-Jan-08, at 09:56 , Mark W. Shead wrote:
> >>>
> >>>> http://tapestryjava.blogspot.com/2007/11/maven-wont-get-fooled-again.html
> >>>>
> >>>> After reading Howard's thoughts on using Maven for a large project,
> >>>> I'm concerned that Tapestry might drop Maven support entirely and I
> >>>> wanted to offer an end user perspective.  As far as what is used to
> >>>> build T5 for the developers, I understand if they want to switch to
> >>>> something else.  However, since most Java developers are going to
> >>>> be
> >>>> using Maven for something, I think it is vital to keep the
> >>>> capability of creating a T5 project from an archetype.
> >>>>
> >>>> This lowers the barrier for people wanting to try it out.  Doing
> >>>> away with this capability would increased the real (or at least
> >>>> perceived) complexity of "trying things out" for developers who are
> >>>> already using Maven for other things.
> >>>>
> >>>> Just my two cents.
> >>>>
> >>>> Mark
> >>>>
> >>>> ---------------------------------------------------------------------
> >>>> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> >>>> For additional commands, e-mail: users-help@tapestry.apache.org
> >>>>
> >>>
> >>>
> >>> ---------------------------------------------------------------------
> >>> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> >>> For additional commands, e-mail: users-help@tapestry.apache.org
> >>>
> >>>
> >>
> >>
> >>
> >> --
> >> Howard M. Lewis Ship
> >>
> >> Creator Apache Tapestry and Apache HiveMind
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> >> For additional commands, e-mail: users-help@tapestry.apache.org
> >>
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> > For additional commands, e-mail: users-help@tapestry.apache.org
> >
>
>



-- 
Andreas Andreou - andyhot@apache.org - http://blog.andyhot.gr
Tapestry / Tacos developer
Open Source / JEE Consulting

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org


Re: Maven Support

Posted by Howard Lewis Ship <hl...@gmail.com>.
I'm now using build #7675 ... it's not quite as stable as 7.0.2
however.  I also had to re-import my projects that used Maven.  Other
than that (and a few keystrokes changing their meaning) I haven't be
able to see a real difference.

On Jan 31, 2008 10:57 AM, Michael Lake <ml...@netvue.com> wrote:
>
> oh wow, you're right, there are fixes!
>
> thanks for setting the record straight!
>
> -mike
>
>
> On Jan 31, 2008, at 1:45 PM, Jesse Kuhnert wrote:
>
> > I've been using all of the 7.0.3 eap releases and can confirm that
> > they have actually been fixing the bugs - even if they don't close
> > them in JIRA.   Every release since the first introduction of it has
> > had a bug fixed that I've noticed.
> >
> > On Thu, Jan 31, 2008 at 1:42 PM, Michael Lake <ml...@netvue.com>
> > wrote:
> >>
> >> For those of you IDEA users, i did a little roundup of information
> >> regarding maven2 integration:
> >>
> >> I was thinking of trying out IDEA's EAP release of 7.0.3 found
> >> here: http://www.jetbrains.net/confluence/display/IDEADEV/Selena+EAP
> >>
> >> But then I dug into the Jetbrains' JIRA for maven integration: http://www.jetbrains.net/jira/browse/IDEADEV/component/11121
> >> which shows quite a few bug reports with currently ZERO fixes going
> >> into 7.0.3 and 25 fixes for IDEA 8.0
> >>
> >> It seems that IDEA's integration was taken from a sub-project the
> >> mevenide project:
> >> http://mevenide.codehaus.org/m2-site/mevenide2-idea/
> >>
> >> and NetBeans' integration came from another sub-project of the
> >> mevenide project:
> >> http://mevenide.codehaus.org/m2-site/index.html
> >>
> >> doing a little fooling around and it's true, the netbeans one does
> >> work a lot better than IDEA's.
> >>
> >> The plugins appear to be from different teams. Perhaps Sun is lining
> >> someone's pockets better than JetBrains? :)
> >>
> >> Hopefully 2.1 answers all our prayers and that the IDE plugin dev
> >> teams can integrate successfully.
> >>
> >> -mike
> >>
> >>
> >>
> >> On Jan 31, 2008, at 12:17 PM, Christian Edward Gruber wrote:
> >>
> >>> Heh.   I've been following the maven dev list, and some of the re-
> >>> thinking done for 2.1 seems to clean things out substantially,
> >>> including resolving this whole issue of repeatability and making
> >>> things cleaner for stamping a build environment (sets of plugins,
> >>> etc.)   I'm not saying this to suggest "stick with m2", but just to
> >>> validate that some news of the headaches are reaching the right
> >>> people, and things are being altered to address some of the worst of
> >>> this.
> >>>
> >>> BTW, I've used the maven ant tasks for dependency stuff with great
> >>> success, using the dependency stuff to generate classpaths for ant
> >>> tasks.  Might be the ticket for here, though I don't know if it will
> >>> build maven artifacts suitable for dropping on a repository auto-
> >>> magi-conveniently.
> >>>
> >>> Christian.
> >>>
> >>> On 31-Jan-08, at 11:11 , Howard Lewis Ship wrote:
> >>>
> >>>> It's quite possible to use Ant to build, but to generate Maven
> >>>> artifacts.  The dependencies are the good part of Maven, it's just
> >>>> the
> >>>> build system layered on those dependencies that is atrocious.
> >>>>
> >>>> On Jan 31, 2008 6:59 AM, Christian Edward Gruber
> >>>> <ch...@gmail.com> wrote:
> >>>>> I'd like to second that, and at the very least, releasing maven
> >>>>> artifacts for those wanting to build T5 apps using M2 is critical.
> >>>>> This can be done regardless of whether T5 itself is using maven,
> >>>>> but
> >>>>> it would be critical to easy use in most environments in which I
> >>>>> have
> >>>>> worked or foresee working.
> >>>>>
> >>>>> Christian.
> >>>>>
> >>>>>
> >>>>> On 31-Jan-08, at 09:56 , Mark W. Shead wrote:
> >>>>>
> >>>>>> http://tapestryjava.blogspot.com/2007/11/maven-wont-get-fooled-again.html
> >>>>>>
> >>>>>> After reading Howard's thoughts on using Maven for a large
> >>>>>> project,
> >>>>>> I'm concerned that Tapestry might drop Maven support entirely
> >>>>>> and I
> >>>>>> wanted to offer an end user perspective.  As far as what is
> >>>>>> used to
> >>>>>> build T5 for the developers, I understand if they want to
> >>>>>> switch to
> >>>>>> something else.  However, since most Java developers are going to
> >>>>>> be
> >>>>>> using Maven for something, I think it is vital to keep the
> >>>>>> capability of creating a T5 project from an archetype.
> >>>>>>
> >>>>>> This lowers the barrier for people wanting to try it out.  Doing
> >>>>>> away with this capability would increased the real (or at least
> >>>>>> perceived) complexity of "trying things out" for developers who
> >>>>>> are
> >>>>>> already using Maven for other things.
> >>>>>>
> >>>>>> Just my two cents.
> >>>>>>
> >>>>>> Mark
> >>>>>>
> >>>>>> ---------------------------------------------------------------------
> >>>>>> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> >>>>>> For additional commands, e-mail: users-help@tapestry.apache.org
> >>>>>>
> >>>>>
> >>>>>
> >>>>> ---------------------------------------------------------------------
> >>>>> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> >>>>> For additional commands, e-mail: users-help@tapestry.apache.org
> >>>>>
> >>>>>
> >>>>
> >>>>
> >>>>
> >>>> --
> >>>> Howard M. Lewis Ship
> >>>>
> >>>> Creator Apache Tapestry and Apache HiveMind
> >>>>
> >>>> ---------------------------------------------------------------------
> >>>> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> >>>> For additional commands, e-mail: users-help@tapestry.apache.org
> >>>>
> >>>
> >>>
> >>> ---------------------------------------------------------------------
> >>> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> >>> For additional commands, e-mail: users-help@tapestry.apache.org
> >>>
> >>
> >>
> >
> >
> >
> > --
> > Jesse Kuhnert
> > Tapestry / OGNL / Dojo team member/developer
> >
> > Open source based consulting work centered around
> > dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> > For additional commands, e-mail: users-help@tapestry.apache.org
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@tapestry.apache.org
>
>



-- 
Howard M. Lewis Ship

Creator Apache Tapestry and Apache HiveMind

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org


Re: Maven Support

Posted by Michael Lake <ml...@netvue.com>.
oh wow, you're right, there are fixes!

thanks for setting the record straight!

-mike

On Jan 31, 2008, at 1:45 PM, Jesse Kuhnert wrote:

> I've been using all of the 7.0.3 eap releases and can confirm that
> they have actually been fixing the bugs - even if they don't close
> them in JIRA.   Every release since the first introduction of it has
> had a bug fixed that I've noticed.
>
> On Thu, Jan 31, 2008 at 1:42 PM, Michael Lake <ml...@netvue.com>  
> wrote:
>>
>> For those of you IDEA users, i did a little roundup of information
>> regarding maven2 integration:
>>
>> I was thinking of trying out IDEA's EAP release of 7.0.3 found  
>> here: http://www.jetbrains.net/confluence/display/IDEADEV/Selena+EAP
>>
>> But then I dug into the Jetbrains' JIRA for maven integration: http://www.jetbrains.net/jira/browse/IDEADEV/component/11121
>> which shows quite a few bug reports with currently ZERO fixes going
>> into 7.0.3 and 25 fixes for IDEA 8.0
>>
>> It seems that IDEA's integration was taken from a sub-project the
>> mevenide project:
>> http://mevenide.codehaus.org/m2-site/mevenide2-idea/
>>
>> and NetBeans' integration came from another sub-project of the
>> mevenide project:
>> http://mevenide.codehaus.org/m2-site/index.html
>>
>> doing a little fooling around and it's true, the netbeans one does
>> work a lot better than IDEA's.
>>
>> The plugins appear to be from different teams. Perhaps Sun is lining
>> someone's pockets better than JetBrains? :)
>>
>> Hopefully 2.1 answers all our prayers and that the IDE plugin dev
>> teams can integrate successfully.
>>
>> -mike
>>
>>
>>
>> On Jan 31, 2008, at 12:17 PM, Christian Edward Gruber wrote:
>>
>>> Heh.   I've been following the maven dev list, and some of the re-
>>> thinking done for 2.1 seems to clean things out substantially,
>>> including resolving this whole issue of repeatability and making
>>> things cleaner for stamping a build environment (sets of plugins,
>>> etc.)   I'm not saying this to suggest "stick with m2", but just to
>>> validate that some news of the headaches are reaching the right
>>> people, and things are being altered to address some of the worst of
>>> this.
>>>
>>> BTW, I've used the maven ant tasks for dependency stuff with great
>>> success, using the dependency stuff to generate classpaths for ant
>>> tasks.  Might be the ticket for here, though I don't know if it will
>>> build maven artifacts suitable for dropping on a repository auto-
>>> magi-conveniently.
>>>
>>> Christian.
>>>
>>> On 31-Jan-08, at 11:11 , Howard Lewis Ship wrote:
>>>
>>>> It's quite possible to use Ant to build, but to generate Maven
>>>> artifacts.  The dependencies are the good part of Maven, it's just
>>>> the
>>>> build system layered on those dependencies that is atrocious.
>>>>
>>>> On Jan 31, 2008 6:59 AM, Christian Edward Gruber
>>>> <ch...@gmail.com> wrote:
>>>>> I'd like to second that, and at the very least, releasing maven
>>>>> artifacts for those wanting to build T5 apps using M2 is critical.
>>>>> This can be done regardless of whether T5 itself is using maven,  
>>>>> but
>>>>> it would be critical to easy use in most environments in which I
>>>>> have
>>>>> worked or foresee working.
>>>>>
>>>>> Christian.
>>>>>
>>>>>
>>>>> On 31-Jan-08, at 09:56 , Mark W. Shead wrote:
>>>>>
>>>>>> http://tapestryjava.blogspot.com/2007/11/maven-wont-get-fooled-again.html
>>>>>>
>>>>>> After reading Howard's thoughts on using Maven for a large  
>>>>>> project,
>>>>>> I'm concerned that Tapestry might drop Maven support entirely  
>>>>>> and I
>>>>>> wanted to offer an end user perspective.  As far as what is  
>>>>>> used to
>>>>>> build T5 for the developers, I understand if they want to  
>>>>>> switch to
>>>>>> something else.  However, since most Java developers are going to
>>>>>> be
>>>>>> using Maven for something, I think it is vital to keep the
>>>>>> capability of creating a T5 project from an archetype.
>>>>>>
>>>>>> This lowers the barrier for people wanting to try it out.  Doing
>>>>>> away with this capability would increased the real (or at least
>>>>>> perceived) complexity of "trying things out" for developers who  
>>>>>> are
>>>>>> already using Maven for other things.
>>>>>>
>>>>>> Just my two cents.
>>>>>>
>>>>>> Mark
>>>>>>
>>>>>> ---------------------------------------------------------------------
>>>>>> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
>>>>>> For additional commands, e-mail: users-help@tapestry.apache.org
>>>>>>
>>>>>
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
>>>>> For additional commands, e-mail: users-help@tapestry.apache.org
>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Howard M. Lewis Ship
>>>>
>>>> Creator Apache Tapestry and Apache HiveMind
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
>>>> For additional commands, e-mail: users-help@tapestry.apache.org
>>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
>>> For additional commands, e-mail: users-help@tapestry.apache.org
>>>
>>
>>
>
>
>
> -- 
> Jesse Kuhnert
> Tapestry / OGNL / Dojo team member/developer
>
> Open source based consulting work centered around
> dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@tapestry.apache.org
>


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org


Re: Maven Support

Posted by Jesse Kuhnert <jk...@gmail.com>.
I've been using all of the 7.0.3 eap releases and can confirm that
they have actually been fixing the bugs - even if they don't close
them in JIRA.   Every release since the first introduction of it has
had a bug fixed that I've noticed.

On Thu, Jan 31, 2008 at 1:42 PM, Michael Lake <ml...@netvue.com> wrote:
>
>  For those of you IDEA users, i did a little roundup of information
>  regarding maven2 integration:
>
>  I was thinking of trying out IDEA's EAP release of 7.0.3 found here: http://www.jetbrains.net/confluence/display/IDEADEV/Selena+EAP
>
>  But then I dug into the Jetbrains' JIRA for maven integration: http://www.jetbrains.net/jira/browse/IDEADEV/component/11121
>  which shows quite a few bug reports with currently ZERO fixes going
>  into 7.0.3 and 25 fixes for IDEA 8.0
>
>  It seems that IDEA's integration was taken from a sub-project the
>  mevenide project:
>  http://mevenide.codehaus.org/m2-site/mevenide2-idea/
>
>  and NetBeans' integration came from another sub-project of the
>  mevenide project:
>  http://mevenide.codehaus.org/m2-site/index.html
>
>  doing a little fooling around and it's true, the netbeans one does
>  work a lot better than IDEA's.
>
>  The plugins appear to be from different teams. Perhaps Sun is lining
>  someone's pockets better than JetBrains? :)
>
>  Hopefully 2.1 answers all our prayers and that the IDE plugin dev
>  teams can integrate successfully.
>
>  -mike
>
>
>
>  On Jan 31, 2008, at 12:17 PM, Christian Edward Gruber wrote:
>
>  > Heh.   I've been following the maven dev list, and some of the re-
>  > thinking done for 2.1 seems to clean things out substantially,
>  > including resolving this whole issue of repeatability and making
>  > things cleaner for stamping a build environment (sets of plugins,
>  > etc.)   I'm not saying this to suggest "stick with m2", but just to
>  > validate that some news of the headaches are reaching the right
>  > people, and things are being altered to address some of the worst of
>  > this.
>  >
>  > BTW, I've used the maven ant tasks for dependency stuff with great
>  > success, using the dependency stuff to generate classpaths for ant
>  > tasks.  Might be the ticket for here, though I don't know if it will
>  > build maven artifacts suitable for dropping on a repository auto-
>  > magi-conveniently.
>  >
>  > Christian.
>  >
>  > On 31-Jan-08, at 11:11 , Howard Lewis Ship wrote:
>  >
>  >> It's quite possible to use Ant to build, but to generate Maven
>  >> artifacts.  The dependencies are the good part of Maven, it's just
>  >> the
>  >> build system layered on those dependencies that is atrocious.
>  >>
>  >> On Jan 31, 2008 6:59 AM, Christian Edward Gruber
>  >> <ch...@gmail.com> wrote:
>  >>> I'd like to second that, and at the very least, releasing maven
>  >>> artifacts for those wanting to build T5 apps using M2 is critical.
>  >>> This can be done regardless of whether T5 itself is using maven, but
>  >>> it would be critical to easy use in most environments in which I
>  >>> have
>  >>> worked or foresee working.
>  >>>
>  >>> Christian.
>  >>>
>  >>>
>  >>> On 31-Jan-08, at 09:56 , Mark W. Shead wrote:
>  >>>
>  >>>> http://tapestryjava.blogspot.com/2007/11/maven-wont-get-fooled-again.html
>  >>>>
>  >>>> After reading Howard's thoughts on using Maven for a large project,
>  >>>> I'm concerned that Tapestry might drop Maven support entirely and I
>  >>>> wanted to offer an end user perspective.  As far as what is used to
>  >>>> build T5 for the developers, I understand if they want to switch to
>  >>>> something else.  However, since most Java developers are going to
>  >>>> be
>  >>>> using Maven for something, I think it is vital to keep the
>  >>>> capability of creating a T5 project from an archetype.
>  >>>>
>  >>>> This lowers the barrier for people wanting to try it out.  Doing
>  >>>> away with this capability would increased the real (or at least
>  >>>> perceived) complexity of "trying things out" for developers who are
>  >>>> already using Maven for other things.
>  >>>>
>  >>>> Just my two cents.
>  >>>>
>  >>>> Mark
>  >>>>
>  >>>> ---------------------------------------------------------------------
>  >>>> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
>  >>>> For additional commands, e-mail: users-help@tapestry.apache.org
>  >>>>
>  >>>
>  >>>
>  >>> ---------------------------------------------------------------------
>  >>> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
>  >>> For additional commands, e-mail: users-help@tapestry.apache.org
>  >>>
>  >>>
>  >>
>  >>
>  >>
>  >> --
>  >> Howard M. Lewis Ship
>  >>
>  >> Creator Apache Tapestry and Apache HiveMind
>  >>
>  >> ---------------------------------------------------------------------
>  >> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
>  >> For additional commands, e-mail: users-help@tapestry.apache.org
>  >>
>  >
>  >
>  > ---------------------------------------------------------------------
>  > To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
>  > For additional commands, e-mail: users-help@tapestry.apache.org
>  >
>
>



-- 
Jesse Kuhnert
Tapestry / OGNL / Dojo team member/developer

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

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org


Re: Maven Support

Posted by Michael Lake <ml...@netvue.com>.
For those of you IDEA users, i did a little roundup of information  
regarding maven2 integration:

I was thinking of trying out IDEA's EAP release of 7.0.3 found here: http://www.jetbrains.net/confluence/display/IDEADEV/Selena+EAP

But then I dug into the Jetbrains' JIRA for maven integration: http://www.jetbrains.net/jira/browse/IDEADEV/component/11121
which shows quite a few bug reports with currently ZERO fixes going  
into 7.0.3 and 25 fixes for IDEA 8.0

It seems that IDEA's integration was taken from a sub-project the  
mevenide project:
http://mevenide.codehaus.org/m2-site/mevenide2-idea/

and NetBeans' integration came from another sub-project of the  
mevenide project:
http://mevenide.codehaus.org/m2-site/index.html

doing a little fooling around and it's true, the netbeans one does  
work a lot better than IDEA's.

The plugins appear to be from different teams. Perhaps Sun is lining  
someone's pockets better than JetBrains? :)

Hopefully 2.1 answers all our prayers and that the IDE plugin dev  
teams can integrate successfully.

-mike

On Jan 31, 2008, at 12:17 PM, Christian Edward Gruber wrote:

> Heh.   I've been following the maven dev list, and some of the re- 
> thinking done for 2.1 seems to clean things out substantially,  
> including resolving this whole issue of repeatability and making  
> things cleaner for stamping a build environment (sets of plugins,  
> etc.)   I'm not saying this to suggest "stick with m2", but just to  
> validate that some news of the headaches are reaching the right  
> people, and things are being altered to address some of the worst of  
> this.
>
> BTW, I've used the maven ant tasks for dependency stuff with great  
> success, using the dependency stuff to generate classpaths for ant  
> tasks.  Might be the ticket for here, though I don't know if it will  
> build maven artifacts suitable for dropping on a repository auto- 
> magi-conveniently.
>
> Christian.
>
> On 31-Jan-08, at 11:11 , Howard Lewis Ship wrote:
>
>> It's quite possible to use Ant to build, but to generate Maven
>> artifacts.  The dependencies are the good part of Maven, it's just  
>> the
>> build system layered on those dependencies that is atrocious.
>>
>> On Jan 31, 2008 6:59 AM, Christian Edward Gruber
>> <ch...@gmail.com> wrote:
>>> I'd like to second that, and at the very least, releasing maven
>>> artifacts for those wanting to build T5 apps using M2 is critical.
>>> This can be done regardless of whether T5 itself is using maven, but
>>> it would be critical to easy use in most environments in which I  
>>> have
>>> worked or foresee working.
>>>
>>> Christian.
>>>
>>>
>>> On 31-Jan-08, at 09:56 , Mark W. Shead wrote:
>>>
>>>> http://tapestryjava.blogspot.com/2007/11/maven-wont-get-fooled-again.html
>>>>
>>>> After reading Howard's thoughts on using Maven for a large project,
>>>> I'm concerned that Tapestry might drop Maven support entirely and I
>>>> wanted to offer an end user perspective.  As far as what is used to
>>>> build T5 for the developers, I understand if they want to switch to
>>>> something else.  However, since most Java developers are going to  
>>>> be
>>>> using Maven for something, I think it is vital to keep the
>>>> capability of creating a T5 project from an archetype.
>>>>
>>>> This lowers the barrier for people wanting to try it out.  Doing
>>>> away with this capability would increased the real (or at least
>>>> perceived) complexity of "trying things out" for developers who are
>>>> already using Maven for other things.
>>>>
>>>> Just my two cents.
>>>>
>>>> Mark
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
>>>> For additional commands, e-mail: users-help@tapestry.apache.org
>>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
>>> For additional commands, e-mail: users-help@tapestry.apache.org
>>>
>>>
>>
>>
>>
>> -- 
>> Howard M. Lewis Ship
>>
>> Creator Apache Tapestry and Apache HiveMind
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
>> For additional commands, e-mail: users-help@tapestry.apache.org
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@tapestry.apache.org
>


Re: Maven Support

Posted by Christian Edward Gruber <ch...@gmail.com>.
Heh.   I've been following the maven dev list, and some of the re- 
thinking done for 2.1 seems to clean things out substantially,  
including resolving this whole issue of repeatability and making  
things cleaner for stamping a build environment (sets of plugins,  
etc.)   I'm not saying this to suggest "stick with m2", but just to  
validate that some news of the headaches are reaching the right  
people, and things are being altered to address some of the worst of  
this.

BTW, I've used the maven ant tasks for dependency stuff with great  
success, using the dependency stuff to generate classpaths for ant  
tasks.  Might be the ticket for here, though I don't know if it will  
build maven artifacts suitable for dropping on a repository auto-magi- 
conveniently.

Christian.

On 31-Jan-08, at 11:11 , Howard Lewis Ship wrote:

> It's quite possible to use Ant to build, but to generate Maven
> artifacts.  The dependencies are the good part of Maven, it's just the
> build system layered on those dependencies that is atrocious.
>
> On Jan 31, 2008 6:59 AM, Christian Edward Gruber
> <ch...@gmail.com> wrote:
>> I'd like to second that, and at the very least, releasing maven
>> artifacts for those wanting to build T5 apps using M2 is critical.
>> This can be done regardless of whether T5 itself is using maven, but
>> it would be critical to easy use in most environments in which I have
>> worked or foresee working.
>>
>> Christian.
>>
>>
>> On 31-Jan-08, at 09:56 , Mark W. Shead wrote:
>>
>>> http://tapestryjava.blogspot.com/2007/11/maven-wont-get-fooled-again.html
>>>
>>> After reading Howard's thoughts on using Maven for a large project,
>>> I'm concerned that Tapestry might drop Maven support entirely and I
>>> wanted to offer an end user perspective.  As far as what is used to
>>> build T5 for the developers, I understand if they want to switch to
>>> something else.  However, since most Java developers are going to be
>>> using Maven for something, I think it is vital to keep the
>>> capability of creating a T5 project from an archetype.
>>>
>>> This lowers the barrier for people wanting to try it out.  Doing
>>> away with this capability would increased the real (or at least
>>> perceived) complexity of "trying things out" for developers who are
>>> already using Maven for other things.
>>>
>>> Just my two cents.
>>>
>>> Mark
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
>>> For additional commands, e-mail: users-help@tapestry.apache.org
>>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
>> For additional commands, e-mail: users-help@tapestry.apache.org
>>
>>
>
>
>
> -- 
> Howard M. Lewis Ship
>
> Creator Apache Tapestry and Apache HiveMind
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@tapestry.apache.org
>


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org


Re: Maven Support

Posted by Howard Lewis Ship <hl...@gmail.com>.
It's quite possible to use Ant to build, but to generate Maven
artifacts.  The dependencies are the good part of Maven, it's just the
build system layered on those dependencies that is atrocious.

On Jan 31, 2008 6:59 AM, Christian Edward Gruber
<ch...@gmail.com> wrote:
> I'd like to second that, and at the very least, releasing maven
> artifacts for those wanting to build T5 apps using M2 is critical.
> This can be done regardless of whether T5 itself is using maven, but
> it would be critical to easy use in most environments in which I have
> worked or foresee working.
>
> Christian.
>
>
> On 31-Jan-08, at 09:56 , Mark W. Shead wrote:
>
> > http://tapestryjava.blogspot.com/2007/11/maven-wont-get-fooled-again.html
> >
> > After reading Howard's thoughts on using Maven for a large project,
> > I'm concerned that Tapestry might drop Maven support entirely and I
> > wanted to offer an end user perspective.  As far as what is used to
> > build T5 for the developers, I understand if they want to switch to
> > something else.  However, since most Java developers are going to be
> > using Maven for something, I think it is vital to keep the
> > capability of creating a T5 project from an archetype.
> >
> > This lowers the barrier for people wanting to try it out.  Doing
> > away with this capability would increased the real (or at least
> > perceived) complexity of "trying things out" for developers who are
> > already using Maven for other things.
> >
> > Just my two cents.
> >
> > Mark
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> > For additional commands, e-mail: users-help@tapestry.apache.org
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@tapestry.apache.org
>
>



-- 
Howard M. Lewis Ship

Creator Apache Tapestry and Apache HiveMind

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org


Re: Maven Support

Posted by Christian Edward Gruber <ch...@gmail.com>.
I'd like to second that, and at the very least, releasing maven  
artifacts for those wanting to build T5 apps using M2 is critical.   
This can be done regardless of whether T5 itself is using maven, but  
it would be critical to easy use in most environments in which I have  
worked or foresee working.

Christian.

On 31-Jan-08, at 09:56 , Mark W. Shead wrote:

> http://tapestryjava.blogspot.com/2007/11/maven-wont-get-fooled-again.html
>
> After reading Howard's thoughts on using Maven for a large project,  
> I'm concerned that Tapestry might drop Maven support entirely and I  
> wanted to offer an end user perspective.  As far as what is used to  
> build T5 for the developers, I understand if they want to switch to  
> something else.  However, since most Java developers are going to be  
> using Maven for something, I think it is vital to keep the  
> capability of creating a T5 project from an archetype.
>
> This lowers the barrier for people wanting to try it out.  Doing  
> away with this capability would increased the real (or at least  
> perceived) complexity of "trying things out" for developers who are  
> already using Maven for other things.
>
> Just my two cents.
>
> Mark
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@tapestry.apache.org
>


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org