You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@aries.apache.org by Jeremy Hughes <hu...@apache.org> on 2011/10/24 18:44:24 UTC
Blueprint release
I've been staging all the bundles up to and including (from a
dependency perspective) the Blueprint ones. I'm hitting a problem in
staging the blueprint-core module. The
org.apache.aries.blueprint.core-0.4.jar that I get after running mvn
release:prepare includes the /org/apache/aries/blueprint/blueprint.xsd
file. Then I carry out the mvn release:perform step (which checks out
the tag that was created into target/checkout) and that creates
another org.apache.aries.blueprint.core-0.4.jar built from the newly
checked-out tag. But the blueprint.xsd file is missing from this
binary? If anyone has any idea what is happening, please say.
Thanks,
Jeremy
Re: Blueprint release
Posted by Jeremy Hughes <hu...@apache.org>.
On 25 October 2011 00:32, Guillaume Nodet <gn...@gmail.com> wrote:
> IIRC, I origianlly included the xsd only in the blueprint-core (it's
> actually needed for validation) but was asked to put in the api jar (because
> it could be considered part of the api).
> I'd remove it from the api if we need to remove one.
With help from Tim Ward I think I have the right maven-bundle-plugin
incantation. Adding:
<Include-Resource>
{maven-resources},
/org/apache/aries/blueprint/blueprint.xsd=/org/osgi/service/blueprint/blueprint.xsd
</Include-Resource>
to the <properties> element and removing the resources plugin
configuration gives me the blueprint.xsd in the core.
>
> On Tue, Oct 25, 2011 at 00:12, David Jencks <da...@yahoo.com> wrote:
>
>> Hi Jeremy,
>>
>> Apparently the maven-dependency-plugin and maven-bundle-plugin don't relate
>> well enough for my idea to work. However looking at the jar, it already has
>> the blueprint.xsd from the api bundle at the same location as the api
>> bundle, org/osgi/service/blueprint/blueprint.xsd Why do there need to be
>> two copies of the schema in the jar?
>>
>> thanks
>> david jencks
>>
>> On Oct 24, 2011, at 2:39 PM, Jeremy Hughes wrote:
>>
>> > Hi David, totally agree. This shouldn't have been done and is now a
>> > particular problem since we're releasing at a finer grained level. If you
>> > have any cycles to have a go at this I'd appreciate it otherwise I'll be
>> > looking in the morning.
>> >
>> > Thx, Jeremy
>> > On 24 Oct 2011 20:22, "David Jencks" <da...@yahoo.com> wrote:
>> >
>> >> stunts like that are definitely a release blocker (I'd vote -1 if I knew
>> >> about this even if it didn't break the build). What's the goal of this?
>> To
>> >> have the same resource (xsd) in both the api and the implementation jar?
>> If
>> >> this is really a good idea then you should use the
>> maven-dependency-plugin
>> >> to extract the xsd from the blueprint-api jar into the target path. I'd
>> >> think duplicating resources should be avoided if at all possible
>> however.
>> >>
>> >> thanks
>> >> david jencks
>> >>
>> >> On Oct 24, 2011, at 9:47 AM, Jeremy Hughes wrote:
>> >>
>> >>> OK, I think I may have found the rogue element in the pom.xml. The
>> >>> resource plugin is going up a directory and into blueprint-api which
>> >>> of course isn't there are the release:perform stage.
>> >>>
>> >>> <build>
>> >>> <resources>
>> >>> <resource>
>> >>> <directory>src/main/resources</directory>
>> >>> </resource>
>> >>> <resource>
>> >>>
>> >>>
>> >>
>> <directory>../blueprint-api/src/main/resources/org/osgi/service/blueprint</directory>
>> >>> <targetPath>org/apache/aries/blueprint</targetPath>
>> >>> <includes>
>> >>> <include>blueprint.xsd</include>
>> >>> </includes>
>> >>> </resource>
>> >>> <resource>
>> >>> <directory>${project.build.sourceDirectory}</directory>
>> >>> <includes>
>> >>> <include>**/packageinfo</include>
>> >>> </includes>
>> >>> </resource>
>> >>> </resources>
>> >>> </build>
>> >>>
>> >>> On 24 October 2011 17:44, Jeremy Hughes <hu...@apache.org> wrote:
>> >>>> I've been staging all the bundles up to and including (from a
>> >>>> dependency perspective) the Blueprint ones. I'm hitting a problem in
>> >>>> staging the blueprint-core module. The
>> >>>> org.apache.aries.blueprint.core-0.4.jar that I get after running mvn
>> >>>> release:prepare includes the /org/apache/aries/blueprint/blueprint.xsd
>> >>>> file. Then I carry out the mvn release:perform step (which checks out
>> >>>> the tag that was created into target/checkout) and that creates
>> >>>> another org.apache.aries.blueprint.core-0.4.jar built from the newly
>> >>>> checked-out tag. But the blueprint.xsd file is missing from this
>> >>>> binary? If anyone has any idea what is happening, please say.
>> >>>>
>> >>>> Thanks,
>> >>>> Jeremy
>> >>>>
>> >>
>> >>
>>
>>
>
>
> --
> ------------------------
> Guillaume Nodet
> ------------------------
> Blog: http://gnodet.blogspot.com/
> ------------------------
> Open Source SOA
> http://fusesource.com
>
Re: Blueprint release
Posted by Guillaume Nodet <gn...@gmail.com>.
IIRC, I origianlly included the xsd only in the blueprint-core (it's
actually needed for validation) but was asked to put in the api jar (because
it could be considered part of the api).
I'd remove it from the api if we need to remove one.
On Tue, Oct 25, 2011 at 00:12, David Jencks <da...@yahoo.com> wrote:
> Hi Jeremy,
>
> Apparently the maven-dependency-plugin and maven-bundle-plugin don't relate
> well enough for my idea to work. However looking at the jar, it already has
> the blueprint.xsd from the api bundle at the same location as the api
> bundle, org/osgi/service/blueprint/blueprint.xsd Why do there need to be
> two copies of the schema in the jar?
>
> thanks
> david jencks
>
> On Oct 24, 2011, at 2:39 PM, Jeremy Hughes wrote:
>
> > Hi David, totally agree. This shouldn't have been done and is now a
> > particular problem since we're releasing at a finer grained level. If you
> > have any cycles to have a go at this I'd appreciate it otherwise I'll be
> > looking in the morning.
> >
> > Thx, Jeremy
> > On 24 Oct 2011 20:22, "David Jencks" <da...@yahoo.com> wrote:
> >
> >> stunts like that are definitely a release blocker (I'd vote -1 if I knew
> >> about this even if it didn't break the build). What's the goal of this?
> To
> >> have the same resource (xsd) in both the api and the implementation jar?
> If
> >> this is really a good idea then you should use the
> maven-dependency-plugin
> >> to extract the xsd from the blueprint-api jar into the target path. I'd
> >> think duplicating resources should be avoided if at all possible
> however.
> >>
> >> thanks
> >> david jencks
> >>
> >> On Oct 24, 2011, at 9:47 AM, Jeremy Hughes wrote:
> >>
> >>> OK, I think I may have found the rogue element in the pom.xml. The
> >>> resource plugin is going up a directory and into blueprint-api which
> >>> of course isn't there are the release:perform stage.
> >>>
> >>> <build>
> >>> <resources>
> >>> <resource>
> >>> <directory>src/main/resources</directory>
> >>> </resource>
> >>> <resource>
> >>>
> >>>
> >>
> <directory>../blueprint-api/src/main/resources/org/osgi/service/blueprint</directory>
> >>> <targetPath>org/apache/aries/blueprint</targetPath>
> >>> <includes>
> >>> <include>blueprint.xsd</include>
> >>> </includes>
> >>> </resource>
> >>> <resource>
> >>> <directory>${project.build.sourceDirectory}</directory>
> >>> <includes>
> >>> <include>**/packageinfo</include>
> >>> </includes>
> >>> </resource>
> >>> </resources>
> >>> </build>
> >>>
> >>> On 24 October 2011 17:44, Jeremy Hughes <hu...@apache.org> wrote:
> >>>> I've been staging all the bundles up to and including (from a
> >>>> dependency perspective) the Blueprint ones. I'm hitting a problem in
> >>>> staging the blueprint-core module. The
> >>>> org.apache.aries.blueprint.core-0.4.jar that I get after running mvn
> >>>> release:prepare includes the /org/apache/aries/blueprint/blueprint.xsd
> >>>> file. Then I carry out the mvn release:perform step (which checks out
> >>>> the tag that was created into target/checkout) and that creates
> >>>> another org.apache.aries.blueprint.core-0.4.jar built from the newly
> >>>> checked-out tag. But the blueprint.xsd file is missing from this
> >>>> binary? If anyone has any idea what is happening, please say.
> >>>>
> >>>> Thanks,
> >>>> Jeremy
> >>>>
> >>
> >>
>
>
--
------------------------
Guillaume Nodet
------------------------
Blog: http://gnodet.blogspot.com/
------------------------
Open Source SOA
http://fusesource.com
Re: Blueprint release
Posted by David Jencks <da...@yahoo.com>.
Hi Jeremy,
Apparently the maven-dependency-plugin and maven-bundle-plugin don't relate well enough for my idea to work. However looking at the jar, it already has the blueprint.xsd from the api bundle at the same location as the api bundle, org/osgi/service/blueprint/blueprint.xsd Why do there need to be two copies of the schema in the jar?
thanks
david jencks
On Oct 24, 2011, at 2:39 PM, Jeremy Hughes wrote:
> Hi David, totally agree. This shouldn't have been done and is now a
> particular problem since we're releasing at a finer grained level. If you
> have any cycles to have a go at this I'd appreciate it otherwise I'll be
> looking in the morning.
>
> Thx, Jeremy
> On 24 Oct 2011 20:22, "David Jencks" <da...@yahoo.com> wrote:
>
>> stunts like that are definitely a release blocker (I'd vote -1 if I knew
>> about this even if it didn't break the build). What's the goal of this? To
>> have the same resource (xsd) in both the api and the implementation jar? If
>> this is really a good idea then you should use the maven-dependency-plugin
>> to extract the xsd from the blueprint-api jar into the target path. I'd
>> think duplicating resources should be avoided if at all possible however.
>>
>> thanks
>> david jencks
>>
>> On Oct 24, 2011, at 9:47 AM, Jeremy Hughes wrote:
>>
>>> OK, I think I may have found the rogue element in the pom.xml. The
>>> resource plugin is going up a directory and into blueprint-api which
>>> of course isn't there are the release:perform stage.
>>>
>>> <build>
>>> <resources>
>>> <resource>
>>> <directory>src/main/resources</directory>
>>> </resource>
>>> <resource>
>>>
>>>
>> <directory>../blueprint-api/src/main/resources/org/osgi/service/blueprint</directory>
>>> <targetPath>org/apache/aries/blueprint</targetPath>
>>> <includes>
>>> <include>blueprint.xsd</include>
>>> </includes>
>>> </resource>
>>> <resource>
>>> <directory>${project.build.sourceDirectory}</directory>
>>> <includes>
>>> <include>**/packageinfo</include>
>>> </includes>
>>> </resource>
>>> </resources>
>>> </build>
>>>
>>> On 24 October 2011 17:44, Jeremy Hughes <hu...@apache.org> wrote:
>>>> I've been staging all the bundles up to and including (from a
>>>> dependency perspective) the Blueprint ones. I'm hitting a problem in
>>>> staging the blueprint-core module. The
>>>> org.apache.aries.blueprint.core-0.4.jar that I get after running mvn
>>>> release:prepare includes the /org/apache/aries/blueprint/blueprint.xsd
>>>> file. Then I carry out the mvn release:perform step (which checks out
>>>> the tag that was created into target/checkout) and that creates
>>>> another org.apache.aries.blueprint.core-0.4.jar built from the newly
>>>> checked-out tag. But the blueprint.xsd file is missing from this
>>>> binary? If anyone has any idea what is happening, please say.
>>>>
>>>> Thanks,
>>>> Jeremy
>>>>
>>
>>
Re: Blueprint release
Posted by Jeremy Hughes <hu...@apache.org>.
Hi David, totally agree. This shouldn't have been done and is now a
particular problem since we're releasing at a finer grained level. If you
have any cycles to have a go at this I'd appreciate it otherwise I'll be
looking in the morning.
Thx, Jeremy
On 24 Oct 2011 20:22, "David Jencks" <da...@yahoo.com> wrote:
> stunts like that are definitely a release blocker (I'd vote -1 if I knew
> about this even if it didn't break the build). What's the goal of this? To
> have the same resource (xsd) in both the api and the implementation jar? If
> this is really a good idea then you should use the maven-dependency-plugin
> to extract the xsd from the blueprint-api jar into the target path. I'd
> think duplicating resources should be avoided if at all possible however.
>
> thanks
> david jencks
>
> On Oct 24, 2011, at 9:47 AM, Jeremy Hughes wrote:
>
> > OK, I think I may have found the rogue element in the pom.xml. The
> > resource plugin is going up a directory and into blueprint-api which
> > of course isn't there are the release:perform stage.
> >
> > <build>
> > <resources>
> > <resource>
> > <directory>src/main/resources</directory>
> > </resource>
> > <resource>
> >
> >
> <directory>../blueprint-api/src/main/resources/org/osgi/service/blueprint</directory>
> > <targetPath>org/apache/aries/blueprint</targetPath>
> > <includes>
> > <include>blueprint.xsd</include>
> > </includes>
> > </resource>
> > <resource>
> > <directory>${project.build.sourceDirectory}</directory>
> > <includes>
> > <include>**/packageinfo</include>
> > </includes>
> > </resource>
> > </resources>
> > </build>
> >
> > On 24 October 2011 17:44, Jeremy Hughes <hu...@apache.org> wrote:
> >> I've been staging all the bundles up to and including (from a
> >> dependency perspective) the Blueprint ones. I'm hitting a problem in
> >> staging the blueprint-core module. The
> >> org.apache.aries.blueprint.core-0.4.jar that I get after running mvn
> >> release:prepare includes the /org/apache/aries/blueprint/blueprint.xsd
> >> file. Then I carry out the mvn release:perform step (which checks out
> >> the tag that was created into target/checkout) and that creates
> >> another org.apache.aries.blueprint.core-0.4.jar built from the newly
> >> checked-out tag. But the blueprint.xsd file is missing from this
> >> binary? If anyone has any idea what is happening, please say.
> >>
> >> Thanks,
> >> Jeremy
> >>
>
>
Re: Blueprint release
Posted by David Jencks <da...@yahoo.com>.
stunts like that are definitely a release blocker (I'd vote -1 if I knew about this even if it didn't break the build). What's the goal of this? To have the same resource (xsd) in both the api and the implementation jar? If this is really a good idea then you should use the maven-dependency-plugin to extract the xsd from the blueprint-api jar into the target path. I'd think duplicating resources should be avoided if at all possible however.
thanks
david jencks
On Oct 24, 2011, at 9:47 AM, Jeremy Hughes wrote:
> OK, I think I may have found the rogue element in the pom.xml. The
> resource plugin is going up a directory and into blueprint-api which
> of course isn't there are the release:perform stage.
>
> <build>
> <resources>
> <resource>
> <directory>src/main/resources</directory>
> </resource>
> <resource>
>
> <directory>../blueprint-api/src/main/resources/org/osgi/service/blueprint</directory>
> <targetPath>org/apache/aries/blueprint</targetPath>
> <includes>
> <include>blueprint.xsd</include>
> </includes>
> </resource>
> <resource>
> <directory>${project.build.sourceDirectory}</directory>
> <includes>
> <include>**/packageinfo</include>
> </includes>
> </resource>
> </resources>
> </build>
>
> On 24 October 2011 17:44, Jeremy Hughes <hu...@apache.org> wrote:
>> I've been staging all the bundles up to and including (from a
>> dependency perspective) the Blueprint ones. I'm hitting a problem in
>> staging the blueprint-core module. The
>> org.apache.aries.blueprint.core-0.4.jar that I get after running mvn
>> release:prepare includes the /org/apache/aries/blueprint/blueprint.xsd
>> file. Then I carry out the mvn release:perform step (which checks out
>> the tag that was created into target/checkout) and that creates
>> another org.apache.aries.blueprint.core-0.4.jar built from the newly
>> checked-out tag. But the blueprint.xsd file is missing from this
>> binary? If anyone has any idea what is happening, please say.
>>
>> Thanks,
>> Jeremy
>>
Re: Blueprint release
Posted by Jeremy Hughes <hu...@apache.org>.
OK, I think I may have found the rogue element in the pom.xml. The
resource plugin is going up a directory and into blueprint-api which
of course isn't there are the release:perform stage.
<build>
<resources>
<resource>
<directory>src/main/resources</directory>
</resource>
<resource>
<directory>../blueprint-api/src/main/resources/org/osgi/service/blueprint</directory>
<targetPath>org/apache/aries/blueprint</targetPath>
<includes>
<include>blueprint.xsd</include>
</includes>
</resource>
<resource>
<directory>${project.build.sourceDirectory}</directory>
<includes>
<include>**/packageinfo</include>
</includes>
</resource>
</resources>
</build>
On 24 October 2011 17:44, Jeremy Hughes <hu...@apache.org> wrote:
> I've been staging all the bundles up to and including (from a
> dependency perspective) the Blueprint ones. I'm hitting a problem in
> staging the blueprint-core module. The
> org.apache.aries.blueprint.core-0.4.jar that I get after running mvn
> release:prepare includes the /org/apache/aries/blueprint/blueprint.xsd
> file. Then I carry out the mvn release:perform step (which checks out
> the tag that was created into target/checkout) and that creates
> another org.apache.aries.blueprint.core-0.4.jar built from the newly
> checked-out tag. But the blueprint.xsd file is missing from this
> binary? If anyone has any idea what is happening, please say.
>
> Thanks,
> Jeremy
>