ok, let's try: it's easy to revert :) Regards,
Hervé Le samedi 7 mars 2015 17:21:03 Karl Heinz Marbaise a écrit : > Hi Hervé, > > On 3/7/15 4:32 PM, Hervé BOUTEMY wrote: > > it's good to undesrtand the details: yes, install vs verify... > > > > Notice that it's a good thing (TM) to check releases during vote with > > verify instead of install, so the local repository doesn't get polluted > > by local build of a release that will later have an official build on > > central > > > > should we change Jankins configuration with verify instead of install? > > That's what i'm thinking of cause it would have alarmed us before doing > the VOTE.... > > Kind regards > Karl Heinz Marbaise > > > Regards, > > > > Hervé > > > > Le samedi 7 mars 2015 15:36:56 Karl Heinz Marbaise a écrit : > >> Hi Hervé, > >> > >> what made me mad was that our buildservers haven't alarmed us on such > >> problem... > >> > >> After diving a little bit into it i have found out the real difference > >> between my usage on our build servers / in the bug description and my > >> usage: > >> > >> The build servers use: mvn -Prun-its clean install > >> I have used: mvn -Prun-its clean verify (i use it allways) > >> > >> If i use mvn -Prun-its clean verify the maven-invoker-plugin (version > >> 1.7) doesn't install all artifacts in the local integration test > >> repository despite the fact of using the `install` goal, which seems the > >> real problem. version 1.9 looks ok. > >> > >> If you use mvn -Prun-its clean install it will be installed during the > >> module build in the users local repository...and will be accessible > >> during the integration tests. > >> > >> This is the reason why it has not been itched us yet... > >> > >> > >> Kind regards > >> Karl Heinz Marbaise > >> > >> On 3/7/15 3:12 PM, Hervé BOUTEMY wrote: > >>> ok, thank you for the precision: in this case, this is really a > >>> showstopper > >>> > >>> the bug is more strange: it affects distribution but not git checkout :/ > >>> > >>> hopefully, newer m-invoker-p version seems ok with distribution > >>> > >>> let's try... > >>> > >>> Regards, > >>> > >>> Hervé > >>> > >>> Le samedi 7 mars 2015 13:53:09 Karl Heinz Marbaise a écrit : > >>>> Hi Hervé , > >>>> > >>>> On 3/7/15 12:16 PM, Hervé BOUTEMY wrote: > >>>>> like Benson, I wanted to understand why we didn't find the issue > >>>>> before > >>>>> the > >>>>> release (I built the git HEAD without any issue) > >>>> > >>>> I have added the appropriate log files for Maven 3.0.5, 3.1.1, 3.2.5 > >>>> where i have always the same issue with Maven Invoker 1.7....just for > >>>> the record and for the history... > >>>> > >>>> If the bug had only itched Maven 2.2.1 i would have ignored but it > >>>> itched all Maven versions... > >>>> > >>>>> looking at the build logs, it seems that it's only an issue when built > >>>>> with > >>>>> Maven 2.2.1 (which I didn't test), and the bug seems more in > >>>>> m-invoker-p > >>>>> than in archetype > >>>> > >>>> Of course i wrote so....but unfortunately not only Maven 2.2.1 all > >>>> other > >>>> maven versions as well... > >>>> > >>>>> then, personally, I wouldn't have cancelled the vote... > >>>>> > >>>>> that's really a good thing (TM) that we stop Maven 2.2.1 support for > >>>>> plugins! at least, this cancelled release clearly shows one thing we > >>>>> gain > >>>>> from it. > >>>>> > >>>>> Regards, > >>>>> > >>>>> Hervé > >>>>> > >>>>> Le vendredi 6 mars 2015 18:19:08 Karl Heinz Marbaise a écrit : > >>>>>> Hi Benson, > >>>>>> > >>>>>> I have attached the appropriate log files to the JIRA ticket... > >>>>>> > >>>>>> Kind regards > >>>>>> Karl Heinz Marbaise > >>>>>> > >>>>>> On 3/6/15 3:22 PM, Benson Margulies wrote: > >>>>>>> I'll respin, but I wonder why it failed to bite me. > >>>>>>> > >>>>>>> On Fri, Mar 6, 2015 at 2:59 AM, Karl Heinz Marbaise > >>>>>>> <[email protected]> > >>>>> > >>>>> wrote: > >>>>>>>> Hi Benson, > >>>>>>>> > >>>>>>>> first the link to the release is unfortunately wrong...the correct > >>>>>>>> link > >>>>>>>> is: > >>>>>>>> > >>>>>>>> https://repository.apache.org/content/repositories/maven-1146/org/a > >>>>>>>> pa > >>>>>>>> ch > >>>>>>>> e/ > >>>>>>>> maven/archetype/maven-archetype/2.3/maven-archetype-2.3-source-rele > >>>>>>>> as > >>>>>>>> e. > >>>>>>>> zi > >>>>>>>> p > >>>>>>>> > >>>>>>>> Checked SHA1 Ok... > >>>>>>>> > >>>>>>>> Next step checking with Maven 2.2.1, 3.0.5, 3.1.1, 3.2.5 via mvn > >>>>>>>> -Prun-its > >>>>>>>> clean verify > >>>>>>>> > >>>>>>>> i have found that two integration tests are failing for all Maven > >>>>>>>> versions: > >>>>>>>> > >>>>>>>> [ERROR] The following builds failed: > >>>>>>>> [ERROR] * build-archetype/pom.xml > >>>>>>>> [ERROR] * property-setting-cli/pom.xml > >>>>>>>> > >>>>>>>> After looking a little bit into it...i found out that if i change > >>>>>>>> the > >>>>>>>> maven-invoker-plugin version in maven-archetype-plugin from 1.7 to > >>>>>>>> 1.9 > >>>>>>>> it > >>>>>>>> works without any issue. I have created an issue for that > >>>>>>>> http://jira.codehaus.org/browse/ARCHETYPE-477 and fixed it in git > >>>>>>>> > >>>>>>>> Unfortunately that this issue is for all > >>>>>>>> Maven versions i have to give: -1 > >>>>>>>> > >>>>>>>> Cause this would result in a release package which can't be built > >>>>>>>> without > >>>>>>>> changing it.... > >>>>>>>> > >>>>>>>> Kind regards > >>>>>>>> Karl Heinz Marbaise > >>>>>>>> > >>>>>>>> On 3/6/15 1:21 AM, Benson Margulies wrote: > >>>>>>>>> Hi, > >>>>>>>>> > >>>>>>>>> This is a vote to release Archetype 2.3, intended as the last > >>>>>>>>> version > >>>>>>>>> of Archetype built to support Maven 2.2.x. > >>>>>>>>> > >>>>>>>>> We solved some issues: > >>>>>>>>> > >>>>>>>>> Release Notes - Maven Archetype - Version 2.3 > >>>>>>>>> > >>>>>>>>> > >>>>>>>>> ** Bug > >>>>>>>>> > >>>>>>>>> * [ARCHETYPE-345] - archetype:create-from-project do not > >>>>>>>>> process > >>>>>>>>> > >>>>>>>>> <jarModule> and <ejbModule> sections into EAR's pom.xml > >>>>>>>>> > >>>>>>>>> * [ARCHETYPE-397] - Required property default value is > >>>>>>>>> not > >>>>>>>>> > >>>>>>>>> displayed correctly if a Velocity expression > >>>>>>>>> > >>>>>>>>> * [ARCHETYPE-413] - on linux adding <parent> element to > >>>>>>>>> generate > >>>>>>>>> > >>>>>>>>> pom.xml changes line endings to /r/n > >>>>>>>>> > >>>>>>>>> * [ARCHETYPE-429] - JIRA report in site only shows fixes > >>>>>>>>> up > >>>>>>>>> to > >>>>>>>>> > >>>>>>>>> v2.1 of plugin > >>>>>>>>> > >>>>>>>>> * [ARCHETYPE-435] - Bad link to old docs in usage page > >>>>>>>>> > >>>>>>>>> ** Improvement > >>>>>>>>> > >>>>>>>>> * [ARCHETYPE-182] - Adding 'role-hint' for the default > >>>>>>>>> > >>>>>>>>> Selector/Configurer/Queryer implementations > >>>>>>>>> > >>>>>>>>> * [ARCHETYPE-401] - use repo.maven.apache.org CNAME to > >>>>>>>>> provide > >>>>>>>>> > >>>>>>>>> more stability > >>>>>>>>> > >>>>>>>>> * [ARCHETYPE-418] - use plugin annotations > >>>>>>>>> * [ARCHETYPE-428] - Improve Generate project in batch > >>>>>>>>> mode > >>>>>>>>> doc > >>>>>>>>> page > >>>>>>>>> * [ARCHETYPE-465] - Upgrade to maven-parent version 26 > >>>>>>>>> * [ARCHETYPE-466] - Upgrade maven-invoker 2.0.11 to 2.1.1 > >>>>>>>>> * [ARCHETYPE-467] - Removed unused maven-war-plugin > >>>>>>>>> dependency. > >>>>>>>>> * [ARCHETYPE-468] - Upgrade maven-plugin-testing-harness > >>>>>>>>> to > >>>>>>>>> 1.3 > >>>>>>>>> > >>>>>>>>> ** Task > >>>>>>>>> > >>>>>>>>> * [ARCHETYPE-431] - Only include Apache Maven archetypes > >>>>>>>>> in > >>>>>>>>> > >>>>>>>>> internal archetype catalog > >>>>>>>>> > >>>>>>>>> * [ARCHETYPE-432] - Update distributionManagement in POM > >>>>>>>>> * [ARCHETYPE-471] - Make a final Maven 2.2.1 release > >>>>>>>>> > >>>>>>>>> ** Wish > >>>>>>>>> > >>>>>>>>> * [ARCHETYPE-464] - Upgrade Plugin Required Maven Version > >>>>>>>>> to > >>>>>>>>> 2.2.1 > >>>>>>>>> > >>>>>>>>> There are still a couple of issues left in JIRA: > >>>>>>>>> > >>>>>>>>> http://jira.codehaus.org/browse/ARCHETYPE-460?jql=project%20%3D%20 > >>>>>>>>> AR > >>>>>>>>> CH > >>>>>>>>> ET > >>>>>>>>> YPE%20AND%20resolution%20%3D%20Unresolved%20AND%20status%20%3D%20O > >>>>>>>>> pe > >>>>>>>>> n% > >>>>>>>>> 20 > >>>>>>>>> ORDER%20BY%20priority%20DESC%2C%20key%20DESC > >>>>>>>>> > >>>>>>>>> Staging repo: > >>>>>>>>> > >>>>>>>>> https://repository.apache.org/content/repositories/maven-1146/cont > >>>>>>>>> en > >>>>>>>>> t/ > >>>>>>>>> or > >>>>>>>>> g/apache/maven/archetype/maven-archetype/2.3/maven-archetype-2.3-s > >>>>>>>>> ou > >>>>>>>>> rc > >>>>>>>>> e- > >>>>>>>>> release.zip>> > >>>>>>>> > >>>>>>>> https://repository.apache.org/content/repositories/maven-1146/org/a > >>>>>>>> pa > >>>>>>>> ch > >>>>>>>> e/ > >>>>>>>> maven/archetype/maven-archetype/2.3/maven-archetype-2.3-source-rele > >>>>>>>> as > >>>>>>>> e. > >>>>>>>> zi > >>>>>>>> p>> > >>>>>>>> > >>>>>>>>> https://repository.apache.org/content/repositories/maven-1146/cont > >>>>>>>>> en > >>>>>>>>> t/ > >>>>>>>>> or > >>>>>>>>> g/apache/maven/archetype/maven-archetype/2.3/maven-archetype-2.3-s > >>>>>>>>> ou > >>>>>>>>> rc > >>>>>>>>> e- > >>>>>>>>> release.zip > >>>>>>>>> > >>>>>>>>> Source release checksum(s): > >>>>>>>>> [NAME-OF]-source-release.zip sha1: > >>>>>>>>> 842a4a5a9aa478883e6bef0c195bf0f943b440a5 > >>>>>>>>> > >>>>>>>>> Staging site: > >>>>>>>>> http://maven.apache.org/archetype-archives/archetype-LATEST > >>>>>>>>> > >>>>>>>>> Guide to testing staged releases: > >>>>>>>>> http://maven.apache.org/guides/development/guide-testing-releases. > >>>>>>>>> ht > >>>>>>>>> ml > >>>>>>>>> > >>>>>>>>> Vote open for 72 hours. > >>>>>>>>> > >>>>>>>>> [ ] +1 > >>>>>>>>> [ ] +0 > >>>>>>>>> [ ] -1 > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
