You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@excalibur.apache.org by Leif Mortenson <le...@tanukisoftware.com> on 2005/12/03 16:02:34 UTC
Re: svn commit: r351917 - in /excalibur/trunk: ./ components/ components/datasource/
components/monitor/ components/pool/ components/pool/api/ components/pool/impl/
components/pool/instrumented/ components/sourceresolve/ components/store/
components/thread...
Thanks for working on this.
What is the standard for the groupid. I have been looking at maven2
this week
as well. The values in this change are package like, but not quite the
same
as the package. In some cases, org.apache.avalon.* is used where in others
org.apache.excalibur.* is used. As the groupid does not appear to be a
package name, should we be showing that all of these jars are from
Excalibur?
Avalon no longer exists.
Cheers,
Leif
jheymans@apache.org wrote:
> Author: jheymans
> Date: Sat Dec 3 04:29:26 2005
> New Revision: 351917
>
> URL: http://svn.apache.org/viewcvs?rev=351917&view=rev
> Log:
> - changed groupId structure to be more maven friendly/compliant eg org.apache.excalibur instead of just "excalibur"
> This was requested by Brett Porter.
>
> Modified:
> excalibur/trunk/components/datasource/pom.xml
> excalibur/trunk/components/monitor/pom.xml
> excalibur/trunk/components/pom.xml
> excalibur/trunk/components/pool/api/pom.xml
> excalibur/trunk/components/pool/impl/pom.xml
> excalibur/trunk/components/pool/instrumented/pom.xml
> excalibur/trunk/components/pool/pom.xml
> excalibur/trunk/components/sourceresolve/pom.xml
> excalibur/trunk/components/store/pom.xml
> excalibur/trunk/components/thread/api/pom.xml
> excalibur/trunk/components/thread/impl/pom.xml
> excalibur/trunk/components/thread/instrumented/pom.xml
> excalibur/trunk/components/thread/pom.xml
> excalibur/trunk/components/xmlutil/pom.xml
> excalibur/trunk/containerkit/instrument/api/pom.xml
> excalibur/trunk/containerkit/instrument/client/pom.xml
> excalibur/trunk/containerkit/instrument/mgr-api/pom.xml
> excalibur/trunk/containerkit/instrument/mgr-http/pom.xml
> excalibur/trunk/containerkit/instrument/mgr-impl/pom.xml
> excalibur/trunk/containerkit/instrument/pom.xml
> excalibur/trunk/containerkit/lifecycle/api/pom.xml
> excalibur/trunk/containerkit/lifecycle/impl/pom.xml
> excalibur/trunk/containerkit/lifecycle/pom.xml
> excalibur/trunk/containerkit/logger/pom.xml
> excalibur/trunk/containerkit/logkit/pom.xml
> excalibur/trunk/containerkit/pom.xml
> excalibur/trunk/deprecated/component/pom.xml
> excalibur/trunk/deprecated/event/api/pom.xml
> excalibur/trunk/deprecated/event/impl/pom.xml
> excalibur/trunk/deprecated/event/pom.xml
> excalibur/trunk/deprecated/pom.xml
> excalibur/trunk/deprecated/testcase/pom.xml
> excalibur/trunk/fortress/bean/pom.xml
> excalibur/trunk/fortress/container-api/pom.xml
> excalibur/trunk/fortress/container-impl/pom.xml
> excalibur/trunk/fortress/examples/pom.xml
> excalibur/trunk/fortress/meta/pom.xml
> excalibur/trunk/fortress/platform/pom.xml
> excalibur/trunk/fortress/pom.xml
> excalibur/trunk/framework/api/pom.xml
> excalibur/trunk/framework/impl/pom.xml
> excalibur/trunk/framework/pom.xml
> excalibur/trunk/pom.xml
>
<snip>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@excalibur.apache.org
For additional commands, e-mail: dev-help@excalibur.apache.org
Re: svn commit: r351917 - in /excalibur/trunk: ./ components/ components/datasource/
components/monitor/ components/pool/ components/pool/api/ components/pool/impl/
components/pool/instrumented/ components/sourceresolve/ components/store/
components/thread...
Posted by Jorg Heymans <jh...@domek.be>.
Leif Mortenson wrote:
> Thanks for working on this. What is the standard for the groupid. I
> have been looking at maven2 this week as well. The values in this
> change are package like, but not quite the same as the package. In
> some cases, org.apache.avalon.* is used where in others
> org.apache.excalibur.* is used. As the groupid does not appear to
> be a package name, should we be showing that all of these jars are
> from Excalibur? Avalon no longer exists.
>
There is no strict standard (yet) for defining the groupId of an
artifact. I created the groupIds after the repository organisation where
I thought it made sense.
but eg containerkit/logkit AFAIK was always referred to as
"avalon-logkit" so i left it that way to avoid confusion.
Brett told me that they would want to move more to a package alike
structure, perhaps even set the groupId to the top level distinctive
java package in the artifact.
Do you want me to remove all references to avalon in the poms?
Jorg
FYI here's brett's email on this
> Hi, I was just looking in:
>
> http://cvs.apache.org/maven-snapshot-repository/
>
> Is it possible to change the group IDs of the artifacts you are
> deploying to the deeper structure?
>
> I would imagine they would be:
>
> org.apache.cocoon
> org.apache.avalon
> org.apache.excalibur
> org.apache.excalibur.components
>
> That just gives them that little more separation, navigability and
> consistency with how we are going forward.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@excalibur.apache.org
For additional commands, e-mail: dev-help@excalibur.apache.org