I'm now using build #7675 ... it's not quite as stable as 7.0.2
however. I also had to re-import my projects that used Maven. Other
than that (and a few keystrokes changing their meaning) I haven't be
able to see a real difference.
On Jan 31, 2008 10:57 AM, Michael Lake <[EMAIL PROTECTED]> wrote
On Jan 31, 2008 8:42 PM, Michael Lake <[EMAIL PROTECTED]> wrote:
>
> The plugins appear to be from different teams. Perhaps Sun is lining
> someone's pockets better than JetBrains? :)
AFAIK, that's not the case! NB's plugin is just a 'spare-time'
project, and it's
amazing that it works so well...
oh wow, you're right, there are fixes!
thanks for setting the record straight!
-mike
On Jan 31, 2008, at 1:45 PM, Jesse Kuhnert wrote:
I've been using all of the 7.0.3 eap releases and can confirm that
they have actually been fixing the bugs - even if they don't close
them in JIRA. Every r
We should probably take this all offline, or to the maven users lists,
as this isn't really directly relevant to T{3..5}.
Christian
On 31-Jan-08, at 13:42 , Michael Lake wrote:
For those of you IDEA users, i did a little roundup of information
regarding maven2 integration:
I was thinkin
I've been using all of the 7.0.3 eap releases and can confirm that
they have actually been fixing the bugs - even if they don't close
them in JIRA. Every release since the first introduction of it has
had a bug fixed that I've noticed.
On Thu, Jan 31, 2008 at 1:42 PM, Michael Lake <[EMAIL PROTEC
For those of you IDEA users, i did a little roundup of information
regarding maven2 integration:
I was thinking of trying out IDEA's EAP release of 7.0.3 found here:
http://www.jetbrains.net/confluence/display/IDEADEV/Selena+EAP
But then I dug into the Jetbrains' JIRA for maven integration:
Heh. I've been following the maven dev list, and some of the re-
thinking done for 2.1 seems to clean things out substantially,
including resolving this whole issue of repeatability and making
things cleaner for stamping a build environment (sets of plugins,
etc.) I'm not saying this to
It's quite possible to use Ant to build, but to generate Maven
artifacts. The dependencies are the good part of Maven, it's just the
build system layered on those dependencies that is atrocious.
On Jan 31, 2008 6:59 AM, Christian Edward Gruber
<[EMAIL PROTECTED]> wrote:
> I'd like to second that,
I'd like to second that, and at the very least, releasing maven
artifacts for those wanting to build T5 apps using M2 is critical.
This can be done regardless of whether T5 itself is using maven, but
it would be critical to easy use in most environments in which I have
worked or foresee wo
