You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by Marnie McCormack <ma...@googlemail.com> on 2006/11/23 13:08:11 UTC
Re: Maven feedback ?
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 <ma...@googlemail.com> 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
>
RE: Maven feedback ?
Posted by Blšták Peter <pe...@softec.sk>.
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:jkuhnert@gmail.com]
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 <pe...@softec.sk> 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:hlship@gmail.com]
> Sent: št 23. 11. 2006 16:23
> To: Tapestry development
> Cc: marnie.mccormack@googlemail.com
> 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 <ma...@googlemail.com> 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 <ma...@googlemail.com> 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: dev-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: dev-help@tapestry.apache.org
>
>
--
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: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
Re: Maven feedback ?
Posted by Jesse Kuhnert <jk...@gmail.com>.
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 <pe...@softec.sk> 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:hlship@gmail.com]
> Sent: št 23. 11. 2006 16:23
> To: Tapestry development
> Cc: marnie.mccormack@googlemail.com
> 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 <ma...@googlemail.com> 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 <ma...@googlemail.com> 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/>
>
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: dev-help@tapestry.apache.org
>
>
--
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
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
RE: Maven feedback ?
Posted by Blšták Peter <pe...@softec.sk>.
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:hlship@gmail.com]
Sent: št 23. 11. 2006 16:23
To: Tapestry development
Cc: marnie.mccormack@googlemail.com
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 <ma...@googlemail.com> 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 <ma...@googlemail.com> 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/>
Re: Maven feedback ?
Posted by Howard Lewis Ship <hl...@gmail.com>.
What Jesse said :-)
On 11/27/06, Mark Stang <ms...@pingidentity.com> wrote:
>
> Jesse,
> Thanks, I will try and convert to that!
>
> regards,
>
> Mark
>
> Mark J. Stang
> Senior Engineer/Architect
> office: +1 303.468.2900
> mobile: +1 303.507.2833
> Ping Identity
>
>
>
> -----Original Message-----
> From: Jesse Kuhnert [mailto:jkuhnert@gmail.com]
> Sent: Mon 11/27/2006 10:36 AM
> To: Tapestry development
> Cc: marnie.mccormack@googlemail.com
> Subject: Re: Maven feedback ?
>
> Does this help?
>
> <build>
> <sourceDirectory>src/java</sourceDirectory>
> <outputDirectory>src/context/WEB-INF/classes</outputDirectory>
>
> <resources>
> <resource>
> <directory>src/java</directory>
> <includes>
> <include>**/*.xml</include>
> <include>**/*.jwc</include>
> <include>**/*.page</include>
> <include>**/*.html</include>
> </includes>
> </resource>
> </resources>
>
> <plugins>
> <plugin>
> <groupId>org.mortbay.jetty</groupId>
> <artifactId>maven-jetty-plugin</artifactId>
> <version>6.1-SNAPSHOT</version>
> <configuration>
>
> <webAppSourceDirectory>src/context</webAppSourceDirectory>
> <contextPath>/</contextPath>
> <userRealms>
> <userRealm
> implementation="org.mortbay.jetty.security.HashUserRealm">
> <name>Administration Area</name>
> <config>etc/realm.properties</config>
> </userRealm>
> </userRealms>
> </configuration>
> <dependencies>
> <dependency>
> <groupId>commons-logging</groupId>
> <artifactId>commons-logging</artifactId>
> <version>1.0.4</version>
> </dependency>
> <dependency>
> <groupId>log4j</groupId>
> <artifactId>log4j</artifactId>
> <version>1.2.13</version>
> </dependency>
> </dependencies>
> </plugin>
>
> <plugin>
> <groupId>org.apache.maven.plugins</groupId>
> <artifactId>maven-war-plugin</artifactId>
> <version>2.0.2-SNAPSHOT</version>
> <configuration>
> <warSourceDirectory>src/context</warSourceDirectory>
> <webResources>
> <resource>
> <directory>src/context/WEB-INF</directory>
> <targetPath>WEB-INF/classes</targetPath>
> <includes>
> <include>hibernate.cfg.xml</include>
> </includes>
> </resource>
> <resource>
> <directory>src/java</directory>
> <includes>
> <include>**/*.xml</include>
> <include>**/*.jwc</include>
> <include>**/*.page</include>
> <include>**/*.html</include>
> </includes>
> </resource>
> <resource>
> <directory>external-lib</directory>
> <targetPath>WEB-INF/lib</targetPath>
> <includes>
> <include>jta-1.1.jar</include>
> </includes>
> </resource>
> </webResources>
> </configuration>
> </plugin>
> <plugin>
> <groupId>org.apache.maven.plugins</groupId>
> <artifactId>maven-clean-plugin</artifactId>
> <version>2.2-SNAPSHOT</version>
> </plugin>
> <plugin>
> <groupId>org.apache.maven.plugins</groupId>
> <artifactId>maven-compiler-plugin</artifactId>
> <version>2.1-SNAPSHOT</version>
> <inherited>true</inherited>
> <configuration>
> <source>1.5</source>
> <target>1.5</target>
> </configuration>
> </plugin>
> </plugins>
> <extensions>
> <extension>
> <groupId>mysql</groupId>
> <artifactId>mysql-connector-java</artifactId>
> <version>5.0.4</version>
> </extension>
> </extensions>
> </build>
>
> On 11/27/06, Mark Stang <ms...@pingidentity.com> wrote:
> > Howard,
> > How are you handling "Tapestry Components"? Our build guy reformatted
> out code layout and <sigh> once again put the .html/.jwc in a different
> directory from the .java file that goes with the component. His reasoning
> was that Maven didn't like putting the .html/.jwc somewhere other than in
> resources. Well now, Spindle is as confused as hell and no longer seems to
> be able to find files. All of them now have errors and I am not getting any
> "feedback" about errors.</sigh>
> >
> > regards,
> >
> > Mark
> >
> > Mark J. Stang
> > Senior Engineer/Architect
> > office: +1 303.468.2900
> > mobile: +1 303.507.2833
> > Ping Identity
> >
> >
> >
> > -----Original Message-----
> > From: Howard Lewis Ship [mailto:hlship@gmail.com]
> > Sent: Thu 11/23/2006 8:23 AM
> > To: Tapestry development
> > Cc: marnie.mccormack@googlemail.com
> > 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 <ma...@googlemail.com> 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 <ma...@googlemail.com> 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
> >
> >
> >
>
>
> --
> 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
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: dev-help@tapestry.apache.org
>
>
>
>
--
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
RE: Maven feedback ?
Posted by Mark Stang <ms...@pingidentity.com>.
Jesse,
Thanks, I will try and convert to that!
regards,
Mark
Mark J. Stang
Senior Engineer/Architect
office: +1 303.468.2900
mobile: +1 303.507.2833
Ping Identity
-----Original Message-----
From: Jesse Kuhnert [mailto:jkuhnert@gmail.com]
Sent: Mon 11/27/2006 10:36 AM
To: Tapestry development
Cc: marnie.mccormack@googlemail.com
Subject: Re: Maven feedback ?
Does this help?
<build>
<sourceDirectory>src/java</sourceDirectory>
<outputDirectory>src/context/WEB-INF/classes</outputDirectory>
<resources>
<resource>
<directory>src/java</directory>
<includes>
<include>**/*.xml</include>
<include>**/*.jwc</include>
<include>**/*.page</include>
<include>**/*.html</include>
</includes>
</resource>
</resources>
<plugins>
<plugin>
<groupId>org.mortbay.jetty</groupId>
<artifactId>maven-jetty-plugin</artifactId>
<version>6.1-SNAPSHOT</version>
<configuration>
<webAppSourceDirectory>src/context</webAppSourceDirectory>
<contextPath>/</contextPath>
<userRealms>
<userRealm
implementation="org.mortbay.jetty.security.HashUserRealm">
<name>Administration Area</name>
<config>etc/realm.properties</config>
</userRealm>
</userRealms>
</configuration>
<dependencies>
<dependency>
<groupId>commons-logging</groupId>
<artifactId>commons-logging</artifactId>
<version>1.0.4</version>
</dependency>
<dependency>
<groupId>log4j</groupId>
<artifactId>log4j</artifactId>
<version>1.2.13</version>
</dependency>
</dependencies>
</plugin>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-war-plugin</artifactId>
<version>2.0.2-SNAPSHOT</version>
<configuration>
<warSourceDirectory>src/context</warSourceDirectory>
<webResources>
<resource>
<directory>src/context/WEB-INF</directory>
<targetPath>WEB-INF/classes</targetPath>
<includes>
<include>hibernate.cfg.xml</include>
</includes>
</resource>
<resource>
<directory>src/java</directory>
<includes>
<include>**/*.xml</include>
<include>**/*.jwc</include>
<include>**/*.page</include>
<include>**/*.html</include>
</includes>
</resource>
<resource>
<directory>external-lib</directory>
<targetPath>WEB-INF/lib</targetPath>
<includes>
<include>jta-1.1.jar</include>
</includes>
</resource>
</webResources>
</configuration>
</plugin>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-clean-plugin</artifactId>
<version>2.2-SNAPSHOT</version>
</plugin>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-compiler-plugin</artifactId>
<version>2.1-SNAPSHOT</version>
<inherited>true</inherited>
<configuration>
<source>1.5</source>
<target>1.5</target>
</configuration>
</plugin>
</plugins>
<extensions>
<extension>
<groupId>mysql</groupId>
<artifactId>mysql-connector-java</artifactId>
<version>5.0.4</version>
</extension>
</extensions>
</build>
On 11/27/06, Mark Stang <ms...@pingidentity.com> wrote:
> Howard,
> How are you handling "Tapestry Components"? Our build guy reformatted out code layout and <sigh> once again put the .html/.jwc in a different directory from the .java file that goes with the component. His reasoning was that Maven didn't like putting the .html/.jwc somewhere other than in resources. Well now, Spindle is as confused as hell and no longer seems to be able to find files. All of them now have errors and I am not getting any "feedback" about errors.</sigh>
>
> regards,
>
> Mark
>
> Mark J. Stang
> Senior Engineer/Architect
> office: +1 303.468.2900
> mobile: +1 303.507.2833
> Ping Identity
>
>
>
> -----Original Message-----
> From: Howard Lewis Ship [mailto:hlship@gmail.com]
> Sent: Thu 11/23/2006 8:23 AM
> To: Tapestry development
> Cc: marnie.mccormack@googlemail.com
> 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 <ma...@googlemail.com> 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 <ma...@googlemail.com> 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
>
>
>
--
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
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
Re: Maven feedback ?
Posted by Jesse Kuhnert <jk...@gmail.com>.
Does this help?
<build>
<sourceDirectory>src/java</sourceDirectory>
<outputDirectory>src/context/WEB-INF/classes</outputDirectory>
<resources>
<resource>
<directory>src/java</directory>
<includes>
<include>**/*.xml</include>
<include>**/*.jwc</include>
<include>**/*.page</include>
<include>**/*.html</include>
</includes>
</resource>
</resources>
<plugins>
<plugin>
<groupId>org.mortbay.jetty</groupId>
<artifactId>maven-jetty-plugin</artifactId>
<version>6.1-SNAPSHOT</version>
<configuration>
<webAppSourceDirectory>src/context</webAppSourceDirectory>
<contextPath>/</contextPath>
<userRealms>
<userRealm
implementation="org.mortbay.jetty.security.HashUserRealm">
<name>Administration Area</name>
<config>etc/realm.properties</config>
</userRealm>
</userRealms>
</configuration>
<dependencies>
<dependency>
<groupId>commons-logging</groupId>
<artifactId>commons-logging</artifactId>
<version>1.0.4</version>
</dependency>
<dependency>
<groupId>log4j</groupId>
<artifactId>log4j</artifactId>
<version>1.2.13</version>
</dependency>
</dependencies>
</plugin>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-war-plugin</artifactId>
<version>2.0.2-SNAPSHOT</version>
<configuration>
<warSourceDirectory>src/context</warSourceDirectory>
<webResources>
<resource>
<directory>src/context/WEB-INF</directory>
<targetPath>WEB-INF/classes</targetPath>
<includes>
<include>hibernate.cfg.xml</include>
</includes>
</resource>
<resource>
<directory>src/java</directory>
<includes>
<include>**/*.xml</include>
<include>**/*.jwc</include>
<include>**/*.page</include>
<include>**/*.html</include>
</includes>
</resource>
<resource>
<directory>external-lib</directory>
<targetPath>WEB-INF/lib</targetPath>
<includes>
<include>jta-1.1.jar</include>
</includes>
</resource>
</webResources>
</configuration>
</plugin>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-clean-plugin</artifactId>
<version>2.2-SNAPSHOT</version>
</plugin>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-compiler-plugin</artifactId>
<version>2.1-SNAPSHOT</version>
<inherited>true</inherited>
<configuration>
<source>1.5</source>
<target>1.5</target>
</configuration>
</plugin>
</plugins>
<extensions>
<extension>
<groupId>mysql</groupId>
<artifactId>mysql-connector-java</artifactId>
<version>5.0.4</version>
</extension>
</extensions>
</build>
On 11/27/06, Mark Stang <ms...@pingidentity.com> wrote:
> Howard,
> How are you handling "Tapestry Components"? Our build guy reformatted out code layout and <sigh> once again put the .html/.jwc in a different directory from the .java file that goes with the component. His reasoning was that Maven didn't like putting the .html/.jwc somewhere other than in resources. Well now, Spindle is as confused as hell and no longer seems to be able to find files. All of them now have errors and I am not getting any "feedback" about errors.</sigh>
>
> regards,
>
> Mark
>
> Mark J. Stang
> Senior Engineer/Architect
> office: +1 303.468.2900
> mobile: +1 303.507.2833
> Ping Identity
>
>
>
> -----Original Message-----
> From: Howard Lewis Ship [mailto:hlship@gmail.com]
> Sent: Thu 11/23/2006 8:23 AM
> To: Tapestry development
> Cc: marnie.mccormack@googlemail.com
> 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 <ma...@googlemail.com> 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 <ma...@googlemail.com> 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
>
>
>
--
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
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org
RE: Maven feedback ?
Posted by Mark Stang <ms...@pingidentity.com>.
Howard,
How are you handling "Tapestry Components"? Our build guy reformatted out code layout and <sigh> once again put the .html/.jwc in a different directory from the .java file that goes with the component. His reasoning was that Maven didn't like putting the .html/.jwc somewhere other than in resources. Well now, Spindle is as confused as hell and no longer seems to be able to find files. All of them now have errors and I am not getting any "feedback" about errors.</sigh>
regards,
Mark
Mark J. Stang
Senior Engineer/Architect
office: +1 303.468.2900
mobile: +1 303.507.2833
Ping Identity
-----Original Message-----
From: Howard Lewis Ship [mailto:hlship@gmail.com]
Sent: Thu 11/23/2006 8:23 AM
To: Tapestry development
Cc: marnie.mccormack@googlemail.com
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 <ma...@googlemail.com> 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 <ma...@googlemail.com> 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
Re: Maven feedback ?
Posted by Howard Lewis Ship <hl...@gmail.com>.
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 <ma...@googlemail.com> 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 <ma...@googlemail.com> 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