You are viewing a plain text version of this content. The canonical link for it is here.
Posted to general@jakarta.apache.org by ba...@apache.org on 2006/08/11 06:03:22 UTC
svn commit: r430653 - /jakarta/jakarta-build/trunk/pom.xml
Author: bayard
Date: Thu Aug 10 21:03:21 2006
New Revision: 430653
URL: http://svn.apache.org/viewvc?rev=430653&view=rev
Log:
not released yet, so giving it a dev version of 1-SNAPSHOT
Modified:
jakarta/jakarta-build/trunk/pom.xml
Modified: jakarta/jakarta-build/trunk/pom.xml
URL: http://svn.apache.org/viewvc/jakarta/jakarta-build/trunk/pom.xml?rev=430653&r1=430652&r2=430653&view=diff
==============================================================================
--- jakarta/jakarta-build/trunk/pom.xml (original)
+++ jakarta/jakarta-build/trunk/pom.xml Thu Aug 10 21:03:21 2006
@@ -10,7 +10,7 @@
<artifactId>jakarta-parent</artifactId>
<packaging>pom</packaging>
<!-- TODO: dummy version. In Maven 2.1, this will be auto-versioned being a generic parent -->
- <version>1</version>
+ <version>1-SNAPSHOT</version>
<name>Apache Jakarta</name>
<url>http://jakarta.apache.org/</url>
<inceptionYear>1999</inceptionYear>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@jakarta.apache.org
For additional commands, e-mail: general-help@jakarta.apache.org
Re: [m2 config] was: Re: svn commit: r430653 - /jakarta/jakarta-build/trunk/pom.xml
Posted by Craig McClanahan <cr...@apache.org>.
On 8/27/06, Phil Steitz <ph...@steitz.com> wrote:
>
> <snip/>
>
> Dennis Lundberg wrote:
>
> I don't think so. After I had deployed the pom, Maven wanted to deploy
> *all* of the sandbox components. At this point I simply canceled the
> rest of the deploy.
By the way, there is a technique to avoid this problem .. "mvn -N deploy"
will only deploy the POM in the directory you're executing the command from,
while "mvn deploy" does that POM and all its modules.
Craig
Thanks again, Dennis. Let's take this to commons-dev now.
>
> Sorry, all, about all the noise.
>
> Phil
> >> Still in learning mode here...
> >>
> >> Phil
> >
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: general-help@jakarta.apache.org
>
>
[m2 config] was: Re: svn commit: r430653 - /jakarta/jakarta-build/trunk/pom.xml
Posted by Phil Steitz <ph...@steitz.com>.
<snip/>
Dennis Lundberg wrote:
I don't think so. After I had deployed the pom, Maven wanted to deploy
*all* of the sandbox components. At this point I simply canceled the
rest of the deploy.
Thanks again, Dennis. Let's take this to commons-dev now.
Sorry, all, about all the noise.
Phil
>> Still in learning mode here...
>>
>> Phil
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@jakarta.apache.org
For additional commands, e-mail: general-help@jakarta.apache.org
Re: svn commit: r430653 - /jakarta/jakarta-build/trunk/pom.xml
Posted by Dennis Lundberg <de...@apache.org>.
Phil Steitz wrote:
> Dennis Lundberg wrote:
>> Phil Steitz wrote:
>>> Henri Yandell wrote:
>>>> On Fri, 11 Aug 2006, Dennis Lundberg wrote:
>>>>
>>>>> Phil Steitz wrote:
>>>>>> Thanks, Dennis. That helps and I agree with your arguments for
>>>>>> inheritence in genera;.
>>>>>> But why a Jakarta parent?
>>>>> I'll leave that one for Henri to answer.
>>>> Do I look like I know what I'm doing? :)
>>>>
>>>> The Jakarta pom is there because it seemed like a good idea to share
>>>> things between Jakarta m2 projects and not just Commons ones - or at
>>>> least to try and encourage that sharing. Though I had thought that the
>>>> mailing lists in the parent would appear in the children and that's
>>>> not happened.
>>>>
>>>> It didn't seem like it would be damaging to represent the current
>>>> structure and Brett didn't run screaming when I asked him :)
>>>>
>>>> I'm not tied to it though - just throwing energy at the commons to m2
>>>> problems.
>>> Can someone less m2-newbie than me pls publish the jakarta and commons
>>> parents to the m2-snapshot-repo? The sandbox parent appears to be
>>> there, but the others are not and they have to be manually installed to
>>> get any commons m2 builds to work. That makes it pretty hard for the
>>> non-initiate to build the components (e.g. [pipeline]) that are dropping
>>> m1 poms.
>> Done.
>> I have deployed the poms jakarta, commons and commons-sandbox.
>>
> Thanks, Dennis!
>
> Now I am confused, though, since we seem to have both commons-sandbox
> and commons-sandbox-parent and the sanbox m2 builds seem to be evenly
> split between them, though all (other than pipeline) are listed as
> modules of commons-sandbox. Are these for different purposes?
commons-sandbox-parent was set up by Brett when he introduced the Maven
2 build in the sandbox.
commons-sandbox was set up by Henri as part of the Jakarta Maven 2 setup.
So I guess we should be moving from commons-sandbox-parent to
commons-sandbox. Perhaps Henri can comment on this.
> Also, do we really want to have the individual components set up as modules?
I don't think so. After I had deployed the pom, Maven wanted to deploy
*all* of the sandbox components. At this point I simply canceled the
rest of the deploy.
> Still in learning mode here...
>
> Phil
--
Dennis Lundberg
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@jakarta.apache.org
For additional commands, e-mail: general-help@jakarta.apache.org
Re: svn commit: r430653 - /jakarta/jakarta-build/trunk/pom.xml
Posted by Phil Steitz <ph...@steitz.com>.
Dennis Lundberg wrote:
> Phil Steitz wrote:
>> Henri Yandell wrote:
>>>
>>> On Fri, 11 Aug 2006, Dennis Lundberg wrote:
>>>
>>>> Phil Steitz wrote:
>>>>> Thanks, Dennis. That helps and I agree with your arguments for
>>>>> inheritence in genera;.
>>>>> But why a Jakarta parent?
>>>> I'll leave that one for Henri to answer.
>>> Do I look like I know what I'm doing? :)
>>>
>>> The Jakarta pom is there because it seemed like a good idea to share
>>> things between Jakarta m2 projects and not just Commons ones - or at
>>> least to try and encourage that sharing. Though I had thought that the
>>> mailing lists in the parent would appear in the children and that's
>>> not happened.
>>>
>>> It didn't seem like it would be damaging to represent the current
>>> structure and Brett didn't run screaming when I asked him :)
>>>
>>> I'm not tied to it though - just throwing energy at the commons to m2
>>> problems.
>> Can someone less m2-newbie than me pls publish the jakarta and commons
>> parents to the m2-snapshot-repo? The sandbox parent appears to be
>> there, but the others are not and they have to be manually installed to
>> get any commons m2 builds to work. That makes it pretty hard for the
>> non-initiate to build the components (e.g. [pipeline]) that are dropping
>> m1 poms.
>
> Done.
> I have deployed the poms jakarta, commons and commons-sandbox.
>
Thanks, Dennis!
Now I am confused, though, since we seem to have both commons-sandbox
and commons-sandbox-parent and the sanbox m2 builds seem to be evenly
split between them, though all (other than pipeline) are listed as
modules of commons-sandbox. Are these for different purposes?
Also, do we really want to have the individual components set up as modules?
Still in learning mode here...
Phil
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@jakarta.apache.org
For additional commands, e-mail: general-help@jakarta.apache.org
Re: svn commit: r430653 - /jakarta/jakarta-build/trunk/pom.xml
Posted by Dennis Lundberg <de...@apache.org>.
Phil Steitz wrote:
> Henri Yandell wrote:
>>
>> On Fri, 11 Aug 2006, Dennis Lundberg wrote:
>>
>>> Phil Steitz wrote:
>>>> Thanks, Dennis. That helps and I agree with your arguments for
>>>> inheritence in genera;.
>>>> But why a Jakarta parent?
>>> I'll leave that one for Henri to answer.
>> Do I look like I know what I'm doing? :)
>>
>> The Jakarta pom is there because it seemed like a good idea to share
>> things between Jakarta m2 projects and not just Commons ones - or at
>> least to try and encourage that sharing. Though I had thought that the
>> mailing lists in the parent would appear in the children and that's
>> not happened.
>>
>> It didn't seem like it would be damaging to represent the current
>> structure and Brett didn't run screaming when I asked him :)
>>
>> I'm not tied to it though - just throwing energy at the commons to m2
>> problems.
> Can someone less m2-newbie than me pls publish the jakarta and commons
> parents to the m2-snapshot-repo? The sandbox parent appears to be
> there, but the others are not and they have to be manually installed to
> get any commons m2 builds to work. That makes it pretty hard for the
> non-initiate to build the components (e.g. [pipeline]) that are dropping
> m1 poms.
Done.
I have deployed the poms jakarta, commons and commons-sandbox.
--
Dennis Lundberg
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@jakarta.apache.org
For additional commands, e-mail: general-help@jakarta.apache.org
Re: svn commit: r430653 - /jakarta/jakarta-build/trunk/pom.xml
Posted by Phil Steitz <ph...@steitz.com>.
Henri Yandell wrote:
>
>
> On Fri, 11 Aug 2006, Dennis Lundberg wrote:
>
>> Phil Steitz wrote:
>>> Thanks, Dennis. That helps and I agree with your arguments for
>>> inheritence in genera;.
>>> But why a Jakarta parent?
>>
>> I'll leave that one for Henri to answer.
>
> Do I look like I know what I'm doing? :)
>
> The Jakarta pom is there because it seemed like a good idea to share
> things between Jakarta m2 projects and not just Commons ones - or at
> least to try and encourage that sharing. Though I had thought that the
> mailing lists in the parent would appear in the children and that's
> not happened.
>
> It didn't seem like it would be damaging to represent the current
> structure and Brett didn't run screaming when I asked him :)
>
> I'm not tied to it though - just throwing energy at the commons to m2
> problems.
Can someone less m2-newbie than me pls publish the jakarta and commons
parents to the m2-snapshot-repo? The sandbox parent appears to be
there, but the others are not and they have to be manually installed to
get any commons m2 builds to work. That makes it pretty hard for the
non-initiate to build the components (e.g. [pipeline]) that are dropping
m1 poms.
Thanks!
Phil
>
> Hen
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: general-help@jakarta.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@jakarta.apache.org
For additional commands, e-mail: general-help@jakarta.apache.org
Re: svn commit: r430653 - /jakarta/jakarta-build/trunk/pom.xml
Posted by Henri Yandell <ba...@generationjava.com>.
On Fri, 11 Aug 2006, Dennis Lundberg wrote:
> Phil Steitz wrote:
>> Thanks, Dennis. That helps and I agree with your arguments for inheritence
>> in genera;.
>> But why a Jakarta parent?
>
> I'll leave that one for Henri to answer.
Do I look like I know what I'm doing? :)
The Jakarta pom is there because it seemed like a good idea to share
things between Jakarta m2 projects and not just Commons ones - or at least
to try and encourage that sharing. Though I had thought that the mailing
lists in the parent would appear in the children and that's not happened.
It didn't seem like it would be damaging to represent the current
structure and Brett didn't run screaming when I asked him :)
I'm not tied to it though - just throwing energy at the commons to m2
problems.
Hen
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@jakarta.apache.org
For additional commands, e-mail: general-help@jakarta.apache.org
Re: svn commit: r430653 - /jakarta/jakarta-build/trunk/pom.xml
Posted by Dennis Lundberg <de...@apache.org>.
Phil Steitz wrote:
> Thanks, Dennis. That helps and I agree with your arguments for inheritence in genera;.
>
> But why a Jakarta parent?
I'll leave that one for Henri to answer.
> And can you answer the second question about addressing? I am -0 on doing anything that cements "Jakarta" into the namespace above commons artifacts. Sorry if this has been discussed and agreed and I just missed it.
As it is currently done the namespace for commons artifacts is and will
be org.apache.commons, so there's no jakarta in there. The pom for
commons does have a parent which is currently the jakarta pom. If
Jakarta would be dissolved, that could easily be changed to something
else, say the ASF pom.
>
> Phil
>
> ________________________________
>
> From: Dennis Lundberg [mailto:dennisl@apache.org]
> Sent: Fri 8/11/2006 9:36 AM
> To: Jakarta General List
> Subject: Re: svn commit: r430653 - /jakarta/jakarta-build/trunk/pom.xml
>
>
>
> Phil Steitz wrote:
>> Henri Yandell wrote:
>>> First few commit messages bounced on this btw, until I fixed that up.
>>> It's a maven2
>> Hen,
>>
>> Can you enlighten the rest of us as to what this is for and what, if
>> any, implications it has on how we address maven2 artifacts originating
>> in jakarta projects?
>>
>> Phil
>
> <snip/>
>
> The purpose of having a parent pom is to reduce the amount of
> information you need to put in the pom of a specific project.
>
> It also makes sure that all projects us the *same* information for
> certain things. These things are put in the parent. An example of this
> is which plugins *all* projects must use. Each project can then add more
> plugins if they so desire.
>
> Now I know some of you are preparing to throw in arguments about how we
> tried to do this with Maven 1 and it failed. Before you do there is one
> crucial difference. In Maven 1 the parent had to reside somewhere within
> the same file system as your project. In Maven 2 the parent pom is
> published to a Maven repository. It is then downloaded like any other
> artifact by Maven automatically. So there will be no need to check out
> jakarta-build from svn and putting it in the exact correct location on
> your own machine.
>
> --
> Dennis Lundberg
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: general-help@jakarta.apache.org
>
>
>
>
>
>
> ------------------------------------------------------------------------
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: general-help@jakarta.apache.org
--
Dennis Lundberg
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@jakarta.apache.org
For additional commands, e-mail: general-help@jakarta.apache.org
RE: svn commit: r430653 - /jakarta/jakarta-build/trunk/pom.xml
Posted by Phil Steitz <ph...@steitz.com>.
Thanks, Dennis. That helps and I agree with your arguments for inheritence in genera;.
But why a Jakarta parent? And can you answer the second question about addressing? I am -0 on doing anything that cements "Jakarta" into the namespace above commons artifacts. Sorry if this has been discussed and agreed and I just missed it.
Phil
________________________________
From: Dennis Lundberg [mailto:dennisl@apache.org]
Sent: Fri 8/11/2006 9:36 AM
To: Jakarta General List
Subject: Re: svn commit: r430653 - /jakarta/jakarta-build/trunk/pom.xml
Phil Steitz wrote:
> Henri Yandell wrote:
>> First few commit messages bounced on this btw, until I fixed that up.
>> It's a maven2
> Hen,
>
> Can you enlighten the rest of us as to what this is for and what, if
> any, implications it has on how we address maven2 artifacts originating
> in jakarta projects?
>
> Phil
<snip/>
The purpose of having a parent pom is to reduce the amount of
information you need to put in the pom of a specific project.
It also makes sure that all projects us the *same* information for
certain things. These things are put in the parent. An example of this
is which plugins *all* projects must use. Each project can then add more
plugins if they so desire.
Now I know some of you are preparing to throw in arguments about how we
tried to do this with Maven 1 and it failed. Before you do there is one
crucial difference. In Maven 1 the parent had to reside somewhere within
the same file system as your project. In Maven 2 the parent pom is
published to a Maven repository. It is then downloaded like any other
artifact by Maven automatically. So there will be no need to check out
jakarta-build from svn and putting it in the exact correct location on
your own machine.
--
Dennis Lundberg
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@jakarta.apache.org
For additional commands, e-mail: general-help@jakarta.apache.org
Re: svn commit: r430653 - /jakarta/jakarta-build/trunk/pom.xml
Posted by Dennis Lundberg <de...@apache.org>.
Phil Steitz wrote:
> Henri Yandell wrote:
>> First few commit messages bounced on this btw, until I fixed that up.
>> It's a maven2
> Hen,
>
> Can you enlighten the rest of us as to what this is for and what, if
> any, implications it has on how we address maven2 artifacts originating
> in jakarta projects?
>
> Phil
<snip/>
The purpose of having a parent pom is to reduce the amount of
information you need to put in the pom of a specific project.
It also makes sure that all projects us the *same* information for
certain things. These things are put in the parent. An example of this
is which plugins *all* projects must use. Each project can then add more
plugins if they so desire.
Now I know some of you are preparing to throw in arguments about how we
tried to do this with Maven 1 and it failed. Before you do there is one
crucial difference. In Maven 1 the parent had to reside somewhere within
the same file system as your project. In Maven 2 the parent pom is
published to a Maven repository. It is then downloaded like any other
artifact by Maven automatically. So there will be no need to check out
jakarta-build from svn and putting it in the exact correct location on
your own machine.
--
Dennis Lundberg
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@jakarta.apache.org
For additional commands, e-mail: general-help@jakarta.apache.org
Re: svn commit: r430653 - /jakarta/jakarta-build/trunk/pom.xml
Posted by Phil Steitz <ph...@steitz.com>.
Henri Yandell wrote:
>
> First few commit messages bounced on this btw, until I fixed that up.
> It's a maven2
Hen,
Can you enlighten the rest of us as to what this is for and what, if
any, implications it has on how we address maven2 artifacts originating
in jakarta projects?
Phil
> parent pom for Jakarta projects. Created under advice from Brett on
> #maven :)
>
> Hen
>
> On Fri, 11 Aug 2006 bayard@apache.org wrote:
>
>> Author: bayard
>> Date: Thu Aug 10 21:03:21 2006
>> New Revision: 430653
>>
>> URL: http://svn.apache.org/viewvc?rev=430653&view=rev
>> Log:
>> not released yet, so giving it a dev version of 1-SNAPSHOT
>>
>> Modified:
>> jakarta/jakarta-build/trunk/pom.xml
>>
>> Modified: jakarta/jakarta-build/trunk/pom.xml
>> URL:
>> http://svn.apache.org/viewvc/jakarta/jakarta-build/trunk/pom.xml?rev=430653&r1=430652&r2=430653&view=diff
>>
>> ==============================================================================
>>
>> --- jakarta/jakarta-build/trunk/pom.xml (original)
>> +++ jakarta/jakarta-build/trunk/pom.xml Thu Aug 10 21:03:21 2006
>> @@ -10,7 +10,7 @@
>> <artifactId>jakarta-parent</artifactId>
>> <packaging>pom</packaging>
>> <!-- TODO: dummy version. In Maven 2.1, this will be auto-versioned
>> being a generic parent -->
>> - <version>1</version>
>> + <version>1-SNAPSHOT</version>
>> <name>Apache Jakarta</name>
>> <url>http://jakarta.apache.org/</url>
>> <inceptionYear>1999</inceptionYear>
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: general-unsubscribe@jakarta.apache.org
>> For additional commands, e-mail: general-help@jakarta.apache.org
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: general-help@jakarta.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@jakarta.apache.org
For additional commands, e-mail: general-help@jakarta.apache.org
Re: svn commit: r430653 - /jakarta/jakarta-build/trunk/pom.xml
Posted by Henri Yandell <ba...@generationjava.com>.
First few commit messages bounced on this btw, until I fixed that up. It's
a maven2 parent pom for Jakarta projects. Created under advice from Brett
on #maven :)
Hen
On Fri, 11 Aug 2006 bayard@apache.org wrote:
> Author: bayard
> Date: Thu Aug 10 21:03:21 2006
> New Revision: 430653
>
> URL: http://svn.apache.org/viewvc?rev=430653&view=rev
> Log:
> not released yet, so giving it a dev version of 1-SNAPSHOT
>
> Modified:
> jakarta/jakarta-build/trunk/pom.xml
>
> Modified: jakarta/jakarta-build/trunk/pom.xml
> URL: http://svn.apache.org/viewvc/jakarta/jakarta-build/trunk/pom.xml?rev=430653&r1=430652&r2=430653&view=diff
> ==============================================================================
> --- jakarta/jakarta-build/trunk/pom.xml (original)
> +++ jakarta/jakarta-build/trunk/pom.xml Thu Aug 10 21:03:21 2006
> @@ -10,7 +10,7 @@
> <artifactId>jakarta-parent</artifactId>
> <packaging>pom</packaging>
> <!-- TODO: dummy version. In Maven 2.1, this will be auto-versioned being a generic parent -->
> - <version>1</version>
> + <version>1-SNAPSHOT</version>
> <name>Apache Jakarta</name>
> <url>http://jakarta.apache.org/</url>
> <inceptionYear>1999</inceptionYear>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: general-help@jakarta.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@jakarta.apache.org
For additional commands, e-mail: general-help@jakarta.apache.org