Hi,
Tested with company builds : looks fine.
+1
Thanks !
--
Olivier
2009/2/10 Brian E. Fox bri...@reply.infinity.nu:
It's finally time after 8 Release Candidates:
Issues fixed:
http://jira.codehaus.org/secure/ReleaseNote.jspa?version=14112styleName
=HtmlprojectId=10500Create=Create
2009/2/11 Olivier Lamy ol...@apache.org:
Hi,
Tested with company builds : looks fine.
+1
Thanks !
Ditto here, tried with various company projects, and no problems so far
-
To unsubscribe, e-mail:
My projects build fine, but I am giving a +0 right now because:
Option --show-version should be displaying the version information and
continuing the build. It wouldn't recognize that option for me.
Thoughts?
http://jira.codehaus.org/browse/MNG-3368
Based on the ticket, I am trying this
I'm +1, it looked pretty good when I ran a build out on the grid.
I'm just a little concerned about MNG-3368. I'm fine redesignating it
for 2.1.0-M1 only if we can find out that the patch wasn't applied to
2.0.x...then we can try it again for 2.0.11 or whatever. It's working in
2.1.0-*
I've linked the two issues related to this that I know about in JIRA
(MDEPLOY-94, MNG-3057), but I basically agree that the patch would look
like what Brett has shown in terms of how to implement it. I'm not as
familiar with the ArtifactTransformation system any more,
unfortunately...too many
+1, tested on various projects
Arnaud
2009/2/10 Brian E. Fox bri...@reply.infinity.nu
It's finally time after 8 Release Candidates:
Issues fixed:
http://jira.codehaus.org/secure/ReleaseNote.jspa?version=14112styleName
Brian E. Fox wrote:
Binaries are at:
https://repository.apache.org/content/repositories/maven-staging-45dca90
660cc84/org/apache/maven/apache-maven/2.0.10/
+1
Benjamin
-
To unsubscribe, e-mail:
Hi everyone,
I just wanted to let you know that I'm updating the Twitter account:
SonatypeBuilds (http://twitter.com/sonatypebuilds) with Hudson Grid
updates.
Whenever there is an outage or some major problem we're trying to deal
with, I'll post updates to that account.
Just FYI.
Thanks,
+1
Vincent
2009/2/9 Brian E. Fox bri...@reply.infinity.nu:
It's finally time after 8 Release Candidates:
Issues fixed:
http://jira.codehaus.org/secure/ReleaseNote.jspa?version=14112styleName
=HtmlprojectId=10500Create=Create
NOTE: The urls below are using a self-signed certificate.
Hi
I would like to start using bugtraq [1] in our subversion repositories.
If we set a bunch of svn properties in the repository, then version
control tools can link to issues in JIRA.
What do you think?
[1] http://tortoisesvn.net/issuetracker_integration
--
Dennis Lundberg
Hi,
(resending due to SMTP-server problems)
The time has finally come to release Doxia 1.0. For more info on the
relationship to plugins and other components, see the Doxia Release Plan at
http://docs.codehaus.org/display/MAVEN/Doxia+Release+Plan
We've solved 1 issue:
I was working with the Selenium tests for Continuum, and noticed that
there are still UI tests living in shared:
http://svn.apache.org/repos/asf/maven/shared/trunk/maven-web-ui-tests/
I think these are left over from when Continuum and Archiva lived
here, and can be removed.
--
Wendy
+1
On 11-Feb-09, at 6:43 PM, Wendy Smoak wrote:
I was working with the Selenium tests for Continuum, and noticed that
there are still UI tests living in shared:
http://svn.apache.org/repos/asf/maven/shared/trunk/maven-web-ui-tests/
I think these are left over from when Continuum and Archiva
Brian has moved everything over to the Nexus instance and we can't
manage artifact in two separate repositories. Brian wrote up full
documentation and staging to Nexus is pretty easy, and then promoting
is dead simple.
On 11-Feb-09, at 5:56 PM, Dennis Lundberg wrote:
Hi,
(resending due
Doesn't jira already scrape the svn repo for the tickets? I used the
bugtraq stuff before and seem to recall that it only helps for clients
that pay attention to it, so it's not an enforcement tool. That said, it
does make life a little easier if you do have a client that obeys it.
-Original
Dennis, your call. If you want to respin the release with the new
distMgt and stage it to Nexus, that will work. Otherwise, I'll have to
manually import your existing artifacts to the new system so they get
merged correctly. I don't mind either way since I'm still working on
getting the poms fixed
Does any tool exist that can build a project in Maven 2 and Maven 3
and then compare the binaries to see if they are equal? Assuming v3 is
fully backwards compatible with v2, I hope there would be only
superficial differences.
Paul
I don't think I'll be making any byte for byte exactly guarantees but
as we progress I am going to try and ensure backward compatibility
insofar as behavior. Plugins will work the same apart from plugins
that use components from maven-artifact. We'll be using Mercury for
that and for any
I have a tool that compares resolved dependency lists between Mercury
and Maven2, not binaries. Will not be hard to modify to add binary
comparison.
Paul Benedict wrote:
Does any tool exist that can build a project in Maven 2 and Maven 3
and then compare the binaries to see if they are equal?
On 11-Feb-09, at 10:28 PM, Oleg Gusakov wrote:
I have a tool that compares resolved dependency lists between
Mercury and Maven2, not binaries. Will not be hard to modify to add
binary comparison.
There you go, Oleg will check them for you :-)
Paul Benedict wrote:
Does any tool exist
Hi,
The time has finally come to release Doxia 1.0. For more info on the
relationship to plugins and other components, see the Doxia Release Plan at
http://docs.codehaus.org/display/MAVEN/Doxia+Release+Plan
We've solved 1 issue:
21 matches
Mail list logo