Hi Thomas,
one question - the quartz library pulls in javax.transaction, c3p0 and slf4j
since this is defined in its pom. Do we really want those dependency propagated
or shall we exclude them directly for this project?
Thanks in advance
Siegfried Goeschl
fulcrum> mvn dependency:tree
[INFO] Scanning for projects...
[INFO] Searching repository for plugin with prefix: 'dependency'.
[INFO] ------------------------------------------------------------------------
[INFO] Building Fulcrum Quartz
[INFO] task-segment: [dependency:tree]
[INFO] ------------------------------------------------------------------------
[INFO] [dependency:tree {execution: default-cli}]
[INFO] org.apache.fulcrum:fulcrum-quartz:jar:1.1.0
[INFO] +- junit:junit:jar:3.8.1:test
[INFO] +- org.apache.fulcrum:fulcrum-testcontainer:jar:1.0.6:test
[INFO] +- org.apache.fulcrum:fulcrum-yaafi:jar:1.0.6:test
[INFO] | \- org.apache.avalon.framework:avalon-framework-impl:jar:4.3.1:test
[INFO] +- org.quartz-scheduler:quartz:jar:2.0.0:compile
[INFO] | +- javax.transaction:jta:jar:1.1:compile
[INFO] | +- c3p0:c3p0:jar:0.9.1.1:compile
[INFO] | \- org.slf4j:slf4j-api:jar:1.6.1:compile
[INFO] \- org.apache.avalon.framework:avalon-framework-api:jar:4.3.1:compile
----- Ursprüngliche Mail -----
Von: "Thomas Vandahl" <[email protected]>
An: "Turbine Developers List" <[email protected]>
Gesendet: Mittwoch, 14. September 2011 20:17:53
Betreff: [fulcrum] [VOTE] Release fulcrum-quartz-1.1.0 based on RC1
Hi folks,
Time for some releases again. A release candidate for
fulcrum-quartz-1.1.0 has been prepared. The uploaded files might need
some time to be mirrored.
Please verify this release candidate and vote...
Tag:
https://svn.apache.org/repos/asf/turbine/fulcrum/tags/FULCRUM_QUARTZ_1_1_0/
Site:
http://turbine.apache.org/builds/fulcrum/fulcrum-quartz/1.1.0/RC1/site/
Binaries:
http://turbine.apache.org/builds/turbine/fulcrum/fulcrum-quartz/1.1.0/RC1/staged/org/apache/fulcrum/fulcrum-quartz/1.1.0/
[ ] +1 release it
[ ] +0 go ahead I don't care
[ ] -1 no, do not release it because
Bye, Thomas.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
