Nope, using the maven-release-plugin [1] would be enough as it takes care of
checking/changing versions both in the dependencies (if there is any
-SNAPSHOT dependency) and in the modules' versions.
A very quickly look at the process goes like running mvn release:prepare
which signs artifact,
Thanks for the answers.
This would all be fine if maven were the primary build mechanism for
ManifoldCF, but it is not at this time, for many reasons. From your
description the pom's should remain -SNAPSHOT in the release if this
is the case, no? Also, is there any way to have it not change
[
https://issues.apache.org/jira/browse/CONNECTORS-240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13100504#comment-13100504
]
Emmanuel Keller commented on CONNECTORS-240:
Sorry, I am a little bit
[
https://issues.apache.org/jira/browse/CONNECTORS-240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13100509#comment-13100509
]
Karl Wright commented on CONNECTORS-240:
I put together an RC0, but have not
Hello.
I tested sharedrive connector/ authority connector
on 0.3RC0 and confirmed changes.
It worked well.
BTW, ant run-script-engine-tests said build failed.
The same error is in trunk . Is it okay?
Regards,
Shinichiron Abe
On 2011/09/08, at 8:17, Karl Wright wrote:
You can find it here:
jcifs.jar download
--
Key: CONNECTORS-251
URL: https://issues.apache.org/jira/browse/CONNECTORS-251
Project: ManifoldCF
Issue Type: Improvement
Components: JCIFS connector
Affects Versions: ManifoldCF next
