This is not just MNG-5668, but also contains several non-existing issues, that
should be mentioned explicitly as they will have huge impact:
- support before:/after: prefix for phase-binding
- introduce priority
- reduce phases (this one hasn't been implemented, but seems to be the reason
behin
Done, JIRA ticket is here https://issues.apache.org/jira/browse/ARCHETYPE-583
Regards
--
Łukasz
+ 48 606 323 122 http://www.lenart.org.pl/
pon., 11 lis 2019 o 20:44 Robert Scholte napisał(a):
>
> Github is not our issue management system, could you create a JIRA issue at
> https://issues.apac
I'd say start a release. As it is based on JSR223 is should be very easy for
any scripting language to be supported.
Robert
On 11-11-2019 22:29:26, Enrico Olivelli wrote:
Hi,
we have a plugin, the maven-scripting-plugin that has never been released !!
https://github.com/apache/maven-scripting-p
Hi,
The vote has passed with the following result:
+1 : Michael Osipov, Olivier Lamy, Enrico Olivelli, Hervé Boutemy
-1: Vladimir Sitnikov
We'll fix the wagon-http-<>-shaded.jar licensing issue in a next release: many
options available require some time to select the best approach
PMC quorum
here is my +1
Regards,
Hervé
Le dimanche 3 novembre 2019, 21:04:16 CET Hervé BOUTEMY a écrit :
> Hi,
>
> We solved 5 issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318122&ve
> rsion=12345956&styleName=Text
>
> There are still a couple of issues left in JIRA:
> htt
Hi,
we have a plugin, the maven-scripting-plugin that has never been released !!
https://github.com/apache/maven-scripting-plugin
Many months ago I tried to help the plugin as it had a contribution.
Shall we cut a release or shall we drop it ?
In case of a release, I can do it, but I will need
+1 (non binding) from me in the current form.
I have tested on Linux (Fedora 30) + jdk8 (1.8.0_222, vendor: AdoptOpenJDK)
The licensing issue can be addressed in a new release, we have ideas and we
are working on it.
In my opinion it is not good to block this release.
Wagon Http is used and distri
Hi,
We solved 6 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317422&version=12343262
There are still a couple of issues left in JIRA:
https://issues.apache.org/jira/issues/?jql=project%20%3D%20MEAR%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20key%20DESC%2C%2
Github is not our issue management system, could you create a JIRA issue at
https://issues.apache.org/jira/browse/ARCHETYPE
thanks,
Robert
On 11-11-2019 20:40:33, Lukasz Lenart wrote:
Here is draft PR
https://github.com/apache/maven-archetype/pull/33
Regards
--
Łukasz
+ 48 606 323 122 http://
Here is draft PR
https://github.com/apache/maven-archetype/pull/33
Regards
--
Łukasz
+ 48 606 323 122 http://www.lenart.org.pl/
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h.
https://github.com/apache/maven/tree/mng-5668-poc is my POC implementation
for anyone interested in trying it out.
Here's a pom that builds with the PoC
4.0.0
localdomain
foo
1.0-SNAPSHOT
maven-antrun-plugin
Hi Elliotte,
On 11.11.19 19:55, Elliotte Rusty Harold wrote:
What is the significance of the M2/M3 classifier in the version
string? It's not obvious to me whether this is a release version or
not.
This is a milestone which is not finally the whole work intended to be
done for 3.0.0 which will
W dniu pon., 11.11.2019 o 19:24 Robert Scholte
napisał(a):
> bq. Now an empty archetype is added to the catalog.
>
> So this is what should be fixed, don't introduce a skip-parameter for it.
Hm... I can try to detect project packaging but I am not sure if everyone
is using maven-archetype [1] t
What is the significance of the M2/M3 classifier in the version
string? It's not obvious to me whether this is a release version or
not.
Is there a reason not to call this simply 3.0.0 or 3.0.1?
On Mon, Nov 11, 2019 at 1:50 PM Karl Heinz Marbaise wrote:
>
> Hi,
>
> I've seen there are a lot of f
Hi,
I've seen there are a lot of fixes in the meantime in the current state
so I would like to cut a release and the end of the week.
So if someone has any objections please raise your hand.
Kind regards
Karl Heinz Marbaise
-
bq. Now an empty archetype is added to the catalog.
So this is what should be fixed, don't introduce a skip-parameter for it.
Robert
On 11-11-2019 18:39:38, Lukasz Lenart wrote:
Hi,
Is there an option to skip a project when updating local catalog? I
have a multi-module project and I would like
This is not the point Tibor and I'll just repeat it a last time: there are
fixes in this version - rerun is not one - and we agreed one month ago to
let it be released as a milestone. There is no real way to excuse the fact
we missed it cause of other featurethis is exactly why it is milestones
Hi,
Is there an option to skip a project when updating local catalog? I
have a multi-module project and I would like to skip the parent
project when updating the catalog. Now an empty archetype is added to
the catalog.
I noticed that there is option but it's used to skip
integration tests, not t
Looks like I was wrong, everything is ok when using the latest Archetype Plugin.
On 2019/11/03 15:02:56, Lukasz Lenart wrote:
> Hi,>
>
> I'm working on Struts Archetypes [1] and discovered that running:>
>
> mvn clean install archetype:update-local-catalog>
>
> will create/update "~/.m2/reposit
Romain, You have to understand also me, users, contributors. You are not
alone. Olivier is also not alone.
See the others, e.g. Enrico, Jonathan, Matt, etc. They are greatly
communicating, understanding, and they are petitioned what it means to
accept requirements from others and making a compromis
@Tibor: I'd like to gently remind you that we - asf - are community driven
and holding a release is generally bad if it does not bite us after which
is the case there. As mentionned by Olivier we already agreed to release
and it got delayed for no reason compared to the original agreement. Please
u
Roman, it does not make sense to continue with you because you do not
understand the whole track with this project, and again nobody said
anything about architecture. It's your permanent opinions and very bad
attitude. So it is waste of the time to continue to explain the same things
over rand over
@Tibor: point is more that we don't need to hold a milestone for a feature,
we can just release and let fixes get out and get this huge architectural
change in another milestone. Only valid reason to delay a release is IMO a
regression or a major change we can't revert later (3.0.0 would be in this
The reason of M4 was to introduce TCP communication.
Meanwhile first we wanted to cut the release one month ago but we postponed
it and we were waiting for clarifying license issues and fixed J13 issue
yesterday.
I was working on TCP/Pipes together with Jonathan Bell and we wanted to
make it in M4
+1 to release next week, no reason to wait since it is another "m" release
IMHO
Le lun. 11 nov. 2019 à 12:44, Olivier Lamy a écrit :
> That will be great.
> If you don't have time before end of the week. I'm happy to help and do it.
> cheers
> Olivier
>
> On Mon, 11 Nov 2019 at 21:35, Tibor Diga
That will be great.
If you don't have time before end of the week. I'm happy to help and do it.
cheers
Olivier
On Mon, 11 Nov 2019 at 21:35, Tibor Digana wrote:
> @Olivier as we clarified this Slack. The release will be fast. No delay!
>
> On Mon, Nov 11, 2019 at 12:07 PM Olivier Lamy wrote:
>
@Olivier as we clarified this Slack. The release will be fast. No delay!
On Mon, Nov 11, 2019 at 12:07 PM Olivier Lamy wrote:
> Why? delay again
> I thought 1 month ago we agreed ago to move non finished stuff to 3.0.0-M5
> and release 3.0.0-M5 later.
>
>
> On Mon, 11 Nov 2019 at 20:59, Tibor Di
Why? delay again
I thought 1 month ago we agreed ago to move non finished stuff to 3.0.0-M5
and release 3.0.0-M5 later.
On Mon, 11 Nov 2019 at 20:59, Tibor Digana wrote:
> Pls don't do it.
> I will cut it and move some issues to M5 but I need Matt to finish his
> work. I am in contact with Mat.
Pls don't do it.
I will cut it and move some issues to M5 but I need Matt to finish his
work. I am in contact with Mat.
I talked about it with the contributor Jonathan Bell about reasoning.
T
On Mon, Nov 11, 2019 at 11:41 AM Olivier Lamy wrote:
> Hi
> Starting again this thread as we agreed but
Hi
Starting again this thread as we agreed but I didn't do it.
So I'd like to cut release 3.0.0-M4 by the end of this week.
On Mon, 14 Oct 2019 at 11:40, Tibor Digana wrote:
> The SUREFIRE-1689 progress has been finished until the CI build succeeds.
> T
>
> On Sun, Oct 13, 2019 at 10:27 AM Rob
30 matches
Mail list logo
