Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [m2e-dev] [m2e-users] kepler m1 candidate build (aka juno sr1 release candidate) 
There were couple of changes in this area in 1.2 and I guess one of them
introduced this regression. I don't use import from scm functionality
myself, but if somebody provides a quality patch and corresponding
regression test(s) in next few days, I will consider it for 1.2.

https://bugs.eclipse.org/bugs/show_bug.cgi?id=384510
https://bugs.eclipse.org/bugs/show_bug.cgi?id=387252

--
Regards,
Igor


On 12-08-31 6:58 AM, Anders Hammar wrote:

Using staged version 1.2.0.20120828-2132, I see a weird behavior when
checking out a multi-module project from svn as Maven projects. The
name of the aggregator project ends up as "Maven.1346blabla". But the
artifactId is "maven-release". Never seen this before for multi-module
projects.

This is a Juno instance (although upgraded from Indigo so it's not
from a fresh package). Kan anyone reproduce?
Try the maven-release trunk:
https://svn.apache.org/repos/asf/maven/release/trunk

Not sure it matters, but here's the scm connector I have installed:
   Maven SCM Handler for
Subversive	0.13.0.201208191312	org.sonatype.m2e.subversive.feature.feature.group	Sonatype,
Inc.

/Anders

On Wed, Aug 22, 2012 at 5:28 PM, Igor Fedorenko <igor@xxxxxxxxxxxxxx> wrote:

done. new build is 1.2.0.20120822-1446.

--
Regards,
Igor


On 12-08-22 9:49 AM, Fred Bricon wrote:


Igor,

any chance you could do a last respin (I promise) to get the fix for my
screw-up : https://bugs.eclipse.org/bugs/show_bug.cgi?id=387784
Beer will be paid ;-)

Regards,

Fred Bricon

On Tue, Aug 21, 2012 at 3:39 PM, Igor Fedorenko <igor@xxxxxxxxxxxxxx
<mailto:igor@xxxxxxxxxxxxxx>> wrote:

     Ok, the new candidate build is 1.2.0.20120821-1306

     --
     Regards,
     Igor


     On 12-08-21 8:21 AM, Fred Bricon wrote:

         Igor,

         The initial fix for
         https://bugs.eclipse.org/bugs/__show_bug.cgi?id=387521

         <https://bugs.eclipse.org/bugs/show_bug.cgi?id=387521> turned out
to
         severely break archetypes with required properties.
         Can you please restage a RC candidate so that it includes the
         proper fix
         :

http://git.eclipse.org/c/m2e/__m2e-core.git/commit/?id=__ae69d184a22952e74a08c3f7fecd79__6cd019046b


<http://git.eclipse.org/c/m2e/m2e-core.git/commit/?id=ae69d184a22952e74a08c3f7fecd796cd019046b>


         Thx,

         Fred Bricon

         On Tue, Aug 21, 2012 at 1:52 PM, Igor Fedorenko
         <igor@xxxxxxxxxxxxxx <mailto:igor@xxxxxxxxxxxxxx>
         <mailto:igor@xxxxxxxxxxxxxx <mailto:igor@xxxxxxxxxxxxxx>>> wrote:

              Friendly reminder, kepler m1 is this coming Friday. If you
         don't test
              and don't report problems you find, currently staged
         candidate build
              1.2.0.20120819-2129 will become m2e 1.2 release.

              --
              Regards,
              Igor


              On 12-08-17 11:10 PM, Igor Fedorenko wrote:

                  I've just uploaded m2e 1.2.0.20120818-0226 to [1]. This
         is out
                  current
                  kepler m1 candidate build. You can see full list of
         fixes in
                  this build
                  in [2], but the big change is of course workspace-level
         lifecycle
                  mapping configuration. Kudos to Andrew Eisenberg from
         VMWare for
                  driving
                  this work to completion.

                  There appears to be a recent regression in archetyper
         support
                  tracked as
                  bug 387521, so we may have another build early next
         week, but
                  unless new
                  regressions are found, I do not expect any other
         changes before
                  final
                  kepler m1 build is declared. We also plan to contribute
         the same
                  build
                  to juno sr1, so it will likely be our official m2e 1.2
         release
                  (I guess
                  I need to start doing the paperwork already).

                  Please test m2e 1.2 and provide feedback either here or
         in m2e
                  bugzilla.

                  [1]
         http://download.eclipse.org/____technology/m2e/milestones/1.2
         <http://download.eclipse.org/__technology/m2e/milestones/1.2>


         <http://download.eclipse.org/__technology/m2e/milestones/1.2
         <http://download.eclipse.org/technology/m2e/milestones/1.2>>
                  [2]

https://bugs.eclipse.org/bugs/____buglist.cgi?list_id=2652291&____query_format=advanced&__product=__m2e&target___milestone=Kepler%__20M1

<https://bugs.eclipse.org/bugs/__buglist.cgi?list_id=2652291&__query_format=advanced&product=__m2e&target_milestone=Kepler%__20M1>



<https://bugs.eclipse.org/__bugs/buglist.cgi?list_id=__2652291&query_format=advanced&__product=m2e&target_milestone=__Kepler%20M1


<https://bugs.eclipse.org/bugs/buglist.cgi?list_id=2652291&query_format=advanced&product=m2e&target_milestone=Kepler%20M1>>


                  --
                  Regards,
                  Igor
                  ___________________________________________________

                  m2e-dev mailing list
         m2e-dev@xxxxxxxxxxx <mailto:m2e-dev@xxxxxxxxxxx>
         <mailto:m2e-dev@xxxxxxxxxxx <mailto:m2e-dev@xxxxxxxxxxx>>
         https://dev.eclipse.org/____mailman/listinfo/m2e-dev
         <https://dev.eclipse.org/__mailman/listinfo/m2e-dev>
                  <https://dev.eclipse.org/__mailman/listinfo/m2e-dev
         <https://dev.eclipse.org/mailman/listinfo/m2e-dev>>

              ___________________________________________________

              m2e-users mailing list
         m2e-users@xxxxxxxxxxx <mailto:m2e-users@xxxxxxxxxxx>
         <mailto:m2e-users@xxxxxxxxxxx <mailto:m2e-users@xxxxxxxxxxx>>
         https://dev.eclipse.org/____mailman/listinfo/m2e-users
         <https://dev.eclipse.org/__mailman/listinfo/m2e-users>


              <https://dev.eclipse.org/__mailman/listinfo/m2e-users
         <https://dev.eclipse.org/mailman/listinfo/m2e-users>>




         --
         "Have you tried turning it off and on again" - The IT Crowd


         _________________________________________________
         m2e-dev mailing list
         m2e-dev@xxxxxxxxxxx <mailto:m2e-dev@xxxxxxxxxxx>
         https://dev.eclipse.org/__mailman/listinfo/m2e-dev
         <https://dev.eclipse.org/mailman/listinfo/m2e-dev>

     _________________________________________________
     m2e-dev mailing list
     m2e-dev@xxxxxxxxxxx <mailto:m2e-dev@xxxxxxxxxxx>
     https://dev.eclipse.org/__mailman/listinfo/m2e-dev
     <https://dev.eclipse.org/mailman/listinfo/m2e-dev>




--
"Have you tried turning it off and on again" - The IT Crowd


_______________________________________________
m2e-dev mailing list
m2e-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/m2e-dev


_______________________________________________
m2e-dev mailing list
m2e-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/m2e-dev

_______________________________________________
m2e-dev mailing list
m2e-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/m2e-dev

Back to the top