ory
> as
> > my checkout source. This would result in the pom.xml appearing in the
> root.
> > However, I use git which I don't think I can specify a subdirectory in
> my
> > git project for checkout. At least not using the SCM configuration in
> > M
; Maven.
>
> --
> View this message in context:
> http://maven.40175.n5.nabble.com/Release-plugin-when-POM-is-not-in-root-directory-tp4956364p4958980.html
> Sent from the Maven - Users mailing list archive at Nabble.com.
>
> -
This would result in the pom.xml appearing in the root.
However, I use git which I don't think I can specify a subdirectory in my
git project for checkout. At least not using the SCM configuration in Maven.
--
View this message in context:
http://maven.40175.n5.nabble.com/Release-plugin-when-
/user/SendEmail.jtp?type=node&node=4956527&i=1>
>
>
>
> ------------------
> If you reply to this email, your message will be added to the discussion
> below:
>
> http://maven.40175.n5.nabble.com/Release-plugin-when-POM-is-not-in-root-directory-tp49563
Am 01.11.2011 22:27, schrieb Jim Cook:
> This is where the problem occurs, since the pom.xml is not in the working
> directory.
Just for clarity: does this mean, your pom.xml is not in the git
repository you're trying to release?
If so: DFMYL (Don't Fight Maven, You'll Lose!).
Put your pom.xml un
, but I cannot find any help
online. Anyone have a suggestion?
--
View this message in context:
http://maven.40175.n5.nabble.com/Release-plugin-when-POM-is-not-in-root-directory-tp4956364p4956364.html
Sent from the Maven - Users mailing list archive at Nabble.com.
