On 12 Mar 2015, at 11:57, Jason van Zyl wrote:
> Time to release Maven 3.3.0!
So far looks good from my projects, tho it looks like its likely to be
rerolled, so +0 for now :)
--
Mark Derricutt
http://www.theoryinpractice.net
http://www.chaliceofblood.net
http://plus.google.com/+MarkDerricutt
Works on Android Maven Plugin, Android NDK Maven Plugin, Maven Repository Tools
and Ksoap2-android and a couple of private projects I have tried this.
Manfred
Jason van Zyl wrote on 11.03.2015 15:57:
> Hi,
>
> Time to release Maven 3.3.0!
>
> Here is a link to Jira with 22 issues resolved:
>
If we re-roll the release -- which looks likely -- I'll try to integrate it.
On Mar 11, 2015, at 7:37 PM, Arcadiy Ivanov wrote:
> MNG-5688 not coming in for this release?
>
> On 2015-03-11 22:23, Jason van Zyl wrote:
>> Updated, thanks.
>>
>> On Mar 11, 2015, at 7:08 PM, Paul Benedict wrote:
MNG-5688 not coming in for this release?
On 2015-03-11 22:23, Jason van Zyl wrote:
Updated, thanks.
On Mar 11, 2015, at 7:08 PM, Paul Benedict wrote:
What about the two open issues? Are they fixed in this release or need to
be moved?
On Mar 11, 2015 5:58 PM, "Jason van Zyl" wrote:
Hi,
Ti
Updated, thanks.
On Mar 11, 2015, at 7:08 PM, Paul Benedict wrote:
> What about the two open issues? Are they fixed in this release or need to
> be moved?
> On Mar 11, 2015 5:58 PM, "Jason van Zyl" wrote:
>
>> Hi,
>>
>> Time to release Maven 3.3.0!
>>
>> Here is a link to Jira with 22 issues
What about the two open issues? Are they fixed in this release or need to
be moved?
On Mar 11, 2015 5:58 PM, "Jason van Zyl" wrote:
> Hi,
>
> Time to release Maven 3.3.0!
>
> Here is a link to Jira with 22 issues resolved:
>
> https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&vers
Then it likely is a general problem. I'll take a look.
On Mar 11, 2015, at 6:13 PM, Karl Heinz Marbaise wrote:
> Hi Jason,
>
>
> checked several projects...but..unfortunately found a problem using Maven
> 3.3.0 to build maven-assembly-plugin (current trunk) via
>
> mvn -Prun-its clean verify
Hi Jason,
checked several projects...but..unfortunately found a problem using
Maven 3.3.0 to build maven-assembly-plugin (current trunk) via
mvn -Prun-its clean verify ...
which results in a problem like this:
/usr/share/java/apache-maven-3.3.0/bin/mvn: line 198: cd:
/Users/kama/apache-mav
+1
Analyzing release validity...
stagingUrl: https://repository.apache.org/content/repositories/maven-1149
groupId: org.apache.maven
artifactId: apache-maven
version: 3.3.0
Source ZIP url exists.
https://repository.apache.org/content/repositories/maven-1149/org/apache/maven/apache-maven/3.3.0/ap
Hi,
Time to release Maven 3.3.0!
Here is a link to Jira with 22 issues resolved:
https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&version=21012
Staging repo:
https://repository.apache.org/content/repositories/maven-1149/
The distributable binaries and sources for testing can be
Github user jvanzyl commented on the pull request:
https://github.com/apache/maven/pull/32#issuecomment-78341680
And I have been talking about this for years but have admittedly done
nothing yet. But I believe the direction to go is to make some example data
generators that can be use
Hi,
currently i have the problem creating a plugin which adds some
properties...to the current project...
@Parameter(defaultValue = "${project}", readonly = true, required =
true)
private MavenProject mavenProject;
mavenProject.getProperties().put("NAme", "Value");
Github user ChristianSchulte commented on the pull request:
https://github.com/apache/maven/pull/32#issuecomment-78290027
I totally agree with this. Do not cripple Maven to support bad ideas or
concepts. "Supported by Maven" as an indicator for something. Not supported by
Maven so not
This also breaks plugin line mine, which invokes mvn.bat. Good release
notes is needed
-Dan
On Wed, Mar 11, 2015 at 7:59 AM, Stephen Connolly <
stephen.alan.conno...@gmail.com> wrote:
> See
>
> https://builds.apache.org/job/maven-3.3-release-status-test-windows/lastCompletedBuild/testReport/
>
Github user ChristianSchulte closed the pull request at:
https://github.com/apache/maven/pull/32
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature
See
https://builds.apache.org/job/maven-3.3-release-status-test-windows/lastCompletedBuild/testReport/
Github user jvanzyl commented on the pull request:
https://github.com/apache/maven/pull/32#issuecomment-78277642
@ChristianSchulte Definitely more along the lines of what you describe
where there is no site lifecycle. I think this is a design error in allowing
non-build lifecycles. Bu
At the end of the day, nobody has felt strongly enough about
https://git1-us-west.apache.org/repos/asf?p=maven.git;a=commit;h=07b8477b
to veto or even -0.5 that commit.
I know we have been having the discussion here, but to me it seems like
these are "bolting the stable doors after the horse has b
Github user ChristianSchulte commented on the pull request:
https://github.com/apache/maven/pull/32#issuecomment-78226219
I am really no fan of adding just another workaround.
@Jason: Are you suggesting to split site rendering from report data
generation ? So the build lifecyc
Github user hboutemy commented on the pull request:
https://github.com/apache/maven/pull/32#issuecomment-78220459
thank you for your work: the bugs are fixed now, cobertura-maven-plugin and
m-site-p ITs pass
now back to the start of this PR :)
Christian: did you know
Le mardi 10 mars 2015 01:22:29 Jason van Zyl a écrit :
> I agree we're spending too much energy
we have a constructive discussion to make a community decision: yes, it costs
energy (not so much since the discussion is constructive), but it's useful
> but I don't plan to roll anything
> back. I do
21 matches
Mail list logo
