WTP and m2eclipse -- when will it be mature enough for using it
|
View:
New views
4 Messages
—
Rating Filter:
Alert me
|
 |
WTP and m2eclipse -- when will it be mature enough for using it
by ulrike adrion
::
Rate this Message:
I have posted a m2eclipse issue (see https://issues.sonatype.org/browse/MNGECLIPSE-714) in spring 2008.
All our applications uses eclipse WTP and especially that bug prevents us for enrolling the plugin for our company. Now I'm a little bit frustrated because I saw that this issue isn't assigned to anyone and I fear that this error will be never fixed ... What are the reasons that this issue is treated with so low priority? In general we are very satisfied with the functionality of m2eclipse and we are very interested in using it. Could anyone tell us where to find more details about the WTP - m2eclipse integration. Perhaps it would be possible that we will fix that issue? Best regards, Ulrike |
|
|
Re: WTP and m2eclipse -- when will it be mature enough for using it
by jvanzyl
::
Rate this Message:
On 2009-09-28, at 3:51 AM, ulrike adrion wrote:
> > I have posted a m2eclipse issue (see > https://issues.sonatype.org/browse/MNGECLIPSE-714) in spring 2008. > > All our applications uses eclipse WTP and especially that bug > prevents us > for enrolling the plugin for our company. Now I'm a little bit > frustrated > because I saw that this issue isn't assigned to anyone and I fear > that this > error will be never fixed ... > What are the reasons that this issue is treated with so low priority? > Because issues in WTP are so expensive and costly to fix. WTP is not very easy to integrate with although this is getting easier with later releases. Fixing WTP/M2Eclipse issues could easily consume all our resources. We just can't afford to do that. The JBoss folks are interested in WTP/M2Eclipse integration so we hope that they help with this integration. The general Maven interoperability is more important for us for the 1.0, so WTP is likely to be marked as alpha quality and after the 1.0 we will look at the issues again. It really is just an enormous amount of work and WTP just isn't the easiest thing to work with. > In general we are very satisfied with the functionality of m2eclipse > and we > are very interested in using it. > > Could anyone tell us where to find more details about the WTP - > m2eclipse > integration. Perhaps it would be possible that we will fix that issue? > Source code is probably the best place to look. We always looking for comprehensive use cases and tests (including UI tests) and that's really what's going to help us get mature support for WTP. If we could get 1.0 production quality WTP support that would be fantastic. We can discuss how much time you and your team have to contribute and we'll see if we can change the scheduling. If by "we" you actually mean us then it's unlikely it will be fixed. If by "we" you actually mean your group then anything is possible :-) > Best regards, Ulrike > > -- > View this message in context: http://www.nabble.com/WTP-and-m2eclipse----when-will-it-be-mature-enough-for-using-it-tp25643728p25643728.html > Sent from the Maven Eclipse - User mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > Thanks, Jason ---------------------------------------------------------- Jason van Zyl Founder, Apache Maven http://twitter.com/jvanzyl ---------------------------------------------------------- --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email |
|
|
Re: WTP and m2eclipse -- when will it be mature enough for using it
by Snjezana Peco
::
Rate this Message:
I haven't faced this problem. I have also tried to reproduce the problem
described in https://issues.sonatype.org/browse/MNGECLIPSE-714 and http://jira.codehaus.org/browse/MNGECLIPSE-950, but haven't succeeded. Deploying works correctly when using Galileo 3.5.0/WTP 3.1 and m2eclipse trunk. Snjeza Jason van Zyl wrote: > On 2009-09-28, at 3:51 AM, ulrike adrion wrote: > >> >> I have posted a m2eclipse issue (see >> https://issues.sonatype.org/browse/MNGECLIPSE-714) in spring 2008. >> >> All our applications uses eclipse WTP and especially that bug >> prevents us >> for enrolling the plugin for our company. Now I'm a little bit >> frustrated >> because I saw that this issue isn't assigned to anyone and I fear >> that this >> error will be never fixed ... >> What are the reasons that this issue is treated with so low priority? >> > > Because issues in WTP are so expensive and costly to fix. WTP is not > very easy to integrate with although this is getting easier with later > releases. Fixing WTP/M2Eclipse issues could easily consume all our > resources. We just can't afford to do that. The JBoss folks are > interested in WTP/M2Eclipse integration so we hope that they help with > this integration. > > The general Maven interoperability is more important for us for the > 1.0, so WTP is likely to be marked as alpha quality and after the 1.0 > we will look at the issues again. It really is just an enormous amount > of work and WTP just isn't the easiest thing to work with. > >> In general we are very satisfied with the functionality of m2eclipse >> and we >> are very interested in using it. >> >> Could anyone tell us where to find more details about the WTP - >> m2eclipse >> integration. Perhaps it would be possible that we will fix that issue? >> > > Source code is probably the best place to look. We always looking for > comprehensive use cases and tests (including UI tests) and that's > really what's going to help us get mature support for WTP. If we could > get 1.0 production quality WTP support that would be fantastic. We can > discuss how much time you and your team have to contribute and we'll > see if we can change the scheduling. If by "we" you actually mean us > then it's unlikely it will be fixed. If by "we" you actually mean your > group then anything is possible :-) > >> Best regards, Ulrike >> >> -- >> View this message in context: >> http://www.nabble.com/WTP-and-m2eclipse----when-will-it-be-mature-enough-for-using-it-tp25643728p25643728.html >> >> Sent from the Maven Eclipse - User mailing list archive at Nabble.com. >> >> >> --------------------------------------------------------------------- >> To unsubscribe from this list, please visit: >> >> http://xircles.codehaus.org/manage_email >> >> > > Thanks, > > Jason > > ---------------------------------------------------------- > Jason van Zyl > Founder, Apache Maven > http://twitter.com/jvanzyl > ---------------------------------------------------------- > > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email |
|
|
Re: WTP and m2eclipse -- when will it be mature enough for using it
by Fred Bricon
::
Rate this Message:
As I explained today in MNGECLIPSE-714, the bug occurs when the user configures the Maven Library to be deployed from Jar/Ejb projects.It's like crossing the streams, please don't do it. Simply deselect it under Java EE Module Dependencies and it should work.
The fix for MNGECLIPSE-855 is on its way. regards, Fred Bricon On Tue, Sep 29, 2009 at 12:27 AM, Snjezana Peco <snjezana.peco@...> wrote: I haven't faced this problem. I have also tried to reproduce the problem described in https://issues.sonatype.org/browse/MNGECLIPSE-714 and http://jira.codehaus.org/browse/MNGECLIPSE-950, but haven't succeeded. Deploying works correctly when using Galileo 3.5.0/WTP 3.1 and m2eclipse trunk. |
| Free embeddable forum powered by Nabble | Forum Help |
