On Mar 18, 2008, at 2:29 PM, Reinhard Poetz wrote:
I've created another series of non-Maven release artifacts. See
http://people.apache.org/~reinhard/cocoon-staging/cocoon-servlet-service/
Jar file name to source/documentation directory name mapping is
inconsistent:
Vadim Gritsenko wrote:
On Mar 18, 2008, at 2:29 PM, Reinhard Poetz wrote:
I've created another series of non-Maven release artifacts. See
http://people.apache.org/~reinhard/cocoon-staging/cocoon-servlet-service/
Jar file name to source/documentation directory name mapping is
inconsistent:
Reinhard Poetz wrote:
Vadim Gritsenko wrote:
Do we really have to include each license into single LICENSE.txt file?
I think I missed this development...
There were so many discussions on several Apache lists that I can't point
you to the thread :-/
Anyway, I was following the
I've created another series of non-Maven release artifacts. See
http://people.apache.org/~reinhard/cocoon-staging/cocoon-servlet-service/
and
http://people.apache.org/~reinhard/cocoon-staging/getting-started/
What has changed:
o The archive name is the base directory of the ZIP.
o fix EOL,
Reinhard Poetz wrote:
David Crossley wrote:
I saw that some committers have been using lowercase filenames
e.g. notice.txt, so the release-builder needs to handle that.
Is there some requirement that the file names of notice.txt and
license.txt have to be either lower or upper case? Or is it
Carsten Ziegeler wrote:
Reinhard Poetz wrote:
David Crossley wrote:
I saw that some committers have been using lowercase filenames
e.g. notice.txt, so the release-builder needs to handle that.
Is there some requirement that the file names of notice.txt and
license.txt have to be either
Reinhard Poetz wrote:
If I understood some discussion on [EMAIL PROTECTED] correctly, we would also
have to put NOTICE and LICENSE into the main directory of each
sub-tree, that in our case relates to each of our modules that are
released separately.
Yes.
We should do this clean-up work in
Reinhard Poetz wrote:
David Crossley wrote:
I see that the META-INF/NOTICE.txt etc. files in each
of cocoon-components and impl directory, would correspond
with those from the sources. However where does top-level
NOTICE.txt file come from? Should it be generated as a
combination of the
Carsten Ziegeler wrote:
Reinhard Poetz wrote:
David Crossley wrote:
I saw that some committers have been using lowercase filenames
e.g. notice.txt, so the release-builder needs to handle that.
Is there some requirement that the file names of notice.txt and
license.txt have to be either
David Crossley wrote:
Reinhard Poetz wrote:
Reinhard Poetz wrote:
This time I will
create the Maven 2 release artifacts and normal zip/tar release
artifacts for non-Maven users.
I created release artifacts for the Servlet-Service framework using the old
RC1 release form October last year and
David Crossley wrote:
I saw that some committers have been using lowercase filenames
e.g. notice.txt, so the release-builder needs to handle that.
Is there some requirement that the file names of notice.txt and license.txt have
to be either lower or upper case? Or is it up to us?
--
Reinhard Poetz wrote:
Reinhard Poetz wrote:
This time I will
create the Maven 2 release artifacts and normal zip/tar release
artifacts for non-Maven users.
I created release artifacts for the Servlet-Service framework using the old
RC1 release form October last year and published them to
I saw that some committers have been using lowercase filenames
e.g. notice.txt, so the release-builder needs to handle that.
-David
Reinhard Poetz wrote:
This time I will
create the Maven 2 release artifacts and normal zip/tar release
artifacts for non-Maven users.
I created release artifacts for the Servlet-Service framework using the old RC1
release form October last year and published them to
14 matches
Mail list logo
