You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by Phil Steitz <ph...@gmail.com> on 2006/08/10 05:21:07 UTC
[nightly build] m2 support - a little help, pls
I would like to add m2 support to the nightly build script, but am
still an m2 newbie, so could use a little help. I thought that
starting with [csv] would be good, since the migration page lists it
as "done". I have a couple of questions.
1. It seems to use pom inheritence, which I am sure someone will
convince me is a good thing, despite the fact that my first experience
with it is a build failure because of it. How do I find and I guess
"install" the commons-sandbox-parent? How do we indicate to users
that they are going to need to set this up for builds to work? Do we
really need this?
2. Properties files seem to be replaced by settings.xml. Is this
where we designate repo lists? If so, can someone commit a
settings.xml.sample?
3. I assume that the reference to 'minotaur' in the
distributionManagement section of the csv pom should be changed to
'people'? Once this is fixed, I assume "deploy" will work correctly
using the ssh key that the script is using to connect to people now.
4. The dist plugin seems to be gone and the release plugin looks like
it is really just aiming to deploy jars and tag releases. Should I
use ant tasks to roll the distros manually or is there some m2 plugin
that will do this?
Thanks!
Phil
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: [nightly build] m2 support - a little help, pls
Posted by Dennis Lundberg <de...@apache.org>.
Stephen Colebourne wrote:
> Henri Yandell wrote:
>> Feel free to use [csv] as a test case if you want. I'm ready to delete
>> the maven-1 stuff and be fully on maven-2; I just deployed the site
>> from maven-2 and it looks good.
>
> It does look a little different from current commons proper styling
> though, eg. [lang].
>
> Note the larger bar below the header, and the lack of underlines in the
> left navigation.
There are two ways we can go to alter the site appearance in Maven 2:
1. Easy route: add css and use a custom velocity template
2. Solid route: create a commons skin [1]
It's easier to go with 1 to start with. It can be turned into 2 later on.
[1] http://maven.apache.org/plugins/maven-site-plugin/creating-a-skin.html
>
> We may choose to change the style at this point, however we shouldn't
> loose the ability to add ApacheCon images easily, currently achieved via
> a linked remote css file.
> http://wiki.apache.org/jakarta-commons/MavenWebsiteStucture
> (there may be a better way than this in M2)
>
> Stephen
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: commons-dev-help@jakarta.apache.org
>
--
Dennis Lundberg
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: [nightly build] m2 support - a little help, pls
Posted by Stephen Colebourne <sc...@btopenworld.com>.
Henri Yandell wrote:
> Feel free to use [csv] as a test case if you want. I'm ready to delete
> the maven-1 stuff and be fully on maven-2; I just deployed the site
> from maven-2 and it looks good.
It does look a little different from current commons proper styling
though, eg. [lang].
Note the larger bar below the header, and the lack of underlines in the
left navigation.
We may choose to change the style at this point, however we shouldn't
loose the ability to add ApacheCon images easily, currently achieved via
a linked remote css file.
http://wiki.apache.org/jakarta-commons/MavenWebsiteStucture
(there may be a better way than this in M2)
Stephen
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: [nightly build] m2 support - a little help, pls
Posted by Henri Yandell <fl...@gmail.com>.
On 8/11/06, Phil Steitz <ph...@gmail.com> wrote:
> On 8/10/06, Henri Yandell <fl...@gmail.com> wrote:
> > Feel free to use [csv] as a test case if you want. I'm ready to delete
> > the maven-1 stuff
>
> I don't see why we should do that (delete maven 1 builds) for a while.
Couple of reasons for me:
*) The back of the mind/gut screaming at having 3 separate build systems.
*) I like deleting/simplifying things, so it's a good carrot :)
Will try to grokk the m2 nightly problem a bit later,
Hen
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: [nightly build] m2 support - a little help, pls
Posted by Phil Steitz <ph...@gmail.com>.
On 8/10/06, Henri Yandell <fl...@gmail.com> wrote:
> Feel free to use [csv] as a test case if you want. I'm ready to delete
> the maven-1 stuff
I don't see why we should do that (delete maven 1 builds) for a while.
>and be fully on maven-2; I just deployed the site
> from maven-2 and it looks good.
>
> I'm going to go ahead and extract a jakarta-pom out of the
> commons-sandbox one, and then make a commons-proper pom. Just to make
> your life more difficult :)
>
> Hen
One problem that I am running into is that the "finalName" parameter
in the assembly docs does not seem to work from the command line, so I
can't use the same trick that I did for the maven 1 builds to get the
timestamp shoved into the artifact names. Also, since I will be using
the deploy goal to publish the snapshot jars instead of copying them
manually (at least I hope to do it this way), the updating symlinks
strategy to keep a -SNAPSHOT link pointing to the latest nightly while
a weeks worth stay available in the repo will not work. So, for maven
2, it would be simpler if we just agreed to use "overwrite" semantics
- i.e., only one jar published, overwritten every night. I guess I
could munge the names manually for the tarballs and keep a week's
worth around in /nightlies.
Sound OK?
Phil
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: commons-dev-help@jakarta.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: [nightly build] m2 support - a little help, pls
Posted by Henri Yandell <fl...@gmail.com>.
Feel free to use [csv] as a test case if you want. I'm ready to delete
the maven-1 stuff and be fully on maven-2; I just deployed the site
from maven-2 and it looks good.
I'm going to go ahead and extract a jakarta-pom out of the
commons-sandbox one, and then make a commons-proper pom. Just to make
your life more difficult :)
Hen
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: [nightly build] m2 support - a little help, pls
Posted by Phil Steitz <ph...@gmail.com>.
On 8/9/06, Craig McClanahan <cr...@apache.org> wrote:
> On 8/9/06, Phil Steitz <ph...@gmail.com> wrote:
> >
> > On 8/9/06, Brett Porter <br...@apache.org> wrote:
> > > On 10/08/2006 1:21 PM, Phil Steitz wrote:
> > > > I would like to add m2 support to the nightly build script, but am
> > > > still an m2 newbie, so could use a little help. I thought that
> > > > starting with [csv] would be good, since the migration page lists it
> > > > as "done". I have a couple of questions.
> > > >
> > > > 1. It seems to use pom inheritence, which I am sure someone will
> > > > convince me is a good thing, despite the fact that my first experience
> > > > with it is a build failure because of it. How do I find and I guess
> > > > "install" the commons-sandbox-parent?
> > >
> > > It's in sandbox-trunks for now
> >
> > OK, so I just did "mvn install" from the root of sandbox trunk and I
> > guess that did it.
>
>
> Keep the faith Phil ... despite some frustrations with how Maven resolves
> conflicts over requests for differing versions of the same dependency,
> there's a lot of good stuff here :-).
>
Yes indeed. Just need to learn it and get some docs out so we can all
take advantage of it.
> The Struts, Shale, and MyFaces projects have evolved some pretty intricate
> multiple level build environments with Maven2 that might be worth looking at
> for inspiration and ideas. The commons world is a subset of that kind of
> complexity (because it's not likely to be hierarchical to more than one
> level, since each library is pretty much independent), but there's good
> ideas in those POMs.
Thanks! Will definitely have a look.
>
<snip/>
>
> This was actually one of my favorite discoveries about m2. For Shale, I
> took the philosophy that a release artifact should include:
> * The binary artifacts (jar, war, or whatever)
> * A directory containing all the binary dependencies
You mean bundling all of the dependent jars? Doesn' t that sort of
defeat the purpose of the maven repo setup?
> * Javadocs
> * Sources
> * And the pom.xml in the top level directory so that, if you have
> Maven2 installed, you can just type "mvn install" in the top level
> directory of the release, and it reconstitutes itself.
>
Do you think we should do away with the source vs binary distinction?
Looks like you are pretty much including everything there.
> Check out "framework/shale-dist" (in the Shale repository) for how this
> works for the "framework" release artifact (which accumulates a bunch of
> individual jars from sub-projects ... could do something like this for an
> uber-commons release pretty easily once everything was m2-ized), or how each
> of the webapps under framework/shale-apps can create a self contained
> release that includes all of the above stuff (similar to what you might do
> for an individual commons library).
Interesting. Definitely more complex than what we have in commons,
but lots of good examples. We collectively need to get itches and
cycles to get this experience into /dev docs for apache projects and
to help improve the maven docs in general.
Thanks!
Phil
>
>
> Phil
>
>
> Craig
>
>
> ---------------------------------------------------------------------
> > To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: commons-dev-help@jakarta.apache.org
> >
> >
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: [nightly build] m2 support - a little help, pls
Posted by Craig McClanahan <cr...@apache.org>.
On 8/9/06, Phil Steitz <ph...@gmail.com> wrote:
>
> On 8/9/06, Brett Porter <br...@apache.org> wrote:
> > On 10/08/2006 1:21 PM, Phil Steitz wrote:
> > > I would like to add m2 support to the nightly build script, but am
> > > still an m2 newbie, so could use a little help. I thought that
> > > starting with [csv] would be good, since the migration page lists it
> > > as "done". I have a couple of questions.
> > >
> > > 1. It seems to use pom inheritence, which I am sure someone will
> > > convince me is a good thing, despite the fact that my first experience
> > > with it is a build failure because of it. How do I find and I guess
> > > "install" the commons-sandbox-parent?
> >
> > It's in sandbox-trunks for now
>
> OK, so I just did "mvn install" from the root of sandbox trunk and I
> guess that did it.
Keep the faith Phil ... despite some frustrations with how Maven resolves
conflicts over requests for differing versions of the same dependency,
there's a lot of good stuff here :-).
>
> > How do we indicate to users
> > > that they are going to need to set this up for builds to work?
> >
> > It shouldn't be necessary. If the parent is finalised and released as an
> > independant artifact first, it will be downloaded from the repository
> > like any dependency.
> >
> > Do we
> > > really need this?
> >
> > It's extremely useful for reducing duplication and making changes (such
> > as repository location) easier, and also allows the same for any
> > generated sites, so I'd say yes :)
>
> OK, so the repo list will eventually go there? When it failed once it
> displayed a list of repos including apache.snapshots that I could not
> figure out where it was getting. I guess those are defaults and the
> right way to set things up is to use repository elements in the pom.
> So these should probably be specified then in the sandbox-parent and
> proper-parent.
The Struts, Shale, and MyFaces projects have evolved some pretty intricate
multiple level build environments with Maven2 that might be worth looking at
for inspiration and ideas. The commons world is a subset of that kind of
complexity (because it's not likely to be hierarchical to more than one
level, since each library is pretty much independent), but there's good
ideas in those POMs.
>
> > >
> > > 2. Properties files seem to be replaced by settings.xml. Is this
> > > where we designate repo lists? If so, can someone commit a
> > > settings.xml.sample?
> >
> > project.properties is replaced by pom.xml (ie, plugin configuration is
> > brought in). This is all you should need to commit to SVN, and it can
> > contain repository references if needed.
> >
> > settings.xml is the equivalent of ~/build.properties. It should only
> > need additions if you are a deployer or want to add additional
> > repositories yourself.
> >
> Good. We should then provide examples for RMs eventually.
> > >
> > > 3. I assume that the reference to 'minotaur' in the
> > > distributionManagement section of the csv pom should be changed to
> > > 'people'? Once this is fixed, I assume "deploy" will work correctly
> > > using the ssh key that the script is using to connect to people now.
> >
> > Should do.
> >
> > >
> > > 4. The dist plugin seems to be gone and the release plugin looks like
> > > it is really just aiming to deploy jars and tag releases. Should I
> > > use ant tasks to roll the distros manually or is there some m2 plugin
> > > that will do this?
> >
> > The assembly plugin is the equivalent of dist (but is a lot more
> > flexible). There is a default descriptor for building source and binary
> > tarballs/zips, but you can also create your own, describing the layout
> > of the resulting archive.
>
> Nice! Much nicer than the old muck with maven.xml approach. I will
> have a play with this and either use built-ins or commit descriptors
> that we can use for the nightlies to start and then standardize for
> releases. Suggestions / commits welcome!
This was actually one of my favorite discoveries about m2. For Shale, I
took the philosophy that a release artifact should include:
* The binary artifacts (jar, war, or whatever)
* A directory containing all the binary dependencies
* Javadocs
* Sources
* And the pom.xml in the top level directory so that, if you have
Maven2 installed, you can just type "mvn install" in the top level
directory of the release, and it reconstitutes itself.
Check out "framework/shale-dist" (in the Shale repository) for how this
works for the "framework" release artifact (which accumulates a bunch of
individual jars from sub-projects ... could do something like this for an
uber-commons release pretty easily once everything was m2-ized), or how each
of the webapps under framework/shale-apps can create a self contained
release that includes all of the above stuff (similar to what you might do
for an individual commons library).
Phil
Craig
---------------------------------------------------------------------
> To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: commons-dev-help@jakarta.apache.org
>
>
Re: [nightly build] m2 support - a little help, pls
Posted by Phil Steitz <ph...@gmail.com>.
On 8/9/06, Brett Porter <br...@apache.org> wrote:
> On 10/08/2006 1:21 PM, Phil Steitz wrote:
> > I would like to add m2 support to the nightly build script, but am
> > still an m2 newbie, so could use a little help. I thought that
> > starting with [csv] would be good, since the migration page lists it
> > as "done". I have a couple of questions.
> >
> > 1. It seems to use pom inheritence, which I am sure someone will
> > convince me is a good thing, despite the fact that my first experience
> > with it is a build failure because of it. How do I find and I guess
> > "install" the commons-sandbox-parent?
>
> It's in sandbox-trunks for now
OK, so I just did "mvn install" from the root of sandbox trunk and I
guess that did it.
>
> How do we indicate to users
> > that they are going to need to set this up for builds to work?
>
> It shouldn't be necessary. If the parent is finalised and released as an
> independant artifact first, it will be downloaded from the repository
> like any dependency.
>
> Do we
> > really need this?
>
> It's extremely useful for reducing duplication and making changes (such
> as repository location) easier, and also allows the same for any
> generated sites, so I'd say yes :)
OK, so the repo list will eventually go there? When it failed once it
displayed a list of repos including apache.snapshots that I could not
figure out where it was getting. I guess those are defaults and the
right way to set things up is to use repository elements in the pom.
So these should probably be specified then in the sandbox-parent and
proper-parent.
>
> >
> > 2. Properties files seem to be replaced by settings.xml. Is this
> > where we designate repo lists? If so, can someone commit a
> > settings.xml.sample?
>
> project.properties is replaced by pom.xml (ie, plugin configuration is
> brought in). This is all you should need to commit to SVN, and it can
> contain repository references if needed.
>
> settings.xml is the equivalent of ~/build.properties. It should only
> need additions if you are a deployer or want to add additional
> repositories yourself.
>
Good. We should then provide examples for RMs eventually.
> >
> > 3. I assume that the reference to 'minotaur' in the
> > distributionManagement section of the csv pom should be changed to
> > 'people'? Once this is fixed, I assume "deploy" will work correctly
> > using the ssh key that the script is using to connect to people now.
>
> Should do.
>
> >
> > 4. The dist plugin seems to be gone and the release plugin looks like
> > it is really just aiming to deploy jars and tag releases. Should I
> > use ant tasks to roll the distros manually or is there some m2 plugin
> > that will do this?
>
> The assembly plugin is the equivalent of dist (but is a lot more
> flexible). There is a default descriptor for building source and binary
> tarballs/zips, but you can also create your own, describing the layout
> of the resulting archive.
Nice! Much nicer than the old muck with maven.xml approach. I will
have a play with this and either use built-ins or commit descriptors
that we can use for the nightlies to start and then standardize for
releases. Suggestions / commits welcome!
Phil
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: [nightly build] m2 support - a little help, pls
Posted by Brett Porter <br...@apache.org>.
On 10/08/2006 1:21 PM, Phil Steitz wrote:
> I would like to add m2 support to the nightly build script, but am
> still an m2 newbie, so could use a little help. I thought that
> starting with [csv] would be good, since the migration page lists it
> as "done". I have a couple of questions.
>
> 1. It seems to use pom inheritence, which I am sure someone will
> convince me is a good thing, despite the fact that my first experience
> with it is a build failure because of it. How do I find and I guess
> "install" the commons-sandbox-parent?
It's in sandbox-trunks for now
How do we indicate to users
> that they are going to need to set this up for builds to work?
It shouldn't be necessary. If the parent is finalised and released as an
independant artifact first, it will be downloaded from the repository
like any dependency.
Do we
> really need this?
It's extremely useful for reducing duplication and making changes (such
as repository location) easier, and also allows the same for any
generated sites, so I'd say yes :)
>
> 2. Properties files seem to be replaced by settings.xml. Is this
> where we designate repo lists? If so, can someone commit a
> settings.xml.sample?
project.properties is replaced by pom.xml (ie, plugin configuration is
brought in). This is all you should need to commit to SVN, and it can
contain repository references if needed.
settings.xml is the equivalent of ~/build.properties. It should only
need additions if you are a deployer or want to add additional
repositories yourself.
>
> 3. I assume that the reference to 'minotaur' in the
> distributionManagement section of the csv pom should be changed to
> 'people'? Once this is fixed, I assume "deploy" will work correctly
> using the ssh key that the script is using to connect to people now.
Should do.
>
> 4. The dist plugin seems to be gone and the release plugin looks like
> it is really just aiming to deploy jars and tag releases. Should I
> use ant tasks to roll the distros manually or is there some m2 plugin
> that will do this?
The assembly plugin is the equivalent of dist (but is a lot more
flexible). There is a default descriptor for building source and binary
tarballs/zips, but you can also create your own, describing the layout
of the resulting archive.
Thanks!
- Brett
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org