sorry, I forgot to do it while merging
done: I hope the result will be as good as expected
Regards,
Hervé
Le mardi 15 janvier 2019, 16:09:22 CET Mickael Istria a écrit :
> Hi again,
>
> The (hopefully) final patch to make save GBs of RAM in m2e was merged in
> Maven earlier today.
> I'd like
Hi again,
The (hopefully) final patch to make save GBs of RAM in m2e was merged in
Maven earlier today.
I'd like m2e CI builds to be able to test against it. Can someone please
publish the current master as SNAPSHOT ?
Cheers,
Obligatory, "Trunk-Based Development (with short-lived feature branches if
you like) is best" -
https://trunkbaseddevelopment.com/short-lived-feature-branches/ - *shout
out*.
- Paul (majority author of the above site).
Hi,
master seems by far enough to me, and I think support for specific other
branches should be considered in another future step if it happens to be
requested one day.
About nightly, I think it's usually not such a good rule. I wrote about it
some time ago when I started to deal with release
+1 for master and nightly, timezone is not so important
Enrico
Il gio 10 gen 2019, 21:44 Stephen Connolly
ha scritto:
> I say if we are doing automatic snapshot deployment, master branch only and
> either weekly or daily or on every commit... pick one for all our projects.
>
> Other branches
I say if we are doing automatic snapshot deployment, master branch only and
either weekly or daily or on every commit... pick one for all our projects.
Other branches would just confuse things so keep them as manual deployment
and if doing that require the branch name included in the version
We already had this discussion so many times and it always turns to non
ended complicated discussion with very complicated cases which NEVER happen
here
So the most important is: We must take it easy and avoid overthinking!.
+1 for every night a master snapshot or every master changes.
but
how about just deploy nightly snapshot of active 'main' branch ( ie master)?
-D
On Thu, Jan 10, 2019 at 9:03 AM Robert Scholte wrote:
> Now that we use branches actively, it is way more important where a
> SNAPSHOT is coming from.
> I've seen it too often that people thought they were testing
Now that we use branches actively, it is way more important where a
SNAPSHOT is coming from.
I've seen it too often that people thought they were testing with a
version from a specific branch, but that it was redeployed with another
version.
The first steps are done to rewrite the pom-file
On Thu, 10 Jan 2019 at 09:11, Mickael Istria wrote:
> Hi,
>
> Eclipse m2e, as a consumer of Maven as a library, would love to see the
> latest HEAD from master published automatically as SNAPSHOTs soon after
> every change is made. This seems like a requirement to enable continuous
> feedback
Hi,
Eclipse m2e, as a consumer of Maven as a library, would love to see the
latest HEAD from master published automatically as SNAPSHOTs soon after
every change is made. This seems like a requirement to enable continuous
feedback from m2e to Maven.
Publishing some other branches or commits
The question is more what our policy is.
In my opinion you need one of two policies:
* snapshots are deployed manually
* snapshots are deployed automatically from a specific branch
We have used manual as our policy. If we change that’s fine, but we should
stop manual deployment and clarify the
We should only have to setup a CI job which does
mvn deploy
AFAIK ASF Jenkins are allowed to push snapshots
Enrico
Il gio 10 gen 2019, 00:34 Mickael Istria ha scritto:
> On Wednesday, January 9, 2019, Robert Scholte
> wrote:
>
> > I've just deployed the SNAPSHOTs from current master to
> >
On Wednesday, January 9, 2019, Robert Scholte wrote:
> I've just deployed the SNAPSHOTs from current master to
> repository.apache.org
>
Thanks a lot! Could it be done continuously? Technicallu, a CI job.checking
the repo could tale care of doing it soon after each change without further
human
I've just deployed the SNAPSHOTs from current master to
repository.apache.org
Robert
On Wed, 09 Jan 2019 19:16:40 +0100, Mickael Istria
wrote:
Hi,
I'd like to give a try to latest Maven snapshots with m2e. As it's on an
automated verification build, I can't build the snapshots locally.
15 matches
Mail list logo
