I've been "playing" with JetSpeed for a couple of years (1.4 -> 1.5 -
> J2) to use as a personal portal. Unfortunately, I'm no longer a
developer professionally; I use my free time to try to stay somewhat
current with Java and Apache open source projects.
There have been a few comments on this thread that I heartily agree
with:
-Maven makes the learning curve for new people much steeper, because
the Maven documentation is hopelessly inadequate. I want to spend my
precious time learning more about JetSpeed and nothing at all about a
build/project management environment (I learned Ant in about 2 hours
and liked it a lot, until I wanted my first if-then-else..). I
strongly believe the Jetspeed community would be served by reducing
the learning curve for new folks.
- Simple Eclipse integration should be a high priority.
I'd vote Ant, but given the amount of time I can invest in the
Jetspeed community, I'd count that as a +0.01
-Eric
On Feb 23, 2006, at 10:18 AM, Scott T Weaver wrote:
Why should a developer be forced to set a remote repo up to placate
Maven?
The company I work for manages remote dependencies via an Anthill
build
server, whose format does not match up with Maven's strict repo
format. So
I had to duplicate and manually synch a local Maven repo with the
build
server. Maven is quite a bit more than a build program; it is
truly a build
infrastructure. Honestly, this works well when everyone in your
development
team is on board with it and understands. However, enforcing this
infrastructure to simply build an application is too much to shackle a
developer with.
-Scott
-----Original Message-----
From: Ralph Goers [mailto:[EMAIL PROTECTED]
Sent: Thursday, February 23, 2006 10:02 AM
To: Jetspeed Users List
Subject: Re: RFC: J2 Build System
Church Michael R wrote:
Maven requires a network connection the first time you build,
whether or
not
you are building from source. Try building and deploying the
"simplest
portlet" example after initial binary installation, when you have no
internet connection, and see what happens....
Mike Church
Software Engineering
This is completely untrue. It is not maven that is requiring
this. It
is your configuration.
Create a build.properties file in your home directory and then put a
definition for "maven.repo.remote" in it that points to a local maven
repository somewhere on your internal network or on your local
machine.
Ralph
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: jetspeed-user-
[EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
