| /[Apache-SVN]/cocoon/trunk/parent/pom.xml |
Parent Directory
| 
Revision Log
| Links to HEAD: | (view) (annotate) |
| Sticky Revision: |
fix version numbers that caused broken subproject docs
back in SNAPSHOT mode
back in SNAPSHOT mode
[maven-release-plugin] prepare for next development iteration
[maven-release-plugin] prepare release cocoon-8
increase doc version numbers
Update to poi-3.2-FINAL
Added dlegg to developer list.
Added myself to list of developers.
spelling
Added myself to the list
<action dev="reinhard" type="add"> Make the HTTP port of Jetty configureable. The JettyStarterMojo can be configured by the parameter 'port'. </action> <action dev="reinhard" type="add"> Add a parameter 'keepRunning'. If true, the 'integration-test' phase keeps running stops after the Jetty container has been started. This is useful for debugging the 'integration-test' phase. </action> <action dev="reinhard" type="update"> Upgrade to JUnit 4.4. </action> <action dev="reinhard" type="update"> Java 5 as minimum requirement. </action>
enable shortcut for rat plugin (mvn rat:check)
add and configure the codehaus rat plugin (version, excludes, add it to the 'release' profile)
Switch to Java 1.5 and enforce Maven 2.0.9 as minimal for Cocoon's trunk. Also, updated links to Java APIs to point to Java 1.5 API docs.
add apples, eventcache, jcr and jms to the documentation system
Cocoon PMC -= Gianugo
set 'breadcrumb' version
increase SNAPSHOT versions after release
fix version number of docs-cleaner (has never been released IIRC)
fix ssf doc version
Add sitemaptags2daisy to build process. It's executed in step 2 (Build all modules required for the site generation) of http://cocoon.apache.org/1256_1_1.html and updates the sitemap annotations in daisy.
. use spring-configurator 2.1.0-SNAPSHOT internally . use improved Daisy plugin again after release . set version of the maven-plugin-plugin . enable SNAPSHOT section again after release
[maven-release-plugin] prepare for next development iteration
[maven-release-plugin] prepare release cocoon-7
[maven-release-plugin] prepare for next development iteration
[maven-release-plugin] prepare release cocoon-7
[maven-release-plugin] prepare for next development iteration
[maven-release-plugin] prepare release cocoon-7
[maven-release-plugin] prepare for next development iteration
[maven-release-plugin] prepare release cocoon-7
. increase version number of the spring-configurator to 2.0.0-SNAPSHOT . add jnet and block-deployment to docs configuration
Reflect adding the cdocs-it collection to daisy
explicitly set version numbers because of the Maven 2 - Java 1.4 bug (that has hit us soooo many times)
set version numbers of dependencies used in jms/event-cache blocks
Increase version number for Spring Configurator to 1.1.0-SNAPSHOT as preparation step to adding new features to it.
Switch to arbitrary version of daisy-util which will be served from my own *temporary* repository. Once I sort out all problems with site generation I'll clean up dependencies.
Temporarily added my repository that hosts SNAPSHOT build of daisy-maven-plugin.
Switch to SNAPSHOT version of daisy-maven-plugin.
upgrade to Spring 2.5.5
Update to poi-3.0.2, 2nd iteration
Vadim = Cocoon PMC chair
. fix mount paths of ssf samples (after the split up) . set version numbers of samples . fix paths of integration tests
make use of the new subprojects JNet and BlockDeploy
. use SNAPSHOT versions of SSF and spring configurator again
. set version of aspectj . set version of SSF and Spring configurator to recent releases
Fix version
Fix version
increment versions of cocoon-core too
Spring 2.5.1 -> 2.5.2; spring-dao -> spring-tx
add it-fw properties
fix typo in version of cocoon-xml-impl
back in SNAPSHOT mode after release
use new SNAPSHOT version of servlet-service-impl
set SNAPSHOT versions again
back to SNAPSHOT mode (for now without incrementing version numbers)
[maven-release-plugin] prepare for next development iteration
[maven-release-plugin] prepare release cocoon-6
set version of cocoon-it
add license and notice files to the META-INF directory of each module
Make jcr block compilable and fix test cases.
Java 1.4 seems to not ship with javax.mail library.
enable integration tests for trunk: use the 'it'profile for that purpose (mvn install -P it)
cocoon-databases-impl must depend on cocoon-databases-bridge module because it provides replacement forstandard DataSourceComponentSelector.
Update to Spring 2.5.1.
Documentation is published even for unreleased blocks. Properties defining documentation location must be uncommented.
congratulations, Arje!
add markmail.org archives
Fix typo (and documentation publishing as well).
configure cdocs-expression site
Fix database bridge docs generation.
Update castor to latest release.
upgrade cocoon-lucene block to lucene 2.2.0
upgrade to Spring 2.5
Too fast too furious.
Docs of cocoon-databases-bridge should be published to separate site.
adding back additional samples
use latest version of surefire plugin
fix relative paths
configure javadocs plugin for the daily docs build on the cocoon.zone
current version of template block
upgrade to xindice 1.1
Remove module section from parent pom.
Start moving of parent pom into its own directory (WiP)
Cocoon PMC -= Peter Royal
Springified CForms (as much as possible)
fix versions
increment snapshot version
[maven-release-plugin] prepare for next development iteration
[maven-release-plugin] prepare release cocoon-5
fix paths for creation of subproject docs; move javadocs-script reporting plugin into its own profile
snapshot mode
[maven-release-plugin] prepare for next development iteration
[maven-release-plugin] prepare release cocoon-5
prepare for a release (third time lucky): - use the new javadocs script report - move configuration of the javadocs plugin into the release section and don
make trunk buildable again
SNAPSHOT mode
[maven-release-plugin] prepare for next development iteration
[maven-release-plugin] prepare release cocoon-5
[maven-release-plugin] prepare for next development iteration
[maven-release-plugin] prepare release cocoon-5
SNAPSHOT mode
try it this way ... (the release plugin eagerly removes comments under some circumstances)
[maven-release-plugin] prepare release cocoon-5
svn rev id
upgrade to latest plugin version
Adding profile for compiling with Spring 2.1. This is needed in the Cocoon-OSGi work as I need to switch to the current development version of spring-osgi that is based on Spring 2.1 instead of Spring 2.0.
back to 1.2.14 because the log4j community pleases us with a load of unrequired dependencies
upgrade to latest versions of Rhino and log4j
adjust properties for docs build
COCOON-2125: Create new module cocoon-xml-util.
COCOON-2120: * Move welcome page and samples handling from cocoon-webapp to cocoon-welcome module. * Configure Cocoon blocks dispatcher (ServletDispatcher) to handle all requests. It's not experimental anymore.
Add test-jar artifact of cocoon-sitemap-impl to dependency managment section.
use java 1.4
Set scope to provided for some dependencies.
Move charsets to own module.
fix subproject sites
Use latest soureceresolver release.
Update Maven Eclipse plugin to 2.4 version
Use only the "correct" group id for the portlet-api.
fixed dependencies amongth modules
COCOON-2081: Adding cocoon-expression-language-* modules to dependency managment.
Creating empty module for expression language and object model.
back in snapshot mode; upgrade to Spring 2.0.6
[maven-release-plugin] prepare for next development iteration
[maven-release-plugin] prepare release cocoon-4
add license header (again)
added cocoon-acegisecurity-sample block
enable SNAPSHOT versions again after release
[maven-release-plugin] prepare for next development iteration
[maven-release-plugin] prepare release cocoon-4
[maven-release-plugin] prepare for next development iteration
[maven-release-plugin] prepare release cocoon-4
comment snapshot dependencies for the release
use released version of commons-jci
set docs.mode property
Cocoon PMC -= Niclas
Enable the FOP 0.9x block in the build now that the appropriate artifacts are in the central repository
use latest release of xreporter
upgrade to latest Spring
correct developer information if people activly asked for emeritus status or have never been on the Cocoon PMC
Added missing committers, set emeritus status, added missing roles
All active, inactive and emeritus developers added that I could find
increment version numbers of pom modules after release (tested with an empty repo - hopefully it works for others too)
correct version number
back in snapshot mode
Add samples to dependencyManagement
fix versions after release
set snapshot versions for own modules again in dependencyManagement section
[maven-release-plugin] prepare for next development iteration
[maven-release-plugin] prepare release cocoon-4
comment all Cocoon snapshot dependencies
I will increase the version number later so that the build of all trunk users isn't affected
[maven-release-plugin] prepare for next development iteration
[maven-release-plugin] prepare release cocoon-4
fixed typo
breaks link calculation
set back to 2.0.6 again
fix site generation in multi-module builds: as long as site/pom.xml was a child of the root pom, the site module did crazy things. Now site/pom.xml is a root POM and references all modules that procude site content. Probably the problem was the the root pom was in in the execution chain AND in the inheritance chain.
move all relevant modules for building a site into the daisy profile
use a profile for site creation
0.93 is out, still not in this groupId in maven.
Correction in name of Tay Thien Luh + addition as contributor to pom.xml
downgrade because excalibur-sourceresolve 2.2.2 is broken (at least for us)
upgrading to latest excalibur releases, fixes COCOON-2029. Cleaned up duplicate groupid/artifactid declaration for sourceresolve and datasource
explicitly set plugin version
Enforcing 2.0.6+ as minimal Maven version using enforcer plugin.
use latest eclipse plugin version
rename documentation too
Adding myself to the contributor list
removed duplicate developer and order the rest in alphabetical order
update version due to http://jira.codehaus.org/browse/MNG-2959
fix artifact version
was only a local experiment
configuration of block documentation: changes.xml, version + path properties
adding myself as developer
poms without version element in dependency section
switch to cocoon-thien skin; use latest version of Daisy export plugin together with our custom export strategy, don't use absolute paths in the skin but set a relativizer path instead; fix properties of site paths and versions
Fixed indentation of dependencyManagement section. Kept in sync with recent changes to cocoon-form-impl pom.
added dependencyManagement section with aggregated deps from sub poms
uncommented references to daisy-export-strategy that broke the build
add docs for all modules that already have a milestone release
add myself to Cocoon developers list
Me too ;-)
configure gpg plugin
compiler plugin update
upgrading to new apache pom
- site generation for new "website-only" sites should work now
fix relative paths to docs
upgrade to latest Avalon/Excalibur releases; root pom only depends on the Maven central repository - if some module has a dependency to a different repository, it is declared explicitly there; minor cleanups
add more properties for upcoming documentation modules; add modules to site build but leave them commented as long as the Daisy integration has been configured
tid up poms: use snapshot versions
adding profile block docs config
add sub projects to root pom
add Daisy plugin again after release
[maven-release-plugin] prepare for next development iteration
[maven-release-plugin] prepare release cocoon-3
configure maven-release-plugin supporting the new folder structure of https://svn.apache.org/repos/asf/cocoon/tags
set version of maven-eclipse-plugin, otherwise it doesn't work with an empty repository
comment checkstyle plugin too
comment maven-reports plugin as it breaks the build as long as it is unreleased
Add support for checkstyle report generation
Correct pom and add configuration api
sort properties; add subprojects
use properties to set these values only once
Add daisy information for site generation
add findbugs reports
add properties for 4 core modules
only create changes-report; add properties for blocks-fw-impl docs
make the Javadocs and the changes report default reports; add more links to Javadoc; start introducing properties for each documentation module to simplify mainainance
different path for reloading classloader plugin documentation; set Javadoc links; add 'summary' project-info report by default
use latest war plugin (2.0.2); restructure reporting plugins and upgrade to the latest versions of each
add cdocs-rcl-plugin documentation
seems like we're lagging a bit behind on the javadoc plugin
fix repoUrl
reactivate Daisy plugin again
[maven-release-plugin] prepare for next development iteration
[maven-release-plugin] prepare release cocoon-2
switch back to alpha-6 of the wagon-ssh-external plugin
[maven-release-plugin] prepare for next development iteration
[maven-release-plugin] prepare release cocoon-2
make it well-formed again
comment Daisy plugin; upgrade to latest version of wagon-ssh-external; change tagBase configuration parameter of the release plugin
add reporting section to default site.xml
use SNAPSHOT versions again; comment in Daisy
first round of version increments
[maven-release-plugin] prepare for next development iteration
[maven-release-plugin] prepare release cocoon-2
set staging repository to people.apache.org/www/people.apache.org/builds/cocoon; comment all dependencies on snapshot plugins
order of roles; add PMC member role for devs who have forgotten themselves
add self to POM developer listing
workaround for a Maven bug, at least IMO (pom configuration parameters override sysytem properties)
added my PMC member role
add role
Add role
added myself to the pom
Added my profile
personal info + making war plugin explicit
profile added
added my profile to the pom
Adding my details
Added my profile
update my roles
fix path to main site
cocoon.zones.apache.org can't be resolved from our zone. change this to localhost for some Continuum experiments
tweaking repositories
enabling compiler plugin to 1.4, setting repo1 as primary repository again
include dists
Update to final release of Spring 2.0 Correct our namespace for spring configuration Use 2.1 as version for assembly plugin to avoid build problems
latest assembly plugin snapshot works (not in repository yet)
adding repo type
Daisy docs infrastructure added
comment out assembly plugin
add the template block configuration; add reports but only to a profile
the right to assemble
fix incorrect path
cleanup generated site.xml before running the Daisy Maven plugin
add reports; default report is the license only
add new collection/path mapping
make use of the new configuration parameter 'siteXmlContent' that allows to configure a default site.xml for the Maven site generation; rename docs properties by using the 'docs' prefix; configure the new collection cdocs-site-maven-plugins
configure the Maven Daisy plugin + a plugin snapshot repository; configure the site plugin; set the inception year; remove license configuration as it is inherited from the Apache pom
Please add version numbers to plugins, otherwise build fails on machine which have not downloaded the plugin yet
configure idea plugin
adding new license header to all poms
better be explicit in the url
moving staging repo to people.a.o
rolling back test release
[maven-release-plugin] prepare for next development iteration
[maven-release-plugin] prepare release cocoon-2-test-will-be-removed
testing staging repository
root apache pom is on version 3 now
Add version of release plugin (otherwise it doesn't build on some machines)
reactivate modules
[maven-release-plugin] prepare for next development iteration
[maven-release-plugin] prepare release cocoon-1
comment modules as I don't want to do a bulk release
configure release plugin
pom cleanup, applying ./tools/depmngt/pomCleanup.xsl
changing deployment targets to new locations, as announced on repository@a.o
add self
starting pluginManagement section to 'lock down' the build plugin versions used
cvs.a.o wasn't a recommended hostname. Removed default install goal
fixing some typos
updated README, main pom
- setup ASF-wide pom as parent - codehaus repo is not used anymore - renamed cvs.a.o to svn.a.o (it's the same host)
remove irc notifier now that the mailinglist is getting notifications
relisting central as first repository, this greatly improves the timeout problems on cvs.a.o because it's not contacted so often anymore
XSP block: Fix regression introduced in 2.1.8 that under specific circumstances logicsheets were not applied, leading to compilation errors. This manifested itself only if a) two XSPs referred to the same custom logicsheet by a relative location path, b) the custom logicsheet used another logicsheet, and c) the built-in logicsheet's namespace was not mentioned in xsp:page. The compilation errors occurred always when calling the second XSP for the first time. Fix also race condition which could lead to similar XSP compilation errors under high load when accessing the same logicsheet for the first time.
applied COCOON-1837 , supplied by Ben Pope
Fix typo.
configure mailinglist notifier
Add some blocks to build
switch versioning schema for pom artifacts as suggested by Jorg
integrate the deployer, start to get cocoon-webapp working again; minor cleanups
get cocon-core, forms and ajax compiling again
Spring block is not needed anymore; make sub sitemaps work correctly
Both cocoon-webapp and cocoon-databases complie, so they should be part of the main module list.
add cocoon-default module
Compile the new block.
add new cocoon-core-components module; add myself as project committer
adding myself to the developers list
fixed pom for renamed/moved blocks
Update quartz to 1.5.1 and add cron block to build
now the Maven 2 plugin can be added to the reactor build too
found a workaroundn for relative paths in poms so that stand-alone and reactor build work with the same configuration
Add some balance to the TimeZone weight ... developers += crossley
The proper name is "The Apache Software Foundation".
Adding myself to pom.xml, reordering alphabetical order
Disable failing modules, add new modules
Add myself and move Betrand according to the alphabet.
Add myself
added myself
added myself
added myself
adding myself
Added myself
add myself as a developer, others should do this as well
prepare root pom for reporting and site generation
added plugins to build system
we're not owning our own channel so outside notifications won't work
freenode.NET
added archetypes to the build tree of modules
wagon-ssh-external has been released
Improved POMs and some deletes that I forgot to commit.
correcting scm urls, adding ciManagement section
trying to get continuum running again
Portal impl now compiles
made cocoon-validation compile
commented not compiling blocks
make all blocks belong to the same groupId
Adding license element
Test enable ajax block
adjusting poms for authentication-fw to build
switchting to excalibur libs, make root pom versioned
change groupId to maven standard
make cocoon snapshots deployable
Use first the official mavenw repo.
- created pom in src/blocks, referenced from root pom as a module. Moved block definitions to this pom. - setup forms block with new pom structure - adding some name descriptors - removing reports for now - removed webapp block dependencies
We don't need to include this repo as it is mirrored by Ibiblio.
[M10N] - updated commons-jci and commons-javaflow - adding ajax block to the build - forms block depends on ajax block
Create own project for cocoon testing framework and fix dependencies.
Fix dependencies for block and add all blocks as dependencies to webapp to find problems with transitive dependencies
add the remainder of the blocks.
Adding hsqldb, html, itext, javaflow, jfor, linkrewriter, lucene, mail and midi block for compilation to maven2 build. I have uploaded the necessary dependencies to the cvs.apache.org repository. Added mocks as separate module for inclusion by other blocks.
Adding faces, portal and taglib block for compilation to maven2 build. I have uploaded the necessary dependencies to the cvs.apache.org repository, except for the pluto-1.0.1-rc4 which is still pending.
introduce m2 style pom inheritance.
Use alphabetical order for blocks Add missing dependency to servlet api to axis block
Adding asciiart, bsf, chaperon, deli and fop block for compilation to maven2 build. I have uploaded the necessary dependencies to the cvs.apache.org repository
Adding apples, axis, batik and forms block for compilation to maven2 build. I have uploaded the necessary dependencies to the cvs.apache.org repository
Add spring-app, portal poms
Add cron
Add template block to m2 build
Update to latest avalon framework, include session and authentication in m2 build
Add webapp module and move javaflow related stuff into the javaflow block
Add main pom
This form allows you to request diffs between any two revisions of this file. For each of the two "sides" of the diff, enter a numeric revision.
| apache@apache.org | ViewVC Help |
| Powered by ViewVC 1.1.2 |