[Commons Wiki] Update of "UsingGIT" by BerndEckenfels
Dear Wiki user, You have subscribed to a wiki page or wiki category on "Commons Wiki" for change notification. The "UsingGIT" page has been changed by BerndEckenfels: https://wiki.apache.org/commons/UsingGIT?action=diff&rev1=21&rev2=22 Comment: fixed remote show command and added more context `git checkout -- `''path'' * `svn info` -`git remote -v` and `git remote origin` +`git remote -v` lists all remotes and `git remote show ` shows details about remote (for example `git remote show origin` for the default remote name). * `svn cp` ''https://svn.apache.org/.../trunk'' ''https://svn.apache.org/.../tags/my-tag'' `-m message` `git tag -m message my-tag` (or better, add also -s or -u option to create a cryptographically signed tag)<> - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
[Commons Wiki] Update of "UsingGIT" by sebbapache
Dear Wiki user, You have subscribed to a wiki page or wiki category on "Commons Wiki" for change notification. The "UsingGIT" page has been changed by sebbapache: https://wiki.apache.org/commons/UsingGIT?action=diff&rev1=20&rev2=21 Comment: How to fix EOL in working copy If there haven't been any merge conflicts you can simply push the result. Otherwise you've got to resolve the conflict and commit the result of the merge before pushing. + == Fixing line endings in working copy == + + Ensure that .gitattributes is set up correctly. + + If your version of git honors it you can apply the attributes to your existing + working copy by pulling, removing .git/index and then running "git reset + --hard" + - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
[Commons Wiki] Update of "ContributorsGroup" by StefanBodewig
Dear Wiki user, You have subscribed to a wiki page or wiki category on "Commons Wiki" for change notification. The "ContributorsGroup" page has been changed by StefanBodewig: https://wiki.apache.org/commons/ContributorsGroup?action=diff&rev1=15&rev2=16 * NiallPemberton * OliverHeger * PhilSteitz + * RobTompkins * SebastienBrisard * SimoneTripodi * ThomasNeidhart * ThomasVandahl * Woonsan Ko - - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
[Commons Wiki] Update of "MovingToGit" by BenediktRitter
Dear Wiki user, You have subscribed to a wiki page or wiki category on "Commons Wiki" for change notification. The "MovingToGit" page has been changed by BenediktRitter: https://wiki.apache.org/commons/MovingToGit?action=diff&rev1=7&rev2=8 Comment: Add requirement to start a vote before migration Notes on things to look out for if a component moves from SVN to Git. * This is a work in progress * + + == Start a vote == + + To migrate a component to git, start a VOTE by LAZY CONSENSUS on the dev ML. If the vote passes, proceed with the following steps. == Request a new Git repository == - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
[Commons Wiki] Update of "MovingToGit" by BenediktRitter
Dear Wiki user, You have subscribed to a wiki page or wiki category on "Commons Wiki" for change notification. The "MovingToGit" page has been changed by BenediktRitter: https://wiki.apache.org/commons/MovingToGit?action=diff&rev1=6&rev2=7 Comment: Better formatting == Migrate code to new repository == - 1. Clone the new Git repository: git clone https://git-wip-us.apache.org/repos/asf/commons-foo.git + 1. Clone the new Git repository: git clone https://git-wip-us.apache.org/repos/asf/commons-foo.git - 2. Add the already existing GitHub mirror as new remote: git remote add GitHub g...@github.com:apache/commons-foo.git + 2. Add the already existing GitHub mirror as new remote: git remote add GitHub g...@github.com:apache/commons-foo.git - 3. Create the master branch: git checkout -b master + 3. Create the master branch: git checkout -b master - 4. Add all commits from the mirrored trunk branch from the GitHub mirror to the master branch: git fetch github trunk && git merge github/trunk + 4. Add all commits from the mirrored trunk branch from the GitHub mirror to the master branch: git fetch github trunk && git merge github/trunk - 5. Add all other branches and tags to your local repository + 5. Add all other branches and tags to your local repository - 6. push everything to the new repository + 6. push everything to the new repository == Update pom and website == - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
[Commons Wiki] Update of "MovingToGit" by BenediktRitter
Dear Wiki user, You have subscribed to a wiki page or wiki category on "Commons Wiki" for change notification. The "MovingToGit" page has been changed by BenediktRitter: https://wiki.apache.org/commons/MovingToGit?action=diff&rev1=5&rev2=6 Comment: Describe what to do in order to migrate code from svn to git == Request a new Git repository == Requesting git repositories is managed by an Infra self-service which is located at http://reporeq.apache.org. Go to that website an request the new git repository. Note, that the repository name has to be the component name. So for example for Commons CLI, the repository name had to be "cli". This generated "commons-cli" as generated name. + + == Migrate code to new repository == + + 1. Clone the new Git repository: git clone https://git-wip-us.apache.org/repos/asf/commons-foo.git + 2. Add the already existing GitHub mirror as new remote: git remote add GitHub g...@github.com:apache/commons-foo.git + 3. Create the master branch: git checkout -b master + 4. Add all commits from the mirrored trunk branch from the GitHub mirror to the master branch: git fetch github trunk && git merge github/trunk + 5. Add all other branches and tags to your local repository + 6. push everything to the new repository == Update pom and website == - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
[Commons Wiki] Update of "MovingToGit" by BenediktRitter
Dear Wiki user, You have subscribed to a wiki page or wiki category on "Commons Wiki" for change notification. The "MovingToGit" page has been changed by BenediktRitter: https://wiki.apache.org/commons/MovingToGit?action=diff&rev1=4&rev2=5 Comment: Document how to request git repositories Notes on things to look out for if a component moves from SVN to Git. * This is a work in progress * + + == Request a new Git repository == + + Requesting git repositories is managed by an Infra self-service which is located at http://reporeq.apache.org. Go to that website an request the new git repository. Note, that the repository name has to be the component name. So for example for Commons CLI, the repository name had to be "cli". This generated "commons-cli" as generated name. == Update pom and website == - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
[Commons Wiki] Update of "FrontPage" by sebbapache
Dear Wiki user, You have subscribed to a wiki page or wiki category on "Commons Wiki" for change notification. The "FrontPage" page has been changed by sebbapache: https://wiki.apache.org/commons/FrontPage?action=diff&rev1=137&rev2=138 Comment: += Security Committers: CommonsPeople | ComponentPlans | CommonsCommitters | CommonsOsgi | UsingNexus | CommonsGroupids | Maven3Plan Bug Reports: [[https://issues.apache.org/jira/secure/Dashboard.jspa|Jira]] + + Security Reports: [[http://commons.apache.org/security.html|Security]] = Components = On this wiki: - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
[Commons Wiki] Update of "CommonsGroupids" by sebbapache
Dear Wiki user, You have subscribed to a wiki page or wiki category on "Commons Wiki" for change notification. The "CommonsGroupids" page has been changed by sebbapache: https://wiki.apache.org/commons/CommonsGroupids?action=diff&rev1=2&rev2=3 Comment: Typo Many Commons components have migrated to the Maven groupId ''org.apache.commons'', but some are still using groupIds of the form ''commons-''. - '''Note that the groupId can only be changed if the Java package is also changed; see MavenAndClassPath'''. + '''Note that the groupId can only be changed if the Java package is also changed; see MavenAndClasspath'''. This page records which components still use their own groupIds, and whether there are any plans to migrate to ''org.apache.commons'' or not. - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
[Commons Wiki] Update of "CommonsGroupids" by sebbapache
Dear Wiki user, You have subscribed to a wiki page or wiki category on "Commons Wiki" for change notification. The "CommonsGroupids" page has been changed by sebbapache: https://wiki.apache.org/commons/CommonsGroupids?action=diff&rev1=1&rev2=2 = Commons GroupIds = Many Commons components have migrated to the Maven groupId ''org.apache.commons'', but some are still using groupIds of the form ''commons-''. + + '''Note that the groupId can only be changed if the Java package is also changed; see MavenAndClassPath'''. This page records which components still use their own groupIds, and whether there are any plans to migrate to ''org.apache.commons'' or not. - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
[Commons Wiki] Update of "CodeStyle" by sebbapache
Dear Wiki user, You have subscribed to a wiki page or wiki category on "Commons Wiki" for change notification. The "CodeStyle" page has been changed by sebbapache: https://wiki.apache.org/commons/CodeStyle?action=diff&rev1=13&rev2=14 1. Mutable data: this increases the difficulty of ensuring thread-safety (including safe publication of changes). Data should be confined to a class; mutation should only be allowed via a setter which can ensure thread-safety. Be careful that the getter does not expose array contents (which are always mutable) 1. Even constants can cause problems: the Java compiler can inline constant values from another class. So if the constant should ever change, classes that are not recompiled could contain the old value. 1. Array entries are always mutable. Only empty arrays are immutable; they can be safely shared. + 1. If a reference to a mutable object is exposed via a getter, then it can be modified in a way that breaks thread-safety. + 1. If a mutable object is saved by a setter and the caller keeps a reference to the object then it can be changed without using the setter, bypassing any restrictions the setter would have enforced. - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
[Commons Wiki] Update of "CodeStyle" by sebbapache
Dear Wiki user, You have subscribed to a wiki page or wiki category on "Commons Wiki" for change notification. The "CodeStyle" page has been changed by sebbapache: https://wiki.apache.org/commons/CodeStyle?action=diff&rev1=12&rev2=13 Comment: OK to expose primitives via getter/setter ||Object visibility should be the minimum required (See notes)||warning || ||Prefer immutable classes as these are automatically thread-safe ||info || ||Mutable fields must be private (See notes)||error || - ||Mutable fields should not be exposed via getters/setters (See notes)||warning || + ||Mutable fields (except primitives) should not be exposed via getters/setters (See notes)||warning || ||Add your rule here ||warning || Notes: - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
[Commons Wiki] Update of "CodeStyle" by sebbapache
Dear Wiki user, You have subscribed to a wiki page or wiki category on "Commons Wiki" for change notification. The "CodeStyle" page has been changed by sebbapache: https://wiki.apache.org/commons/CodeStyle?action=diff&rev1=11&rev2=12 Comment: += array entry mutability 1. Object visibility: once code is released, it can be impossible to reduce the visibility of fields, classes, methods without breaking compatibility, so initial releases should use the minimum visibility possible. 1. Mutable data: this increases the difficulty of ensuring thread-safety (including safe publication of changes). Data should be confined to a class; mutation should only be allowed via a setter which can ensure thread-safety. Be careful that the getter does not expose array contents (which are always mutable) 1. Even constants can cause problems: the Java compiler can inline constant values from another class. So if the constant should ever change, classes that are not recompiled could contain the old value. + 1. Array entries are always mutable. Only empty arrays are immutable; they can be safely shared. - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
[Commons Wiki] Update of "CodeStyle" by sebbapache
Dear Wiki user, You have subscribed to a wiki page or wiki category on "Commons Wiki" for change notification. The "CodeStyle" page has been changed by sebbapache: https://wiki.apache.org/commons/CodeStyle?action=diff&rev1=10&rev2=11 Comment: Warning re: constant inlining 1. Document authors in POM, not in source files (see http://markmail.org/message/k34w6gsx5iic45z2). 1. Object visibility: once code is released, it can be impossible to reduce the visibility of fields, classes, methods without breaking compatibility, so initial releases should use the minimum visibility possible. 1. Mutable data: this increases the difficulty of ensuring thread-safety (including safe publication of changes). Data should be confined to a class; mutation should only be allowed via a setter which can ensure thread-safety. Be careful that the getter does not expose array contents (which are always mutable) + 1. Even constants can cause problems: the Java compiler can inline constant values from another class. So if the constant should ever change, classes that are not recompiled could contain the old value. - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
[Commons Wiki] Update of "Compress" by StefanBodewig
Dear Wiki user,
You have subscribed to a wiki page or wiki category on "Commons Wiki" for
change notification.
The "Compress" page has been changed by StefanBodewig:
https://wiki.apache.org/commons/Compress?action=diff&rev1=8&rev2=9
Comment:
COMPRESS-381 - improve performance by buffering
Same goes for Compressor. Compressor streams are: bz2, gz, lzma, xz, pack200,
Z.
=== Compressing a file ===
- {{{final OutputStream out = new FileOutputStream(output);
+ {{{final OutputStream out = new BufferedOutputStream(new
FileOutputStream(output));
CompressorOutputStream cos = new
CompressorStreamFactory().createCompressorOutputStream("bzip2", out);
IOUtils.copy(new FileInputStream(input), cos);
cos.close();}}}
=== Decompressing a file ===
- {{{final InputStream is = new FileInputStream(input);
+ {{{final InputStream is = new BufferedInputStream(new
FileInputStream(input));
CompressorInputStream in = new
CompressorStreamFactory().createCompressorInputStream("bzip2", is);
IOUtils.copy(in, new FileOutputStream(output));
in.close();}}}
-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org
[Commons Wiki] Update of "CompressRoadmap" by StefanBodewig
Dear Wiki user,
You have subscribed to a wiki page or wiki category on "Commons Wiki" for
change notification.
The "CompressRoadmap" page has been changed by StefanBodewig:
https://wiki.apache.org/commons/CompressRoadmap?action=diff&rev1=19&rev2=20
Compress has seen several releases of the 1.x series. While the factory and
stream APIs have proven to be useful there are pieces that "don't feel right"
and cannot be changed without breaking backwards compatibility. Also Compress'
API has been designed for Java 1.4 and could benefit from generics and enums.
- The idea of a 2.0 release that is allowed to break backwards compatibility
has come up more than once over a span of three years or even longer. This
page will gather requirements and design ideas in the hope that a real
implementation will be created based on the existing code.
+ The idea of a 2.0 release that is allowed to break backwards compatibility
has come up more than once over a span of five years or even longer. This page
will gather requirements and design ideas in the hope that a real
implementation will be created based on the existing code.
- A starting ground for some design ideas is
http://svn.apache.org/repos/asf/commons/proper/compress/branches/compress-2.0/
- nothing carved into stone, yet. Feedback, ideas and corrections more than
welcome.
+ A starting ground for some design ideas is the compress-2.0 branch
https://git-wip-us.apache.org/repos/asf?p=commons-compress.git;a=tree;h=refs/heads/compress-2.0;hb=refs/heads/compress-2.0
- nothing carved into stone, yet. Feedback, ideas and corrections more than
welcome.
== General ==
- * SETTLED: Compress 2.0 will require Java7 at compile and run time.
+ * SETTLED: Compress 2.0 will require Java8 at compile and run time.
* external dependencies?
@@ -32, +32 @@
* common solutions for streaming
- pack200 has to use a temporary files or hold the result in memory as it
uses an API that converts a stream with a single call. The archive classes
that need random access can currently only work on files. Some options have
been discussed on the mailing list in this thread:
http://markmail.org/thread/2jr5qapuynnxnfx6
+ pack200 has to use a temporary files or hold the result in memory as it
uses an API that converts a stream with a single call. The archive classes
that need random access can currently only work on files. This will change for
1.13 with support for SeekableByteChannel
* read-only support
- The list of formats we ca read but not write seems to be growing. Do we
want to add some sort of meta-data for a format we can query to know whether it
supports writing? Might be part of the "make factories configurable" solution.
+ The list of formats we can read but not write seems to be growing. Do we
want to add some sort of meta-data for a format we can query to know whether it
supports writing? Might be part of the "make factories configurable" solution.
* events for certain stages of (un)archiving/(un)compressing?
@@ -50, +50 @@
* unify common stuff in ArchiveEntry
- this includes extracting a common representation for modes/persmission
(COMPRESS-136) but doesn't need to stop there. There is a discussion thread
that is more than three years old with ideas about this:
http://markmail.org/thread/fsxtzs3vsepycu25
+ this includes extracting a common representation for modes/permission
(COMPRESS-136) but doesn't need to stop there. There is a discussion thread
that is more than three years old with ideas about this:
http://markmail.org/thread/fsxtzs3vsepycu25
* embrace generics at least for the {{{getNextEntry}}}/{{{putArchiveEntry}}}
methods
-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org
[Commons Wiki] Update of "VfsReleaseState" by BerndEckenfels
Dear Wiki user, You have subscribed to a wiki page or wiki category on "Commons Wiki" for change notification. The "VfsReleaseState" page has been changed by BerndEckenfels: https://wiki.apache.org/commons/VfsReleaseState?action=diff&rev1=20&rev2=21 Comment: is released: 2.1 - = Upcoming commons-vfs2-2.1 release = + = Upcoming commons-vfs2-2.2 release = - * Preview of Site: N/A + * News: Apache Commons VFS 2.1 has been released. + * State: next release 2.1.1 or 2.2 is considered + == Todo List for Releases == - This is a list of things to do for the (upcoming) next release of VFS 2.1 - - * explain/resolve clirr incompatibilities - * create and commit RELEASE-NOTES.txt (Java6, hadoop - draft with all changes checked in) - * step through the release process for software and site Things to be aware of + * VFS is a multi-module project, sandbox is even optional (profile) - * the maven-release-plugin does not work very well with the current release strategy of Apache Commons (Tag after vote). It might be easier to not use it + * the maven-release-plugin does not work very well with the current release strategy of Apache Commons (Tag after vote) * tag conventions in the 2.0 release have a bit messed up the repo. The 2.0 release is named (VFS-1.0 vs. commons-vfs2-project-2.0) - * vfs site is a post 2.0 snapshot with broken links (SVN version is better but not published yet) - * hdfs support is new, needs to be announced and explained (write mode VFS-570 is missing) * JIRA report does not include more than 100 fixes and changes-plugin cant page (http://jira.codehaus.org/browse/MCHANGES-351). As INFRA cant raise the limit. The report is not prominent, so we will create it incomplete. After Release - * close all 2.1 bugs (resolved->closed) + * Mark Version as released, clsoe all resolved Bugs in Version. Change Fix Version for unresolved bugs * open next snapshot * DOAP file - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
[Commons Wiki] Update of "VfsReleaseState" by BerndEckenfels
Dear Wiki user, You have subscribed to a wiki page or wiki category on "Commons Wiki" for change notification. The "VfsReleaseState" page has been changed by BerndEckenfels: https://wiki.apache.org/commons/VfsReleaseState?action=diff&rev1=19&rev2=20 = Upcoming commons-vfs2-2.1 release = + * Preview of Site: N/A - * Preview of Site: http://people.apache.org/~ecki/commons-vfs/ - * Decided: will use manual not release-plugin process - * JIRA report does not include more than 100 fixes and changes-plugin cant page (http://jira.codehaus.org/browse/MCHANGES-351). As INFRA cant raise the limit. The report is not prominent, so we will create it incomplete. This is a list of things to do for the (upcoming) next release of VFS 2.1 @@ -17, +15 @@ * the maven-release-plugin does not work very well with the current release strategy of Apache Commons (Tag after vote). It might be easier to not use it * tag conventions in the 2.0 release have a bit messed up the repo. The 2.0 release is named (VFS-1.0 vs. commons-vfs2-project-2.0) * vfs site is a post 2.0 snapshot with broken links (SVN version is better but not published yet) - * hdfs support is new, needs to be announced and explained + * hdfs support is new, needs to be announced and explained (write mode VFS-570 is missing) + * JIRA report does not include more than 100 fixes and changes-plugin cant page (http://jira.codehaus.org/browse/MCHANGES-351). As INFRA cant raise the limit. The report is not prominent, so we will create it incomplete. After Release - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
[Commons Wiki] Update of "VfsReleaseState" by BerndEckenfels
Dear Wiki user, You have subscribed to a wiki page or wiki category on "Commons Wiki" for change notification. The "VfsReleaseState" page has been changed by BerndEckenfels: https://wiki.apache.org/commons/VfsReleaseState?action=diff&rev1=18&rev2=19 Comment: added some caveats * create and commit RELEASE-NOTES.txt (Java6, hadoop - draft with all changes checked in) * step through the release process for software and site + Things to be aware of + * VFS is a multi-module project, sandbox is even optional (profile) + * the maven-release-plugin does not work very well with the current release strategy of Apache Commons (Tag after vote). It might be easier to not use it + * tag conventions in the 2.0 release have a bit messed up the repo. The 2.0 release is named (VFS-1.0 vs. commons-vfs2-project-2.0) + * vfs site is a post 2.0 snapshot with broken links (SVN version is better but not published yet) + * hdfs support is new, needs to be announced and explained After Release - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
[Commons Wiki] Update of "ContributorsGroup" by StefanBodewig
Dear Wiki user, You have subscribed to a wiki page or wiki category on "Commons Wiki" for change notification. The "ContributorsGroup" page has been changed by StefanBodewig: https://wiki.apache.org/commons/ContributorsGroup?action=diff&rev1=14&rev2=15 * ThomasNeidhart * ThomasVandahl * [[Woonsan Ko]] + * umagangumalla - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
[Commons Wiki] Update of "UsingGIT" by StefanBodewig
Dear Wiki user,
You have subscribed to a wiki page or wiki category on "Commons Wiki" for
change notification.
The "UsingGIT" page has been changed by StefanBodewig:
https://wiki.apache.org/commons/UsingGIT?action=diff&rev1=19&rev2=20
Comment:
typo
Much like for svn based you can download a git patch file by appending
".patch" to the URI of the pull request, e.g.
https://github.com/apache/commons-foo/pull/72.patch
- Inside the working copy of your commons component check out the master branch
and apply the patch using "git am", this will preserve the original infoamtion
of the original commits.
+ Inside the working copy of your commons component check out the master branch
and apply the patch using "git am", this will preserve the original information
of the original commits.
{{{
$ git checkout master
-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org
[Commons Wiki] Update of "UsingGIT" by StefanBodewig
Dear Wiki user,
You have subscribed to a wiki page or wiki category on "Commons Wiki" for
change notification.
The "UsingGIT" page has been changed by StefanBodewig:
https://wiki.apache.org/commons/UsingGIT?action=diff&rev1=18&rev2=19
If you've done it right, the PR will be marked as merged at !GitHub. Remember
that this will only work if the original commits of the contributor show up in
the history of the component's repository.
+ == Applying Pull Requests (for git based components) - alternative approach ==
+
+ Much like for svn based you can download a git patch file by appending
".patch" to the URI of the pull request, e.g.
https://github.com/apache/commons-foo/pull/72.patch
+
+ Inside the working copy of your commons component check out the master branch
and apply the patch using "git am", this will preserve the original infoamtion
of the original commits.
+
+ {{{
+ $ git checkout master
+ $ git pull
+ $ git am 72.patch
+ }}}
+
+ If there haven't been any merge conflicts you can simply push the result.
Otherwise you've got to resolve the conflict and commit the result of the merge
before pushing.
+
-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org
[Commons Wiki] Trivial Update of "ComponentPlans" by BerndEckenfels
Dear Wiki user, You have subscribed to a wiki page or wiki category on "Commons Wiki" for change notification. The "ComponentPlans" page has been changed by BerndEckenfels: https://wiki.apache.org/commons/ComponentPlans?action=diff&rev1=14&rev2=15 Comment: updated vfs plan * resources * transaction * validator - see http://wiki.apache.org/jakarta-commons/Validator14ProjectPlan - * vfs - release 1.0 + * vfs - see VfsReleaseState - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
[Commons Wiki] Update of "VfsReleaseState" by BerndEckenfels
Dear Wiki user, You have subscribed to a wiki page or wiki category on "Commons Wiki" for change notification. The "VfsReleaseState" page has been changed by BerndEckenfels: https://wiki.apache.org/commons/VfsReleaseState?action=diff&rev1=17&rev2=18 Comment: release notes updated This is a list of things to do for the (upcoming) next release of VFS 2.1 - * only show aggregate checkstyle report toplevel * explain/resolve clirr incompatibilities - * create and commit RELEASE-NOTES.txt (Java6, hadoop) + * create and commit RELEASE-NOTES.txt (Java6, hadoop - draft with all changes checked in) * step through the release process for software and site - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
[Commons Wiki] Update of "VfsReleaseState" by BerndEckenfels
Dear Wiki user, You have subscribed to a wiki page or wiki category on "Commons Wiki" for change notification. The "VfsReleaseState" page has been changed by BerndEckenfels: https://wiki.apache.org/commons/VfsReleaseState?action=diff&rev1=16&rev2=17 Comment: new parent works for java 8 * only show aggregate checkstyle report toplevel * explain/resolve clirr incompatibilities * create and commit RELEASE-NOTES.txt (Java6, hadoop) - * fix Java 8 build problems - waits for commons-parent:39 * step through the release process for software and site - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
[Commons Wiki] Update of "VfsReleaseState" by BerndEckenfels
Dear Wiki user, You have subscribed to a wiki page or wiki category on "Commons Wiki" for change notification. The "VfsReleaseState" page has been changed by BerndEckenfels: https://wiki.apache.org/commons/VfsReleaseState?action=diff&rev1=15&rev2=16 Comment: java 8 builds will work * only show aggregate checkstyle report toplevel * explain/resolve clirr incompatibilities * create and commit RELEASE-NOTES.txt (Java6, hadoop) - * (fix Java 8 build problems) + * fix Java 8 build problems - waits for commons-parent:39 * step through the release process for software and site - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
[Commons Wiki] Update of "FrontPage" by sebbapache
Dear Wiki user, You have subscribed to a wiki page or wiki category on "Commons Wiki" for change notification. The "FrontPage" page has been changed by sebbapache: https://wiki.apache.org/commons/FrontPage?action=diff&rev1=135&rev2=136 Comment: += UseClirrWithShade Welcome: CommonsEtiquette | CommonsResources | ArticlesAndTutorials - Developers: GettingInvolved | [[UsingSVN]] | [[UsingGIT]] | CodeStyle | [[MovingToGit]] + Developers: GettingInvolved | [[UsingSVN]] | [[UsingGIT]] | CodeStyle | [[MovingToGit]] | [[UseClirrWithShade]] Committers: CommonsPeople | ComponentPlans | CommonsCommitters | CommonsOsgi | UsingNexus | CommonsGroupids | Maven3Plan - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
[Commons Wiki] Update of "UseClirrWithShade" by sebbapache
Dear Wiki user, You have subscribed to a wiki page or wiki category on "Commons Wiki" for change notification. The "UseClirrWithShade" page has been changed by sebbapache: https://wiki.apache.org/commons/UseClirrWithShade?action=diff&rev1=1&rev2=2 Comment: We don't need the extra POM shade - true + false - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
[Commons Wiki] Update of "UseClirrWithShade" by sebbapache
Dear Wiki user,
You have subscribed to a wiki page or wiki category on "Commons Wiki" for
change notification.
The "UseClirrWithShade" page has been changed by sebbapache:
https://wiki.apache.org/commons/UseClirrWithShade
Comment:
How to use Shade with Clirr
New page:
This page describes how one can use Clirr with Shade to compare components that
have changed packages.
Clirr compares different versions of classes with the same package name
Shade can be used to change package names throughout a jar file
By combining the two, it is possible to use Clirr to check classes that are now
in a new package.
The process is:
* use Shade to convert the old package names to the new package names
* install the shaded jar in the local repository
* run Clirr against the shaded jar
Here is a sample POM (shade.xml) for comparing org.apache.bcel:bcel:5.2 against
org.apache.commons:commons-bcel6:6.0
{{{
http://maven.apache.org/POM/4.0.0";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
http://maven.apache.org/maven-v4_0_0.xsd";>
4.0.0
org.apache
apache
17
org.apache.commons
commons-bcel6
jar
5.2-SHADED
Commons BCEL shader
This POM can be used to install a shaded version of BCEL 5.2
in the local repo. Usage:
mvn -f shade.xml install
You can then run Clirr using the default POM:
mvn clirr:clirr
http://maven.apache.org
true
true
true
true
org.apache.bcel
bcel
5.2
jakarta-regexp
jakarta-regexp
package
org.apache.maven.plugins
maven-shade-plugin
2.4.1
package
shade
true
org.apache.bcel
org.apache.commons.bcel6
}}}
-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org
[Commons Wiki] Update of "VfsReleaseState" by BerndEckenfels
Dear Wiki user, You have subscribed to a wiki page or wiki category on "Commons Wiki" for change notification. The "VfsReleaseState" page has been changed by BerndEckenfels: https://wiki.apache.org/commons/VfsReleaseState?action=diff&rev1=14&rev2=15 Comment: hdfs is no optional This is a list of things to do for the (upcoming) next release of VFS 2.1 - * OSGI imports are not optional (https://issues.apache.org/jira/browse/VFS-498) - use and test commons-parent release * only show aggregate checkstyle report toplevel * explain/resolve clirr incompatibilities * create and commit RELEASE-NOTES.txt (Java6, hadoop) - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
[Commons Wiki] Update of "MovingToGit" by BenediktRitter
Dear Wiki user,
You have subscribed to a wiki page or wiki category on "Commons Wiki" for
change notification.
The "MovingToGit" page has been changed by BenediktRitter:
https://wiki.apache.org/commons/MovingToGit?action=diff&rev1=3&rev2=4
Comment:
Document how to remove a component from svn:externals
Once the Git repo is up and running:
- 0) Edit the projects data file (as below) and replace the location reference
if necessary:
+ 1) Edit the projects data file (as below) and replace the location reference
if necessary:
https://svn.apache.org/repos/asf/infrastructure/site-tools/trunk/projects/files.xml
+ 2) Remove the project from the svn:externals property of the trunks-proper
directory:
+
+ {{{
+ svn pe svn:externals https://svn.apache.org/repos/asf/commons/trunks-proper
+ }}}
+
- 1) Add a README file to the top level of the SVN tree for the component, e.g.
math
+ 3) Add a README file to the top level of the SVN tree for the component, e.g.
math
For example:
https://svn.apache.org/repos/asf/commons/proper/math/MathNowUsesGit.txt
- 2) Move the rest of the contents (branches,tags,trunk, etc) to
+ 4) Move the rest of the contents (branches,tags,trunk, etc) to
https://svn.apache.org/repos/asf/commons/_moved_to_git/math
-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org
[Commons Wiki] Update of "MovingToGit" by sebbapache
Dear Wiki user, You have subscribed to a wiki page or wiki category on "Commons Wiki" for change notification. The "MovingToGit" page has been changed by sebbapache: https://wiki.apache.org/commons/MovingToGit?action=diff&rev1=2&rev2=3 Comment: files.xml Therefore it was decided on the following process: Once the Git repo is up and running: + + 0) Edit the projects data file (as below) and replace the location reference if necessary: + + https://svn.apache.org/repos/asf/infrastructure/site-tools/trunk/projects/files.xml 1) Add a README file to the top level of the SVN tree for the component, e.g. math - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
[Commons Wiki] Update of "MovingToGit" by sebbapache
Dear Wiki user,
You have subscribed to a wiki page or wiki category on "Commons Wiki" for
change notification.
The "MovingToGit" page has been changed by sebbapache:
https://wiki.apache.org/commons/MovingToGit?action=diff&rev1=1&rev2=2
Comment:
Worked example SCXML
Replace {{{availid}}} with the ASF login id of the person doing the move, and
{{{xyz}}} with the name of the component.
+ == Sample SVN commands (using SCXML as an example) ==
+
+ {{{
+
+ # N.B. make sure you do this first!
+ svn mkdir -m"SCXML => Git"
https://svn.eu.apache.org/repos/asf/commons/_moved_to_git/scxml
+
+
+ svn mv -m"Now using Git" \
+ https://svn.apache.org/repos/asf/commons/proper/scxml/branches \
+ https://svn.apache.org/repos/asf/commons/_moved_to_git/scxml/
+
+ # Don't omit the trailing / after the target
+ # If it is omitted, and the target does not exist, then the source directory
may be renamed
+
+ svn mv -m"Now using Git" \
+ https://svn.apache.org/repos/asf/commons/proper/scxml/tags \
+ https://svn.apache.org/repos/asf/commons/_moved_to_git/scxml/
+
+ svn mv -m"Now using Git" \
+ https://svn.apache.org/repos/asf/commons/proper/scxml/trunk \
+ https://svn.apache.org/repos/asf/commons/_moved_to_git/scxml/
+
+ # Check source tree
+ svn ls https://svn.apache.org/repos/asf/commons/proper/scxml/
+
+ # If there are any files/folders (apart from ScxmlMovedToGit.txt) then these
also need
+ # to be moved as above.
+
+ # Check target tree:
+ svn ls https://svn.apache.org/repos/asf/commons/_moved_to_git/scxml/
+
+ }}}
+
Once the process is completed, the {{{asf-authorization-template}}} should be
updated to remove the temporary entries
-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org
[Commons Wiki] Update of "Commons_Logging_FUD" by sebbapache
Dear Wiki user, You have subscribed to a wiki page or wiki category on "Commons Wiki" for change notification. The "Commons_Logging_FUD" page has been changed by sebbapache: https://wiki.apache.org/commons/Commons_Logging_FUD?action=diff&rev1=4&rev2=5 Comment: Note that Tomcat has moved on Class loader problems are commons-logging's fault? Hardly. It is the mixture of a popular project, some unfortunate class loader decisions and the rants of people who might not understand all the implications of the web container class loaders. + + Note: the following applies to Tomcat 5.5; later versions of Tomcat store the jar in the same place but change the package name so it is only used by Tomcat itself. + See [[http://tomcat.apache.org/tomcat-6.0-doc/class-loader-howto.html#Class_Loader_Definitions|Tomcat 6 class loader reference]]. + However the problems caused by the Tomcat 5.5 implementation continue to affect the perception of Commons Logging. If you look at the [[http://tomcat.apache.org/tomcat-5.5-doc/class-loader-howto.html|Tomcat 5.5 class loader reference]], you will notice that commons-logging-api.jar was put into the bin/ directory and is available through the System classloader. That was the unfortunate decision. @@ -43, +47 @@ The purpose of Commons Logging is ''not'' to isolate your code from changes in the underlying logging framework. (That's certainly easy enough to do on your own, and not really worth doing in the first place given the ease of switching from one logging framework to another.) The purpose of Commons Logging is ''not'' to somehow be more useful than actual logging frameworks by being more general. The purpose of Commons Logging is ''not'' to somehow take the logging world by storm. In fact, there are very limited circumstances in which Commons Logging is useful. If you're building a stand-alone application, don't use commons-logging. If you're building an application server, don't use commons-logging. If you're building a moderately large framework, don't use commons-logging. If however, like the Jakarta Commons project, you're building a tiny little component that you intend for other developers to embed in their applications and frameworks, and you believe that logging information might be useful to those clients, and you can't be sure what logging framework they're going to want to use, then commons-logging might be useful to you. - - - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
[Commons Wiki] Update of "VfsReleaseState" by BerndEckenfels
Dear Wiki user, You have subscribed to a wiki page or wiki category on "Commons Wiki" for change notification. The "VfsReleaseState" page has been changed by BerndEckenfels: https://wiki.apache.org/commons/VfsReleaseState?action=diff&rev1=13&rev2=14 * only show aggregate checkstyle report toplevel * explain/resolve clirr incompatibilities * create and commit RELEASE-NOTES.txt (Java6, hadoop) + * (fix Java 8 build problems) * step through the release process for software and site - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
[Commons Wiki] Update of "VfsReleaseState" by BerndEckenfels
Dear Wiki user, You have subscribed to a wiki page or wiki category on "Commons Wiki" for change notification. The "VfsReleaseState" page has been changed by BerndEckenfels: https://wiki.apache.org/commons/VfsReleaseState?action=diff&rev1=12&rev2=13 * OSGI imports are not optional (https://issues.apache.org/jira/browse/VFS-498) - use and test commons-parent release * only show aggregate checkstyle report toplevel - + * explain/resolve clirr incompatibilities - * create and commit RELEASE-NOTES.txt (Java6, interface changes in clirr report) + * create and commit RELEASE-NOTES.txt (Java6, hadoop) + * step through the release process for software and site After Release - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
[Commons Wiki] Update of "FrontPage" by sebbapache
Dear Wiki user, You have subscribed to a wiki page or wiki category on "Commons Wiki" for change notification. The "FrontPage" page has been changed by sebbapache: https://wiki.apache.org/commons/FrontPage?action=diff&rev1=134&rev2=135 Comment: Add link to Git move page Welcome: CommonsEtiquette | CommonsResources | ArticlesAndTutorials - Developers: GettingInvolved | [[UsingSVN]] | [[UsingGIT]] | CodeStyle + Developers: GettingInvolved | [[UsingSVN]] | [[UsingGIT]] | CodeStyle | [[MovingToGit]] Committers: CommonsPeople | ComponentPlans | CommonsCommitters | CommonsOsgi | UsingNexus | CommonsGroupids | Maven3Plan - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
[Commons Wiki] Update of "MovingToGit" by sebbapache
Dear Wiki user,
You have subscribed to a wiki page or wiki category on "Commons Wiki" for
change notification.
The "MovingToGit" page has been changed by sebbapache:
https://wiki.apache.org/commons/MovingToGit
Comment:
Notes on moving to Git
New page:
= Moving to Git =
Notes on things to look out for if a component moves from SVN to Git.
* This is a work in progress *
== Update pom and website ==
Ensure that the SCM references in the POM and on the website are updated as
soon as possible after the Git repo goes live.
== Update CI builds ==
There are various CI builds: Jenkins, Continuum, Buildbot. These will need to
be updated after the Git repo goes live
== Tidy up SVN repository Tree ==
As part of moving a component to Git, Infra will make the current SVN tree
read-only.
However the files will still remain. This can cause confusion; it is easy to
find the SVN files and think they are still current.
Therefore it was decided on the following process:
Once the Git repo is up and running:
1) Add a README file to the top level of the SVN tree for the component, e.g.
math
For example:
https://svn.apache.org/repos/asf/commons/proper/math/MathNowUsesGit.txt
2) Move the rest of the contents (branches,tags,trunk, etc) to
https://svn.apache.org/repos/asf/commons/_moved_to_git/math
The _moved_to_git tree is read-only except as needed to move stuff into it.
In order to do this, the person doing it needs to have write access to the
component tree and _moved_to_git.
This is controlled by the
[[https://svn.apache.org/repos/infra/infrastructure/trunk/subversion/authorization/asf-authorization-template|asf-authorization-template]]
file. The entries need to look something like:
{{{
[/commons/_moved_to_git]
* = r
# Temporary override to allow xyz to be moved from proper
availid = rw
# Now using git
[/commons/proper/xyz]
* = r
# Temporary override to allow xyz to be moved to _moved_to_git
availid = rw
}}}
Replace {{{availid}}} with the ASF login id of the person doing the move, and
{{{xyz}}} with the name of the component.
Once the process is completed, the {{{asf-authorization-template}}} should be
updated to remove the temporary entries
-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org
[Commons Wiki] Trivial Update of "FrontPage" by sebbapache
Dear Wiki user, You have subscribed to a wiki page or wiki category on "Commons Wiki" for change notification. The "FrontPage" page has been changed by sebbapache: https://wiki.apache.org/commons/FrontPage?action=diff&rev1=133&rev2=134 Comment: Restore original list formatting = Components = On this wiki: - * - BeanUtils - Utilities for manipulating java beans, including copying properties, cloning, invoking methods and type conversion. + * BeanUtils - Utilities for manipulating java beans, including copying properties, cloning, invoking methods and type conversion. - * - [[Betwixt]] - Services for mapping !JavaBeans to XML documents, and vice versa. + * [[Betwixt]] - Services for mapping !JavaBeans to XML documents, and vice versa. - * - [[Chain]] - A "Chain of Responsibility" pattern implemention for organizing complex processing flows. + * [[Chain]] - A "Chain of Responsibility" pattern implemention for organizing complex processing flows. - * - [[CLI]] - Command Line Interface library for processing command-line options and arguments. + * [[CLI]] - Command Line Interface library for processing command-line options and arguments. - * - [[Codec]] - General encoding/decoding algorithms. Includes some phonetic encoders, Hex, Base64, and a URL encoder. + * [[Codec]] - General encoding/decoding algorithms. Includes some phonetic encoders, Hex, Base64, and a URL encoder. - * - [[Collections]] - Builds upon the Java Collections Framework of List, Set and Map to provide many more implementations, new collections and abstract base classes. + * [[Collections]] - Builds upon the Java Collections Framework of List, Set and Map to provide many more implementations, new collections and abstract base classes. - * - [[Configuration]] - Tools to assist in the reading of configuration/preferences files in various formats + * [[Configuration]] - Tools to assist in the reading of configuration/preferences files in various formats - * - [[Compress]] - Defines an API for working with archives and compression formats including but not limited to: tar,gz, ar, cpio, zip and bzip2 files + * [[Compress]] - Defines an API for working with archives and compression formats including but not limited to: tar,gz, ar, cpio, zip and bzip2 files - * - [[Daemon]] - Run (java) applications as windows service or UNIX daemon. + * [[Daemon]] - Run (java) applications as windows service or UNIX daemon. - * - [[DBCP]] - Database connection pooling services. + * [[DBCP]] - Database connection pooling services. - * - [[Digester]] - An XML-to-Java-object mapping utility commonly used for parsing XML configuration files. + * [[Digester]] - An XML-to-Java-object mapping utility commonly used for parsing XML configuration files. - * - [[Email]] - Simplify email sending with Java. Built on top of the Java Mail API. + * [[Email]] - Simplify email sending with Java. Built on top of the Java Mail API. - * - [[Exec]] - A Java library to execute external processes from within a Java application + * [[Exec]] - A Java library to execute external processes from within a Java application - * - FileUpload - Makes it easy to add robust, high-performance, file upload capability to your servlets and web applications + * FileUpload - Makes it easy to add robust, high-performance, file upload capability to your servlets and web applications - * - [[Functor]] - Supports functional programming in Java + * [[Functor]] - Supports functional programming in Java - * - [[http://wiki.apache.org/HttpComponents/FrontPage|HttpClient]] - A framework for working with the client-side of the HTTP protocol. + * [[http://wiki.apache.org/HttpComponents/FrontPage|HttpClient]] - A framework for working with the client-side of the HTTP protocol. - * - [[IO]] - Utility classes, stream implementations, file filters and endian classes to assist in input/output operations. + * [[IO]] - Utility classes, stream implementations, file filters and endian classes to assist in input/output operations. - * - [[JCI]] - Java Compiler Interface + * [[JCI]] - Java Compiler Interface - * - [[JEXL]] - A velocity-esque expression interpreter + * [[JEXL]] - A velocity-esque expression interpreter - * - [[Jelly]] - An XML-based scripting language + * [[Jelly]] - An XML-based scripting language - * - [[JXPath]] - Facilities for applying xpath expressions to graphs of objects of all kinds: Java beans, Maps, Servlet contexts, DOM etc. + * [[JXPath]] - Facilities for applying xpath expressions to graphs of objects of all kinds: Java beans, Maps, Servlet contexts, DOM etc. - * - [[Lang]] - Common utilities that should be provided by the JDK, including String handling, Object and Date helpers, nested exceptions and enumerated types. + * [[Lang]] - Common utilities that should be provided by the JDK, including String handling, Object an
[Commons Wiki] Update of "FrontPage" by sebbapache
Dear Wiki user,
You have subscribed to a wiki page or wiki category on "Commons Wiki" for
change notification.
The "FrontPage" page has been changed by sebbapache:
https://wiki.apache.org/commons/FrontPage?action=diff&rev1=132&rev2=133
Comment:
Commons also uses Git
|| {{http://commons.apache.org/images/logo.png}} ||This is the
[[ApacheGeneral:FrontPage|Apache Wiki]] for the
[[http://commons.apache.org/|Apache Commons]] project and is maintained by the
[[commons:FrontPage|Commons]] community. To edit pages, visit
[[UserPreferences|login]] near the top right corner of any page to create a
user profile or to login. Then send a brief request '''(including your wiki
username)''' to the [[http://commons.apache.org/mail-lists.html|Commons dev@
list]] asking to be added to the [[ContributorsGroup|Contributors Group]]. You
can then edit the pages in this Wiki. Notifications of all changes you make
will be sent to the dev@commons mailing list, so we will be aware of your
changes and we will happily correct any small mistakes that you might make. ||
- We're a [[http://wiki.apache.org/commons/FrontPage|Commons]] community,
dedicated to creating reusable library components in Java. Apache Commons is
now using [[http://subversion.tigris.org/|Subversion]] as the version control
system.
+ We're a [[http://wiki.apache.org/commons/FrontPage|Commons]] community,
dedicated to creating reusable library components in Java.
+ Apache Commons mainly uses [[http://subversion.tigris.org/|Subversion]] as
its version control system, however some components now use
[[https://git-scm.com/|Git]],
+ and Commons components are available as read-only mirrors on
[[https://github.com/apache?query=commons|Github]].
Welcome: CommonsEtiquette | CommonsResources | ArticlesAndTutorials
-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org
[Commons Wiki] Update of "UsingGIT" by BenediktRitter
Dear Wiki user, You have subscribed to a wiki page or wiki category on "Commons Wiki" for change notification. The "UsingGIT" page has been changed by BenediktRitter: https://wiki.apache.org/commons/UsingGIT?action=diff&rev1=17&rev2=18 Comment: Add pointer to GitHub plain text views for pull requests == Applying Pull Requests (for svn based components) == + If you accept a pull request, you have to apply it as a patch to the Apache WIP repository, this commit will then be propagated to the !GitHub mirror. !GitHub provides a nice API for retrieving diffs for pull requests: just add ".diff" or ".patch" to the PR URL and you will get the diff/patch, for example https://github.com/apache/commons-foo/pull/72.diff. - If you accept a pull request, you have to apply it as a patch to the Apache WIP repository, this commit will then be propagated to the !GitHub mirror. In the comment of the commit/merge you should use !GitHub syntax (closes #xx) to close the PR. There is no other way to close pull requests. So to reduce the INFRA teams workload (to work on your tickets with close requests) remember this procedure. + In the comment of the commit/merge you should use !GitHub syntax (closes #xx) to close the PR. There is no other way to close pull requests. So to reduce the INFRA teams workload (to work on your tickets with close requests) remember this procedure. == Applying Pull Requests (for git based components) == - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
[Commons Wiki] Update of "UsingGIT" by BenediktRitter
Dear Wiki user,
You have subscribed to a wiki page or wiki category on "Commons Wiki" for
change notification.
The "UsingGIT" page has been changed by BenediktRitter:
https://wiki.apache.org/commons/UsingGIT?action=diff&rev1=16&rev2=17
Comment:
Add missing push to origin step
== Applying Pull Requests (for git based components) ==
- First of all, make sure the the PR you want to merge does not contain merge
conflicts. If that is the case you can start merging the PR by fetching it into
your local clone of repository. To do this the !GitHub mirror has to be defined
as a remote in your local clone. This only has to be done once and you can
check whether you already did it with:
+ First of all, make sure the the PR you want to merge does not contain merge
conflicts. If that is not the case, it's best to ask the contributor to resolve
any merge conflicts by rebasing against the master branch. If all conflicts
have been resolved you can start merging the PR by fetching it into your local
clone of repository. To do this the !GitHub mirror has to be defined as a
remote in your local clone. This only has to be done once and you can check
whether you already did it with:
{{{
$ git remote show
@@ -183, +183 @@
This will print a list of all remotes you have defined:
{{{
- $ git remote show -n
+ $ git remote show
github
origin
}}}
@@ -235, +235 @@
}}}
The pull makes sure you have the lastest changes from the Apache repository
in your local clone. Merging with --no-ff option will create a separate merge
commit. This is why your $EDITOR will be started asking you to provide a commit
message. The first line will be "Merge branch 'fix-foo-in-bar'". You should
leave it this way so the fact that this branch has been merged can be seen in
the history. Furthermore a reference to the corrensponding Jira should be
added. For an example see
https://git-wip-us.apache.org/repos/asf?p=commons-lang.git;a=commit;h=640953167adf3580a2c21077d78e7e7ce84ead03
+ If the PR did not contain merge conflicts, only the commits you added before
merging can produce merge conflicts. This happens for example if you've added
the corresponding jira issue to changes.xml but the master branch already
contained newer entries. Resolve all conflicts, all files using {{{$ git add
.}}} and then finalize the merge with {{{$ git commit}}}. Up to this point
you've only modified your local repository. So it's time to push the changes
back to the Apache git repository:
+ {{{
+ $ git push origin master
+ }}}
+
+ If you've done it right, the PR will be marked as merged at !GitHub. Remember
that this will only work if the original commits of the contributor show up in
the history of the component's repository.
+
-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org
[Commons Wiki] Update of "UsingGIT" by BenediktRitter
Dear Wiki user,
You have subscribed to a wiki page or wiki category on "Commons Wiki" for
change notification.
The "UsingGIT" page has been changed by BenediktRitter:
https://wiki.apache.org/commons/UsingGIT?action=diff&rev1=15&rev2=16
Comment:
Document how to integrate pull requests from github
= GitHub Integration =
- GitHub is a popular commercial Git hosting service. The ASF GIT repositories
are mirrored there to increase visibility and to encourage more collaborators.
The Infra team is responsible for maintaining the
[[https://github.com/apache/|Github Apache Organisation]]. As an Apache
committer you can also get added to the Team on !GitHub, but this has no
function for access control, it is purely to show off your affiliation. Some
Apache Commons projects chose to advertise the related !GitHub project (to
accept pull requests or even problem reports). For example the ''README.md''
and ''CONTRIBUTING.md'' files produced by the ''build-plgin'' describe this
workflow. If you accept a pull request, you have to apply it as a patch to the
Apache WIP repository, this commit will then be propagated to the !GitHub
mirror. In the comment of the commit/merge you should use !GitHub syntax
(closes #xx) to close the PR. There is no other way to close pull requests. So
to reduce the INFRA teams workload (to work on your tickets with close
requests) remember this procedure.
+ !GitHub is a popular commercial Git hosting service. The ASF GIT repositories
are mirrored there to increase visibility and to encourage more collaborators.
The Infra team is responsible for maintaining the
[[https://github.com/apache/|Github Apache Organisation]]. As an Apache
committer you can also get added to the Team on !GitHub, but this has no
function for access control, it is purely to show off your affiliation. Some
Apache Commons projects chose to advertise the related !GitHub project (to
accept pull requests or even problem reports). For example the ''README.md''
and ''CONTRIBUTING.md'' files produced by the ''build-plugin'' describe this
workflow.
+ Since the !GitHub mirrors are read only, the Web UI cannot be used for
merging PR. This has to be done manually using the command line. The procedure
differs depending on whether the component you want to apply the PR to uses SVN
or git.
+
+ == Applying Pull Requests (for svn based components) ==
+
+ If you accept a pull request, you have to apply it as a patch to the Apache
WIP repository, this commit will then be propagated to the !GitHub mirror. In
the comment of the commit/merge you should use !GitHub syntax (closes #xx) to
close the PR. There is no other way to close pull requests. So to reduce the
INFRA teams workload (to work on your tickets with close requests) remember
this procedure.
+
+ == Applying Pull Requests (for git based components) ==
+
+ First of all, make sure the the PR you want to merge does not contain merge
conflicts. If that is the case you can start merging the PR by fetching it into
your local clone of repository. To do this the !GitHub mirror has to be defined
as a remote in your local clone. This only has to be done once and you can
check whether you already did it with:
+
+ {{{
+ $ git remote show
+ }}}
+
+ This will print a list of all remotes you have defined:
+
+ {{{
+ $ git remote show -n
+ github
+ origin
+ }}}
+
+ If you don't have an entry for the github mirror yet, you can add one with:
+
+ {{{
+ $ git remote add github g...@github.com:apache/commons-foo.git
+ }}}
+
+ After that {{{$ git remote show}}} should list the new remote. You can check
the configuration with
+
+ {{{
+ $ git remote show github
+ }}}
+
+ which should print something like:
+
+ {{{
+ $ git remote show github
+ * remote github
+ Fetch URL: g...@github.com:apache/commons-lang.git
+ Push URL: g...@github.com:apache/commons-lang.git
+ HEAD branch: master
+ Remote branches:
+ LANG_1_0_BRANCH new (next fetch will store in remotes/github)
+ LANG_2_2_X new (next fetch will store in remotes/github)
+ LANG_2_Xnew (next fetch will store in remotes/github)
+ LANG_4_Xnew (next fetch will store in remotes/github)
+ LANG_POST_2_4 new (next fetch will store in remotes/github)
+ LangTwo-1.x new (next fetch will store in remotes/github)
+ master new (next fetch will store in remotes/github)
+ Local ref configured for 'git push':
+ master pushes to master (up to date)
+ }}}
+
+ After your remote is set up, you need to fetch the branch containing the PR
changes. !GitHub provides readonly branches for all PR. They follow the name
schema: pull/ID/head:branch-name. So if you want to merge PR #72 and the branch
which was initially created by the contributor is called fix-foo-in-bar, then
you need to fetch:
+
+ {{{
+ $ git fetch github pull/72/head:fix-foo-in-bar
+ }}}
+
+ After this you can checkout the PR branch locally using {{{$ git checkout
fix
[Commons Wiki] Update of "UsingGIT" by BerndEckenfels
Dear Wiki user, You have subscribed to a wiki page or wiki category on "Commons Wiki" for change notification. The "UsingGIT" page has been changed by BerndEckenfels: https://wiki.apache.org/commons/UsingGIT?action=diff&rev1=14&rev2=15 = GitHub Integration = - GitHub is a popular commercial Git hosting service. The ASF GIT repositories are mirrored there to increase visibility and to encourage more collaborators. The Infra team is responsible for maintaining the [[https://github.com/apache/|Github Apache Organisation]]. As an Apache committer you can also get added to the Team on GitHub, but this has no function for access control, it is purely to show off your affiliation. Some Apache Commons projects chose to advertise the related GitHub project (to accept pull requests or even problem reports). For example the ''README.md'' and ''CONTRIBUTING.md'' files produced by the ''build-plgin'' describe this workflow. If you accept a pull request, you have to apply it as a patch to the Apache WIP repository, this commit will then be propagated to the GitHub mirror. In the comment of the commit/merge you should use GitHub syntax (closes #xx) to close the PR. There is no other way to close pull requests, so to avoid opening a ticket to the Infra team remember this procedure. + GitHub is a popular commercial Git hosting service. The ASF GIT repositories are mirrored there to increase visibility and to encourage more collaborators. The Infra team is responsible for maintaining the [[https://github.com/apache/|Github Apache Organisation]]. As an Apache committer you can also get added to the Team on !GitHub, but this has no function for access control, it is purely to show off your affiliation. Some Apache Commons projects chose to advertise the related !GitHub project (to accept pull requests or even problem reports). For example the ''README.md'' and ''CONTRIBUTING.md'' files produced by the ''build-plgin'' describe this workflow. If you accept a pull request, you have to apply it as a patch to the Apache WIP repository, this commit will then be propagated to the !GitHub mirror. In the comment of the commit/merge you should use !GitHub syntax (closes #xx) to close the PR. There is no other way to close pull requests. So to reduce the INFRA teams workload (to work on your tickets with close requests) remember this procedure. - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
[Commons Wiki] Update of "UsingGIT" by BerndEckenfels
Dear Wiki user, You have subscribed to a wiki page or wiki category on "Commons Wiki" for change notification. The "UsingGIT" page has been changed by BerndEckenfels: https://wiki.apache.org/commons/UsingGIT?action=diff&rev1=13&rev2=14 * `svn help `''sub-command'' `git` ''sub-command'' `--help` - = GitHub Integration= + = GitHub Integration = - GitHub is a popular commercial Git hosting service. The ASF GIT repositories are mirrored there to increase visibility and to encourage more collaborators. The Infra team is responsible for maintaining the [[https://github.com/apache/|Github Apache Organisation]]. As an Apache comitter you can also get added to the Team on Github, but this has no function for access control, it is purely to show off your affiliation. Some Apache Commons projects chose to advertise the related Github project (to accept pull requests or even problem reports). For example the ''README.md'' and ''CONTRIBUTING.md'' files produced by the ''build-plgin'' describe this workflow. If you accept a pull request, you have to apply it as a patch to the Apache WIP repository, this commit will then be propagated to the Github mirror. In the comment of the commit/merge you should use Github syntax (closes #xx) to close the PR. There is no other way to close pull requests, so to avoid opening a ticket to the Infra team remeber this procedure. + GitHub is a popular commercial Git hosting service. The ASF GIT repositories are mirrored there to increase visibility and to encourage more collaborators. The Infra team is responsible for maintaining the [[https://github.com/apache/|Github Apache Organisation]]. As an Apache committer you can also get added to the Team on GitHub, but this has no function for access control, it is purely to show off your affiliation. Some Apache Commons projects chose to advertise the related GitHub project (to accept pull requests or even problem reports). For example the ''README.md'' and ''CONTRIBUTING.md'' files produced by the ''build-plgin'' describe this workflow. If you accept a pull request, you have to apply it as a patch to the Apache WIP repository, this commit will then be propagated to the GitHub mirror. In the comment of the commit/merge you should use GitHub syntax (closes #xx) to close the PR. There is no other way to close pull requests, so to avoid opening a ticket to the Infra team remember this procedure. + - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
[Commons Wiki] Update of "UsingGIT" by BerndEckenfels
Dear Wiki user, You have subscribed to a wiki page or wiki category on "Commons Wiki" for change notification. The "UsingGIT" page has been changed by BerndEckenfels: https://wiki.apache.org/commons/UsingGIT?action=diff&rev1=12&rev2=13 * `svn help `''sub-command'' `git` ''sub-command'' `--help` - =Githib Integration= + = GitHub Integration= - GitHub is a popular commercial Git hosting service. The ASF repositories are mirrored there to increase visibility and to encourage more collaborators. The Infra team is responsible for maintaining the [[https://github.com/apache/|Github Apache Organisation]]. As an Apache comitter you can also get added to the Team on Github, but this has no function for access control, it is purely to show off your affiliation. Some Apache Commons projects chose to advertise the related Github project (to accept pull requests or even problem reports). For example the ''README.md'' and ''CONTRIBUTING.md'' files produced by the ''build-plgin'' describe this workflow. If you accept a pull request, you have to apply it as a patch to the Apache WIP repository, this commit will then be propagated to the Github mirror. In the comment of the commit/merge you should use Github syntax (closes #xx) to close the PR. There is no other way to close pull requests, so to avoid opening a ticket to the Infra team remeber this procedure. + GitHub is a popular commercial Git hosting service. The ASF GIT repositories are mirrored there to increase visibility and to encourage more collaborators. The Infra team is responsible for maintaining the [[https://github.com/apache/|Github Apache Organisation]]. As an Apache comitter you can also get added to the Team on Github, but this has no function for access control, it is purely to show off your affiliation. Some Apache Commons projects chose to advertise the related Github project (to accept pull requests or even problem reports). For example the ''README.md'' and ''CONTRIBUTING.md'' files produced by the ''build-plgin'' describe this workflow. If you accept a pull request, you have to apply it as a patch to the Apache WIP repository, this commit will then be propagated to the Github mirror. In the comment of the commit/merge you should use Github syntax (closes #xx) to close the PR. There is no other way to close pull requests, so to avoid opening a ticket to the Infra team remeber this procedure. - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
[Commons Wiki] Update of "UsingGIT" by BerndEckenfels
Dear Wiki user, You have subscribed to a wiki page or wiki category on "Commons Wiki" for change notification. The "UsingGIT" page has been changed by BerndEckenfels: https://wiki.apache.org/commons/UsingGIT?action=diff&rev1=11&rev2=12 Comment: added Github info * `svn help `''sub-command'' `git` ''sub-command'' `--help` + =Githib Integration= + GitHub is a popular commercial Git hosting service. The ASF repositories are mirrored there to increase visibility and to encourage more collaborators. The Infra team is responsible for maintaining the [[https://github.com/apache/|Github Apache Organisation]]. As an Apache comitter you can also get added to the Team on Github, but this has no function for access control, it is purely to show off your affiliation. Some Apache Commons projects chose to advertise the related Github project (to accept pull requests or even problem reports). For example the ''README.md'' and ''CONTRIBUTING.md'' files produced by the ''build-plgin'' describe this workflow. If you accept a pull request, you have to apply it as a patch to the Apache WIP repository, this commit will then be propagated to the Github mirror. In the comment of the commit/merge you should use Github syntax (closes #xx) to close the PR. There is no other way to close pull requests, so to avoid opening a ticket to the Infra team remeber this procedure. + - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
[Commons Wiki] Update of "VFS" by BerndEckenfels
Dear Wiki user, You have subscribed to a wiki page or wiki category on "Commons Wiki" for change notification. The "VFS" page has been changed by BerndEckenfels: https://wiki.apache.org/commons/VFS?action=diff&rev1=21&rev2=22 Comment: added vfs-azure * [[http://www.leisenfels.com/products/vfslib|VFSLib Java Library]] - Commons VFS providers for Dropbox, Google Drive, and Amazon S3 cloud file systems first published in 2013. - * [[https://github.com/ecki/seeburger-vfs2|seeburger-vfs2]] - VFS providers for database blobs and layered git-trees + * [[https://github.com/ecki/seeburger-vfs2|seeburger-vfs2]] - VFS providers for database blobs and layered git-trees. + + * [[https://github.com/kervinpierre/vfs-azure|vfs-azure]] - VFS provider for Microsoft Azure Blob Storage by Kervin Pierre. - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
[Commons Wiki] Update of "VFS" by BerndEckenfels
Dear Wiki user, You have subscribed to a wiki page or wiki category on "Commons Wiki" for change notification. The "VFS" page has been changed by BerndEckenfels: https://wiki.apache.org/commons/VFS?action=diff&rev1=20&rev2=21 == Usage and Solutions == - * '''VfsExampleShell''' + * '''VfsExampleShell''' - command line (classpath) samples * '''VfsCacheStrategy''' + * '''VfsFaq''' - lets start a FAQ - - == FAQ == - Lets start creating a FAQ: + * '''VfsCapabilitiesMatrix''' - Capabilities of file system providers - * '''VfsFaq''' - - * '''VfsCapabilitiesMatrix''' - == Future == + == Future and Contributions == Stuff we will see in (one of) the next release(s): * '''VfsNext''' - ideas, todos, open issues (needs cleanup) * '''VfsReleaseState''' - roadmap for next release + + * '''VfsTestServers''' - how to integration test with external servers == Articles == - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
[Commons Wiki] Update of "VfsReleaseState" by BerndEckenfels
Dear Wiki user, You have subscribed to a wiki page or wiki category on "Commons Wiki" for change notification. The "VfsReleaseState" page has been changed by BerndEckenfels: https://wiki.apache.org/commons/VfsReleaseState?action=diff&rev1=11&rev2=12 Comment: test documentation is up to date, osgi fix is available. * Preview of Site: http://people.apache.org/~ecki/commons-vfs/ * Decided: will use manual not release-plugin process - * JIRA report does not include more than 100 fixes and changes-plugin cant page (http://jira.codehaus.org/browse/MCHANGES-351). As INFRA cant raise the limit, I plan to not create a JIRA report for the release (as all of them are in the chnages.xml anyway). + * JIRA report does not include more than 100 fixes and changes-plugin cant page (http://jira.codehaus.org/browse/MCHANGES-351). As INFRA cant raise the limit. The report is not prominent, so we will create it incomplete. This is a list of things to do for the (upcoming) next release of VFS 2.1 - * update testing/test-server site: some protocols are tested now, hdfs with windows profile - * OSGI imports are not optional (https://issues.apache.org/jira/browse/VFS-498) - pending commons-parent release + * OSGI imports are not optional (https://issues.apache.org/jira/browse/VFS-498) - use and test commons-parent release * only show aggregate checkstyle report toplevel + * create and commit RELEASE-NOTES.txt (Java6, interface changes in clirr report) - * announce Java 1.6 in release-notes - * create and commit RELEASE-NOTES.txt After Release - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
[Commons Wiki] Update of "VfsTestServers" by BerndEckenfels
Dear Wiki user,
You have subscribed to a wiki page or wiki category on "Commons Wiki" for
change notification.
The "VfsTestServers" page has been changed by BerndEckenfels:
https://wiki.apache.org/commons/VfsTestServers
Comment:
Initial Version
New page:
== VFS Testing with external Servers ==
This page collects a number of example configurations and setup instructions
for external servers. This is intended to be used with the integration tests,
as described on the
[[http://commons.apache.org/proper/commons-vfs/testing.html|Apache Commons VFS
site]].
=== Samba 3 ===
To test the (sandbox) SMB provider you can export a share with Samba 3 server
and connect to it:
Setup a 'vfsusr' login with password 'vfstest'
{{{
smbpasswd -a vfsusr
}}}
Configure a new share in Samba by adding the following lines to the
configuration:
{{{
[vfsusr]
comment = VFS Test Directory
path = /home/vfsusr
guest ok = yes
writable = yes
}}}
=== OpenSSH ===
In '''/etc/ssh/sshd_config''' ensure
{{{
PasswordAuthentication yes
}}}
Then you can crate the test directory in the home of any user (of course not
root) and use it as the base for testing.
-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org
[Commons Wiki] Update of "VfsReleaseState" by BerndEckenfels
Dear Wiki user, You have subscribed to a wiki page or wiki category on "Commons Wiki" for change notification. The "VfsReleaseState" page has been changed by BerndEckenfels: https://wiki.apache.org/commons/VfsReleaseState?action=diff&rev1=10&rev2=11 * Preview of Site: http://people.apache.org/~ecki/commons-vfs/ * Decided: will use manual not release-plugin process - + * JIRA report does not include more than 100 fixes and changes-plugin cant page (http://jira.codehaus.org/browse/MCHANGES-351). As INFRA cant raise the limit, I plan to not create a JIRA report for the release (as all of them are in the chnages.xml anyway). This is a list of things to do for the (upcoming) next release of VFS 2.1 * update testing/test-server site: some protocols are tested now, hdfs with windows profile - * JIRA report does not include more than 100 fixed, there are 141 in this release. What to do? (http://jira.codehaus.org/browse/MCHANGES-351 https://issues.apache.org/jira/browse/INFRA-9069) - * OSGI imports are not optional (https://issues.apache.org/jira/browse/VFS-498) - pending CP release + * OSGI imports are not optional (https://issues.apache.org/jira/browse/VFS-498) - pending commons-parent release * only show aggregate checkstyle report toplevel * announce Java 1.6 in release-notes - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
[Commons Wiki] Update of "VfsReleaseState" by BerndEckenfels
Dear Wiki user, You have subscribed to a wiki page or wiki category on "Commons Wiki" for change notification. The "VfsReleaseState" page has been changed by BerndEckenfels: https://wiki.apache.org/commons/VfsReleaseState?action=diff&rev1=9&rev2=10 Comment: Opened INFRA ticket This is a list of things to do for the (upcoming) next release of VFS 2.1 * update testing/test-server site: some protocols are tested now, hdfs with windows profile - * JIRA report does not include more than 100 fixed, there are 141 in this release. What to do? (http://jira.codehaus.org/browse/MCHANGES-351) + * JIRA report does not include more than 100 fixed, there are 141 in this release. What to do? (http://jira.codehaus.org/browse/MCHANGES-351 https://issues.apache.org/jira/browse/INFRA-9069) * OSGI imports are not optional (https://issues.apache.org/jira/browse/VFS-498) - pending CP release * only show aggregate checkstyle report toplevel - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
[Commons Wiki] Update of "ContributorsGroup" by StefanBodewig
Dear Wiki user, You have subscribed to a wiki page or wiki category on "Commons Wiki" for change notification. The "ContributorsGroup" page has been changed by StefanBodewig: https://wiki.apache.org/commons/ContributorsGroup?action=diff&rev1=13&rev2=14 * DennisLundberg * EmmanuelBourg * GillesSadowski + * jochen * JörgSchaible * KonstantinKolinko * KristianRosenvold - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
[Commons Wiki] Update of "VfsReleaseState" by BerndEckenfels
Dear Wiki user, You have subscribed to a wiki page or wiki category on "Commons Wiki" for change notification. The "VfsReleaseState" page has been changed by BerndEckenfels: https://wiki.apache.org/commons/VfsReleaseState?action=diff&rev1=8&rev2=9 Comment: +osgi and jira problems This is a list of things to do for the (upcoming) next release of VFS 2.1 * update testing/test-server site: some protocols are tested now, hdfs with windows profile + * JIRA report does not include more than 100 fixed, there are 141 in this release. What to do? (http://jira.codehaus.org/browse/MCHANGES-351) + * OSGI imports are not optional (https://issues.apache.org/jira/browse/VFS-498) - pending CP release * only show aggregate checkstyle report toplevel * announce Java 1.6 in release-notes - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
[Commons Wiki] Update of "VfsExampleShell" by BerndEckenfels
Dear Wiki user,
You have subscribed to a wiki page or wiki category on "Commons Wiki" for
change notification.
The "VfsExampleShell" page has been changed by BerndEckenfels:
https://wiki.apache.org/commons/VfsExampleShell?action=diff&rev1=5&rev2=6
Comment:
Thanks to Dave Marion for HDFS example and testing.
= Commons VFS Example Shell =
This page shows some examples to configure the classpath and use the VFS
Example Shell.
- All examples expect to be started from within the Apache Commons VFS source
directory (refering to build artifacts as well as external dependencies in a
local maven repository). Linux/Unix commands are marked with `$` prompt, for
sample Windows command you see a `C:vfs>` prompt.
+ All examples expect to be started from within the Apache Commons VFS source
directory (refering to build artifacts as well as external dependencies in a
local maven repository). Linux/Unix commands are marked with `$ ` prompt, for
sample Windows command you see a `C:vfs> ` prompt. Commands entered into the
VFS Example Shell are marked with the `> ` prompt.
Enabling the SMB provider from the sandbox:
@@ -77, +77 @@
Crawl-Delay: 4
}}}
+ The following example describes how to set up a file in HDFS and how to
access it with the VFS Example Shell:
+ {{{
+ $ HADOOP_HOME=/home/user/hadoop-2.6.0
+ $ HADOOP_CLASSPATH=`$HADOOP_HOME/bin/hadoop classpath`
+ $ $HADOOP_HOME/bin/hadoop fs -mkdir /vfs-test
+ $ $HADOOP_HOME/bin/hadoop fs -copyFromLocal /tmp/test.txt /vfs-test/text.txt
+ $ $HADOOP_HOME/bin/hadoop fs -ls -R /
+ drwxr-xr-x - user supergroup 0 2015-01-09 21:56 /vfs-test
+ -rw-r--r-- 3 user supergroup 15 2015-01-09 21:56 /vfs-test/text.txt
+
+ $ REP=~/.m2/repository
+ $ LIBS=$REP/commons-logging/commons-logging/1.2/commons-logging-1.2.jar
+ $
LIBS=$LIBS:core/target/commons-vfs2-2.1-SNAPSHOT.jar:examples/target/commons-vfs2-examples-2.1-SNAPSHOT.jar
+ $ java -cp $LIBS:$HADOOP_CLASSPATH org.apache.commons.vfs2.example.Shell
+ 15/01/09 22:01:44 INFO impl.StandardFileSystemManager: Using "/tmp/vfs_cache"
as temporary files store.
+ VFS Shell 2.1-SNAPSHOT
+ > info
+ Default manager: "org.apache.commons.vfs2.impl.StandardFileSystemManager"
version 2.1-SNAPSHOT
+ Provider Schemes: [https, res, gz, hdfs, sftp, ftps, ram, http, file, ftp,
tmp, bz2]
+ Virtual Schemes: [zip, war, par, ear, jar, sar, ejb3, tar, tbz2, tgz]
+ > info hdfs
+ Provider Info for scheme "hdfs":
+ capabilities: [GET_TYPE, READ_CONTENT, URI, GET_LAST_MODIFIED, ATTRIBUTES,
RANDOM_ACCESS_READ, DIRECTORY_READ_CONTENT, LIST_CHILDREN]
+ > ls hdfs://server:8020/vfs-test/
+ 15/01/09 22:02:06 INFO Configuration.deprecation: fs.default.name is
deprecated. Instead, use fs.defaultFS
+ 15/01/09 22:02:06 WARN util.NativeCodeLoader: Unable to load native-hadoop
library for your platform... using builtin-java classes where applicable
+ Contents of hdfs://server:8020/vfs-test
+ text.txt
+ > cat hdfs://server:8020/vfs-test/text.txt
+ This is a test
+ }}}
+
-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org
[Commons Wiki] Trivial Update of "VfsReleaseState" by BerndEckenfels
Dear Wiki user, You have subscribed to a wiki page or wiki category on "Commons Wiki" for change notification. The "VfsReleaseState" page has been changed by BerndEckenfels: https://wiki.apache.org/commons/VfsReleaseState?action=diff&rev1=7&rev2=8 Comment: hadoop up to date = Upcoming commons-vfs2-2.1 release = - Preview of Site: http://people.apache.org/~ecki/commons-vfs/ + * Preview of Site: http://people.apache.org/~ecki/commons-vfs/ + * Decided: will use manual not release-plugin process + This is a list of things to do for the (upcoming) next release of VFS 2.1 - * decide on minimum hdfs version and update it, finally resolve VFS-530 * update testing/test-server site: some protocols are tested now, hdfs with windows profile - * fix multi-module checkstyle problem (and only show aggregate report toplevel) + * only show aggregate checkstyle report toplevel + * announce Java 1.6 in release-notes * create and commit RELEASE-NOTES.txt - * Decided: will use manual not release-plugin process After Release - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
[Commons Wiki] Update of "VfsProblems" by BerndEckenfels
Dear Wiki user,
You have subscribed to a wiki page or wiki category on "Commons Wiki" for
change notification.
The "VfsProblems" page has been changed by BerndEckenfels:
https://wiki.apache.org/commons/VfsProblems?action=diff&rev1=2&rev2=3
Comment:
add build problems section, ubuntu maven problem
- === VFS - Problems ===
+ == VFS Troubleshooting ==
+ === Build Problems ===
+
+ '''org.apache.commons.lang.!StringUtils missing when running Maven on
Ubuntu'''
+
+ Some Maven goals like `site:stage` fail under Ubuntu 14.04 with
+
+ A required class was missing while executing
+ org.apache.maven.plugins:maven-site-plugin:3.4:stage:
org/apache/commons/lang/StringUtils
+
+ This happens if you use the Ubuntu Maven package which misses the
commons-lang dependency. You can either unpack a stand-alone Maven archive or
use the following commands:
+
+ {{{
+ cd /usr/share/maven/lib
+ sudo ln -s ../../java/commons-lang.jar .
+ }}}
+
+ === Filesystem Problems ===
+
- This page collects steps for various filesystems to check if access to the
destination failes.
+ This page collects steps for various filesystems to check if access to the
destination fails.
'''VfsProblemsFtp'''
-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org
[Commons Wiki] Trivial Update of "VFS" by BerndEckenfels
Dear Wiki user, You have subscribed to a wiki page or wiki category on "Commons Wiki" for change notification. The "VFS" page has been changed by BerndEckenfels: https://wiki.apache.org/commons/VFS?action=diff&rev1=19&rev2=20 Comment: current commons-vfs link, https, better headings = VFS - Virtual File System = - Commons VFS provides a single API for accessing various different file systems. It presents a uniform view of the files from various different sources, such as the files on local disk, on an HTTP server, or inside a Zip archive. + Apache Commons VFS provides a single API for accessing various different file systems. It presents a uniform view of the files from various different sources, such as the files on local disk, on an HTTP server, or inside a Zip archive. - Its homepage is located at: http://commons.apache.org/vfs/. + Its homepage is located at: https://commons.apache.org/proper/commons-vfs/. - == Problems == + == Troubleshooting == What to do if access to a filesystem fails. - '''VfsProblems''' + * '''VfsProblems''' - == Solutions == + == Usage and Solutions == + + * '''VfsExampleShell''' + - '''VfsCacheStrategy''' + * '''VfsCacheStrategy''' == FAQ == @@ -27, +30 @@ == Future == Stuff we will see in (one of) the next release(s): - '''VfsNext''' + * '''VfsNext''' - ideas, todos, open issues (needs cleanup) - '''VfsReleaseState''' - roadmap for next release + * '''VfsReleaseState''' - roadmap for next release == Articles == - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
[Commons Wiki] Update of "VfsReleaseState" by BerndEckenfels
Dear Wiki user, You have subscribed to a wiki page or wiki category on "Commons Wiki" for change notification. The "VfsReleaseState" page has been changed by BerndEckenfels: https://wiki.apache.org/commons/VfsReleaseState?action=diff&rev1=6&rev2=7 Comment: progress: verified and added dependency examples This is a list of things to do for the (upcoming) next release of VFS 2.1 * decide on minimum hdfs version and update it, finally resolve VFS-530 - * announce Java 1.6 in .vm / site (partially done) * update testing/test-server site: some protocols are tested now, hdfs with windows profile * fix multi-module checkstyle problem (and only show aggregate report toplevel) + * announce Java 1.6 in release-notes * create and commit RELEASE-NOTES.txt - * site: finish usage sample (and verify dependencies): http://people.apache.org/~ecki/commons-vfs/download.html (ideally the example shell has a command to list all loaded provider schemes) * Decided: will use manual not release-plugin process - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
[Commons Wiki] Update of "VfsExampleShell" by BerndEckenfels
Dear Wiki user,
You have subscribed to a wiki page or wiki category on "Commons Wiki" for
change notification.
The "VfsExampleShell" page has been changed by BerndEckenfels:
https://wiki.apache.org/commons/VfsExampleShell?action=diff&rev1=3&rev2=4
Comment:
added http which requires common-codec
artifactId=commons-vfs2
}}}
+ For http(s) (and more general URIs):
+ {{{
+ C:vfs> set
LIBS=%REP%\commons-logging\commons-logging\1.2\commons-logging-1.2.jar
+ C:vfs> set
LIBS=%LIBS%;%REP%\org\apache\commons\httpclient;%REP%\commons-httpclient\commons-httpclient\3.1\commons-httpclient-3.1.jar
+ C:vfs> set
LIBS=%LIBS%;%REP%\commons-codec\commons-codec\1.2\commons-codec-1.2.jar
+ C:vfs> set
LIBS=%LIBS%;core\target\commons-vfs2-2.1.jar;examples/target/commons-vfs2-examples-2.1.jar
+ C:vfs> java -cp $LIBS org.apache.commons.vfs2.example.Shell
+ VFS Shell 2.1
+ > cat http://www.facebook.com/robots.txt
+ > cat https://www.apache.org/robots.txt
+ User-agent: *
+ Disallow: /websrc
+ Crawl-Delay: 4
+ }}}
+
-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org
[Commons Wiki] Update of "VfsExampleShell" by BerndEckenfels
Dear Wiki user, You have subscribed to a wiki page or wiki category on "Commons Wiki" for change notification. The "VfsExampleShell" page has been changed by BerndEckenfels: https://wiki.apache.org/commons/VfsExampleShell?action=diff&rev1=4&rev2=5 Comment: added http which requires common-codec C:vfs> set LIBS=%LIBS%;core\target\commons-vfs2-2.1.jar;examples/target/commons-vfs2-examples-2.1.jar C:vfs> java -cp $LIBS org.apache.commons.vfs2.example.Shell VFS Shell 2.1 - > cat http://www.facebook.com/robots.txt > cat https://www.apache.org/robots.txt User-agent: * Disallow: /websrc - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
[Commons Wiki] Update of "VfsExampleShell" by BerndEckenfels
Dear Wiki user,
You have subscribed to a wiki page or wiki category on "Commons Wiki" for
change notification.
The "VfsExampleShell" page has been changed by BerndEckenfels:
https://wiki.apache.org/commons/VfsExampleShell?action=diff&rev1=2&rev2=3
source/
}}}
+ Loading resources from the classpath:
+ {{{
+ VFS Shell 2.1
+ > ls -R res:META-INF/maven/
+ Contents of
jar:file:///C:/ws/asf/commons-vfs2-project/core/target/commons-vfs2-2.1-SNAPSHOT.jar!/META-INF/maven
+ org.apache.commons/
+ commons-vfs2/
+ pom.properties
+ pom.xml
+ > cat res:META-INF/maven/org.apache.commons/commons-vfs2/pom.properties
+ #Generated by Maven
+ #Fri Jan 09 02:48:03 CET 2015
+ version=2.1-SNAPSHOT
+ groupId=org.apache.commons
+ artifactId=commons-vfs2
+ }}}
+
-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org
[Commons Wiki] Trivial Update of "VfsExampleShell" by BerndEckenfels
Dear Wiki user,
You have subscribed to a wiki page or wiki category on "Commons Wiki" for
change notification.
The "VfsExampleShell" page has been changed by BerndEckenfels:
https://wiki.apache.org/commons/VfsExampleShell?action=diff&rev1=1&rev2=2
= Commons VFS Example Shell =
-
This page shows some examples to configure the classpath and use the VFS
Example Shell.
All examples expect to be started from within the Apache Commons VFS source
directory (refering to build artifacts as well as external dependencies in a
local maven repository). Linux/Unix commands are marked with `$` prompt, for
sample Windows command you see a `C:vfs>` prompt.
@@ -19, +18 @@
Info about default manager
"org.apache.commons.vfs2.impl.StandardFileSystemManager":
Provider Schemes: [res, ram, file, tmp, smb]
Virtual Schemes: [gz, zip, war, par, ear, jar, sar, ejb3]
+ > ls smb://Domain\User:PASSWORD@host/Users/
+ Administrator/
+ All Users/
+ User/
+ desktop.ini
}}}
-
Using the ftp(s) provider:
{{{
@@ -40, +43 @@
README.html
RELEASE_NOTES.txt
binaries/
- source/}}}
+ source/
+ }}}
-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org
[Commons Wiki] Update of "VfsExampleShell" by BerndEckenfels
Dear Wiki user,
You have subscribed to a wiki page or wiki category on "Commons Wiki" for
change notification.
The "VfsExampleShell" page has been changed by BerndEckenfels:
https://wiki.apache.org/commons/VfsExampleShell
Comment:
some VFS Example Shell examples
New page:
= Commons VFS Example Shell =
This page shows some examples to configure the classpath and use the VFS
Example Shell.
All examples expect to be started from within the Apache Commons VFS source
directory (refering to build artifacts as well as external dependencies in a
local maven repository). Linux/Unix commands are marked with `$` prompt, for
sample Windows command you see a `C:vfs>` prompt.
Enabling the SMB provider from the sandbox:
{{{
$ REP=~/.m2/repository
$ LIBS=$REP/commons-logging/commons-logging/1.2/commons-logging-1.2.jar
$ LIBS=$LIBS:$REP/jcifs/jcifs/0.8.3/jcifs-0.8.3.jar
$
LIBS=$LIBS:core/target/commons-vfs2-2.1.jar:examples/target/commons-vfs2-examples-2.1.jar:sandbox/target/commons-VFS2-sandbox-2.1.jar
$ java -cp $LIBS org.apache.commons.vfs2.example.Shell
VFS Shell 2.1
> info
Info about default manager
"org.apache.commons.vfs2.impl.StandardFileSystemManager":
Provider Schemes: [res, ram, file, tmp, smb]
Virtual Schemes: [gz, zip, war, par, ear, jar, sar, ejb3]
}}}
Using the ftp(s) provider:
{{{
C:vfs> set REP=\Users\USERNAME\.m2\repository
C:vfs> set
LIBS=%REP%\commons-logging\commons-logging\1.2\commons-logging-1.2.jar
C:vfs> set LIBS=%LIBS%;%REP%\commons-net\commons-net\2.2\commons-net-2.2.jar
C:vfs> set
LIBS=%LIBS%;core\target\commons-vfs2-2.1.jar;examples/target/commons-vfs2-examples-2.1.jar
C:vfs> java -cp $LIBS org.apache.commons.vfs2.example.Shell
VFS Shell 2.1
> info
Info about default manager
"org.apache.commons.vfs2.impl.StandardFileSystemManager":
Provider Schemes: [res, ram, ftps, file, ftp, tmp]
Virtual Schemes: [gz, zip, war, par, ear, jar, sar, ejb3]
> ls ftp://ftp.fau.de/apache/commons/vfs/
Contents of ftp://ftp.fau.de/apache/commons/vfs
HEADER.html
README.html
RELEASE_NOTES.txt
binaries/
source/}}}
-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org
[Commons Wiki] Update of "VfsReleaseState" by BerndEckenfels
Dear Wiki user, You have subscribed to a wiki page or wiki category on "Commons Wiki" for change notification. The "VfsReleaseState" page has been changed by BerndEckenfels: https://wiki.apache.org/commons/VfsReleaseState?action=diff&rev1=5&rev2=6 Comment: added site-todo * update testing/test-server site: some protocols are tested now, hdfs with windows profile * fix multi-module checkstyle problem (and only show aggregate report toplevel) * create and commit RELEASE-NOTES.txt + * site: finish usage sample (and verify dependencies): http://people.apache.org/~ecki/commons-vfs/download.html (ideally the example shell has a command to list all loaded provider schemes) * Decided: will use manual not release-plugin process - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
[Commons Wiki] Update of "VfsReleaseState" by BerndEckenfels
Dear Wiki user, You have subscribed to a wiki page or wiki category on "Commons Wiki" for change notification. The "VfsReleaseState" page has been changed by BerndEckenfels: https://wiki.apache.org/commons/VfsReleaseState?action=diff&rev1=4&rev2=5 Comment: work done: vfs-457 fixed This is a list of things to do for the (upcoming) next release of VFS 2.1 - * check test dependencies, update them and finally resolve VFS-457 * decide on minimum hdfs version and update it, finally resolve VFS-530 - * announce Java 1.6 in .vm / site + * announce Java 1.6 in .vm / site (partially done) * update testing/test-server site: some protocols are tested now, hdfs with windows profile - * define the mave-release-plugin process (tags, RCs, votes) * fix multi-module checkstyle problem (and only show aggregate report toplevel) * create and commit RELEASE-NOTES.txt + + * Decided: will use manual not release-plugin process After Release - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
[Commons Wiki] Update of "UsingGIT" by ThomasNeidhart
Dear Wiki user, You have subscribed to a wiki page or wiki category on "Commons Wiki" for change notification. The "UsingGIT" page has been changed by ThomasNeidhart: https://wiki.apache.org/commons/UsingGIT?action=diff&rev1=10&rev2=11 }}} - The first setting forces Git to only strip accidental CR/LF when committing into the repository, but never when cheking + The first setting forces Git to only strip accidental CR/LF when committing into the repository, but never when checking out files from the repository. The second setting forces Git to convert CR/LF line endings in the workspace while maintaining LF only line endings in the repository. @@ -134, +134 @@ `git diff` (shows only unstaged changes, `git diff --cached` shows prepared commit) * `svn add` -`svn add` -- used to stage for commit +`git add` -- used to stage for commit * `svn update` `git pull` - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
[Commons Wiki] Update of "UsingGIT" by sebbapache
Dear Wiki user,
You have subscribed to a wiki page or wiki category on "Commons Wiki" for
change notification.
The "UsingGIT" page has been changed by sebbapache:
https://wiki.apache.org/commons/UsingGIT?action=diff&rev1=9&rev2=10
Comment:
Trivial typos
can be created. Of course, for collaborative development, some policy has to
be decided and modifications made by one user on its own
cloned repository must be ''pushed'' back to a public repository.
- At Apache, the policy is that the official reference is the one hold by
Apache servers (for example
https://git-wip-us.apache.org/repos/asf/commons-math.git).
+ At Apache, the policy is that the official reference is the one held by
Apache servers (for example
https://git-wip-us.apache.org/repos/asf/commons-math.git).
Therefore, all users who want to get the latest version know this is were
they should point at to retrieve it,
and developers who have commit access must push their modifications back to
this repository for official publication.
@@ -60, +60 @@
line-ending conversion done between the Apache repository and your workspace.
If you are using MacOSX or Linux, you should run: {{{
- git config --global core.autocrlf input`
+ git config --global core.autocrlf input
}}}
If you are using Windows, you should run: {{{
@@ -112, +112 @@
git config --local user.email apach...@apache.org
}}}
- = Comparison with subversion commands =
+ = Comparison with Subversion commands =
One of the most important difference from a user point of view is that since
there is always one ''local'' repository and
one or several ''remote'' repositories, there is a distinction in git between
saving some work only locally on a private
-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org
[Commons Wiki] Update of "FrontPage" by LucMaisonobe
Dear Wiki user, You have subscribed to a wiki page or wiki category on "Commons Wiki" for change notification. The "FrontPage" page has been changed by LucMaisonobe: https://wiki.apache.org/commons/FrontPage?action=diff&rev1=131&rev2=132 Welcome: CommonsEtiquette | CommonsResources | ArticlesAndTutorials - Developers: GettingInvolved | [[UsingSVN]] | UsingGIT | CodeStyle + Developers: GettingInvolved | [[UsingSVN]] | [[UsingGIT]] | CodeStyle Committers: CommonsPeople | ComponentPlans | CommonsCommitters | CommonsOsgi | UsingNexus | CommonsGroupids | Maven3Plan - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
[Commons Wiki] Update of "UsingGIT" by LucMaisonobe
Dear Wiki user, You have subscribed to a wiki page or wiki category on "Commons Wiki" for change notification. The "UsingGIT" page has been changed by LucMaisonobe: https://wiki.apache.org/commons/UsingGIT?action=diff&rev1=8&rev2=9 an example, of course you should adapt it depending on the project). * `svn checkout `''repo-url'' -`git clone https://apach...@git-wip-us.apache.org/repos/asf/commons-math.git` (read/write access, where apacheID is committer ID) +`git clone https://apach...@git-wip-us.apache.org/repos/asf/commons-math.git` (read/write access, where apacheID is committer ID)<> `git clone https://git-wip-us.apache.org/repos/asf/commons-math.git` (read-only access) * `svn diff` @@ -152, +152 @@ `git remote -v` and `git remote origin` * `svn cp` ''https://svn.apache.org/.../trunk'' ''https://svn.apache.org/.../tags/my-tag'' `-m message` -`git tag -m message my-tag` (or better, add also -s or -u option to create a cryptographically signed tag) +`git tag -m message my-tag` (or better, add also -s or -u option to create a cryptographically signed tag)<> if you want the tag to also be on Apache servers, you should `git push origin my-tag` to push it to the origin remote repository) * `svn cp` ''https://svn.apache.org/.../trunk'' ''https://svn.apache.org/.../branches/my-branch'' `-m message` -`git branch my-branch` +`git branch my-branch`<> if you want the branch to also be on Apache servers, you should `git push origin my-branch` to push it to the origin remote repository) * `svn help `''sub-command'' - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
[Commons Wiki] Update of "UsingGIT" by LucMaisonobe
Dear Wiki user,
You have subscribed to a wiki page or wiki category on "Commons Wiki" for
change notification.
The "UsingGIT" page has been changed by LucMaisonobe:
https://wiki.apache.org/commons/UsingGIT?action=diff&rev1=7&rev2=8
you should configure at least configure one parameter: the `core.autocrlf`
setting. This setting will adapt the
line-ending conversion done between the Apache repository and your workspace.
- If you are using MacOSX or Linux, you should run: { { {
+ If you are using MacOSX or Linux, you should run: {{{
git config --global core.autocrlf input`
- } } }
+ }}}
- If you are using Windows, you should run: { { {
+ If you are using Windows, you should run: {{{
git config --global core.autocrlf true
- } } }
+ }}}
The first setting forces Git to only strip accidental CR/LF when committing
into the repository, but never when cheking
@@ -74, +74 @@
If for some reason some specific files needs to be checked in with specific
conversion (or without conversion at all),
they can be specified in a ``.gitattributes`` file. For example, you can
force files to be handled as text, or on
- the contrary to never be considered as text and therefore not converted: { { {
+ the contrary to never be considered as text and therefore not converted: {{{
# general pattern for files known to be text: End Of Line transformations
will be done
*.apt text
*.html text
@@ -102, +102 @@
# specific data files known to not be text: no End Of Line transformations
will be done
src/*/resources/*/weird-*-binary-file -text
- } } }
+ }}}
Two other important parameters should be set, but they may need to be set on
a per-repository
basis, in case you have different usernames and mail addresses for Apache and
non-Apache projects.
In this case, the following comands must be run after you have cloned the
repository, and they
- should be run from inside the cloned workspace: { { {
+ should be run from inside the cloned workspace: {{{
git config --local user.name "You Name"
git config --local user.email apach...@apache.org
- } } }
+ }}}
= Comparison with subversion commands =
-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org
[Commons Wiki] Update of "UsingGIT" by LucMaisonobe
Dear Wiki user,
You have subscribed to a wiki page or wiki category on "Commons Wiki" for
change notification.
The "UsingGIT" page has been changed by LucMaisonobe:
https://wiki.apache.org/commons/UsingGIT?action=diff&rev1=6&rev2=7
= Git References =
There are numerous references available online for Git. The first one is the
official [[http://git-scm.com/book/en/|Pro Git book]].<>
+ A quick Git reference: [[http://gitref.org/|Git Reference]].<>
An Apache specific page is [[https://git-wip-us.apache.org/|here]].<>
There is also a wiki at kernel.org: [[https://git.wiki.kernel.org/|Git Wiki
Homepage]].<>
Also a quick tutorial on [[http://git.or.cz/course/svn.html|Git for SVN
users]].
Eclipse users could have a look at
[[http://www.vogella.com/tutorials/EclipseGit/article.html|Git version control
with Eclipse (EGit) - Tutorial]].
+
+
+ = Git configuration =
+
+ The configuration for the local Git client is stored at two different levels.
There is a `global` configuration
+ (typically in your home directory) where you can put everything that will
remain the same accross all repositories
+ you clone, and there is a `local` configuration in each repository. You can
modify and list configuration keys and
+ values using the `git config` command. Before you try anything else (even
before you clone your first repository),
+ you should configure at least configure one parameter: the `core.autocrlf`
setting. This setting will adapt the
+ line-ending conversion done between the Apache repository and your workspace.
+
+ If you are using MacOSX or Linux, you should run: { { {
+ git config --global core.autocrlf input`
+ } } }
+
+ If you are using Windows, you should run: { { {
+ git config --global core.autocrlf true
+ } } }
+
+
+ The first setting forces Git to only strip accidental CR/LF when committing
into the repository, but never when cheking
+ out files from the repository. The second setting forces Git to convert CR/LF
line endings in the workspace while maintaining
+ LF only line endings in the repository.
+
+ If for some reason some specific files needs to be checked in with specific
conversion (or without conversion at all),
+ they can be specified in a ``.gitattributes`` file. For example, you can
force files to be handled as text, or on
+ the contrary to never be considered as text and therefore not converted: { { {
+ # general pattern for files known to be text: End Of Line transformations
will be done
+ *.apt text
+ *.html text
+ *.java text
+ *.propertiestext
+ *.puml text
+ *.svg text
+ *.txt text
+ *.xml text
+ *.fml text
+
+ # general pattern for files known to not be text: no End Of Line
transformations will be done
+ *.gz -text
+ *.zip -text
+ *.ico -text
+ *.xcf -text
+ *.jpg -text
+ *.odg -text
+ *.png -text
+
+ # specific data files known to be text: End Of Line transformations will be
done
+ .gitattributes text
+ .gitignore text
+ .checkstyle text
+
+ # specific data files known to not be text: no End Of Line transformations
will be done
+ src/*/resources/*/weird-*-binary-file -text
+ } } }
+
+ Two other important parameters should be set, but they may need to be set on
a per-repository
+ basis, in case you have different usernames and mail addresses for Apache and
non-Apache projects.
+ In this case, the following comands must be run after you have cloned the
repository, and they
+ should be run from inside the cloned workspace: { { {
+ git config --local user.name "You Name"
+ git config --local user.email apach...@apache.org
+ } } }
= Comparison with subversion commands =
@@ -88, +152 @@
`git remote -v` and `git remote origin`
* `svn cp` ''https://svn.apache.org/.../trunk''
''https://svn.apache.org/.../tags/my-tag'' `-m message`
-`git tag -m message MY_TAG` (or better, add also -s or -u option to create
a cryptographically signed tag)
+`git tag -m message my-tag` (or better, add also -s or -u option to create
a cryptographically signed tag)
if you want the tag to also be on Apache servers, you should `git push
origin my-tag` to push it to the origin remote repository)
* `svn cp` ''https://svn.apache.org/.../trunk''
''https://svn.apache.org/.../branches/my-branch'' `-m message`
-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional
[Commons Wiki] Update of "UsingGIT" by LucMaisonobe
Dear Wiki user, You have subscribed to a wiki page or wiki category on "Commons Wiki" for change notification. The "UsingGIT" page has been changed by LucMaisonobe: https://wiki.apache.org/commons/UsingGIT?action=diff&rev1=5&rev2=6 * `svn info` `git remote -v` and `git remote origin` + * `svn cp` ''https://svn.apache.org/.../trunk'' ''https://svn.apache.org/.../tags/my-tag'' `-m message` +`git tag -m message MY_TAG` (or better, add also -s or -u option to create a cryptographically signed tag) +if you want the tag to also be on Apache servers, you should `git push origin my-tag` to push it to the origin remote repository) + + * `svn cp` ''https://svn.apache.org/.../trunk'' ''https://svn.apache.org/.../branches/my-branch'' `-m message` +`git branch my-branch` +if you want the branch to also be on Apache servers, you should `git push origin my-branch` to push it to the origin remote repository) + + * `svn help `''sub-command'' +`git` ''sub-command'' `--help` + - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
[Commons Wiki] Update of "UsingGIT" by LucMaisonobe
Dear Wiki user, You have subscribed to a wiki page or wiki category on "Commons Wiki" for change notification. The "UsingGIT" page has been changed by LucMaisonobe: https://wiki.apache.org/commons/UsingGIT?action=diff&rev1=4&rev2=5 An Apache specific page is [[https://git-wip-us.apache.org/|here]].<> There is also a wiki at kernel.org: [[https://git.wiki.kernel.org/|Git Wiki Homepage]].<> Also a quick tutorial on [[http://git.or.cz/course/svn.html|Git for SVN users]]. + Eclipse users could have a look at [[http://www.vogella.com/tutorials/EclipseGit/article.html|Git version control with Eclipse (EGit) - Tutorial]]. = Comparison with subversion commands = - - We first list a subversion command, and after that the equivalent git command. One of the most important difference from a user point of view is that since there is always one ''local'' repository and one or several ''remote'' repositories, there is a distinction in git between saving some work only locally on a private @@ -60, +59 @@ and `status`) only work on the local copy of a remote repository. You should therefore use `git fetch` regularly to refresh your copy (if you do not want to `pull`). + We first list a subversion command, and after that the equivalent git command (we use Apache Commons Math git repository as + an example, of course you should adapt it depending on the project). + * `svn checkout `''repo-url'' +`git clone https://apach...@git-wip-us.apache.org/repos/asf/commons-math.git` (read/write access, where apacheID is committer ID) -`git clone https://git-wip-us.apache.org/repos/asf/commons-math.git` +`git clone https://git-wip-us.apache.org/repos/asf/commons-math.git` (read-only access) * `svn diff` `git diff` (shows only unstaged changes, `git diff --cached` shows prepared commit) - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
[Commons Wiki] Update of "UsingGIT" by BerndEckenfels
Dear Wiki user, You have subscribed to a wiki page or wiki category on "Commons Wiki" for change notification. The "UsingGIT" page has been changed by BerndEckenfels: https://wiki.apache.org/commons/UsingGIT?action=diff&rev1=3&rev2=4 Comment: wikified links, formatted commands, use https instead of http, explain offline, explain staging = Overview = - Some of the Apache Commons components use [http://git-scm.com/ GIT] Source Code Management System instead of [http://subversion.apache.org Subversion]. + Some of the Apache Commons components use [[http://git-scm.com/|GIT]] Source Code Management System instead of [[http://subversion.apache.org|Subversion]]. Both systems allow collaborative development and both systems maintain an history of file changes. There are however several differences. = Distributed Version Control = Git is a distributed version control system. This means that instead of a single central repository holding the full history of project - files and numerous clients connecting to it to check out some versions, Git uses a symetrical view were everyone connecting to the + files and numerous clients connecting to it to check out some versions, Git uses a symmetrical view were everyone connecting to the repository clones the full history and from then on could (at least theoretically) act as a new server that another user could clone and so on. Each repository is created by cloning an ''origin'' repository. Once cloned, the ''origin'' repository is the first ''remote'' repository known to the clone. It is possible to add later on several other ''remote'', so a complete web of repositories can be created. Of course, for collaborative development, some policy has to be decided and modifications made by one user on its own cloned repository must be ''pushed'' back to a public repository. - At Apache, the policy is that the official reference is the one hold by Apache servers (for example http://git-wip-us.apache.org/repos/asf/commons-math.git). + At Apache, the policy is that the official reference is the one hold by Apache servers (for example https://git-wip-us.apache.org/repos/asf/commons-math.git). Therefore, all users who want to get the latest version know this is were they should point at to retrieve it, and developers who have commit access must push their modifications back to this repository for official publication. @@ -27, +27 @@ review the work would declare this repository as a remote for his own working clone and would ''pull'' the proposed changes. He could review everything on his computer, and if satisfied could ''push'' the to the Apache ''origin'' repository, as he has write access to it. In a way, the Apache committer acts here as a proxy for the contributor, and makes sure everything is good to include. + (Consequently Git can have different authors and commiters of a commit. If pulled in as git-patch or pull request the author is preserved). A second use case is an Apache committer working either on a long experimental stuff not yet ready for publication or working without internet access for some time (typically during a business trip). In both cases, the committer would simply commit @@ -41, +42 @@ = Git References = - There are numerous references available online for Git. The first one is the official [http://git-scm.com/book/en/ Pro Git book]. + There are numerous references available online for Git. The first one is the official [[http://git-scm.com/book/en/|Pro Git book]].<> - An Apache specific page is [https://git-wip-us.apache.org/ here] + An Apache specific page is [[https://git-wip-us.apache.org/|here]].<> - There is also a wiki at kernel.org: [https://git.wiki.kernel.org/ Git Wiki Homepage] + There is also a wiki at kernel.org: [[https://git.wiki.kernel.org/|Git Wiki Homepage]].<> - Also a quick tutorial on [http://git.or.cz/course/svn.html Git for SVN users] + Also a quick tutorial on [[http://git.or.cz/course/svn.html|Git for SVN users]]. = Comparison with subversion commands = @@ -55, +56 @@ computer and making it available to other people who see only public remote computers. The first action is called ''commit'', and it is therefore completely different from a subversion commit. The second action is called ''push''. The equivalent to svn commit is therefore a pair of two commands, git commit followed by git push. It is possible to perform several - git commits without doing any git push, which is impossible to do with subversion. + git commits without doing any git push, which is impossible to do with subversion. Note that most commands (including `log` + and `status`) only work on the local copy of a remote repository. You should therefore use `git fetch` regularly to refresh your + copy (if you do not want to `pull`). - * svn checkout + * `svn checkout `''repo-url'' -git clone http://git-wip-us.apache.org/repos/asf/commons-math.git +
[Commons Wiki] Update of "UsingGIT" by sebbapache
Dear Wiki user, You have subscribed to a wiki page or wiki category on "Commons Wiki" for change notification. The "UsingGIT" page has been changed by sebbapache: https://wiki.apache.org/commons/UsingGIT?action=diff&rev1=2&rev2=3 computer and making it available to other people who see only public remote computers. The first action is called ''commit'', and it is therefore completely different from a subversion commit. The second action is called ''push''. The equivalent to svn commit is therefore a pair of two commands, git commit followed by git push. It is possible to perform several - git commit without doing any git push, which is impossible to do with subversion. + git commits without doing any git push, which is impossible to do with subversion. * svn checkout git clone http://git-wip-us.apache.org/repos/asf/commons-math.git @@ -69, +69 @@ * svn commit git commit, followed by git push + * svn status +git status + + * svn revert ''path'' +git checkout ''path'' + - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
[Commons Wiki] Update of "UsingGIT" by sebbapache
Dear Wiki user, You have subscribed to a wiki page or wiki category on "Commons Wiki" for change notification. The "UsingGIT" page has been changed by sebbapache: https://wiki.apache.org/commons/UsingGIT?action=diff&rev1=1&rev2=2 Comment: Added link to http://git.or.cz/course/svn.html cloned repository must be ''pushed'' back to a public repository. At Apache, the policy is that the official reference is the one hold by Apache servers (for example http://git-wip-us.apache.org/repos/asf/commons-math.git). - Therefore, all users who want to get the latest version known this is were they should point at to retrieve it, + Therefore, all users who want to get the latest version know this is were they should point at to retrieve it, and developers who have commit access must push their modifications back to this repository for official publication. Distributed version control allow some additional features. @@ -44, +44 @@ There are numerous references available online for Git. The first one is the official [http://git-scm.com/book/en/ Pro Git book]. An Apache specific page is [https://git-wip-us.apache.org/ here] There is also a wiki at kernel.org: [https://git.wiki.kernel.org/ Git Wiki Homepage] + Also a quick tutorial on [http://git.or.cz/course/svn.html Git for SVN users] = Comparison with subversion commands = - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
[Commons Wiki] Update of "ContributorsGroup" by sebbapache
Dear Wiki user, You have subscribed to a wiki page or wiki category on "Commons Wiki" for change notification. The "ContributorsGroup" page has been changed by sebbapache: https://wiki.apache.org/commons/ContributorsGroup?action=diff&rev1=12&rev2=13 Comment: += KristianRosenvold * GillesSadowski * JörgSchaible * KonstantinKolinko + * KristianRosenvold * LucMaisonobe * MattBenson * NiallPemberton - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
[Commons Wiki] Update of "UsingGIT" by LucMaisonobe
Dear Wiki user, You have subscribed to a wiki page or wiki category on "Commons Wiki" for change notification. The "UsingGIT" page has been changed by LucMaisonobe: https://wiki.apache.org/commons/UsingGIT Comment: Page creation New page: = Overview = Some of the Apache Commons components use [http://git-scm.com/ GIT] Source Code Management System instead of [http://subversion.apache.org Subversion]. Both systems allow collaborative development and both systems maintain an history of file changes. There are however several differences. = Distributed Version Control = Git is a distributed version control system. This means that instead of a single central repository holding the full history of project files and numerous clients connecting to it to check out some versions, Git uses a symetrical view were everyone connecting to the repository clones the full history and from then on could (at least theoretically) act as a new server that another user could clone and so on. Each repository is created by cloning an ''origin'' repository. Once cloned, the ''origin'' repository is the first ''remote'' repository known to the clone. It is possible to add later on several other ''remote'', so a complete web of repositories can be created. Of course, for collaborative development, some policy has to be decided and modifications made by one user on its own cloned repository must be ''pushed'' back to a public repository. At Apache, the policy is that the official reference is the one hold by Apache servers (for example http://git-wip-us.apache.org/repos/asf/commons-math.git). Therefore, all users who want to get the latest version known this is were they should point at to retrieve it, and developers who have commit access must push their modifications back to this repository for official publication. Distributed version control allow some additional features. A first use case is a user who do not have commit access but would like to contribute something to the project. This user would clone the Apache ''origin'' repository on a publicly accessible computer where he would have commit access, then he would commit his changes there. Once the features are complete, the user would propose to the project that they import his changes back to the official Apache repository. In order to do so, he would make his repository available (even read-only). Then an Apache committer willing to review the work would declare this repository as a remote for his own working clone and would ''pull'' the proposed changes. He could review everything on his computer, and if satisfied could ''push'' the to the Apache ''origin'' repository, as he has write access to it. In a way, the Apache committer acts here as a proxy for the contributor, and makes sure everything is good to include. A second use case is an Apache committer working either on a long experimental stuff not yet ready for publication or working without internet access for some time (typically during a business trip). In both cases, the committer would simply commit his work on his laptop, using the full features of the source code management system (branches, version comparisons, commits, ...). Once the experiment is completed or internet access is recovered, the committer would push his work from the past few hours, days or week back to official repository, with all independent commits preserved instead of being forced to push a big blob representing a tremendous work all at once, which would be impossible for his peer committers to review. A third use case is a user who do not have commit access (and don't want to), but needs to maintain some local changes. This user would clone the Apache ''origin'' repository on a private computer, use Git on this computer to manage his local changes, and from time to time will merge changes from origin into his clone. This user would never push anything back. = Git References = There are numerous references available online for Git. The first one is the official [http://git-scm.com/book/en/ Pro Git book]. An Apache specific page is [https://git-wip-us.apache.org/ here] There is also a wiki at kernel.org: [https://git.wiki.kernel.org/ Git Wiki Homepage] = Comparison with subversion commands = We first list a subversion command, and after that the equivalent git command. One of the most important difference from a user point of view is that since there is always one ''local'' repository and one or several ''remote'' repositories, there is a distinction in git between saving some work only locally on a private computer and making it available to other people who see only public remote computers. The first action is called ''commit'', and it is therefore completely different from a subversion commit. The second action is called ''push''. The equivalent to svn commit is therefore a pair of two commands, git commit followed by git push. It is possible to perform several git commit without doing
[Commons Wiki] Update of "FrontPage" by LucMaisonobe
Dear Wiki user,
You have subscribed to a wiki page or wiki category on "Commons Wiki" for
change notification.
The "FrontPage" page has been changed by LucMaisonobe:
https://wiki.apache.org/commons/FrontPage?action=diff&rev1=130&rev2=131
Comment:
Adding a page for GIT
##language:en
#pragma section-numbers off
+ = Welcome to the Apache Commons Wiki =
+ || {{http://commons.apache.org/images/logo.png}} ||This is the
[[ApacheGeneral:FrontPage|Apache Wiki]] for the
[[http://commons.apache.org/|Apache Commons]] project and is maintained by the
[[commons:FrontPage|Commons]] community. To edit pages, visit
[[UserPreferences|login]] near the top right corner of any page to create a
user profile or to login. Then send a brief request '''(including your wiki
username)''' to the [[http://commons.apache.org/mail-lists.html|Commons dev@
list]] asking to be added to the [[ContributorsGroup|Contributors Group]]. You
can then edit the pages in this Wiki. Notifications of all changes you make
will be sent to the dev@commons mailing list, so we will be aware of your
changes and we will happily correct any small mistakes that you might make. ||
- = Welcome to the Apache Commons Wiki =
- || {{http://commons.apache.org/images/logo.png}} || This is the
[[ApacheGeneral:FrontPage|Apache Wiki]] for the
[[http://commons.apache.org/|Apache Commons]] project and is maintained by the
[[commons:FrontPage|Commons]] community. To edit pages, visit
[[UserPreferences|login]] near the top right corner of any page to create a
user profile or to login. Then send a brief request '''(including your wiki
username)''' to the [[http://commons.apache.org/mail-lists.html| Commons dev@
list]] asking to be added to the [[ContributorsGroup|Contributors Group]]. You
can then edit the pages in this Wiki. Notifications of all changes you make
will be sent to the dev@commons mailing list, so we will be aware of your
changes and we will happily correct any small mistakes that you might make. ||
We're a [[http://wiki.apache.org/commons/FrontPage|Commons]] community,
dedicated to creating reusable library components in Java. Apache Commons is
now using [[http://subversion.tigris.org/|Subversion]] as the version control
system.
Welcome: CommonsEtiquette | CommonsResources | ArticlesAndTutorials
- Developers: GettingInvolved | [[UsingSVN]] | CodeStyle
+ Developers: GettingInvolved | [[UsingSVN]] | UsingGIT | CodeStyle
Committers: CommonsPeople | ComponentPlans | CommonsCommitters | CommonsOsgi
| UsingNexus | CommonsGroupids | Maven3Plan
Bug Reports: [[http://issues.apache.org/jira/secure/Dashboard.jspa|Jira]]
= Components =
+ On this wiki:
- On this wiki:
+ *
- * [[BeanUtils]] - Utilities for manipulating java beans, including copying
properties, cloning, invoking methods and type conversion.
+ BeanUtils - Utilities for manipulating java beans, including copying
properties, cloning, invoking methods and type conversion.
+
+ *
- * [[Betwixt]] - Services for mapping !JavaBeans to XML documents, and vice
versa.
+ [[Betwixt]] - Services for mapping !JavaBeans to XML documents, and vice
versa.
+
+ *
- * [[Chain]] - A "Chain of Responsibility" pattern implemention for
organizing complex processing flows.
+ [[Chain]] - A "Chain of Responsibility" pattern implemention for organizing
complex processing flows.
+
+ *
- * [[CLI]] - Command Line Interface library for processing command-line
options and arguments.
+ [[CLI]] - Command Line Interface library for processing command-line options
and arguments.
+
+ *
- * [[Codec]] - General encoding/decoding algorithms. Includes some phonetic
encoders, Hex, Base64, and a URL encoder.
+ [[Codec]] - General encoding/decoding algorithms. Includes some phonetic
encoders, Hex, Base64, and a URL encoder.
+
+ *
- * [[Collections]] - Builds upon the Java Collections Framework of List, Set
and Map to provide many more implementations, new collections and abstract base
classes.
+ [[Collections]] - Builds upon the Java Collections Framework of List, Set
and Map to provide many more implementations, new collections and abstract base
classes.
+
+ *
- * [[Configuration]] - Tools to assist in the reading of
configuration/preferences files in various formats
+ [[Configuration]] - Tools to assist in the reading of
configuration/preferences files in various formats
+
+ *
- * [[Compress]] - Defines an API for working with archives and compression
formats including but not limited to: tar,gz, ar, cpio, zip and bzip2 files
+ [[Compress]] - Defines an API for working with archives and compression
formats including but not limited to: tar,gz, ar, cpio, zip and bzip2 files
+
+ *
- * [[Daemon]] - Run (java) applications as windows service or UNIX daemon.
+ [[Daemon]] - Run (java) applications as windows service or UNI
[Commons Wiki] Update of "ContributorsGroup" by sebbapache
Dear Wiki user, You have subscribed to a wiki page or wiki category on "Commons Wiki" for change notification. The "ContributorsGroup" page has been changed by sebbapache: https://wiki.apache.org/commons/ContributorsGroup?action=diff&rev1=11&rev2=12 * GillesSadowski * JörgSchaible * KonstantinKolinko + * LucMaisonobe * MattBenson * NiallPemberton * OliverHeger - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
[Commons Wiki] Update of "VfsReleaseState" by BerndEckenfels
Dear Wiki user, You have subscribed to a wiki page or wiki category on "Commons Wiki" for change notification. The "VfsReleaseState" page has been changed by BerndEckenfels: https://wiki.apache.org/commons/VfsReleaseState?action=diff&rev1=3&rev2=4 This is a list of things to do for the (upcoming) next release of VFS 2.1 * check test dependencies, update them and finally resolve VFS-457 + * decide on minimum hdfs version and update it, finally resolve VFS-530 * announce Java 1.6 in .vm / site * update testing/test-server site: some protocols are tested now, hdfs with windows profile * define the mave-release-plugin process (tags, RCs, votes) - * fix multi-module checkstyle problem - * decide on minimum hdfs version and update it, finally resolve VFS-530 + * fix multi-module checkstyle problem (and only show aggregate report toplevel) + * create and commit RELEASE-NOTES.txt After Release - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
[Commons Wiki] Update of "VfsReleaseState" by BerndEckenfels
Dear Wiki user, You have subscribed to a wiki page or wiki category on "Commons Wiki" for change notification. The "VfsReleaseState" page has been changed by BerndEckenfels: https://wiki.apache.org/commons/VfsReleaseState?action=diff&rev1=2&rev2=3 Comment: regenerated download template (2.0 release), added site preview link = Upcoming commons-vfs2-2.1 release = + + Preview of Site: http://people.apache.org/~ecki/commons-vfs/ This is a list of things to do for the (upcoming) next release of VFS 2.1 * check test dependencies, update them and finally resolve VFS-457 * announce Java 1.6 in .vm / site - * add 2.0 release (1.5) to download page (release.2) * update testing/test-server site: some protocols are tested now, hdfs with windows profile * define the mave-release-plugin process (tags, RCs, votes) * fix multi-module checkstyle problem @@ -15, +16 @@ After Release * close all 2.1 bugs (resolved->closed) + * open next snapshot + * DOAP file - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
[Commons Wiki] Trivial Update of "VfsReleaseState" by BerndEckenfels
Dear Wiki user, You have subscribed to a wiki page or wiki category on "Commons Wiki" for change notification. The "VfsReleaseState" page has been changed by BerndEckenfels: https://wiki.apache.org/commons/VfsReleaseState?action=diff&rev1=1&rev2=2 Comment: added VFS-530 * update testing/test-server site: some protocols are tested now, hdfs with windows profile * define the mave-release-plugin process (tags, RCs, votes) * fix multi-module checkstyle problem + * decide on minimum hdfs version and update it, finally resolve VFS-530 After Release - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
[Commons Wiki] Update of "VfsReleaseState" by BerndEckenfels
Dear Wiki user, You have subscribed to a wiki page or wiki category on "Commons Wiki" for change notification. The "VfsReleaseState" page has been changed by BerndEckenfels: https://wiki.apache.org/commons/VfsReleaseState Comment: Initial Todos. New page: = Upcoming commons-vfs2-2.1 release = This is a list of things to do for the (upcoming) next release of VFS 2.1 * check test dependencies, update them and finally resolve VFS-457 * announce Java 1.6 in .vm / site * add 2.0 release (1.5) to download page (release.2) * update testing/test-server site: some protocols are tested now, hdfs with windows profile * define the mave-release-plugin process (tags, RCs, votes) * fix multi-module checkstyle problem After Release * close all 2.1 bugs (resolved->closed) - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
[Commons Wiki] Update of "VFS" by BerndEckenfels
Dear Wiki user, You have subscribed to a wiki page or wiki category on "Commons Wiki" for change notification. The "VFS" page has been changed by BerndEckenfels: https://wiki.apache.org/commons/VFS?action=diff&rev1=18&rev2=19 Comment: Add release preparation page Its homepage is located at: http://commons.apache.org/vfs/. - == Problems == What to do if access to a filesystem fails. '''VfsProblems''' - == Solutions == '''VfsCacheStrategy''' - == FAQ == Lets start creating a FAQ: * '''VfsFaq''' + * '''VfsCapabilitiesMatrix''' - == Future == Stuff we will see in (one of) the next release(s): '''VfsNext''' + '''VfsReleaseState''' - roadmap for next release + - == Articles == * [[http://www.devx.com/Java/Article/30117|Extend the JDK Classes with Jakarta Commons, Part III]] - Explore Jakarta Commons components that enable you to parse arguments in a command-line application, connect to various file systems at the same time, allow an application to uniformly access configurations loaded from various sources, and pool any object. + * [[http://www.jroller.com/phidias/entry/scripting_vfs|Scripting VFS]] - JavaScript scripting examples using Commons VFS - == Related Projects == * [[http://vfsjfilechooser.sourceforge.net/|VFS JFileChooser]] - A Java Swing component which browses local or remote locations using VFS + * [[http://dctmvfs.sourceforge.net/|Dctm VFS]] - Provides a plugin for Commons VFS that allows you to access EMC Documentum as a filesystem. + * [[http://dctmvfs.sourceforge.net/ftpserver-vfs/|VFS FTPServer]] - provides a Commons VFS implementation for the Apache FTPServer project + * [[http://code.google.com/p/gaevfs/|GaeVFS]] - GaeVFS is an Apache Commons VFS plug-in that implements a distributed, writeable virtual file system for Google App Engine (GAE) for Java. + * [[http://commons-vfs-ui.sourceforge.net/|Commons VFS UI]] - Commons VFS UI is a gui application for the Commons VFS. + - * [[https://github.com/abashev/vfs-s3|VFS-S3]] - Amazon S3 plugin for VFS (Apache Commons Virtual File System). VFS-S3 allows you to operate Amazon S3 buckets and files using Commons VFS. Original version from [[http://code.google.com/p/vfs-s3/]] was outdated and is not supported anymore - [[http://code.google.com/p/vfs-s3/issues/detail?id=4|proof]] + * [[https://github.com/abashev/vfs-s3|VFS-S3]] - Amazon S3 plugin for VFS (Apache Commons Virtual File System). VFS-S3 allows you to operate Amazon S3 buckets and files using Commons VFS. Original version from http://code.google.com/p/vfs-s3/ was outdated and is not supported anymore - [[http://code.google.com/p/vfs-s3/issues/detail?id=4|proof]] + - * [[http://sourceforge.net/projects/commonsvfsgrid/|Commons VFS Grid]] - Commons VFS Grid is a collection of file system providers for Commons VFS, which provide SRB, GridFTP and other Grid file systems. + * [[http://sourceforge.net/projects/commonsvfsgrid/|Commons VFS Grid]] - Commons VFS Grid is a collection of file system providers for Commons VFS, which provide SRB, GridFTP and other Grid file systems. + * [[http://sourceforge.net/projects/loopy/|Loopy]] - Loopy is ISO9660 file system (i.e. .iso files) plug-in for Apache Commons VFS. + - * [[http://sourceforge.net/projects/vfs-utils/|VFS-utils]] - This project provides some utilities for working with the Apache Commons VFS libraries. It provides a bridge to the Apache Mina FTP Server and a Java shell / console providing a command line interface to VFS operations. + * [[http://sourceforge.net/projects/vfs-utils/|VFS-utils]] - This project provides some utilities for working with the Apache Commons VFS libraries. It provides a bridge to the Apache Mina FTP Server and a Java shell / console providing a command line interface to VFS operations. + - * [[http://www.antcommander.com/|Ant Commander]] - Ant Commander is a free file manager written in Java/Swing and is based on Apache Ant and Apache Commons-vfs. Ant Commander includes Commons-vfs and the libraries needed for the different file systems. + * [[http://www.antcommander.com/|Ant Commander]] - Ant Commander is a free file manager written in Java/Swing and is based on Apache Ant and Apache Commons-vfs. Ant Commander includes Commons-vfs and the libraries needed for the different file systems. + * [[http://www.leisenfels.com/products/vfslib|VFSLib Java Library]] - Commons VFS providers for Dropbox, Google Drive, and Amazon S3 cloud file systems first published in 2013. + * [[https://github.com/ecki/seeburger-vfs2|seeburger-vfs2]] - VFS providers for database blobs and layered git-trees + - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
[Commons Wiki] Update of "VfsNext" by BerndEckenfels
Dear Wiki user,
You have subscribed to a wiki page or wiki category on "Commons Wiki" for
change notification.
The "VfsNext" page has been changed by BerndEckenfels:
https://wiki.apache.org/commons/VfsNext?action=diff&rev1=21&rev2=22
Comment:
added todos from project-site.
= VFS - Next =
-
== done - 1. apply http://issues.apache.org/bugzilla/show_bug.cgi?id=33795 ==
-
ram filesystem
== partially done. 2. apply http://issues.apache.org/jira/browse/VFS-43 ==
@@ -27, +25 @@
exif.process();
String camera = exif.getCameraModel();
}}}
-
You get the idea?
Finally I decided to use the wording "operation" (idea from:
http://people.tryphon.org/~alban/io-operations/docs/api/index.html) instead of
"service".
@@ -38, +35 @@
Using a callback mechanism to get this data when needed.
== 4. progress, pause and cancellation api ==
- callbacks to be informed about ongoing operations (copy, move, rename,
delete, copy-progress, move-progress (if between filesystems))
+ callbacks to be informed about ongoing operations (copy, move, rename,
delete, copy-progress, move-progress (if between filesystems)) Ability to pause
or cancel the operation.
- Ability to pause or cancel the operation.
== 5. browse roots ==
e.g. smb or local partitions (windows - c:, d:, ...)
@@ -71, +67 @@
== 11. write support for archives ==
this would require it to
+
1. copy the archive locally
- 2. apply the change
+ 1. apply the change
- 3. repack the archive
+ 1. repack the archive
- 4. copy the archive back to its place
+ 1. copy the archive back to its place
We should stay in state 2. until one sends a signal to finish with the
archive.
== new filesystems ==
-
* pop, imap (useable for emails)
* mime (for the email itself - pretty much like an archive)
+
Consider this url:
+
{{{
zip:mime:imap://user@mailserver/INBOX/folders/newMail.mime!/attachment1.zip!/zipentry.txt
}}}
Cool, isnt it?
+
* generic XML
* ant (only a variant of XML? Cant we just set a dtd or scheme using some
sort of configurationOption ?)
* java structure (by class, by source?)
- == wishes ==
+ == Todos ==
+ The following is a list of items that need to be completed.
Contributions are welcome!
+ === Release 1.1 ===
+* moveTo should handle a directory move if it moves from a
different filesystem.
+
+ === Open ===
+* More documentation (status, file naming etc).
+ * Fix the TODO items
+ * Add more providers:
+ * rsync
+ * subversion
+ * nfs
+ * cvs
+ * jdbc filesystem
+ * xml filesystem
+ * jndi
+ * imap
+ * local mirror
+ * spidering http
+ * ...
+ * JNDI integration.
+ * Formalise the provider API.
+ * WebDAV Provider:
+ * Add plain http support, and auto-detect dav resources.
+ * Add set last-modified.
+ * HTTPS
+ * Zip/Jar Provider:
+ * Extract an AbstractLayerFileSystem out of ZipFileSystem.
+ * Track changes to the parent layer. Eg when the
parent layer is deleted, mark all the files in the
fs as 'does-not-exist'.
+ * Add support for writing to zip/jar files.
+ * URL Provider:
+ * Support attributes.
+ * HTTP Provider:
+ * Support attributes.
+ * HTTPS support.
+ * The local disk caching mechanism also needs more work. Needs
to check last-modified time. Replicator needs to be more
configurable.
+ * Add persistent replicator.
+ * Finish support for junctions: Make ancestors of a junction
point visible, fire events when junction is added or removed,
tests.
+ * Add support for federation (ie transparently crossing file
system boundaries, such as drilling down into the contents
of a Jar file).
+ * Add an equivalent of the fileScanner Jelly tag.
+ * Add an equivalent of Ant path, fileset, dirset, filelist, etc.
Ideally, these can be abstracted into a single data type.
+ * Allow selectors, name mappers, and filters to be specified
for the Ant tasks.
+ * Add capabilities to FileObject.
+ * Attributes and attribute schema.
+ * Handle file canonicalisation better (for cases like
case-insensitive file systems, symbolic links, name mangling, etc).
+ * Add more selectors: XPath, Ant style, regular expression.
+ * Add adaptor (NodePointerFactory?) for use with JXpath.
+ * Add content-changed, attribute-changed, and move events to
FileListener. Maybe split into structure and content
listeners.
+ * Get/set the file permissions.
+ * Automatically checksum and/or verify remote files.
+ * Look at adding native code for fine-grained control over
permissions, file monitoring, faster move
[Commons Wiki] Update of "MavenAndClasspath" by sebbapache
Dear Wiki user,
You have subscribed to a wiki page or wiki category on "Commons Wiki" for
change notification.
The "MavenAndClasspath" page has been changed by sebbapache:
https://wiki.apache.org/commons/MavenAndClasspath
New page:
This page describes why Maven coordinates and Java class package names need to
be co-ordinated.
== Maven classpath ==
Maven identifies jars using the coordinate triple {groupId, artifactId,
version}.
It assumes that jars with the same pair {groupId, artifactId} are different
versions of the same jar,
and will ensure that only one instance of the jar is added to the classpath (in
general the one with the highest version).
Jars with different {groupId, artifactId} pairs are treated as entirely
different jars, even if they contain identical classes.
Maven does not examine the contents of jars; it relies on the {groupId,
artifactId} pair to determine whether different jars have the same or different
classes in them.
== Java classloader ==
The Java runtime system only allows a single instance of a class to exist in a
given classloader.
Classes are uniquely identified using the package name and class name.
For example, the class {{{Utils}}} in the package
{{{org.apache.commons.example}}} can only appear once in a classloader.
The classloader uses the classpath to find the classes needed by an application.
If the classpath contains more than one jar which contains the above Utils
class, then the JVM will load only one of the instances.
If the class instances in the different jars are identical, then this is not a
problem, but if there are two different versions of the class, the classloader
may choose the wrong one. And different JVMs may process the classpath in a
different order.
To ensure that the expected class is loaded, it is vital that the classpath
only contain a single instance of each different class.
This is normally achieved by grouping classes in jars according to their
package names, and ensuring that there is only one instance of each such jar on
the classpath.
==Maven coords and package names==
When using Maven to construct the classpath, it is therefore essential that
Maven knows which jars hold different versions of the same classes and which
jars have completely different classes.
Therefore, it is vital that two jars with the same {groupId, artifactId} pair
use the same package name.
Likewise, it is vital that two jars with the same package name use the same
{groupId, artifactId} pair.
'''There must be a 1-1 correspondance between the Maven {groupId, artifactId}
pair and the Java package name.'''
If either/both of the Maven groupId or artifactId is changed, the package name
must be changed.
Otherwise, Maven may add more than one copy of a class to the classpath (in
different jars) causing unpredictable behaviour.
Likewise, a change of package name (e.g. for a binary break) must be
accompanied by a change of either Maven groupId or artifactId.
Otherwise, Maven won't be able to to add the original package name to the
classpath, breaking code that relies on the original package name.
-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org
[Commons Wiki] Update of "UsingNexus" by GaryGregory
Dear Wiki user,
You have subscribed to a wiki page or wiki category on "Commons Wiki" for
change notification.
The "UsingNexus" page has been changed by GaryGregory:
https://wiki.apache.org/commons/UsingNexus?action=diff&rev1=34&rev2=35
Comment:
Update section "Publish the website" with link to SCM publishing docs.
This will create the binary, source and javadoc jars and hashes and upload
them.
- The {{{-Prelease}}} flag ensures that the source and javadoc jars are created.
- The {{{-Dgpg.skip}}} flag skips the signing phase; do not omit this as it
might mislead users if a signed jar was deployed as a snapshot
+ The {{{-Prelease}}} flag ensures that the source and javadoc jars are
created. The {{{-Dgpg.skip}}} flag skips the signing phase; do not omit this as
it might mislead users if a signed jar was deployed as a snapshot
The resulting snapshot will appear in the Nexus repository under:
@@ -253, +252 @@
-DstagingSiteURL=scp://[...]/people.apache.org/builds/commons/compress/1.1/RC1
}}}
The site should appear on the specified folder. Alternatively, you can stage
the site in your ''public_html'' folder in your home directory on
''people.apache.org''. This can be done with the following command:
+
{{{
mvn site:stage-deploy
-DstagingSiteURL=scp://people.apache.org/home//public_html/foo-1.2rc1
}}}
-
Send Out The Vote
Below you find a vote template to save you some time ...
@@ -313, +312 @@
* -e robots=off ignore robots.txt
* --wait 10 wait between retrievals
- Check the MD5/SHA hashes! This can be done for instance with the
''verify_sigs.sh'' script available under
[[https://svn.apache.org/repos/private/committers/tools/releases]] (just check
out from SVN and place the shell scripts in the ''bin'' folder below your home
directory).
+ Check the MD5/SHA hashes! This can be done for instance with the
''verify_sigs.sh'' script available under
https://svn.apache.org/repos/private/committers/tools/releases (just check out
from SVN and place the shell scripts in the ''bin'' folder below your home
directory).
Also, change the group to commons and ensure that the files can be written by
the group:
+
{{{
chgrp commons *
chmod g+w *
@@ -368, +368 @@
1. Follow the links to the binaries and source directories. Check them in a
similar manner.
= Publish the website =
+ See https://commons.apache.org/site-publish.html
- Run the following to deploy the new component website:
-
- {{{
- mvn site:deploy
- }}}
- On people.apache.org, verify that the directory has been updated, and that
the file and directory permissions are correct (readable by all, not writeable
by world, but group writeable). Also, ensure that the group is set to
'commons'. For example:
-
- {{{
- pwd commons.apache.org : ls -l compress
- total 1366
- drwxrwsr-x 5 niallp commons 20 Aug 19 07:22 apidocs
- -rw-rw-r-- 1 grobmeier commons 21050 Aug 19 09:19 changes-report.html
- drwxrwsr-x 5 niallp commons 98 Aug 19 07:22 cobertura
- -rw-rw-r-- 1 grobmeier commons7555 Aug 19 09:19 conventions.html
- }}}
- Note that the files are transferred to the real web site only every few
hours, so it may be a while before you see your changes appear. However if you
set your webbrowser's HTTP proxy to 140.211.11.10 port 80 and access
http://commons.apache.org/ you should be able to see the changes immediately.
= Send announcement =
Announce the availability of the new release. Please check that the mirrors
have been updated with the new release before sending the announce. There is no
need to check all mirrors, but it's worthwhile checking a few of them.
@@ -404, +389 @@
The actual release task is now complete, however there are some remaining
steps to do some cleanup and to prepare the next development iteration.
* '''Remove Obsolete Releases''': Unless old versions are especially
required, remove them from the dist directory. This will cause the files to
also be deleted from the mirrors and save them some diskspace as well as
simplifying things for users. Note that the contents of the
/www/www.apache.org/dist directory is regularly copied to
/www/archive.apache.org/dist and from there transferred to host
archive.apache.org. Deleting files from the standard distribution directories
does ''not'' delete them from the archive dist directories so users will still
be able to access old files even when they are not available from the mirrors.
- * '''Update JIRA''': Mark the release as released in the JIRA project admin
and CLOSE all issues RESOLVED in this release. Make sure the FIX VERSION for
all issues closed with this release is set correctly to this version. If this
has not already been done, create a JIRA version for the next release.
+ * '''Update JIRA''': Mark the release as released in the JIRA project admin
and CLOSE all issues RESOLVED in this release. Make sure the FIX VERSION for
all
[Commons Wiki] Update of "VfsCapabilitiesMatrix" by BerndEckenfels
Dear Wiki user, You have subscribed to a wiki page or wiki category on "Commons Wiki" for change notification. The "VfsCapabilitiesMatrix" page has been changed by BerndEckenfels: https://wiki.apache.org/commons/VfsCapabilitiesMatrix?action=diff&rev1=2&rev2=3 Comment: VFS2 declares setLastModified for SMB ||fsAttributes|| || || || ||x|| || || || || || || || || ||signing|| || || || ||x|| || || || || || || || || ||manifestAttributes|| || || || ||x|| || || || || || || || || - ||setLastModifiedFile|| || || || || ||x||x|| ||x|| || ||x|| || + ||setLastModifiedFile|| || || || || ||x||x|| ||x||x|| ||x|| || - ||setLastModifiedFolder|| || || || || ||x||x|| || || || ||x|| || + ||setLastModifiedFolder|| || || || || ||x||x|| || ||x|| ||x|| || ||dispatcher|| || || || || || || ||x|| || || || || || - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
[Commons Wiki] Update of "CompressRoadmap" by StefanBodewig
Dear Wiki user, You have subscribed to a wiki page or wiki category on "Commons Wiki" for change notification. The "CompressRoadmap" page has been changed by StefanBodewig: https://wiki.apache.org/commons/CompressRoadmap?action=diff&rev1=18&rev2=19 The idea of a 2.0 release that is allowed to break backwards compatibility has come up more than once over a span of three years or even longer. This page will gather requirements and design ideas in the hope that a real implementation will be created based on the existing code. + A starting ground for some design ideas is http://svn.apache.org/repos/asf/commons/proper/compress/branches/compress-2.0/ - nothing carved into stone, yet. Feedback, ideas and corrections more than welcome. + == General == - * do we stick with Java5 or does one of the later versions offer anything that would really benefit Compress? + * SETTLED: Compress 2.0 will require Java7 at compile and run time. - Stefan sees a chance NIO2 will help and is totally sure the "new java.util.zip" of Java7 is even worse than the old code :-) - * external dependencies? we have copied or reinvented some code from IO - do we want to keep our copy or use a dependency? - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
[Commons Wiki] Update of "CompressRoadmap" by StefanBodewig
Dear Wiki user, You have subscribed to a wiki page or wiki category on "Commons Wiki" for change notification. The "CompressRoadmap" page has been changed by StefanBodewig: https://wiki.apache.org/commons/CompressRoadmap?action=diff&rev1=17&rev2=18 This might be used for progress bars or similar stuff at a higher level. COMPRESS-207 + * a common solution for things that are extensible inside a given format like an API that allows third parties to implement und use compression/encryption methods without modifying Compress' codebase. + + This is COMPRESS-143 for ZIP but also applies to 7z or for extra fields inside the ZIP format. + == Archivers == * unify common stuff in ArchiveEntry @@ -60, +64 @@ === ZIP === - * try to share more code between ZipFile and InputStream + * try to share more code between ZipFile and InputStream - - * provide an API that allows third parties to implement und use compression/encryption methods without modifying Compress' codebase. - - COMPRESS-143 == Compressors == - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
[Commons Wiki] Update of "CompressRoadmap" by StefanBodewig
Dear Wiki user, You have subscribed to a wiki page or wiki category on "Commons Wiki" for change notification. The "CompressRoadmap" page has been changed by StefanBodewig: https://wiki.apache.org/commons/CompressRoadmap?action=diff&rev1=16&rev2=17 Comment: ebourg's addition * some general cleanup we have encoding code in the zip packages that gets used in tar and other archived classes. We should make a run for extracting common code into utilities. + + Some names could be better like the constants in ZipMethod. * make the factories configurable - i.e. allow third parties to register new formats without changing Compress - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
[Commons Wiki] Update of "CompressImplementationDetails" by sebbapache
Dear Wiki user, You have subscribed to a wiki page or wiki category on "Commons Wiki" for change notification. The "CompressImplementationDetails" page has been changed by sebbapache: https://wiki.apache.org/commons/CompressImplementationDetails?action=diff&rev1=5&rev2=6 ##language:en - '''This page is obsplete and kept for its historical value''' + '''This page is obsolete and kept for its historical value''' = Compress Implementation Details = - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
[Commons Wiki] Update of "CompressRoadmap" by StefanBodewig
Dear Wiki user,
You have subscribed to a wiki page or wiki category on "Commons Wiki" for
change notification.
The "CompressRoadmap" page has been changed by StefanBodewig:
https://wiki.apache.org/commons/CompressRoadmap?action=diff&rev1=15&rev2=16
== About this page ==
- Compress has seen several releases of the 1.x series. While the factory and
stream APIs have proven to be useful there pieces that "don't feel right" and
cannot be changed without breaking backwards compatibility. Also Compress API
has been designed for Java 1.4 and could benefit from generics and enums.
+ Compress has seen several releases of the 1.x series. While the factory and
stream APIs have proven to be useful there are pieces that "don't feel right"
and cannot be changed without breaking backwards compatibility. Also Compress'
API has been designed for Java 1.4 and could benefit from generics and enums.
The idea of a 2.0 release that is allowed to break backwards compatibility
has come up more than once over a span of three years or even longer. This
page will gather requirements and design ideas in the hope that a real
implementation will be created based on the existing code.
@@ -16, +16 @@
Stefan sees a chance NIO2 will help and is totally sure the "new
java.util.zip" of Java7 is even worse than the old code :-)
+ * external dependencies?
+
+ we have copied or reinvented some code from IO - do we want to keep our
copy or use a dependency?
+
+ * some general cleanup
+
+ we have encoding code in the zip packages that gets used in tar and other
archived classes. We should make a run for extracting common code into
utilities.
+
+ * make the factories configurable - i.e. allow third parties to register new
formats without changing Compress
+
+ ServiceProvider?
+
+ * common solutions for streaming
+
+ pack200 has to use a temporary files or hold the result in memory as it
uses an API that converts a stream with a single call. The archive classes
that need random access can currently only work on files. Some options have
been discussed on the mailing list in this thread:
http://markmail.org/thread/2jr5qapuynnxnfx6
+
+ * read-only support
+
+ The list of formats we ca read but not write seems to be growing. Do we
want to add some sort of meta-data for a format we can query to know whether it
supports writing? Might be part of the "make factories configurable" solution.
+
+ * events for certain stages of (un)archiving/(un)compressing?
+
+ This might be used for progress bars or similar stuff at a higher level.
COMPRESS-207
+
+ == Archivers ==
+
+ * unify common stuff in ArchiveEntry
+
+ this includes extracting a common representation for modes/persmission
(COMPRESS-136) but doesn't need to stop there. There is a discussion thread
that is more than three years old with ideas about this:
http://markmail.org/thread/fsxtzs3vsepycu25
+
+ * embrace generics at least for the {{{getNextEntry}}}/{{{putArchiveEntry}}}
methods
+
+ * streaming vs random-access
+
+ For some archivers we don't have streams as their formats really require
random access to work properly (7z) for others there is a stream and a diferent
class for random access (zip) which is superior. Should we generalize this in
some way like having a factory and a common API for the random access based
classes? See also the "general" bullet point on this.
+
+ === JAR ===
+
+ * stop extending the zip stuff but do something useful for JAR archives like
providing access to the manifest. COMPRESS-18
+
+ === ZIP ===
+
+ * try to share more code between ZipFile and InputStream
+
+ * provide an API that allows third parties to implement und use
compression/encryption methods without modifying Compress' codebase.
+
+ COMPRESS-143
+
+ == Compressors ==
+
+ * provide byte[] based Compressors/Decompressors as an alternative to streams
+
+ COMPRESS-134
+
...
-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org
[Commons Wiki] Trivial Update of "ComponentPlans" by StefanBodewig
Dear Wiki user, You have subscribed to a wiki page or wiki category on "Commons Wiki" for change notification. The "ComponentPlans" page has been changed by StefanBodewig: https://wiki.apache.org/commons/ComponentPlans?action=diff&rev1=13&rev2=14 Comment: typo * codec * collections - release needed, smaller jar file needed * configuration - release 1.2 - * compress - planning a 2.x API applying lessons leraned over the past four years. See: http://wiki.apache.org/commons/CompressRoadmap + * compress - planning a 2.x API applying lessons learned over the past four years. See: http://wiki.apache.org/commons/CompressRoadmap * daemon * dbcp * dbutils - release 1.1? - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
[Commons Wiki] Update of "CompressRoadmap" by StefanBodewig
Dear Wiki user, You have subscribed to a wiki page or wiki category on "Commons Wiki" for change notification. The "CompressRoadmap" page has been changed by StefanBodewig: https://wiki.apache.org/commons/CompressRoadmap?action=diff&rev1=14&rev2=15 == About this page == - Compress is preparing for a first release 1.0. The following page trys to describe necessary changes before the first release can happen. If there are changes for a later release, they will be added here too. + Compress has seen several releases of the 1.x series. While the factory and stream APIs have proven to be useful there pieces that "don't feel right" and cannot be changed without breaking backwards compatibility. Also Compress API has been designed for Java 1.4 and could benefit from generics and enums. - == Commons Compress 1.0 == + The idea of a 2.0 release that is allowed to break backwards compatibility has come up more than once over a span of three years or even longer. This page will gather requirements and design ideas in the hope that a real implementation will be created based on the existing code. + == General == - * Final checks: Do all fields and methods have most restrictive access modifiers as possible? - * Is the website up to date? - == Commons Compress 1.1 == + * do we stick with Java5 or does one of the later versions offer anything that would really benefit Compress? + + Stefan sees a chance NIO2 will help and is totally sure the "new java.util.zip" of Java7 is even worse than the old code :-) + ... - * COMPRESS-17 TAR formaT unspecified - * COMPRESS-16 unable to extract a TAR file that contains an entry which is 10 GB in size - * COMPRESS-18 JarArchiveEntry does not populate manifestAttributes or certificates - * COMPRESS-36 ZIP64 support (archiving files > 2GB) - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
[Commons Wiki] Trivial Update of "CompressImplementationDetails" by StefanBodewig
Dear Wiki user, You have subscribed to a wiki page or wiki category on "Commons Wiki" for change notification. The "CompressImplementationDetails" page has been changed by StefanBodewig: https://wiki.apache.org/commons/CompressImplementationDetails?action=diff&rev1=4&rev2=5 ##language:en - '''This page is oboslete and kept for its historical value''' + '''This page is obsplete and kept for its historical value''' = Compress Implementation Details = - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
[Commons Wiki] Update of "CompressImplementationDetails" by StefanBodewig
Dear Wiki user, You have subscribed to a wiki page or wiki category on "Commons Wiki" for change notification. The "CompressImplementationDetails" page has been changed by StefanBodewig: https://wiki.apache.org/commons/CompressImplementationDetails?action=diff&rev1=3&rev2=4 ##language:en + + '''This page is oboslete and kept for its historical value''' = Compress Implementation Details = - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
