Can we keep the file in github and remove it from the source
distribution? The file is provided as convenience for contributors to
adhere to the Apex coding style. We may create jar out of the .xml file,
but this will require running the build prior to creating an IDE project
and importing codestyle definition.
Do we need to have license embedded into the .xml file that is currently
inside the jar? The file is generated by IDE.
Vlad
On 1/29/16 17:43, Pramod Immaneni wrote:
Alan, Taylor,
Thanks for the reasoning behind it and the suggestions. We will
immediately look into including the actual text files without
packaging them into a binary file.
Thanks
On Fri, Jan 29, 2016 at 5:21 PM, Alan Gates <[email protected]
<mailto:[email protected]>> wrote:
The problem with jars (or any binary files) is we can't verify the
contents. When I as an IPMC member vote on this I am asserting
that this is safe and good software, in compliance with licenses,
etc. I can't do that once binary code is in there. There's no
way you'll get this through the IPMC with a jar in the source
release. Apache is very insistent that official releases be
source only. This is for its legal protection. You can do a
binary "release" which is just making convenience artifacts
available on the website, that includes this jar if you want, or
you can include the source for the jar (assuming it's not binary)
and put in rules in the pom to jar it up at build time.
Alan.
Pramod Immaneni <mailto:[email protected]>
January 29, 2016 at 16:35
Hi Alan,
The jar only contains code styles for intellij idea ide,
compatible with the coding guidelines for the project and only
contains only xml configuration files. I am running the tests to
see if I can replicate the error you are seeing.
Thanks
Thomas Weise <mailto:[email protected]>
January 29, 2016 at 9:31
Dear Community,
Please vote on the following Apache Apex Core 3.3.0-incubating
release
candidate.
This release adds exciting new features, including support for
iterative
processing, modules (ability to expand building blocks into
subgraph of
lower level operators), new callback to perform custom operator
logic prior
to a checkpoint etc.
This is a source release with binary artifacts published to Maven.
List of all issues fixed: http://s.apache.org/wUB
Staging directory:
https://dist.apache.org/repos/dist/dev/incubator/apex/v3.3.0-incubating-RC1
Source zip:
https://dist.apache.org/repos/dist/dev
/incubator/apex/v3.3.0-incubating-RC1/apex-3.3.0-incubating-source-release.zip
Source tar.gz:
https://dist.apache.org/repos/dist/dev
/incubator/apex/v3.3.0-incubating-RC1/apex-3.3.0-incubating-source-release.tar.
gz
Maven staging repository:
https://repository.apache.org/content/repositories/orgapacheapex-1005/
Git source:
https://git-wip-us.apache.org/repos/asf
?p=incubator-apex-core.git;a=commit;h=refs/tags/v3.3.0-incubating-RC1
(commit: 03c7ef2eb2fbd385196c85ca5da2ac2e6e051233)
PGP key:
http://pgp.mit.edu:11371/pks/lookup?op=vindex&[email protected]
KEYS file:
https://dist.apache.org/repos/dist/release/incubator/apex/KEYS
More information at:
http://apex.incubator.apache.org
Please try the release and vote; vote will be open for at least
72 hours.
[ ] +1 approve (and what verification was done)
[ ] -1 disapprove (and reason why)
http://www.apache.org/foundation/voting.html
Please add (binding) if your vote is binding (PPMC votes are
binding):
http://incubator.apache.org/projects/apex.html
How to verify release candidate (under construction):
https://github.com/sandeepdeshmukh/incubator-apex-site/blob/APEXCORE-215.build-verification-steps/src/md/verification.md
Thanks,
Thomas
