Home » Eclipse Projects » UOMo » I'm getting "The activator org.eclipse.uomo.core.Activator for bundle org.eclipse.uomo.core is
| | | |
| Re: I'm getting "The activator org.eclipse.uomo.core.Activator for bundle org.eclipse.uomo.core [message #663348 is a reply to message #656621] |
Mon, 04 April 2011 17:18   |
 Werner Keil
Messages: 1087
Registered: July 2009 |
Senior Member |
|
|
Carlo,
Sorry for responding about a month later. I was on a conference trip and had
only limited internet access from most locations.
I gave your code a try and it works perfectly fine. So good, I even consider
porting it into UOMo Examples with your permission.
I did add a few lines of code to the View and a ContentProvider class, to
display units not only in the console, but the view itself.
The problem becomes relatively clear in the last lines of your exception
log:
Caused by: java.lang.Error: Unresolved compilation problems:
Syntax error, annotations are only available if source level is 1.5
Syntax error, parameterized types are only available if source level is 1.5
Syntax error, parameterized types are only available if source level is 1.5
at org.eclipse.uomo.core.Activator.<init>(Activator.java:44)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Nativ e Method)
at
sun.reflect.NativeConstructorAccessorImpl.newInstance(Native ConstructorAccessorImpl.java:39)
at
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(De legatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:5 13)
at java.lang.Class.newInstance0(Class.java:355)
at java.lang.Class.newInstance(Class.java:308)
at
org.eclipse.osgi.framework.internal.core.AbstractBundle.load BundleActivator(AbstractBundle.java:151)
... 90 more
Somehow importing the code or setting up a new project the wrong Java
version was selected. It must be at least 1.5 or better 1.6, the exception
tells that part of the code, either the example itself or some dependencies
were compiled against JDK 1.4 or settings compatible with it.
Hope this helped either you or others, even a bit later?
Cheers,
Werner
|
|
|
| Re: I'm getting "The activator org.eclipse.uomo.core.Activator for bundle org.eclipse.uomo.core [message #663560 is a reply to message #663348] |
Tue, 05 April 2011 15:30 |
Carlo Salinari
Messages: 66
Registered: October 2010 |
Member |
|
|
On 4/4/2011 7:18 PM, Werner Keil wrote:
> Carlo,
>
> Sorry for responding about a month later. I was on a conference trip and had
> only limited internet access from most locations.
Hi Werner, glad to see you back. No problem at all.
> I gave your code a try and it works perfectly fine. So good, I even consider
> porting it into UOMo Examples with your permission.
Sure, go ahead.
> The problem becomes relatively clear in the last lines of your exception
> log:
> [...]
> Somehow importing the code or setting up a new project the wrong Java
> version was selected. It must be at least 1.5 or better 1.6, the exception
> tells that part of the code, either the example itself or some dependencies
> were compiled against JDK 1.4 or settings compatible with it.
>
> Hope this helped either you or others, even a bit later?
Uh, that's odd. Thanks a lot for the hint.
Regards,
Carlo
|
|
|
| Re: I'm getting "The activator org.eclipse.uomo.core.Activator for bundle org.eclipse.uomo.core [message #667510 is a reply to message #663560] |
Fri, 29 April 2011 09:28 |
Carlo Salinari
Messages: 66
Registered: October 2010 |
Member |
|
|
On 4/5/2011 5:30 PM, Carlo Salinari wrote:
> On 4/4/2011 7:18 PM, Werner Keil wrote:
>> [...]
>> Somehow importing the code or setting up a new project the wrong Java
>> version was selected. It must be at least 1.5 or better 1.6, the exception
>> tells that part of the code, either the example itself or some dependencies
>> were compiled against JDK 1.4 or settings compatible with it.
>>
>> Hope this helped either you or others, even a bit later?
>
> Uh, that's odd. Thanks a lot for the hint.
Werner,
I'm still hitting this problem each time I try to use the uomo plugins
(core, units, uom api).
Could you please double-check that the error isn't on the uomo side,
i.e. one of the jars was compiled with java profile < 1.5?
I can always replicate the problem with these steps:
0. fresh eclipse helios rcp/rap install
1. install uomo from update site
2. make new "rcp app with a view" from template
3. add dependencies core, units, uom api
4. paste HelloUnits in the View createPartControl()
5. run
Cheers,
Carlo
|
|
|
| Re: I'm getting "The activator org.eclipse.uomo.core.Activator for bundle org.eclipse.uomo.core [message #668136 is a reply to message #667510] |
Tue, 03 May 2011 22:39 |
Carlo Salinari
Messages: 66
Registered: October 2010 |
Member |
|
|
On 4/29/2011 11:28 AM, Carlo Salinari wrote:
> On 4/5/2011 5:30 PM, Carlo Salinari wrote:
>> On 4/4/2011 7:18 PM, Werner Keil wrote:
>>> [...]
>>> Somehow importing the code or setting up a new project the wrong Java
>>> version was selected. It must be at least 1.5 or better 1.6, the exception
>>> tells that part of the code, either the example itself or some dependencies
>>> were compiled against JDK 1.4 or settings compatible with it.
>>>
>>> Hope this helped either you or others, even a bit later?
>>
>> Uh, that's odd. Thanks a lot for the hint.
>
> Werner,
>
> I'm still hitting this problem each time I try to use the uomo plugins
> (core, units, uom api).
>
> Could you please double-check that the error isn't on the uomo side,
> i.e. one of the jars was compiled with java profile < 1.5?
>
> I can always replicate the problem with these steps:
>
> 0. fresh eclipse helios rcp/rap install
> 1. install uomo from update site
> 2. make new "rcp app with a view" from template
> 3. add dependencies core, units, uom api
> 4. paste HelloUnits in the View createPartControl()
> 5. run
It seems that the problem is in unit-api .classpath file. The
JRE_CONTAINER is not set to 1.5 there.
|
|
|
| Re: I'm getting "The activator org.eclipse.uomo.core.Activator for bundle org.eclipse.uomo.core [message #668245 is a reply to message #668136] |
Wed, 04 May 2011 15:50 |
Werner Keil
Messages: 1087
Registered: July 2009 |
Senior Member |
|
|
Some of those files aren't checked in, because the project runs entirely on
Maven.
Thanks for the tip so far and glad, it may lead you to a solution.
Which for the moment is setting all this for your sample project (Maven is
configured to use the right JVM, Java 6 AFAIK)
If it makes it easier for people to just check out sources, I'd add selected
..classpath or .project files where it helps, as long as all their content is
platform neutral and works from Windows to Linux on all major OSs, Eclipse
runs on.
I may take that to Eclipse Day India, and will mention your input, hope you
don't mind the kudos?;-)
Thanks,
Werner
|
|
|
| Re: I'm getting "The activator org.eclipse.uomo.core.Activator for bundle org.eclipse.uomo.core [message #668285 is a reply to message #668245] |
Wed, 04 May 2011 20:35 |
Carlo Salinari
Messages: 66
Registered: October 2010 |
Member |
|
|
On 5/4/2011 5:50 PM, Werner Keil wrote:
> Some of those files aren't checked in, because the project runs entirely on
> Maven.
>
> Thanks for the tip so far and glad, it may lead you to a solution.
> Which for the moment is setting all this for your sample project (Maven is
> configured to use the right JVM, Java 6 AFAIK)
> If it makes it easier for people to just check out sources, I'd add selected
> ..classpath or .project files where it helps, as long as all their content is
> platform neutral and works from Windows to Linux on all major OSs, Eclipse
> runs on.
I'm afraid we are not understanding each other here. What I was saying
in the previous messages is basically that the uomo bundles can't
possibly work as they are distributed now, because they depend on a
package that is compiled with a java profile < 1.5.
This, unfortunately, implies two more things:
1. the jars were never actually tested inside an eclipse app (which
seems rather odd for an eclipse project)
2. I'm the only one trying to actually use them (otherwise the list
would be flooded by messages all reporting the same error)
What I had to do in order to use uomo was:
1. create new eclipse-plugin projects named
uomo.core
uomo.units
uom-api
2. re-import the java sources (thus eliminating all the maven stuff and
switching to the more familiar pde build, with autobuild syntax
checking, error markers and all the usual eclipse ide stuff)
3. update the auto-generated method signatures for
AbstractSystemOfUnits.getUnit that had gone out of sync (I wonder how
you have been able to compile them)
from:
public <Q extends Quantity<Q>> Unit<Q> getUnit(Class<Quantity<Q>> arg0)
to:
public <Q extends Quantity<Q>> Unit<Q> getUnit(Class<Q> quantityType)
4. copying the messages*.properties files to the same package of
Messages.java
You can see all this on bitbucket:
https://bitbucket.org/carlo_salinari/myuomo // test app
https://bitbucket.org/carlo_salinari/uom-api
https://bitbucket.org/carlo_salinari/uomo.core
https://bitbucket.org/carlo_salinari/uomo.units
where I've put the sources reorganized in standard eclipse projects, so
that my colleagues can start using uomo.
All this should have made clear that the uomo project (besides being an
excellent idea with a good code-base) at present has severe usability
problems for the average eclipse programmer and seems to lack any clear
guideline about how to integrate it in an eclipse application.
I really would like to see uomo adopted by as many java projects as
possible, both in the academic and commercial world, but I don't see
this happening until it really makes life easier for the programmers.
|
|
|
| Re: I'm getting "The activator org.eclipse.uomo.core.Activator for bundle org.eclipse.uomo.core [message #668437 is a reply to message #668285] |
Thu, 05 May 2011 16:35 |
Werner Keil
Messages: 1087
Registered: July 2009 |
Senior Member |
|
|
Carlo,
Thanks for the detailed updates.
>1. the jars were never actually tested inside an eclipse app
>(which seems rather odd for an eclipse project)
This is clearly wrong! I used the download URL directly inside Eclipse, it even works with distributions like STS.
If there was a dependency issue that wouldn't work there either.
The somewhat limited number of people using it might be true. Like other projects, e.g. AMP (Agent Modeling Platform) or STEM it has impression on many people to be primarily for scientific use cases. Earlier implementations of Unit-API and its predecessors especially JScience confirmed that impression by their names.
Maven is certainly necessary for automated builds (even if they may not deploy to an Upload Site every time) but the manual PDE build is for most settings there. If one or two might be missing, and you don't adjust that before doing a PDE build, then you'll end up with the mentioned behavior, but the files on the Upload site don't seem to have that problem. At least not with Eclipse 3.5/3.6
Your "clone" is welcome to provide input which files migh be missing, but they should only compliment Maven, not replace it. As soon as the Tycho stuff works well enough, I plan to switch the project to it, but other popular Sonatype projects at Eclipse.org like M2E have significant problems with WTP. It doesn't affect UOMo, but shows, that even a project that has been around for years and is backed by 12 Mio. US$ Venture Capital for Sonatype is facing problems severe enough to draw entire teams away from Eclipse to other IDEs like NetBeans or IntelliJ.
Tomorrow's Eclipse Day India should further spread the word, at least in India. And for Unit-API some of us are working on probing the option of making a new proposal for a Java standard. It is except for manually integrating it as PDE project not easy to understand, why one woule need that as Eclipse project, but I know from similar PDE builds how difficult it can be without such "proxy" projects.
>3. update the auto-generated method signatures for
>AbstractSystemOfUnits.getUnit that had gone out of sync (I wonder how
>you have been able to compile them)
This seems odd and if the problem existed, the Maven build would simply break. I guess after switching to a manual PDE dependency you got a different (older or newer) version of ICU4J which may have caused such issues. The code in Git (both Eclipse and Github) is correct and builds, especially with regards to such basic Java requirements. Hudson here does the job of showing such issues immediately.
Did you actually Git-clone those projects to BitBucket, or are they file-copies not linked to one of the original repositories any more?
Clones or mirrors certainly help, and are welcome, as long as they don't get out of sync with the main Git repositories.
Regards,
Werner
|
|
| |
| Re: I'm getting "The activator org.eclipse.uomo.core.Activator for bundle org.eclipse.uomo.core [message #668469 is a reply to message #668437] |
Thu, 05 May 2011 19:06 |
Carlo Salinari
Messages: 66
Registered: October 2010 |
Member |
|
|
On 5/5/2011 6:35 PM, Werner Keil wrote:
> Carlo,
>
> Thanks for the detailed updates.
>
>> 1. the jars were never actually tested inside an eclipse app
>> (which seems rather odd for an eclipse project)
>
> This is clearly wrong! I used the download URL directly inside Eclipse, it even works with distributions like STS.
> If there was a dependency issue that wouldn't work there either.
As I told you in a previous message, in helios I can always replicate
the problem:
0. fresh eclipse helios rcp/rap install
1. install uomo from update site
2. make new "rcp app with a view" from template
3. add dependencies core, units, uom api
4. paste HelloUnits in the View createPartControl()
5. run
this is what I intend by "tested in an eclipse app", and it clearly
doesn't work.
How did you test it?
> The somewhat limited number of people using it might be true. Like other projects, e.g. AMP (Agent Modeling Platform) or STEM it has impression on many people to be primarily for scientific use cases. Earlier implementations of Unit-API and its predecessors especially JScience confirmed that impression by their names.
That's agreed, and there's nothing wrong with it. What I am saying is:
how many developers came to the uomo site thinking:
"Hey, that's exactly what I was looking for!"
and then desisted because they couldn't even figure out how to build the
thing or run an example?
Those are the really important numbers to watch to assess the project's
usability from the users viewpoint. And I suspect they are pretty high.
> Maven is certainly necessary for automated builds (even if they may not deploy to an Upload Site every time) but the manual PDE build is for most settings there. If one or two might be missing, and you don't adjust that before doing a PDE build, then you'll end up with the mentioned behavior, but the files on the Upload site don't seem to have that problem. At least not with Eclipse 3.5/3.6
Nobody wants to start a religion war about build tools here. You, as the
project leader, have every right to choose the tools you consider the
most appropriate.
Having said that, since PDE is basically Ant, it can do automated builds
as well. Thus, I don't see the necessity of maven, but that's not the point.
The user shouldn't be bothered with build tools details: give him/her
well documented working jars and he/she will be happy as a lark (At
least I would :-) ). That's the whole point.
> Your "clone" is welcome to provide input which files migh be missing, but they should only compliment Maven, not replace it. As soon as the Tycho stuff works well enough, I plan to switch the project to it, but other popular Sonatype projects at Eclipse.org like M2E have significant problems with WTP. It doesn't affect UOMo, but shows, that even a project that has been around for years and is backed by 12 Mio. US$ Venture Capital for Sonatype is facing problems severe enough to draw entire teams away from Eclipse to other IDEs like NetBeans or IntelliJ.
My clone was made out of desperation, because I didn't know any other
way to make the code work and make it usable by my colleagues.
> Tomorrow's Eclipse Day India should further spread the word, at least in India. And for Unit-API some of us are working on probing the option of making a new proposal for a Java standard. It is except for manually integrating it as PDE project not easy to understand, why one woule need that as Eclipse project, but I know from similar PDE builds how difficult it can be without such "proxy" projects.
>
>> 3. update the auto-generated method signatures for
>> AbstractSystemOfUnits.getUnit that had gone out of sync (I wonder how
>> you have been able to compile them)
> This seems odd and if the problem existed, the Maven build would simply break. I guess after switching to a manual PDE dependency you got a different (older or newer) version of ICU4J which may have caused such issues. The code in Git (both Eclipse and Github) is correct and builds, especially with regards to such basic Java requirements. Hudson here does the job of showing such issues immediately.
You are probably right here, I really don't know.
> Did you actually Git-clone those projects to BitBucket, or are they file-copies not linked to one of the original repositories any more?
Copies.
> Clones or mirrors certainly help, and are welcome, as long as they don't get out of sync with the main Git repositories.
Sure, I understand. But please you understand that
out-of-sync-but-works-for-me is better than
in-sync-but-can't-make-it-work, especially if one has deadlines.
Enjoy your staying in India, spread the word about uomo and please think
over the matter a little.
Cheers,
Carlo
|
|
|
| Re: I'm getting "The activator org.eclipse.uomo.core.Activator for bundle org.eclipse.uomo.core [message #668526 is a reply to message #668469] |
Fri, 06 May 2011 04:54 |
Werner Keil
Messages: 1087
Registered: July 2009 |
Senior Member |
|
|
Thanks for the quick response.
I did the same (install, from Update Site and then try it with your earlier ZIP file) in STS, but at the very least after the update site has been moved to its official location, I should be able to do more tests with different Eclipse packages, too.
While the most important part was to hear from co-committer Grahame after he moved to a new company, we are now working on getting at least one or two more committers on board (Eclipse requires an absolute majority of votes, so if out of 2 one doesn't vote, it fails  ) After that succeeded, based on 3 or 4 we'd be happy to consider dedicated people such as yourself, if you feel like contributing this way?
Greetings from Bangalore,
Werner
|
|
| | |
| Re: I'm getting "The activator org.eclipse.uomo.core.Activator for bundle org.eclipse.uomo. [message #694988 is a reply to message #656621] |
Sun, 10 July 2011 14:56 |
Werner Keil
Messages: 1087
Registered: July 2009 |
Senior Member |
|
|
Carlo/all,
The problem is solved!
I'll also update the Bugzilla item as soon as it's all committed.
There were multiple reasons:
- Different target environments seems to have played a minor or no role, but
it is now set to "JavaSE-1.6" in all related OSGi bundles.
- At least one missing dependency to Apache-Commons-Lang. I included 2.3,
gonna test it with 2.1 which comes at least with Indigo for JavaEE, for all
others the "Orbit" dependency on Commons-Lang needs to be available in the
Update Site if necessary.
- Encoding Issue in UOMo Units. At least DimensionImpl contained the "Theta"
character which requires UTF-8 encoding. While Maven and even Eclipse's own
project settings correctly use it, the PDE export of a bundle has the nasty
habbit of using the Eclipse default preference for that. Unless every
workbench where you build it is also set to UTF-8, the class and therefore
plugin fail. This could have been a key factor why your fork didn't work,
but I'm not completely sure.
I created a separate bug:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=351656 to handle this. There
are some weird PDE build.properties settings per library, but I can't yet
say, how they fit with changing file names, e.g. if using a qualifier
(current date/time/build number)
Hope that helps and thanks a lot everybody who contributed to solving it,
Werner
|
|
|
Goto Forum:
Current Time: Thu Apr 18 23:32:04 GMT 2024
Powered by FUDForum. Page generated in 0.02828 seconds |
] 
Search
Help
Register
Login
Home
