Le Tue, 12 Oct 2010 19:35:46 -0500,
Kenneth McDonald a écrit :
> Yes, I realize this is flamebait, but after trying to puzzle out the
> following maven plugin:
>
>
> maven-antrun-plugin
> 1.6
>
>
>
On Oct 12, 2010, at 10:01 PM, Martin Gainty wrote:
> Suprisingly maven is not the first programming language to use XML
This is worth clarifying. What makes Maven unique, and I believe
groundbreaking, is that the POM is declarative, not procedural. It is not a
programming language in the tra
Think of maven is a way to declare operations and attributes to acheieve tasks
in a build environment using XML
Suprisingly maven is not the first programming language to use XML
ColdFusion is composed of XML declarative descriptors to express operations
thru element descriptors and operators as
> Yes, I realize this is flamebait, but after trying to puzzle out the
> following maven plugin:
>
>
> maven-antrun-plugin
Write a proper Maven plugin instead of leaning on the antrun plugin to
do your dirty work. They are surprisingly simple to write -- I'm sure
you ca
Using antrun is not Maven
Curt Yanko | Continuous Integration Services | UnitedHealth Group IT
Making IT Happen, one build at a time
-Original Message-
From: Kenneth McDonald [mailto:kenneth.m.mcdon...@sbcglobal.net]
Sent: Tuesday, October 12, 2010 8:
On Tue, Oct 12, 2010 at 8:35 PM, Kenneth McDonald
wrote:
> Yes, I realize this is flamebait, but after trying to puzzle out the
> following maven plugin:
You are complaining about using Ant to execute Git to do something
inside a Maven build? Yeah, that's going to be ugly.
In the event you act
wow, you're wish has almost been granted.
check out polyglot maven.
On Tue, Oct 12, 2010 at 7:35 PM, Kenneth McDonald
wrote:
> Yes, I realize this is flamebait, but after trying to puzzle out the
> following maven plugin:
>
>
> maven-antrun-plugin
> 1.6
Yes, I realize this is flamebait, but after trying to puzzle out the following
maven plugin:
maven-antrun-plugin
1.6
deploy
deploy-gh-pages
Hi all,
is it possible to access the parent POM by means of property interpolation?
While the help:evaluate goal correctly interpolates
${project.parent.url}, using the property in the child POM doesn't
trigger interpolation (in neither Maven 2.2 nor 3.0); the string stays
as is. I could only get
I'm seeing this same problem with a previously working setup.
On Tue, Oct 12, 2010 at 6:42 AM, Joakim Olsson wrote:
> Hi,
>
> I have a problem using shared assemblies after upgrading from version
> 2.2-beta-5 to the newly released version 2.2.
>
> This is my configuration:
>
> maven-
Hi all,
I upgraded to Maven 3 very recently and since then I am experiencing
issues with my proxy definition. It seems like the "nonProxyHosts"
parameter is not honored anymore.
Here is my proxy configuration:
- settings.xml ---
ELCA
true
http
proxy.elca.ch
8080
*.elca
Thanks for that - it's at least useful in getting a report of which
version to put in our pluginManagement section in the parent. The pom
updating doesn't seem to include a goal that will update plugin
versions, but given a list we can do that by hand.
On Tue, Oct 12, 2010 at 12:41 PM, kristian
On Fri, Oct 8, 2010 at 6:45 AM, wrote:
> I work on a portlet project so some dependencies are provided by the portal
> (ie hibernate, spring etc...).
>
> My project has 2 modules :
> -parent
> |_services
> |_ui
>
> Hibernate is a dependency from the services module. The services module is a
>
try
mvn versions:display-plugin-updates
which should give you an overview. there is more to the plugin and it
does insert the versions where needed with one of its goals.
regards Kristian
On Tue, Oct 12, 2010 at 10:00 PM, Patrick Aikens wrote:
> I do agree that from a repeatability standpoint, s
I do agree that from a repeatability standpoint, specifying versions
for ALL plugins is desirable - but since Maven provides a super-pom
that everything inherits from we get certain plugins automatically.
Aside from looking at that pom and basically copying the build.plugins
section there's no simp
Yes, Maven provides default versions, but those are likely to change
as Maven does future patch releases. To give you a predictable build,
lock down your plugins so you control what versions are selected.
Paul
On Tue, Oct 12, 2010 at 10:27 AM, Patrick Aikens wrote:
> I've got several projects th
I've got several projects that provide additional configuration of
standard Maven plugins (like the compiler plugin or the jar plugin),
most commonly changing the source and target values for the compiler
plugin. Unfortunately, I get the following warnings:
[WARNING] 'build.plugins.plugin.version
Hi,
I have a problem using shared assemblies after upgrading from version
2.2-beta-5 to the newly released version 2.2.
This is my configuration:
maven-assembly-plugin
2.2-beta-5
make-base-war
package
si
Hi all,
FYI - I resolved this (was running the plugin report against the wrong project).
Cheers,
Martijn
On Thu, Oct 7, 2010 at 6:41 PM, Martijn Verburg
wrote:
> Hi all,
> I'm pretty sure I must be configuring something wrong in my poms, but the
> plugin update reports is telling me I don't hav
19 matches
Mail list logo
