of a pain than it's worth. For me, it's just easier to code the stuff. You
> I've really enjoyed getting to use Maven on my recent projects. I'm no
> Maven expert, but I'm finding that I don't have to be -- it really
> just does a great job. Getting Maven working with JDeveloper has not
> been going well so far, so that's been one hangup.
>
> There are a few reasons for the department-wide IDE mandate. Our
> manager has just discovered UML (I don't know anything about it, to be
> honest), and JDeveloper provides UML functionality out of the box,
> while any of the free Eclipse UML plugins I could find required a
> mountain of dependencies and don't appear to work as smoothly as the
> JDev one. Also, we're trying to replace TOAD as our database tool, and
> JDev looks like it can do that. The third reason is that most of our
> applications are Oracle ApEx, and JDev has stuff for that too.
>
> I'm trying to port my existing apps to JDeveloper, but without much
> success. The main problems so far are:
> - How do I import a Wicket project using the Maven standard directory
> layout? (I am aware of the Maven JDev plugin for JDev 10, but it has
> issues with JDev 11)
> - How do I run a Wicket app in JDeveloper using the internal WebLogic
> server?
> - Does JDeveloper have some sort of Maven-like functionality for
> project lifecycle management?
>
> I imagine (hope) that most of these questions have easy answers, but
> I'm just not finding a lot of relevant online
> documentation/discussion. Most of the JDeveloper web app documentation
> is focused on EJBs or basic Servlet/JSP-based apps.
>
>
> On Fri, Jun 19, 2009 at 3:53 AM, James
> Carman<
jcarman@...> wrote:
> > +1 on using Maven. Most folks at our job site use eclipse, but I'm an
> > IntelliJ junkie (they got me hooked many years ago and I can't break
> > free). For the most part, we don't have issues between environments,
> > provided folks have their plugins set up correctly.
> >
> > On Fri, Jun 19, 2009 at 6:39 AM, Martijn Reuvers
> > <
martijn.reuvers@...> wrote:
> >>
> >> When you use ADF, then stick to JDeveloper you'll get a lot of
> >> integration for your application and can really build applications
> >> fast.
> >>
> >> However if you use open-source frameworks like wicket, you're better
> >> off using one of the other IDE's (Netbeans, Eclipse, IntelliJ). Just
> >> use maven or so, then your management has nothing to say, as it does
> >> not really matter what IDE you use. I always say: Use whatever gets
> >> the job done. =)
> >>
> >> On Fri, Jun 19, 2009 at 1:00 AM, Dane Laverty<
danelaverty@...>
> wrote:
> >> > Our management has chosen to make JDeveloper 11g the required IDE for
> >> > the department. Searching the Wicket mailing list archives, I find
> >> > that there is very little discussion about JDev. I'd be interested to
> >> > know, are any of you currently using JDeveloper as your main Wicket
> >> > IDE?
> >> >
> >> > ---------------------------------------------------------------------
> >> > To unsubscribe, e-mail:
users-unsubscribe@...
> >> > For additional commands, e-mail:
users-help@...
> >> >
> >> >
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail:
users-unsubscribe@...
> >> For additional commands, e-mail:
users-help@...
> >>
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail:
users-unsubscribe@...
> > For additional commands, e-mail:
users-help@...
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
users-unsubscribe@...
> For additional commands, e-mail:
users-help@...
>
>