Re: [VOTE] Release Apache Maven Doxia Sitetools version 2.0.0

2024-10-07 Thread Tamás Cservenák
+1

On Sun, Oct 6, 2024 at 8:49 PM Michael Osipov  wrote:
>
> Hi,
>
> we solved 107 issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317320&version=12354040
>
> There are still a couple of issues left in JIRA:
> https://issues.apache.org/jira/issues/?jql=project%20%3D%2012317320%20AND%20status%20%3D%20Open
>
> Staging repo:
> https://repository.apache.org/content/repositories/maven-2215
> https://repository.apache.org/content/repositories/maven-2215/org/apache/maven/doxia/doxia-sitetools/2.0.0/doxia-sitetools-2.0.0-source-release.zip
>
> Source release checksum(s):
> doxia-sitetools-2.0.0-source-release.zip
> sha512:
> 9d589ad5165add7a162343497bacd45316547be03120b282f6de4756580348386f4eff0c54da3dee1649f113f200db21772ab2d5ed307a2f29d2135f056379ed
>
> Staging site:
> https://maven.apache.org/doxia/doxia-sitetools-archives/doxia-sitetools-LATEST/
>
> Guide to testing staged releases:
> https://maven.apache.org/guides/development/guide-testing-releases.html
>
> Vote open for 72 hours.
>
> [ ] +1
> [ ] +0
> [ ] -1
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org



Re: [VOTE] Release Apache Maven Dependency Analyzer version 1.15.0

2024-10-07 Thread Slawomir Jaranowski
On Sun, 6 Oct 2024 at 15:12, Tamás Cservenák  wrote:
>
> +1
>
> But asm is not shaded or alike, so one can up it as plugin dep, no?

True ... can be overridden by dependencies.

>
> T
>
> On Sun, Oct 6, 2024, 12:22 Sylwester Lachiewicz 
> wrote:
>
> > +1
> >
> > While there is new version of ASM
> >
> > https://asm.ow2.io/versions.html with few additions
> >
> >
> >
> >
> > niedz., 6 paź 2024, 12:04 użytkownik Michael Osipov 
> > napisał:
> >
> > > Am 2024-10-04 um 19:13 schrieb Slawomir Jaranowski:
> > > > Hi,
> > > >
> > > > We solved 4 issue:
> > > >
> > >
> > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317922&version=12354753
> > > >
> > > > There are still a couple of issues left in JIRA:
> > > >
> > >
> > https://issues.apache.org/jira/issues/?jql=project%20%3D%20MSHARED%20AND%20resolution%20%3D%20Unresolved%20AND%20component%20%3D%20maven-dependency-analyzer
> > > >
> > > > Staging repo:
> > > > https://repository.apache.org/content/repositories/maven-2214/
> > > >
> > >
> > https://repository.apache.org/content/repositories/maven-2214/org/apache/maven/shared/maven-dependency-analyzer/1.15.0/maven-dependency-analyzer-1.15.0-source-release.zip
> > > >
> > > >
> > > > Source release checksum(s):
> > > > maven-dependency-analyzer-1.15.0-source-release.zip - SHA-512 :
> > > >
> > >
> > d26eb9cc9e1aeb7d7e5da4f172bb44b2decbb565bd84669f8d2547f3995ef0a2ae599f7bfed21845fdc0384cac3caf51a2739e4b808f5527f2d88e36392d00b9
> > > >
> > > > Staging site:
> > > >
> > >
> > https://maven.apache.org/shared-archives/maven-dependency-analyzer-LATEST/
> > > >
> > > > Guide to testing staged releases:
> > > >
> > https://maven.apache.org/guides/development/guide-testing-releases.html
> > > >
> > > > Vote open for at least 72 hours.
> > >
> > > +1
> > >
> > > -
> > > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> > > For additional commands, e-mail: dev-h...@maven.apache.org
> > >
> > >
> >



-- 
Sławomir Jaranowski

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org



Re: [VOTE] Release Apache Maven Doxia Sitetools version 2.0.0

2024-10-07 Thread Sylwester Lachiewicz
+1

pon., 7 paź 2024, 08:59 użytkownik Slawomir Jaranowski <
s.jaranow...@gmail.com> napisał:

> +1
>
> On Sun, 6 Oct 2024 at 20:52, Michael Osipov  wrote:
> >
> > Hi,
> >
> > we solved 107 issues:
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317320&version=12354040
> >
> > There are still a couple of issues left in JIRA:
> >
> https://issues.apache.org/jira/issues/?jql=project%20%3D%2012317320%20AND%20status%20%3D%20Open
> >
> > Staging repo:
> > https://repository.apache.org/content/repositories/maven-2215
> >
> https://repository.apache.org/content/repositories/maven-2215/org/apache/maven/doxia/doxia-sitetools/2.0.0/doxia-sitetools-2.0.0-source-release.zip
> >
> > Source release checksum(s):
> > doxia-sitetools-2.0.0-source-release.zip
> > sha512:
> >
> 9d589ad5165add7a162343497bacd45316547be03120b282f6de4756580348386f4eff0c54da3dee1649f113f200db21772ab2d5ed307a2f29d2135f056379ed
> >
> > Staging site:
> >
> https://maven.apache.org/doxia/doxia-sitetools-archives/doxia-sitetools-LATEST/
> >
> > Guide to testing staged releases:
> > https://maven.apache.org/guides/development/guide-testing-releases.html
> >
> > Vote open for 72 hours.
> >
> > [ ] +1
> > [ ] +0
> > [ ] -1
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> > For additional commands, e-mail: dev-h...@maven.apache.org
> >
>
>
> --
> Sławomir Jaranowski
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>


[DISCUSS] Merge ITs in maven

2024-10-07 Thread Guillaume Nodet
I'd like to discuss merging ITs into maven core repository.
The ITs have already been splitted some time ago between the 3.x branch and
master for testing Maven master.  But I don't really see a good reason to
keep the repositories separated, this makes things more complicated when
modifying maven code and adding ITs.

The following script allow merging the two repositories while keeping both
histories:


brew install git-filter-repo

git clone https://github.com/apache/maven

git clone https://github.com/apache/maven-integration-testing

(cd maven-integration-testing && \

git filter-repo --to-subdirectory-filter its)

(cd maven && \

git remote add its ../maven-integration-testing && \

git fetch its --no-tags && \

EDITOR=true git merge --allow-unrelated-histories its/master && \

git remote remove its)

The next step would be to actually include them in a profile and update the
github workflow.
I think they could be refactored to:
  * first perform a full  run on Ubuntu + latest LTS JDK:
 - restore cache
 -  checkout
 -  build with no tests
 - run IT bootstrap (to prime local repo)
 - save cache
 - build again with tests and ITs
  * if this first run succeeds, do the same on other platforms / jdks

The cache is important to add imho.  It seems lately, GH runners have often
problems downloading from maven central, so that would help a lot
increasing the stability.  So using
https://github.com/marketplace/actions/maven-cache or a similar action
would be handy imho.

We should also upload nightlies from GH.
And automate the releases as much as possible

-- 

Guillaume Nodet