Ok, the signatures are fixed in the staging repo, thanks to Brian, so I'd say we
call it a release. The voting period has passed and we have 3 binding +1 (Vincent,
Benjamin, myself), plus one non-binding (Nicolas).
I'll wait a few more hours before promoting the artifacts if anybody wants to
I heard some time ago that the profiles.xml were removed in Maven3. Although
I'm still using 2.1.0 I want to be prepared for such changes.
IMHO I think it's a bad choice to remove this option.
Maven should provide some sort of way where developers can set/change project
properties without
I am wondering if it is now safe to have multiple Maven 2.1.0 processes
running concurrently using the same local repository. I know that with
older versions of Maven this was certainly not safe, but reading
comments on some JIRA issues leads me to believe that this may have been
addressed
We are pleased to announce the release of Maven Doxia and Maven Doxia Sitetools,
version 1.1.1.
Doxia is a content generation framework that provides powerful techniques for
generating static and dynamic content: Doxia can be used in a web-based publishing
context to generate static sites,
Almost certainly no. The 2.1 you saw mentioned most likely refers to
the old 2.1 that is now 3.0. FWIW, I don't believe this has been or
will be addressed in 3.0.0 which is focused on 2.x compatibility.
http://www.sonatype.com/people/2008/11/a-visual-history-of-maven-2/
On Wed, Jun 24, 2009 at
use new File(basedir,)
On Tue, Jun 23, 2009 at 4:21 PM, Barrie Treloarbaerr...@gmail.com wrote:
Interesting...
[INFO] Executing tasks
[echo] script =
/home/hudson/workspace/plugins-CI-with-maven-2.1.x/jdk/1.5/label/ubuntu/trunk/maven-eclipse-plugin/verify-integration-tests-checks.bsh
Why not just put those values into the settings.xml?
On Wed, Jun 24, 2009 at 4:31 AM, Robert Scholterfscho...@codehaus.org wrote:
I heard some time ago that the profiles.xml were removed in Maven3. Although
I'm still using 2.1.0 I want to be prepared for such changes.
IMHO I think it's a
A major difference is that the settings.xml file is not stored with the project
source.
If your project depends on the profile(s) in some crucial way the information
should be archived with the project. In that case the settings.xml is not an
option.
Stan
- Original Message -
From:
Brian Fox wrote:
Almost certainly no. The 2.1 you saw mentioned most likely refers to
the old 2.1 that is now 3.0. FWIW, I don't believe this has been or
will be addressed in 3.0.0 which is focused on 2.x compatibility.
http://www.sonatype.com/people/2008/11/a-visual-history-of-maven-2/
On Wed, Jun 24, 2009 at 10:07 AM, Jason Voegeleja...@jvoegele.com wrote:
Thanks for the response. I guess I'll try my hand at using a lock file or
something similar in my wrapper scripts. I'm thinking that this algorithm
might work:
You might look at Don Brown's work on parallel resolution
In the settings.xml it's not possible to activate a profile by project. Then
again: I believe settings.xml are actually maven-settings and not
project-settings. For most users it's a big step to dive into the
settings.xml. For them there are only a few reasons to access the settings
file:
- to
From inside an the antrun plugin?
On Thu, Jun 25, 2009 at 1:42 AM, Brian Foxbri...@infinity.nu wrote:
use new File(basedir,)
On Tue, Jun 23, 2009 at 4:21 PM, Barrie Treloarbaerr...@gmail.com wrote:
Interesting...
[INFO] Executing tasks
[echo] script =
Well, the mixin support should cover the profiles.xml and moreeven
better it should be possible to resolve the mixins from the repository which
means they are versioned and deployed artifacts like everything else.
On Wed, Jun 24, 2009 at 11:41 AM, Robert Scholte rfscho...@codehaus.orgwrote:
13 matches
Mail list logo
