You are viewing a plain text version of this content. The canonical link for it is here.
Posted to repository@apache.org by Henning Schmiedehausen <he...@apache.org> on 2007/05/01 14:20:10 UTC
Re: Anakia and texen in the repository
Carlos,
please stop this.
For maven-1, we either keep texen and anakia in the velocity group or
drop it completely from there. That is fine with me, no more groups,
yadda, yadda.
However, for maven-2 we will adhere to your 'standards'. This means, the
packages go into org.apache.texen and org.apache.anakia. That is the way
*you* as repo people recommended it.
If you have a problem with the jar being twice in your repo, well, maybe
it is time that you get your act together and have an uniform policy for
maven-1 and maven-2.
If you do not agree here, then we will go to org.apache.texen and
org.apache.anakia and drop the jars in the velocity group. I am not
really interested in second guessing what you want to have and how you
intend to organize it. The maven repos are a distribution mechanism, not
a policy tool.
Please rename the .bak directories. Feel free to drop the jars from the
velocity group at your discretion, I do not really care.
Best regards
Henning
Carlos Sanchez schrieb:
> I guess these are the same as the ones in
> http://people.apache.org/repo/m1-ibiblio-rsync-repository/velocity/jars
>
> - they should be only in the m1 OR m2 repo
> - Putting them in two different groupIds is confusing
> - if they are subprojects of velocity they should be in
> org.apache.velocity.*
> - missing PGP signatures
>
> I've moved anakia and texen out of the way for the moment (to .bak)
>
>
> On 30 Apr 2007 08:16:24 -0000, bayard@apache.org <ba...@apache.org> wrote:
>> Repository changed
>> ==================
>>
>> Repository: /www/people.apache.org/repo/m2-ibiblio-rsync-repository/
>>
>> Added
>> -----
>> [henning] org/apache/anakia
>> [henning] org/apache/anakia/anakia
>> [henning] org/apache/anakia/anakia/1.0
>> [henning] org/apache/anakia/anakia/1.0/anakia-1.0.jar
>> [henning] org/apache/anakia/anakia/1.0/anakia-1.0.jar.md5
>> [henning] org/apache/anakia/anakia/1.0/anakia-1.0.jar.sha1
>> [henning] org/apache/anakia/anakia/1.0/anakia-1.0.pom
>> [henning] org/apache/anakia/anakia/1.0/anakia-1.0.pom.md5
>> [henning] org/apache/anakia/anakia/1.0/anakia-1.0.pom.sha1
>> [henning] org/apache/anakia/anakia/maven-metadata.xml
>> [henning] org/apache/anakia/anakia/maven-metadata.xml.md5
>> [henning] org/apache/anakia/anakia/maven-metadata.xml.sha1
>> [henning] org/apache/texen
>> [henning] org/apache/texen/texen
>> [henning] org/apache/texen/texen/1.0
>> [henning] org/apache/texen/texen/1.0/texen-1.0.jar
>> [henning] org/apache/texen/texen/1.0/texen-1.0.jar.md5
>> [henning] org/apache/texen/texen/1.0/texen-1.0.jar.sha1
>> [henning] org/apache/texen/texen/1.0/texen-1.0.pom
>> [henning] org/apache/texen/texen/1.0/texen-1.0.pom.md5
>> [henning] org/apache/texen/texen/1.0/texen-1.0.pom.sha1
>> [henning] org/apache/texen/texen/maven-metadata.xml
>> [henning] org/apache/texen/texen/maven-metadata.xml.md5
>> [henning] org/apache/texen/texen/maven-metadata.xml.sha1
>>
>> Removed
>> -------
>>
>
>
Re: Anakia and texen in the repository
Posted by Henning Schmiedehausen <he...@apache.org>.
Yes, sure.
Best regards
Henning
Will Glass-Husain schrieb:
> Henning,
>
> If consensus is reached between you and Carlos, could you post a summary
> on the dev list on process/location changes for the next release? I
> know the discussion has been public, but a paragraph or two summary
> would be very helpful for those of us who are not Maven mavens.
>
> best,
> WILL
>
> On 5/3/07, *Henning Schmiedehausen* <henning@apache.org
> <ma...@apache.org>> wrote:
>
> Hi Carlos,
>
> I will put in the signatures shortly.
>
> For the engine, we have extension from the Apache POM already in SVN,
> for the others it will follow too before we release.
>
> Best regards
> Henning
>
>
> Carlos Sanchez schrieb:
> > ok, so you are going to use those groups and put the artifacts only in
> > the m2 repo from now on, right?
> >
> > I've rename them, you still have to add the PGP signatures to jars
> and poms
> >
> > for next versions I'd suggest you to extend the apache parent pom to
> > inherit some common information and reduce the size of your poms.
> > http://repo1.maven.org/maven2/org/apache/apache/4/apache-4.pom
> >
> >
> > On 5/1/07, Henning Schmiedehausen <henning@apache.org
> <ma...@apache.org>> wrote:
> >> Thank you for the clarification, Carlos.
> >>
> >> Can you fix the repo to use the new id's (org.apache.texen and
> >> org.apache.anakia) by renaming the directories back and remove the
> >> velocity-anakia and velocity-texen groups or can we do this
> ourselves?
> >>
> >> Best regards
> >> Henning
> >>
> >>
> >> Carlos Sanchez schrieb:
> >> > unfortunately there's no tooling for policy enforcement in the
> repo
> >> > and we are force to deal with issues like this after things are
> >> > deployed and before they get propagated to the mirrors. It's
> not the
> >> > best solution, but is the only one right now.
> >> > And I'm trying to solve future problems based on past experiences.
> >> >
> >> > The m1 and m2 repos are automatically converted to each other,
> so you
> >> > only need to deploy to one of them.
> >> >
> >> > Policies are the same, you can use old groupIds or use new ones
> under
> >> > org.apache.*
> >> >
> >> > You can put under m1 repo org.apache.velocity groupid, no
> problem with
> >> > that. For convenience people usually deploy with ant or m1 to
> the m1
> >> > repo and with m2 to the m2 repo.
> >> >
> >> > Another different issue is the group naming convention, for me
> it'd
> >> > make sense that anakia and texen were under org.apache.velocity.*
> >> > based on my experience and considering the explosion of groups that
> >> > could happen if all subprojects start using top level groupIds.
> AFAIK
> >> > there's no policy about this, so that's just my suggestion.
> >> >
> >> > What it is a policy is that all releases must be PGP signed,
> and also
> >> > you have to remove the repositories/repository entry
> >> > "http://people.apache.org/repo/m2-ibiblio-rsync-repository"
> from the
> >> > poms as it's internal use only.
> >> >
> >> > Sorry for the trouble. For me it'd be also easier to forget
> about it,
> >> > but in the long term this is going to save problems.
> >> >
> >> >
> >> > On 5/1/07, Henning Schmiedehausen < henning@apache.org
> <ma...@apache.org>> wrote:
> >> >> Carlos,
> >> >>
> >> >> please stop this.
> >> >>
> >> >> For maven-1, we either keep texen and anakia in the velocity
> group or
> >> >> drop it completely from there. That is fine with me, no more
> groups,
> >> >> yadda, yadda.
> >> >>
> >> >> However, for maven-2 we will adhere to your 'standards'. This
> >> means, the
> >> >> packages go into org.apache.texen and org.apache.anakia. That is
> >> the way
> >> >> *you* as repo people recommended it.
> >> >>
> >> >> If you have a problem with the jar being twice in your repo,
> well,
> >> maybe
> >> >> it is time that you get your act together and have an uniform
> >> policy for
> >> >> maven-1 and maven-2.
> >> >>
> >> >> If you do not agree here, then we will go to org.apache.texen and
> >> >> org.apache.anakia and drop the jars in the velocity group. I
> am not
> >> >> really interested in second guessing what you want to have and
> how you
> >> >> intend to organize it. The maven repos are a distribution
> >> mechanism, not
> >> >> a policy tool.
> >> >>
> >> >> Please rename the .bak directories. Feel free to drop the jars
> from
> >> the
> >> >> velocity group at your discretion, I do not really care.
> >> >>
> >> >>
> >> >>
> >> >> Best regards
> >> >> Henning
> >> >>
> >> >>
> >> >>
> >> >>
> >> >> Carlos Sanchez schrieb:
> >> >> > I guess these are the same as the ones in
> >> >> >
> >>
> http://people.apache.org/repo/m1-ibiblio-rsync-repository/velocity/jars
> >> >> >
> >> >> > - they should be only in the m1 OR m2 repo
> >> >> > - Putting them in two different groupIds is confusing
> >> >> > - if they are subprojects of velocity they should be in
> >> >> > org.apache.velocity.*
> >> >> > - missing PGP signatures
> >> >> >
> >> >> > I've moved anakia and texen out of the way for the moment
> (to .bak)
> >> >> >
> >> >> >
> >> >> > On 30 Apr 2007 08:16:24 -0000, bayard@apache.org
> <ma...@apache.org> <bayard@apache.org
> <ma...@apache.org>>
> >> >> wrote:
> >> >> >> Repository changed
> >> >> >> ==================
> >> >> >>
> >> >> >> Repository:
> >> /www/people.apache.org/repo/m2-ibiblio-rsync-repository/
> >> >> >>
> >> >> >> Added
> >> >> >> -----
> >> >> >> [henning] org/apache/anakia
> >> >> >> [henning] org/apache/anakia/anakia
> >> >> >> [henning] org/apache/anakia/anakia/1.0
> >> >> >> [henning] org/apache/anakia/anakia/1.0/anakia-1.0.jar
> >> >> >> [henning] org/apache/anakia/anakia/1.0/anakia- 1.0.jar.md5
> >> >> >> [henning] org/apache/anakia/anakia/1.0/anakia-1.0.jar.sha1
> >> >> >> [henning] org/apache/anakia/anakia/1.0/anakia-1.0.pom
> >> >> >> [henning] org/apache/anakia/anakia/1.0/anakia- 1.0.pom.md5
> >> >> >> [henning] org/apache/anakia/anakia/1.0/anakia-1.0.pom.sha1
> >> >> >> [henning] org/apache/anakia/anakia/maven-metadata.xml
> >> >> >> [henning] org/apache/anakia/anakia/maven- metadata.xml.md5
> >> >> >> [henning] org/apache/anakia/anakia/maven-metadata.xml.sha1
> >> >> >> [henning] org/apache/texen
> >> >> >> [henning] org/apache/texen/texen
> >> >> >> [henning] org/apache/texen/texen/1.0
> >> >> >> [henning] org/apache/texen/texen/1.0/texen-1.0.jar
> >> >> >> [henning] org/apache/texen/texen/1.0/texen- 1.0.jar.md5
> >> >> >> [henning] org/apache/texen/texen/1.0/texen-1.0.jar.sha1
> >> >> >> [henning] org/apache/texen/texen/1.0/texen-1.0.pom
> >> >> >> [henning] org/apache/texen/texen/1.0/texen- 1.0.pom.md5
> >> >> >> [henning] org/apache/texen/texen/1.0/texen-1.0.pom.sha1
> >> >> >> [henning] org/apache/texen/texen/maven-metadata.xml
> >> >> >> [henning] org/apache/texen/texen/maven- metadata.xml.md5
> >> >> >> [henning] org/apache/texen/texen/maven-metadata.xml.sha1
> >> >> >>
> >> >> >> Removed
> >> >> >> -------
> >> >> >>
> >> >> >
> >> >> >
> >> >>
> >> >
> >> >
> >>
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@velocity.apache.org
> <ma...@velocity.apache.org>
> For additional commands, e-mail: dev-help@velocity.apache.org
> <ma...@velocity.apache.org>
>
>
>
>
> --
> Forio Business Simulations
>
> Will Glass-Husain
> wglass@forio.com <ma...@forio.com>
> www.forio.com <http://www.forio.com>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@velocity.apache.org
For additional commands, e-mail: dev-help@velocity.apache.org
Re: Anakia and texen in the repository
Posted by Will Glass-Husain <wg...@gmail.com>.
Henning,
If consensus is reached between you and Carlos, could you post a summary on
the dev list on process/location changes for the next release? I know the
discussion has been public, but a paragraph or two summary would be very
helpful for those of us who are not Maven mavens.
best,
WILL
On 5/3/07, Henning Schmiedehausen <he...@apache.org> wrote:
>
> Hi Carlos,
>
> I will put in the signatures shortly.
>
> For the engine, we have extension from the Apache POM already in SVN,
> for the others it will follow too before we release.
>
> Best regards
> Henning
>
>
> Carlos Sanchez schrieb:
> > ok, so you are going to use those groups and put the artifacts only in
> > the m2 repo from now on, right?
> >
> > I've rename them, you still have to add the PGP signatures to jars and
> poms
> >
> > for next versions I'd suggest you to extend the apache parent pom to
> > inherit some common information and reduce the size of your poms.
> > http://repo1.maven.org/maven2/org/apache/apache/4/apache-4.pom
> >
> >
> > On 5/1/07, Henning Schmiedehausen <he...@apache.org> wrote:
> >> Thank you for the clarification, Carlos.
> >>
> >> Can you fix the repo to use the new id's (org.apache.texen and
> >> org.apache.anakia) by renaming the directories back and remove the
> >> velocity-anakia and velocity-texen groups or can we do this ourselves?
> >>
> >> Best regards
> >> Henning
> >>
> >>
> >> Carlos Sanchez schrieb:
> >> > unfortunately there's no tooling for policy enforcement in the repo
> >> > and we are force to deal with issues like this after things are
> >> > deployed and before they get propagated to the mirrors. It's not the
> >> > best solution, but is the only one right now.
> >> > And I'm trying to solve future problems based on past experiences.
> >> >
> >> > The m1 and m2 repos are automatically converted to each other, so you
> >> > only need to deploy to one of them.
> >> >
> >> > Policies are the same, you can use old groupIds or use new ones under
> >> > org.apache.*
> >> >
> >> > You can put under m1 repo org.apache.velocity groupid, no problem
> with
> >> > that. For convenience people usually deploy with ant or m1 to the m1
> >> > repo and with m2 to the m2 repo.
> >> >
> >> > Another different issue is the group naming convention, for me it'd
> >> > make sense that anakia and texen were under org.apache.velocity.*
> >> > based on my experience and considering the explosion of groups that
> >> > could happen if all subprojects start using top level groupIds. AFAIK
> >> > there's no policy about this, so that's just my suggestion.
> >> >
> >> > What it is a policy is that all releases must be PGP signed, and also
> >> > you have to remove the repositories/repository entry
> >> > "http://people.apache.org/repo/m2-ibiblio-rsync-repository" from the
> >> > poms as it's internal use only.
> >> >
> >> > Sorry for the trouble. For me it'd be also easier to forget about it,
> >> > but in the long term this is going to save problems.
> >> >
> >> >
> >> > On 5/1/07, Henning Schmiedehausen <he...@apache.org> wrote:
> >> >> Carlos,
> >> >>
> >> >> please stop this.
> >> >>
> >> >> For maven-1, we either keep texen and anakia in the velocity group
> or
> >> >> drop it completely from there. That is fine with me, no more groups,
> >> >> yadda, yadda.
> >> >>
> >> >> However, for maven-2 we will adhere to your 'standards'. This
> >> means, the
> >> >> packages go into org.apache.texen and org.apache.anakia. That is
> >> the way
> >> >> *you* as repo people recommended it.
> >> >>
> >> >> If you have a problem with the jar being twice in your repo, well,
> >> maybe
> >> >> it is time that you get your act together and have an uniform
> >> policy for
> >> >> maven-1 and maven-2.
> >> >>
> >> >> If you do not agree here, then we will go to org.apache.texen and
> >> >> org.apache.anakia and drop the jars in the velocity group. I am not
> >> >> really interested in second guessing what you want to have and how
> you
> >> >> intend to organize it. The maven repos are a distribution
> >> mechanism, not
> >> >> a policy tool.
> >> >>
> >> >> Please rename the .bak directories. Feel free to drop the jars from
> >> the
> >> >> velocity group at your discretion, I do not really care.
> >> >>
> >> >>
> >> >>
> >> >> Best regards
> >> >> Henning
> >> >>
> >> >>
> >> >>
> >> >>
> >> >> Carlos Sanchez schrieb:
> >> >> > I guess these are the same as the ones in
> >> >> >
> >> http://people.apache.org/repo/m1-ibiblio-rsync-repository/velocity/jars
> >> >> >
> >> >> > - they should be only in the m1 OR m2 repo
> >> >> > - Putting them in two different groupIds is confusing
> >> >> > - if they are subprojects of velocity they should be in
> >> >> > org.apache.velocity.*
> >> >> > - missing PGP signatures
> >> >> >
> >> >> > I've moved anakia and texen out of the way for the moment (to
> .bak)
> >> >> >
> >> >> >
> >> >> > On 30 Apr 2007 08:16:24 -0000, bayard@apache.org <
> bayard@apache.org>
> >> >> wrote:
> >> >> >> Repository changed
> >> >> >> ==================
> >> >> >>
> >> >> >> Repository:
> >> /www/people.apache.org/repo/m2-ibiblio-rsync-repository/
> >> >> >>
> >> >> >> Added
> >> >> >> -----
> >> >> >> [henning] org/apache/anakia
> >> >> >> [henning] org/apache/anakia/anakia
> >> >> >> [henning] org/apache/anakia/anakia/1.0
> >> >> >> [henning] org/apache/anakia/anakia/1.0/anakia-1.0.jar
> >> >> >> [henning] org/apache/anakia/anakia/1.0/anakia-1.0.jar.md5
> >> >> >> [henning] org/apache/anakia/anakia/1.0/anakia-1.0.jar.sha1
> >> >> >> [henning] org/apache/anakia/anakia/1.0/anakia-1.0.pom
> >> >> >> [henning] org/apache/anakia/anakia/1.0/anakia-1.0.pom.md5
> >> >> >> [henning] org/apache/anakia/anakia/1.0/anakia-1.0.pom.sha1
> >> >> >> [henning] org/apache/anakia/anakia/maven-metadata.xml
> >> >> >> [henning] org/apache/anakia/anakia/maven-metadata.xml.md5
> >> >> >> [henning] org/apache/anakia/anakia/maven-metadata.xml.sha1
> >> >> >> [henning] org/apache/texen
> >> >> >> [henning] org/apache/texen/texen
> >> >> >> [henning] org/apache/texen/texen/1.0
> >> >> >> [henning] org/apache/texen/texen/1.0/texen-1.0.jar
> >> >> >> [henning] org/apache/texen/texen/1.0/texen-1.0.jar.md5
> >> >> >> [henning] org/apache/texen/texen/1.0/texen-1.0.jar.sha1
> >> >> >> [henning] org/apache/texen/texen/1.0/texen-1.0.pom
> >> >> >> [henning] org/apache/texen/texen/1.0/texen-1.0.pom.md5
> >> >> >> [henning] org/apache/texen/texen/1.0/texen-1.0.pom.sha1
> >> >> >> [henning] org/apache/texen/texen/maven-metadata.xml
> >> >> >> [henning] org/apache/texen/texen/maven-metadata.xml.md5
> >> >> >> [henning] org/apache/texen/texen/maven-metadata.xml.sha1
> >> >> >>
> >> >> >> Removed
> >> >> >> -------
> >> >> >>
> >> >> >
> >> >> >
> >> >>
> >> >
> >> >
> >>
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@velocity.apache.org
> For additional commands, e-mail: dev-help@velocity.apache.org
>
>
--
Forio Business Simulations
Will Glass-Husain
wglass@forio.com
www.forio.com
Re: Anakia and texen in the repository
Posted by Henning Schmiedehausen <he...@apache.org>.
Hi Carlos,
I will put in the signatures shortly.
For the engine, we have extension from the Apache POM already in SVN,
for the others it will follow too before we release.
Best regards
Henning
Carlos Sanchez schrieb:
> ok, so you are going to use those groups and put the artifacts only in
> the m2 repo from now on, right?
>
> I've rename them, you still have to add the PGP signatures to jars and poms
>
> for next versions I'd suggest you to extend the apache parent pom to
> inherit some common information and reduce the size of your poms.
> http://repo1.maven.org/maven2/org/apache/apache/4/apache-4.pom
>
>
> On 5/1/07, Henning Schmiedehausen <he...@apache.org> wrote:
>> Thank you for the clarification, Carlos.
>>
>> Can you fix the repo to use the new id's (org.apache.texen and
>> org.apache.anakia) by renaming the directories back and remove the
>> velocity-anakia and velocity-texen groups or can we do this ourselves?
>>
>> Best regards
>> Henning
>>
>>
>> Carlos Sanchez schrieb:
>> > unfortunately there's no tooling for policy enforcement in the repo
>> > and we are force to deal with issues like this after things are
>> > deployed and before they get propagated to the mirrors. It's not the
>> > best solution, but is the only one right now.
>> > And I'm trying to solve future problems based on past experiences.
>> >
>> > The m1 and m2 repos are automatically converted to each other, so you
>> > only need to deploy to one of them.
>> >
>> > Policies are the same, you can use old groupIds or use new ones under
>> > org.apache.*
>> >
>> > You can put under m1 repo org.apache.velocity groupid, no problem with
>> > that. For convenience people usually deploy with ant or m1 to the m1
>> > repo and with m2 to the m2 repo.
>> >
>> > Another different issue is the group naming convention, for me it'd
>> > make sense that anakia and texen were under org.apache.velocity.*
>> > based on my experience and considering the explosion of groups that
>> > could happen if all subprojects start using top level groupIds. AFAIK
>> > there's no policy about this, so that's just my suggestion.
>> >
>> > What it is a policy is that all releases must be PGP signed, and also
>> > you have to remove the repositories/repository entry
>> > "http://people.apache.org/repo/m2-ibiblio-rsync-repository" from the
>> > poms as it's internal use only.
>> >
>> > Sorry for the trouble. For me it'd be also easier to forget about it,
>> > but in the long term this is going to save problems.
>> >
>> >
>> > On 5/1/07, Henning Schmiedehausen <he...@apache.org> wrote:
>> >> Carlos,
>> >>
>> >> please stop this.
>> >>
>> >> For maven-1, we either keep texen and anakia in the velocity group or
>> >> drop it completely from there. That is fine with me, no more groups,
>> >> yadda, yadda.
>> >>
>> >> However, for maven-2 we will adhere to your 'standards'. This
>> means, the
>> >> packages go into org.apache.texen and org.apache.anakia. That is
>> the way
>> >> *you* as repo people recommended it.
>> >>
>> >> If you have a problem with the jar being twice in your repo, well,
>> maybe
>> >> it is time that you get your act together and have an uniform
>> policy for
>> >> maven-1 and maven-2.
>> >>
>> >> If you do not agree here, then we will go to org.apache.texen and
>> >> org.apache.anakia and drop the jars in the velocity group. I am not
>> >> really interested in second guessing what you want to have and how you
>> >> intend to organize it. The maven repos are a distribution
>> mechanism, not
>> >> a policy tool.
>> >>
>> >> Please rename the .bak directories. Feel free to drop the jars from
>> the
>> >> velocity group at your discretion, I do not really care.
>> >>
>> >>
>> >>
>> >> Best regards
>> >> Henning
>> >>
>> >>
>> >>
>> >>
>> >> Carlos Sanchez schrieb:
>> >> > I guess these are the same as the ones in
>> >> >
>> http://people.apache.org/repo/m1-ibiblio-rsync-repository/velocity/jars
>> >> >
>> >> > - they should be only in the m1 OR m2 repo
>> >> > - Putting them in two different groupIds is confusing
>> >> > - if they are subprojects of velocity they should be in
>> >> > org.apache.velocity.*
>> >> > - missing PGP signatures
>> >> >
>> >> > I've moved anakia and texen out of the way for the moment (to .bak)
>> >> >
>> >> >
>> >> > On 30 Apr 2007 08:16:24 -0000, bayard@apache.org <ba...@apache.org>
>> >> wrote:
>> >> >> Repository changed
>> >> >> ==================
>> >> >>
>> >> >> Repository:
>> /www/people.apache.org/repo/m2-ibiblio-rsync-repository/
>> >> >>
>> >> >> Added
>> >> >> -----
>> >> >> [henning] org/apache/anakia
>> >> >> [henning] org/apache/anakia/anakia
>> >> >> [henning] org/apache/anakia/anakia/1.0
>> >> >> [henning] org/apache/anakia/anakia/1.0/anakia-1.0.jar
>> >> >> [henning] org/apache/anakia/anakia/1.0/anakia-1.0.jar.md5
>> >> >> [henning] org/apache/anakia/anakia/1.0/anakia-1.0.jar.sha1
>> >> >> [henning] org/apache/anakia/anakia/1.0/anakia-1.0.pom
>> >> >> [henning] org/apache/anakia/anakia/1.0/anakia-1.0.pom.md5
>> >> >> [henning] org/apache/anakia/anakia/1.0/anakia-1.0.pom.sha1
>> >> >> [henning] org/apache/anakia/anakia/maven-metadata.xml
>> >> >> [henning] org/apache/anakia/anakia/maven-metadata.xml.md5
>> >> >> [henning] org/apache/anakia/anakia/maven-metadata.xml.sha1
>> >> >> [henning] org/apache/texen
>> >> >> [henning] org/apache/texen/texen
>> >> >> [henning] org/apache/texen/texen/1.0
>> >> >> [henning] org/apache/texen/texen/1.0/texen-1.0.jar
>> >> >> [henning] org/apache/texen/texen/1.0/texen-1.0.jar.md5
>> >> >> [henning] org/apache/texen/texen/1.0/texen-1.0.jar.sha1
>> >> >> [henning] org/apache/texen/texen/1.0/texen-1.0.pom
>> >> >> [henning] org/apache/texen/texen/1.0/texen-1.0.pom.md5
>> >> >> [henning] org/apache/texen/texen/1.0/texen-1.0.pom.sha1
>> >> >> [henning] org/apache/texen/texen/maven-metadata.xml
>> >> >> [henning] org/apache/texen/texen/maven-metadata.xml.md5
>> >> >> [henning] org/apache/texen/texen/maven-metadata.xml.sha1
>> >> >>
>> >> >> Removed
>> >> >> -------
>> >> >>
>> >> >
>> >> >
>> >>
>> >
>> >
>>
>
>
Re: Anakia and texen in the repository
Posted by Henning Schmiedehausen <he...@apache.org>.
Hi Carlos,
I will put in the signatures shortly.
For the engine, we have extension from the Apache POM already in SVN,
for the others it will follow too before we release.
Best regards
Henning
Carlos Sanchez schrieb:
> ok, so you are going to use those groups and put the artifacts only in
> the m2 repo from now on, right?
>
> I've rename them, you still have to add the PGP signatures to jars and poms
>
> for next versions I'd suggest you to extend the apache parent pom to
> inherit some common information and reduce the size of your poms.
> http://repo1.maven.org/maven2/org/apache/apache/4/apache-4.pom
>
>
> On 5/1/07, Henning Schmiedehausen <he...@apache.org> wrote:
>> Thank you for the clarification, Carlos.
>>
>> Can you fix the repo to use the new id's (org.apache.texen and
>> org.apache.anakia) by renaming the directories back and remove the
>> velocity-anakia and velocity-texen groups or can we do this ourselves?
>>
>> Best regards
>> Henning
>>
>>
>> Carlos Sanchez schrieb:
>> > unfortunately there's no tooling for policy enforcement in the repo
>> > and we are force to deal with issues like this after things are
>> > deployed and before they get propagated to the mirrors. It's not the
>> > best solution, but is the only one right now.
>> > And I'm trying to solve future problems based on past experiences.
>> >
>> > The m1 and m2 repos are automatically converted to each other, so you
>> > only need to deploy to one of them.
>> >
>> > Policies are the same, you can use old groupIds or use new ones under
>> > org.apache.*
>> >
>> > You can put under m1 repo org.apache.velocity groupid, no problem with
>> > that. For convenience people usually deploy with ant or m1 to the m1
>> > repo and with m2 to the m2 repo.
>> >
>> > Another different issue is the group naming convention, for me it'd
>> > make sense that anakia and texen were under org.apache.velocity.*
>> > based on my experience and considering the explosion of groups that
>> > could happen if all subprojects start using top level groupIds. AFAIK
>> > there's no policy about this, so that's just my suggestion.
>> >
>> > What it is a policy is that all releases must be PGP signed, and also
>> > you have to remove the repositories/repository entry
>> > "http://people.apache.org/repo/m2-ibiblio-rsync-repository" from the
>> > poms as it's internal use only.
>> >
>> > Sorry for the trouble. For me it'd be also easier to forget about it,
>> > but in the long term this is going to save problems.
>> >
>> >
>> > On 5/1/07, Henning Schmiedehausen <he...@apache.org> wrote:
>> >> Carlos,
>> >>
>> >> please stop this.
>> >>
>> >> For maven-1, we either keep texen and anakia in the velocity group or
>> >> drop it completely from there. That is fine with me, no more groups,
>> >> yadda, yadda.
>> >>
>> >> However, for maven-2 we will adhere to your 'standards'. This
>> means, the
>> >> packages go into org.apache.texen and org.apache.anakia. That is
>> the way
>> >> *you* as repo people recommended it.
>> >>
>> >> If you have a problem with the jar being twice in your repo, well,
>> maybe
>> >> it is time that you get your act together and have an uniform
>> policy for
>> >> maven-1 and maven-2.
>> >>
>> >> If you do not agree here, then we will go to org.apache.texen and
>> >> org.apache.anakia and drop the jars in the velocity group. I am not
>> >> really interested in second guessing what you want to have and how you
>> >> intend to organize it. The maven repos are a distribution
>> mechanism, not
>> >> a policy tool.
>> >>
>> >> Please rename the .bak directories. Feel free to drop the jars from
>> the
>> >> velocity group at your discretion, I do not really care.
>> >>
>> >>
>> >>
>> >> Best regards
>> >> Henning
>> >>
>> >>
>> >>
>> >>
>> >> Carlos Sanchez schrieb:
>> >> > I guess these are the same as the ones in
>> >> >
>> http://people.apache.org/repo/m1-ibiblio-rsync-repository/velocity/jars
>> >> >
>> >> > - they should be only in the m1 OR m2 repo
>> >> > - Putting them in two different groupIds is confusing
>> >> > - if they are subprojects of velocity they should be in
>> >> > org.apache.velocity.*
>> >> > - missing PGP signatures
>> >> >
>> >> > I've moved anakia and texen out of the way for the moment (to .bak)
>> >> >
>> >> >
>> >> > On 30 Apr 2007 08:16:24 -0000, bayard@apache.org <ba...@apache.org>
>> >> wrote:
>> >> >> Repository changed
>> >> >> ==================
>> >> >>
>> >> >> Repository:
>> /www/people.apache.org/repo/m2-ibiblio-rsync-repository/
>> >> >>
>> >> >> Added
>> >> >> -----
>> >> >> [henning] org/apache/anakia
>> >> >> [henning] org/apache/anakia/anakia
>> >> >> [henning] org/apache/anakia/anakia/1.0
>> >> >> [henning] org/apache/anakia/anakia/1.0/anakia-1.0.jar
>> >> >> [henning] org/apache/anakia/anakia/1.0/anakia-1.0.jar.md5
>> >> >> [henning] org/apache/anakia/anakia/1.0/anakia-1.0.jar.sha1
>> >> >> [henning] org/apache/anakia/anakia/1.0/anakia-1.0.pom
>> >> >> [henning] org/apache/anakia/anakia/1.0/anakia-1.0.pom.md5
>> >> >> [henning] org/apache/anakia/anakia/1.0/anakia-1.0.pom.sha1
>> >> >> [henning] org/apache/anakia/anakia/maven-metadata.xml
>> >> >> [henning] org/apache/anakia/anakia/maven-metadata.xml.md5
>> >> >> [henning] org/apache/anakia/anakia/maven-metadata.xml.sha1
>> >> >> [henning] org/apache/texen
>> >> >> [henning] org/apache/texen/texen
>> >> >> [henning] org/apache/texen/texen/1.0
>> >> >> [henning] org/apache/texen/texen/1.0/texen-1.0.jar
>> >> >> [henning] org/apache/texen/texen/1.0/texen-1.0.jar.md5
>> >> >> [henning] org/apache/texen/texen/1.0/texen-1.0.jar.sha1
>> >> >> [henning] org/apache/texen/texen/1.0/texen-1.0.pom
>> >> >> [henning] org/apache/texen/texen/1.0/texen-1.0.pom.md5
>> >> >> [henning] org/apache/texen/texen/1.0/texen-1.0.pom.sha1
>> >> >> [henning] org/apache/texen/texen/maven-metadata.xml
>> >> >> [henning] org/apache/texen/texen/maven-metadata.xml.md5
>> >> >> [henning] org/apache/texen/texen/maven-metadata.xml.sha1
>> >> >>
>> >> >> Removed
>> >> >> -------
>> >> >>
>> >> >
>> >> >
>> >>
>> >
>> >
>>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@velocity.apache.org
For additional commands, e-mail: dev-help@velocity.apache.org
Re: Anakia and texen in the repository
Posted by Carlos Sanchez <ca...@apache.org>.
ok, so you are going to use those groups and put the artifacts only in
the m2 repo from now on, right?
I've rename them, you still have to add the PGP signatures to jars and poms
for next versions I'd suggest you to extend the apache parent pom to
inherit some common information and reduce the size of your poms.
http://repo1.maven.org/maven2/org/apache/apache/4/apache-4.pom
On 5/1/07, Henning Schmiedehausen <he...@apache.org> wrote:
> Thank you for the clarification, Carlos.
>
> Can you fix the repo to use the new id's (org.apache.texen and
> org.apache.anakia) by renaming the directories back and remove the
> velocity-anakia and velocity-texen groups or can we do this ourselves?
>
> Best regards
> Henning
>
>
> Carlos Sanchez schrieb:
> > unfortunately there's no tooling for policy enforcement in the repo
> > and we are force to deal with issues like this after things are
> > deployed and before they get propagated to the mirrors. It's not the
> > best solution, but is the only one right now.
> > And I'm trying to solve future problems based on past experiences.
> >
> > The m1 and m2 repos are automatically converted to each other, so you
> > only need to deploy to one of them.
> >
> > Policies are the same, you can use old groupIds or use new ones under
> > org.apache.*
> >
> > You can put under m1 repo org.apache.velocity groupid, no problem with
> > that. For convenience people usually deploy with ant or m1 to the m1
> > repo and with m2 to the m2 repo.
> >
> > Another different issue is the group naming convention, for me it'd
> > make sense that anakia and texen were under org.apache.velocity.*
> > based on my experience and considering the explosion of groups that
> > could happen if all subprojects start using top level groupIds. AFAIK
> > there's no policy about this, so that's just my suggestion.
> >
> > What it is a policy is that all releases must be PGP signed, and also
> > you have to remove the repositories/repository entry
> > "http://people.apache.org/repo/m2-ibiblio-rsync-repository" from the
> > poms as it's internal use only.
> >
> > Sorry for the trouble. For me it'd be also easier to forget about it,
> > but in the long term this is going to save problems.
> >
> >
> > On 5/1/07, Henning Schmiedehausen <he...@apache.org> wrote:
> >> Carlos,
> >>
> >> please stop this.
> >>
> >> For maven-1, we either keep texen and anakia in the velocity group or
> >> drop it completely from there. That is fine with me, no more groups,
> >> yadda, yadda.
> >>
> >> However, for maven-2 we will adhere to your 'standards'. This means, the
> >> packages go into org.apache.texen and org.apache.anakia. That is the way
> >> *you* as repo people recommended it.
> >>
> >> If you have a problem with the jar being twice in your repo, well, maybe
> >> it is time that you get your act together and have an uniform policy for
> >> maven-1 and maven-2.
> >>
> >> If you do not agree here, then we will go to org.apache.texen and
> >> org.apache.anakia and drop the jars in the velocity group. I am not
> >> really interested in second guessing what you want to have and how you
> >> intend to organize it. The maven repos are a distribution mechanism, not
> >> a policy tool.
> >>
> >> Please rename the .bak directories. Feel free to drop the jars from the
> >> velocity group at your discretion, I do not really care.
> >>
> >>
> >>
> >> Best regards
> >> Henning
> >>
> >>
> >>
> >>
> >> Carlos Sanchez schrieb:
> >> > I guess these are the same as the ones in
> >> > http://people.apache.org/repo/m1-ibiblio-rsync-repository/velocity/jars
> >> >
> >> > - they should be only in the m1 OR m2 repo
> >> > - Putting them in two different groupIds is confusing
> >> > - if they are subprojects of velocity they should be in
> >> > org.apache.velocity.*
> >> > - missing PGP signatures
> >> >
> >> > I've moved anakia and texen out of the way for the moment (to .bak)
> >> >
> >> >
> >> > On 30 Apr 2007 08:16:24 -0000, bayard@apache.org <ba...@apache.org>
> >> wrote:
> >> >> Repository changed
> >> >> ==================
> >> >>
> >> >> Repository: /www/people.apache.org/repo/m2-ibiblio-rsync-repository/
> >> >>
> >> >> Added
> >> >> -----
> >> >> [henning] org/apache/anakia
> >> >> [henning] org/apache/anakia/anakia
> >> >> [henning] org/apache/anakia/anakia/1.0
> >> >> [henning] org/apache/anakia/anakia/1.0/anakia-1.0.jar
> >> >> [henning] org/apache/anakia/anakia/1.0/anakia-1.0.jar.md5
> >> >> [henning] org/apache/anakia/anakia/1.0/anakia-1.0.jar.sha1
> >> >> [henning] org/apache/anakia/anakia/1.0/anakia-1.0.pom
> >> >> [henning] org/apache/anakia/anakia/1.0/anakia-1.0.pom.md5
> >> >> [henning] org/apache/anakia/anakia/1.0/anakia-1.0.pom.sha1
> >> >> [henning] org/apache/anakia/anakia/maven-metadata.xml
> >> >> [henning] org/apache/anakia/anakia/maven-metadata.xml.md5
> >> >> [henning] org/apache/anakia/anakia/maven-metadata.xml.sha1
> >> >> [henning] org/apache/texen
> >> >> [henning] org/apache/texen/texen
> >> >> [henning] org/apache/texen/texen/1.0
> >> >> [henning] org/apache/texen/texen/1.0/texen-1.0.jar
> >> >> [henning] org/apache/texen/texen/1.0/texen-1.0.jar.md5
> >> >> [henning] org/apache/texen/texen/1.0/texen-1.0.jar.sha1
> >> >> [henning] org/apache/texen/texen/1.0/texen-1.0.pom
> >> >> [henning] org/apache/texen/texen/1.0/texen-1.0.pom.md5
> >> >> [henning] org/apache/texen/texen/1.0/texen-1.0.pom.sha1
> >> >> [henning] org/apache/texen/texen/maven-metadata.xml
> >> >> [henning] org/apache/texen/texen/maven-metadata.xml.md5
> >> >> [henning] org/apache/texen/texen/maven-metadata.xml.sha1
> >> >>
> >> >> Removed
> >> >> -------
> >> >>
> >> >
> >> >
> >>
> >
> >
>
--
I could give you my word as a Spaniard.
No good. I've known too many Spaniards.
-- The Princess Bride
Re: Anakia and texen in the repository
Posted by Carlos Sanchez <ca...@apache.org>.
ok, so you are going to use those groups and put the artifacts only in
the m2 repo from now on, right?
I've rename them, you still have to add the PGP signatures to jars and poms
for next versions I'd suggest you to extend the apache parent pom to
inherit some common information and reduce the size of your poms.
http://repo1.maven.org/maven2/org/apache/apache/4/apache-4.pom
On 5/1/07, Henning Schmiedehausen <he...@apache.org> wrote:
> Thank you for the clarification, Carlos.
>
> Can you fix the repo to use the new id's (org.apache.texen and
> org.apache.anakia) by renaming the directories back and remove the
> velocity-anakia and velocity-texen groups or can we do this ourselves?
>
> Best regards
> Henning
>
>
> Carlos Sanchez schrieb:
> > unfortunately there's no tooling for policy enforcement in the repo
> > and we are force to deal with issues like this after things are
> > deployed and before they get propagated to the mirrors. It's not the
> > best solution, but is the only one right now.
> > And I'm trying to solve future problems based on past experiences.
> >
> > The m1 and m2 repos are automatically converted to each other, so you
> > only need to deploy to one of them.
> >
> > Policies are the same, you can use old groupIds or use new ones under
> > org.apache.*
> >
> > You can put under m1 repo org.apache.velocity groupid, no problem with
> > that. For convenience people usually deploy with ant or m1 to the m1
> > repo and with m2 to the m2 repo.
> >
> > Another different issue is the group naming convention, for me it'd
> > make sense that anakia and texen were under org.apache.velocity.*
> > based on my experience and considering the explosion of groups that
> > could happen if all subprojects start using top level groupIds. AFAIK
> > there's no policy about this, so that's just my suggestion.
> >
> > What it is a policy is that all releases must be PGP signed, and also
> > you have to remove the repositories/repository entry
> > "http://people.apache.org/repo/m2-ibiblio-rsync-repository" from the
> > poms as it's internal use only.
> >
> > Sorry for the trouble. For me it'd be also easier to forget about it,
> > but in the long term this is going to save problems.
> >
> >
> > On 5/1/07, Henning Schmiedehausen <he...@apache.org> wrote:
> >> Carlos,
> >>
> >> please stop this.
> >>
> >> For maven-1, we either keep texen and anakia in the velocity group or
> >> drop it completely from there. That is fine with me, no more groups,
> >> yadda, yadda.
> >>
> >> However, for maven-2 we will adhere to your 'standards'. This means, the
> >> packages go into org.apache.texen and org.apache.anakia. That is the way
> >> *you* as repo people recommended it.
> >>
> >> If you have a problem with the jar being twice in your repo, well, maybe
> >> it is time that you get your act together and have an uniform policy for
> >> maven-1 and maven-2.
> >>
> >> If you do not agree here, then we will go to org.apache.texen and
> >> org.apache.anakia and drop the jars in the velocity group. I am not
> >> really interested in second guessing what you want to have and how you
> >> intend to organize it. The maven repos are a distribution mechanism, not
> >> a policy tool.
> >>
> >> Please rename the .bak directories. Feel free to drop the jars from the
> >> velocity group at your discretion, I do not really care.
> >>
> >>
> >>
> >> Best regards
> >> Henning
> >>
> >>
> >>
> >>
> >> Carlos Sanchez schrieb:
> >> > I guess these are the same as the ones in
> >> > http://people.apache.org/repo/m1-ibiblio-rsync-repository/velocity/jars
> >> >
> >> > - they should be only in the m1 OR m2 repo
> >> > - Putting them in two different groupIds is confusing
> >> > - if they are subprojects of velocity they should be in
> >> > org.apache.velocity.*
> >> > - missing PGP signatures
> >> >
> >> > I've moved anakia and texen out of the way for the moment (to .bak)
> >> >
> >> >
> >> > On 30 Apr 2007 08:16:24 -0000, bayard@apache.org <ba...@apache.org>
> >> wrote:
> >> >> Repository changed
> >> >> ==================
> >> >>
> >> >> Repository: /www/people.apache.org/repo/m2-ibiblio-rsync-repository/
> >> >>
> >> >> Added
> >> >> -----
> >> >> [henning] org/apache/anakia
> >> >> [henning] org/apache/anakia/anakia
> >> >> [henning] org/apache/anakia/anakia/1.0
> >> >> [henning] org/apache/anakia/anakia/1.0/anakia-1.0.jar
> >> >> [henning] org/apache/anakia/anakia/1.0/anakia-1.0.jar.md5
> >> >> [henning] org/apache/anakia/anakia/1.0/anakia-1.0.jar.sha1
> >> >> [henning] org/apache/anakia/anakia/1.0/anakia-1.0.pom
> >> >> [henning] org/apache/anakia/anakia/1.0/anakia-1.0.pom.md5
> >> >> [henning] org/apache/anakia/anakia/1.0/anakia-1.0.pom.sha1
> >> >> [henning] org/apache/anakia/anakia/maven-metadata.xml
> >> >> [henning] org/apache/anakia/anakia/maven-metadata.xml.md5
> >> >> [henning] org/apache/anakia/anakia/maven-metadata.xml.sha1
> >> >> [henning] org/apache/texen
> >> >> [henning] org/apache/texen/texen
> >> >> [henning] org/apache/texen/texen/1.0
> >> >> [henning] org/apache/texen/texen/1.0/texen-1.0.jar
> >> >> [henning] org/apache/texen/texen/1.0/texen-1.0.jar.md5
> >> >> [henning] org/apache/texen/texen/1.0/texen-1.0.jar.sha1
> >> >> [henning] org/apache/texen/texen/1.0/texen-1.0.pom
> >> >> [henning] org/apache/texen/texen/1.0/texen-1.0.pom.md5
> >> >> [henning] org/apache/texen/texen/1.0/texen-1.0.pom.sha1
> >> >> [henning] org/apache/texen/texen/maven-metadata.xml
> >> >> [henning] org/apache/texen/texen/maven-metadata.xml.md5
> >> >> [henning] org/apache/texen/texen/maven-metadata.xml.sha1
> >> >>
> >> >> Removed
> >> >> -------
> >> >>
> >> >
> >> >
> >>
> >
> >
>
--
I could give you my word as a Spaniard.
No good. I've known too many Spaniards.
-- The Princess Bride
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@velocity.apache.org
For additional commands, e-mail: dev-help@velocity.apache.org
Re: Anakia and texen in the repository
Posted by Henning Schmiedehausen <he...@apache.org>.
Thank you for the clarification, Carlos.
Can you fix the repo to use the new id's (org.apache.texen and
org.apache.anakia) by renaming the directories back and remove the
velocity-anakia and velocity-texen groups or can we do this ourselves?
Best regards
Henning
Carlos Sanchez schrieb:
> unfortunately there's no tooling for policy enforcement in the repo
> and we are force to deal with issues like this after things are
> deployed and before they get propagated to the mirrors. It's not the
> best solution, but is the only one right now.
> And I'm trying to solve future problems based on past experiences.
>
> The m1 and m2 repos are automatically converted to each other, so you
> only need to deploy to one of them.
>
> Policies are the same, you can use old groupIds or use new ones under
> org.apache.*
>
> You can put under m1 repo org.apache.velocity groupid, no problem with
> that. For convenience people usually deploy with ant or m1 to the m1
> repo and with m2 to the m2 repo.
>
> Another different issue is the group naming convention, for me it'd
> make sense that anakia and texen were under org.apache.velocity.*
> based on my experience and considering the explosion of groups that
> could happen if all subprojects start using top level groupIds. AFAIK
> there's no policy about this, so that's just my suggestion.
>
> What it is a policy is that all releases must be PGP signed, and also
> you have to remove the repositories/repository entry
> "http://people.apache.org/repo/m2-ibiblio-rsync-repository" from the
> poms as it's internal use only.
>
> Sorry for the trouble. For me it'd be also easier to forget about it,
> but in the long term this is going to save problems.
>
>
> On 5/1/07, Henning Schmiedehausen <he...@apache.org> wrote:
>> Carlos,
>>
>> please stop this.
>>
>> For maven-1, we either keep texen and anakia in the velocity group or
>> drop it completely from there. That is fine with me, no more groups,
>> yadda, yadda.
>>
>> However, for maven-2 we will adhere to your 'standards'. This means, the
>> packages go into org.apache.texen and org.apache.anakia. That is the way
>> *you* as repo people recommended it.
>>
>> If you have a problem with the jar being twice in your repo, well, maybe
>> it is time that you get your act together and have an uniform policy for
>> maven-1 and maven-2.
>>
>> If you do not agree here, then we will go to org.apache.texen and
>> org.apache.anakia and drop the jars in the velocity group. I am not
>> really interested in second guessing what you want to have and how you
>> intend to organize it. The maven repos are a distribution mechanism, not
>> a policy tool.
>>
>> Please rename the .bak directories. Feel free to drop the jars from the
>> velocity group at your discretion, I do not really care.
>>
>>
>>
>> Best regards
>> Henning
>>
>>
>>
>>
>> Carlos Sanchez schrieb:
>> > I guess these are the same as the ones in
>> > http://people.apache.org/repo/m1-ibiblio-rsync-repository/velocity/jars
>> >
>> > - they should be only in the m1 OR m2 repo
>> > - Putting them in two different groupIds is confusing
>> > - if they are subprojects of velocity they should be in
>> > org.apache.velocity.*
>> > - missing PGP signatures
>> >
>> > I've moved anakia and texen out of the way for the moment (to .bak)
>> >
>> >
>> > On 30 Apr 2007 08:16:24 -0000, bayard@apache.org <ba...@apache.org>
>> wrote:
>> >> Repository changed
>> >> ==================
>> >>
>> >> Repository: /www/people.apache.org/repo/m2-ibiblio-rsync-repository/
>> >>
>> >> Added
>> >> -----
>> >> [henning] org/apache/anakia
>> >> [henning] org/apache/anakia/anakia
>> >> [henning] org/apache/anakia/anakia/1.0
>> >> [henning] org/apache/anakia/anakia/1.0/anakia-1.0.jar
>> >> [henning] org/apache/anakia/anakia/1.0/anakia-1.0.jar.md5
>> >> [henning] org/apache/anakia/anakia/1.0/anakia-1.0.jar.sha1
>> >> [henning] org/apache/anakia/anakia/1.0/anakia-1.0.pom
>> >> [henning] org/apache/anakia/anakia/1.0/anakia-1.0.pom.md5
>> >> [henning] org/apache/anakia/anakia/1.0/anakia-1.0.pom.sha1
>> >> [henning] org/apache/anakia/anakia/maven-metadata.xml
>> >> [henning] org/apache/anakia/anakia/maven-metadata.xml.md5
>> >> [henning] org/apache/anakia/anakia/maven-metadata.xml.sha1
>> >> [henning] org/apache/texen
>> >> [henning] org/apache/texen/texen
>> >> [henning] org/apache/texen/texen/1.0
>> >> [henning] org/apache/texen/texen/1.0/texen-1.0.jar
>> >> [henning] org/apache/texen/texen/1.0/texen-1.0.jar.md5
>> >> [henning] org/apache/texen/texen/1.0/texen-1.0.jar.sha1
>> >> [henning] org/apache/texen/texen/1.0/texen-1.0.pom
>> >> [henning] org/apache/texen/texen/1.0/texen-1.0.pom.md5
>> >> [henning] org/apache/texen/texen/1.0/texen-1.0.pom.sha1
>> >> [henning] org/apache/texen/texen/maven-metadata.xml
>> >> [henning] org/apache/texen/texen/maven-metadata.xml.md5
>> >> [henning] org/apache/texen/texen/maven-metadata.xml.sha1
>> >>
>> >> Removed
>> >> -------
>> >>
>> >
>> >
>>
>
>
Re: Anakia and texen in the repository
Posted by Henning Schmiedehausen <he...@apache.org>.
Thank you for the clarification, Carlos.
Can you fix the repo to use the new id's (org.apache.texen and
org.apache.anakia) by renaming the directories back and remove the
velocity-anakia and velocity-texen groups or can we do this ourselves?
Best regards
Henning
Carlos Sanchez schrieb:
> unfortunately there's no tooling for policy enforcement in the repo
> and we are force to deal with issues like this after things are
> deployed and before they get propagated to the mirrors. It's not the
> best solution, but is the only one right now.
> And I'm trying to solve future problems based on past experiences.
>
> The m1 and m2 repos are automatically converted to each other, so you
> only need to deploy to one of them.
>
> Policies are the same, you can use old groupIds or use new ones under
> org.apache.*
>
> You can put under m1 repo org.apache.velocity groupid, no problem with
> that. For convenience people usually deploy with ant or m1 to the m1
> repo and with m2 to the m2 repo.
>
> Another different issue is the group naming convention, for me it'd
> make sense that anakia and texen were under org.apache.velocity.*
> based on my experience and considering the explosion of groups that
> could happen if all subprojects start using top level groupIds. AFAIK
> there's no policy about this, so that's just my suggestion.
>
> What it is a policy is that all releases must be PGP signed, and also
> you have to remove the repositories/repository entry
> "http://people.apache.org/repo/m2-ibiblio-rsync-repository" from the
> poms as it's internal use only.
>
> Sorry for the trouble. For me it'd be also easier to forget about it,
> but in the long term this is going to save problems.
>
>
> On 5/1/07, Henning Schmiedehausen <he...@apache.org> wrote:
>> Carlos,
>>
>> please stop this.
>>
>> For maven-1, we either keep texen and anakia in the velocity group or
>> drop it completely from there. That is fine with me, no more groups,
>> yadda, yadda.
>>
>> However, for maven-2 we will adhere to your 'standards'. This means, the
>> packages go into org.apache.texen and org.apache.anakia. That is the way
>> *you* as repo people recommended it.
>>
>> If you have a problem with the jar being twice in your repo, well, maybe
>> it is time that you get your act together and have an uniform policy for
>> maven-1 and maven-2.
>>
>> If you do not agree here, then we will go to org.apache.texen and
>> org.apache.anakia and drop the jars in the velocity group. I am not
>> really interested in second guessing what you want to have and how you
>> intend to organize it. The maven repos are a distribution mechanism, not
>> a policy tool.
>>
>> Please rename the .bak directories. Feel free to drop the jars from the
>> velocity group at your discretion, I do not really care.
>>
>>
>>
>> Best regards
>> Henning
>>
>>
>>
>>
>> Carlos Sanchez schrieb:
>> > I guess these are the same as the ones in
>> > http://people.apache.org/repo/m1-ibiblio-rsync-repository/velocity/jars
>> >
>> > - they should be only in the m1 OR m2 repo
>> > - Putting them in two different groupIds is confusing
>> > - if they are subprojects of velocity they should be in
>> > org.apache.velocity.*
>> > - missing PGP signatures
>> >
>> > I've moved anakia and texen out of the way for the moment (to .bak)
>> >
>> >
>> > On 30 Apr 2007 08:16:24 -0000, bayard@apache.org <ba...@apache.org>
>> wrote:
>> >> Repository changed
>> >> ==================
>> >>
>> >> Repository: /www/people.apache.org/repo/m2-ibiblio-rsync-repository/
>> >>
>> >> Added
>> >> -----
>> >> [henning] org/apache/anakia
>> >> [henning] org/apache/anakia/anakia
>> >> [henning] org/apache/anakia/anakia/1.0
>> >> [henning] org/apache/anakia/anakia/1.0/anakia-1.0.jar
>> >> [henning] org/apache/anakia/anakia/1.0/anakia-1.0.jar.md5
>> >> [henning] org/apache/anakia/anakia/1.0/anakia-1.0.jar.sha1
>> >> [henning] org/apache/anakia/anakia/1.0/anakia-1.0.pom
>> >> [henning] org/apache/anakia/anakia/1.0/anakia-1.0.pom.md5
>> >> [henning] org/apache/anakia/anakia/1.0/anakia-1.0.pom.sha1
>> >> [henning] org/apache/anakia/anakia/maven-metadata.xml
>> >> [henning] org/apache/anakia/anakia/maven-metadata.xml.md5
>> >> [henning] org/apache/anakia/anakia/maven-metadata.xml.sha1
>> >> [henning] org/apache/texen
>> >> [henning] org/apache/texen/texen
>> >> [henning] org/apache/texen/texen/1.0
>> >> [henning] org/apache/texen/texen/1.0/texen-1.0.jar
>> >> [henning] org/apache/texen/texen/1.0/texen-1.0.jar.md5
>> >> [henning] org/apache/texen/texen/1.0/texen-1.0.jar.sha1
>> >> [henning] org/apache/texen/texen/1.0/texen-1.0.pom
>> >> [henning] org/apache/texen/texen/1.0/texen-1.0.pom.md5
>> >> [henning] org/apache/texen/texen/1.0/texen-1.0.pom.sha1
>> >> [henning] org/apache/texen/texen/maven-metadata.xml
>> >> [henning] org/apache/texen/texen/maven-metadata.xml.md5
>> >> [henning] org/apache/texen/texen/maven-metadata.xml.sha1
>> >>
>> >> Removed
>> >> -------
>> >>
>> >
>> >
>>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@velocity.apache.org
For additional commands, e-mail: dev-help@velocity.apache.org
Re: Anakia and texen in the repository
Posted by Henning Schmiedehausen <hp...@intermeta.de>.
Hi,
no, the policy set with maven-2 and also by the repo people is to use
the package name of the application as it builds nicely into a tree and
avoids having thousands of one-level subdirectories. This has been set
in http://www.apache.org/dev/repository-faq.html (FAQ #1, they seek to
phase out m1 repos).
So for anakia this is org.apache.anakia, for texen it is
org.apache.texen. The repo is not really about project relations and
"this is part of velocity, let's have velocity somewhere". It is a
machine readable tree for downloading dependencies.
Best regards
Henning
Will Glass-Husain schrieb:
> Henning,
>
>
> FYI...Like you, I am not super happy about the jar files being moved
> around (though I think all parties have the best of intentions). It'd
> make sense to me to us the name in the jar path as the group id, e.g.
> org.apache.anakia is anakia, or perhaps velocity-anakia. I'm following
> this - but think it's best we speak with one voice so am deferring to
> you for correspondence with Carlos.
>
> Best, WILL
>
> On 5/1/07, *Carlos Sanchez* <carlos@apache.org
> <ma...@apache.org>> wrote:
>
> unfortunately there's no tooling for policy enforcement in the repo
> and we are force to deal with issues like this after things are
> deployed and before they get propagated to the mirrors. It's not the
> best solution, but is the only one right now.
> And I'm trying to solve future problems based on past experiences.
>
> The m1 and m2 repos are automatically converted to each other, so you
> only need to deploy to one of them.
>
> Policies are the same, you can use old groupIds or use new ones under
> org.apache.*
>
> You can put under m1 repo org.apache.velocity groupid, no problem with
> that. For convenience people usually deploy with ant or m1 to the m1
> repo and with m2 to the m2 repo.
>
> Another different issue is the group naming convention, for me it'd
> make sense that anakia and texen were under org.apache.velocity.*
> based on my experience and considering the explosion of groups that
> could happen if all subprojects start using top level groupIds. AFAIK
> there's no policy about this, so that's just my suggestion.
>
> What it is a policy is that all releases must be PGP signed, and also
> you have to remove the repositories/repository entry
> "http://people.apache.org/repo/m2-ibiblio-rsync-repository
> <http://people.apache.org/repo/m2-ibiblio-rsync-repository>" from the
> poms as it's internal use only.
>
> Sorry for the trouble. For me it'd be also easier to forget about it,
> but in the long term this is going to save problems.
>
>
> On 5/1/07, Henning Schmiedehausen < henning@apache.org
> <ma...@apache.org>> wrote:
> > Carlos,
> >
> > please stop this.
> >
> > For maven-1, we either keep texen and anakia in the velocity group or
> > drop it completely from there. That is fine with me, no more groups,
> > yadda, yadda.
> >
> > However, for maven-2 we will adhere to your 'standards'. This
> means, the
> > packages go into org.apache.texen and org.apache.anakia. That is
> the way
> > *you* as repo people recommended it.
> >
> > If you have a problem with the jar being twice in your repo, well,
> maybe
> > it is time that you get your act together and have an uniform
> policy for
> > maven-1 and maven-2.
> >
> > If you do not agree here, then we will go to org.apache.texen and
> > org.apache.anakia and drop the jars in the velocity group. I am not
> > really interested in second guessing what you want to have and how you
> > intend to organize it. The maven repos are a distribution
> mechanism, not
> > a policy tool.
> >
> > Please rename the .bak directories. Feel free to drop the jars
> from the
> > velocity group at your discretion, I do not really care.
> >
> >
> >
> > Best regards
> > Henning
> >
> >
> >
> >
> > Carlos Sanchez schrieb:
> > > I guess these are the same as the ones in
> > >
> http://people.apache.org/repo/m1-ibiblio-rsync-repository/velocity/jars
> > >
> > > - they should be only in the m1 OR m2 repo
> > > - Putting them in two different groupIds is confusing
> > > - if they are subprojects of velocity they should be in
> > > org.apache.velocity.*
> > > - missing PGP signatures
> > >
> > > I've moved anakia and texen out of the way for the moment (to .bak)
> > >
> > >
> > > On 30 Apr 2007 08:16:24 -0000, bayard@apache.org
> <ma...@apache.org> <bayard@apache.org
> <ma...@apache.org>> wrote:
> > >> Repository changed
> > >> ==================
> > >>
> > >> Repository:
> /www/people.apache.org/repo/m2-ibiblio-rsync-repository/
> > >>
> > >> Added
> > >> -----
> > >> [henning] org/apache/anakia
> > >> [henning] org/apache/anakia/anakia
> > >> [henning] org/apache/anakia/anakia/1.0
> > >> [henning] org/apache/anakia/anakia/1.0/anakia-1.0.jar
> > >> [henning] org/apache/anakia/anakia/1.0/anakia-1.0.jar.md5
> > >> [henning] org/apache/anakia/anakia/1.0/anakia- 1.0.jar.sha1
> > >> [henning] org/apache/anakia/anakia/1.0/anakia-1.0.pom
> > >> [henning] org/apache/anakia/anakia/1.0/anakia-1.0.pom.md5
> > >> [henning] org/apache/anakia/anakia/1.0/anakia- 1.0.pom.sha1
> > >> [henning] org/apache/anakia/anakia/maven-metadata.xml
> > >> [henning] org/apache/anakia/anakia/maven-metadata.xml.md5
> > >> [henning] org/apache/anakia/anakia/maven-metadata.xml.sha1
> > >> [henning] org/apache/texen
> > >> [henning] org/apache/texen/texen
> > >> [henning] org/apache/texen/texen/1.0
> > >> [henning] org/apache/texen/texen/1.0/texen-1.0.jar
> > >> [henning] org/apache/texen/texen/1.0/texen- 1.0.jar.md5
> > >> [henning] org/apache/texen/texen/1.0/texen-1.0.jar.sha1
> > >> [henning] org/apache/texen/texen/1.0/texen-1.0.pom
> > >> [henning] org/apache/texen/texen/1.0/texen-1.0.pom.md5
> > >> [henning] org/apache/texen/texen/1.0/texen-1.0.pom.sha1
> > >> [henning] org/apache/texen/texen/maven-metadata.xml
> > >> [henning] org/apache/texen/texen/maven-metadata.xml.md5
> > >> [henning] org/apache/texen/texen/maven- metadata.xml.sha1
> > >>
> > >> Removed
> > >> -------
> > >>
> > >
> > >
> >
>
>
> --
> I could give you my word as a Spaniard.
> No good. I've known too many Spaniards.
> -- The Princess Bride
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@velocity.apache.org
> <ma...@velocity.apache.org>
> For additional commands, e-mail: dev-help@velocity.apache.org
> <ma...@velocity.apache.org>
>
>
>
>
> --
> Forio Business Simulations
>
> Will Glass-Husain
> wglass@forio.com <ma...@forio.com>
> www.forio.com <http://www.forio.com>
--
Henning P. Schmiedehausen -- hps@intermeta.de | J2EE, Linux
91054 Buckenhof, Germany -- +49 9131 506540 | Apache person
Open Source Consulting, Development, Design | Velocity - Turbine
"Save the cheerleader. Save the world."
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@velocity.apache.org
For additional commands, e-mail: dev-help@velocity.apache.org
Re: Anakia and texen in the repository
Posted by Will Glass-Husain <wg...@gmail.com>.
Henning,
FYI...Like you, I am not super happy about the jar files being moved around
(though I think all parties have the best of intentions). It'd make sense
to me to us the name in the jar path as the group id, e.g.
org.apache.anakiais anakia, or perhaps velocity-anakia. I'm following
this - but think it's
best we speak with one voice so am deferring to you for correspondence with
Carlos.
Best, WILL
On 5/1/07, Carlos Sanchez <ca...@apache.org> wrote:
>
> unfortunately there's no tooling for policy enforcement in the repo
> and we are force to deal with issues like this after things are
> deployed and before they get propagated to the mirrors. It's not the
> best solution, but is the only one right now.
> And I'm trying to solve future problems based on past experiences.
>
> The m1 and m2 repos are automatically converted to each other, so you
> only need to deploy to one of them.
>
> Policies are the same, you can use old groupIds or use new ones under
> org.apache.*
>
> You can put under m1 repo org.apache.velocity groupid, no problem with
> that. For convenience people usually deploy with ant or m1 to the m1
> repo and with m2 to the m2 repo.
>
> Another different issue is the group naming convention, for me it'd
> make sense that anakia and texen were under org.apache.velocity.*
> based on my experience and considering the explosion of groups that
> could happen if all subprojects start using top level groupIds. AFAIK
> there's no policy about this, so that's just my suggestion.
>
> What it is a policy is that all releases must be PGP signed, and also
> you have to remove the repositories/repository entry
> "http://people.apache.org/repo/m2-ibiblio-rsync-repository" from the
> poms as it's internal use only.
>
> Sorry for the trouble. For me it'd be also easier to forget about it,
> but in the long term this is going to save problems.
>
>
> On 5/1/07, Henning Schmiedehausen <he...@apache.org> wrote:
> > Carlos,
> >
> > please stop this.
> >
> > For maven-1, we either keep texen and anakia in the velocity group or
> > drop it completely from there. That is fine with me, no more groups,
> > yadda, yadda.
> >
> > However, for maven-2 we will adhere to your 'standards'. This means, the
> > packages go into org.apache.texen and org.apache.anakia. That is the way
> > *you* as repo people recommended it.
> >
> > If you have a problem with the jar being twice in your repo, well, maybe
> > it is time that you get your act together and have an uniform policy for
> > maven-1 and maven-2.
> >
> > If you do not agree here, then we will go to org.apache.texen and
> > org.apache.anakia and drop the jars in the velocity group. I am not
> > really interested in second guessing what you want to have and how you
> > intend to organize it. The maven repos are a distribution mechanism, not
> > a policy tool.
> >
> > Please rename the .bak directories. Feel free to drop the jars from the
> > velocity group at your discretion, I do not really care.
> >
> >
> >
> > Best regards
> > Henning
> >
> >
> >
> >
> > Carlos Sanchez schrieb:
> > > I guess these are the same as the ones in
> > >
> http://people.apache.org/repo/m1-ibiblio-rsync-repository/velocity/jars
> > >
> > > - they should be only in the m1 OR m2 repo
> > > - Putting them in two different groupIds is confusing
> > > - if they are subprojects of velocity they should be in
> > > org.apache.velocity.*
> > > - missing PGP signatures
> > >
> > > I've moved anakia and texen out of the way for the moment (to .bak)
> > >
> > >
> > > On 30 Apr 2007 08:16:24 -0000, bayard@apache.org <ba...@apache.org>
> wrote:
> > >> Repository changed
> > >> ==================
> > >>
> > >> Repository: /www/people.apache.org/repo/m2-ibiblio-rsync-repository/
> > >>
> > >> Added
> > >> -----
> > >> [henning] org/apache/anakia
> > >> [henning] org/apache/anakia/anakia
> > >> [henning] org/apache/anakia/anakia/1.0
> > >> [henning] org/apache/anakia/anakia/1.0/anakia-1.0.jar
> > >> [henning] org/apache/anakia/anakia/1.0/anakia-1.0.jar.md5
> > >> [henning] org/apache/anakia/anakia/1.0/anakia-1.0.jar.sha1
> > >> [henning] org/apache/anakia/anakia/1.0/anakia-1.0.pom
> > >> [henning] org/apache/anakia/anakia/1.0/anakia-1.0.pom.md5
> > >> [henning] org/apache/anakia/anakia/1.0/anakia-1.0.pom.sha1
> > >> [henning] org/apache/anakia/anakia/maven-metadata.xml
> > >> [henning] org/apache/anakia/anakia/maven-metadata.xml.md5
> > >> [henning] org/apache/anakia/anakia/maven-metadata.xml.sha1
> > >> [henning] org/apache/texen
> > >> [henning] org/apache/texen/texen
> > >> [henning] org/apache/texen/texen/1.0
> > >> [henning] org/apache/texen/texen/1.0/texen-1.0.jar
> > >> [henning] org/apache/texen/texen/1.0/texen-1.0.jar.md5
> > >> [henning] org/apache/texen/texen/1.0/texen-1.0.jar.sha1
> > >> [henning] org/apache/texen/texen/1.0/texen-1.0.pom
> > >> [henning] org/apache/texen/texen/1.0/texen-1.0.pom.md5
> > >> [henning] org/apache/texen/texen/1.0/texen-1.0.pom.sha1
> > >> [henning] org/apache/texen/texen/maven-metadata.xml
> > >> [henning] org/apache/texen/texen/maven-metadata.xml.md5
> > >> [henning] org/apache/texen/texen/maven-metadata.xml.sha1
> > >>
> > >> Removed
> > >> -------
> > >>
> > >
> > >
> >
>
>
> --
> I could give you my word as a Spaniard.
> No good. I've known too many Spaniards.
> -- The Princess Bride
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@velocity.apache.org
> For additional commands, e-mail: dev-help@velocity.apache.org
>
>
--
Forio Business Simulations
Will Glass-Husain
wglass@forio.com
www.forio.com
Re: Anakia and texen in the repository
Posted by Carlos Sanchez <ca...@apache.org>.
unfortunately there's no tooling for policy enforcement in the repo
and we are force to deal with issues like this after things are
deployed and before they get propagated to the mirrors. It's not the
best solution, but is the only one right now.
And I'm trying to solve future problems based on past experiences.
The m1 and m2 repos are automatically converted to each other, so you
only need to deploy to one of them.
Policies are the same, you can use old groupIds or use new ones under
org.apache.*
You can put under m1 repo org.apache.velocity groupid, no problem with
that. For convenience people usually deploy with ant or m1 to the m1
repo and with m2 to the m2 repo.
Another different issue is the group naming convention, for me it'd
make sense that anakia and texen were under org.apache.velocity.*
based on my experience and considering the explosion of groups that
could happen if all subprojects start using top level groupIds. AFAIK
there's no policy about this, so that's just my suggestion.
What it is a policy is that all releases must be PGP signed, and also
you have to remove the repositories/repository entry
"http://people.apache.org/repo/m2-ibiblio-rsync-repository" from the
poms as it's internal use only.
Sorry for the trouble. For me it'd be also easier to forget about it,
but in the long term this is going to save problems.
On 5/1/07, Henning Schmiedehausen <he...@apache.org> wrote:
> Carlos,
>
> please stop this.
>
> For maven-1, we either keep texen and anakia in the velocity group or
> drop it completely from there. That is fine with me, no more groups,
> yadda, yadda.
>
> However, for maven-2 we will adhere to your 'standards'. This means, the
> packages go into org.apache.texen and org.apache.anakia. That is the way
> *you* as repo people recommended it.
>
> If you have a problem with the jar being twice in your repo, well, maybe
> it is time that you get your act together and have an uniform policy for
> maven-1 and maven-2.
>
> If you do not agree here, then we will go to org.apache.texen and
> org.apache.anakia and drop the jars in the velocity group. I am not
> really interested in second guessing what you want to have and how you
> intend to organize it. The maven repos are a distribution mechanism, not
> a policy tool.
>
> Please rename the .bak directories. Feel free to drop the jars from the
> velocity group at your discretion, I do not really care.
>
>
>
> Best regards
> Henning
>
>
>
>
> Carlos Sanchez schrieb:
> > I guess these are the same as the ones in
> > http://people.apache.org/repo/m1-ibiblio-rsync-repository/velocity/jars
> >
> > - they should be only in the m1 OR m2 repo
> > - Putting them in two different groupIds is confusing
> > - if they are subprojects of velocity they should be in
> > org.apache.velocity.*
> > - missing PGP signatures
> >
> > I've moved anakia and texen out of the way for the moment (to .bak)
> >
> >
> > On 30 Apr 2007 08:16:24 -0000, bayard@apache.org <ba...@apache.org> wrote:
> >> Repository changed
> >> ==================
> >>
> >> Repository: /www/people.apache.org/repo/m2-ibiblio-rsync-repository/
> >>
> >> Added
> >> -----
> >> [henning] org/apache/anakia
> >> [henning] org/apache/anakia/anakia
> >> [henning] org/apache/anakia/anakia/1.0
> >> [henning] org/apache/anakia/anakia/1.0/anakia-1.0.jar
> >> [henning] org/apache/anakia/anakia/1.0/anakia-1.0.jar.md5
> >> [henning] org/apache/anakia/anakia/1.0/anakia-1.0.jar.sha1
> >> [henning] org/apache/anakia/anakia/1.0/anakia-1.0.pom
> >> [henning] org/apache/anakia/anakia/1.0/anakia-1.0.pom.md5
> >> [henning] org/apache/anakia/anakia/1.0/anakia-1.0.pom.sha1
> >> [henning] org/apache/anakia/anakia/maven-metadata.xml
> >> [henning] org/apache/anakia/anakia/maven-metadata.xml.md5
> >> [henning] org/apache/anakia/anakia/maven-metadata.xml.sha1
> >> [henning] org/apache/texen
> >> [henning] org/apache/texen/texen
> >> [henning] org/apache/texen/texen/1.0
> >> [henning] org/apache/texen/texen/1.0/texen-1.0.jar
> >> [henning] org/apache/texen/texen/1.0/texen-1.0.jar.md5
> >> [henning] org/apache/texen/texen/1.0/texen-1.0.jar.sha1
> >> [henning] org/apache/texen/texen/1.0/texen-1.0.pom
> >> [henning] org/apache/texen/texen/1.0/texen-1.0.pom.md5
> >> [henning] org/apache/texen/texen/1.0/texen-1.0.pom.sha1
> >> [henning] org/apache/texen/texen/maven-metadata.xml
> >> [henning] org/apache/texen/texen/maven-metadata.xml.md5
> >> [henning] org/apache/texen/texen/maven-metadata.xml.sha1
> >>
> >> Removed
> >> -------
> >>
> >
> >
>
--
I could give you my word as a Spaniard.
No good. I've known too many Spaniards.
-- The Princess Bride
Re: Anakia and texen in the repository
Posted by Carlos Sanchez <ca...@apache.org>.
unfortunately there's no tooling for policy enforcement in the repo
and we are force to deal with issues like this after things are
deployed and before they get propagated to the mirrors. It's not the
best solution, but is the only one right now.
And I'm trying to solve future problems based on past experiences.
The m1 and m2 repos are automatically converted to each other, so you
only need to deploy to one of them.
Policies are the same, you can use old groupIds or use new ones under
org.apache.*
You can put under m1 repo org.apache.velocity groupid, no problem with
that. For convenience people usually deploy with ant or m1 to the m1
repo and with m2 to the m2 repo.
Another different issue is the group naming convention, for me it'd
make sense that anakia and texen were under org.apache.velocity.*
based on my experience and considering the explosion of groups that
could happen if all subprojects start using top level groupIds. AFAIK
there's no policy about this, so that's just my suggestion.
What it is a policy is that all releases must be PGP signed, and also
you have to remove the repositories/repository entry
"http://people.apache.org/repo/m2-ibiblio-rsync-repository" from the
poms as it's internal use only.
Sorry for the trouble. For me it'd be also easier to forget about it,
but in the long term this is going to save problems.
On 5/1/07, Henning Schmiedehausen <he...@apache.org> wrote:
> Carlos,
>
> please stop this.
>
> For maven-1, we either keep texen and anakia in the velocity group or
> drop it completely from there. That is fine with me, no more groups,
> yadda, yadda.
>
> However, for maven-2 we will adhere to your 'standards'. This means, the
> packages go into org.apache.texen and org.apache.anakia. That is the way
> *you* as repo people recommended it.
>
> If you have a problem with the jar being twice in your repo, well, maybe
> it is time that you get your act together and have an uniform policy for
> maven-1 and maven-2.
>
> If you do not agree here, then we will go to org.apache.texen and
> org.apache.anakia and drop the jars in the velocity group. I am not
> really interested in second guessing what you want to have and how you
> intend to organize it. The maven repos are a distribution mechanism, not
> a policy tool.
>
> Please rename the .bak directories. Feel free to drop the jars from the
> velocity group at your discretion, I do not really care.
>
>
>
> Best regards
> Henning
>
>
>
>
> Carlos Sanchez schrieb:
> > I guess these are the same as the ones in
> > http://people.apache.org/repo/m1-ibiblio-rsync-repository/velocity/jars
> >
> > - they should be only in the m1 OR m2 repo
> > - Putting them in two different groupIds is confusing
> > - if they are subprojects of velocity they should be in
> > org.apache.velocity.*
> > - missing PGP signatures
> >
> > I've moved anakia and texen out of the way for the moment (to .bak)
> >
> >
> > On 30 Apr 2007 08:16:24 -0000, bayard@apache.org <ba...@apache.org> wrote:
> >> Repository changed
> >> ==================
> >>
> >> Repository: /www/people.apache.org/repo/m2-ibiblio-rsync-repository/
> >>
> >> Added
> >> -----
> >> [henning] org/apache/anakia
> >> [henning] org/apache/anakia/anakia
> >> [henning] org/apache/anakia/anakia/1.0
> >> [henning] org/apache/anakia/anakia/1.0/anakia-1.0.jar
> >> [henning] org/apache/anakia/anakia/1.0/anakia-1.0.jar.md5
> >> [henning] org/apache/anakia/anakia/1.0/anakia-1.0.jar.sha1
> >> [henning] org/apache/anakia/anakia/1.0/anakia-1.0.pom
> >> [henning] org/apache/anakia/anakia/1.0/anakia-1.0.pom.md5
> >> [henning] org/apache/anakia/anakia/1.0/anakia-1.0.pom.sha1
> >> [henning] org/apache/anakia/anakia/maven-metadata.xml
> >> [henning] org/apache/anakia/anakia/maven-metadata.xml.md5
> >> [henning] org/apache/anakia/anakia/maven-metadata.xml.sha1
> >> [henning] org/apache/texen
> >> [henning] org/apache/texen/texen
> >> [henning] org/apache/texen/texen/1.0
> >> [henning] org/apache/texen/texen/1.0/texen-1.0.jar
> >> [henning] org/apache/texen/texen/1.0/texen-1.0.jar.md5
> >> [henning] org/apache/texen/texen/1.0/texen-1.0.jar.sha1
> >> [henning] org/apache/texen/texen/1.0/texen-1.0.pom
> >> [henning] org/apache/texen/texen/1.0/texen-1.0.pom.md5
> >> [henning] org/apache/texen/texen/1.0/texen-1.0.pom.sha1
> >> [henning] org/apache/texen/texen/maven-metadata.xml
> >> [henning] org/apache/texen/texen/maven-metadata.xml.md5
> >> [henning] org/apache/texen/texen/maven-metadata.xml.sha1
> >>
> >> Removed
> >> -------
> >>
> >
> >
>
--
I could give you my word as a Spaniard.
No good. I've known too many Spaniards.
-- The Princess Bride
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@velocity.apache.org
For additional commands, e-mail: dev-help@velocity.apache.org