« Return to Thread: problems after update netbeans maven plugin to 3.1.4
Re: problems after update netbeans maven plugin to 3.1.4
by Cyrill Rüttimann-2
::
Rate this Message:
Hello,
This topic (Companies depending on OpenSource Software) is a really
interesting one!
We are using for example JasperReports and JFreeChart. We always have
to make clear to the customer what is means to have free beer software
as a dependency. No one is responsible to fix a certain bug in this
type of software and thus we can not commit to have a certain
functionality the customer wants to have implemented by the requested
date. Enhance or fix an open source library/programm means:
- someone from the dev team has to pick up the bug report or feature
request dependend of the time they can spend and the importance of the
bug/feature request
- Do it yourself and hope one of the developers will pick up the patch
- Spend some money to have it fixed immediately (JasperReport model)
In my eyes it is not a good idea to stop fixing the 3.1.x branch for
Netbeans 6.1 before the next version is out the doors, but we have to
respect the decision of the maintainers. They have for sure a good
reason to do so!
I have written myself a maven plugin (original author of the findbugs
plugin) and I was surprised how many email you receive with feature
requests. Your whole life apart from the daily job gets filled up if
you like to make everyone happy.
Regards,
Cyrill
On 28.08.2008, at 05:02, Dietrich wrote:
>
>
>
> Milos Kleint wrote:
>>
>> Unfortunately I don't plan any more updates for 6.1, the 3.1.4 is the
>> final release for 6.1 as far as I'm concerned (currently).
>>
>>
>
> Are you aware of the costs and the effects on an organization which
> uses
> mevenide in their projects - developers innocently upgrade their
> netbeans,
> their build stops working and nobody is there to help them until
> someone
> finds this post? This certainly gives everybody the impression that
> there is
> no strong commitment to the "stable" mevenide build system. Please
> reconsider your decision not to fix this.
> Or at least, please consider revoking the 3.1.4 update on
> plugins.netbeans.org if you are not going to fix this.
>
> --
> View this message in context: http://www.nabble.com/problems-after-update-netbeans-maven-plugin-to-3.1.4-tp18864420p19193461.html
> Sent from the mevenide - user mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> 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
This topic (Companies depending on OpenSource Software) is a really
interesting one!
We are using for example JasperReports and JFreeChart. We always have
to make clear to the customer what is means to have free beer software
as a dependency. No one is responsible to fix a certain bug in this
type of software and thus we can not commit to have a certain
functionality the customer wants to have implemented by the requested
date. Enhance or fix an open source library/programm means:
- someone from the dev team has to pick up the bug report or feature
request dependend of the time they can spend and the importance of the
bug/feature request
- Do it yourself and hope one of the developers will pick up the patch
- Spend some money to have it fixed immediately (JasperReport model)
In my eyes it is not a good idea to stop fixing the 3.1.x branch for
Netbeans 6.1 before the next version is out the doors, but we have to
respect the decision of the maintainers. They have for sure a good
reason to do so!
I have written myself a maven plugin (original author of the findbugs
plugin) and I was surprised how many email you receive with feature
requests. Your whole life apart from the daily job gets filled up if
you like to make everyone happy.
Regards,
Cyrill
On 28.08.2008, at 05:02, Dietrich wrote:
>
>
>
> Milos Kleint wrote:
>>
>> Unfortunately I don't plan any more updates for 6.1, the 3.1.4 is the
>> final release for 6.1 as far as I'm concerned (currently).
>>
>>
>
> Are you aware of the costs and the effects on an organization which
> uses
> mevenide in their projects - developers innocently upgrade their
> netbeans,
> their build stops working and nobody is there to help them until
> someone
> finds this post? This certainly gives everybody the impression that
> there is
> no strong commitment to the "stable" mevenide build system. Please
> reconsider your decision not to fix this.
> Or at least, please consider revoking the 3.1.4 update on
> plugins.netbeans.org if you are not going to fix this.
>
> --
> View this message in context: http://www.nabble.com/problems-after-update-netbeans-maven-plugin-to-3.1.4-tp18864420p19193461.html
> Sent from the mevenide - user mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> 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
« Return to Thread: problems after update netbeans maven plugin to 3.1.4
| Free embeddable forum powered by Nabble | Forum Help |
