You are viewing a plain text version of this content. The canonical link for it is here.
Posted to repository@apache.org by Henri Yandell <fl...@gmail.com> on 2006/04/14 19:38:16 UTC
Repo complaints
First off, an ibiblio complaint rather than our repo.
There are sources.jars on ibiblio for Apache code that do not look
like they were released via the Apache repository. How do we find out
how they got there?
http://www.ibiblio.org/maven2/commons-lang/commons-lang/2.0/
Secondly, jars are removed from java-repository. Are we doing this
now? The accompanying pom files weren't deleted, so our removal
process isn't up to scratch.
and a question, is the distributions/ bit in the m1 style repository a
dead concept that we can delete?
Hen
Re: Repo complaints
Posted by Henri Yandell <fl...@gmail.com>.
On 4/14/06, Brett Porter <br...@gmail.com> wrote:
> On 4/15/06, Henri Yandell <fl...@gmail.com> wrote:
> > Secondly, jars are removed from java-repository. Are we doing this
> > now? The accompanying pom files weren't deleted, so our removal
> > process isn't up to scratch.
>
> I don't understand what you are referring to. Is who doing what?
>
> If you are expecting deletions to be propogated - no, they are not currently.
Nope, just didn't know that we were actively deleting the old jars
yet, just thought it had been talked about.
If it has - should the pom files be being deleted too or are they
being left on purpose?
Hen
Re: Repo complaints
Posted by Brett Porter <br...@gmail.com>.
On 4/15/06, Henri Yandell <fl...@gmail.com> wrote:
> Secondly, jars are removed from java-repository. Are we doing this
> now? The accompanying pom files weren't deleted, so our removal
> process isn't up to scratch.
I don't understand what you are referring to. Is who doing what?
If you are expecting deletions to be propogated - no, they are not currently.
- Brett
Re: Repo complaints
Posted by Henri Yandell <fl...@gmail.com>.
On 4/14/06, Carlos Sanchez <ca...@apache.org> wrote:
> On 4/14/06, Henri Yandell <fl...@gmail.com> wrote:
> > Any reason not to just rm the distribution folders?
>
> nope
I'll look into doing so.
> > On the commons-lang source/javadoc - how do the projects replace the
> > ones currently deployed? Can we deploy to the m1 repository on apache
> > and it'll replace, or will the ones that are there by hand take
> > precedence?
>
> new ones will replace old ones (I think). We'll need to check after.
>
> >
> > How do you build them out of interest? Source distribution, svn tag? I
> > noticed that they don't have a manifest (I presume you used zip rather
> > than jar?), is there a need for a manifest?
>
> they only use case for them I know is IDE integration, so as long as
> it's a valid jar it's ok. You can do either from tag or source distro
Reason for asking in this case is that until very recently the tag for
Lang 2.1 was broken - it had source that shouldn't be in it. I'm
guessing you used the distro or did it after the tag was fixed as
you've not got the text package in there.
Hen
Re: Repo complaints
Posted by Carlos Sanchez <ca...@apache.org>.
On 4/14/06, Henri Yandell <fl...@gmail.com> wrote:
> Any reason not to just rm the distribution folders?
nope
>
> On the commons-lang source/javadoc - how do the projects replace the
> ones currently deployed? Can we deploy to the m1 repository on apache
> and it'll replace, or will the ones that are there by hand take
> precedence?
new ones will replace old ones (I think). We'll need to check after.
>
> How do you build them out of interest? Source distribution, svn tag? I
> noticed that they don't have a manifest (I presume you used zip rather
> than jar?), is there a need for a manifest?
they only use case for them I know is IDE integration, so as long as
it's a valid jar it's ok. You can do either from tag or source distro
>
> Hen
>
> On 4/14/06, Carlos Sanchez <ca...@apache.org> wrote:
> > distributions folder is not used right now for the m2 repo
> >
> > I've uploaded sources for the apache projects directly to ibiblio. I'd
> > be more than happy to force apache projects to do it themselves, but
> > until it is a reality I wouldn't like to prevent users to contribute
> > the sources or javadocs unofficially, as the possible harm is really
> > minimal.
> >
> > On 4/14/06, Wendy Smoak <ws...@gmail.com> wrote:
> > > On 4/14/06, Henri Yandell <fl...@gmail.com> wrote:
> > >
> > > > First off, an ibiblio complaint rather than our repo.
> > > >
> > > > There are sources.jars on ibiblio for Apache code that do not look
> > > > like they were released via the Apache repository. How do we find out
> > > > how they got there?
> > >
> > > Here's one way:
> > > http://jira.codehaus.org/browse/MAVENUPLOAD-838
> > > http://www.ibiblio.org/maven2/struts/struts-el/1.2.9/
> > >
> > > ISTR in the past, uploads for Apache projects being rejected and the
> > > user referred to the project. Maybe that's only for the binaries?
> > >
> > > --
> > > Wendy
> > >
> >
> >
> > --
> > I could give you my word as a Spaniard.
> > No good. I've known too many Spaniards.
> > -- The Princess Bride
> >
>
--
I could give you my word as a Spaniard.
No good. I've known too many Spaniards.
-- The Princess Bride
Re: Repo complaints
Posted by Henri Yandell <fl...@gmail.com>.
Any reason not to just rm the distribution folders?
On the commons-lang source/javadoc - how do the projects replace the
ones currently deployed? Can we deploy to the m1 repository on apache
and it'll replace, or will the ones that are there by hand take
precedence?
How do you build them out of interest? Source distribution, svn tag? I
noticed that they don't have a manifest (I presume you used zip rather
than jar?), is there a need for a manifest?
Hen
On 4/14/06, Carlos Sanchez <ca...@apache.org> wrote:
> distributions folder is not used right now for the m2 repo
>
> I've uploaded sources for the apache projects directly to ibiblio. I'd
> be more than happy to force apache projects to do it themselves, but
> until it is a reality I wouldn't like to prevent users to contribute
> the sources or javadocs unofficially, as the possible harm is really
> minimal.
>
> On 4/14/06, Wendy Smoak <ws...@gmail.com> wrote:
> > On 4/14/06, Henri Yandell <fl...@gmail.com> wrote:
> >
> > > First off, an ibiblio complaint rather than our repo.
> > >
> > > There are sources.jars on ibiblio for Apache code that do not look
> > > like they were released via the Apache repository. How do we find out
> > > how they got there?
> >
> > Here's one way:
> > http://jira.codehaus.org/browse/MAVENUPLOAD-838
> > http://www.ibiblio.org/maven2/struts/struts-el/1.2.9/
> >
> > ISTR in the past, uploads for Apache projects being rejected and the
> > user referred to the project. Maybe that's only for the binaries?
> >
> > --
> > Wendy
> >
>
>
> --
> I could give you my word as a Spaniard.
> No good. I've known too many Spaniards.
> -- The Princess Bride
>
Re: Repo complaints
Posted by Carlos Sanchez <ca...@apache.org>.
distributions folder is not used right now for the m2 repo
I've uploaded sources for the apache projects directly to ibiblio. I'd
be more than happy to force apache projects to do it themselves, but
until it is a reality I wouldn't like to prevent users to contribute
the sources or javadocs unofficially, as the possible harm is really
minimal.
On 4/14/06, Wendy Smoak <ws...@gmail.com> wrote:
> On 4/14/06, Henri Yandell <fl...@gmail.com> wrote:
>
> > First off, an ibiblio complaint rather than our repo.
> >
> > There are sources.jars on ibiblio for Apache code that do not look
> > like they were released via the Apache repository. How do we find out
> > how they got there?
>
> Here's one way:
> http://jira.codehaus.org/browse/MAVENUPLOAD-838
> http://www.ibiblio.org/maven2/struts/struts-el/1.2.9/
>
> ISTR in the past, uploads for Apache projects being rejected and the
> user referred to the project. Maybe that's only for the binaries?
>
> --
> Wendy
>
--
I could give you my word as a Spaniard.
No good. I've known too many Spaniards.
-- The Princess Bride
Re: Repo complaints
Posted by Wendy Smoak <ws...@gmail.com>.
On 4/14/06, Henri Yandell <fl...@gmail.com> wrote:
> First off, an ibiblio complaint rather than our repo.
>
> There are sources.jars on ibiblio for Apache code that do not look
> like they were released via the Apache repository. How do we find out
> how they got there?
Here's one way:
http://jira.codehaus.org/browse/MAVENUPLOAD-838
http://www.ibiblio.org/maven2/struts/struts-el/1.2.9/
ISTR in the past, uploads for Apache projects being rejected and the
user referred to the project. Maybe that's only for the binaries?
--
Wendy