hi, the problem is fixed and all the tasks are now green.
BR
Sylwester
wt., 7 sty 2020 o 23:03 Robert Scholte napisał(a):
> Hi,
>
> the site master is broken since this commit, not sure if it is cause, so
> please investigate:
>
> https://builds.apache.org/job/dist-tool-plugin/site/dist-tool-mas
Team,
pom.xml
Description: XML document
I am facing the below issue. I am attaching the pom file here for your reference…. I am facing the same issue even when I change the version. To 1.7 and change target to tasks==[ERROR] Unknown lifecycle phase " ". You must specify a valid lifecycle phase
Hi,
the site master is broken since this commit, not sure if it is cause, so please
investigate:
https://builds.apache.org/job/dist-tool-plugin/site/dist-tool-master-jobs.html
https://builds.apache.org/job/maven-box/job/maven-site/job/master/
thanks,
Robert
On 6-1-2020 21:16:05, elh...@apache.o
Elliotte Rusty Harold wrote on 2020-01-07 13:38 (GMT -08:00):
> On Tue, Jan 7, 2020 at 4:00 PM Clemens Quoss wrote:
>>
>> artifactId-version-classifier.jar
>>
>> How do i separate the classifier?
>>
>
> If all you have is the name of the jar, I don't think you can. You
> need the repo metadata o
On Tue, Jan 7, 2020 at 4:00 PM Clemens Quoss wrote:
>
> artifactId-version-classifier.jar
>
> How do i separate the classifier?
>
If all you have is the name of the jar, I don't think you can. You
need the repo metadata or the coordinates or the pom.xml to tell
whether google-cloud-firestore-0.4
To be honest I dont think this needs fixing on the Maven side. If we change
behavior we just break other approaches.
Instead users that want to use semver with three digits and want logic ordering
should just do so.
So do NOT use a version like 2.1 .. instead use 2.1.0.
Problem solved.
Also .
Hi Elliotte,
OK. I understand. Right now it is up to you to sync the doc to the
implementation.
Next step is to make improvements to the implementation.
All this with regard to how the version comparison is handled.
My question was:
Given a jar named
artifactId-version-classifier.jar
How
I'd mark the Fix version as 4.0.x-candidate
On 7-1-2020 13:16:57, Elliotte Rusty Harold wrote:
I've been looking at Maven 's version comparison algorithm: what it
does, what it's documented to do, and what it should do. I ran a quick
poll on my twitter feed to see what developers expect how versio
Thank you very much, Robert. Got it.. Replacing only required elements
from the working command worked...
On Tue, Jan 7, 2020 at 1:27 PM Robert Scholte wrote:
> My guess is that the problem is not in the pom, but in the commandline.
> Looks like your mvn command contains/ends with a character t
My guess is that the problem is not in the pom, but in the commandline.
Looks like your mvn command contains/ends with a character that looks like a
space, but is not.
thanks, Robert
On 7-1-2020 18:30:34, sireindera...@gmail.com wrote:
Adding users group too..
mvn -version
*Apache Maven 3.6.3
Adding users group too..
mvn -version
*Apache Maven 3.6.3 (cecedd343002696d0abb50b32b541b8a6ba2883f)*
Maven home: /Users//apache-maven-3.6.3
Java version: 1.8.0_231, vendor: Oracle Corporation, runtime:
/Library/Java/JavaVirtualMachines/jdk1.8.0_231.jdk/Contents/Home/jre
Default locale: e
(I feel us...@maven.apache.org is suitable place)
What's command to get the error?
What does "mvn -version" say?
On Tue, Jan 7, 2020 at 12:15 PM sireindera...@gmail.com
wrote:
>
> Team,
>
> I am facing the below issue. I am attaching the pom file here for your
> reference….
>
> I am facing the s
Team,
I am facing the below issue. I am attaching the pom file here for your
reference….
I am facing the same issue even when I change the version. To 1.7 and
change target to tasks
==
[*ERROR*] Unknown lifecycle phase " ". You must specify a valid lifecycle
phase or a goal in the format :
This is what we currently claim to implement:
https://maven.apache.org/pom.html#Version_Order_Specification
However, there are bugs in both the spec and the implementation. That
is, there are cases the spec does not describe and other parts where
the spec is ambiguous. There also cases where the
OK. Found it myself:
https://maven.apache.org/plugins/maven-deploy-plugin/examples/deploying-with-classifiers.html
So classifier for sources, javadoc etc. Got it.
But still: What is the alogorithm to separate version from classifier
when I only have the artifact name? Seems not possible, ri
Consider this artifact:
artifactId-1.0-alpha1-classifier.jar
How to separate version (1.0-alpha1) from classifier (classifier), then?
TIA
Clemens
Am 07.01.2020 um 16:12 schrieb Elliotte Rusty Harold:
Classifiers are a separate part of the coordinates and are never part
of the version string.
Classifiers are a separate part of the coordinates and are never part
of the version string. "alpha1" is not a classifier and neither is
"q".
On Tue, Jan 7, 2020 at 9:57 AM Clemens Quoss wrote:
>
> Is 'q' considered a classifier or not? Classifier like 'alpha1',
> 'beta2' and even 'SNAPSHOT' d
Is 'q' considered a classifier or not? Classifier like 'alpha1',
'beta2' and even 'SNAPSHOT' denote a pre-production version, IMHO.
With: artifactId-1.0.alpha1 < artifactId-1.0.beta2 < ... <
artifactId-1.0.SNAPSHOT < ...
Is there really a difference between putting a hyphen or a dot to
sepa
I've been looking at Maven 's version comparison algorithm: what it
does, what it's documented to do, and what it should do. I ran a quick
poll on my twitter feed to see what developers expect how version
strings such as 2.1.q and 2.1 are compared. That is, what's the higher
version? 2.1.q or 2.1?
19 matches
Mail list logo
