• last updated a few seconds ago
Constraints: committers
Constraints: files
Constraints: dates
Preparing for next dev cycle

Preparing for tagging jbossws-parent 1.2.0.Final

Prepare to next dev cycle

Preparing for tagging

Move to 1.2.0-SNAPSHOT and enfore Java 1.7 and Maven 3.2.2 requirements

Move to maven-assembly-plugin 2.5.3

Updating maven-resources-plugin and maven-surefire-plugin

Move to maven-dependency-plugin 2.8 version

[JBWS-3860] Require JDK 1.7+ for building JBossWS

Preparing for next dev cycle

Preparing for tagging 1.1.0.GA

Moving to maven compiler plugin 2.4

introducing new JBossWS trunk version
[JBWS-3480] Updating maven plugin versions

Preparing for next dev cycle

[JBWS-3382] Require maven-assembly-plugin 2.2-beta-5 and at least maven 2.2.1

Added properties and resources configuration
prepare for next dev cycle
prepare for release
force 2.6 version of maven-eclipse-plugin to workaround 2.8 version issue
better maven-surefire-plugin defaults
Remove duplicate plugin configuation
[JBWS-3080]:Update maven plugin to the latest version
use explicit maven-war-plugin version to have reliable builds
explicitely set maven-clean-plugin version - to remove warnings
Update maven plugin and specifiy the plugin version to remove the warning message in maven3
Moving to next dev cycle

[JBWS-2957] Maven 2.0.11 is actually enough

[JBWS-2957] Update enforces plugin to require at least Maven 2.1.0 as that's what comes with a maven antrun plugin having Ant 1.7.x or greater (and currently Maven does not support version ranges for plugins...)

[JBWS-3093] configuring JBossWS compiler to always use UTF-8 during compilation phase