On 29 February 2012 05:11, Konstantin Kolinko knst.koli...@gmail.com wrote:
2012/2/29 Jeremy Boynes jboy...@apache.org:
Removed from svn. A dry run of the next release shows they are automatically
added to the source bundle.
1. Where it takes those files from? Is their content correct.
Reverted r1294943.
Do you know how this was addressed in Commons? Any patches? :)
On Feb 29, 2012, at 9:14 AM, sebb wrote:
On 29 February 2012 05:11, Konstantin Kolinko knst.koli...@gmail.com wrote:
2012/2/29 Jeremy Boynes jboy...@apache.org:
Removed from svn. A dry run of the next release
On 29 February 2012 18:07, Jeremy Boynes jboy...@apache.org wrote:
Reverted r1294943.
Do you know how this was addressed in Commons?
Yes, see commons-parent pom
http://repo1.maven.org/maven2/org/apache/commons/commons-parent/23/commons-parent-23.pom
search for NOTICE
Any patches? :)
On
Perso, I prefer using something which read pom and generate
automatically NL from metadatas rather than maintaining those files
manually (for me manually means you always missed to add/modify :-) )
(but sure it's my POV)
BTW Did you create any issues for that ?
2012/2/29 sebb seb...@gmail.com:
On 29 February 2012 19:15, Olivier Lamy ol...@apache.org wrote:
Perso, I prefer using something which read pom and generate
automatically NL from metadatas rather than maintaining those files
manually (for me manually means you always missed to add/modify :-) )
(but sure it's my POV)
AFAICT
A gentle call for more votes please, only one at the moment.
On Feb 26, 2012, at 11:15 PM, Olivier Lamy wrote:
+1
2012/2/27 Jeremy Boynes jboy...@apache.org:
OK. Artefacts re-staged at
https://repository.apache.org/content/repositories/orgapachetomcat-084/
Thanks
Jeremy
On Feb 26,
On 02/27/2012 12:33 AM, Jeremy Boynes wrote:
OK. Artefacts re-staged at
https://repository.apache.org/content/repositories/orgapachetomcat-084/
+1
Signatures and content OK.
Although not sure why you have LICENSE and LICENSE.txt as well
as NOTICE and NOTICE.txt with the same content
(well,
On 28 February 2012 16:43, Mladen Turk mt...@apache.org wrote:
On 02/27/2012 12:33 AM, Jeremy Boynes wrote:
OK. Artefacts re-staged at
https://repository.apache.org/content/repositories/orgapachetomcat-084/
+1
Signatures and content OK.
Although not sure why you have LICENSE and
On 02/28/2012 08:57 PM, sebb wrote:
On 28 February 2012 16:43, Mladen Turkmt...@apache.org wrote:
Although not sure why you have LICENSE and LICENSE.txt as well
as NOTICE and NOTICE.txt with the same content
That is probably caused by the Apache POM, which tries to be helpful
by adding the
Removed from svn. A dry run of the next release shows they are automatically
added to the source bundle.
Thanks
Jeremy
On Feb 28, 2012, at 12:12 PM, Mladen Turk wrote:
On 02/28/2012 08:57 PM, sebb wrote:
On 28 February 2012 16:43, Mladen Turkmt...@apache.org wrote:
Although not sure why
2012/2/29 Jeremy Boynes jboy...@apache.org:
Removed from svn. A dry run of the next release shows they are automatically
added to the source bundle.
1. Where it takes those files from? Is their content correct.
Besides extra blank lines before and after the text in NOTICE file,
there is
On Feb 28, 2012, at 9:11 PM, Konstantin Kolinko wrote:
2012/2/29 Jeremy Boynes jboy...@apache.org:
Removed from svn. A dry run of the next release shows they are automatically
added to the source bundle.
1. Where it takes those files from? Is their content correct.
The remote-resources
Hello Jeremy,
I think you must first close the repository in the Staging
repositories entry menu.
After that the url
(https://repository.apache.org/content/repositories/orgapachetomcat-068/)
will be available.
2012/2/25 Jeremy Boynes jboy...@apache.org:
The proposed Apache Taglibs Parent POM v1
I do but I can't as it seems I signed with the wrong key - a subkey that is not
recognized.
Can I just delete the subkey from my keyring and re-run release:perform?
On Feb 26, 2012, at 11:20 AM, Olivier Lamy wrote:
Hello Jeremy,
I think you must first close the repository in the Staging
2012/2/26 Jeremy Boynes jboy...@apache.org:
I do but I can't as it seems I signed with the wrong key - a subkey that is
not recognized.
Can I just delete the subkey from my keyring and re-run release:perform?
Yup.
Just delete the current staging repository.
If you still have the
OK. Artefacts re-staged at
https://repository.apache.org/content/repositories/orgapachetomcat-084/
Thanks
Jeremy
On Feb 26, 2012, at 3:00 PM, Olivier Lamy wrote:
2012/2/26 Jeremy Boynes jboy...@apache.org:
I do but I can't as it seems I signed with the wrong key - a subkey that is
not
On 26 February 2012 23:33, Jeremy Boynes jboy...@apache.org wrote:
OK. Artefacts re-staged at
https://repository.apache.org/content/repositories/orgapachetomcat-084/
Looks a bit odd to have
orgapachetomcat
above
yet the Maven package is org.apache.taglibs ?
But perhaps that's just a feature
I believe this is a Nexus thing where orgapachetomcat comes from the staging
profile which I presume is associated with the TLP/PMC that will be voting on a
release. Once released, the artefacts will end up in the repository under
o.a.tagllibs.
Maven's recommendation is that the groupId match
+1
2012/2/27 Jeremy Boynes jboy...@apache.org:
OK. Artefacts re-staged at
https://repository.apache.org/content/repositories/orgapachetomcat-084/
Thanks
Jeremy
On Feb 26, 2012, at 3:00 PM, Olivier Lamy wrote:
2012/2/26 Jeremy Boynes jboy...@apache.org:
I do but I can't as it seems I
The proposed Apache Taglibs Parent POM v1 release is now available for voting.
This contains Maven project metadata for building and releasing the actual
Taglibs project files.
The Maven staging repo is:
https://repository.apache.org/content/repositories/orgapachetomcat-068/
The svn tag is:
20 matches
Mail list logo
