See below:
[EMAIL PROTECTED] wrote:
>
> I think this is a bit premature. Here are my reasons:
> 1. We need to make sure the 1.1 branch builds with maven 2.0 final
> release. It doesn't work for me. BTW, the m2 maven 2.0 driver is now
> deprecated. The README file needs to change to reflect this fact.
>
> Would you please let us know your issues building so we can help
> work through them and resolve any issues we may have.
>
I supply a password multiple times after this prompt:
The authenticity of host 'cvs.apache.org' can't be established.
DSA key fingerprint is . . . . .
Are you sure you want to continue connecting? (yes/no):
And then the build fails with the message:
[INFO] Error building POM (may not be this project's POM).
Project ID: javax.servlet:servlet-api
Reason: Error getting POM for 'javax.servlet:servlet-api' from the
repository: A
uthentication failed: Cannot connect. Reason: Auth fail
javax.servlet:servlet-api:2.3:pom
from the specified remote repositories:
central (http://repo1.maven.org/maven2),
m1 (scp://cvs.apache.org/repository),
m2 (scp://people.apache.org/home/ddewolf/public_html/m2)
I have also tried to build pluto 1.1 on another machine and get stuck in
a 'Are you sure you want to continue connecting?' loop.
This is a result of a bad distribution server definition. For some
reason I thought Zehng had check in the fix. I'll check it in later on
today.
> I have updated the m2 references to mvn.
>
> 2. We need more 1.1 xdocs. The docs I put together on building 1.1 needs
> to be expanded and be more explicit.There is no documentation on how to
> integrate the 1.1 portlet container into a portal. It would also be a
> good idea to have some documentation on 1.1 architecture.
>
> Is this something you're willing to work on? My experience is that
> the docs will get flushed out as things stabalize and new users get
> involved. I'd hate to put the onus on the few of us that are
> actively developing 1.1 to create comprehensive documentation. If
> this is a requirement we will never get 1.1 moving.
>
I would be very happy to document the build and install process once I
have it figured out. This needs to be in place at a minimum. It will be
a disservice to recruiting 1.1 developers if we don't have clear
instructions on how to build the 1.1 distribution.
Sweet. There is a set of instructions to start from in
<svn>/pluto-site/src/site/apt
Apt files now get built as part of the website build. I'm *pretty sure*
that these are acurate, but if not, I can help you plug through some
more solid docs.
I can also help document the portal integration process for pluto 1.1,
but I'll need some help.
Yup, that's something that's definately on my plate and can use help
with (always good to have someone that has't gotten started with it
involved). I just don't think this is a requirement right off the bat
for moving to the main dev trunk.
At any rate, we should be prepared to modify the web site when we switch
to a 1.1 trunk to make it clear that the current Installation Guide,
User Guide and Development Guide refer to the 1.0.1 branch. Again, I'll
help to do this.
Really? I disagree with this. I'd like to keep the 1.0.1 site up until
we're a little further along.
>
> 3. All major functionality of the portlet container should work
> including cross-context session dispatching like Zheng has pointed out.
>
>
> Really? It seems like the only way this will happen is if we begin
> to make more steady progress. To me, steady progress happens by
> elevating 1.1 to trunk - which represents the "primary" development
repo.
>
> Perhaps we have different philosophies on what the trunk is. To me
> it is the primary development source code. It does not reflect the
> stability of the code - that's what releases do.
>
You do have a point here. I just want to make sure that it is clear in
the documentation or Jira what currently works or what doesn't. I will
help to document this when I get 1.1 working on my machine.
Thanks,
David
