Hi Tibor,
i have a strange thing...
If i check the -sources.zip file ...(Maven 3.0.5).
I got the following:
~/Downloads/maven-shared-utils-0.8$ mvn clean verify
[INFO] Scanning for projects...
[INFO]
[INFO]
[INFO] Build
It's because the symlinks dont get packaged properly as a symlink inside
source-jar. This is probably because an old version of
maven-assembly-plugin has been used when building the source-jar
Kristian
2015-06-17 10:09 GMT+02:00 Karl Heinz Marbaise :
> Hi Tibor,
>
> i have a strange thing...
>
Hi Tibor,
apart from that packging problem here is my +1 ...
Kind regards
Karl Heinz Marbaise
On 6/17/15 10:09 AM, Karl Heinz Marbaise wrote:
Hi Tibor,
i have a strange thing...
If i check the -sources.zip file ...(Maven 3.0.5).
I got the following:
~/Downloads/maven-shared-utils-0.8$ mvn
Should I upgrade the version of assembly plugin and restart the vote in
version 0.9 ?
--
View this message in context:
http://maven.40175.n5.nabble.com/VOTE-Release-Apache-Maven-Shared-Utils-version-0-8-tp5837727p5837763.html
Sent from the Maven Developers mailing list archive at Nabble.com.
-
Hi Tibor,
On 6/17/15 1:19 PM, Tibor Digana wrote:
Should I upgrade the version of assembly plugin and restart the vote in
version 0.9 ?
Hm..May be yes (i think i would do so), but the decision is yours...
Kind regards
Karl Heinz Marbaise
-
I would report a bug in 0.9 assign it to me and continue the vote.
I believe you had such issue, but I trust the command mvn release:prepare
which passed with all over 800 tests on original sources.
Karl, maybe you can check the surefire reports html on the site.
How important is -sources.jar if we
+1
This has probably been released a couple of times already in this state, so
my 2NOK is just to make an issue.
Kristian
2015-06-17 13:29 GMT+02:00 Tibor Digana :
> I would report a bug in 0.9 assign it to me and continue the vote.
> I believe you had such issue, but I trust the command mvn r
Hi Tibor,
On 6/17/15 1:29 PM, Tibor Digana wrote:
I would report a bug in 0.9 assign it to me and continue the vote.
I believe you had such issue, but I trust the command mvn release:prepare
which passed with all over 800 tests on original sources.
Karl, maybe you can check the surefire reports
Kristian, Karl, What JDK version you use while building maven-shared ?
Maybe this is the case, because I see in Karls Nexus staging repo Maven 3.1
or 3.2 and JDK7 and I use Maven 3.0.5 and JDK5.
--
View this message in context:
http://maven.40175.n5.nabble.com/VOTE-Release-Apache-Maven-Shared-
Under some unknown conditions the build fails on tests maven-shared-utils
with command mvn clean verify.
Failed tests:
DirectoryScannerTest.followSymlinks:179 null
FileUtilsTest.copyFileThatIsSymlink:433 null
Tests run: 858, Failures: 2, Errors: 0, Skipped: 27
Let's redirect the issue in the thread Broken-build-on-maven-shared-utils.
http://maven.40175.n5.nabble.com/Broken-build-on-maven-shared-utils-td5837795.html
--
View this message in context:
http://maven.40175.n5.nabble.com/VOTE-Release-Apache-Maven-Shared-Utils-version-0-8-tp5837727p5837796.ht
Github user josephw commented on the pull request:
https://github.com/apache/maven/pull/51#issuecomment-112843851
@kwin , @mosabua: thanks. I've rewritten it to reflect that distinction,
that it's only deprecated for compile-time enforcement.
---
If your project is set up for it, you
I fixed the root cause by upgrading assembly-plugin to 2.5.5 in r1686055,
which includes proper symlinks in the zip. Did you make an issue for this ?
Kristian
2015-06-17 15:10 GMT+02:00 Tibor Digana :
> Under some unknown conditions the build fails on tests maven-shared-utils
> with command mvn
QDox has been moved to the account of Paul Hammant:
https://github.com/paul-hammant/qdox
He has more Codehaus originals, which depends on QDox, so this way the
family stays together.
And yes, I'm involved by being the project lead of QDox since 2010 :)
Robert
Op Wed, 17 Jun 2015 00:16:34 +02
uh, no organization to be able to work together?
is it a deliberate choice, or just something done quickly before having time
to do better?
Regards,
Hervé
Le mercredi 17 juin 2015 19:06:12 Robert Scholte a écrit :
> QDox has been moved to the account of Paul Hammant:
> https://github.com/paul-h
See http://markmail.org/thread/hgm2z5ah7k4w72l4
I still have all the commit-rights so for me there's no real change.
Although it might be a bit harder to find the project.
Robert
Op Wed, 17 Jun 2015 19:16:07 +0200 schreef Hervé BOUTEMY
:
uh, no organization to be able to work together?
is i
Why does the maven compiler plugin STILL target 1.5 by default and not the
JDK's current version? This seems completely backwards. We use CI tools to test
against different JDK versions and architectures and it is a massive pain to
implement all these workarounds to have the compiler target each
I wonder if this would be a good candidate for a corporate POM that deals with
this kind of configuration?
Sander Verhagen
[ san...@sanderverhagen.net ]
NOTICE: my e-mail address has changed. You may still e-mail me at
verha...@sander.com but you will see me using san...@sanderverhagen.net
Yes... a corporate or some other higher level pom is typically how you
configure this across lots of projects. But even if you dont ... its two lines
of config on the compiler plugin.
Manfred
Sander Verhagen wrote on 17.06.2015 15:16:
> I wonder if this would be a good candidate for a corporat
Hi,
here is my +1.
Kind regards
Karl Heinz Marbaise
On 6/16/15 10:15 PM, Karl Heinz Marbaise wrote:
Hi,
We solved 2 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317421&version=12332797
There are still a couple of issues left in JIRA:
https://issues.apache.org/ji
20 matches
Mail list logo