Actually, this only affect building archetypes, so there is no need for a
note. This is an internal Weld issue (which is now resolved).
-Dan
On Wed, Dec 9, 2009 at 12:27 AM, Dan Allen <dan.j.allen(a)gmail.com> wrote:
Finally got around to fixing this.
https://jira.jboss.org/jira/browse/WELD-336
The archetypes will have to wait on a release of Weld to loosen this
requirement, so we should just add a note to the archetype tutorial that the
restriction will be gone in the future.
-Dan
On Thu, Nov 26, 2009 at 6:51 AM, Pete Muir <pmuir(a)redhat.com> wrote:
> Good point :-)
>
> Can you fix that?
>
> On 26 Nov 2009, at 02:14, Steven Boscarine wrote:
>
> >
> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed
> > Content-Transfer-Encoding: 7bit
> >
> > Hello Pete,
> > I saw the max maven version constraint was added to the new parent POM.
> > Can we make it a min version only constraint like it used to be?
> >
> > I think it'll be more convenient for causal contributers if they don't
> > have to maintain a legacy maven version just to build our project.
> >
> > Thanks,
> > Steven
> > _______________________________________________
> > weld-dev mailing list
> > weld-dev(a)lists.jboss.org
> >
https://lists.jboss.org/mailman/listinfo/weld-dev
>
> _______________________________________________
> weld-dev mailing list
> weld-dev(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/weld-dev
>
--
Dan Allen
Senior Software Engineer, Red Hat | Author of Seam in Action
Registered Linux User #231597
http://mojavelinux.com
http://mojavelinux.com/seaminaction
http://www.google.com/profiles/dan.j.allen
--
Dan Allen
Senior Software Engineer, Red Hat | Author of Seam in Action
Registered Linux User #231597
http://mojavelinux.com
http://mojavelinux.com/seaminaction
http://www.google.com/profiles/dan.j.allen