Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [aperi-dev] R0.3 RC1 results so far


Todd,
Neither of these two pre-reqs are listed in the IP Log, http://www.eclipse.org/aperi/project-info/IP-Log.html , so I updated it.  

Can you please check that the information is correct before I submit Contribution Questionnaires for these?  Thanks.

Cheers,   Tom
___________________________________________
Tom Guinane     Aperi Project Lead     IBM     408-284-4795     guinane@xxxxxxxxxx     http://www.eclipse.org/aperi/



Todd Singleton/San Jose/IBM@IBMUS
Sent by: aperi-dev-bounces@xxxxxxxxxxx

05/16/2007 09:10 AM

Please respond to
Aperi Development <aperi-dev@xxxxxxxxxxx>

To
Aperi Development <aperi-dev@xxxxxxxxxxx>
cc
Subject
Re: [aperi-dev] R0.3 RC1 results so far






Brenda,

Sorry for the confusion.  
geronimo-j2ee_1.4_spec-1.1.jar is a replacement for j2ee.jar - a prereq in the .2 version of Aperi.  jh.jar is also a prereq.  So both are prereqs needed for the runtime to function properly.  Both prereqs are currently downloaded manually by the end-user.  Craig has mentioned that the download of geronimo-j2ee_1.4_spec-1.1.jar could actually be automated.  That would leave us with only one file that an end user would have to manually download, dig thru, and place within the aperi directories.  Because jh.jar (Java Help) is distributed by Sun, it seems like the only alternative is to migrate away from that dependency.  I'm not sure of the exact cost of migrating from Java Help to Eclipse Help.  This primarily affects the gui.  

Todd Singleton
Software Engineer, Tivoli, IBM
Menlo Park, CA
email: toddsing@xxxxxxxxxx



Brenda Haynes/Raleigh/IBM@ibmus
Sent by: aperi-dev-bounces@xxxxxxxxxxx

05/16/2007 08:26 AM

Please respond to
Aperi Development <aperi-dev@xxxxxxxxxxx>

To
Aperi Development <aperi-dev@xxxxxxxxxxx>
cc
Subject
Re: [aperi-dev] R0.3 RC1 results so far







Todd, thanks. see my question below. Brenda

Brenda Haynes
Director, Aperi Open Source Project
zStorage SW Product Management
IBM Software Group
bhaynes@xxxxxxxxxx
877-328-8470 T/L (930)-5127

Inactive hide details for Todd Singleton/San Jose/IBM@IBMUSTodd Singleton/San Jose/IBM@IBMUS
Todd Singleton/San Jose/IBM@IBMUS
Sent by: aperi-dev-bounces@xxxxxxxxxxx

05/16/2007 04:05 AM

Please respond to
Aperi Development <aperi-dev@xxxxxxxxxxx>




To

Aperi Development <aperi-dev@xxxxxxxxxxx>


cc


Subject

Re: [aperi-dev] R0.3 RC1 results so far







Brenda,

What is left in regards to IP approvals:

iText 1.3
- new to this release, but can be downloaded automatically thru the installer (blh: ok and I saw a note that cfgaperi can automate this so that is good)
org.mortbay.jaas 5.1.10
- new to this release, but can be downloaded automatically thru the installer (blh: ok also saw note that cfgaperi can automate this so again this helps the install experience)

(blh: Are these two items (geronimo and jh.jar) suggested replacement for the existing prereqs? Not sure i follow why you mentioned these as replacements vs prereqs that need installed?)

geronimo-j2ee_1.4_spec-1.1.jar
- replacement of the old j2ee.jar (still inconvenient to end-user)
jh.jar (Java Help) - the oldest and still the most inconvenient to the end-user; can be replaced by Eclipse Help (significant change)


Todd Singleton
Software Engineer, Tivoli, IBM
Menlo Park, CA
email: toddsing@xxxxxxxxxx

Brenda Haynes/Raleigh/IBM@ibmus
Sent by: aperi-dev-bounces@xxxxxxxxxxx

05/15/2007 06:24 PM

Please respond to
Aperi Development <aperi-dev@xxxxxxxxxxx>


To
Aperi Development <aperi-dev@xxxxxxxxxxx>
cc
Subject
Re: [aperi-dev] R0.3 RC1 results so far









I had a question. Do we need to do something to better document the cfgaperi easy option to help folks do this successfully or know when not to use this route.

My two cents on the Linux install instructions, I think we should provide them..I was thinking Robert got us a base on this for the 0.2 milestone but maybe that was build instructions?

With the recent IP Approvals from Eclipse: can someone give me the run down on what is left in the prereq list that we can not include in our Aperi package and of those prereqs can they all be automated by cfgaperi?
thanks, Brenda

Brenda Haynes
Director, Aperi Open Source Project
zStorage SW Product Management
IBM Software Group
bhaynes@xxxxxxxxxx
877-328-8470 T/L (930)-5127


Inactive hide details for "David Wolfe" <2dwolfe@xxxxxxxxx>"David Wolfe" <2dwolfe@xxxxxxxxx>
"David Wolfe" <2dwolfe@xxxxxxxxx>
Sent by: aperi-dev-bounces@xxxxxxxxxxx

05/15/2007 02:14 PM

Please respond to
Aperi Development <aperi-dev@xxxxxxxxxxx>





To

"Aperi Development" <aperi-dev@xxxxxxxxxxx>



cc



Subject

Re: [aperi-dev] R0.3 RC1 results so far








Chris owns the windows instructions. He should work with me and or Craig to resolve any specific issues (I think the emails have stated the file name changes etc).
The general issue of the complexity of the install is out of scope for V0.3 and will get resolved as we get IP issues solved and can bundle the bits.

We don't have a requirement to provide install instructions for Linux in V0.3 (we haven't provided them before now). I think this should be a high priority fix-it item for an early milestone release of V0.4.

There are only two things that cfgaperi can download: itext and jaas.
Everything else is either bundled or must be downloaded by hand.
I think Todd would be the logical owner of the definitive list of 3rd party SW that still needs to be downloaded. Todd, can you provide that list to Chris?

Is there any reason why the documentation issues can't get turned around today?

I think Craig claimed ownership of the two Linux problems.

There is no defect for the adm group issue. Sounds like an issue that's been around for awhile and the work around is don't use 'easy' mode unless the adm group works for you.
Can we file an enhancement for that and deal with it in the next release?

Sounds like SCSI bug (176657) has a fix already? This one looks like it should go into V0.3 since it causes a crash and we seem to have a fix and the risk seems low?
Is that right? Or can we defer this one as well?

-DaveW

On 5/15/07, Tom Guinane <
guinane@xxxxxxxxxx > wrote:

Dave,
That looks like the right list. The only thing missing would be to assign owners to each item and define targets for resolution. Were you planing on doing that or should I call a meeting?


Cheers, Tom
___________________________________________
Tom Guinane Aperi Project Lead IBM 408-284-4795
guinane@xxxxxxxxxx http://www.eclipse.org/aperi/
"David Wolfe" <2dwolfe@xxxxxxxxx>
Sent by:
aperi-dev-bounces@xxxxxxxxxxx

05/15/2007 09:46 AM


Please respond to
Aperi Development <
aperi-dev@xxxxxxxxxxx>


To
"Aperi Development" <aperi-dev@xxxxxxxxxxx>
cc
Subject
[aperi-dev] R0.3 RC1 results so far













If I am reading right it sounds like:

1) The instructions for windows are still a bit confusing, but once worked through produce a running install.
2) The instructions for Linux don't exist, but one can derive the from the windows instructions and eventually arrive at a running install
3) There are 2 defects outstanding for Linux, one about the default admin group (bugzilla?), one about the scsi disks (176657)
4) There is general confusion about what 3rd party bits are or are not bundled with the install versus what is and is not downloaded by cfgaperi

Am I missing anything?

-DaveW
_______________________________________________
aperi-dev mailing list

aperi-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/aperi-dev


_______________________________________________
aperi-dev mailing list

aperi-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/aperi-dev
_______________________________________________
aperi-dev mailing list
aperi-dev@xxxxxxxxxxx

https://dev.eclipse.org/mailman/listinfo/aperi-dev
_______________________________________________
aperi-dev mailing list
aperi-dev@xxxxxxxxxxx

https://dev.eclipse.org/mailman/listinfo/aperi-dev
_______________________________________________
aperi-dev mailing list
aperi-dev@xxxxxxxxxxx

https://dev.eclipse.org/mailman/listinfo/aperi-dev
_______________________________________________
aperi-dev mailing list
aperi-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/aperi-dev

_______________________________________________
aperi-dev mailing list
aperi-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/aperi-dev


Back to the top