Hi,
I have a multi-module project and I want to create a shorter version of the
build that selectively builds a sub-set of the modules. I am using a maven
profile for this. So if total I have module a, b, c, d and e, in a profile I
have a module list of a, b and c. The module c's pom.xml has
Thanks for the tip about types and files.
I agree that these should be deployed with different coordinates, but I
don't want to change names of these non-maven project artifacts, because
it would break many existing builds ... But this is what I'll do in the
future.
--
View this message in
Hi,
The Mojo team is pleased to announce the release of the LESS CSS Maven
Plugin version 1.0-beta-2.
This plugin can be used to compile *LESS* sources to *CSS*
stylesheets. See http://www.*lesscss*.org/ http://www.lesscss.org/
for more information about *LESS*.
I tried adding
*commitByProjecthttp://maven.apache.org/plugins/maven-release-plugin/prepare-mojo.html#commitByProject
and that got me a bit further.
I can see it commit properly, but the push step is failing because it's
trying to push a repo that hasn't had any changes in it yet.
For instance,
Am 27.01.2012 17:43, schrieb Maven User:
If your aggregate pom is NOT a parent pom, can you execute the release from
there?
Yes. This works. Doing it all the time in my projects. You can use any
POM which is available from a Maven repository as parent of your child
modules. It does not need to
Really?
Every time I do this, I get a message about things NOT being in the root
project...
Are you using mercurial or git or something entirely different?
I'm slowly starting to think this is an issue with the mercurial scm
implementation, NOT the release plugin
Oh and THANK you for your
Am 28.01.2012 00:23, schrieb Maven User:
Really?
Every time I do this, I get a message about things NOT being in the root
project...
Could you possibly post the actual error message?
Are you using mercurial or git or something entirely different?
Git. If you want, have a look at an
Am 27.01.2012 18:02, schrieb Maven User:
But the push is trying to push the aggregate repository, NOT the jar
repository.
Any suggestions?
AFAIK, that's the way it works with DVCS like Git. Not done a release
with a HG-based project though.
DVCS version the whole repository, not single
