On Mar 25, 2009, at 2:01 AM, Emmanuel Lecharny wrote:
Where did the Ant build files go? Where are the IntelliJ files?
(I know nothing but) I thought the idea was to move to Maven. IDE
project
files for IntelliJ, Eclipse etc. can be generated via Maven. You
can use
"mvn idea:idea" to generate the project files for IDEA (
http://maven.apache.org/plugins/maven-idea-plugin/), but I think
the newest
version has a pretty good support for Maven built-in.
There was tremendous push back on getting rid of the IDEA files
that were checked in and, so, we need to collect a community
consensus before we remove them; don't get me wrong I want to get
rid of them and I think, like you, that they are superfluous.
Well, I won't be that cautious in this case. We all know that Maven
can generate those files, so there is ne need to keep them around.
As I mentioned above we all understood that the IDEA files were
superfluous and yet other developers insisted that they be kept
around. There's no difference between me just moving forward and
deleting them myself earlier this year and Les doing it now; if the
former were done there would have been a riot. The point is that it
is a very well know point of contention and it should have been
resolved before any action is done. One can't just blow past a
community problem just because *one* of the members changed his mind.
Regarding the ant files, the best would have been to get a bit more
formal approval at some point (well, a vote), but again, I don't see
that as an big mistake to have done the switch from ant to maven as
we already lengthly discussed this matter last year.
Discussion, yes. Consensus, no.
Look, I would love to just keep my mouth shut, especially since things
are going my way, but this is the Incubator and I think we're all
overlooking that there are community issues that are being overlooked
for the sake of expediency, i.e. code is being held as the priority
over community. This isn't the ASF way.
Basically, my personal opinion is that, yes, it's a good practice to
ask the list for such moves before doing so. That's help new comers
to feel like they are part of the community. It gives them the
feeling we are a community, not a bunch of developper deciding to
change some code because you need it or think it's good for the
project. I think that's the message Alan want to transmit here.
If you don't have time (for instance because you need a quick
version to be cut), then it's probably better to do it in a branch.
Then when the community has catched up and agreed with your points,
then the branch can be merged into the trunk.
The above comments are spot on for general development. Thanks
Emmanuel.
Anyway, the Maven move was a good move.
Agreed!
Regards,
Alan
