Just saw something odd in Gmail web clip/sponsored link while browsing
emails to the list...
"Maven Enterprise Edition - www.overall.ca/maven - Build the ultimate
toolbox for your Windows support tools"
>From their site:
"Introducing Maven Enterprise Edition
Your enterprise data is typically foun
Hi,
The vote has passed with the following result :
+1 (binding): Benjamin Bentmann, Olivier Lamy, John Casey, Arnaud
Heritier, Dennis Lundberg
I will promote the artifacts to the central repo.
Dennis Lundberg wrote:
> Hi,
>
> We solved 12 issues:
> http://jira.codehaus.org/secure/ReleaseNote.j
The Maven team is pleased to announce the release of the Maven Install
Plugin, version 2.3
The Install Plugin is used during the install phase to add artifact(s)
to the local repository.
http://maven.apache.org/plugins/maven-install-plugin/
You should specify the version in your project's plugin
On Mon, Dec 15, 2008 at 10:33 PM, Vincent Siveton
wrote:
>> So am I right in that the namespace for assembly xml files should be
>>
>> > xmlns="http://maven.apache.org/plugins/maven-assembly-plugin/assembly/1.1.0";
>> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
>> xsi:schemaLocation="ht
Thanks Jason and Dennis!
-Original Message-
From: Jason Chaffee [mailto:jason.chaf...@zilliontv.tv]
Sent: Wednesday, March 25, 2009 1:51 PM
To: Maven Developers List
Subject: RE: Maven 2.1.0 regression issue w/ testResources
outputDirectory
I believe this is a parameter for the plugin c
This IT is failing in my environment:
container-descriptors\custom-containerDescriptorHandler
I can't find any documentation to help work out what the following in
the assembly configuration means:
file.txt
Anyone else got this problem?
---
I don't think so, but you can get your hands on the
RuntimeInformation.ROLE component. Bear in mind it will almost
certainly cause your plugin to get broken in Maven 3.0 though.
- Brett
On 26/03/2009, at 6:20 AM, Paul Gier wrote:
That's true, I can get the OS and Java version from standard
I've had a quick try on one of my projects and it seems to work fine for me.
SaM
On Thu, Mar 26, 2009 at 5:51 AM, Brian E. Fox wrote:
> I tried a build with -N (non recursive) and I get an error with 2.1.0:
>
>
>
> [INFO] Parent project loaded from repository.
>
> [INFO]
> --
+1
Dennis Lundberg wrote:
> Hi,
>
> We solved 12 issues:
> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11136&styleName=Html&version=13495
>
> There are still a couple of issues left in JIRA:
> http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=11136&status=1
>
> S
outputDirectory is a plugin configuration parameter.
See this page for how it can be used:
http://maven.apache.org/plugins/maven-resources-plugin/examples/copy-resources.html
Steve Ariantaj wrote:
> Thanks for your quick reply, Benjamin.
>
> According to the resource plugin v2.3,
> http://maven.
I believe this is a parameter for the plugin configuration itself. For example,
...
org.apache.maven.plugins
maven-resources-plugin
...
foo/bar
...
...
...
-Original Message-
From: Ste
Steve Ariantaj wrote:
According to the resource plugin v2.3,
http://maven.apache.org/plugins/maven-resources-plugin/testResources-mojo.html
there is a required outputDirectory parameter:
http://maven.apache.org/plugins/maven-resources-plugin/testResources-mojo.html#outputDirectory
The mojo p
It happened on the enforcer plugin parent. I was testing the upgraded
repo so I changed the tlp to a release test version, then did mvn deploy
-N. I tried again later and got the same behavior with 2.0.10 so it's
not a regression in 2.1 but I've yet to check 2.0.9
-Original Message-
From:
Not a property, but there's a component - RuntimeInformation iirc that
has it. Take a look at the enforcer:display-info goal code, it shows all
of it for you.
-Original Message-
From: Paul Gier [mailto:pg...@redhat.com]
Sent: Wednesday, March 25, 2009 3:21 PM
To: Maven Developers List
Sub
fwiw, that is working for me on 2.1 and jetty for parent pom and project pom
jesse
--
jesse mcconnell
jesse.mcconn...@gmail.com
On Wed, Mar 25, 2009 at 12:20 PM, John Casey wrote:
> File it, and if you have a test project setup that we can use to duplicate
> it, we'll take a look. That's the
On Mon, Mar 9, 2009 at 3:31 PM, Lukas Theussl wrote:
> Rémy Sanlaville wrote:
>> Otherwise three possible improvements:
>> 1. Why it's a (build) plugin and not a report plugin ?
>
> I have no strong opinion for or against either but I guess we'll have to pin
> it down for the first release. Open
Thanks for your quick reply, Benjamin.
According to the resource plugin v2.3,
http://maven.apache.org/plugins/maven-resources-plugin/testResources-moj
o.html
there is a required outputDirectory parameter:
http://maven.apache.org/plugins/maven-resources-plugin/testResources-moj
o.html#outputDire
File it, and if you have a test project setup that we can use to
duplicate it, we'll take a look. That's the best I can tell you...the
console output you included really isn't much to go on.
Sorry,
-john
Brian E. Fox wrote:
I tried a build with -N (non recursive) and I get an error with 2.1.
That's true, I can get the OS and Java version from standard properties, and
then put them in the Manifest or somewhere else. Is there a property that
contains the current running version of maven?
Brian E. Fox wrote:
It seems like if there were some properties available, or known to the
reso
Steve Ariantaj wrote:
I'm getting the following error with maven 2.1.0. Pom chunk pasted
below.
${project.build.testOutputDirectory}
Did outputDirectory element's name/order got changed in 2.1.0? This was
working fine in 2.0.9.
Compare the Maven Model Reference [0]:
I tried a build with -N (non recursive) and I get an error with 2.1.0:
[INFO] Parent project loaded from repository.
[INFO]
[ERROR] BUILD ERROR
[INFO]
Shane Isbell wrote:
In the Jira issue, John mentioned changing in
the Boolean to String, which would solve the problem here.
+1
John's own concern with this approach was backward-compat with the
existing plugins but I think we can keep compat by following the same
pattern that Brett used to
I thought I would raise this on the general list since it could involve API
changes in the Maven Model for Maven 3.0. I've run into a situation where
Boolean values in Maven model are causing problems with interpolation.The
general issue is here: http://jira.codehaus.org/browse/MNG-1995
I've put i
I'm getting the following error with maven 2.1.0. Pom chunk pasted
below.
${project.build.testOutputDirectory}
Did outputDirectory element's name/order got changed in 2.1.0? This was
working fine in 2.0.9.
[INFO] Scanning for projects...
[INFO]
---
It seems like if there were some properties available, or known to the
resources plugin, then you could filter these values in anywhere you
wanted them.
-Original Message-
From: Paul Gier [mailto:pg...@redhat.com]
Sent: Wednesday, March 25, 2009 11:54 AM
To: Maven Developers List
Subject:
On Tuesday 24 March 2009 07:20:54 pm Jason Voegele wrote:
> On Tuesday 24 March 2009 06:08:16 pm Raphaël Piéroni wrote:
> > I just uploaded a new version of the 2.0-a-5 snapshot on the apache
> > snapshot repository.
> > Please try it "mvn
> > org.apache.maven.plugins:maven-archetype-plugin:2.0-alp
MWAR-187
On Wed, Mar 25, 2009 at 9:40 AM, Stephane Nicoll
wrote:
> Is there a Jira issue for this? If not, can you create one?
>
> Thanks,
> Stéphane
>
> On Wed, Mar 25, 2009 at 8:36 AM, nicolas de loof
> wrote:
>
> > Hi
> > here is a more detailled trace building the webapp with 2.1-beta-1 :
>
I'd like to be able to record the build environment (maven version, java, OS,
etc) for each build that is run in a standard way. I originally created a jira
issue in the release plugin (MRELEASE-352) to record information just for
releases. But now I'm thinking that this could be useful for an
Is there a Jira issue for this? If not, can you create one?
Thanks,
Stéphane
On Wed, Mar 25, 2009 at 8:36 AM, nicolas de loof
wrote:
> Hi
> here is a more detailled trace building the webapp with 2.1-beta-1 :
>
>
>
>
>org.apache.maven.plugins
> maven-war-plugin
>
Hi
here is a more detailled trace building the webapp with 2.1-beta-1 :
org.apache.maven.plugins
maven-war-plugin
2.1-beta-1
bios-pdc
Let me know any other usefull info I could provide
mvn package -V -e -X
+ Error stacktrace
Nicolas,
You can disable the caching system and it will work. This is still an
alpha/beta feature (hence the reason why I was reluctant to call it 2.1 when
we cast the war plugin vote)
See http://maven.apache.org/plugins/maven-war-plugin/war-mojo.html#useCache
I'll try to find some time to final
31 matches
Mail list logo
