AW: Release plugin & ${project.version} dependencies
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 built a Jenkins plugin for Volkswagen and they allowed me to publish
that. It's main goal is to allow to configure that commandline by selecting
checkboxes and suggesting version.
https://dev.c-ware.de/confluence/display/PUBLIC/Developing+a+Jenkins+Plugin+for+the+Maven+Release+Plugin
It allows to do a "Major" release (All modules are set to the same version) or
a minor release, in which you check a checkbox for the modules you want to
release. The tool automatically queries a repo for existing versions and
suggests a new version number for that minor release. I did do quite some work
on that plugin in the last 2 Weeks and am planning on updating my documentation
and publishing the code at github as soon as I have the time to cleanup the
code and strip out the VW-specifics.
Chris
-Ursprüngliche Nachricht-
Von: Robert Scholte [mailto:rfscho...@apache.org]
Gesendet: Donnerstag, 13. Dezember 2012 21:38
An: Maven Users List
Betreff: Re: Release plugin & ${project.version} dependencies
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 your
MSI config is changed, does that require a new project-main?
So I understand why it was implemented like this.
You could change the value for allowTimestampedSnapshots[1] to true, but then
you've lost the check for all snapshots.
What you could probably do is combine this with the enforcer rule called
RequireReleaseDependencies[2] (have never done this myself though).
Robert
[1]
http://maven.apache.org/plugins/maven-release-plugin/prepare-mojo.html#allowTimestampedSnapshots
[2] http://maven.apache.org/enforcer/enforcer-rules/requireReleaseDeps.html
Op Thu, 13 Dec 2012 13:51:06 +0100 schreef Dan Godfrey
:
> 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 they would be updated to non-SNAPSHOT
> dependencies in a later phase.
>
> I was wondering if anybody knows of anyway to get around this?
>
> To explain why: I have 2 separate projects project-main &
> project-windows.
> project-main is a jar (well multiple jars)which are deployed to our
> local repo. project-windows then takes that deployed jar and packages
> it up as an MSI. Both of these projects are kept in lockstep with
> regards version numbers and have separate CI jobs. I've split the 2
> projects up in different SCM repos like this as we have have other CI
> jobs depending on project-main for testing, and potentially in the
> future a project-linux, etc.
>
> Thanks,
> Dan.
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: What's new in maven-compiler-plugin 3.0?
> 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 compilation info in a better way. So although you didn't see this in earlier version you might still have had the "problems". /Anders
Re: What's new in maven-compiler-plugin 3.0?
> 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 Date: Mon, Nov 19, 2012 at 2:29 AM Subject: [ANN] Maven Compiler Plugin 3.0 Released To: annou...@maven.apache.org, Maven Users List Cc: Maven Developers List The Maven team is pleased to announce the release of the Maven Compiler Plugin, version 3.0 ...snip... Release Notes - Maven 2.x Compiler Plugin - Version 3.0 ** Bug * [MCOMPILER-160] - javac error but build SUCCESS * [MCOMPILER-173] - use new maven plugin annotations * [MCOMPILER-179] - Warnings * [MCOMPILER-181] - Exception on compilation are not properly reported * [MCOMPILER-182] - Case sensitivity changes in class names not detected by compiler * [MCOMPILER-184] - use last plexus-compiler 2.0 api * [MCOMPILER-186] - mojos are in wrong package (org.apache.maven.plugin) ** Task * [MCOMPILER-171] - use maven-plugin-tools' java 5 annotations > 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. Can you be more specific (with error messages etc), or perhaps even create a little sample Maven project to share that demonstrates the issues you're seeing? Eclipse has its own compiler so it is not necessarily true that no failures in Eclipse means no failures when compiling with Oracle's JDK. Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
What's new in maven-compiler-plugin 3.0?
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 the 2.5.1 version, nor do they show up in Eclipse.
Re: Maven and Jenkins question
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. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven and Jenkins question
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? http://maven.apache.org/plugins/maven-deploy-plugin/deploy-mojo.html#skip http://maven.apache.org/plugins/maven-site-plugin/site-mojo.html#skip -Curtis On Thu, Dec 13, 2012 at 3:49 PM, vincentx wrote: > 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 you > could nest per module. I know that probably doesn't exist but > thats > the kind of functionality i'm looking for. > > > > -- > View this message in context: > http://maven.40175.n5.nabble.com/Maven-and-Jenkins-question-tp5738064p5738077.html > Sent from the Maven - Users mailing list archive at Nabble.com. > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > >
Re: Maven and Jenkins question
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 you could nest per module. I know that probably doesn't exist but thats the kind of functionality i'm looking for. -- View this message in context: http://maven.40175.n5.nabble.com/Maven-and-Jenkins-question-tp5738064p5738077.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven and Jenkins question
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 work for you? -Curtis On Thu, Dec 13, 2012 at 3:23 PM, vincentx wrote: > 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 > artifacts in the application. However, each module will have different > goals, mainly, the JAR i want to do a "mvn deploy site", and the WAR and > EAR > modules just a "mvn install". Since Jenkins only cares about the parent > pom > is there a way to specify in that pom what goals I want run on each module? > Or is there something I have to do in the module pom files? Any help or > suggestions are appreciated. Thanks! > > > > -- > View this message in context: > http://maven.40175.n5.nabble.com/Maven-and-Jenkins-question-tp5738064.html > Sent from the Maven - Users mailing list archive at Nabble.com. > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > >
Maven and Jenkins question
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 artifacts in the application. However, each module will have different goals, mainly, the JAR i want to do a "mvn deploy site", and the WAR and EAR modules just a "mvn install". Since Jenkins only cares about the parent pom is there a way to specify in that pom what goals I want run on each module? Or is there something I have to do in the module pom files? Any help or suggestions are appreciated. Thanks! -- View this message in context: http://maven.40175.n5.nabble.com/Maven-and-Jenkins-question-tp5738064.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Surefire 2.13 close to release, last chance to give feedback !
Thanks for the fix, works like a charme :-). Regards Mirko On Thu, Dec 13, 2012 at 2:18 PM, Kristian Rosenvold wrote: > Thanks for testing ! > > No need for an issue this time, I will fix real soon. > > > Kristian > > > > > 2012/12/13 Mirko Friedenhagen : >> 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 invoking test runs >> only in Netbeans, however, it uses the XML output, so reporting and >> running tests from the still works. >> >> For humans the stacktraces look IMO better, though :-). >> Should I open an issue? >> >> Regards Mirko >> >> On Tue, Dec 11, 2012 at 5:02 PM, Kristian Rosenvold >> wrote: >>> The current 2.13-SNAPSHOT is functionally pretty close to what will be >>> the staged version for release. >>> >>> Most users (especially JUnit 4.x users) should appreciate the heavily >>> revised summary of which tests failed during a test run and improved >>> stacktrace trimming. >>> >>> So if you want to give this version a spin, this is effectively the >>> last chance for feedback before we stage the 2.13 release. If you do >>> test it, make sure you break some tests to check the new output ;) >>> Feedback/problems here or at https://jira.codehaus.org/browse/SUREFIRE >>> >>> Kristian >>> >>> - >>> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org >>> For additional commands, e-mail: users-h...@maven.apache.org >>> >> >> - >> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org >> For additional commands, e-mail: users-h...@maven.apache.org >> > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Release plugin & ${project.version} dependencies
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 your MSI config is changed, does that require a new project-main?
So I understand why it was implemented like this.
You could change the value for allowTimestampedSnapshots[1] to true, but
then you've lost the check for all snapshots.
What you could probably do is combine this with the enforcer rule called
RequireReleaseDependencies[2] (have never done this myself though).
Robert
[1]
http://maven.apache.org/plugins/maven-release-plugin/prepare-mojo.html#allowTimestampedSnapshots
[2] http://maven.apache.org/enforcer/enforcer-rules/requireReleaseDeps.html
Op Thu, 13 Dec 2012 13:51:06 +0100 schreef Dan Godfrey
:
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 they would be updated to non-SNAPSHOT dependencies in a
later
phase.
I was wondering if anybody knows of anyway to get around this?
To explain why: I have 2 separate projects project-main &
project-windows.
project-main is a jar (well multiple jars)which are deployed to our local
repo. project-windows then takes that deployed jar and packages it up as
an
MSI. Both of these projects are kept in lockstep with regards version
numbers and have separate CI jobs. I've split the 2 projects up in
different SCM repos like this as we have have other CI jobs depending on
project-main for testing, and potentially in the future a project-linux,
etc.
Thanks,
Dan.
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: deploy plugin in offline mode
Fedora packaging for example, enforces offline mode. On Thu, Dec 13, 2012 at 3:29 PM, Anders Hammar 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 > complicated and painful than necessary. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven 3.0.4 + Maven Project + Modules
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 pom files that are in the reactor during the > course of the build (not encouraged but possible... I've heard of people > doing crazy stuff with my versions-m-p) in which case the files on disk > differ from the in-memory model that the build is working from and you will > generate inconsistent results. > > Trust me, if you want a stable build and to write a good plugin, resolve > from the reactor if available first > > > On 13 December 2012 13:13, Marcos Mendez wrote: > >> 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 parsed >> the pom files myself for what i need... >> >> On Dec 13, 2012, at 7:14, Stephen Connolly < >> stephen.alan.conno...@gmail.com> wrote: >> >>> 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 wrote: >>> 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 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 wrote: > >> >> 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 go up, but I need to be able to get the child modules as >> projects and repeat the process recursively. >> - >> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org >> For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org >> >> - >> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org >> For additional commands, e-mail: users-h...@maven.apache.org >> >> - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: deploy plugin in offline mode
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 wrote: > 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 wrote: > > 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, would be my advice. > > > > /Anders > > > > > > On Thu, Dec 13, 2012 at 1:57 PM, Alon Bar-Lev > wrote: > > > >> On Thu, Dec 13, 2012 at 3:33 AM, Wayne Fay 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 unavailable when you are offline. > >> > >> Hmmm... thanks... but I don't control the build nor can I install more > >> dependencies on the build machine. Modifying every project to have > >> extra hierarchy just to be able to use the dependency plugin is also > >> intrusive and complex. > >> > >> I just need to deploy artifacts in maven repository layout... I > >> expected it to be simple... as the deploy plugin does exactly that... > >> :( > >> > >> Alon. > >> > >> - > >> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > >> For additional commands, e-mail: users-h...@maven.apache.org > >> > >> > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > >
Re: deploy plugin in offline mode
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 wrote: > 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, would be my advice. > > /Anders > > > On Thu, Dec 13, 2012 at 1:57 PM, Alon Bar-Lev wrote: > >> On Thu, Dec 13, 2012 at 3:33 AM, Wayne Fay 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 unavailable when you are offline. >> >> Hmmm... thanks... but I don't control the build nor can I install more >> dependencies on the build machine. Modifying every project to have >> extra hierarchy just to be able to use the dependency plugin is also >> intrusive and complex. >> >> I just need to deploy artifacts in maven repository layout... I >> expected it to be simple... as the deploy plugin does exactly that... >> :( >> >> Alon. >> >> - >> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org >> For additional commands, e-mail: users-h...@maven.apache.org >> >> - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven 3.0.4 + Maven Project + Modules
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 wrote: > 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 parsed > the pom files myself for what i need... > > On Dec 13, 2012, at 7:14, Stephen Connolly < > stephen.alan.conno...@gmail.com> wrote: > > > 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 wrote: > > > >> 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 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 > >> wrote: > >>> > > 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 go up, but I need to be able to get the child modules as > projects and repeat the process recursively. > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > >> > >> > >> - > >> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > >> For additional commands, e-mail: users-h...@maven.apache.org > >> > >> > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > >
Re: Maven 3.0.4 + Maven Project + Modules
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 doing crazy stuff with my versions-m-p) in which case the files on disk differ from the in-memory model that the build is working from and you will generate inconsistent results. Trust me, if you want a stable build and to write a good plugin, resolve from the reactor if available first On 13 December 2012 13:13, Marcos Mendez wrote: > 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 parsed > the pom files myself for what i need... > > On Dec 13, 2012, at 7:14, Stephen Connolly < > stephen.alan.conno...@gmail.com> wrote: > > > 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 wrote: > > > >> 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 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 > >> wrote: > >>> > > 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 go up, but I need to be able to get the child modules as > projects and repeat the process recursively. > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > >> > >> > >> - > >> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > >> For additional commands, e-mail: users-h...@maven.apache.org > >> > >> > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > >
Re: deploy plugin in offline mode
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, would be my advice. /Anders On Thu, Dec 13, 2012 at 1:57 PM, Alon Bar-Lev wrote: > On Thu, Dec 13, 2012 at 3:33 AM, Wayne Fay 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 unavailable when you are offline. > > Hmmm... thanks... but I don't control the build nor can I install more > dependencies on the build machine. Modifying every project to have > extra hierarchy just to be able to use the dependency plugin is also > intrusive and complex. > > I just need to deploy artifacts in maven repository layout... I > expected it to be simple... as the deploy plugin does exactly that... > :( > > Alon. > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > >
Re: Surefire 2.13 close to release, last chance to give feedback !
Thanks for testing ! No need for an issue this time, I will fix real soon. Kristian 2012/12/13 Mirko Friedenhagen : > 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 invoking test runs > only in Netbeans, however, it uses the XML output, so reporting and > running tests from the still works. > > For humans the stacktraces look IMO better, though :-). > Should I open an issue? > > Regards Mirko > > On Tue, Dec 11, 2012 at 5:02 PM, Kristian Rosenvold > wrote: >> The current 2.13-SNAPSHOT is functionally pretty close to what will be >> the staged version for release. >> >> Most users (especially JUnit 4.x users) should appreciate the heavily >> revised summary of which tests failed during a test run and improved >> stacktrace trimming. >> >> So if you want to give this version a spin, this is effectively the >> last chance for feedback before we stage the 2.13 release. If you do >> test it, make sure you break some tests to check the new output ;) >> Feedback/problems here or at https://jira.codehaus.org/browse/SUREFIRE >> >> Kristian >> >> - >> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org >> For additional commands, e-mail: users-h...@maven.apache.org >> > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven 3.0.4 + Maven Project + Modules
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 parsed the pom files myself for what i need... On Dec 13, 2012, at 7:14, Stephen Connolly wrote: > 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 wrote: > >> 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 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 >> wrote: >>> 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 go up, but I need to be able to get the child modules as projects and repeat the process recursively. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org >> >> >> - >> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org >> For additional commands, e-mail: users-h...@maven.apache.org >> >> - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: deploy plugin in offline mode
On Thu, Dec 13, 2012 at 3:33 AM, Wayne Fay 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 unavailable when you are offline. Hmmm... thanks... but I don't control the build nor can I install more dependencies on the build machine. Modifying every project to have extra hierarchy just to be able to use the dependency plugin is also intrusive and complex. I just need to deploy artifacts in maven repository layout... I expected it to be simple... as the deploy plugin does exactly that... :( Alon. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Release plugin & ${project.version} dependencies
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 they would be updated to non-SNAPSHOT dependencies in a later
phase.
I was wondering if anybody knows of anyway to get around this?
To explain why: I have 2 separate projects project-main & project-windows.
project-main is a jar (well multiple jars)which are deployed to our local
repo. project-windows then takes that deployed jar and packages it up as an
MSI. Both of these projects are kept in lockstep with regards version
numbers and have separate CI jobs. I've split the 2 projects up in
different SCM repos like this as we have have other CI jobs depending on
project-main for testing, and potentially in the future a project-linux,
etc.
Thanks,
Dan.
Re: Maven 3.0.4 + Maven Project + Modules
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 wrote: > 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 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 > wrote: > > > >> > >> 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 go up, but I need to be able to get the child modules as > >> projects and repeat the process recursively. > >> - > >> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > >> For additional commands, e-mail: users-h...@maven.apache.org > >> > >> > > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > >
Re: Surefire 2.13 close to release, last chance to give feedback !
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 invoking test runs only in Netbeans, however, it uses the XML output, so reporting and running tests from the still works. For humans the stacktraces look IMO better, though :-). Should I open an issue? Regards Mirko On Tue, Dec 11, 2012 at 5:02 PM, Kristian Rosenvold wrote: > The current 2.13-SNAPSHOT is functionally pretty close to what will be > the staged version for release. > > Most users (especially JUnit 4.x users) should appreciate the heavily > revised summary of which tests failed during a test run and improved > stacktrace trimming. > > So if you want to give this version a spin, this is effectively the > last chance for feedback before we stage the 2.13 release. If you do > test it, make sure you break some tests to check the new output ;) > Feedback/problems here or at https://jira.codehaus.org/browse/SUREFIRE > > Kristian > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven 3.0.4 + Maven Project + Modules
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 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 wrote: > >> >> 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 go up, but I need to be able to get the child modules as >> projects and repeat the process recursively. >> - >> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org >> For additional commands, e-mail: users-h...@maven.apache.org >> >> - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven 3.0.4 + Maven Project + Modules
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 wrote: > > 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 go up, but I need to be able to get the child modules as > projects and repeat the process recursively. > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > >
Maven 3.0.4 + Maven Project + Modules
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 go up, but I need to be able to get the child modules as projects and repeat the process recursively. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
