Hello,
if I remember right, I had problems because the enforcer duplicate class
rule was complaining. I think an artifact called API should not have or at
least expose any dependencies not found in it's contracts, so maybe that is
the problem.
Regards
Mirko
--
Sent from my mobile
On Nov 7, 2014
The Apache Maven team is pleased to announce the release of the
Apache Maven Assembly Plugin, version 2.5.1.
The Assembly Plugin for Maven is primarily intended to allow users to aggregate
the project output along with its dependencies, modules, site documentation,
and other files into a single
Hi,
I have tested via mvn -Prun-its clean verify with the following
Maven versions: 3.0.5, 3.1.1, 3.2.1, 3.2.2 and 3.2.3 but unfortunately i
got the following result with Maven 2.2.1:
INFO] Building: mpmd-89/pom.xml
[INFO] ..FAILED (3.5 s)
[INFO] The build exited with code 0. See
The Apache Maven team is pleased to announce the release of the Apache
Maven Surefire Plugin, version 2.18
The release contains a number of bug fixes, and introduces an option to
automatically rerun failing tests, including proper reporting on the
console and in the XML reports for the individual
Thanks Karl Heinz, the vote is canceled, I hopefully am able to fix the
issue and will start a second round.
Regards
Mirko
--
Sent from my mobile
On Nov 8, 2014 11:37 AM, Karl Heinz Marbaise khmarba...@gmx.de wrote:
Hi,
I have tested via mvn -Prun-its clean verify with the following
Maven
Hello,
now that I canceled the vote on maven-pmd-plugin 3.3 should I go for 3.3.1
or _delete_ and _reuse_ the tag. Or may the release responsible decide this
on his own? I am always in favor of creating a new tag.
Regards
Mirko
--
Sent from my mobile
Hi Mirco,
I i had to cancel a vote i have deleted the tag, cause it does not made
it to the real public and recreated after fixing the problem...
Based on staging you have the choice of going back
Kind regards
Karl Heinz Marbaise
for svn, in the past, we've deleted and reused the tag
but the release manager decides if he wants to create a new tag: it doesn't
hurt
for git, we've seen deleting a tag is not really possible in a safe way, so
there is only one solution
Regards,
Hervé
Le samedi 8 novembre 2014 13:15:21
I would just respin the release with version 3.3. With Subversion it's not
that big a deal to delete a tag (with a proper comment) and recreate it for
the re-spin.
With git it would be a big no-no to replace an already pushed tag, that's
why I create the final tag only after the vote completed and
Hi,
On 11/8/14 1:21 PM, Hervé BOUTEMY wrote:
for svn, in the past, we've deleted and reused the tag
but the release manager decides if he wants to create a new tag: it doesn't
hurt
for git, we've seen deleting a tag is not really possible in a safe way, so
there is only one solution
Hmare
If you haven't pushed the tag, it is perfectly safe to delete and
recreate it. If you did push, however, the new tag will have to be
propagated manually in each and every clone. You can find more details
in [1], look for On Re-tagging section.
Even without git, I find artifacts with the same
I'm not a git expert, then my explanations are to be confirmed
From what I understood, there is no problem on canonical ASF repo not github
mirror. The problem is for people who cloned the repo or updated their clone
with initial tag: they don't get the tag update unless they manually delete
IMO you never delete a tag that has a VOTE associated with it.
Gary
div Original message /divdivFrom: Mirko Friedenhagen
mfriedenha...@gmail.com /divdivDate:11/08/2014 07:15 (GMT-05:00)
/divdivTo: Maven Developers List dev@maven.apache.org /divdivSubject:
Stance on patch
We had a lot of trolling about not deleting git tags; but I think they
all left us. Personally it seems to me like it does not really matter
all that much; and I'm still here :)
if you rewrite a tag it will be updated once you refresh from the
remote. There is a danger some replication settings
+1
On Nov 8, 2014, at 9:52 AM, Kristian Rosenvold kristian.rosenv...@gmail.com
wrote:
We had a lot of trolling about not deleting git tags; but I think they
all left us. Personally it seems to me like it does not really matter
all that much; and I'm still here :)
if you rewrite a tag it
Hello,
I am a bit out of ideas. While mpmd-89 fails correctly with Maven-3.X,
Maven-2.2.1 does not report any violations when using PMD-5.2.1. I
inspected the build log for maven-pmd-plugin-3.2 (uses PMD-5.1.2) and
the current trunk when using Maven-2.2.1 but do not see any relevant
difference.
I’ve got it somewhat working by extending TestsToRun with my implementation.
Everything is fine, except that surefire loads all test classes before
launching any test just to create test description.
(It’s a JUnit4Provider that’s doing it).
Do you think it’s safe to omit creation of test
17 matches
Mail list logo
