Does anyone know to get children modules as MavenProjects?
I'm building a plugin. I've already created something to find the parent
project from any child project. Now I want to find a specific project by group
and artifact ids. So I need to traverse the hierarchy from any child module. I
can
I don't know, but I would look in the source code of some open source maven
plugin that does similar things. Try the javadoc plugin as I believe it has
an aggregate goal.
/Anders
On Thu, Dec 13, 2012 at 11:55 AM, Marcos Mendez mar...@jitisoft.com wrote:
Does anyone know to get children
Well. figured it out. Thanks.
Found a way to get the root module. Then figured out how to load the modules by
using the maven project builder.
On Dec 13, 2012, at 6:47 AM, Anders Hammar wrote:
I don't know, but I would look in the source code of some open source maven
plugin that does
Hello Kristian,
I tried 2.13-SNAPSHOT and the stacktraces are not indented anymore and
the at is missing.
Netbeans (7.3 Beta 2) does not recognize these stacktraces when pasted
into the analyze window nor when clicking into the console output.
This is IMO a regression compared to 2.12.4. When
FYI: You should look for them in the list of reactor project first before
resorting to building a new model. Otherwise subtle effects to do with
order of installation into the maven repository can creep in
On 13 December 2012 11:53, Marcos Mendez mar...@jitisoft.com wrote:
Well. figured it
Hi,
I'm having trouble using the release-plugin on a project as it is
complaining that it has snapshot dependencies, even though those
dependencies are actually set to ${project.version}. So when the dependency
check phase runs they are indeed SNAPSHOT dependencies, if it were to
continue then
On Thu, Dec 13, 2012 at 3:33 AM, Wayne Fay wayne...@gmail.com wrote:
I do not understand your suggestion, can you elaborate?
He means, install a copy of Nexus locally on your laptop, and deploy
to it when you need to run offline rather than deploying to your
real repo which we assume is
reactor projects in the plugin are not all the projects and i'm not going to
force the user to run things from a top-level project. i'm interested in simple
properties not building or doing anything else with the project. my plugin does
just that with a little elbow grease. i could also just
Thanks for testing !
No need for an issue this time, I will fix real soon.
Kristian
2012/12/13 Mirko Friedenhagen mfriedenha...@gmail.com:
Hello Kristian,
I tried 2.13-SNAPSHOT and the stacktraces are not indented anymore and
the at is missing.
Netbeans (7.3 Beta 2) does not recognize
Well, normally most things are simple with Maven if you have a good
infrastructure setup, which includes a Maven repository Manager. But you
don't, and then you run into issues when you want to do workarounds. Get a
repo manager and you probably will not run into more issues as you continue
on,
The point I am making is that you should check the reactor list *FIRST* and
if not there *ONLY THEN* do you go and build the project. The Maven build
itself may have modified the pom files that are in the reactor during the
course of the build (not encouraged but possible... I've heard of people
Just for records, I'd like to state that you're creating something that is
not the Maven way. In Maven, projects should be self-contained and only
rely on dependencies to artifacts (not source code).
/Anders
On Thu, Dec 13, 2012 at 2:13 PM, Marcos Mendez mar...@jitisoft.com wrote:
reactor
Thanks, but as I wrote, this won't help me to package artifacts into
distributions.
I will continue to copy artifacts manually.
Thank you all.
On Thu, Dec 13, 2012 at 3:22 PM, Anders Hammar and...@hammar.net wrote:
Well, normally most things are simple with Maven if you have a good
But of course it would. Then you would do a build without the offline
switch and everything would just work.
Just understand you've been warned of going the path of making things more
complicated and painful than necessary.
/Anders
On Thu, Dec 13, 2012 at 2:25 PM, Alon Bar-Lev
Thanks. Doesn't apply to me. I've solved it in a good way.
On Dec 13, 2012, at 8:22 AM, Stephen Connolly wrote:
The point I am making is that you should check the reactor list *FIRST* and
if not there *ONLY THEN* do you go and build the project. The Maven build
itself may have modified the
Fedora packaging for example, enforces offline mode.
On Thu, Dec 13, 2012 at 3:29 PM, Anders Hammar and...@hammar.net wrote:
ld. Then you would do a build without the offline
switch and everything would just work.
Just understand you've been warned of going the path of making things more
Hi,
the maven-release-plugins only accepts ${project.version} for
reactor-projects, i.e. projects being part of a multi-module project.
The fact that your projects are separated also means that they both have
their own release-cycle. As you describe, they often(!) will be the same,
but if
Thanks for the fix, works like a charme :-).
Regards Mirko
On Thu, Dec 13, 2012 at 2:18 PM, Kristian Rosenvold
kristian.rosenv...@gmail.com wrote:
Thanks for testing !
No need for an issue this time, I will fix real soon.
Kristian
2012/12/13 Mirko Friedenhagen mfriedenha...@gmail.com:
I have a Git repository which is an application consisting of an EAR, WAR,
and JAR project. Each project has it's own pom.xml and then we have an
application level pom which just references the 3 modules. Our Jenkins job
will clone the git repository and use the high level pom to build the 3
Hi Brett,
the JAR i want to do a mvn deploy site, and the WAR and EAR modules
just a mvn install.
Jenkins lets you write whatever shell you want. So why not a shell script
like:
# at top level
mvn install
# deploy the JAR only
(cd myJarModule mvn deploy site)
Would that
I thought about the shell script idea as well, but would prefer just a single
step of pointing it to the parent pom and everything is handled. Leaving
the configuration out of Jenkins and putting it into the POM. Something
along the lines of in the parent POM where you specify the modules you
Hi Brett,
Leaving the configuration out of Jenkins and putting it into the POM.
In that case, could you add plugins configuration block to your child POMs
which sets the skip property for maven-deploy-plugin and
maven-site-plugin?
Good idea, worked like a charm. Thanks for your help!
--
View this message in context:
http://maven.40175.n5.nabble.com/Maven-and-Jenkins-question-tp5738064p5738111.html
Sent from the Maven - Users mailing list archive at Nabble.com.
Is there any documentation about what's new in maven-compiler-plugin 3.0
over the 2.5.1 version? I scoured the project site found nothing; various
Google searches have also found nothing.
After switching to maven-compiler-plugin 3.0 I'm seeing compilation
problems that do not show up when using
Is there any documentation about what's new in maven-compiler-plugin 3.0
over the 2.5.1 version? I scoured the project site found nothing; various
Google searches have also found nothing.
-- Forwarded message --
From: Olivier Lamy ol...@apache.org
Date: Mon, Nov 19, 2012 at
After switching to maven-compiler-plugin 3.0 I'm seeing compilation
problems that do not show up when using the 2.5.1 version, nor do they show
up in Eclipse.
Do you mean compilation errors or warnings? There's some major changes in
the the underlying plexus-compiler that will provide
Actually the release plugin allows you to specify a release and a development
version for any module in your build:
http://maven.apache.org/plugins/maven-release-plugin/examples/non-interactive-release.html
Even if this means you have to configure a comandline that is insanely long.
I recently
27 matches
Mail list logo
