[EMAIL PROTECTED] wrote:
I prefer to have version in the filename. but do we want to FORCE that
on projects prublishing to our repository.
Yes.
Ok I think we can concur. and add this to the requirement/ Goals doc
All artifacts in the repository WILL include the version in t
Nick Chalko <[EMAIL PROTECTED]> wrote on 31/10/2003 10:32:28 AM:
> [EMAIL PROTECTED] wrote:
>
> >Nick Chalko <[EMAIL PROTECTED]> wrote on 31/10/2003 09:05:06 AM:
> >>Must every artivact have the version in the file name?
> >>
> >Definitely.
>
> Some artifacts don't like having the full version n
Adam R. B. Jack wrote:
I feel we could/should unashamedly complete our thoughts on Java, then go
and recruit some per-language specialists to chime in on their flavour.
Maybe we'll have one repository 'class' with per language sub-classes. Let's
mature what we can agree upon before we specialize &
> Some artifacts don't like having the full version number.
> dll for example. I think the DLL name needs to be stable and thus
> would not have the full version info.
> For the dll example we can mandate that it has to be put in a versioned
> zip/tar.gzip
If we continue to think 100% genericall
[EMAIL PROTECTED] wrote:
Nick Chalko <[EMAIL PROTECTED]> wrote on 31/10/2003 09:05:06 AM:
Must every artivact have the version in the file name?
Definitely.
Some artifacts don't like having the full version number.
dll for example. I think the DLL name needs to be stable and thus
"Adam R. B. Jack" <[EMAIL PROTECTED]> wrote on 31/10/2003 09:10:44 AM:
> Folks wrote:
> Are we discussing URI or URL? If URI, ok good .. but is this current?
>
> I thought it was more like (w/ pseudo-regexp notation):
>
> http:jars/[-][-].ext
'jars' is the of the thing. e.g. jars, tlds
Nick Chalko <[EMAIL PROTECTED]> wrote on 31/10/2003 09:05:06 AM:
> So here are some open questions.
>
> How do we pick unique human readable top level directories, in other
> words how do we name the directories for projects ad sub-projects.
Again, only as an example, maven takes the subproje
[EMAIL PROTECTED] wrote:
There is still some naming details to work out. An apache project can
be a very big thing.
Take the CLI project in Jakarta commons that would be
apache-jakarta-commons-cli
vs the pacakge name org.apache.commons.cli
This is where the previous naming conventi
Nick Chalko <[EMAIL PROTECTED]> wrote on 31/10/2003 08:38:36 AM:
> >Since this is an ASF repo, isn't the ASF project name enough?
> >
> >
> >
> I think I would still prefix it with apache, so that other organizations
> can follow our pattern with out conflicts. Also allowing other
> reposito
Folks wrote:
> >
> > So here is a key focuossed issue.
> > What should the URI look like
> >
> > The latest URI discussed was
> >
> > http:/artifact-[].ext
> >
> > For example
> > * http://repo.apache.org/org-apache-ant/1.5.1/ant-1.5.1.jar
Are we discussing URI or URL? If URI, ok good .. but
So here are some open questions.
How do we pick unique human readable top level directories, in other
words how do we name the directories for projects ad sub-projects.
Should each version have its own subdir?
Should each artifact type have it's own subir?
Do we support both version and type su
Nick Chalko wrote:
...
What should the URI look like
The latest URI discussed was
http:/artifact-[].ext
For example
* http://repo.apache.org/org-apache-ant/1.5.1/ant-1.5.1.jar
* http://repo.apache.org/org-apache-ant/1.5.1/ant-testutil-1.5.1.jar
* http://repo.apache.org/org-apache-ant/1.5.1/LICE
[EMAIL PROTECTED] wrote:
= Special versions. =
Most people agree we should support Latest (released), and Nightly,
along with the normal released builds
Maven also has 'SNAPSHOT' which is similar in context to Nightly, but not
necessarily built on a nightly basis.
+1
The part still n
Nick Chalko <[EMAIL PROTECTED]> wrote on 31/10/2003 05:43:38 AM:
> [EMAIL PROTECTED] wrote:
>
> >
> >Simple focussed discussion without talking about incubating projects or
> >adopting projects works for me. Those are separate issues.
>
> So here is a key focuossed issue.
> What should the URI
Noel J. Bergman wrote:
The part still needs to be decided is the project name.
I think the most stable idea proposed is the java package name with -
instead of .
Let's be careful. We should be -1 to anything that is Java-specific in such
manner as to preclude non-Java projects. Reme
> The part still needs to be decided is the project name.
> I think the most stable idea proposed is the java package name with -
> instead of .
Let's be careful. We should be -1 to anything that is Java-specific in such
manner as to preclude non-Java projects. Rememnber: this is the ASF
Repos
16 matches
Mail list logo