GitHub user chonton opened a pull request:
https://github.com/apache/maven-site/pull/5
fix formatting of introduction-to-the-lifecycle
MNGSITE-281 updates weren't formatted precisely.
You can merge this pull request into a Git repository by running:
$ git pull https://github.co
On Fri, May 6, 2016 at 4:51 PM, Christian Schulte
wrote:
> Hello,
>
> I know this has been discussed before. I do not find relevant thread(s).
> What was/is still the reason for keeping things targetted at Java 6?
> Whenever I stumble upon something with '-target <1.7', can I just set it
> to '-t
Hello,
I know this has been discussed before. I do not find relevant thread(s).
What was/is still the reason for keeping things targetted at Java 6?
Whenever I stumble upon something with '-target <1.7', can I just set it
to '-target 1.7'? I would like to use Java 7 features as soon as
possible. T
Hello,
I'm developing a plugin where I need to download a file from a place and
install it with a created pom for it in a local maven repository.
while investigating how to do that I found that AbstractArtifactMetadata
class is deprecated.
It is there a replacement for it or a newest way to
Hi,
On 5/6/16 10:08 PM, Christian Schulte wrote:
This would need to be enforced automatically in a way that a release
with a version string not containing three digits cannot be performed.
This could be handled via writing a Maven Enforcer Plugin rule...
Maybe also get rid of -alpha, -beta,
This would need to be enforced automatically in a way that a release
with a version string not containing three digits cannot be performed.
Maybe also get rid of -alpha, -beta, -whatever that way.
Am 05/06/16 um 22:00 schrieb Karl Heinz Marbaise:
> Hi to all,
>
> I would like to suggest to keep t
+100 ... I always found it weird to drop of the last digits.
Manfred
Karl Heinz Marbaise wrote on 2016-05-06 13:00:
> Hi to all,
>
> I would like to suggest to keep the version number of the plugins and
> shared components to the following format (and may be also things we are
> using like p
Hi to all,
I would like to suggest to keep the version number of the plugins and
shared components to the following format (and may be also things we are
using like plexus?):
Major.Minor.Patch(-SNAPSHOT):
(Following SemVer.org):
So adding a new functionality which will not break the 3.0.X p
Hi,
On 5/6/16 6:32 PM, Stian Soiland-Reyes wrote:
OK, that's inverse process from other ASF projects I've been on -
which require a commit ID in the email because of the fact you CAN
change a tag AND drop a Staging repository; e.g. it is not a
long-lasting record of the vote (for the failed RCs
Hi Stian,
Cool thanks for your support..
Kind regards
Karl Heinz
On 5/6/16 6:27 PM, Stian Soiland-Reyes wrote:
+1 also from Windows 10 :)
[INFO] BUILD SUCCESS
[INFO]
[INFO] Total time: 02:25 min
[INFO] Finished at: 2016-0
OK, that's inverse process from other ASF projects I've been on -
which require a commit ID in the email because of the fact you CAN
change a tag AND drop a Staging repository; e.g. it is not a
long-lasting record of the vote (for the failed RCs at least).
Perhaps that is a bit paranoid :-) But i
+1 also from Windows 10 :)
[INFO] BUILD SUCCESS
[INFO]
[INFO] Total time: 02:25 min
[INFO] Finished at: 2016-05-06T16:44:19+01:00
[INFO] Final Memory: 37M/435M
[INFO] --
Hi,
reference of the release procedure here:
https://maven.apache.org/developers/release/maven-project-release-procedure.html
Kind regards
Karl Heinz
On 5/6/16 5:59 PM, Karl Heinz Marbaise wrote:> Hi Stian,
On 5/6/16 5:39 PM, Stian Soiland-Reyes wrote:
The commit id was missing from the vot
Hi Stian,
On 5/6/16 5:39 PM, Stian Soiland-Reyes wrote:
The commit id was missing from the vote email.
We don't use the commit id in the vote mails cause we only stage the
release which has a related tag in svn:
svn log -v -l1
https://svn.apache.org/repos/asf/maven/plugins/tags/maven-jar-p
The commit id was missing from the vote email.
I assume you mean:
https://svn.apache.org/repos/asf/maven/plugins/tags/maven-jar-plugin-3.0.0/@1742311
(I would have expected the tag to be maven-jar-plugin-3.0.0-RC1 until
the release vote was passed)
I verified the above match against
maven-jar-pl
Sure!
Verified with Ubuntu 14.04:
Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5;
2015-11-10T16:41:47+00:00)
Maven home: /home/stain/software/maven
Java version: 1.8.0_72-internal, vendor: Oracle Corporation
Java home: /usr/lib/jvm/java-8-openjdk-amd64/jre
Default locale: en_GB, pla
Hi Stian,
first thanks for your support...great...thanks for the feedback...
would it be possible to check the release package via:
mvn -Prun-its clean verify
also on your OS / environment to see if the integration tests don't have
issues as well...
Thanks in advance..
Kind regards
Karl He
+1 (non-binding)
+1 signatures, hashes
+1 mvn clean install of maven-jar-plugin src
+1 mvn clean install of incubator-taverna-engine (which uses bundle plugin)
+1 mvn clean install of maven-jar-plugin src using maven-jar-plugin 3.0.0
+1 (turtles all the way GCC style) maven clean install of
maven-
Hi,
I wrote a Maven plugin that lets you execute java code directly from the
project and bind it to build cycle phases. I believe this can be helpful
when you want to do something specific in your project without having to
develop your own custom plugin (or before spending time packaging it as a
p
19 matches
Mail list logo
