I have a multi-module project where moduleA has a test-jar depedency to
moduleB.
I am running Maven 3 and was under the impression that maven would figure
out the dependency in the same reactor (I am running through the parent
project). However, some goals can't find the test-jar dependency:
- si
Hi there,
hibernate-core 4.0.0CR4 is in central and has a dependency on jandex that is not
present in maven central:
http://search.maven.org/remotecontent?filepath=org/hibernate/hibernate-core/4.0.0.CR4/hibernate-core-4.0.0.CR4.pom
I thought that via the nexus staging process this is prevented b
On Fri, Oct 7, 2011 at 2:14 PM, Laird Nelson wrote:
> It appeared that the tag option was simply ignored.
>
Bug filed against either the plugin option itself or the documentation:
http://jira.codehaus.org/browse/MRELEASE-712
Thanks,
Laird
--
http://about.me/lairdnelson
On Fri, Oct 7, 2011 at 1:24 PM, Laird Nelson wrote:
> My best guess was that maybe it was the tag from which a branch should be
> created? I.e. in Subversion: svn copy ^/tags/the-tag-name-goes-here
> ^/branches/the-branch-name-goes-here
>
Well, I tried this, and then diffed the resulting branch
I couldn't tell from the documentation what the "tag" option is for in the
maven-release-plugin branch goal.
I understand fully what it is for in the prepare goal.
My best guess was that maybe it was the tag from which a branch should be
created? I.e. in Subversion: svn copy ^/tags/the-tag-name-
