Hi,
sebb schrieb:
On 27/05/2009, Felix Meschberger <fmesc...@gmail.com> wrote:
Maven reports the following problem:
[WARNING] Using platform encoding (Cp1252 actually) to copy filtered
resources, i.e. build is platform dependent!
The encoding needs to be explicitly defined if the pom uses filtering.
We do not use filtering for now, so this is not an issue.
You may not have used filters explicitly, but the Maven message says
that it is using Cp1252, so clearly the encoding IS an issue.
Right. And I agree, that we will setup the resource plugin to force
UTF-8 for future builds (we are currently voting on using repository.a.o
for deployments and as a consequence would the inherit vom Apache parent
6, which IIRC has the resource plugin setup correct).
It would be useful if the Manifest files in the jars contained the
Specification and Implementation entries.
We have the OSGi manifest headers, mostly the Bundle-SymbolicName,
Bundle-Version and Bundle-Name headers. These are equivalent. But we will
certainly consider adding at least the Implementation entries in future
releases.
I am referring to items such as:
Implementation-Title:
Implementation-Vendor:
Implementation-Vendor-Id:
Implementation-Version:
Specification-Title:
Specification-Vendor:
Specification-Version:
Although some of the values are present in Bundle headers, the above
are more standard for non-OSGI applications.
Ok. We will setup the bundle plugin to include these standard headers.
Regards
Felix
The Javadoc jar does not contain a NOTICE or a LICENSE file (nor is
the disclaimer mentioned)
I think this needs to be fixed before release.
Hmm, too bad. So lets not publish the Javadoc packages and go on with the
release.
OK.
==
There are various missing SVN properties in
Hmm, thanks for remarking ... Will have to recheck my svn config file again
... (I thought I did that already ;-)
Regards
Felix
On 25/05/2009, Niclas Hedhman <nic...@hedhman.org> wrote:
+1
On May 25, 2009 6:05 PM, "Felix Meschberger" <fmesc...@gmail.com>
wrote:
The Apache Sling community voted on and has approved a proposal to
release Apache Sling MIME type mapping support Version 2.1.0-incubator
bundle. Pursuant to the Releases section of the Incubation Policy we
would now like to request the permission of the Incubator PMC to
publish
the tarball on the Sling Download page (this will be
http://incubator.apache.org/sling/site/download.html).
The following votes were cast:
+1 Felix Meschberger
+1 Carsten Ziegeler
+1 Bertrand Delacretaz
+1 Jukka Zitting
This vote therefore passed with 4 +1 votes and no other votes. All
voters are members of the Sling PPMC and the Incubator PMC.
Please cast your votes!
Thanks
Felix
Proposal, vote thread and vote result:
http://mail-archives.apache.org/mod_mbox/incubator-sling-dev/200905.mbox/%3c4a1130b0.3030...@gmail.com%3e
Releases section of the Incubation Policy:
http://incubator.apache.org/incubation/Incubation_Policy.html#Releases
---------------------------------------------------------------------
To unsubscribe, e-mail:
general-unsubscr...@incubator.apache.org
For additional commands, e-mail:
general-h...@incubator.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail:
general-unsubscr...@incubator.apache.org
For additional commands, e-mail:
general-h...@incubator.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail:
general-unsubscr...@incubator.apache.org
For additional commands, e-mail:
general-h...@incubator.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org
