I wasn’t able to get as far as the MD5 hash in my testing
before, my problems occurred before that.
I tried to run the plugin from the dropins folder, that worked
better, then I got as far you Daniel, that
the MD5 is in the wrong case.
I changed the hash to be lowercase on the site and now it works,
I could install the SDK from the site,
what is left to do on my part?
Br and thanks for the help,
/Tomas
From: sequoyah-dev-bounces@xxxxxxxxxxx
[mailto:sequoyah-dev-bounces@xxxxxxxxxxx] On Behalf Of Daniel Barboza
Franco
Sent: onsdag den 9 juni 2010 20:52
To: Sequoyah Developers
Subject: Re: [sequoyah-dev] RE: Metadata generator for Pulsar
Hi again,
I've tested your files inside Eclipse. I've downloaded your files and saved
them this way:
c:/test/
- artifacts.xml
- content.xml
- semc_java_me_cldc_sdk.2-5-0-7.zip
I've also downloaded semcsdk_1.0.0.jar, and imported it in my Eclipse 3.6.0. In
this plugin, I changed the value of siteUrl to "file:/C:/test"
Then I ran Eclipse Pulsar (I had the pulsar projects in the same workspace).
All the information was there, so the files are correct. When I clicked
Install, I got the following error:
An
error occurred while collecting items to be installed
session
context was:(profile=""
phase=org.eclipse.equinox.internal.p2.engine.phases.Collect, operand=,
action="">
Problems
downloading artifact: unzip,semc_java_me_cldc_sdk.2-5-0-7.zip,2.5.0.7.
MD5
hash is not as expected. Expected: C91BD55056893EC5A854681F6EDFB24D and found
c91bd55056893ec5a854681f6edfb24d.
This message is not so true, because the expected is c91bd55056893ec5a854681f6edfb24d and
the declared is C91BD55056893EC5A854681F6EDFB24D. Anyway, when I changed this
in artifacts.xml the Sony Ericsson SDK installer started.
Probably is a difference in our environments, since the files are correct
(despite of the MD5).
Tell us exactly what you doing, how your files are organized, which projects
you have in your workspace. I think that you are close :)
Daniel.
On Wed, Jun 9, 2010 at 12:41 PM, <David.Dubrow@xxxxxxxxx> wrote:
Yes,
I get the same error when I try to install from my debugged Pulsar.
You could try dropping your discovery metadata jar file into the dropins folder
and start Pulsar and see if you can test installing that way.
--David
Hi David,
It seems the problem was with files in my site directory that shouldn’t
be there.
For some reason I added an empty content.jar ( I think the metadata generator
asked for
this file, though unfortunately I can’t remember exactly ).
Apparently this file was causing the error which was:
Problems occurred while performing installation: Unable to read repository at
file:/C:/tmp/localrepo.
org.eclipse.equinox.p2.core.ProvisionException: Unable to read repository at
file:/C:/tmp/localrepo.
at
org.eclipse.equinox.internal.p2.metadata.repository.SimpleMetadataRepositoryFactory.load(SimpleMetadataRepositoryFactory.java:128)
at
org.eclipse.equinox.internal.p2.metadata.repository.MetadataRepositoryManager.factoryLoad(MetadataRepositoryManager.java:57)
at
org.eclipse.equinox.internal.p2.repository.helpers.AbstractRepositoryManager.loadRepository(AbstractRepositoryManager.java:713)
at
org.eclipse.equinox.internal.p2.repository.helpers.AbstractRepositoryManager.loadRepository(AbstractRepositoryManager.java:661)
at
org.eclipse.equinox.internal.p2.metadata.repository.MetadataRepositoryManager.loadRepository(MetadataRepositoryManager.java:96)
at
org.eclipse.equinox.internal.p2.metadata.repository.MetadataRepositoryManager.loadRepository(MetadataRepositoryManager.java:92)
at
org.eclipse.equinox.internal.p2.ui.discovery.operations.DiscoveryInstallOperation.addRepositories(DiscoveryInstallOperation.java:273)
at
org.eclipse.equinox.internal.p2.ui.discovery.operations.DiscoveryInstallOperation.computeInstallableUnits(DiscoveryInstallOperation.java:105)
at
org.eclipse.equinox.internal.p2.ui.discovery.operations.DiscoveryInstallOperation.run(DiscoveryInstallOperation.java:63)
at
org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121)
Caused by: java.io.IOException: file:/C:/tmp/localrepo is not a valid
repository location.
at
org.eclipse.equinox.internal.p2.metadata.repository.SimpleMetadataRepositoryFactory.load(SimpleMetadataRepositoryFactory.java:102)
...
9 more
Once I removed the file, I got the same error that the Nokia SDK gives me,
which is:
Problems
occurred while performing installation: Operation details
Operation details
Cannot complete the install because of a conflicting dependency.
Software currently installed: Shared profile 1.0.0.1275480135961
(epp.package.pulsar 1.0.0.1275480135961)
Only one of the following can be installed at once:
Pulsar for Mobile Developers 1.3.0.20100521-0437 (epp.package.pulsar
1.3.0.20100521-0437)
Shared profile 1.0.0.1275480135961 (epp.package.pulsar 1.0.0.1275480135961)
Cannot satisfy dependency:
From: Shared profile 1.0.0.1275480135961 (epp.package.pulsar
1.0.0.1275480135961)
To: epp.package.pulsar [1.3.0.20100521-0437]
But I’m assuming this won’t be a problem in the real environment
since the Nokia SDK gives me the same
error.
Not sure really what tests I can run to see that it works the way it should, do
you have any ideas?
Br Tomas
From: sequoyah-dev-bounces@xxxxxxxxxxx
[mailto:sequoyah-dev-bounces@xxxxxxxxxxx]
On Behalf Of David.Dubrow@xxxxxxxxx
Sent: onsdag den 9 juni 2010 16:51
To: sequoyah-dev@xxxxxxxxxxx
Subject: Re: [sequoyah-dev] RE: Metadata generator for Pulsar
Hi Tomas,
I’m sorry you’re having problems. :(
I didn’t immediately see anything wrong with your content.xml either.
Some questions:
At what point do you get the error?
Is there something in the error log?
Is the zip file in the same directory and publicly accessible?
--David
On 6/9/10 9:18 AM, "ext Westling, Thomas" <Thomas.Westling@xxxxxxxxxxxxxxxx>
wrote:
Hi again Daniel and thanks for the help sofar J
I’m still having problems with our site after correcting the id in
content.xml.
I don’t think the ‘ instead of “ should be a problem since
the Nokia content.xml uses ‘ and is working fine.
Right now when I try it locally I get an error saying my repository is not
valid. By experimenting with Nokia’s plugin
and site, it seems there is some problem in my content.xml, I’m having
little success in finding it though. My current version is
at www.sonyericsson.com/pulsar/content.xml
<http://www.sonyericsson.com/pulsar/content.xml>
Br Tomas
From: sequoyah-dev-bounces@xxxxxxxxxxx
[mailto:sequoyah-dev-bounces@xxxxxxxxxxx]
On Behalf Of Daniel Barboza Franco
Sent: onsdag den 2 juni 2010 19:21
To: Sequoyah Developers
Subject: Re: [sequoyah-dev] RE: Metadata generator for Pulsar
Hi Thomas,
I think that the problem here is the id of your unit in the content.xml file
Instead of
<unit id='SonyEricsson Java ME SDK'
(...)
<provided namespace='org.eclipse.equinox.p2.iu' name='SonyEricsson Java ME
SDK'
try
<unit
id='SonyEricsson_Java_ME_SDK.feature.group'
(...)
<provided namespace='org.eclipse.equinox.p2.iu'
name='SonyEricsson_Java_ME_SDK.feature.group'
Other 2 points that could make difference:
1) You are using ' not " to declare properties inside the xml
2) The last property tag inside properties is no closed
In order to test locally, you don't need the jar file inside
your repo. You can create a folder with your xml files and your zip. Then, in
plugin.xml put siteUrl:"file:/C:/myFolder <file:///C:\myFolder>
" in the place of siteUrl:"http://www.sonyericsson.com/pulsar/".
Hi David and Daniel,
I’ve updated our old content and artifacts.xml as well as created a
plugin for the discovery metadata.
>From testing the plugin locally, it seems to work, as far as the UI parts
atleast.
I am not sure on how to test the content.xml/artifacts.xml and the site itself
though. When I try to install
from the Mobile SDK’s view I get an error:
Problems occurred while performing
installation: The following extensions are not available: Sony Ericsson Java ME
SDK 2.5.0.7 (id=semc_java_me_cldc_sdk.2-5-0-7.zip.feature.group, site=http://www.sonyericsson.com/pulsar/)
The following extensions are not available: Sony Ericsson Java ME SDK 2.5.0.7
(id=semc_java_me_cldc_sdk.2-5-0-7.zip.feature.group, site=http://www.sonyericsson.com/pulsar/)
I guess this error is due to the jar file not being part of the Sequoyah
discovery directory xml file.
Is there a way to test the content.xml/artifacts.xml locally?
The plugin jar file is on our site now anyways, here:
http://www.sonyericsson.com/pulsar/semcsdk_1.0.0.jar
Br Tomas
From: sequoyah-dev-bounces@xxxxxxxxxxx [mailto:sequoyah-dev-bounces@xxxxxxxxxxx]
On Behalf Of David.Dubrow@xxxxxxxxx
Sent: tisdag den 1 juni 2010 15:01
To: sequoyah-dev@xxxxxxxxxxx
Subject: Re: [sequoyah-dev] RE: Metadata generator for Pulsar
Hi Daniel,
I think that making the metadata generator create the discovery jars would be a
non-trivial amount of work and would not give us too much benefit over the
existing plugin.xml editor. The steps I outlined for using the plugin.xml
editor should be pretty easy to follow. I think the hardest part will be
creating the marketing elements (icon, screenshot and summary) not adding them
to the discovery jar. ;)
BR,
David
On 5/31/10 12:26 PM, "ext Daniel Barboza Franco" <nkvg64@xxxxxxxxxxxx <http://nkvg64@xxxxxxxxxxxx>
> wrote:
Hey guys,
It seems that the metadata generator tool is not updated with the new SDK
discovery feature.
Thomas, you will need 3 files:
- artifacts.xml
- content.xml
- <your-plug-in>.jar
<your-plug-in>.jar
will contain the extensions for the SDK discovery view.
David, is there an easier way than manually create the files? In which parts
the metadata generator can improve the steps?
As a reference you can use Nokia's repository: http://tools.ext.nokia.com/pulsar/
Nokia does not have .exe as installers, if this is your case let me know so I
can explain how to do the trick.
regards,
Daniel.
On Mon, May 31, 2010 at 8:35 AM, Westling, Thomas <Thomas.Westling@xxxxxxxxxxxxxxxx
<http://Thomas.Westling@xxxxxxxxxxxxxxxx>
> wrote:
Hi David,
I tried the RC1 Pulsar package as dev env, and succeeded in running the New
Repository wizard.
However, when I’ve finished, the content.xml only contain the following
information:
<repository name='Sony Ericsson Java ME SDK'
type='org.eclipse.equinox.internal.p2.metadata.repository.LocalMetadataRepository'
version='1'>
<properties size='2'>
<property name='p2.timestamp'
value='1275304955804'/>
<property name='p2.compressed' value='false'/>
</properties>
</repository>
All the information I added in the wizard, such as description, license etc, is
missing. I’ve tried this both with an exe inside a zip, or just an exe.
The artifacts are present in the local repo which I browse to, any idea what
isn’t working?
Another question, you say that there is a document describing how to create the
discovery metadata,
where can I find this document?
Br Tomas
From: Westling, Thomas
Sent: torsdag den 27 maj 2010 15:51
To: 'David.Dubrow@xxxxxxxxx <David.Dubrow@xxxxxxxxx>
<http://David.Dubrow@xxxxxxxxx>
'
Good idea, now that I think of it, I should probably sent it there in the first
place
J
I haven’t tried using Pulsar as dev env, I will give that a try,
Thanks,
Tomas
From: David.Dubrow@xxxxxxxxx <http://David.Dubrow@xxxxxxxxx>
[mailto:David.Dubrow@xxxxxxxxx]
Sent: torsdag den 27 maj 2010 15:46
To: Westling, Thomas
Cc: sequoyah-dev@xxxxxxxxxxx
<http://sequoyah-dev@xxxxxxxxxxx>
Subject: Re: Metadata generator for Pulsar
I’ve copied this thread to the Sequoyah-dev list because it may be useful
to others. :)
Have you tried using the Pulsar RC1 package itself as a development
environment?
You would only need the metadata generator project since everything else would
be coming from Pulsar as the target platform.
Then run or debug from an Eclipse Application launch configuration and in the
running eclipse, the metadata generator tool will show up as a menu item:
Pulsar Admin->New Repository
This brings up a dialog to create a local repository and allow adding
installable units representing the sdks.
One restriction is that in the local repository you are creating, the sdk
installers must be present so that the artifacts’ size and other info can
be gathered.
Then once everything is working locally, you can move it to a server and let
the Sequoyah team know the URL.
After the p2 repository is generated, you will need to create the discovery
metadata jar.
This can be tested also from a local workspace and then deployed with
File->Export... Plug-in Development/Deployable plug-ins and fragments as
outlined in my doc for creating the discovery metadata.
BR and HTH,
--David
On 5/27/10 8:11 AM, "ext Westling, Thomas" <Thomas.Westling@xxxxxxxxxxxxxxxx
<http://Thomas.Westling@xxxxxxxxxxxxxxxx>
<http://Thomas.Westling@xxxxxxxxxxxxxxxx>
> wrote:
I’ve tried with both Helios and Galileo versions of the Classic Eclipse
dist.
Both have p2, but both also lack the p2.discovery bundles.
My compilation errors exist outside of p2.discovery though, so I’m afraid
that
if I find the p2.discovery bundles, I will still have compilation errors.
Br Tomas
From: David.Dubrow@xxxxxxxxx <http://David.Dubrow@xxxxxxxxx>
<http://David.Dubrow@xxxxxxxxx>
[mailto:David.Dubrow@xxxxxxxxx]
Sent: torsdag den 27 maj 2010 15:08
To: Westling, Thomas
Cc: kpqb38@xxxxxxxxxxxx
<http://kpqb38@xxxxxxxxxxxx>
<http://kpqb38@xxxxxxxxxxxx>
Subject: Re: Metadata generator for Pulsar
Hi Thomas,
The projects on the trunk should be the correct version of the source to use.
What version of eclipse are you using to build the pulsar projects?
It looks like you don’t have p2 in your target platform.
I’ve cc’d Daniel to see if he has some suggestions.
--David
On 5/27/10 7:27 AM, "ext Westling, Thomas" <Thomas.Westling@xxxxxxxxxxxxxxxx
<http://Thomas.Westling@xxxxxxxxxxxxxxxx>
<http://Thomas.Westling@xxxxxxxxxxxxxxxx>
> wrote:
Hi David,
I am trying to use your Metadata generator tool to generate the proper
information for the
Sony Ericsson SDK. I couldn’t find any information on how to use the tool
in the Pulsar mail thread,
is it available somewhere else?
I get a lot of compilation errors and missing bundles when importing the
following
Bundles from svn:
org.eclipse.sequoyah.pulsar.metadata.generator
org.eclipse.sequoyah.pulsar.core
org.eclipse.sequoyah.pulsar.ui
org.eclipse.sequoyah.pulsar.core.tests
The org.eclipse.equinox.p2.discovery.xxx bundles seem to be missing from my
workspace,
but in addition, I get a lot of compilation errors, from the
org.eclipse.equinox.p2.metadata package.
Do you know what I’m doing wrong?
I’ve tried the version of the plugins in the trunk as well as the pulsar
branch
of the sequyoah svn, on Galileo and Helios.
Best regards,
Tomas Westling,
Sony Ericsson
_______________________________________________
sequoyah-dev mailing list
sequoyah-dev@xxxxxxxxxxx
<http://sequoyah-dev@xxxxxxxxxxx>
https://dev.eclipse.org/mailman/listinfo/sequoyah-dev
_______________________________________________
sequoyah-dev mailing list
sequoyah-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/sequoyah-dev
_______________________________________________
sequoyah-dev mailing list
sequoyah-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/sequoyah-dev
|
