Ah! I missed that little nugget.
Curt Yanko | Continuous Integration Services | UnitedHealth Group IT
Making IT Happen, one build at a time, 600 times a day
-Original Message-
From: Stephen Connolly [mailto:stephen.alan.conno...@gmail.com]
Sent: Tuesd
On 08 Nov 2010, at 7:03 PM, jhumble wrote:
Two reasons: one, the faster you get feedback on the part of the
story you
have done so far, the faster you know if any further work is going
to be
valuable, and what in fact the next most valuable thing to deliver is.
How do you handle branches?
Thanks Oliver.
I think that it'll be quite a while before people write MOJOs just for Maven 3.
From my own perspective having just written two new MOJOs, I'd like to be able
to write for the future but recognise the present. It'd be great to use @inject
in my code now and then use the MOJO with
Jesse Glick wrote:
I am interested in experimenting with whether a plugin running in Maven
3 and declared as a build extension can *replace* a standard service.
Not possible.
I would like to replace DefaultProjectDependenciesResolver
with a variant that behaves specially on certain kinds of
Hi,
Using @Inject will work only with maven 3. You can inject a Plexus
composent using it.
But not sure it's a good design to mix stuff.
2010/11/10 Christopher Hunt :
> Hi there,
>
> Is it possible to develop MOJOs with JSR-330 dependency injection, and
> thereby not depend on Plexus? If so then
Hi there,
Is it possible to develop MOJOs with JSR-330 dependency injection, and thereby
not depend on Plexus? If so then will Maven 2 be able to host JSR-330 MOJOs?
There's not a lot of doco on this... all that I could find was how to write a
MOJO using Plexus:
http://maven.apache.org/guides/
I am interested in experimenting with whether a plugin running in Maven 3 and declared as a build extension can *replace* a standard service. In particular, I would like
to replace DefaultProjectDependenciesResolver with a variant that behaves specially on certain kinds of dependency artifacts (do
By decouple, I mean decouple failing from running... i.e. run tests, run
tests, check tests, check tests... Not run tests, check tests, run tests,
check tests
On 9 Nov 2010 21:43, "Bogdan Calmac" wrote:
No, I don't necessarily want to decouple the tests from the build. It's also
OK if the build
Hi,
I am using Maven 2.2.1 and mave-site-plugin 2.1.1. When I run 'maven site', it
gives me an error on parsing my APT file on table generation. It is stopped on
the first line where I defined the table with
*--++ +
|
*--
...
This used to wo
No, I don't necessarily want to decouple the tests from the build. It's also
OK if the build fails after running only the mssql tests. The only thing is
that I don't want the build to succeed when after of the test executions
failed.
--
View this message in context:
http://maven.40175.n5.nabble.
I have used profiles activated by the presence of the pom.xml file in
the sub-module
so you have
if A/pom.xml exists then add module A
if B/pom.xml exists then add module B
-Stephen
On 9 November 2010 20:59, Ben Caradoc-Davies
wrote:
> You can use profiles to enable the optional building of su
You might be better served with the maven-failsafe-plugin as you want
to decouple running tests from failing the build (i.e. you want to run
all tests and then fail the build)
Also, if you are using a real database, they sound more like
integration tests... again a use case for m-f-p
But having s
Our project is configured to run the unit tests twice, with oracle and mssql
databases. This is achieved by configuring two executions of the surefire
plugin and passing in a different system property. Here is the relevant
snippet from the POM:
org.apache.maven.plugins
But if we do it my way, the tag has the resolved versions, while trunk keeps
the ranges... Best of all worlds ;-)
On 9 Nov 2010 16:21, "Yanko, Curtis" wrote:
Because I thought we want to keep the version ranges in SCC for developers
and just package the POM fully versioned for that build.
___
You can use profiles to enable the optional building of submodules (you
can use a top-level aggregating pom if the projects are distinct). Note
that, if you have built a module locally, maven will use the version
from your local repo if it is newer than a deployed version. If not
built locally,
What you want can be achieved by having one big aggregator that contains all
your modules and your ears, and use the reactor feature.
By typing mvn -pl my-project:app -am, where my-project:app is the groupId of
your ear, you will actually build the ear and all its transitive
dependencies accross y
I currently work on a large enterprise app built with Ant. The app is
divided into several projects divided into functional areas. In order
to build the entire EAR, all of the projects have to be built, even if
you're only working on a single one of those projects.
I'm examining how we could m
On Tue, Nov 9, 2010 at 8:34 AM, jon.mithe wrote:
>
> Interesting. I think I have found some unpacking elements in the assembly
> plugin when I write my own descriptor. So it may be possible... needs more
> research.
>
> I think I understand what you are saying about separating the config from
>
On Tue, Nov 9, 2010 at 12:30 PM, Frederic Camblor wrote:
> -DupdateWorkingCopyVersion=false doesn't solve the problem.
>
> Just filed a JIRA : http://jira.codehaus.org/browse/MRELEASE-612
I linked it to http://jira.codehaus.org/browse/MRELEASE-335 (and
closed it as a duplicate).
--
Wendy
-
-DupdateWorkingCopyVersion=false doesn't solve the problem.
Just filed a JIRA : http://jira.codehaus.org/browse/MRELEASE-612
On Mon, Nov 8, 2010 at 11:35 PM, Jon Paynter wrote:
>
> I ran into simmilar behavior when trying to persuade the plugin to make me
> a
> new branch. The plugin seems to
On Tue, Nov 9, 2010 at 11:53 AM, Trevor Paterson
wrote:
> the main .jar deploys ok,
> then the -sources.jar deploys ok,
> but then an attempt is made to deploy the -sources.jar a second time:
> causing a build failure
That's not normal. What version of Maven are you using? Is there
anything in
Hi
Can anyone tell me if I can change the deploy configuration to prevent
this
In a multi-module project I am getting problems deploying multiple release
artifacts (each module builds 3 artifacts for deployment: .jar,
-sources.jar and -javadoc.jar )
running> mvn release:prepare release:per
Because I thought we want to keep the version ranges in SCC for developers and
just package the POM fully versioned for that build.
Curt Yanko | Continuous Integration Services | UnitedHealth Group IT
Making IT Happen, one build at a time, 600 times a day
Interesting. I think I have found some unpacking elements in the assembly
plugin when I write my own descriptor. So it may be possible... needs more
research.
I think I understand what you are saying about separating the config from
the binaries. But I'm not sold on the idea of creating it in
We've just discovered a Google App Engine app called pomyard abusing
several repos. Based on the behavior and name of the service, I have
reason to believe they may be attempting to scrape public all maven
repos not just central, ignoring robots.txt. If you have a public
repo, I suggest you block t
Why bother... the checkin is automatic and actually a good thing IMHO
On 9 November 2010 15:37, Yanko, Curtis wrote:
> What if you just avoid the check in? Only package the pom and deploy the jar?
>
>
>
>
> Curt Yanko | Continuous Integration Services | UnitedHea
What if you just avoid the check in? Only package the pom and deploy the jar?
Curt Yanko | Continuous Integration Services | UnitedHealth Group IT
Making IT Happen, one build at a time, 600 times a day
-Original Message-
From: Stephen Connolly [mailto:
This was precisely where I was headed.
I was thinking about using version ranges in depMgmnt and *burning lots
of versions in the CI process but having a release plugin that ID's the
version retrieved and re-wrote the POM to be version specific at package
time.
I'm drawn to the idea of using an
Yes, and that doesn't describe our case.
Company wide parent pom, similar to the ASF parent pom. is a separate
svn project, not linked from any reactor.
Project specific parent pom with submodules. Project parent pom
extends company wide parent pom.
New release of company wide parent pom : going
Create a separate project for the config. In Maven, one project = one
artifact. Sure, you can create additional artifacts, but that's the golden
rule.
/Anders
On Tue, Nov 9, 2010 at 15:35, jon.mithe wrote:
>
> Thanks for the reply. Yeah that is what I am trying to achieve. So there
> are no
On 9 November 2010 14:10, Thiessen, Todd (Todd) wrote:
> Hey Stephen. I read through your idea a little more closely and I like it.
>
> The only thing I think it is missing is the ability to use snapshots as
> dependencies. That is a very powerful feature of maven that I don't think
> you'd want
Ok, there's no hierarchy in a parent project..
I try to apply your recommendations, thanks for your help,
Jeremy.
--
View this message in context:
http://maven.40175.n5.nabble.com/Eclipse-multi-module-project-with-maven-tp3256822p3256891.html
Sent from the Maven - Users mailing list archive a
Have you go through
https://cwiki.apache.org/MAVEN/maven-3x-compatibility-notes.html#Maven3.xCompatibilityNotes-ParentPOMResolution
On Nov 9, 2010 4:37 PM, "mjsell" wrote:
>
> I ran into this today when trying to move to Maven 3.. any news? Has a
> ticket been written?
> --
> View this message in
Thanks for the reply. Yeah that is what I am trying to achieve. So there
are no configuration files within the jars and I'm trying to keep the
configs in the extra folder on the side. As far as I'm aware maven can only
produce one artifact from the module during the build, so the only way I ca
>
> Does anyone have a reason why Maven snapshots would be useful or
> necessary
> to a project following CD?
>
>From what I am understanding from Jez is that it is crucial that your CI built
>with snapshots isn't "wasted". That you can treat that build as a release
>without having to rebuild.
maven-appassembler-plugin? maven-dependency-plugin, especially
combined with a MANIFEST.MF class path?
On Tue, Nov 9, 2010 at 8:31 AM, Jacob Beard wrote:
>
> On 10-11-09 02:25 PM, Benjamin Bentmann wrote:
>>
>> Jacob Beard wrote:
>>
>>> With maven, however, the libraries are now kept in the locat
Hi,
I'm a new user of maven.. I've seen part of response at my question, but
never exactly got
what I expect.
So, before introducing maven into my project, I had 3 differents projects.
The Api, a batch project, and a web project.
Both web and batch project needs the api.jar to compile.
So, I'v
Hi Ron,
Thanks for the reply.
On 10-11-09 02:06 PM, Ron Wheeler wrote:
If you are using a decent IDE (Eclipse STS for example) with Maven
support, you should not need any of this.
Maven and Eclipse will get everything you need onto the classpath.
My project is a compiler, so I feel that it's
Yes, a parent is a pom project. Your api project is a jar project - it
creates a jar.
So create an aggregating project which can also be the parent project. Then
create three jar projects, which are listed as modules.
There are create resources on the Internet explaining all this.
Regarding Eclip
Ok, I guess there's a confusion speaking about "parent" project..
In my case, web and batch project needs Api jar file to work.. but, I should
not consider the Api project as the parent ?
By the way, if create one aggregating Maven project listing 3 modules..
should I declare the sourceFolder i
I think you should start by separating the configurations from your
binaries. Then it will be so much easier creating the custom zip you want.
You would also avoid having the configuration files duplicated (like outisde
the jars as well as inside some of the jars). That will sooner or later get
you
sure, here it is :
http://maven.apache.org/POM/4.0.0";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
http://maven.apache.org/xsd/maven-4.0.0.xsd";>
4.0.0
fr.gouv.finances.douane.dnsce.mavenProject
Mave
You should create one aggregating Maven project, which is a pom project
which lists your three modules (api, batch, and web).
Then, in the sub-folders stated by your module names, create the Maven
projects that will be creating your jars.
So, in total you will have four Maven projects. This is wha
On 10-11-09 02:25 PM, Benjamin Bentmann wrote:
Jacob Beard wrote:
With maven, however, the libraries are now kept in the location of the
maven repository, several directories deep, based on information kept in
the pom.xml file. I'd like to know, is there a maven solution for
extracting a parti
Hey Stephen. I read through your idea a little more closely and I like it.
The only thing I think it is missing is the ability to use snapshots as
dependencies. That is a very powerful feature of maven that I don't think you'd
want to lose if your using CD.
It is almost like you'd want a mode i
Hi,
I'm trying to switch over to maven for a project I developing in work, new
to maven and finding packaging it a little tricky.
The app I am writing has a core framework module and then a bunch of other
modules that provide plugin like functionality. The idea being I can
produce different bu
2010/11/9 jeb001 :
> In my case, web and batch project needs Api jar file to work.. but, I should
> not consider the Api project as the parent ?
No, it's a dependency.
> By the way, if create one aggregating Maven project listing 3 modules..
> should I declare the sourceFolder in the eclipse clas
Thiessen, Todd (Todd) wrote:
>
> Imagine trying to have a CI build while always having enough information
> in the pom to point to an exact version of your dependencies? Lets say I
> get a feature working in my checkout, and do a build locally before
> committing. The build would have to point
Keep your aggregating project clean. Move you build stuff to a separate
module.
/Anders
On Tue, Nov 9, 2010 at 15:02, jeb001 wrote:
>
> sure, here it is :
>
>
> http://maven.apache.org/POM/4.0.0";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
>xsi:schemaLocation="http://maven
I don't use CI or CD, so you can take my opinions with a grain of salt
My understanding that an application that gets to a CD stage, is ready
for testing by human beings.
In order to test an application, people need to know what the system is
supposed to do.
If a person tests a search function
Could you show us the contents of the parent pom.xml?
On Tue, Nov 9, 2010 at 8:37 AM, jeb001 wrote:
>
> Hi,
>
> I'm a new user of maven.. I've seen part of response at my question, but
> never exactly got
> what I expect.
> So, before introducing maven into my project, I had 3 differents projects
Jacob Beard wrote:
With maven, however, the libraries are now kept in the location of the
maven repository, several directories deep, based on information kept in
the pom.xml file. I'd like to know, is there a maven solution for
extracting a particular classpath from a maven file, such that the
On 09/11/2010 9:09 AM, Anders Hammar wrote:
Yes, a parent is a pom project. Your api project is a jar project - it
creates a jar.
So create an aggregating project which can also be the parent project. Then
create three jar projects, which are listed as modules.
There are create resources on the
.
> >
> > I think it is crucial that the release artifact DOES get rebuilt.
>
>
> I think that exactly the opposite is true
I know you "think" that. You're beating a dead horse. But that isn't the point
here. It is crucial for Maven that it gets rebuilt. It is simply the way Maven
is architect
+1 here. Jez was indicating that it was "Crucial" that a snapshot build not get
"rebuilt" when creating the release and simply get promoted to a release. That
is simply not that way maven currently works. I hope that is now clear.
I do like the idea though of rebuilting a CD build after a succes
Hi,
My project is built around Mozilla Rhino, but and I'm transitioning to
maven for the build system. When my project was using ant, I had a task
that would download dependencies to the local lib/ directory in the
project. I then had a shell script that would run the project, including
the r
On 09/11/2010 7:34 AM, Jacob Beard wrote:
Hi,
My project is built around Mozilla Rhino, but and I'm transitioning to
maven for the build system. When my project was using ant, I had a
task that would download dependencies to the local lib/ directory in
the project. I then had a shell script t
On 09/11/2010 9:03 AM, Anders Hammar wrote:
I think you should start by separating the configurations from your
binaries. Then it will be so much easier creating the custom zip you want.
You would also avoid having the configuration files duplicated (like outisde
the jars as well as inside some o
Start by getting it working with Eclipse and Maven.
Tell Maven and Eclipse that you are trying to build a standalone
application when you create the Eclipse project.
It will structure your project so that it builds one with the assets in
the right place to run it.
Points to remember
1) Don't f
In the case of deploy:file, I can hardly add this to the pom file,
can't I? I'd see this as a regression.
On Tue, Nov 9, 2010 at 10:33 AM, Anders Hammar wrote:
> http://lmgtfy.com/?q=maven+3+wagon+scp&l=1
>
> Google rocks! :-)
>
> /Anders
>
> On Tue, Nov 9, 2010 at 10:30, Jochen Wiedmann
> wrot
http://lmgtfy.com/?q=maven+3+wagon+scp&l=1
Google rocks! :-)
/Anders
On Tue, Nov 9, 2010 at 10:30, Jochen Wiedmann wrote:
> Does anyone have an idea, why this one works flawlessly (some
> parameters omitted):
>
> /c/Prg/apache-maven-2.2.1/bin/mvn deploy:deploy-file ...
> -Durl=scp://
> shell.s
Hi Jochen,
This can be probably fixed with adding wagon scp in the deploy plugin
dependencies.
--
Olivier Lamy
http://twitter.com/olamy
http://www.linkedin.com/in/olamy
2010/11/9 Jochen Wiedmann :
> Does anyone have an idea, why this one works flawlessly (some
> parameters omitted):
>
> /c/Prg
Does anyone have an idea, why this one works flawlessly (some
parameters omitted):
/c/Prg/apache-maven-2.2.1/bin/mvn deploy:deploy-file ...
-Durl=scp://shell.sourceforge.net/home/groups/c/cs/csutils/htdocs/repository
But this one doesn't:
/c/Prg/apache-maven-3.0/bin/mvn deploy:deploy-file ...
Oh and I can see the artifact just fine
On 9 November 2010 09:25, Stephen Connolly
wrote:
> It can take a few hours to fully sync if it's more than 24 hours
> after the announcement, then it's time to start screaming!
>
> On 8 November 2010 23:09, Johan Hedin wrote:
>> Maven refuses to build
It can take a few hours to fully sync if it's more than 24 hours
after the announcement, then it's time to start screaming!
On 8 November 2010 23:09, Johan Hedin wrote:
> Maven refuses to build. Version 1.0 of maven-enforcer-plugin in the
> repo1.maven.org is empty.
>
>
> [INFO]
> -
I think some of the issues are around missuse of Maven.
Maven is a build tool, use it to do your build.
CD needs a separate layer above Maven to do the deployment... now one
could use maven plugins to provide that layer, but there are two
issues I see:
1. the maven lifecycle does not include the
What goal did you specify? The plugin exists at Maven central.
/Anders
On Tue, Nov 9, 2010 at 00:09, Johan Hedin wrote:
> Maven refuses to build. Version 1.0 of maven-enforcer-plugin in the
> repo1.maven.org is empty.
>
>
> [INFO]
> --
I can reach the artifact just fine.
Vincent
2010/11/9 Johan Hedin
> Maven refuses to build. Version 1.0 of maven-enforcer-plugin in the
> repo1.maven.org is empty.
>
>
> [INFO]
>
> Downloading:
> http://repo1.maven.org/ma
Hi,
can any of you guys post how to use custom parameters for home-made maven
artifacts?
-How do you define and use custom parameters inside your archetype project
-how do you pass the parameters when using your artifact for generating a
new project?
Thanks,
Kristof
--
View this message in cont
We need to figure out how to best leverage Maven (keeping in mind its process
and practices) in a Continuous Delivery solution. I like the conversation
around this topic and also see that there is this other discussion about the
meaning of CD versus CI.
>From the comments so far, there has been a
Wayne, my thanks and respects.
On Mon, Nov 8, 2010 at 12:03 PM, Wayne Fay wrote:
> > So your code would be like:
> > /*...@parameter default-value="${warSourceDirectory}" */
> > private File warSourceDir;
>
> Hmm actually that's not entirely correct... you may want to just
> inject ${project} an
I think this is an area where NexusPro or the concept of a staging repository
can be helpful. You gladly burn version numbers all through the dev process
and at some point promote a version to the staging repo for "blessed"
deployment. I am not trying to impose a specific point in the pipeline whe
Maven refuses to build. Version 1.0 of maven-enforcer-plugin in the
repo1.maven.org is empty.
[INFO]
Downloading:
http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-enforcer-plugin/1.0/maven-enforcer-plugin-1.0.p
I ran into this today when trying to move to Maven 3.. any news? Has a
ticket been written?
--
View this message in context:
http://maven.40175.n5.nabble.com/M3-fails-to-download-parent-pom-tp3240199p3256007.html
Sent from the Maven - Users mailing list archive at Nabble.com.
-
74 matches
Mail list logo
