Hi Jason,
Any chance if these session recordings will be available to the wider
community after EclipseCon, ApacheCon?
Thanks,
Rahul
On 12/03/2009 10:34 a.m., Jason van Zyl wrote:
Hi,
For those interested in knowing what Sonatype is working on in the
Maven community, we're having a Maven
Hi,
For those interested in knowing what Sonatype is working on in the
Maven community, we're having a Maven Meetup the week before
EclipseCon in Mountain View.
It's a full day of presentations on Maven and related technologies
like m2eclipse, Nexus, Tycho, Hudson, NMaven, NAR, FlexMojos
It would have, except I used 2.1.0-M1 last time for the release and
2.0.10 this time...at least, I think that's why.
Also, last time I had the blessed copy of the POMs...this branch was
created as a copy of the RC1 tag, though, which is another mistake. The
code was the same, but the versions
Dan,
Can you run help:all-profiles and maybe help:active-profiles with the
config below to verify that the warning is misplaced? If so, please file
the information in a JIRA issue and let me know...I'll take a look tomorrow.
Thanks,
-john
Dan Tran wrote:
My build shows a WARNING on a profi
My build shows a WARNING on a profile not activated even thou the
profile I specified on command actual did run
C:\dev\fortidb\3.2-dev\fdb-java\fdb-config>mvn test -Pdb2
[INFO] Scanning for projects...
[WARNING]
Profile with id: 'db2' has not been activated.
On Wed, Mar 11, 2009 at 5:1
I've tested RC1 and it worked fine w/o any issues.
I will test this version shortly against one of our more complex
projects.
-Original Message-
From: John Casey [mailto:jdca...@commonjava.org]
Sent: Wednesday, March 11, 2009 4:50 PM
To: Maven Developers List
Subject: [PLEASE TEST] Maven
On 12/03/2009, at 8:15 AM, jdca...@apache.org wrote:
Also, fixing a problem where the version-expression transformation
chokes on invalid POMs from the repository during invoker:install.
Shouldn't that have choked earlier?
- Brett
--
Brett Porter
br...@apache.org
http://blogs.exist.com/bpo
Hi again,
I've corrected the four or five issues that popped up in the last couple
days. The new RC is here:
http://tinyurl.com/maven-2-1-0-RC2
(https://repository.apache.org/content/repositories/maven-staging-4f0666d7c70a11/org/apache/maven/apache-maven/2.1.0-RC2)
Again, let me know if you h
Hi Paul
Depending on what you need, this is not entirely trivial. If you just want to
set property 'foo' to value 'bar', then the approach below is just fine. But say
you have a property 'baz' in your pom like this:
xx${foo}xx
And you want 'baz' to evaluate to 'xxbarxx', then you need a b
Le mercredi 11 mars 2009 19:24:20, Nord, James a écrit :
> The following will set a variable I_WAS_HERE to "true".
Thanks, that's what I was looking for.
Simple :)
Paul
> /**
> * Goal which stores some properties
> *
> * @goal getProperty
> * @phase validate
> */
> The following gets the m
Le mercredi 11 mars 2009 19:21:45, Paul Gier a écrit :
> Maybe the properties maven plugin does something similar to what you want.
> http://mojo.codehaus.org/properties-maven-plugin/
I was not aware of this one, thanks for the pointer it can be usefull !
Here the fault : http://repo1.maven.org/maven2/bcel/bcel/5.1/bcel-5.1.pom
--
Olivier
2009/3/11 John Casey :
> Could it be that the gwt-maven-plugin has a block that looks like this:
>
>
> blah
> ...
>
> It looks like a groupId nested immediately inside the dependencies
> collection element...t
Could it be that the gwt-maven-plugin has a block that looks like this:
blah
...
It looks like a groupId nested immediately inside the dependencies
collection element...that would be an invalid structure.
-john
Olivier Lamy wrote:
Hi,
No issue here with company builds.
But I can't bui
Hi,
No issue here with company builds.
But I can't build the gwt-maven-plugin
(https://svn.codehaus.org/mojo/trunk/mojo/gwt-maven-plugin)
mvn clean install -Prun-its
[ERROR] BUILD ERROR
[INFO]
[INFO] Failed to install projec
The following will set a variable I_WAS_HERE to "true".
/**
* Goal which stores some properties
*
* @goal getProperty
* @phase validate
*/
The following gets the maven version and stores it as the maven.version
property.
public class MavenPropertiesMojo extends AbstractMojo {
/**
Maybe the properties maven plugin does something similar to what you want.
http://mojo.codehaus.org/properties-maven-plugin/
Paul wrote:
I need to write a mojo that reads some data and makes it available in the pom
as ${properties}.
Is there a way to achieve this ?
--
I need to write a mojo that reads some data and makes it available in the pom
as ${properties}.
Is there a way to achieve this ?
Please. 2.1.0-RC1 is ideal. Most people will interpret a 2.1.0 as a
release.
Christian
On Mar 11, 2009, at 11:45 AM, Brian E. Fox wrote:
I would change the tag.
-Original Message-
From: John Casey [mailto:jdca...@commonjava.org]
Sent: Wednesday, March 11, 2009 8:22 AM
To: Maven De
The Maven team is pleased to announce the release of the Maven Site
Plugin, version 2.0
The Site Plugin is used to generate a site for the project. The
generated site also includes the project's reports that were configured
in the section of the POM.
http://maven.apache.org/plugins/maven-site-pl
I would change the tag.
-Original Message-
From: John Casey [mailto:jdca...@commonjava.org]
Sent: Wednesday, March 11, 2009 8:22 AM
To: Maven Developers List
Subject: Re: [PLEASE TEST] Maven 2.1.0-RC1
Mistake on my part. I realized it when I started working on the bugfixes
described in
Hi,
The vote has passed with the following result :
+1 (binding): Vincent Siveton, Benjamin Bentmann, Hervé Boutemy, Olivier
Lamy, Lukas Theussl, Dennis Lundberg
+1 (non binding): Fabrice Bellingard
I will promote the artifacts to the central repo.
Dennis Lundberg wrote:
> Hi,
>
> We solved 24
On 12/03/2009, at 2:22 AM, John Casey wrote:
Mistake on my part. I realized it when I started working on the
bugfixes described in this thread. Sorry for the confusion. I'll
amend the tag, too, if you want...just so it's not sitting out there
as 2.1.0.
I don't think that matters too much,
+1
Dennis Lundberg wrote:
> Hi,
>
> We solved 24 issues:
> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11146&styleName=Html&version=13362
>
> There are still a couple of issues left in JIRA:
> http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=11146&status=1
>
> S
Mistake on my part. I realized it when I started working on the bugfixes
described in this thread. Sorry for the confusion. I'll amend the tag,
too, if you want...just so it's not sitting out there as 2.1.0.
-john
Brett Porter wrote:
Just been generally using it and no additional problems.
J
Hi all
How can I set default entries in a list in a custom plugin?
/**
* @parameter default-value="foo,bar,foobar"
*/
private List myList;
I tried different ways, but all I got is this error:
Cause: Cannot assign configuration entry 'myList' to 'interface java.util.List' from 'null', which i
2009/3/11 Brett Porter :
> I wouldn't think so. Can you file it as an issue (probably not a blocker...)
Done: http://jira.codehaus.org/browse/MNG-4082
> Yep, definitely, though be aware they won't work with older versions of
> Maven if you intend to switch.
>
> http://maven.apache.org/guides/mini
Just been generally using it and no additional problems.
Just curious - why 2.1.0 in the version that was released instead of
2.1.0-RC1? Though we now have the SVN Rev # in there, it could prove
confusing for anyone that holds on to it.
Cheers,
Brett
On 10/03/2009, at 3:00 AM, John Casey w
On 11/03/2009, at 10:24 PM, Mark Hobson wrote:
2009/3/11 Brett Porter :
It looks like this occurs when a password matches the definition of
an
encrpyted password (I believe anything wrapped in { ... }), and you
do not
have a master password configured. I'll improve the error message.
Did
2009/3/11 Brett Porter :
> It looks like this occurs when a password matches the definition of an
> encrpyted password (I believe anything wrapped in { ... }), and you do not
> have a master password configured. I'll improve the error message.
>
> Did you already have a password like this, or were
It looks like this occurs when a password matches the definition of an
encrpyted password (I believe anything wrapped in { ... }), and you do
not have a master password configured. I'll improve the error message.
Did you already have a password like this, or were you testing the
encrypted p
Just tried upgrading from 2.0.10 and get this:
[m...@mark]$ mvn clean install
[INFO]
[ERROR] FATAL ERROR
[INFO]
[INFO] Unable to configure Maven for exe
31 matches
Mail list logo