Nexus operation has been resumed. Please vote/test.
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
Am 2014-10-28 um 03:17 schrieb yanshuai:
hi, all,
I found a mistake in slf4j-configuration.properties of maven-embedder project,
org.slf4j.helpers.Log4JLoggerFactory should be
org.slf4j.helpers.Log4jLoggerFactory. Otherwise, when I use log4j2 instead of
slf4j-simple, it will not find the class
hi, all,
I found a mistake in slf4j-configuration.properties of maven-embedder project,
org.slf4j.helpers.Log4JLoggerFactory should be
org.slf4j.helpers.Log4jLoggerFactory. Otherwise, when I use log4j2 instead of
slf4j-simple, it will not find the class org.slf4j.helpers.Log4JLoggerFactory
and
+1
On 27 October 2014 06:48, Karl Heinz Marbaise wrote:
> Hi,
>
> We solved 6 issues:
> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11128&version=20685
>
> There are still 2 issues left in JIRA:
> http://jira.codehaus.org/issues/?jql=project%20%3D%20MCLEAN%20AND%20status%20%3D%20Op
Also read
http://docs.codehaus.org/display/MAVENUSER/POM+Element+for+Source+File+Encoding
Op Mon, 27 Oct 2014 22:26:31 +0100 schreef Mirko Friedenhagen
:
+1 and in the future maybe project.build.sourceEncoding should just
default to the "reasonable" UTF-8.
Regards Mirko
--
http://illegalst
+1 and in the future maybe project.build.sourceEncoding should just
default to the "reasonable" UTF-8.
Regards Mirko
--
http://illegalstateexception.blogspot.com/
https://github.com/mfriedenhagen/ (http://osrc.dfm.io/mfriedenhagen)
https://bitbucket.org/mfriedenhagen/
On Mon, Oct 27, 2014 at 9:16
+1 (non-binding)
SHA1 OK
Tested with Maven 3.0.5, Maven 3.1.1 and Maven 3.2.3
Regards Mirko
--
http://illegalstateexception.blogspot.com/
https://github.com/mfriedenhagen/ (http://osrc.dfm.io/mfriedenhagen)
https://bitbucket.org/mfriedenhagen/
On Sun, Oct 26, 2014 at 8:52 PM, Kristian Rosenvold
hi Michael,
On 10/27/14 9:53 PM, Michael Osipov wrote:
Am 2014-10-27 um 21:21 schrieb Karl Heinz Marbaise:
Hi Dan,
On 10/27/14 9:01 PM, Dan Tran wrote:
@Karl
Are you planing to release a new maven-jar-plugin?
Thanks
Yeah...working on a missging single issue...apart from the current down
i
Am 2014-10-27 um 21:21 schrieb Karl Heinz Marbaise:
Hi Dan,
On 10/27/14 9:01 PM, Dan Tran wrote:
@Karl
Are you planing to release a new maven-jar-plugin?
Thanks
Yeah...working on a missging single issue...apart from the current down
issue of the nexus ...
http://jira.codehaus.org/browse/MJ
As you can see it appears under the "Project Transitive Dependencies"
and it's pulled in by maven-artifact. This is ok, but also explains
why we'll be seeing that dependency for a *loong* time.
Kristian
2014-10-27 21:30 GMT+01:00 Dan Tran :
> or it is OK to show up since it is used by other depe
or it is OK to show up since it is used by other dependencies. In this case
maven-artifact
-D
On Mon, Oct 27, 2014 at 1:29 PM, Dan Tran wrote:
> So I assume it should not show up under
> http://maven.apache.org/surefire/maven-surefire-plugin/dependencies.html
> ??
>
> Thanks
>
> -D
>
> On Mon,
So I assume it should not show up under
http://maven.apache.org/surefire/maven-surefire-plugin/dependencies.html ??
Thanks
-D
On Mon, Oct 27, 2014 at 1:08 PM, Kristian Rosenvold <
kristian.rosenv...@gmail.com> wrote:
> plexus-utils was removed as it was converted to m-s-u, the p-u
> dependency
Hi Dan,
On 10/27/14 9:01 PM, Dan Tran wrote:
@Karl
Are you planing to release a new maven-jar-plugin?
Thanks
Yeah...working on a missging single issue...apart from the current down
issue of the nexus ...
http://jira.codehaus.org/browse/MJAR
Kind regards
Karl Heinz Marbaise
-
plexus-utils was removed as it was converted to m-s-u, the p-u
dependency you see is transitively included from the maven core
version.
Kristian
2014-10-27 20:15 GMT+01:00 Dan Tran :
> Hi,
>
> I notice the dependency report shows a downgrade [1] from 3.x ( at surefire
> 2.12.x) to 1.5.x at surefi
@Karl
Are you planing to release a new maven-jar-plugin?
Thanks
-D
Hi,
I notice the dependency report shows a downgrade [1] from 3.x ( at surefire
2.12.x) to 1.5.x at surefire 2.17
is it expected?
-D
[1] http://maven.apache.org/surefire/maven-surefire-plugin/dependencies.html
See https://issues.apache.org/jira/browse/INFRA-8530 and the numerically
following ;-)
Am Montag, 27. Oktober 2014 schrieb tibor17 :
> The build succeedded after SUREFIRE-649 but the deployment failed
> Failed to transfer file:
>
> https://repository.apache.org/content/repositories/snapshots/org
Github user Tibor17 closed the pull request at:
https://github.com/apache/maven-surefire/pull/62
---
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
The build succeedded after SUREFIRE-649 but the deployment failed
Failed to transfer file:
https://repository.apache.org/content/repositories/snapshots/org/apache/maven/surefire/common-java5/maven-metadata.xml.
Return code is: 502, ReasonPhrase: Proxy Error.
-
BR, tibor17
--
View this messag
I would try to do it as soon as you're done. Preferably earlier than Friday.
Am Montag, 27. Oktober 2014 schrieb tibor17 :
> Hi Andreas,
>
> I am going to push SUREFIRE-649.
> No, actually i will fix SUREFIRE-1053 and open a new minor improvement
> which
> takes me very short time to fix.
> IMH
Hi Andreas,
I am going to push SUREFIRE-649.
No, actually i will fix SUREFIRE-1053 and open a new minor improvement which
takes me very short time to fix.
IMHO i can fix these issues till Wed.
Is that acceptable date for you?
Do you want to make the release on Friday?
-
BR, tibor17
--
View
I've already created the 2.19 version in Jira so issues that we know will
not make it into 2.18 can be moved there or into 3.0.
Am Montag, 27. Oktober 2014 schrieb Andreas Gudian :
> Hi,
>
> I'm kind of done with what I wanted to get in.
>
> Tibor, after you pushed your fix for 649 to master, yo
> On 10/27/14 11:02 AM, Michael Osipov wrote:
> >> Hi Michael,
> >>
> >> On 10/27/14 7:23 AM, Michael Osipov wrote:
> >>> Am 2014-10-26 um 23:15 schrieb Karl Heinz Marbaise:
> Hi,
>
> We solved 10 issues:
> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11085&version
On 10/27/14 11:02 AM, Michael Osipov wrote:
Hi Michael,
On 10/27/14 7:23 AM, Michael Osipov wrote:
Am 2014-10-26 um 23:15 schrieb Karl Heinz Marbaise:
Hi,
We solved 10 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11085&version=19853
JXR-116: Doxia is already at 1.6. S
> > Hi Michael,
> >
> >
> > there had gone something completely wrongcause
> > the staging repository is empty...from the given url as well as from the
> > Nexus...
> >
> >
> > On 10/27/14 10:45 AM, Mikolaj Izdebski wrote:
> > > On 10/26/2014 10:06 PM, Michael Osipov wrote:
> > >> Staging
> Hi Michael,
>
>
> there had gone something completely wrongcause
> the staging repository is empty...from the given url as well as from the
> Nexus...
>
>
> On 10/27/14 10:45 AM, Mikolaj Izdebski wrote:
> > On 10/26/2014 10:06 PM, Michael Osipov wrote:
> >> Staging repo:
> >> https://rep
Hi Michael,
there had gone something completely wrongcause
the staging repository is empty...from the given url as well as from the
Nexus...
On 10/27/14 10:45 AM, Mikolaj Izdebski wrote:
On 10/26/2014 10:06 PM, Michael Osipov wrote:
Staging repo:
https://repository.apache.org/content/r
> Hi Michael,
>
> On 10/27/14 7:23 AM, Michael Osipov wrote:
> > Am 2014-10-26 um 23:15 schrieb Karl Heinz Marbaise:
> >> Hi,
> >>
> >> We solved 10 issues:
> >> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11085&version=19853
> >>
> >
> > JXR-116: Doxia is already at 1.6. Shouldn't
On 10/26/2014 10:06 PM, Michael Osipov wrote:
> Staging repo:
> https://repository.apache.org/content/repositories/maven-1086/
> http://repository.apache.org/content/repositories/maven-1086/org/apache/maven/maven-archiver/2.6/maven-archiver-2.6-source-release.zip
The repository appears to be empty
I see that maven-assembly-plugin will perform filtering with platform
default encoding if none has been specified through
${project.build.sourceEncoding}
I would like to make assembly simply refuse to do filtering if
encoding has not been specified, and simply throw an exception
informing the user
Hi Michael,
On 10/27/14 7:23 AM, Michael Osipov wrote:
Am 2014-10-26 um 23:15 schrieb Karl Heinz Marbaise:
Hi,
We solved 10 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11085&version=19853
JXR-116: Doxia is already at 1.6. Shouldn't we upgrade first?
Yes this is true
yes, the lag on the us site is far more than on the eu site: at the moment, eu
site is ok, but not us one...
as you'll see with INFRA-8491, it is being worked on for some time now, I fear
nothing can be done for us that isn't already done for everybody
Regards,
Hervé
Le lundi 27 octobre 2014
OK, which might explain why the site seems to be flickering back
between 2.5 and 2.6-SNAPSHOT right now. I have checked SVN and it
seems like all three branches are on "2.5". I'll leave this for now,
if the site is still 2.6-SNAPSHOT tomorrow I'll talk to infra.
Kristian
2014-10-27 8:36 GMT+01:0
Hi,
I'm kind of done with what I wanted to get in.
Tibor, after you pushed your fix for 649 to master, you only got 1053 left
to be done, right?
Let me know as soon as you're done with that and I'll start with the
release :-)
Andreas
Am Sonntag, 26. Oktober 2014 schrieb tibor17 :
> I am goin
there is an expected little lag after publish, less than one hour: your update
is now visible on http://maven.apache.org/plugins/index.html
there are some svnpubsub/websites problems actually worked on by INFRA,
because there is more load than expected: see
https://issues.apache.org/jira/browse/
Release has certainly gotten a whole lot more complex since last time I did it.
I tried using the "cms", used "edit" and then "publish". After a while
it says I'm a published author, but it seems like I am published to
/dev/null. What other magic incantations are needed ?
Kristian
2014-10-27 7:
36 matches
Mail list logo
