Re: I am wandering how you do guys debug maven?
John,
I must call you master, it's pretty long since 2005! :-)
I got you now, add the profile and run by it.
Thanks a lot! man.
Simon(ChengHong) Sheng
On Fri, Oct 12, 2018 at 2:42 PM John Patrick wrote:
> simon,
> been using maven since 2005 so 1.x something, so might be better way
> as often i discover features added several releases ago that i simply
> missed to kept using the old approach as it works and isn't broken.
> Something like;
>
> ...
>
> ...
>
> debug
>
> 5005
>
> -agentlib:jdwp=transport=dt_socket,server=y,suspend=y,address=${project.debug.port}
>
>
> ...
>
> ...
>
>
> ${project.debug.args}
>
>
>
>
> then "mvn -Pdebug test" and surefire uses the argLine user property.
> then if you want to change the port "mvn -Pdebug
> -Dproject.debug.port=8000 test". the important part is suspend=y.
>
> Reading the latest
>
> https://maven.apache.org/surefire/maven-surefire-plugin/examples/debugging.html
> ,
> then "mvn -Dmaven.surefire.debug test" should setup a debug port on
> 5005 but i've only just seen that in the latest documentation but i've
> probably not looked at surefire documentation for debugging for maybe
> 6+ years.
>
> John
>
> On Fri, 12 Oct 2018 at 20:25, Simon Sheng wrote:
> >
> > Hi John,
> >
> > I am trying the profile, but no matter 5005 or 8000 port, I can't start
> > debug. Would you please give me more detail of this profile.
> >
> > I global search maven source code, only classworld pom file has debug
> > profile.
> >
> > I am looking into the wrapper you mentioned.
> >
> > Thank you!
> >
> > Simon(ChengHong) Sheng
> >
> >
> > On Tue, Oct 9, 2018 at 5:24 AM John Patrick
> wrote:
> >
> > > others have talked about mvnDebug, i prefer using a profile e.g.
> > > debug, then all the surefire and failsafe and exec-maven-plugin, plus
> > > other plugins are all configured to use ${DEBUG_ARGS}, then;
> > >
> > > $ mvn -Pdebug test
> > > $ mvn -Pdebug exec:java
> > >
> > > Then in intellij/eclipse/netbeans I can just connect a remote debugger
> > > to the code. For some situations you want it to pause the execute
> > > until your debugger is connected otherwise you might miss breakpoints
> > > if those test are executed 1st.
> > >
> > > I've also switched to maven wrapper so don't have mvnDebug anymore as
> > > it means developers don't need to keep their local machines in sync
> > > and just do mvnw and it will sort out the maven version that
> > > project/branch requires.
> > >
> > >
> > > On Tue, 9 Oct 2018 at 06:29, Tibor Digana
> wrote:
> > > >
> > > > In IntelliJ IDEA it is "Remote", see Select Run/Debug Configurations
> >
> > > > Remote, change the port to 8000.
> > > > Run command *mvnDebug test* and then start "Remote" in IDEA.
> > > >
> > > > On Tue, Oct 9, 2018 at 6:16 AM Romain Manni-Bucau <
> rmannibu...@gmail.com
> > > >
> > > > wrote:
> > > >
> > > > > Hello
> > > > >
> > > > > Not sure the question was about test classes - you got answers for
> > > that ;)
> > > > > - or maven and plugins themselves. If the last one, just replace
> "mvn"
> > > by
> > > > > "mvnDebug" in any command and remote debug on port 8000 in your
> IDE.
> > > > >
> > > > > Side note: if you check mvn script you will see maven has a main
> class
> > > so
> > > > > can be remote debugged as any java software ;)
> > > > >
> > > > > Le mar. 9 oct. 2018 05:44, Olivier Lamy a
> écrit :
> > > > >
> > > > > > an other option is to use command line and the surefire option:
> > > > > > -Dmaven.surefire.debug=true
> > > > > > then you can have debug on port 5005 (look at your ide to start a
> > > remote
> > > > > > debug)
> > > > > >
> > > > > > On Tue, 9 Oct 2018 at 08:45, Enrico Olivelli <
> eolive...@gmail.com>
> > > > > wrote:
> > > > > >
> > > > > > > Il lun 8 ott 2018, 23:23 Jeff MAURY ha
> > > scritto:
> > > > > > >
> > > > > > > > M2e takes care of everything
> > > > > > > >
> > > > > > >
> > > > > > > Same for Apache Netbeans :)
> > > > > > >
> > > > > > > Enrico
> > > > > > >
> > > > > > >
> > > > > > > > Jeff
> > > > > > > >
> > > > > > > > Le lun. 8 oct. 2018 à 23:09, Simon Sheng <
> simonshe...@gmail.com>
> > > a
> > > > > > > écrit :
> > > > > > > >
> > > > > > > > > Hi,
> > > > > > > > >
> > > > > > > > > I am bringing this baby question since Maven load all it's
> > > classes
> > > > > by
> > > > > > > > > ClassWorlds. Which means it doesn't have "main method".
> > > instead we
> > > > > > > debug
> > > > > > > > > everything by log, do we have other way like debug with any
> > > IDE:
> > > > > > > Eclipse,
> > > > > > > > > Intellij etc. put breakpoints and debug step by step ?
> > > > > > > > >
> > > > > > > > > Thanks
> > > > > > > > >
> > > > > > > > > Simon(ChengHong) Sheng
> > > > > > > > >
> > > > > > > >
> > > > > > > --
> > > > > > >
> > > > > > >
> > > > > > > -- Enrico Olivelli
> > > > > > >
> > > > > >
> > > > > >
> > > > > > --
> > > > > > Olivier Lamy
> > > > > > http://twitter.com/olamy | http://linkedin.com/in/olamy
> > > > >
Re: I am wandering how you do guys debug maven?
simon,
been using maven since 2005 so 1.x something, so might be better way
as often i discover features added several releases ago that i simply
missed to kept using the old approach as it works and isn't broken.
Something like;
...
...
debug
5005
-agentlib:jdwp=transport=dt_socket,server=y,suspend=y,address=${project.debug.port}
...
...
${project.debug.args}
then "mvn -Pdebug test" and surefire uses the argLine user property.
then if you want to change the port "mvn -Pdebug
-Dproject.debug.port=8000 test". the important part is suspend=y.
Reading the latest
https://maven.apache.org/surefire/maven-surefire-plugin/examples/debugging.html,
then "mvn -Dmaven.surefire.debug test" should setup a debug port on
5005 but i've only just seen that in the latest documentation but i've
probably not looked at surefire documentation for debugging for maybe
6+ years.
John
On Fri, 12 Oct 2018 at 20:25, Simon Sheng wrote:
>
> Hi John,
>
> I am trying the profile, but no matter 5005 or 8000 port, I can't start
> debug. Would you please give me more detail of this profile.
>
> I global search maven source code, only classworld pom file has debug
> profile.
>
> I am looking into the wrapper you mentioned.
>
> Thank you!
>
> Simon(ChengHong) Sheng
>
>
> On Tue, Oct 9, 2018 at 5:24 AM John Patrick wrote:
>
> > others have talked about mvnDebug, i prefer using a profile e.g.
> > debug, then all the surefire and failsafe and exec-maven-plugin, plus
> > other plugins are all configured to use ${DEBUG_ARGS}, then;
> >
> > $ mvn -Pdebug test
> > $ mvn -Pdebug exec:java
> >
> > Then in intellij/eclipse/netbeans I can just connect a remote debugger
> > to the code. For some situations you want it to pause the execute
> > until your debugger is connected otherwise you might miss breakpoints
> > if those test are executed 1st.
> >
> > I've also switched to maven wrapper so don't have mvnDebug anymore as
> > it means developers don't need to keep their local machines in sync
> > and just do mvnw and it will sort out the maven version that
> > project/branch requires.
> >
> >
> > On Tue, 9 Oct 2018 at 06:29, Tibor Digana wrote:
> > >
> > > In IntelliJ IDEA it is "Remote", see Select Run/Debug Configurations >
> > > Remote, change the port to 8000.
> > > Run command *mvnDebug test* and then start "Remote" in IDEA.
> > >
> > > On Tue, Oct 9, 2018 at 6:16 AM Romain Manni-Bucau > >
> > > wrote:
> > >
> > > > Hello
> > > >
> > > > Not sure the question was about test classes - you got answers for
> > that ;)
> > > > - or maven and plugins themselves. If the last one, just replace "mvn"
> > by
> > > > "mvnDebug" in any command and remote debug on port 8000 in your IDE.
> > > >
> > > > Side note: if you check mvn script you will see maven has a main class
> > so
> > > > can be remote debugged as any java software ;)
> > > >
> > > > Le mar. 9 oct. 2018 05:44, Olivier Lamy a écrit :
> > > >
> > > > > an other option is to use command line and the surefire option:
> > > > > -Dmaven.surefire.debug=true
> > > > > then you can have debug on port 5005 (look at your ide to start a
> > remote
> > > > > debug)
> > > > >
> > > > > On Tue, 9 Oct 2018 at 08:45, Enrico Olivelli
> > > > wrote:
> > > > >
> > > > > > Il lun 8 ott 2018, 23:23 Jeff MAURY ha
> > scritto:
> > > > > >
> > > > > > > M2e takes care of everything
> > > > > > >
> > > > > >
> > > > > > Same for Apache Netbeans :)
> > > > > >
> > > > > > Enrico
> > > > > >
> > > > > >
> > > > > > > Jeff
> > > > > > >
> > > > > > > Le lun. 8 oct. 2018 à 23:09, Simon Sheng
> > a
> > > > > > écrit :
> > > > > > >
> > > > > > > > Hi,
> > > > > > > >
> > > > > > > > I am bringing this baby question since Maven load all it's
> > classes
> > > > by
> > > > > > > > ClassWorlds. Which means it doesn't have "main method".
> > instead we
> > > > > > debug
> > > > > > > > everything by log, do we have other way like debug with any
> > IDE:
> > > > > > Eclipse,
> > > > > > > > Intellij etc. put breakpoints and debug step by step ?
> > > > > > > >
> > > > > > > > Thanks
> > > > > > > >
> > > > > > > > Simon(ChengHong) Sheng
> > > > > > > >
> > > > > > >
> > > > > > --
> > > > > >
> > > > > >
> > > > > > -- Enrico Olivelli
> > > > > >
> > > > >
> > > > >
> > > > > --
> > > > > Olivier Lamy
> > > > > http://twitter.com/olamy | http://linkedin.com/in/olamy
> > > > >
> > > >
> >
> > -
> > 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: I am wandering how you do guys debug maven?
Hi John,
I am trying the profile, but no matter 5005 or 8000 port, I can't start
debug. Would you please give me more detail of this profile.
I global search maven source code, only classworld pom file has debug
profile.
I am looking into the wrapper you mentioned.
Thank you!
Simon(ChengHong) Sheng
On Tue, Oct 9, 2018 at 5:24 AM John Patrick wrote:
> others have talked about mvnDebug, i prefer using a profile e.g.
> debug, then all the surefire and failsafe and exec-maven-plugin, plus
> other plugins are all configured to use ${DEBUG_ARGS}, then;
>
> $ mvn -Pdebug test
> $ mvn -Pdebug exec:java
>
> Then in intellij/eclipse/netbeans I can just connect a remote debugger
> to the code. For some situations you want it to pause the execute
> until your debugger is connected otherwise you might miss breakpoints
> if those test are executed 1st.
>
> I've also switched to maven wrapper so don't have mvnDebug anymore as
> it means developers don't need to keep their local machines in sync
> and just do mvnw and it will sort out the maven version that
> project/branch requires.
>
>
> On Tue, 9 Oct 2018 at 06:29, Tibor Digana wrote:
> >
> > In IntelliJ IDEA it is "Remote", see Select Run/Debug Configurations >
> > Remote, change the port to 8000.
> > Run command *mvnDebug test* and then start "Remote" in IDEA.
> >
> > On Tue, Oct 9, 2018 at 6:16 AM Romain Manni-Bucau >
> > wrote:
> >
> > > Hello
> > >
> > > Not sure the question was about test classes - you got answers for
> that ;)
> > > - or maven and plugins themselves. If the last one, just replace "mvn"
> by
> > > "mvnDebug" in any command and remote debug on port 8000 in your IDE.
> > >
> > > Side note: if you check mvn script you will see maven has a main class
> so
> > > can be remote debugged as any java software ;)
> > >
> > > Le mar. 9 oct. 2018 05:44, Olivier Lamy a écrit :
> > >
> > > > an other option is to use command line and the surefire option:
> > > > -Dmaven.surefire.debug=true
> > > > then you can have debug on port 5005 (look at your ide to start a
> remote
> > > > debug)
> > > >
> > > > On Tue, 9 Oct 2018 at 08:45, Enrico Olivelli
> > > wrote:
> > > >
> > > > > Il lun 8 ott 2018, 23:23 Jeff MAURY ha
> scritto:
> > > > >
> > > > > > M2e takes care of everything
> > > > > >
> > > > >
> > > > > Same for Apache Netbeans :)
> > > > >
> > > > > Enrico
> > > > >
> > > > >
> > > > > > Jeff
> > > > > >
> > > > > > Le lun. 8 oct. 2018 à 23:09, Simon Sheng
> a
> > > > > écrit :
> > > > > >
> > > > > > > Hi,
> > > > > > >
> > > > > > > I am bringing this baby question since Maven load all it's
> classes
> > > by
> > > > > > > ClassWorlds. Which means it doesn't have "main method".
> instead we
> > > > > debug
> > > > > > > everything by log, do we have other way like debug with any
> IDE:
> > > > > Eclipse,
> > > > > > > Intellij etc. put breakpoints and debug step by step ?
> > > > > > >
> > > > > > > Thanks
> > > > > > >
> > > > > > > Simon(ChengHong) Sheng
> > > > > > >
> > > > > >
> > > > > --
> > > > >
> > > > >
> > > > > -- Enrico Olivelli
> > > > >
> > > >
> > > >
> > > > --
> > > > Olivier Lamy
> > > > http://twitter.com/olamy | http://linkedin.com/in/olamy
> > > >
> > >
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>
Re: I am wandering how you do guys debug maven?
Hi Romain,
"mvnDebug" works for me. but when I read the script of mvn, I don't see
main method but this:
exec "$JAVACMD" \
17 $MAVEN_OPTS \
18 $MAVEN_DEBUG_OPTS \
19 -classpath "${M2_HOME}"/boot/plexus-classworlds-*.jar \
20 "-Dclassworlds.conf=${M2_HOME}/bin/m2.conf" \
21 "-Dmaven.home=${M2_HOME}"
"-Dmaven.multiModuleProjectDirectory=${MAVEN_PROJECTBASEDIR}" \
22 ${CLASSWORLDS_LAUNCHER} "$@"
and the "CLASSWORLDS_LAUNCHER" is
"org.codehaus.plexus.classworlds.launcher.Launcher" but not maven main.
Thanks a lot
Simon(ChengHong) Sheng
On Mon, Oct 8, 2018 at 11:16 PM Romain Manni-Bucau
wrote:
> Hello
>
> Not sure the question was about test classes - you got answers for that ;)
> - or maven and plugins themselves. If the last one, just replace "mvn" by
> "mvnDebug" in any command and remote debug on port 8000 in your IDE.
>
> Side note: if you check mvn script you will see maven has a main class so
> can be remote debugged as any java software ;)
>
> Le mar. 9 oct. 2018 05:44, Olivier Lamy a écrit :
>
> > an other option is to use command line and the surefire option:
> > -Dmaven.surefire.debug=true
> > then you can have debug on port 5005 (look at your ide to start a remote
> > debug)
> >
> > On Tue, 9 Oct 2018 at 08:45, Enrico Olivelli
> wrote:
> >
> > > Il lun 8 ott 2018, 23:23 Jeff MAURY ha scritto:
> > >
> > > > M2e takes care of everything
> > > >
> > >
> > > Same for Apache Netbeans :)
> > >
> > > Enrico
> > >
> > >
> > > > Jeff
> > > >
> > > > Le lun. 8 oct. 2018 à 23:09, Simon Sheng a
> > > écrit :
> > > >
> > > > > Hi,
> > > > >
> > > > > I am bringing this baby question since Maven load all it's classes
> by
> > > > > ClassWorlds. Which means it doesn't have "main method". instead we
> > > debug
> > > > > everything by log, do we have other way like debug with any IDE:
> > > Eclipse,
> > > > > Intellij etc. put breakpoints and debug step by step ?
> > > > >
> > > > > Thanks
> > > > >
> > > > > Simon(ChengHong) Sheng
> > > > >
> > > >
> > > --
> > >
> > >
> > > -- Enrico Olivelli
> > >
> >
> >
> > --
> > Olivier Lamy
> > http://twitter.com/olamy | http://linkedin.com/in/olamy
> >
>
Re: I am wandering how you do guys debug maven?
Hi Olivier, -Dmaven.surefier.debug=true works for me. I can remote from eclipse and intellij Another baby question: - What is the relationship between maven itself and surefire. My understanding of this is surefire is the original maven in house plugin. But maybe I am wrong. - Is the same thing to debug surefire and debug maven? this question focuses on the relationship of maven itself and surefire too since I know surefire can lead me to maven itself for sure. Thanks a lot for you help. Simon(ChengHong) Sheng On Mon, Oct 8, 2018 at 9:44 PM Olivier Lamy wrote: > an other option is to use command line and the surefire option: > -Dmaven.surefire.debug=true > then you can have debug on port 5005 (look at your ide to start a remote > debug) > > On Tue, 9 Oct 2018 at 08:45, Enrico Olivelli wrote: > > > Il lun 8 ott 2018, 23:23 Jeff MAURY ha scritto: > > > > > M2e takes care of everything > > > > > > > Same for Apache Netbeans :) > > > > Enrico > > > > > > > Jeff > > > > > > Le lun. 8 oct. 2018 à 23:09, Simon Sheng a > > écrit : > > > > > > > Hi, > > > > > > > > I am bringing this baby question since Maven load all it's classes by > > > > ClassWorlds. Which means it doesn't have "main method". instead we > > debug > > > > everything by log, do we have other way like debug with any IDE: > > Eclipse, > > > > Intellij etc. put breakpoints and debug step by step ? > > > > > > > > Thanks > > > > > > > > Simon(ChengHong) Sheng > > > > > > > > > -- > > > > > > -- Enrico Olivelli > > > > > -- > Olivier Lamy > http://twitter.com/olamy | http://linkedin.com/in/olamy >
Re: [VOTE] Release Apache Maven Resolver version 1.3.1
Hi, I have received feedback that it is not clear why we started a new release VOTE so short after the announcement of the previous one. The simple reason is that we have found an issue related to Maven Core which fails tests in Maven Core build.. And this new release will fix them... Kind regards Karl Heinz Marbaise On 11/10/18 23:06, Karl Heinz Marbaise wrote: Hi, We solved 1 issues: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320628=12344286 There are still a couple of issues left in JIRA: https://issues.apache.org/jira/issues/?jql=project%20%3D%20MRESOLVER%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20key%20DESC%2C%20priority%20DESC%2C%20updated%20DESC Staging repo: https://repository.apache.org/content/repositories/maven-1457 https://repository.apache.org/content/repositories/maven-1457/org/apache/maven/resolver/maven-resolver/1.3.1/maven-resolver-1.3.1-source-release.zip Source release checksum(s): maven-resolver-1.3.1-source-release.zip sha512: 720b527130c6380cea988d9b2c664db1f31107b9abd2e8e08bc7296eeb38557994b3bbee9770f80a5211b350a660cb8e9173b4998867287602414eb9ae201828 Staging site: https://maven.apache.org/resolver-archives/resolver-LATEST/ Guide to testing staged releases: https://maven.apache.org/guides/development/guide-testing-releases.html Vote open for at least 72 hours. [ ] +1 [ ] +0 [ ] -1 Kind regards Karl Heinz Marbaise - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Testing Release Candidates
Hi Enrico, On 12/10/18 10:36, Enrico Olivelli wrote: Hi, I would like to test Maven Plugins Release Candidates. Great that you like to help... I know there is a brief guide https://maven.apache.org/guides/development/guide-testing-releases.html But I think this is not very complete and/or it is outdated. It might be if so we need to update/enhance it as needed... The summary of the guide is to run mvn verify For instance this is not true for Surefire. Yes there are some of the release which need different approach usually documented in README.md (I'm not sure if all have a README.md...or need one)...for Maven Core this not enough (mvn clean install) and test the resulting core with different project of your own choice... Can someone explain better how is it expected to run a check on an RC ? First we don't do RC's ...what we sometimes do is to release Milestones (for example with maven-install, maven-deploy-plugin).. But in the end we release usual release something like "3.0.0" or "3.2.0" If it happens that a release has issues we remove the tags and drop the staging repository and spin a new release with the same version... For Maven core we do not use the same version we continue with the next one... In other Apache projects that I know/work on usual checks are: - try to build and run tests on the propostes source artifacts. Usually you should at least run the build on the source artifacts which includes IT's ...something like: mvn -Prun-its clean verify for plugins and for components: mvn clean verify - apache-rat/licensing issues Is already checked by the builds (see above).. - check signatures/shasums.. Usually compare the checksums in email with them which can be downloaded from the staging repositories... - check proposed maven artifacts ?? In which way? Usually voters when the give their '+1' add an explanation about the tests the performed on the RC, I see this is not very common practice in Maven VOTE threads. Sometimes yes sometimes not...usually we don't do it if nothing has been found...but if we find something than we do to find the itch.. Second question, in Maven what is really 'released' ? Are you releasing the SOURCE ZIP ? or something else ? As far as I know in Apache we are 'releasing' the source code and we are providing binaries for convenience to users. I understand that Maven is somehow a very special case. Not really. The real releases are the source artifacts (*.zip)... The binaries which are transfered to Central is as already mentioned convenience... Much to explain..that looks like we need to enhance the release procedure description... My questions are just to understand better in order to give a more significant contribution to the project, I am pointing out problems. Yeah really great... Kind regards Karl Heinz Marbaise Thank you all for carrying on Maven Project ! Cheers Enrico - 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 Resolver version 1.3.1
+1 On Fri, 12 Oct 2018 at 17:33, Robert Scholte wrote: > +1 > > On Thu, 11 Oct 2018 23:06:26 +0200, Karl Heinz Marbaise > wrote: > > > Hi, > > > > We solved 1 issues: > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320628=12344286 > > > > There are still a couple of issues left in JIRA: > > > https://issues.apache.org/jira/issues/?jql=project%20%3D%20MRESOLVER%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20key%20DESC%2C%20priority%20DESC%2C%20updated%20DESC > > > > Staging repo: > > https://repository.apache.org/content/repositories/maven-1457 > > > https://repository.apache.org/content/repositories/maven-1457/org/apache/maven/resolver/maven-resolver/1.3.1/maven-resolver-1.3.1-source-release.zip > > > > Source release checksum(s): > > maven-resolver-1.3.1-source-release.zip sha512: > > > 720b527130c6380cea988d9b2c664db1f31107b9abd2e8e08bc7296eeb38557994b3bbee9770f80a5211b350a660cb8e9173b4998867287602414eb9ae201828 > > > > Staging site: > > https://maven.apache.org/resolver-archives/resolver-LATEST/ > > > > Guide to testing staged releases: > > https://maven.apache.org/guides/development/guide-testing-releases.html > > > > Vote open for at least 72 hours. > > > > [ ] +1 > > [ ] +0 > > [ ] -1 > > > > Kind regards > > Karl Heinz Marbaise > > > > - > > 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 > > -- Olivier Lamy http://twitter.com/olamy | http://linkedin.com/in/olamy
Testing Release Candidates
Hi, I would like to test Maven Plugins Release Candidates. I know there is a brief guide https://maven.apache.org/guides/development/guide-testing-releases.html But I think this is not very complete and/or it is outdated. The summary of the guide is to run mvn verify For instance this is not true for Surefire. Can someone explain better how is it expected to run a check on an RC ? In other Apache projects that I know/work on usual checks are: - try to build and run tests on the propostes source artifacts. - apache-rat/licensing issues - check signatures/shasums.. - check proposed maven artifacts Usually voters when the give their '+1' add an explanation about the tests the performed on the RC, I see this is not very common practice in Maven VOTE threads. Second question, in Maven what is really 'released' ? Are you releasing the SOURCE ZIP ? or something else ? As far as I know in Apache we are 'releasing' the source code and we are providing binaries for convenience to users. I understand that Maven is somehow a very special case. My questions are just to understand better in order to give a more significant contribution to the project, I am pointing out problems. Thank you all for carrying on Maven Project ! Cheers Enrico - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: [VOTE] Release Apache Maven Resolver version 1.3.1
+1 On Thu, 11 Oct 2018 23:06:26 +0200, Karl Heinz Marbaise wrote: Hi, We solved 1 issues: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320628=12344286 There are still a couple of issues left in JIRA: https://issues.apache.org/jira/issues/?jql=project%20%3D%20MRESOLVER%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20key%20DESC%2C%20priority%20DESC%2C%20updated%20DESC Staging repo: https://repository.apache.org/content/repositories/maven-1457 https://repository.apache.org/content/repositories/maven-1457/org/apache/maven/resolver/maven-resolver/1.3.1/maven-resolver-1.3.1-source-release.zip Source release checksum(s): maven-resolver-1.3.1-source-release.zip sha512: 720b527130c6380cea988d9b2c664db1f31107b9abd2e8e08bc7296eeb38557994b3bbee9770f80a5211b350a660cb8e9173b4998867287602414eb9ae201828 Staging site: https://maven.apache.org/resolver-archives/resolver-LATEST/ Guide to testing staged releases: https://maven.apache.org/guides/development/guide-testing-releases.html Vote open for at least 72 hours. [ ] +1 [ ] +0 [ ] -1 Kind regards Karl Heinz Marbaise - 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
