Hello,
The main feature I like about wicketstuff is that its easy for
developers to add in code that is automatically built and deployed into
maven. It allows an easy way to reactor a project to extract certain
reusable functionality, externalize it for others to use, and still be
able to build the originating project reliably.
+1 for using wicketstuff.org for the example applications and the build
server and removing jira and confluence, etc for presupplied low
maintenance options.
I want to help find a solution to the current team city <-> source forge
build problems. I want to look at changing build servers before
considering switching the repository from sf to github. (vote: [X] stay
with sf.net).
I'm not sure how much resources are required to build wicketstuff but I
plan on starting with an old Linux box at work (P4 single core 1.8
Ghz). I want to start with hudson and see if I can keep it unbanned
while running the same high frequency updates.
The other part is getting accounts setup through sonatype to let the
maven artifacts be deployed. This requires an issue being filed into
the sonatype JIRA.
I could start with creating the JIRA issue for me first then if I can
get it to work or others want to help we get the additional users added.
My thinking is that I could test this stuff out separately and if it
works then wicketstuff.org could be switched over.
If anyone thinks it would be a bad idea (or if there are other
considerations I don't seem to be aware of) for me to file the JIRA
request let me know otherwise I'll plan on getting started on this stuff
next week.
Regards,
Mike
http://hudson.zones.apache.org/hudson/job/Apache%20Wicket%201.5.x/
On Sun, Apr 25, 2010 at 11:16 PM, Martijn Dashorst
<[email protected]> wrote:
I've requested hudson access to build our Apache Wicket core projects
on the Apache hudson grid.
Martijn
On Mon, Apr 19, 2010 at 5:31 PM, Martijn Dashorst
<[email protected]> wrote:
Currently we have a maintenance nightmare. Keeping up confluence,
jira, teamcity and the maven repo is cumbersome at best. We keep
running out of diskspace (/var has reached -300M disk free, yes minus
300M).
So I propose the following:
- use Apache's build grid for Wicket code, Apache repository for
staging and snapshot releases: separating the Apache Wicket projects
from Wicket Stuff projects
- no more custom, self hosted products a la confluence and jira (no
matter how much we like them)
- use wicketstuff.org only for running examples and a build server
for wicket stuff projects
- use sonatype's OSS repo hosting for our snapshots, release staging
and releases (no more wicketstuff.org/repository/maven)
Most importantly:
- vote on the future of the hosting of Wicket Stuff:
[ ] stay with sf.net
[ ] move to github
- if we stay on sf.net: use the sf.net provided tools to manage the
project: issues, wiki and website
- if we stay to move to github: use github's provided tools to manage
the project: issues, wiki and website
Martijn
--
Become a Wicket expert, learn from the best: http://wicketinaction.com
Apache Wicket 1.4 increases type safety for web applications
Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.4.7
