jandockx / ppwcode-recovered-from-google-code Goto Github PK
View Code? Open in Web Editor NEWAutomatically exported from code.google.com/p/ppwcode
License: Apache License 2.0
Automatically exported from code.google.com/p/ppwcode
License: Apache License 2.0
When a number of business projects are delivered using the new ppwcode
vernaculars, decide
whether or not this project makes any sense anymore. This JSP project might
contain still some
things that need to be kept, like error pages, ... If not, or if the code is
used in other libraries, this
should be deleted at a given time.
Original issue reported on code.google.com by jandockx
on 11 Jul 2008 at 1:38
Create the Java part of the website
Original issue reported on code.google.com by jandockx
on 11 Jul 2008 at 12:36
Cleanup of ppwcode metainfo. First of all, we need to change the license
headers. Add svn-
annotation code (which is now, amongst others, en Beedraz).
Original issue reported on code.google.com by jandockx
on 3 Jun 2008 at 9:32
release first version asap
Original issue reported on code.google.com by jandockx
on 3 Jun 2008 at 10:47
This project is pretty important, and needs to be reactivated and cleaned asap.
This is not a utility
libary, and not a vernacular. It should become a project at the top level.
Original issue reported on code.google.com by jandockx
on 11 Jul 2008 at 1:43
For building and testing of our libraries, we have dependencies on a number of
external libaries,
some of which are not in the global maven repositories, for different reasons
(mainly license
issues).
For inhouse projects, we normally set up a "missing artifacts" repository, so
that we only need to
find and install those libs once for the entire team.
We cannot do this for these public projects. Such a setup requires a settings
in the maven pom,
and obviously we cannot make the missing artifacts repo publicly available (for
license reasons).
Once the reference to a missing artifacts repo is in the pom however, things
will stop working of
that repo is not public.
Users need to do an mvn install of the lib in question in their local repo
cache by hand. This
obviously is an escape for our developers too, but to sad.
Is there any solution for our team?
Original issue reported on code.google.com by jandockx
on 11 Jul 2008 at 2:07
Reactivate plugin settings and standards for code reports on this level.
Clirr? Check sensibility and configure if kept.
Original issue reported on code.google.com by jandockx
on 11 Jul 2008 at 1:01
add collection code from Toryt
Original issue reported on code.google.com by jandockx
on 15 Jun 2008 at 12:24
When a number of business projects are delivered using the new ppwcode
vernaculars, decide
whether or not this project makes any sense anymore. These things where created
a number of
years ago, when JSF was less stable, there was no Seam, and Spring was in its
infancy. Chances are
that, with those larger projects available, this code is no longer needed.
Original issue reported on code.google.com by jandockx
on 11 Jul 2008 at 1:36
Reactivate plugin settings and standards for code reports on this level.
Configure JavaNCSS:
evaluate, kill if not sensible.
Original issue reported on code.google.com by jandockx
on 11 Jul 2008 at 1:04
Reactivate plugin settings and standards for code reports on this level.
CPD settings. Check them.
Original issue reported on code.google.com by jandockx
on 11 Jul 2008 at 1:02
Describe version numbering scheme + rationale.
Original issue reported on code.google.com by jandockx
on 11 Jul 2008 at 1:18
From our first weeks in this setup, it becomes clear that a separate snapshot
library becomes
sensible. We already decided more or less that "dev" trees in svn will be
deleted once a stable
version is deleted. Why then would we keep the snapshot artifacts in the repo?
Deleting the
snapshots from the repo is a bit of work. By keeping them in a separate
snapshot directory, we can
just delete a subdirectory on the server, and be done with it.
The same applies to the project dev sites.
Original issue reported on code.google.com by jandockx
on 11 Jul 2008 at 1:53
Cleanup of ppw-code exception. Work will be done in the dev_II branch. First of
all, we need to
change the license headers. Further, we need to change the annotations to svn.
For this, we first
need to pull the meta-info project from the purgatory, and clean that, and add
svn-annotation
code (which is now, amongst others, en Beedraz).
Original issue reported on code.google.com by jandockx
on 3 Jun 2008 at 9:29
This old project will largely be incorporated in the semantics vernacular and
an i18n util project or
the smallfries util project. Once this is done, this part of the purgatory
should be deleted.
Original issue reported on code.google.com by jandockx
on 11 Jul 2008 at 1:34
write package documentation and overview
Original issue reported on code.google.com by jandockx
on 3 Jun 2008 at 10:46
Make license headers ok.
Original issue reported on code.google.com by jandockx
on 15 Jun 2008 at 12:22
Get waivers from all members, and client companies we work with from now on,
for ppwcode, and
for Apache (see http://www.apache.org/licenses/#clas).
Original issue reported on code.google.com by jandockx
on 28 May 2008 at 7:59
Reactivate plugin settings and standards for code reports on this level.
Configure FindBugs (this is a re-evaluation; we decided some years ago not to
use it since it is
really over-eager, and Checkstyle + PMD was much better)
Original issue reported on code.google.com by jandockx
on 11 Jul 2008 at 1:03
explanation of maven2 and pom subprojects in Java part. separate subpages?
Original issue reported on code.google.com by jandockx
on 11 Jul 2008 at 12:42
release first version
Original issue reported on code.google.com by jandockx
on 15 Jun 2008 at 12:25
Put existing versions of Java libraries in google code downloads. Copy from
cvs.peopleware.be
maven repo.
Original issue reported on code.google.com by jandockx
on 28 May 2008 at 7:56
Decide on version numbering scheme for implementation version (III-n.m.p-N.M).
It is probably
better and more simple to do this using a timestamp or the revision number.
That seems ok, but it
needs to be implemented in the maven parents.
Original issue reported on code.google.com by jandockx
on 11 Jul 2008 at 1:20
Reactivate plugin settings and standards for code reports on this level.
Evaluate configuration of StatSCM. This plugin must stay, but might replace
other plugins, and
maybe needs a bit of re-configuration.
Original issue reported on code.google.com by jandockx
on 11 Jul 2008 at 1:08
Reactivate plugin settings and standards for code reports on this level.
PMD: use existing standard, add for java 1.5, activate
Original issue reported on code.google.com by jandockx
on 11 Jul 2008 at 1:07
Dependency graph of subprojects on Java part of site.
Original issue reported on code.google.com by jandockx
on 11 Jul 2008 at 12:40
project needs a lot more unit tests
Original issue reported on code.google.com by jandockx
on 15 Jun 2008 at 12:23
ppwcode grows from the PeopleWare JavaLibraries project. We have a applications
in the field that
use the original libraries in a certain version. It is not the intention that
the libraries are further
maintained in the original private vcs, but even this week we encountered a
situation that we did
need to do a checkout of old code.
What are we going to do with this? Use the old private vcs for that? Or put all
those things in
ppwcode, in some subdirectory? In that case, we probably need to do a sizeable
amount of work, to
put all the licenses in order, work which we are now doing while refactoring
the code ...
Original issue reported on code.google.com by jandockx
on 11 Jul 2008 at 1:48
Set up back up of svn repo.
Original issue reported on code.google.com by jandockx
on 28 May 2008 at 8:06
For Maven 2 builds to be reliable in the future, it is necessary to fix the
versions of the plugins
used. This can be done in the root pom once and for all. This is done in the
pluginManagement tag.
Original issue reported on code.google.com by jandockx
on 24 Jun 2008 at 7:26
Create util part of Java part of website.
Explanation, list of projects.
Original issue reported on code.google.com by jandockx
on 11 Jul 2008 at 12:39
Chances are slim that we will do another Struts 1 project. What to do with this
library?
Original issue reported on code.google.com by jandockx
on 11 Jul 2008 at 1:42
list todo's
Original issue reported on code.google.com by jandockx
on 14 Jul 2008 at 11:12
mavenize the project
Original issue reported on code.google.com by jandockx
on 3 Jun 2008 at 10:46
I would really like a visual representation of the dependency graph in the
project reports. I believe I
remember some things on the maven2 mailing lists that say that such a thing
might exist now.
Original issue reported on code.google.com by jandockx
on 11 Jul 2008 at 1:10
This project contains a number of classes that are relevant for web
applications in general.
Consider reactivating them, possibly in the context of the new exception
vernacular. If not, or if the
code is used in other libraries, this should be deleted at a given time.
Original issue reported on code.google.com by jandockx
on 11 Jul 2008 at 1:39
Verify licenses, notices, etc... for release. Use apache projects as example.
Original issue reported on code.google.com by jandockx
on 14 Jul 2008 at 11:11
make copied code compile
Original issue reported on code.google.com by jandockx
on 15 Jun 2008 at 12:25
organize the source in a good new structure using svn move.
Original issue reported on code.google.com by jandockx
on 28 May 2008 at 7:52
Reactivate plugin settings and standards for code reports on this level.
Checkstyle: use existing standard, add for java 1.5, activate
Original issue reported on code.google.com by jandockx
on 11 Jul 2008 at 1:00
Define mailing lists.
Original issue reported on code.google.com by jandockx
on 28 May 2008 at 7:51
Mavenize
Original issue reported on code.google.com by jandockx
on 15 Jun 2008 at 12:21
purgatory settings mainly contains old settings files. Once the tasks for
cleaning the maven2 parent
poms with respect to the project report settings are done, this should be
removed.
On the other hand, this week we had to do some work on the old project, and we
needed the old
version of this repo. ... ?
Original issue reported on code.google.com by jandockx
on 11 Jul 2008 at 1:41
Upload source code from PeopleWare CVS.
Original issue reported on code.google.com by jandockx
on 28 May 2008 at 7:51
Build ppwcode.org website. Include existing maven project sites for existing
versions of libraries.
(Move from cvs.peopleware.be/projects/JavaLibraries/).
Original issue reported on code.google.com by jandockx
on 28 May 2008 at 7:54
forReintegration mainly contains old settings files. Once the tasks for
cleaning the maven2 parent
poms with respect to the project report settings are done, this should be
removed.
Original issue reported on code.google.com by jandockx
on 11 Jul 2008 at 1:33
Create vernacular part of the website. What is this, what are the projects, ...
Original issue reported on code.google.com by jandockx
on 11 Jul 2008 at 12:38
Reactivate plugin settings and standards for code reports on this level.
Configure JDepend: use existing standard, add for java 1.5, activate
Original issue reported on code.google.com by jandockx
on 11 Jul 2008 at 1:05
Verify licenses, notices, etc... for release. Use apache projects as example.
Original issue reported on code.google.com by jandockx
on 14 Jul 2008 at 11:06
Contracts with toryt annotations
Original issue reported on code.google.com by jandockx
on 15 Jun 2008 at 12:23
A declarative, efficient, and flexible JavaScript library for building user interfaces.
๐ Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. ๐๐๐
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google โค๏ธ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.