You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ace.apache.org by Marcel Offermans <ma...@luminis.nl> on 2010/03/19 00:18:29 UTC
Maven migration, almost there.
Hey guys,
Over the last day or two I've been working hard on fixing all the small issues in the Maven build. I've managed to fix most of them, all the bundles are working and with the help of Toni I managed to get some Knopflerfish bundles into the assembly for the server.
There is one remaining issue, and I can't seem to make that work, even with the example that Jean-Baptiste provided, and that is the WebUI bundle (ace-webui). This is a GWT based WAR file that has been converted into a bundle (JAR) file, adding some specific OSGi metadata. Please check the bundle you get when building legacy/core (in deploy/bundle) for reference.
I tried using the URL handler to dynamically wrap a WAR but that does not seem to get me a fully working bundle in this case. It seems to work but interaction with the server is not working, and the URL handler does not pick up on the Activator that is in there and that must be invoked to hook the WAR up to the rest of the bundles.
Anyway, this seems to be a pretty advanced use case for Maven, and I can definitely use some help from some of the Maven experts in the project. We're almost there! :)
Greetings, Marcel
Re: Maven migration, almost there.
Posted by Toni Menzel <to...@okidokiteam.com>.
On Mon, May 17, 2010 at 10:42 PM, Marcel Offermans
<ma...@luminis.nl> wrote:
> Hello Dennis,
>
> On May 17, 2010, at 22:00 , Crissman, Dennis wrote:
>
>> I have been following the community for sometime, but this is my first
>> posting back.
>
> Good to hear from you!
>
>> I am attempting to stand up the server and gateway. Aside from the two felix
>> bundles mentioned below, I have run into some additional problems.
>
>> Before I get to that, when I first attempted to run both I got the following
>> error message:
>> =====
>> -> Felix 2.0.1 : connecting...
>> Oops, there has been a problem!
>> URL [mvn:org.apache.felix/org.apache.felix.main/2.0.1] could not be
>> resolved.
>> =====
>> To resolve I simply added the missing package to the maven repository. Not
>> sure if this is a dependency that was missed in the POM, but thought I might
>> mention it.
>
> Over the last few days I've seen similar messages being posted on the Felix mailing lists, see http://markmail.org/message/nyfsumyqgvsktjax for the thread. I'm still not sure what exactly is causing this. There have been some issues with the Felix download site, and with the OPS4J site hosting the Pax Runner project. Let's see what comes out of this. It's definitely not a problem on your end, I can reproduce the problem here.
>
The artifact of question is a regular felix artifact that should be
picked from central.. so nothing related to ops4j repositories.
But what is much worse: Looks like the main repo instance
(http://osgi.sonatype.org) has been expired (look at the upper right
corner).
You can see what pax runner tries to access when running the run.sh
script with --log=debug option.
Will contact the guys..
Toni
>> After that hurdle, I am now getting different error messages for each.
>>
>> Server:
>> org.ops4j.pax.runner.platform.PlatformException:
>> [file:/path/apache-ace/ace-devserver/ace-bundles/surefire-testng-2.5.jar] is
>> not a valid bundle
>
> Just committed a fix for that (rev 945358). I accidentally forgot to mark this bundle as <scope>test</scope> so it ended up in the distribution.
>
>> Gateway:
>> Felix actually stands up, but a series of exceptions are thrown. I will
>> attach them to keep this email short, but they all seem to revolve around
>> junit.framework being unresolved.
>
> Could be related to the problem above.
>
>> Any assistance on these would be appreciated.
>
> Hope this helps!
>
> Greetings, Marcel
>
>
--
Toni Menzel
Independent Software Developer
Professional Profile: http://okidokiteam.com
toni@okidokiteam.com
http://www.ops4j.org - New Energy for OSS Communities - Open
Participation Software.
Re: Maven migration, almost there.
Posted by "Crissman, Dennis" <dc...@perimeterusa.com>.
Ahh... My mistake. I will do that next time.
Thanks,
Dennis
On 5/19/10 10:39 AM, "Toni Menzel" <to...@okidokiteam.com> wrote:
> On Wed, May 19, 2010 at 4:11 PM, Crissman, Dennis
> <dc...@perimeterusa.com> wrote:
>> I was able to get past the error message, I will continue to play around and
>> let you know if I run into any other issues.
>>
>> One thing I did notice though, when I attempted to re-package the
>> application, the ace-target-devgateway-0.8.0-SNAPSHOT-distribution.zip and
>> ace-target-devserver-0.8.0-SNAPSHOT-distribution.zip files were not getting
>> updated also. I manually navigated to their respective target directories
>> and cleaned and packaged them and they worked just fine. Possibly a missing
>> step? It worked before, so uncertain what may have changed.
>
> Well, what are you doing exactly ?
> Those targets projects are using the standard maven assembly plugin.
> Though, those are not included in the standard profile (currently
> called release, active by default) when doing a mvn clean install on
> the root folder.
> For targets being build, you might want to use the targets profile like so:
> mvn -Ptargets mvn clean install
>
>
>
>
>>
>> Anyway, thank you for looking into these issues.
>>
>> -Dennis
>>
>> On 5/18/10 4:56 PM, "Marcel Offermans" <ma...@luminis.nl> wrote:
>>
>>> On May 18, 2010, Crissman, Dennis wrote:
>>>
>>>> I pulled down the POM change and re-packaged. It looks like I am getting
>>>> the
>>>> same, or at least similar, error messages as before. See attached for
>>>> details.
>>>
>>> Ok, I got everything running again here. Let me know if it works for you too
>>> now.
>>>
>>> Greetings, Marcel
>>>
>>>
>>>
>>
>>
>>
>>
>>
>> --
>> The sender of this email subscribes to Perimeter E-Security's email
>> anti-virus service. This email has been scanned for malicious code and is
>> believed to be virus free. For more information on email security please
>> visit: http://www.perimeterusa.com/services/messaging
>> This communication is confidential, intended only for the named recipient(s)
>> above and may contain trade secrets or other information that is exempt from
>> disclosure under applicable law. Any use, dissemination, distribution or
>> copying of this communication by anyone other than the named recipient(s) is
>> strictly prohibited. If you have received this communication in error,
>> please
>> delete the email and immediately notify our Command Center at 203-541-3444.
>>
>> Thanks
>>
>
>
--
The sender of this email subscribes to Perimeter E-Security's email
anti-virus service. This email has been scanned for malicious code and is
believed to be virus free. For more information on email security please
visit: http://www.perimeterusa.com/services/messaging
This communication is confidential, intended only for the named recipient(s)
above and may contain trade secrets or other information that is exempt from
disclosure under applicable law. Any use, dissemination, distribution or
copying of this communication by anyone other than the named recipient(s) is
strictly prohibited. If you have received this communication in error, please
delete the email and immediately notify our Command Center at 203-541-3444.
Thanks
Re: Maven migration, almost there.
Posted by Toni Menzel <to...@okidokiteam.com>.
On Wed, May 19, 2010 at 4:11 PM, Crissman, Dennis
<dc...@perimeterusa.com> wrote:
> I was able to get past the error message, I will continue to play around and
> let you know if I run into any other issues.
>
> One thing I did notice though, when I attempted to re-package the
> application, the ace-target-devgateway-0.8.0-SNAPSHOT-distribution.zip and
> ace-target-devserver-0.8.0-SNAPSHOT-distribution.zip files were not getting
> updated also. I manually navigated to their respective target directories
> and cleaned and packaged them and they worked just fine. Possibly a missing
> step? It worked before, so uncertain what may have changed.
Well, what are you doing exactly ?
Those targets projects are using the standard maven assembly plugin.
Though, those are not included in the standard profile (currently
called release, active by default) when doing a mvn clean install on
the root folder.
For targets being build, you might want to use the targets profile like so:
mvn -Ptargets mvn clean install
>
> Anyway, thank you for looking into these issues.
>
> -Dennis
>
> On 5/18/10 4:56 PM, "Marcel Offermans" <ma...@luminis.nl> wrote:
>
>> On May 18, 2010, Crissman, Dennis wrote:
>>
>>> I pulled down the POM change and re-packaged. It looks like I am getting the
>>> same, or at least similar, error messages as before. See attached for
>>> details.
>>
>> Ok, I got everything running again here. Let me know if it works for you too
>> now.
>>
>> Greetings, Marcel
>>
>>
>>
>
>
>
>
>
> --
> The sender of this email subscribes to Perimeter E-Security's email
> anti-virus service. This email has been scanned for malicious code and is
> believed to be virus free. For more information on email security please
> visit: http://www.perimeterusa.com/services/messaging
> This communication is confidential, intended only for the named recipient(s)
> above and may contain trade secrets or other information that is exempt from
> disclosure under applicable law. Any use, dissemination, distribution or
> copying of this communication by anyone other than the named recipient(s) is
> strictly prohibited. If you have received this communication in error, please
> delete the email and immediately notify our Command Center at 203-541-3444.
>
> Thanks
>
--
Toni Menzel
Independent Software Developer
Professional Profile: http://okidokiteam.com
toni@okidokiteam.com
http://www.ops4j.org - New Energy for OSS Communities - Open
Participation Software.
Re: Maven migration, almost there.
Posted by "Crissman, Dennis" <dc...@perimeterusa.com>.
I was able to get past the error message, I will continue to play around and
let you know if I run into any other issues.
One thing I did notice though, when I attempted to re-package the
application, the ace-target-devgateway-0.8.0-SNAPSHOT-distribution.zip and
ace-target-devserver-0.8.0-SNAPSHOT-distribution.zip files were not getting
updated also. I manually navigated to their respective target directories
and cleaned and packaged them and they worked just fine. Possibly a missing
step? It worked before, so uncertain what may have changed.
Anyway, thank you for looking into these issues.
-Dennis
On 5/18/10 4:56 PM, "Marcel Offermans" <ma...@luminis.nl> wrote:
> On May 18, 2010, Crissman, Dennis wrote:
>
>> I pulled down the POM change and re-packaged. It looks like I am getting the
>> same, or at least similar, error messages as before. See attached for
>> details.
>
> Ok, I got everything running again here. Let me know if it works for you too
> now.
>
> Greetings, Marcel
>
>
>
--
The sender of this email subscribes to Perimeter E-Security's email
anti-virus service. This email has been scanned for malicious code and is
believed to be virus free. For more information on email security please
visit: http://www.perimeterusa.com/services/messaging
This communication is confidential, intended only for the named recipient(s)
above and may contain trade secrets or other information that is exempt from
disclosure under applicable law. Any use, dissemination, distribution or
copying of this communication by anyone other than the named recipient(s) is
strictly prohibited. If you have received this communication in error, please
delete the email and immediately notify our Command Center at 203-541-3444.
Thanks
Re: Maven migration, almost there.
Posted by Marcel Offermans <ma...@luminis.nl>.
On May 18, 2010, Crissman, Dennis wrote:
> I pulled down the POM change and re-packaged. It looks like I am getting the
> same, or at least similar, error messages as before. See attached for
> details.
Ok, I got everything running again here. Let me know if it works for you too now.
Greetings, Marcel
Re: Maven migration, almost there.
Posted by Marcel Offermans <ma...@luminis.nl>.
Hello Dennis,
Now that Pax Runner is working again, I see the same problems in the gateway target. I probably introduced them by accident when adding unit tests to the different bundles. Working on cleaning up the mistakes, give me some time to complete them! :)
Greetings, Marcel
On May 18, 2010, at 17:25 , Crissman, Dennis wrote:
> Looks like my attachments did not make it.
>
> Server Error:
> =====
> ___
> / /
> / / Oops, there has been a problem!
> / /
> /__/ org.ops4j.pax.runner.platform.PlatformException:
> [file:/path/ace-devserver/ace-bundles/surefire-testng-2.5.jar] is not a
> valid bundle
> ___
> /__/ Use --log=debug to see details.
>
> =====
>
> Gateway Errors:
>
> =====
> -> ERROR: Error starting
> file:bundles/org.apache.ace.deployment_0.8.0.SNAPSHOT.jar
> (org.osgi.framework.BundleException: Unresolved constraint in bundle
> org.apache.ace.deployment [3]: package; (package=junit.framework))
> org.osgi.framework.BundleException: Unresolved constraint in bundle
> org.apache.ace.deployment [3]: package; (package=junit.framework)
> at org.apache.felix.framework.Felix.resolveBundle(Felix.java:3263)
> at org.apache.felix.framework.Felix.startBundle(Felix.java:1597)
> at org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:1077)
> at
> org.apache.felix.framework.StartLevelImpl.run(StartLevelImpl.java:264)
> at java.lang.Thread.run(Thread.java:613)
> ERROR: Error starting
> file:bundles/org.apache.ace.deployment.task_0.8.0.SNAPSHOT.jar
> (org.osgi.framework.BundleException: Unresolved constraint in bundle
> org.apache.ace.discovery.property [5]: package; (package=junit.framework))
> org.osgi.framework.BundleException: Unresolved constraint in bundle
> org.apache.ace.discovery.property [5]: package; (package=junit.framework)
> at org.apache.felix.framework.Felix.resolveBundle(Felix.java:3263)
> at org.apache.felix.framework.Felix.startBundle(Felix.java:1597)
> at org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:1077)
> at
> org.apache.felix.framework.StartLevelImpl.run(StartLevelImpl.java:264)
> at java.lang.Thread.run(Thread.java:613)
> ERROR: Error starting
> file:bundles/org.apache.ace.discovery.property_0.8.0.SNAPSHOT.jar
> (org.osgi.framework.BundleException: Unresolved constraint in bundle
> org.apache.ace.discovery.property [5]: package; (package=junit.framework))
> org.osgi.framework.BundleException: Unresolved constraint in bundle
> org.apache.ace.discovery.property [5]: package; (package=junit.framework)
> at org.apache.felix.framework.Felix.resolveBundle(Felix.java:3263)
> at org.apache.felix.framework.Felix.startBundle(Felix.java:1597)
> at org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:1077)
> at
> org.apache.felix.framework.StartLevelImpl.run(StartLevelImpl.java:264)
> at java.lang.Thread.run(Thread.java:613)
> ERROR: Error starting
> file:bundles/org.apache.ace.gateway.log_0.8.0.SNAPSHOT.jar
> (org.osgi.framework.BundleException: Unresolved constraint in bundle
> org.apache.ace.discovery.property [5]: package; (package=junit.framework))
> org.osgi.framework.BundleException: Unresolved constraint in bundle
> org.apache.ace.discovery.property [5]: package; (package=junit.framework)
> at org.apache.felix.framework.Felix.resolveBundle(Felix.java:3263)
> at org.apache.felix.framework.Felix.startBundle(Felix.java:1597)
> at org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:1077)
> at
> org.apache.felix.framework.StartLevelImpl.run(StartLevelImpl.java:264)
> at java.lang.Thread.run(Thread.java:613)
> ERROR: Error starting
> file:bundles/org.apache.ace.gateway.log.store_0.8.0.SNAPSHOT.jar
> (org.osgi.framework.BundleException: Unresolved constraint in bundle
> org.apache.ace.identification.property [8]: package;
> (package=junit.framework))
> org.osgi.framework.BundleException: Unresolved constraint in bundle
> org.apache.ace.identification.property [8]: package;
> (package=junit.framework)
> at org.apache.felix.framework.Felix.resolveBundle(Felix.java:3263)
> at org.apache.felix.framework.Felix.startBundle(Felix.java:1597)
> at org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:1077)
> at
> org.apache.felix.framework.StartLevelImpl.run(StartLevelImpl.java:264)
> at java.lang.Thread.run(Thread.java:613)
> org.osgi.framework.BundleException: Unresolved constraint in bundle
> org.apache.ace.identification.property [8]: package;
> (package=junit.framework)ERROR: Error starting
> file:bundles/org.apache.ace.identification.property_0.8.0.SNAPSHOT.jar
> (org.osgi.framework.BundleException: Unresolved constraint in bundle
> org.apache.ace.identification.property [8]: package;
> (package=junit.framework))
>
> at org.apache.felix.framework.Felix.resolveBundle(Felix.java:3263)
> at org.apache.felix.framework.Felix.startBundle(Felix.java:1597)
> at org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:1077)
> at
> org.apache.felix.framework.StartLevelImpl.run(StartLevelImpl.java:264)
> at java.lang.Thread.run(Thread.java:613)
> ERROR: Error starting file:bundles/org.apache.ace.log_0.8.0.SNAPSHOT.jar
> (org.osgi.framework.BundleException: Unresolved constraint in bundle
> org.apache.ace.log [9]: package; (package=junit.framework))
> org.osgi.framework.BundleException: Unresolved constraint in bundle
> org.apache.ace.log [9]: package; (package=junit.framework)
> at org.apache.felix.framework.Felix.resolveBundle(Felix.java:3263)
> at org.apache.felix.framework.Felix.startBundle(Felix.java:1597)
> at org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:1077)
> at
> org.apache.felix.framework.StartLevelImpl.run(StartLevelImpl.java:264)
> at java.lang.Thread.run(Thread.java:613)
> ERROR: Error starting
> file:bundles/org.apache.ace.log.listener_0.8.0.SNAPSHOT.jar
> (org.osgi.framework.BundleException: Unresolved constraint in bundle
> org.apache.ace.log [9]: package; (package=junit.framework))
> org.osgi.framework.BundleException: Unresolved constraint in bundle
> org.apache.ace.log [9]: package; (package=junit.framework)
> at org.apache.felix.framework.Felix.resolveBundle(Felix.java:3263)
> at org.apache.felix.framework.Felix.startBundle(Felix.java:1597)
> at org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:1077)
> at
> org.apache.felix.framework.StartLevelImpl.run(StartLevelImpl.java:264)
> at java.lang.Thread.run(Thread.java:613)
> =====
>
> On 5/18/10 9:34 AM, "Dennis Crissman" <dc...@perimeterusa.com> wrote:
>
>> I pulled down the POM change and re-packaged. It looks like I am getting the
>> same, or at least similar, error messages as before. See attached for
>> details.
>>
>> On 5/17/10 4:42 PM, "Marcel Offermans" <ma...@luminis.nl> wrote:
>>
>>> Hello Dennis,
>>>
>>> On May 17, 2010, at 22:00 , Crissman, Dennis wrote:
>>>
>>>> I have been following the community for sometime, but this is my first
>>>> posting back.
>>>
>>> Good to hear from you!
>>>
>>>> I am attempting to stand up the server and gateway. Aside from the two felix
>>>> bundles mentioned below, I have run into some additional problems.
>>>
>>>> Before I get to that, when I first attempted to run both I got the following
>>>> error message:
>>>> =====
>>>> -> Felix 2.0.1 : connecting...
>>>> Oops, there has been a problem!
>>>> URL [mvn:org.apache.felix/org.apache.felix.main/2.0.1] could not be
>>>> resolved.
>>>> =====
>>>> To resolve I simply added the missing package to the maven repository. Not
>>>> sure if this is a dependency that was missed in the POM, but thought I might
>>>> mention it.
>>>
>>> Over the last few days I've seen similar messages being posted on the Felix
>>> mailing lists, see http://markmail.org/message/nyfsumyqgvsktjax for the
>>> thread. I'm still not sure what exactly is causing this. There have been some
>>> issues with the Felix download site, and with the OPS4J site hosting the Pax
>>> Runner project. Let's see what comes out of this. It's definitely not a
>>> problem on your end, I can reproduce the problem here.
>>>
>>>> After that hurdle, I am now getting different error messages for each.
>>>>
>>>> Server:
>>>> org.ops4j.pax.runner.platform.PlatformException:
>>>> [file:/path/apache-ace/ace-devserver/ace-bundles/surefire-testng-2.5.jar] is
>>>> not a valid bundle
>>>
>>> Just committed a fix for that (rev 945358). I accidentally forgot to mark
>>> this
>>> bundle as <scope>test</scope> so it ended up in the distribution.
>>>
>>>> Gateway:
>>>> Felix actually stands up, but a series of exceptions are thrown. I will
>>>> attach them to keep this email short, but they all seem to revolve around
>>>> junit.framework being unresolved.
>>>
>>> Could be related to the problem above.
>>>
>>>> Any assistance on these would be appreciated.
>>>
>>> Hope this helps!
>>>
>>> Greetings, Marcel
>>>
>>>
>>>
>>
>>
>>
>>
>>
>> --
>> The sender of this email subscribes to Perimeter E-Security's email
>> anti-virus service. This email has been scanned for malicious code and is
>> believed to be virus free. For more information on email security please
>> visit: http://www.perimeterusa.com/services/messaging
>> This communication is confidential, intended only for the named recipient(s)
>> above and may contain trade secrets or other information that is exempt from
>> disclosure under applicable law. Any use, dissemination, distribution or
>> copying of this communication by anyone other than the named recipient(s) is
>> strictly prohibited. If you have received this communication in error, please
>> delete the email and immediately notify our Command Center at 203-541-3444.
>>
>> Thanks
>
>
>
>
>
> --
> The sender of this email subscribes to Perimeter E-Security's email
> anti-virus service. This email has been scanned for malicious code and is
> believed to be virus free. For more information on email security please
> visit: http://www.perimeterusa.com/services/messaging
> This communication is confidential, intended only for the named recipient(s)
> above and may contain trade secrets or other information that is exempt from
> disclosure under applicable law. Any use, dissemination, distribution or
> copying of this communication by anyone other than the named recipient(s) is
> strictly prohibited. If you have received this communication in error, please
> delete the email and immediately notify our Command Center at 203-541-3444.
>
> Thanks
>
Re: Maven migration, almost there.
Posted by "Crissman, Dennis" <dc...@perimeterusa.com>.
Looks like my attachments did not make it.
Server Error:
=====
___
/ /
/ / Oops, there has been a problem!
/ /
/__/ org.ops4j.pax.runner.platform.PlatformException:
[file:/path/ace-devserver/ace-bundles/surefire-testng-2.5.jar] is not a
valid bundle
___
/__/ Use --log=debug to see details.
=====
Gateway Errors:
=====
-> ERROR: Error starting
file:bundles/org.apache.ace.deployment_0.8.0.SNAPSHOT.jar
(org.osgi.framework.BundleException: Unresolved constraint in bundle
org.apache.ace.deployment [3]: package; (package=junit.framework))
org.osgi.framework.BundleException: Unresolved constraint in bundle
org.apache.ace.deployment [3]: package; (package=junit.framework)
at org.apache.felix.framework.Felix.resolveBundle(Felix.java:3263)
at org.apache.felix.framework.Felix.startBundle(Felix.java:1597)
at org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:1077)
at
org.apache.felix.framework.StartLevelImpl.run(StartLevelImpl.java:264)
at java.lang.Thread.run(Thread.java:613)
ERROR: Error starting
file:bundles/org.apache.ace.deployment.task_0.8.0.SNAPSHOT.jar
(org.osgi.framework.BundleException: Unresolved constraint in bundle
org.apache.ace.discovery.property [5]: package; (package=junit.framework))
org.osgi.framework.BundleException: Unresolved constraint in bundle
org.apache.ace.discovery.property [5]: package; (package=junit.framework)
at org.apache.felix.framework.Felix.resolveBundle(Felix.java:3263)
at org.apache.felix.framework.Felix.startBundle(Felix.java:1597)
at org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:1077)
at
org.apache.felix.framework.StartLevelImpl.run(StartLevelImpl.java:264)
at java.lang.Thread.run(Thread.java:613)
ERROR: Error starting
file:bundles/org.apache.ace.discovery.property_0.8.0.SNAPSHOT.jar
(org.osgi.framework.BundleException: Unresolved constraint in bundle
org.apache.ace.discovery.property [5]: package; (package=junit.framework))
org.osgi.framework.BundleException: Unresolved constraint in bundle
org.apache.ace.discovery.property [5]: package; (package=junit.framework)
at org.apache.felix.framework.Felix.resolveBundle(Felix.java:3263)
at org.apache.felix.framework.Felix.startBundle(Felix.java:1597)
at org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:1077)
at
org.apache.felix.framework.StartLevelImpl.run(StartLevelImpl.java:264)
at java.lang.Thread.run(Thread.java:613)
ERROR: Error starting
file:bundles/org.apache.ace.gateway.log_0.8.0.SNAPSHOT.jar
(org.osgi.framework.BundleException: Unresolved constraint in bundle
org.apache.ace.discovery.property [5]: package; (package=junit.framework))
org.osgi.framework.BundleException: Unresolved constraint in bundle
org.apache.ace.discovery.property [5]: package; (package=junit.framework)
at org.apache.felix.framework.Felix.resolveBundle(Felix.java:3263)
at org.apache.felix.framework.Felix.startBundle(Felix.java:1597)
at org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:1077)
at
org.apache.felix.framework.StartLevelImpl.run(StartLevelImpl.java:264)
at java.lang.Thread.run(Thread.java:613)
ERROR: Error starting
file:bundles/org.apache.ace.gateway.log.store_0.8.0.SNAPSHOT.jar
(org.osgi.framework.BundleException: Unresolved constraint in bundle
org.apache.ace.identification.property [8]: package;
(package=junit.framework))
org.osgi.framework.BundleException: Unresolved constraint in bundle
org.apache.ace.identification.property [8]: package;
(package=junit.framework)
at org.apache.felix.framework.Felix.resolveBundle(Felix.java:3263)
at org.apache.felix.framework.Felix.startBundle(Felix.java:1597)
at org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:1077)
at
org.apache.felix.framework.StartLevelImpl.run(StartLevelImpl.java:264)
at java.lang.Thread.run(Thread.java:613)
org.osgi.framework.BundleException: Unresolved constraint in bundle
org.apache.ace.identification.property [8]: package;
(package=junit.framework)ERROR: Error starting
file:bundles/org.apache.ace.identification.property_0.8.0.SNAPSHOT.jar
(org.osgi.framework.BundleException: Unresolved constraint in bundle
org.apache.ace.identification.property [8]: package;
(package=junit.framework))
at org.apache.felix.framework.Felix.resolveBundle(Felix.java:3263)
at org.apache.felix.framework.Felix.startBundle(Felix.java:1597)
at org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:1077)
at
org.apache.felix.framework.StartLevelImpl.run(StartLevelImpl.java:264)
at java.lang.Thread.run(Thread.java:613)
ERROR: Error starting file:bundles/org.apache.ace.log_0.8.0.SNAPSHOT.jar
(org.osgi.framework.BundleException: Unresolved constraint in bundle
org.apache.ace.log [9]: package; (package=junit.framework))
org.osgi.framework.BundleException: Unresolved constraint in bundle
org.apache.ace.log [9]: package; (package=junit.framework)
at org.apache.felix.framework.Felix.resolveBundle(Felix.java:3263)
at org.apache.felix.framework.Felix.startBundle(Felix.java:1597)
at org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:1077)
at
org.apache.felix.framework.StartLevelImpl.run(StartLevelImpl.java:264)
at java.lang.Thread.run(Thread.java:613)
ERROR: Error starting
file:bundles/org.apache.ace.log.listener_0.8.0.SNAPSHOT.jar
(org.osgi.framework.BundleException: Unresolved constraint in bundle
org.apache.ace.log [9]: package; (package=junit.framework))
org.osgi.framework.BundleException: Unresolved constraint in bundle
org.apache.ace.log [9]: package; (package=junit.framework)
at org.apache.felix.framework.Felix.resolveBundle(Felix.java:3263)
at org.apache.felix.framework.Felix.startBundle(Felix.java:1597)
at org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:1077)
at
org.apache.felix.framework.StartLevelImpl.run(StartLevelImpl.java:264)
at java.lang.Thread.run(Thread.java:613)
=====
On 5/18/10 9:34 AM, "Dennis Crissman" <dc...@perimeterusa.com> wrote:
> I pulled down the POM change and re-packaged. It looks like I am getting the
> same, or at least similar, error messages as before. See attached for
> details.
>
> On 5/17/10 4:42 PM, "Marcel Offermans" <ma...@luminis.nl> wrote:
>
>> Hello Dennis,
>>
>> On May 17, 2010, at 22:00 , Crissman, Dennis wrote:
>>
>>> I have been following the community for sometime, but this is my first
>>> posting back.
>>
>> Good to hear from you!
>>
>>> I am attempting to stand up the server and gateway. Aside from the two felix
>>> bundles mentioned below, I have run into some additional problems.
>>
>>> Before I get to that, when I first attempted to run both I got the following
>>> error message:
>>> =====
>>> -> Felix 2.0.1 : connecting...
>>> Oops, there has been a problem!
>>> URL [mvn:org.apache.felix/org.apache.felix.main/2.0.1] could not be
>>> resolved.
>>> =====
>>> To resolve I simply added the missing package to the maven repository. Not
>>> sure if this is a dependency that was missed in the POM, but thought I might
>>> mention it.
>>
>> Over the last few days I've seen similar messages being posted on the Felix
>> mailing lists, see http://markmail.org/message/nyfsumyqgvsktjax for the
>> thread. I'm still not sure what exactly is causing this. There have been some
>> issues with the Felix download site, and with the OPS4J site hosting the Pax
>> Runner project. Let's see what comes out of this. It's definitely not a
>> problem on your end, I can reproduce the problem here.
>>
>>> After that hurdle, I am now getting different error messages for each.
>>>
>>> Server:
>>> org.ops4j.pax.runner.platform.PlatformException:
>>> [file:/path/apache-ace/ace-devserver/ace-bundles/surefire-testng-2.5.jar] is
>>> not a valid bundle
>>
>> Just committed a fix for that (rev 945358). I accidentally forgot to mark
>> this
>> bundle as <scope>test</scope> so it ended up in the distribution.
>>
>>> Gateway:
>>> Felix actually stands up, but a series of exceptions are thrown. I will
>>> attach them to keep this email short, but they all seem to revolve around
>>> junit.framework being unresolved.
>>
>> Could be related to the problem above.
>>
>>> Any assistance on these would be appreciated.
>>
>> Hope this helps!
>>
>> Greetings, Marcel
>>
>>
>>
>
>
>
>
>
> --
> The sender of this email subscribes to Perimeter E-Security's email
> anti-virus service. This email has been scanned for malicious code and is
> believed to be virus free. For more information on email security please
> visit: http://www.perimeterusa.com/services/messaging
> This communication is confidential, intended only for the named recipient(s)
> above and may contain trade secrets or other information that is exempt from
> disclosure under applicable law. Any use, dissemination, distribution or
> copying of this communication by anyone other than the named recipient(s) is
> strictly prohibited. If you have received this communication in error, please
> delete the email and immediately notify our Command Center at 203-541-3444.
>
> Thanks
--
The sender of this email subscribes to Perimeter E-Security's email
anti-virus service. This email has been scanned for malicious code and is
believed to be virus free. For more information on email security please
visit: http://www.perimeterusa.com/services/messaging
This communication is confidential, intended only for the named recipient(s)
above and may contain trade secrets or other information that is exempt from
disclosure under applicable law. Any use, dissemination, distribution or
copying of this communication by anyone other than the named recipient(s) is
strictly prohibited. If you have received this communication in error, please
delete the email and immediately notify our Command Center at 203-541-3444.
Thanks
Re: Maven migration, almost there.
Posted by "Crissman, Dennis" <dc...@perimeterusa.com>.
I pulled down the POM change and re-packaged. It looks like I am getting the
same, or at least similar, error messages as before. See attached for
details.
On 5/17/10 4:42 PM, "Marcel Offermans" <ma...@luminis.nl> wrote:
> Hello Dennis,
>
> On May 17, 2010, at 22:00 , Crissman, Dennis wrote:
>
>> I have been following the community for sometime, but this is my first
>> posting back.
>
> Good to hear from you!
>
>> I am attempting to stand up the server and gateway. Aside from the two felix
>> bundles mentioned below, I have run into some additional problems.
>
>> Before I get to that, when I first attempted to run both I got the following
>> error message:
>> =====
>> -> Felix 2.0.1 : connecting...
>> Oops, there has been a problem!
>> URL [mvn:org.apache.felix/org.apache.felix.main/2.0.1] could not be
>> resolved.
>> =====
>> To resolve I simply added the missing package to the maven repository. Not
>> sure if this is a dependency that was missed in the POM, but thought I might
>> mention it.
>
> Over the last few days I've seen similar messages being posted on the Felix
> mailing lists, see http://markmail.org/message/nyfsumyqgvsktjax for the
> thread. I'm still not sure what exactly is causing this. There have been some
> issues with the Felix download site, and with the OPS4J site hosting the Pax
> Runner project. Let's see what comes out of this. It's definitely not a
> problem on your end, I can reproduce the problem here.
>
>> After that hurdle, I am now getting different error messages for each.
>>
>> Server:
>> org.ops4j.pax.runner.platform.PlatformException:
>> [file:/path/apache-ace/ace-devserver/ace-bundles/surefire-testng-2.5.jar] is
>> not a valid bundle
>
> Just committed a fix for that (rev 945358). I accidentally forgot to mark this
> bundle as <scope>test</scope> so it ended up in the distribution.
>
>> Gateway:
>> Felix actually stands up, but a series of exceptions are thrown. I will
>> attach them to keep this email short, but they all seem to revolve around
>> junit.framework being unresolved.
>
> Could be related to the problem above.
>
>> Any assistance on these would be appreciated.
>
> Hope this helps!
>
> Greetings, Marcel
>
>
>
--
The sender of this email subscribes to Perimeter E-Security's email
anti-virus service. This email has been scanned for malicious code and is
believed to be virus free. For more information on email security please
visit: http://www.perimeterusa.com/services/messaging
This communication is confidential, intended only for the named recipient(s)
above and may contain trade secrets or other information that is exempt from
disclosure under applicable law. Any use, dissemination, distribution or
copying of this communication by anyone other than the named recipient(s) is
strictly prohibited. If you have received this communication in error, please
delete the email and immediately notify our Command Center at 203-541-3444.
Thanks
Re: Maven migration, almost there.
Posted by Marcel Offermans <ma...@luminis.nl>.
Hello Dennis,
On May 17, 2010, at 22:00 , Crissman, Dennis wrote:
> I have been following the community for sometime, but this is my first
> posting back.
Good to hear from you!
> I am attempting to stand up the server and gateway. Aside from the two felix
> bundles mentioned below, I have run into some additional problems.
> Before I get to that, when I first attempted to run both I got the following
> error message:
> =====
> -> Felix 2.0.1 : connecting...
> Oops, there has been a problem!
> URL [mvn:org.apache.felix/org.apache.felix.main/2.0.1] could not be
> resolved.
> =====
> To resolve I simply added the missing package to the maven repository. Not
> sure if this is a dependency that was missed in the POM, but thought I might
> mention it.
Over the last few days I've seen similar messages being posted on the Felix mailing lists, see http://markmail.org/message/nyfsumyqgvsktjax for the thread. I'm still not sure what exactly is causing this. There have been some issues with the Felix download site, and with the OPS4J site hosting the Pax Runner project. Let's see what comes out of this. It's definitely not a problem on your end, I can reproduce the problem here.
> After that hurdle, I am now getting different error messages for each.
>
> Server:
> org.ops4j.pax.runner.platform.PlatformException:
> [file:/path/apache-ace/ace-devserver/ace-bundles/surefire-testng-2.5.jar] is
> not a valid bundle
Just committed a fix for that (rev 945358). I accidentally forgot to mark this bundle as <scope>test</scope> so it ended up in the distribution.
> Gateway:
> Felix actually stands up, but a series of exceptions are thrown. I will
> attach them to keep this email short, but they all seem to revolve around
> junit.framework being unresolved.
Could be related to the problem above.
> Any assistance on these would be appreciated.
Hope this helps!
Greetings, Marcel
Re: Maven migration, almost there.
Posted by "Crissman, Dennis" <dc...@perimeterusa.com>.
Greetings,
I have been following the community for sometime, but this is my first
posting back.
I am attempting to stand up the server and gateway. Aside from the two felix
bundles mentioned below, I have run into some additional problems.
Before I get to that, when I first attempted to run both I got the following
error message:
=====
-> Felix 2.0.1 : connecting...
Oops, there has been a problem!
URL [mvn:org.apache.felix/org.apache.felix.main/2.0.1] could not be
resolved.
=====
To resolve I simply added the missing package to the maven repository. Not
sure if this is a dependency that was missed in the POM, but thought I might
mention it.
After that hurdle, I am now getting different error messages for each.
Server:
org.ops4j.pax.runner.platform.PlatformException:
[file:/path/apache-ace/ace-devserver/ace-bundles/surefire-testng-2.5.jar] is
not a valid bundle
Gateway:
Felix actually stands up, but a series of exceptions are thrown. I will
attach them to keep this email short, but they all seem to revolve around
junit.framework being unresolved.
Any assistance on these would be appreciated.
Thanks,
Dennis
On 3/20/10 8:16 AM, "Marcel Offermans" <ma...@luminis.nl> wrote:
> On Mar 19, 2010, at 0:18 , Marcel Offermans wrote:
>
>> There is one remaining issue, and I can't seem to make that work, even with
>> the example that Jean-Baptiste provided, and that is the WebUI bundle
>> (ace-webui). This is a GWT based WAR file that has been converted into a
>> bundle (JAR) file, adding some specific OSGi metadata. Please check the
>> bundle you get when building legacy/core (in deploy/bundle) for reference.
>>
>> I tried using the URL handler to dynamically wrap a WAR but that does not
>> seem to get me a fully working bundle in this case. It seems to work but
>> interaction with the server is not working, and the URL handler does not pick
>> up on the Activator that is in there and that must be invoked to hook the WAR
>> up to the rest of the bundles.
>
> With some help of Toni, yesterday we finally made this bundle work. Of course
> there were still a few other issues that prevented the whole system from
> working properly, but I feel those have been addressed now too.
>
> The whole build works, provided you make sure that you build some "snapshots"
> that ACE depends upon first. These are some bundles that reside in the Apache
> Felix project and have not yet been released (in this form or at all):
>
> Dependency Manager: we migrated to the 3.x version, which broke some APIs and
> is still under construction (we don't use the features that are being worked
> on yet, so from our point of view its using the stable bits).
>
> Deployment Admin: which has also been updated to use 3.x of the dependency
> manager and is still unreleased (mostly because of a missing feature that ACE
> does not use).
>
> So build those first, then to do a full build, use:
>
> mvn clean install -Prelease,targets
>
> If all of that worked, you should have two working distributions: a server and
> a target (in ace-target-devserver/target/ and ace-target-devgateway/target/
> where you can both find zip files and a folder of the same name).
>
> You can run both from a shell with:
>
> sh run.sh
>
> Then point your browser to:
>
> http://localhost:8080/webui/
>
> Now you should be able to see the target, create features, distributions, add
> artifacts (place them in the store/ folder first and then add them via the UI)
> and link them all together.
>
> There's still plenty of work to do. We should migrate both the unit (ACE-78)
> and integration tests (ACE-79) and we should discuss grouping our artifacts
> into folders to get a better overview (the flat list of artifacts is
> confusing).
>
> Greetings, Marcel
>
>
>
--
The sender of this email subscribes to Perimeter E-Security's email
anti-virus service. This email has been scanned for malicious code and is
believed to be virus free. For more information on email security please
visit: http://www.perimeterusa.com/services/messaging
This communication is confidential, intended only for the named recipient(s)
above and may contain trade secrets or other information that is exempt from
disclosure under applicable law. Any use, dissemination, distribution or
copying of this communication by anyone other than the named recipient(s) is
strictly prohibited. If you have received this communication in error, please
delete the email and immediately notify our Command Center at 203-541-3444.
Thanks
Re: Maven migration, almost there.
Posted by Marcel Offermans <ma...@luminis.nl>.
On Mar 19, 2010, at 0:18 , Marcel Offermans wrote:
> There is one remaining issue, and I can't seem to make that work, even with the example that Jean-Baptiste provided, and that is the WebUI bundle (ace-webui). This is a GWT based WAR file that has been converted into a bundle (JAR) file, adding some specific OSGi metadata. Please check the bundle you get when building legacy/core (in deploy/bundle) for reference.
>
> I tried using the URL handler to dynamically wrap a WAR but that does not seem to get me a fully working bundle in this case. It seems to work but interaction with the server is not working, and the URL handler does not pick up on the Activator that is in there and that must be invoked to hook the WAR up to the rest of the bundles.
With some help of Toni, yesterday we finally made this bundle work. Of course there were still a few other issues that prevented the whole system from working properly, but I feel those have been addressed now too.
The whole build works, provided you make sure that you build some "snapshots" that ACE depends upon first. These are some bundles that reside in the Apache Felix project and have not yet been released (in this form or at all):
Dependency Manager: we migrated to the 3.x version, which broke some APIs and is still under construction (we don't use the features that are being worked on yet, so from our point of view its using the stable bits).
Deployment Admin: which has also been updated to use 3.x of the dependency manager and is still unreleased (mostly because of a missing feature that ACE does not use).
So build those first, then to do a full build, use:
mvn clean install -Prelease,targets
If all of that worked, you should have two working distributions: a server and a target (in ace-target-devserver/target/ and ace-target-devgateway/target/ where you can both find zip files and a folder of the same name).
You can run both from a shell with:
sh run.sh
Then point your browser to:
http://localhost:8080/webui/
Now you should be able to see the target, create features, distributions, add artifacts (place them in the store/ folder first and then add them via the UI) and link them all together.
There's still plenty of work to do. We should migrate both the unit (ACE-78) and integration tests (ACE-79) and we should discuss grouping our artifacts into folders to get a better overview (the flat list of artifacts is confusing).
Greetings, Marcel
Re: Maven migration, almost there.
Posted by Toni Menzel <to...@okidokiteam.com>.
On Fri, Mar 19, 2010 at 12:18 AM, Marcel Offermans <
marcel.offermans@luminis.nl> wrote:
> Hey guys,
>
> Over the last day or two I've been working hard on fixing all the small
> issues in the Maven build. I've managed to fix most of them, all the bundles
> are working and with the help of Toni I managed to get some Knopflerfish
> bundles into the assembly for the server.
>
> There is one remaining issue, and I can't seem to make that work, even with
> the example that Jean-Baptiste provided, and that is the WebUI bundle
> (ace-webui). This is a GWT based WAR file that has been converted into a
> bundle (JAR) file, adding some specific OSGi metadata. Please check the
> bundle you get when building legacy/core (in deploy/bundle) for reference.
>
> I tried using the URL handler to dynamically wrap a WAR but that does not
> seem to get me a fully working bundle in this case. It seems to work but
> interaction with the server is not working, and the URL handler does not
> pick up on the Activator that is in there and that must be invoked to hook
> the WAR up to the rest of the bundles.
>
> Anyway, this seems to be a pretty advanced use case for Maven, and I can
> definitely use some help from some of the Maven experts in the project.
> We're almost there! :)
>
> Greetings, Marcel
>
>
Well, Maven is not turing complete like Ant is.
Will have a look at that.