Hi,
I opened https://issues.apache.org/jira/browse/ARIES-661 about the deployment
manifest.
The application-dependencies page looks somewhat better. You might want to
change the word "replacable" (possible to placate again?) and indicate for 3.1
what services you can implement rather than trying to replace something that
isn't there.
You made most of the pom changes I did. I also needed this:
--- blueprint/blueprint-bundle/pom.xml (revision 1125986)
+++ blueprint/blueprint-bundle/pom.xml (working copy)
@@ -105,7 +105,7 @@
<dependency>
<groupId>org.apache.aries.proxy</groupId>
<artifactId>org.apache.aries.proxy</artifactId>
- <version>0.3.1-SNAPSHOT</version>
+ <version>0.4-SNAPSHOT</version>
<scope>test</scope>
</dependency>
<dependency>
I'm not entirely sure why you're updating snapshots to snapshots rather than
released versions... I'd assume that the released versions would work or
someone would have already bumped the version to the latest snapshot.
thanks!
david jencks
On May 21, 2011, at 3:56 AM, Alasdair Nottingham wrote:
> Hi,
>
> Writing a deployment.mf with javax.servlet;{version->2.6.0} is
> definitely not right. So you should probably raise a bug for that.
>
> In 0.3.1 these two were removed:
>
> mavenBundle("org.apache.aries.application","org.apache.aries.application.noop.platform.repo"),
> mavenBundle("org.apache.aries.application","org.apache.aries.application.noop.postresolve.process"),
>
> the function was moved into the bundles that used those services.
> Those bundles still allow you to register a platform repository and
> postresolve processor service, and the service will be used. So the
> effect is the same, but you have less bundles. I'll update the
> instructions, the reason they are out of date because the instructions
> are for the last release (0.3), not the current development version.
>
> I am happy to fix the build problems you are seeing if you could
> provide me the information you have on what is wrong.
>
> Thanks
> Alasdair
>
> On 21 May 2011 06:08, David Jencks <[email protected]> wrote:
>> I'm seeing something that I think is a problem in the application 0.3 jars
>> when I integrate them in geronimo.
>>
>> It looks like aries is generating a Manifest for the deployment.mf with
>> reasonable Import-Package strings of the form
>> javax.servlet;version=\"2.6.0\" however when it is read into a
>> DeploymentManifestImpl and written out into the temporary file it gets
>> mangled into this:
>>
>> javax.servlet;{version->2.6.0},javax.servlet.jsp.el;{version->0.0.0},javax.servlet.jsp.tagext;{version->0.0.0},javax.servlet.jsp.resources;{version->0.0.0},javax.servlet.jsp;{version->0.0.0},javax.servlet.http;{version->2.6.0}
>>
>> Not too surprisingly, this string can't be understood by the manifest
>> parsing code. On the other hand, I can't be sure that this output isn't
>> intended and the parsing code is supposed to understand it.
>>
>> The conversion into a string is done in this method of
>> DeploymentMetadataImpl:
>>
>> private String getContentsAsString (Collection<Content> contents) {
>> StringBuilder builder = new StringBuilder();
>> boolean beginning = true;
>> for (Content c : contents) {
>> if (!!!beginning) {
>> builder.append(",");
>> }
>> builder.append(c);
>> beginning = false;
>>
>> }
>> return builder.toString();
>> }
>>
>>
>>
>> So far I've been stymied in trying to figure out where all the bits needed
>> for integration went in 0.3.1-SNAPSHOT so I'm not too close to being able to
>> look for a solution to this. Are there any instructions for integrating
>> 3.1-snapshot? Is there any dev list discussion about where stuff moved to
>> or why some of the noop packages mentioned in the instructions
>> http://aries.apache.org/documentation/application-dependencies.html have
>> disappeared?
>>
>> BTW trunk does not build for me. One of the application modules is missing
>> from applications/pom.xml and there is a reference to a no-longer existing
>> snapshot in the tools project. I hesitate to commit fixes for these simple
>> problems as the build structure of aries has morphed into something I don't
>> hope to understand.
>>
>> thanks
>> david jencks
>>
>>
>
>
>
> --
> Alasdair Nottingham
> [email protected]
