You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@myfaces.apache.org by Sean Schofield <se...@gmail.com> on 2005/11/29 15:29:03 UTC
Maven scripts?
If anyone has a Maven2 script in progress for MyFaces I would like to
see it. I'm going to try and start one of my own if nobody produces
one. Since I'm completely new to Maven I will be needing the help of
our Maven experts. Hopefully the Tobago team and Struts lurkers will
be able to help us as well ;-)
I'm going to try and devote some time to this in between ApacheCon sessions ...
sean
Re: Maven scripts?
Posted by Bruno Aranda <br...@gmail.com>.
I guess that we can configure the pom's in a way that the current
svn:externals remain the same. I think we could only change the
svn:externals for the current folder, having this structure:
current/pom.xml
|
+------ api/pom.xml
|
+------ share/pom.xml (?)
|
+------ impl/pom.xml
|
+------ tomahawk/pom.xml
|
+------ sandbox/pom.xml
|
+------ examples/pom.xml
|
+---- simple/pom.xml
|
+---- sandbox/pom.xml
.... examples, etc
It would easier to have again a 'share' package, but I guess we can
configure the tomahawk and impl pom's to fetch the shared sources. The
dependencies for each subproject should be defined in each pom.xml.
The root pom could have the common dependencies for all the
subprojects. I would like to hear the opinion of people who is more
used to maven for this...
#1) If we respect the current structure, it is necessary to configure
the jar artifact creation in each subproject pom in order to look for
the current sources. A set of properties might be used here, as the
relative path to sources is the same in every subproject. The
advantage is that no current element is moved. The disadvantage is
that we do not follow the conventions, thing that can imply less
stability, and more learning curve for users who have got used to
maven (eg, the resources are in the src/java folder, mixed with the
java sources)
#2) If we adapt the structure to maven, we have to move the current
sources in src/main/java folders, the resources in src/main/resources
and the test to src/test/java ... This will imply a more clear order
in the myfaces resources, but would imply an update of the svn
structure and the current ant scripts, then, a branch should be
created for security and everyone who is working on the code currenlty
should commit the changes. This way is harder, but the resulting
structure is neat.
Maybe, I would go first for #1 to get the overall idea of this and,
later, I would go for #2. In case we went for #2, I think we should
change the structure before creating a possible branch for JSF1.2...
That is just some brainstorming....
Bruno
2005/11/29, Sean Schofield <se...@gmail.com>:
> According to Wendy, its *much* easier to just change the structure to
> adopt to Maven. What I would like to do is set up a bunch of SVN
> externals to link everything in the manner which Maven expects. This
> way we can build nightlies without changing the structure that
> everyone else is dealing with. I figure we can experiment and see
> whether we can live with the reorg or not.
>
> What do you think?
>
> sean
>
> On 11/29/05, Bruno Aranda <br...@gmail.com> wrote:
> > I am fairly new to maven, but I could help with that if no one has
> > already done the script. I am also migrating a private project to
> > maven, so I am already dealing with this. One question is: it is the
> > intention to maintain the current structure, or do we adapt the source
> > tree to the conventions (eg. src/main/java, src/main/resources). IMO,
> > we need just to provide the pom.xml files for each subproject and a
> > general pom.xml that calls the subprojects poms...
> >
> > Regards,
> >
> > Bruno
> >
> >
> > 2005/11/29, Sean Schofield <se...@gmail.com>:
> > > If anyone has a Maven2 script in progress for MyFaces I would like to
> > > see it. I'm going to try and start one of my own if nobody produces
> > > one. Since I'm completely new to Maven I will be needing the help of
> > > our Maven experts. Hopefully the Tobago team and Struts lurkers will
> > > be able to help us as well ;-)
> > >
> > > I'm going to try and devote some time to this in between ApacheCon sessions ...
> > >
> > > sean
> > >
> >
>
Re: Maven scripts?
Posted by Sean Schofield <se...@gmail.com>.
@ Brend: Thanks for the info.
@ Everyone: I moved all of the resources in the test repository. So
now they are included in the jars.
The only major thing left is transforming and including the TLD's.
Then its on to examples, javadoc and site. So far so good ...
sean
On 12/1/05, Bernd Bohmann <be...@atanion.com> wrote:
> Maybe: http://jira.codehaus.org/browse/MNG-1615
>
> In
>
> maven-jar-plugin/src/main/java/org/apache/maven/plugin/jar/AbstractJarMojo.java
>
> is a @todo Add license files in META-INF directory.
>
> Sean Schofield schrieb:
> > Quick question. How do you include LICENSE.txt in your jar file.
> > Isn't it supposed to be automatic if its in your top level dir?
> >
> > sean
> >
> > On 12/1/05, Sean Schofield <se...@gmail.com> wrote:
> >
> >>I set up a wiki[1] to record the steps needed. If anyone wants to
> >>move things around feel free. Just be sure to update the wiki so (a)
> >>we know you did it (no emails from the test repos) and (b) we remember
> >>to do it again when its time to reorg for real.
> >>
> >>sean
> >>
> >>[1] http://wiki.apache.org/myfaces/Maven_Reorg
> >>
> >>On 11/30/05, Sean Schofield <se...@gmail.com> wrote:
> >>
> >>>I've created a myfaces project in the *test* SVN repostiory[1]. I've
> >>>only included the src files but the "resources" are also mixed in
> >>>there and will need to come out. This is just for test purposes so
> >>>that we can tweak the build.
> >>>
> >>>Maybe we should also start a wiki as we move things around so that we
> >>>know what to do when we are ready for the real reorg. For now lets
> >>>play with this repos (feel free to add stuff and modify the poms.) I
> >>>could use some help with the resources next.
> >>>
> >>>mvn install from the root should do everything you need.
> >>>
> >>>Also, the site stuff is using a dev version (in my local repo) of the
> >>>javadoc plugin but everything will be fine if you don't run the site
> >>>command.
> >>>
> >>>
> >>>sean
> >>>
> >>>[1] http://svn.apache.org/repos/test/myfaces/
> >>>
> >>>
> >>>
> >>>On 11/30/05, Bernd Bohmann <be...@atanion.com> wrote:
> >>>
> >>>>Hello,
> >>>>
> >>>>I would prefer following approach:
> >>>>
> >>>>First we should create a 'common' package.
> >>>>(proposal is done)
> >>>>
> >>>>Then we move the source to the src/main/java,
> >>>>src/main/resources and src/test/java folders
> >>>>and change the ant scripts.
> >>>>
> >>>>Afterwards we can start creating the pom's.
> >>>>
> >>>>Until the maven build is stable the build files and the pom's exists in
> >>>>parallel.
> >>>>
> >>>>After the maven build is stable we should define the names of the
> >>>>artifacts and change the directory names to the name of the artifact.
> >>>>For example:
> >>>>common -> myfaces-common
> >>>>sandbox -> myfaces-sandbox
> >>>>impl -> myfaces-imp
> >>>>api -> myfaces-api
> >>>>...
> >>>>
> >>>>I have no real opinion now, how the sites should organized.
> >>>>
> >>>>Best Regards
> >>>>
> >>>>Bernd
> >>>>
> >>>
> >
>
> --
> Dipl.-Ing. Bernd Bohmann - Atanion GmbH - Software Development
> Bismarckstr. 13, 26122 Oldenburg, http://www.atanion.com
> phone: +49 441 4082312, mobile: +49 173 8839471, fax: +49 441 4082333
>
Re: Maven scripts?
Posted by Bernd Bohmann <be...@atanion.com>.
Maybe: http://jira.codehaus.org/browse/MNG-1615
In
maven-jar-plugin/src/main/java/org/apache/maven/plugin/jar/AbstractJarMojo.java
is a @todo Add license files in META-INF directory.
Sean Schofield schrieb:
> Quick question. How do you include LICENSE.txt in your jar file.
> Isn't it supposed to be automatic if its in your top level dir?
>
> sean
>
> On 12/1/05, Sean Schofield <se...@gmail.com> wrote:
>
>>I set up a wiki[1] to record the steps needed. If anyone wants to
>>move things around feel free. Just be sure to update the wiki so (a)
>>we know you did it (no emails from the test repos) and (b) we remember
>>to do it again when its time to reorg for real.
>>
>>sean
>>
>>[1] http://wiki.apache.org/myfaces/Maven_Reorg
>>
>>On 11/30/05, Sean Schofield <se...@gmail.com> wrote:
>>
>>>I've created a myfaces project in the *test* SVN repostiory[1]. I've
>>>only included the src files but the "resources" are also mixed in
>>>there and will need to come out. This is just for test purposes so
>>>that we can tweak the build.
>>>
>>>Maybe we should also start a wiki as we move things around so that we
>>>know what to do when we are ready for the real reorg. For now lets
>>>play with this repos (feel free to add stuff and modify the poms.) I
>>>could use some help with the resources next.
>>>
>>>mvn install from the root should do everything you need.
>>>
>>>Also, the site stuff is using a dev version (in my local repo) of the
>>>javadoc plugin but everything will be fine if you don't run the site
>>>command.
>>>
>>>
>>>sean
>>>
>>>[1] http://svn.apache.org/repos/test/myfaces/
>>>
>>>
>>>
>>>On 11/30/05, Bernd Bohmann <be...@atanion.com> wrote:
>>>
>>>>Hello,
>>>>
>>>>I would prefer following approach:
>>>>
>>>>First we should create a 'common' package.
>>>>(proposal is done)
>>>>
>>>>Then we move the source to the src/main/java,
>>>>src/main/resources and src/test/java folders
>>>>and change the ant scripts.
>>>>
>>>>Afterwards we can start creating the pom's.
>>>>
>>>>Until the maven build is stable the build files and the pom's exists in
>>>>parallel.
>>>>
>>>>After the maven build is stable we should define the names of the
>>>>artifacts and change the directory names to the name of the artifact.
>>>>For example:
>>>>common -> myfaces-common
>>>>sandbox -> myfaces-sandbox
>>>>impl -> myfaces-imp
>>>>api -> myfaces-api
>>>>...
>>>>
>>>>I have no real opinion now, how the sites should organized.
>>>>
>>>>Best Regards
>>>>
>>>>Bernd
>>>>
>>>
>
--
Dipl.-Ing. Bernd Bohmann - Atanion GmbH - Software Development
Bismarckstr. 13, 26122 Oldenburg, http://www.atanion.com
phone: +49 441 4082312, mobile: +49 173 8839471, fax: +49 441 4082333
Re: Maven scripts?
Posted by Mario Ivankovits <ma...@ops.co.at>.
Sean Schofield wrote:
> Quick question. How do you include LICENSE.txt in your jar file.
> Isn't it supposed to be automatic if its in your top level dir?
>
I am not an expert, but my project.xml contains
<licenses>
<license>
<name>The Apache Software License, Version 2.0</name>
<url>/LICENSE.txt</url>
<distribution>repo</distribution>
</license>
</licenses>
bundling other stuff you have to add a resource
<build>
<resources>
.....
<resource>
<directory>${basedir}</directory>
<targetPath>META-INF</targetPath>
<includes>
<include>NOTICE.txt</include>
</includes>
</resource>
</resources>
Hope that helps!
Mario
Re: Maven scripts?
Posted by Sean Schofield <se...@gmail.com>.
Quick question. How do you include LICENSE.txt in your jar file.
Isn't it supposed to be automatic if its in your top level dir?
sean
On 12/1/05, Sean Schofield <se...@gmail.com> wrote:
> I set up a wiki[1] to record the steps needed. If anyone wants to
> move things around feel free. Just be sure to update the wiki so (a)
> we know you did it (no emails from the test repos) and (b) we remember
> to do it again when its time to reorg for real.
>
> sean
>
> [1] http://wiki.apache.org/myfaces/Maven_Reorg
>
> On 11/30/05, Sean Schofield <se...@gmail.com> wrote:
> > I've created a myfaces project in the *test* SVN repostiory[1]. I've
> > only included the src files but the "resources" are also mixed in
> > there and will need to come out. This is just for test purposes so
> > that we can tweak the build.
> >
> > Maybe we should also start a wiki as we move things around so that we
> > know what to do when we are ready for the real reorg. For now lets
> > play with this repos (feel free to add stuff and modify the poms.) I
> > could use some help with the resources next.
> >
> > mvn install from the root should do everything you need.
> >
> > Also, the site stuff is using a dev version (in my local repo) of the
> > javadoc plugin but everything will be fine if you don't run the site
> > command.
> >
> >
> > sean
> >
> > [1] http://svn.apache.org/repos/test/myfaces/
> >
> >
> >
> > On 11/30/05, Bernd Bohmann <be...@atanion.com> wrote:
> > > Hello,
> > >
> > > I would prefer following approach:
> > >
> > > First we should create a 'common' package.
> > > (proposal is done)
> > >
> > > Then we move the source to the src/main/java,
> > > src/main/resources and src/test/java folders
> > > and change the ant scripts.
> > >
> > > Afterwards we can start creating the pom's.
> > >
> > > Until the maven build is stable the build files and the pom's exists in
> > > parallel.
> > >
> > > After the maven build is stable we should define the names of the
> > > artifacts and change the directory names to the name of the artifact.
> > > For example:
> > > common -> myfaces-common
> > > sandbox -> myfaces-sandbox
> > > impl -> myfaces-imp
> > > api -> myfaces-api
> > > ...
> > >
> > > I have no real opinion now, how the sites should organized.
> > >
> > > Best Regards
> > >
> > > Bernd
> > >
> >
>
Re: Maven scripts?
Posted by Sean Schofield <se...@gmail.com>.
I set up a wiki[1] to record the steps needed. If anyone wants to
move things around feel free. Just be sure to update the wiki so (a)
we know you did it (no emails from the test repos) and (b) we remember
to do it again when its time to reorg for real.
sean
[1] http://wiki.apache.org/myfaces/Maven_Reorg
On 11/30/05, Sean Schofield <se...@gmail.com> wrote:
> I've created a myfaces project in the *test* SVN repostiory[1]. I've
> only included the src files but the "resources" are also mixed in
> there and will need to come out. This is just for test purposes so
> that we can tweak the build.
>
> Maybe we should also start a wiki as we move things around so that we
> know what to do when we are ready for the real reorg. For now lets
> play with this repos (feel free to add stuff and modify the poms.) I
> could use some help with the resources next.
>
> mvn install from the root should do everything you need.
>
> Also, the site stuff is using a dev version (in my local repo) of the
> javadoc plugin but everything will be fine if you don't run the site
> command.
>
>
> sean
>
> [1] http://svn.apache.org/repos/test/myfaces/
>
>
>
> On 11/30/05, Bernd Bohmann <be...@atanion.com> wrote:
> > Hello,
> >
> > I would prefer following approach:
> >
> > First we should create a 'common' package.
> > (proposal is done)
> >
> > Then we move the source to the src/main/java,
> > src/main/resources and src/test/java folders
> > and change the ant scripts.
> >
> > Afterwards we can start creating the pom's.
> >
> > Until the maven build is stable the build files and the pom's exists in
> > parallel.
> >
> > After the maven build is stable we should define the names of the
> > artifacts and change the directory names to the name of the artifact.
> > For example:
> > common -> myfaces-common
> > sandbox -> myfaces-sandbox
> > impl -> myfaces-imp
> > api -> myfaces-api
> > ...
> >
> > I have no real opinion now, how the sites should organized.
> >
> > Best Regards
> >
> > Bernd
> >
>
Re: Maven scripts?
Posted by Sean Schofield <se...@gmail.com>.
I've created a myfaces project in the *test* SVN repostiory[1]. I've
only included the src files but the "resources" are also mixed in
there and will need to come out. This is just for test purposes so
that we can tweak the build.
Maybe we should also start a wiki as we move things around so that we
know what to do when we are ready for the real reorg. For now lets
play with this repos (feel free to add stuff and modify the poms.) I
could use some help with the resources next.
mvn install from the root should do everything you need.
Also, the site stuff is using a dev version (in my local repo) of the
javadoc plugin but everything will be fine if you don't run the site
command.
sean
[1] http://svn.apache.org/repos/test/myfaces/
On 11/30/05, Bernd Bohmann <be...@atanion.com> wrote:
> Hello,
>
> I would prefer following approach:
>
> First we should create a 'common' package.
> (proposal is done)
>
> Then we move the source to the src/main/java,
> src/main/resources and src/test/java folders
> and change the ant scripts.
>
> Afterwards we can start creating the pom's.
>
> Until the maven build is stable the build files and the pom's exists in
> parallel.
>
> After the maven build is stable we should define the names of the
> artifacts and change the directory names to the name of the artifact.
> For example:
> common -> myfaces-common
> sandbox -> myfaces-sandbox
> impl -> myfaces-imp
> api -> myfaces-api
> ...
>
> I have no real opinion now, how the sites should organized.
>
> Best Regards
>
> Bernd
>
Re: Maven scripts?
Posted by Bernd Bohmann <be...@atanion.com>.
Hello,
I would prefer following approach:
First we should create a 'common' package.
(proposal is done)
Then we move the source to the src/main/java,
src/main/resources and src/test/java folders
and change the ant scripts.
Afterwards we can start creating the pom's.
Until the maven build is stable the build files and the pom's exists in
parallel.
After the maven build is stable we should define the names of the
artifacts and change the directory names to the name of the artifact.
For example:
common -> myfaces-common
sandbox -> myfaces-sandbox
impl -> myfaces-imp
api -> myfaces-api
...
I have no real opinion now, how the sites should organized.
Best Regards
Bernd
Re: Maven scripts?
Posted by Sean Schofield <se...@gmail.com>.
> Keep in mind, that's a Maven 1 site. I haven't quite managed to
> convince m2 to do the same thing, but I'm getting closer.
Point taken.
> Watch out for http://jira.codehaus.org/browse/MNG-661, m2 will build
> the site for each module, but won't aggregate it so you can preview
> it.
Yeah I saw that one while searching the archives. I got it open in my
other browser tab right now ;-)
> (Fix version 2.0.1? I never know whether that means it's already
> fixed, or planned to be... different projects seem to use it in
> different ways.)
LOL we have been struggling with that one ourselves!
> Those come from the Project Info Plugin. Looks like you can pick what
> things show up there:
> http://maven.apache.org/plugins/maven-project-info-reports-plugin/howto.html
> (Suppressing this at the module level doesn't make sense-- it's where
> 'Dependencies' will appear, and those will be different for each
> module.)
Is there a way to supress *part* of this output using the plug in?
> Those show up in "Project Reports" and are also configured in
> the<reporting> section. For example, to get CheckStyle:
> <reporting>
> <plugins>
> <plugin>
> <groupId>org.apache.maven.plugins</groupId>
> <artifactId>maven-checkstyle-plugin</artifactId>
> <version>2.0-beta-1</version>
> </plugin>
> </plugins>
> </reporting>
Thanks for the tip.
> HTH,
It did.
> Wendy
Sean
ps. Are you going to be at Apache Con?
Re: Maven scripts?
Posted by Wendy Smoak <ws...@gmail.com>.
On 11/29/05, Sean Schofield <se...@gmail.com> wrote:
> I have a question about Maven website building. It looks like our
> subprojects match up pretty nicely with the Maven "module" concept but
> I'm wondering what the final website will look like. Is it possible
> to link modules into your top level module and site? It looks like
> maybe you can from what the Struts team has done.
Keep in mind, that's a Maven 1 site. I haven't quite managed to
convince m2 to do the same thing, but I'm getting closer.
Watch out for http://jira.codehaus.org/browse/MNG-661, m2 will build
the site for each module, but won't aggregate it so you can preview
it. (Fix version 2.0.1? I never know whether that means it's already
fixed, or planned to be... different projects seem to use it in
different ways.)
> There are certain items that I think should be generated at the top
> project level (list of contributors, mailing lists, issue tracking,
> etc.)
Those come from the Project Info Plugin. Looks like you can pick what
things show up there:
http://maven.apache.org/plugins/maven-project-info-reports-plugin/howto.html
(Suppressing this at the module level doesn't make sense-- it's where
'Dependencies' will appear, and those will be different for each
module.)
> Then there are other items that would be nice to have at the
> subproject level (javadocs, general overview and unit tests.) What
> are the options with Maven as far as this goes?
Those show up in "Project Reports" and are also configured in
the<reporting> section. For example, to get CheckStyle:
<reporting>
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-checkstyle-plugin</artifactId>
<version>2.0-beta-1</version>
</plugin>
</plugins>
</reporting>
HTH,
--
Wendy
Re: Maven scripts?
Posted by Sean Schofield <se...@gmail.com>.
I agree that we probably will just reorg to comply with Maven (should
we vote to go forward.)
I have a question about Maven website building. It looks like our
subprojects match up pretty nicely with the Maven "module" concept but
I'm wondering what the final website will look like. Is it possible
to link modules into your top level module and site? It looks like
maybe you can from what the Struts team has done.
There are certain items that I think should be generated at the top
project level (list of contributors, mailing lists, issue tracking,
etc.) Then there are other items that would be nice to have at the
subproject level (javadocs, general overview and unit tests.) What
are the options with Maven as far as this goes?
sean
On 11/29/05, Bruno Aranda <br...@gmail.com> wrote:
> +1 For making a copy of the repository, move things and start playing
> (Wendy's script is also good idea). Although it is needed more effort
> now it would be easier to maintain in the future... I would create the
> new mavenized structure and, when we are happing with it, make the
> head adopt the new structure,
>
> Bruno
>
> 2005/11/29, Sean Schofield <se...@gmail.com>:
> > My thinking on the externals was that we create a folder called
> > myfaces-maven (or something) and have externals that reorg everything
> > in the way that Maven wants. This wouldn't be a permanent solution,
> > just a convenient way of building the latest and greatest without
> > copying everything outright everytime.
> >
> > Another idea would be to copy the repository to the "test" area of the
> > SVN server (if it still exists) and then just start moving stuff
> > around and skip the external stuff.
> >
> > I looked at Wendy's wiki. That is another interesting approach.
> >
> > Ultimately I need to know more about Maven and what it needs before I
> > can reach a personal conclusion on which method will work best.
> >
> > I am hoping that we can cut down on all of the externals in the new
> > Maven way of doing things. I like the "one build to rule them all"
> > approach but its a real PITA changing the externals for all of those
> > build dirs. Ultimately I would like the only externals to be for the
> > TLD entities and stuff where its truly needed.
> >
> > OK back to my Maven research ...
> >
> > sean
> >
> > On 11/29/05, Wendy Smoak <ws...@gmail.com> wrote:
> > > On 11/29/05, Sean Schofield <se...@gmail.com> wrote:
> > >
> > > > According to Wendy, its *much* easier to just change the structure to
> > > > adopt to Maven. What I would like to do is set up a bunch of SVN
> > > > externals to link everything in the manner which Maven expects. This
> > > > way we can build nightlies without changing the structure that
> > > > everyone else is dealing with. I figure we can experiment and see
> > > > whether we can live with the reorg or not.
> > > >
> > > > What do you think?
> > >
> > > Did you get Colin's m2 build files? I took a look at them and sent
> > > him some feedback, but that was a while ago.
> > >
> > > The svn:externals thing only works for directories, not individual
> > > files. If that doesn't get you far enough, take a look at the Shale
> > > m2 build experiment. I check out from svn and move everything around
> > > with a shell script:
> > > http://wiki.wsmoak.net/cgi-bin/wiki.pl?ShaleMaven2
> > >
> > > I'm sure there will be plenty of people at ApacheCon who can help. :)
> > >
> > > --
> > > Wendy
> > >
> >
>
Re: Maven scripts?
Posted by Bruno Aranda <br...@gmail.com>.
+1 For making a copy of the repository, move things and start playing
(Wendy's script is also good idea). Although it is needed more effort
now it would be easier to maintain in the future... I would create the
new mavenized structure and, when we are happing with it, make the
head adopt the new structure,
Bruno
2005/11/29, Sean Schofield <se...@gmail.com>:
> My thinking on the externals was that we create a folder called
> myfaces-maven (or something) and have externals that reorg everything
> in the way that Maven wants. This wouldn't be a permanent solution,
> just a convenient way of building the latest and greatest without
> copying everything outright everytime.
>
> Another idea would be to copy the repository to the "test" area of the
> SVN server (if it still exists) and then just start moving stuff
> around and skip the external stuff.
>
> I looked at Wendy's wiki. That is another interesting approach.
>
> Ultimately I need to know more about Maven and what it needs before I
> can reach a personal conclusion on which method will work best.
>
> I am hoping that we can cut down on all of the externals in the new
> Maven way of doing things. I like the "one build to rule them all"
> approach but its a real PITA changing the externals for all of those
> build dirs. Ultimately I would like the only externals to be for the
> TLD entities and stuff where its truly needed.
>
> OK back to my Maven research ...
>
> sean
>
> On 11/29/05, Wendy Smoak <ws...@gmail.com> wrote:
> > On 11/29/05, Sean Schofield <se...@gmail.com> wrote:
> >
> > > According to Wendy, its *much* easier to just change the structure to
> > > adopt to Maven. What I would like to do is set up a bunch of SVN
> > > externals to link everything in the manner which Maven expects. This
> > > way we can build nightlies without changing the structure that
> > > everyone else is dealing with. I figure we can experiment and see
> > > whether we can live with the reorg or not.
> > >
> > > What do you think?
> >
> > Did you get Colin's m2 build files? I took a look at them and sent
> > him some feedback, but that was a while ago.
> >
> > The svn:externals thing only works for directories, not individual
> > files. If that doesn't get you far enough, take a look at the Shale
> > m2 build experiment. I check out from svn and move everything around
> > with a shell script:
> > http://wiki.wsmoak.net/cgi-bin/wiki.pl?ShaleMaven2
> >
> > I'm sure there will be plenty of people at ApacheCon who can help. :)
> >
> > --
> > Wendy
> >
>
Re: Maven scripts?
Posted by Sean Schofield <se...@gmail.com>.
My thinking on the externals was that we create a folder called
myfaces-maven (or something) and have externals that reorg everything
in the way that Maven wants. This wouldn't be a permanent solution,
just a convenient way of building the latest and greatest without
copying everything outright everytime.
Another idea would be to copy the repository to the "test" area of the
SVN server (if it still exists) and then just start moving stuff
around and skip the external stuff.
I looked at Wendy's wiki. That is another interesting approach.
Ultimately I need to know more about Maven and what it needs before I
can reach a personal conclusion on which method will work best.
I am hoping that we can cut down on all of the externals in the new
Maven way of doing things. I like the "one build to rule them all"
approach but its a real PITA changing the externals for all of those
build dirs. Ultimately I would like the only externals to be for the
TLD entities and stuff where its truly needed.
OK back to my Maven research ...
sean
On 11/29/05, Wendy Smoak <ws...@gmail.com> wrote:
> On 11/29/05, Sean Schofield <se...@gmail.com> wrote:
>
> > According to Wendy, its *much* easier to just change the structure to
> > adopt to Maven. What I would like to do is set up a bunch of SVN
> > externals to link everything in the manner which Maven expects. This
> > way we can build nightlies without changing the structure that
> > everyone else is dealing with. I figure we can experiment and see
> > whether we can live with the reorg or not.
> >
> > What do you think?
>
> Did you get Colin's m2 build files? I took a look at them and sent
> him some feedback, but that was a while ago.
>
> The svn:externals thing only works for directories, not individual
> files. If that doesn't get you far enough, take a look at the Shale
> m2 build experiment. I check out from svn and move everything around
> with a shell script:
> http://wiki.wsmoak.net/cgi-bin/wiki.pl?ShaleMaven2
>
> I'm sure there will be plenty of people at ApacheCon who can help. :)
>
> --
> Wendy
>
Re: Maven scripts?
Posted by Wendy Smoak <ws...@gmail.com>.
On 11/29/05, Sean Schofield <se...@gmail.com> wrote:
> According to Wendy, its *much* easier to just change the structure to
> adopt to Maven. What I would like to do is set up a bunch of SVN
> externals to link everything in the manner which Maven expects. This
> way we can build nightlies without changing the structure that
> everyone else is dealing with. I figure we can experiment and see
> whether we can live with the reorg or not.
>
> What do you think?
Did you get Colin's m2 build files? I took a look at them and sent
him some feedback, but that was a while ago.
The svn:externals thing only works for directories, not individual
files. If that doesn't get you far enough, take a look at the Shale
m2 build experiment. I check out from svn and move everything around
with a shell script:
http://wiki.wsmoak.net/cgi-bin/wiki.pl?ShaleMaven2
I'm sure there will be plenty of people at ApacheCon who can help. :)
--
Wendy
Re: Maven scripts?
Posted by Sean Schofield <se...@gmail.com>.
According to Wendy, its *much* easier to just change the structure to
adopt to Maven. What I would like to do is set up a bunch of SVN
externals to link everything in the manner which Maven expects. This
way we can build nightlies without changing the structure that
everyone else is dealing with. I figure we can experiment and see
whether we can live with the reorg or not.
What do you think?
sean
On 11/29/05, Bruno Aranda <br...@gmail.com> wrote:
> I am fairly new to maven, but I could help with that if no one has
> already done the script. I am also migrating a private project to
> maven, so I am already dealing with this. One question is: it is the
> intention to maintain the current structure, or do we adapt the source
> tree to the conventions (eg. src/main/java, src/main/resources). IMO,
> we need just to provide the pom.xml files for each subproject and a
> general pom.xml that calls the subprojects poms...
>
> Regards,
>
> Bruno
>
>
> 2005/11/29, Sean Schofield <se...@gmail.com>:
> > If anyone has a Maven2 script in progress for MyFaces I would like to
> > see it. I'm going to try and start one of my own if nobody produces
> > one. Since I'm completely new to Maven I will be needing the help of
> > our Maven experts. Hopefully the Tobago team and Struts lurkers will
> > be able to help us as well ;-)
> >
> > I'm going to try and devote some time to this in between ApacheCon sessions ...
> >
> > sean
> >
>
Re: Maven scripts?
Posted by Bruno Aranda <br...@gmail.com>.
I am fairly new to maven, but I could help with that if no one has
already done the script. I am also migrating a private project to
maven, so I am already dealing with this. One question is: it is the
intention to maintain the current structure, or do we adapt the source
tree to the conventions (eg. src/main/java, src/main/resources). IMO,
we need just to provide the pom.xml files for each subproject and a
general pom.xml that calls the subprojects poms...
Regards,
Bruno
2005/11/29, Sean Schofield <se...@gmail.com>:
> If anyone has a Maven2 script in progress for MyFaces I would like to
> see it. I'm going to try and start one of my own if nobody produces
> one. Since I'm completely new to Maven I will be needing the help of
> our Maven experts. Hopefully the Tobago team and Struts lurkers will
> be able to help us as well ;-)
>
> I'm going to try and devote some time to this in between ApacheCon sessions ...
>
> sean
>