Having trouble running Maven Core with in an IDE.
I've tried all the pages under
https://maven.apache.org/guides/development/guide-maven-development.html
but nothing specific about running within an IDE.
I'm trying to use IntelliJ and get the following output.
The only way this makes sense if it's fully automatic: all code is
formatted on merge, period, without extra commits or human thought.
Anything less is a big -1 from me.
On Wed, Oct 12, 2022 at 4:24 PM Guillaume Nodet wrote:
>
> Related to the discussion about automatically formatting and
+1 to push manually once the vote suceeded, forks can be used during the
vote time. Several asf projects do it with quite some success.
Le sam. 15 oct. 2022 à 14:19, Slawomir Jaranowski
a écrit :
> For failed release I would prefer
> - revert commits if needed - we will have history
> - remove
For failed release I would prefer
- revert commits if needed - we will have history
- remove tag
try again :-)
If we bump versions only caused by technical problems during release we
need to change / create labels in jira, move labeled issues and so on
And we can have questions why some versions
Unpopular opinion:
Deactivate automatic push. If release:perform went well, push main and the tags.
Besides, push --delete works for tags, too (if PMC agrees).
I doubt there are already forks from the tag active anywhere.
But yes, bumping the version is what we used to do in this case.
- Ben
Why alpha-2, we didn't release alpha-1.
Even if some technical problems occur during release we should reuse the
final tag.
In jira we have a label for alpha-1.
sob., 15 paź 2022 o 02:19 Guillaume Nodet napisał(a):
> I've staged a release candidate at
>
Hi,
Link for biaries is:
https://repository.apache.org/content/repositories/maven-1811/org/apache/maven/apache-maven/4.0.0-alpha-2/
By the way binaries should be available at distribution area also ...
https://dist.apache.org/repos/dist/dev/maven/
Did you publish a staging Maven site somewhere?
Le ven. 14 oct. 2022 à 22:14, Jochen Wiedmann a
écrit :
> Hi, Guillaume,
>
> rather than suggesting (and, what's worse: discussing) code change
> details: Is there, by any change, an existing code style, that we
> might adopt? In particular.could we reuse tools, like an Eclipse
> fornatter, and
