JDownloader2/jdownloader
1
0
Fork 0
mirror of https://github.com/mirror/jdownloader.git synced 2024-11-23 03:59:51 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

git-svn-id: svn://svn.jdownloader.org/jdownloader/trunk@12545 ebf7c1c2-ba36-0410-9fe8-c592906822b4

Browse Source
This commit is contained in:
Greeny 2010-09-09 10:19:25 +00:00
parent e5a11471c9
commit 965cca8aa8
12 changed files with 4 additions and 3857 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
.classpath
View File

@ -24,7 +24,6 @@
</attributes>
</classpathentry>
<classpathentry kind="lib" path="ressourcen/libs/clink170.jar"/>
<classpathentry kind="lib" path="ressourcen/libs_ext/junit-4.6.jar"/>
<classpathentry kind="lib" path="ressourcen/libs_ext/mail.jar"/>
<classpathentry kind="lib" path="ressourcen/libs_ext/ui.jar"/>
<classpathentry kind="lib" path="ressourcen/libs_ext/debug-1.0.jar"/>
@ -81,5 +80,6 @@
<classpathentry kind="lib" path="ressourcen/libs/jackson-mapper.jar"/>
<classpathentry kind="lib" path="ressourcen/libs/svnkit.jar" sourcepath="ressourcen/code-ressourcen/svnkitsrc.zip"/>
<classpathentry kind="lib" path="ressourcen/libs/laf/trident.jar"/>
<classpathentry kind="lib" path="ressourcen/libs_ext/junit-4.8.2.jar" sourcepath="ressourcen/code-ressourcen/junit-4.8.2-src.jar"/>
<classpathentry kind="output" path="bin"/>
</classpath>

29
build/yguard-2.2.0/3rdPartyLicenses/asm-license.txt
View File

@ -1,29 +0,0 @@
Copyright (c) 2000-2005 INRIA, France Telecom
All rights reserved.
Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions
are met:
1. Redistributions of source code must retain the above copyright
notice, this list of conditions and the following disclaimer.
2. Redistributions in binary form must reproduce the above copyright
notice, this list of conditions and the following disclaimer in the
documentation and/or other materials provided with the distribution.
3. Neither the name of the copyright holders nor the names of its
contributors may be used to endorse or promote products derived from
this software without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS"
AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE
LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF
THE POSSIBILITY OF SUCH DAMAGE.

510
build/yguard-2.2.0/3rdPartyLicenses/retroguard-LGPL.txt
View File

@ -1,510 +0,0 @@
This license applies to all yGuard library files, which reside in the
com.yworks.yguard.obf and com.yworks.yguard.obf.classfile packages as well as the
classes Conversion, ObfuscationListener and ParseException which reside in the com.yworks.yguard
package.
GNU LESSER GENERAL PUBLIC LICENSE
Version 2.1, February 1999
Copyright (C) 1991, 1999 Free Software Foundation, Inc.
59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
Everyone is permitted to copy and distribute verbatim copies
of this license document, but changing it is not allowed.
[This is the first released version of the Lesser GPL. It also counts
as the successor of the GNU Library Public License, version 2, hence
the version number 2.1.]
Preamble
The licenses for most software are designed to take away your
freedom to share and change it. By contrast, the GNU General Public
Licenses are intended to guarantee your freedom to share and change
free software--to make sure the software is free for all its users.
This license, the Lesser General Public License, applies to some
specially designated software packages--typically libraries--of the
Free Software Foundation and other authors who decide to use it. You
can use it too, but we suggest you first think carefully about whether
this license or the ordinary General Public License is the better
strategy to use in any particular case, based on the explanations below.
When we speak of free software, we are referring to freedom of use,
not price. Our General Public Licenses are designed to make sure that
you have the freedom to distribute copies of free software (and charge
for this service if you wish); that you receive source code or can get
it if you want it; that you can change the software and use pieces of
it in new free programs; and that you are informed that you can do
these things.
To protect your rights, we need to make restrictions that forbid
distributors to deny you these rights or to ask you to surrender these
rights. These restrictions translate to certain responsibilities for
you if you distribute copies of the library or if you modify it.
For example, if you distribute copies of the library, whether gratis
or for a fee, you must give the recipients all the rights that we gave
you. You must make sure that they, too, receive or can get the source
code. If you link other code with the library, you must provide
complete object files to the recipients, so that they can relink them
with the library after making changes to the library and recompiling
it. And you must show them these terms so they know their rights.
We protect your rights with a two-step method: (1) we copyright the
library, and (2) we offer you this license, which gives you legal
permission to copy, distribute and/or modify the library.
To protect each distributor, we want to make it very clear that
there is no warranty for the free library. Also, if the library is
modified by someone else and passed on, the recipients should know
that what they have is not the original version, so that the original
author's reputation will not be affected by problems that might be
introduced by others.
Finally, software patents pose a constant threat to the existence of
any free program. We wish to make sure that a company cannot
effectively restrict the users of a free program by obtaining a
restrictive license from a patent holder. Therefore, we insist that
any patent license obtained for a version of the library must be
consistent with the full freedom of use specified in this license.
Most GNU software, including some libraries, is covered by the
ordinary GNU General Public License. This license, the GNU Lesser
General Public License, applies to certain designated libraries, and
is quite different from the ordinary General Public License. We use
this license for certain libraries in order to permit linking those
libraries into non-free programs.
When a program is linked with a library, whether statically or using
a shared library, the combination of the two is legally speaking a
combined work, a derivative of the original library. The ordinary
General Public License therefore permits such linking only if the
entire combination fits its criteria of freedom. The Lesser General
Public License permits more lax criteria for linking other code with
the library.
We call this license the "Lesser" General Public License because it
does Less to protect the user's freedom than the ordinary General
Public License. It also provides other free software developers Less
of an advantage over competing non-free programs. These disadvantages
are the reason we use the ordinary General Public License for many
libraries. However, the Lesser license provides advantages in certain
special circumstances.
For example, on rare occasions, there may be a special need to
encourage the widest possible use of a certain library, so that it becomes
a de-facto standard. To achieve this, non-free programs must be
allowed to use the library. A more frequent case is that a free
library does the same job as widely used non-free libraries. In this
case, there is little to gain by limiting the free library to free
software only, so we use the Lesser General Public License.
In other cases, permission to use a particular library in non-free
programs enables a greater number of people to use a large body of
free software. For example, permission to use the GNU C Library in
non-free programs enables many more people to use the whole GNU
operating system, as well as its variant, the GNU/Linux operating
system.
Although the Lesser General Public License is Less protective of the
users' freedom, it does ensure that the user of a program that is
linked with the Library has the freedom and the wherewithal to run
that program using a modified version of the Library.
The precise terms and conditions for copying, distribution and
modification follow. Pay close attention to the difference between a
"work based on the library" and a "work that uses the library". The
former contains code derived from the library, whereas the latter must
be combined with the library in order to run.
GNU LESSER GENERAL PUBLIC LICENSE
TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
0. This License Agreement applies to any software library or other
program which contains a notice placed by the copyright holder or
other authorized party saying it may be distributed under the terms of
this Lesser General Public License (also called "this License").
Each licensee is addressed as "you".
A "library" means a collection of software functions and/or data
prepared so as to be conveniently linked with application programs
(which use some of those functions and data) to form executables.
The "Library", below, refers to any such software library or work
which has been distributed under these terms. A "work based on the
Library" means either the Library or any derivative work under
copyright law: that is to say, a work containing the Library or a
portion of it, either verbatim or with modifications and/or translated
straightforwardly into another language. (Hereinafter, translation is
included without limitation in the term "modification".)
"Source code" for a work means the preferred form of the work for
making modifications to it. For a library, complete source code means
all the source code for all modules it contains, plus any associated
interface definition files, plus the scripts used to control compilation
and installation of the library.
Activities other than copying, distribution and modification are not
covered by this License; they are outside its scope. The act of
running a program using the Library is not restricted, and output from
such a program is covered only if its contents constitute a work based
on the Library (independent of the use of the Library in a tool for
writing it). Whether that is true depends on what the Library does
and what the program that uses the Library does.
1. You may copy and distribute verbatim copies of the Library's
complete source code as you receive it, in any medium, provided that
you conspicuously and appropriately publish on each copy an
appropriate copyright notice and disclaimer of warranty; keep intact
all the notices that refer to this License and to the absence of any
warranty; and distribute a copy of this License along with the
Library.
You may charge a fee for the physical act of transferring a copy,
and you may at your option offer warranty protection in exchange for a
fee.
2. You may modify your copy or copies of the Library or any portion
of it, thus forming a work based on the Library, and copy and
distribute such modifications or work under the terms of Section 1
above, provided that you also meet all of these conditions:
a) The modified work must itself be a software library.
b) You must cause the files modified to carry prominent notices
stating that you changed the files and the date of any change.
c) You must cause the whole of the work to be licensed at no
charge to all third parties under the terms of this License.
d) If a facility in the modified Library refers to a function or a
table of data to be supplied by an application program that uses
the facility, other than as an argument passed when the facility
is invoked, then you must make a good faith effort to ensure that,
in the event an application does not supply such function or
table, the facility still operates, and performs whatever part of
its purpose remains meaningful.
(For example, a function in a library to compute square roots has
a purpose that is entirely well-defined independent of the
application. Therefore, Subsection 2d requires that any
application-supplied function or table used by this function must
be optional: if the application does not supply it, the square
root function must still compute square roots.)
These requirements apply to the modified work as a whole. If
identifiable sections of that work are not derived from the Library,
and can be reasonably considered independent and separate works in
themselves, then this License, and its terms, do not apply to those
sections when you distribute them as separate works. But when you
distribute the same sections as part of a whole which is a work based
on the Library, the distribution of the whole must be on the terms of
this License, whose permissions for other licensees extend to the
entire whole, and thus to each and every part regardless of who wrote
it.
Thus, it is not the intent of this section to claim rights or contest
your rights to work written entirely by you; rather, the intent is to
exercise the right to control the distribution of derivative or
collective works based on the Library.
In addition, mere aggregation of another work not based on the Library
with the Library (or with a work based on the Library) on a volume of
a storage or distribution medium does not bring the other work under
the scope of this License.
3. You may opt to apply the terms of the ordinary GNU General Public
License instead of this License to a given copy of the Library. To do
this, you must alter all the notices that refer to this License, so
that they refer to the ordinary GNU General Public License, version 2,
instead of to this License. (If a newer version than version 2 of the
ordinary GNU General Public License has appeared, then you can specify
that version instead if you wish.) Do not make any other change in
these notices.
Once this change is made in a given copy, it is irreversible for
that copy, so the ordinary GNU General Public License applies to all
subsequent copies and derivative works made from that copy.
This option is useful when you wish to copy part of the code of
the Library into a program that is not a library.
4. You may copy and distribute the Library (or a portion or
derivative of it, under Section 2) in object code or executable form
under the terms of Sections 1 and 2 above provided that you accompany
it with the complete corresponding machine-readable source code, which
must be distributed under the terms of Sections 1 and 2 above on a
medium customarily used for software interchange.
If distribution of object code is made by offering access to copy
from a designated place, then offering equivalent access to copy the
source code from the same place satisfies the requirement to
distribute the source code, even though third parties are not
compelled to copy the source along with the object code.
5. A program that contains no derivative of any portion of the
Library, but is designed to work with the Library by being compiled or
linked with it, is called a "work that uses the Library". Such a
work, in isolation, is not a derivative work of the Library, and
therefore falls outside the scope of this License.
However, linking a "work that uses the Library" with the Library
creates an executable that is a derivative of the Library (because it
contains portions of the Library), rather than a "work that uses the
library". The executable is therefore covered by this License.
Section 6 states terms for distribution of such executables.
When a "work that uses the Library" uses material from a header file
that is part of the Library, the object code for the work may be a
derivative work of the Library even though the source code is not.
Whether this is true is especially significant if the work can be
linked without the Library, or if the work is itself a library. The
threshold for this to be true is not precisely defined by law.
If such an object file uses only numerical parameters, data
structure layouts and accessors, and small macros and small inline
functions (ten lines or less in length), then the use of the object
file is unrestricted, regardless of whether it is legally a derivative
work. (Executables containing this object code plus portions of the
Library will still fall under Section 6.)
Otherwise, if the work is a derivative of the Library, you may
distribute the object code for the work under the terms of Section 6.
Any executables containing that work also fall under Section 6,
whether or not they are linked directly with the Library itself.
6. As an exception to the Sections above, you may also combine or
link a "work that uses the Library" with the Library to produce a
work containing portions of the Library, and distribute that work
under terms of your choice, provided that the terms permit
modification of the work for the customer's own use and reverse
engineering for debugging such modifications.
You must give prominent notice with each copy of the work that the
Library is used in it and that the Library and its use are covered by
this License. You must supply a copy of this License. If the work
during execution displays copyright notices, you must include the
copyright notice for the Library among them, as well as a reference
directing the user to the copy of this License. Also, you must do one
of these things:
a) Accompany the work with the complete corresponding
machine-readable source code for the Library including whatever
changes were used in the work (which must be distributed under
Sections 1 and 2 above); and, if the work is an executable linked
with the Library, with the complete machine-readable "work that
uses the Library", as object code and/or source code, so that the
user can modify the Library and then relink to produce a modified
executable containing the modified Library. (It is understood
that the user who changes the contents of definitions files in the
Library will not necessarily be able to recompile the application
to use the modified definitions.)
b) Use a suitable shared library mechanism for linking with the
Library. A suitable mechanism is one that (1) uses at run time a
copy of the library already present on the user's computer system,
rather than copying library functions into the executable, and (2)
will operate properly with a modified version of the library, if
the user installs one, as long as the modified version is
interface-compatible with the version that the work was made with.
c) Accompany the work with a written offer, valid for at
least three years, to give the same user the materials
specified in Subsection 6a, above, for a charge no more
than the cost of performing this distribution.
d) If distribution of the work is made by offering access to copy
from a designated place, offer equivalent access to copy the above
specified materials from the same place.
e) Verify that the user has already received a copy of these
materials or that you have already sent this user a copy.
For an executable, the required form of the "work that uses the
Library" must include any data and utility programs needed for
reproducing the executable from it. However, as a special exception,
the materials to be distributed need not include anything that is
normally distributed (in either source or binary form) with the major
components (compiler, kernel, and so on) of the operating system on
which the executable runs, unless that component itself accompanies
the executable.
It may happen that this requirement contradicts the license
restrictions of other proprietary libraries that do not normally
accompany the operating system. Such a contradiction means you cannot
use both them and the Library together in an executable that you
distribute.
7. You may place library facilities that are a work based on the
Library side-by-side in a single library together with other library
facilities not covered by this License, and distribute such a combined
library, provided that the separate distribution of the work based on
the Library and of the other library facilities is otherwise
permitted, and provided that you do these two things:
a) Accompany the combined library with a copy of the same work
based on the Library, uncombined with any other library
facilities. This must be distributed under the terms of the
Sections above.
b) Give prominent notice with the combined library of the fact
that part of it is a work based on the Library, and explaining
where to find the accompanying uncombined form of the same work.
8. You may not copy, modify, sublicense, link with, or distribute
the Library except as expressly provided under this License. Any
attempt otherwise to copy, modify, sublicense, link with, or
distribute the Library is void, and will automatically terminate your
rights under this License. However, parties who have received copies,
or rights, from you under this License will not have their licenses
terminated so long as such parties remain in full compliance.
9. You are not required to accept this License, since you have not
signed it. However, nothing else grants you permission to modify or
distribute the Library or its derivative works. These actions are
prohibited by law if you do not accept this License. Therefore, by
modifying or distributing the Library (or any work based on the
Library), you indicate your acceptance of this License to do so, and
all its terms and conditions for copying, distributing or modifying
the Library or works based on it.
10. Each time you redistribute the Library (or any work based on the
Library), the recipient automatically receives a license from the
original licensor to copy, distribute, link with or modify the Library
subject to these terms and conditions. You may not impose any further
restrictions on the recipients' exercise of the rights granted herein.
You are not responsible for enforcing compliance by third parties with
this License.
11. If, as a consequence of a court judgment or allegation of patent
infringement or for any other reason (not limited to patent issues),
conditions are imposed on you (whether by court order, agreement or
otherwise) that contradict the conditions of this License, they do not
excuse you from the conditions of this License. If you cannot
distribute so as to satisfy simultaneously your obligations under this
License and any other pertinent obligations, then as a consequence you
may not distribute the Library at all. For example, if a patent
license would not permit royalty-free redistribution of the Library by
all those who receive copies directly or indirectly through you, then
the only way you could satisfy both it and this License would be to
refrain entirely from distribution of the Library.
If any portion of this section is held invalid or unenforceable under any
particular circumstance, the balance of the section is intended to apply,
and the section as a whole is intended to apply in other circumstances.
It is not the purpose of this section to induce you to infringe any
patents or other property right claims or to contest validity of any
such claims; this section has the sole purpose of protecting the
integrity of the free software distribution system which is
implemented by public license practices. Many people have made
generous contributions to the wide range of software distributed
through that system in reliance on consistent application of that
system; it is up to the author/donor to decide if he or she is willing
to distribute software through any other system and a licensee cannot
impose that choice.
This section is intended to make thoroughly clear what is believed to
be a consequence of the rest of this License.
12. If the distribution and/or use of the Library is restricted in
certain countries either by patents or by copyrighted interfaces, the
original copyright holder who places the Library under this License may add
an explicit geographical distribution limitation excluding those countries,
so that distribution is permitted only in or among countries not thus
excluded. In such case, this License incorporates the limitation as if
written in the body of this License.
13. The Free Software Foundation may publish revised and/or new
versions of the Lesser General Public License from time to time.
Such new versions will be similar in spirit to the present version,
but may differ in detail to address new problems or concerns.
Each version is given a distinguishing version number. If the Library
specifies a version number of this License which applies to it and
"any later version", you have the option of following the terms and
conditions either of that version or of any later version published by
the Free Software Foundation. If the Library does not specify a
license version number, you may choose any version ever published by
the Free Software Foundation.
14. If you wish to incorporate parts of the Library into other free
programs whose distribution conditions are incompatible with these,
write to the author to ask for permission. For software which is
copyrighted by the Free Software Foundation, write to the Free
Software Foundation; we sometimes make exceptions for this. Our
decision will be guided by the two goals of preserving the free status
of all derivatives of our free software and of promoting the sharing
and reuse of software generally.
NO WARRANTY
15. BECAUSE THE LIBRARY IS LICENSED FREE OF CHARGE, THERE IS NO
WARRANTY FOR THE LIBRARY, TO THE EXTENT PERMITTED BY APPLICABLE LAW.
EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR
OTHER PARTIES PROVIDE THE LIBRARY "AS IS" WITHOUT WARRANTY OF ANY
KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE
IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE
LIBRARY IS WITH YOU. SHOULD THE LIBRARY PROVE DEFECTIVE, YOU ASSUME
THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
16. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN
WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY
AND/OR REDISTRIBUTE THE LIBRARY AS PERMITTED ABOVE, BE LIABLE TO YOU
FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR
CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE
LIBRARY (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING
RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A
FAILURE OF THE LIBRARY TO OPERATE WITH ANY OTHER SOFTWARE), EVEN IF
SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH
DAMAGES.
END OF TERMS AND CONDITIONS
How to Apply These Terms to Your New Libraries
If you develop a new library, and you want it to be of the greatest
possible use to the public, we recommend making it free software that
everyone can redistribute and change. You can do so by permitting
redistribution under these terms (or, alternatively, under the terms of the
ordinary General Public License).
To apply these terms, attach the following notices to the library. It is
safest to attach them to the start of each source file to most effectively
convey the exclusion of warranty; and each file should have at least the
"copyright" line and a pointer to where the full notice is found.
<one line to give the library's name and a brief idea of what it does.>
Copyright (C) <year> <name of author>
This library is free software; you can redistribute it and/or
modify it under the terms of the GNU Lesser General Public
License as published by the Free Software Foundation; either
version 2 of the License, or (at your option) any later version.
This library is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
Lesser General Public License for more details.
You should have received a copy of the GNU Lesser General Public
License along with this library; if not, write to the Free Software
Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
Also add information on how to contact you by electronic and paper mail.
You should also get your employer (if you work as a programmer) or your
school, if any, to sign a "copyright disclaimer" for the library, if
necessary. Here is a sample; alter the names:
Yoyodyne, Inc., hereby disclaims all copyright interest in the
library `Frob' (a library for tweaking knobs) written by James Random Hacker.
<signature of Ty Coon>, 1 April 1990
Ty Coon, President of Vice
That's all there is to it!

30
build/yguard-2.2.0/3rdPartyLicenses/retrotranslator-license.txt
View File

@ -1,30 +0,0 @@
Retrotranslator: a Java bytecode transformer that translates Java classes
compiled with JDK 5.0 into classes that can be run on JVM 1.4.
Copyright (c) 2005, 2006 Taras Puchko
All rights reserved.
Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions
are met:
1. Redistributions of source code must retain the above copyright
notice, this list of conditions and the following disclaimer.
2. Redistributions in binary form must reproduce the above copyright
notice, this list of conditions and the following disclaimer in the
documentation and/or other materials provided with the distribution.
3. Neither the name of the copyright holders nor the names of its
contributors may be used to endorse or promote products derived from
this software without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS"
AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE
LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF
THE POSSIBILITY OF SUCH DAMAGE

82
build/yguard-2.2.0/LICENSE.html
View File

@ -1,82 +0,0 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
</head>
<body>
<pre>
yGuard Software License Agreement,
version 1.0, October 2002
This is a legal agreement ("this Agreement") between yWorks GmbH ("yWorks") and the licensee ("the Licensee").
This Agreement is governed by the laws of Germany.
yWorks licenses the yGuard software ("the Software") only if all the following
terms are accepted by the Licensee. The Software includes the yGuard bytecode
executable and any files and documents associated with it.
By installing the Software, the Licensee is indicating that the Licensee has read and
understands this Agreement and agrees to be bound by its terms and conditions.
If this Agreement is unacceptable to the Licensee, the Licensee must destroy any copies of the
Software in the Licensee's possession immediately.
1. LICENSE CONDITIONS
The Licensee is granted a non-exclusive and non-transferable license to install the Software.
Any copies of the Software should be complete copies including any copyright notices.
The Licensee may not reverse engineer, disassemble, decompile, alter, or translate the
Software, or otherwise attempt to derive the source code of the Software.
The Licensee acknowledges that Software furnished hereunder is under test and may be
defective.
No claims whatsoever can be made on yWorks based on any expectation about the Software.
2. TERM, TERMINATION AND SURVIVAL
(A) This Agreement is effective unless terminated as follows:
(B) The Licensee may terminate this Agreement at any time by destroying all copies of the
Software in possession.
(C) If the Licensee fails to comply with any term of this Agreement, this Agreement is
terminated and the Licensee has no further right to use the Software.
(E) On termination, the Licensee shall have no claim on or arising from the Software. The
Software and any copies shall be destroyed.
3. NO WARRANTY
The Software is licensed to the Licensee on an "AS IS" basis.
The Licensee is solely responsible for determining the suitability of the Software and
accepts full responsibility and risks associated with the use of the Software.
4. MAINTENANCE AND SUPPORT
yWorks is not required to provide maintenance or support to the Licensee.
5. LIMITATION OF LIABILITY
In no event will yWorks be liable for any damages, including but not limited to any loss
of revenue, profit, or data, however caused, directly or indirectly, by the Software or by
this Agreement.
6. DISTRIBUTION
No distribution is to be made of the Software by the Licensee. The Licensee may make one
copy of the Software for backup purpose only.
7. AVAILABILITY
The Software is not available to those not permitted by laws to have access to the Software.
8. INSERTION OF MARKER
The Software may insert markers into output files to identify
that the files have been generated by the Software. yWorks bears no responsibility
for any damages arising.
</pre>
</body>
</html>

480
build/yguard-2.2.0/README.html
View File

@ -1,480 +0,0 @@
<html>
<head>
<title>yGuard 2.2.0 Release Notes</title>
<style type="text/css">
<!--
body {
font-family:Arial, Helvetica, sans-serif;
text-align:justify;
}
code {
color:#0000C0;
}
ul {
list-style:disc;
margin-top:0%;
margin-bottom:0%;
}
ol {
list-style:decimal;
}
p {
margin-left:2em;
}
h1 {
background-color:Black;
color:White;
text-align:center;
}
h2 {
margin-top:100;
border-top-width:0;
border-left-width:0;
border-bottom-width:2;
border-right-width:0;
border-color:Black;
border-style:solid;
}
h3 {
margin-top:50;
border-top-width:0;
border-left-width:0;
border-bottom-width:2;
border-right-width:0;
border-color:Black;
border-style:solid;
}
h4 {
}
//-->
</style>
</head>
<body bgcolor="#f0f0f0">
<h1>yGuard 2.2.0 Release Notes</h1>
<h2>Contents</h2>
<p>
<table border="0" cellspacing="0" cellpadding="5">
<tr>
<td valign="top">LICENSE.html</td>
<td><a href="LICENSE.html">yGuard Software License</a></td>
</tr>
<tr>
<td valign="top">3rdPartyLicenses/</td>
<td>3rd Party Licenses:
<ul compact>
<li><a href="3rdPartyLicenses/retroguard-LGPL.txt">LGPL</a> (Retroguard)<br></li>
<li><a href="3rdPartyLicenses/retrotranslator-license.txt">Retrotranslator</a></li>
<li><a href="3rdPartyLicenses/asm-license.txt">ASM</a></li>
</ul></td>
</tr>
<tr>
<td valign="top">README.html</td>
<td>this file</td>
</tr>
<tr>
<td valign="top">doc/</td>
<td>documentation:
<ul compact>
<li><a href="doc/yguard_ant_howto.html">yGuard Ant Task documentation</a></li>
</ul></td>
</tr>
<tr>
<td valign="top">lib/</td>
<td>ant task library:
<ul compact>
<li>yguard.jar</li>
</ul></td>
</tr>
</table>
</p>
<p>Please read the documentation for
<a href="doc/yguard_ant_howto.html#installation">installation instructions</a>.</p>
<h2>Technical requirements</h2>
<p>yGuard requires Java2 SDK 1.4.x or greater and Ant 1.5 or greater installed on your system.
It may work with earlier versions of these pieces of software as well, however this has not
been tested thoroughly. yGuard 1.3.x and upwards works together with Ant 1.6.
yGuard works well with JDK 1.6 and Ant 1.7.</p>
<p></p>
<h2>yGuard 2.2.0 - Changes since 2.1.0</h2>
<p>
<ul>
<li>yGuard is now fully JDK-1.6 compatible.</li>
<li>The yGuard task now supports a way of specifying a set of jars that should be obfuscated at the same time
using simple patternset syntax.</li>
<li>yGuard now uses the same technique for all elements in the MANIFEST file to adjust fully qualified class name strings.</li>
<li>It is now possible to tell yGuard not to obfuscate specific package names.</li>
<li>yGuard can now be given a list of digest algorithms that will be used to create the digests in the manifest.</li>
<li>yGuard now issues a warning if the package or class or method name of a native method is obfuscated.</li>
</ul>
</p>
<h2>yGuard 2.1.0 - Changes since 2.0.3</h2>
<p>
<ul>
<li>Fixed a bug that caused yGuard to throw a NullPointerException if a <code>attribute</code> element contained no nested <code>patternset</code>.<li>
<li>Fixed a bug that caused yGuard to use multiple logging instances if a yGuard task was executed multiple times.</li>
<li>Fixed LineNumberTable and SourceFile elements</li>
<li>Added overloadEnabled property</li>
</ul>
</p>
<h2>yGuard 2.0.3 - Changes since 2.0.2</h2>
<p>
<ul>
<li>Fixed a bug that broke the nested <code>map</code> element of the <code>rename</code> element.</li>
</ul>
</p>
<h2>yGuard 2.0.2 - Changes since 2.0.1</h2>
<p>
<ul>
<li>Fixed a bug that caused yGuard to fail during class file parsing if a method signature contained an inner class of a parameterized class.</li>
<li>yGuard will not complain about the Java 1.5 attributes <code>Bridge</code>, <code>Enum</code> and <code>Varargs</code> as 'unknown attributes' anymore.</li>
<li>Fixed a bug that caused all classnames to be kept from renaming if the <code>extends</code> attribute was used in combination with the <code>classes</code> attribute.</li>
</ul>
</p>
<h2>yGuard 2.0.1 - Changes since 2.0</h2>
<p>
<ul>
<li>Fixed an inconsistency between the interpretation of the Ant syntax in the <code>rename</code> and <code>shrink</code> elements. Now, both elements apply <code>patternset</code> elements in nested <code>method</code> and <code>field</code> elements to class names, just as stated in the yGuard documentation.</li>
<li>If the <code>classes</code> attribute of the <code>class</code> element is not set or set to &quot;none&quot;, the shrinking engine will now include the classes that match based on the given <code>name</code> attribute or nested <code>patternset</code>, effectively ignoring the <code>classes</code> attribute.</li>
</ul>
</p>
<h2>yGuard 2.0 - Changes since 1.5.0_03</h2>
<p>
<ul>
<li>New elaborate code shrinking functionality.</li>
<li>More powerful ant syntax: <code>extends</code>/<code>implements</code> attributes for the <code>class</code> element.</li>
<li>General Ant syntax changes due to the introduction of the new <code>yguard</code>,<code>shrink</code> and <code>rename</code> elements.</li>
<li>yGuard now needs Java2 SDK 1.4.x or greater to function properly.</li>
</ul>
</p>
<h2>yGuard 1.5.0_03 - Changes since 1.5.0_02</h2>
<p>
<ul>
<li>
Fixed bad treatment of the new enclosing method feature in Tiger which sometimes led to AbstractMethodErrors at runtime.
</li>
</ul>
</p>
<h2>yGuard 1.5.0_02 - Changes since 1.5.0_01</h2>
<p>
<ul>
<li>
Improved obfuscation logic for enumerations. Now the two static methods valueOf(String) and values() don't have to be exposed manually anymore.
</li>
<li>
Fixed bad annotation handling for non-trivial annotations. Annotations had not been parsed and handled correctly, which could lead to either
errors during obfuscation or Errors at runtime.
</li>
</ul>
</p>
<h2>yGuard 1.5.0_01 - Changes since 1.5</h2>
<p>
<ul>
<li>
Fixed a bug that made yGuard ignore some of the attributes in the expose section ("sourcefile" and "linenumbertable").
</li>
<li>
Fixed a rare but severe bug that accidentally removed method attributes and sometimes led to ArrayIndexOutOfBoundsExceptions
during the obfuscation.
</li>
</ul>
</p>
<h2>yGuard 1.5 - Changes since 1.3.2</h2>
<p>
<ul>
<li>
Added JDK 1.5 (a.k.a Java 5.0 code-named Tiger) compatibility. yGuard can now deal correctly with the
new JDK and Java features: generics, var-args, enumerations, annotations, new "<code>.class</code>" bytecode construct,
signatures, local variable type table, enclosing method information.
</li>
<li>
Implemented the ability to obfuscate/scramble/shrink line number information. This makes it possible to more easily debug
stacktraces without exposing line number information in the obfuscated version of the application.
</li>
<li>
Implemented the ability to obfuscate the source file information. This is necessary in order to view line number information
in stack traces. It is now possible to reassign the source file attribute inside class files so that the original source file
name is not exposed in the obfuscated application.
</li>
<li>
Added the ability to determine on a per-class basis what attributes to expose or obfuscate. This includes line number
information (with optional scrambling/compression or removal), source file attributes, deprecation attributes, etc.
This makes it easy to obfuscate parts of your application while keeping the public API untouched and debug information
for third party jars intact.
</li>
<li>
Improved the stacktrace deobfuscation tool. It can now unscramble line number information from stacktraces, features a
more polished view of the mapping rules and deobfuscates stacktraces more reliably if the stacktraces are ambiguous.
</li>
</ul>
</p>
<h2>yGuard 1.3.2 - Changes since 1.3.1_01</h2>
<p>
<ul>
<li>
Improved name generation. yGuard will now generate legal identifiers
(with respect to <code>Character.isJavaIdentifierStart()</code>
and <code>Character.isJavaIdentifierPart(char)</code> and
<code>Character.isIdentifierIgnorable(char)</code>) and should
therefor produce jars that should verify correctly even on older jdks
if yGuard is run using newer jdks.
</li>
<li>
yGuard now helps in the detection of duplicate class files in source jars.
In pedantic mode yGuard will terminate if duplicate classes are detected
in different source jars. yGuard's obfuscate task will always fail if mutliple
class files containing a definition for the same jar are detected. The log file
displays useful information for finding the duplicate entries.
</li>
<li>
Improved xml log file output for Unicode characters.
</li>
<li>
Made the log file viewer output more consistent with inner class names that
were being mapped during obfuscation versus those who remained fixed.
</li>
<li>
Jar file entries are now being sorted prior to being written to the jar.
</li>
<li>
Improved handling of external classes.
</li>
<li>
Bugfixes:
<ul>
<li>Fixed a name clash problem that occurred when already obfuscated code
was being obfuscated again using different settings.
</li>
<li>
Fixed a resolution problem concerning interfaces from external classpaths.
</li>
</ul>
</li>
</ul>
</p>
<h2>yGuard 1.3.1_01 - Changes since 1.3.1</h2>
<p>
<ul>
<li>
yGuard now treats the COMPATIBLE flag for the language conformity different.
Field names and class names are now made up of lower ascii-only chars.
</li>
<li>
Bugfixes:
<ul>
<li>Fixed a problem concerning the <code>adjust</code> elements throwing
a <code>RuntimeException</code> in the pattern matching code.
</li>
<li>
Fixed a problem where the wrong set of files was affected in the <code>adjust</code>
section.
</li>
</ul>
</li>
</ul>
</p>
<h2>yGuard 1.3.1 - Changes since 1.3</h2>
<p>
<ul>
<li>
yGuard will now generate (empty) directory entries in the resulting jar files for each non-empty directory.
</li>
<li>
Improved the optional keeping of "Deprecated" tags. Somehow they still seem to get lost under certain conditions.
Any feedback on this topic is welcomed.
</li>
<li>
Due to a compile time dependency, yGuard could not be used with jdk 1.3.x anymore even if the automatic
resource adjustment feature was not used. This has now been made possible again.
</li>
<li>
Bugfixes:
<ul>
<li>Fixed a rare problem that broke obfuscated code using static method
invocations and static field references.
</li>
<li>
There was a bug in the log file viewer (<code>java -jar yguard.jar [logfile.xml[.gz]]</code>) that made it crash
under very rare circumstances.
</li>
<li>
Implemented a workaround for an Ant incompatibility problem, which resulted in yGuard behaving differently on
different platforms and in conjunction with different Ant versions.
</li>
</ul>
</li>
</ul>
</p>
<h2>yGuard 1.3 - Changes since 1.2</h2>
<p>
<ul>
<li>
Added automatic text file and property file renaming mechanism. yGuard can
now be configured to rename .properties files according to the obfuscation.
</li>
<li>
It is now possible to process text files and replace occurances
of class names with their obfuscated versions.
</li>
<li>
One can now specify whether resource files should be kept in their original
directory while at the same time the classes residing in the respective
directory can be fully obfuscated to another package.
</li>
<li>
yGuard can now automatically create gzipped (.gz) logfiles and work directly
on compressed logfiles. This reduces the size of the logfiles drastically.
</li>
<li>
It is now possible to simply specify a list of attributes, that should not be
removed by yGuard (for example "<code>Deprecated</code>") using the
<code>expose-attributes</code> property.
</li>
<li>
yGuard has a new name generation method (<code>language-conformity</code> = <code>compatible</code>),
that creates jar file that <b>can</b> be successfully unzipped to the windows
filesystem.
</li>
<li>
In order to avoid namespace clashes, on can now easily specify a prefix
for completeley obfuscated package hierarchies using the <code>obfuscation-prefix</code>
property.
</li>
<li>
Enhanced documentation (DTD, examples, and new features description).
</li>
<li>
Bugfixes:
<ul>
<li>Innerclasses making use of the .class construct should now always be
correctly obfuscated using the replaceClassNameStrings feature.
</li>
<li>
The <code>patch</code> element had a bug concerning field name mappings,
which is now resolved.
</li>
<li>
yGuard now tests whether a newly obfuscated name already exists in external
jars and automatically generates names, that should not clash.
</li>
<li>
yGuard should now work together with Ant version 1.6 (there was an undocumented change in the API of Ant).
</li>
</ul>
</li>
</ul>
</p>
<h2>yGuard 1.2 - Changes since 1.1</h2>
<p>
<ul>
<li>
Added support for external libraries. This allows yGuard to obfuscate
jars that have external dependencies more easily and using stronger
obfuscation. It is now possible to specify dependencies using Ant classpath
elements. yGuard then uses information found in these jars to resolve
external dependencies.
</li>
<li>
Improved error handling and task and logfile output. yGuard will now produce
fewer unreasonable warnings. During the obfuscation run yGuard will give
more detailed warnings and hints when unobfuscatable classes are detected.
</li>
<li>
Added property <code>error-checking</code> which can be set to
<code>pedantic</code>. In this case yGuard will not issue warnings but a
build will fail instead of issueing simple warnings. This helps in finding problems.
</li>
<li>
Fixed a minor issue. The documentation stated, that
<pre>&lt;class classes="protected"/></pre>
behaved like
<pre>&lt;class classes="protected">
&lt;patternset>
&lt;include name="**.*"/>
&lt;/patternset>
&lt;/class></pre>
but in the implementation <code>&lt;include name="*"/></code>
had been applied. This has now been fixed to <code>&lt;include
name="**.*"/></code>.
</li>
<li>
Fixed some bugs in the documentation.
</li>
</ul>
</p>
<h2>yGuard 1.1 - Changes since 1.0.1</h2>
<p>
<ul>
<li>
Added support for different naming schemes. These schemes result in smaller
jar files, better obfuscation and lead to jar files,
which cannot be unpacked to normal filesystems.
</li>
<li>
Fixed two JBuilder incompatibilities. Innerclasses created by JBuilder do
not prevent yGuard from working anymore and (correct) innerclasses created
by yGuard do not crash JBuilder anymore (which btw. is a bug in JB).
</li>
<li>
Implemented a fix for the problem, where the <code>ClassName.class</code>
code construct prevented classes from being obfuscated entirely.
</li>
<li>
yGuard can now automatically obfuscate code of the form <code>
Class.forName("com.mycompany.myapp.MyClass");
</code> so that these classes can now be obfuscated by name, too.
</li>
<li>
Improved the serialization of the obfuscation map to the xml file, which can
now be parsed back in by the included tool even for complicated naming
schemes.
</li>
<li>
Refactored the creation of the final jar files. The current implementation
leads to more standard conform jar files.
</li>
<li>
Fixed two bugs concerning the handling of manifest files.
</li>
<li>
Fixed a bug concerning the handling of the Main-Class attribute of manifest
files.
</li>
</ul>
</p>
<h2>Changes since 1.0</h2>
<p>
<ul>
<li>
Implemented more robust handling of Manifest files. Implementation now makes
use of java.util.jar.Manifest.
</li>
<li>
The Main-Class attribute of the Manifest files will now be translated to the
obfuscated name, if the main class is not exposed.
</li>
<li>
The conserveManifest attribute of the obfuscate task now conserves the
manifest in a better way.
</li>
</ul>
</p>
</body>
</html>

2719
build/yguard-2.2.0/doc/yguard_ant_howto.html
View File

File diff suppressed because it is too large Load Diff

BIN
build/yguard-2.2.0/lib/yguard.jar
View File

Binary file not shown.

BIN
ressourcen/code-ressourcen/junit-4.8.2-src.jar Normal file
View File

Binary file not shown.

BIN
ressourcen/libs_ext/junit-4.6.jar
View File

Binary file not shown.

BIN
ressourcen/libs_ext/junit-4.8.2.jar Normal file
View File

Binary file not shown.

9
src/jd/controlling/reconnect/RouterPlugin.java
View File

@ -42,7 +42,6 @@ public abstract class RouterPlugin {
* @return
*/
public int autoDetection() {
// TODO Auto-generated method stub
return -1;
}
@ -84,7 +83,6 @@ public abstract class RouterPlugin {
* @return
*/
public int getIpCheckInterval() {
// TODO Auto-generated method stub
return 5;
}
@ -125,12 +123,11 @@ public abstract class RouterPlugin {
/**
* Returns if this plugin might be able to find a valid setup without any
* userinteraktion
* userinteraction
*
* @return
*/
public boolean hasAutoDetection() {
// TODO Auto-generated method stub
return false;
}
@ -141,7 +138,6 @@ public abstract class RouterPlugin {
* @return
*/
public boolean hasDetectionWizard() {
// TODO Auto-generated method stub
return false;
}
@ -177,13 +173,14 @@ public abstract class RouterPlugin {
* @throws InterruptedException
*/
public int runDetectionWizard() throws InterruptedException {
// TODO Auto-generated method stub
return -1;
}
public abstract void setCanCheckIP(boolean b);
@Override
public String toString() {
return this.getName();
}
}