OK, clear.
It makes sense.
Thanks
Regards
JB
On 02/23/2011 02:08 PM, Guillaume Nodet wrote:
Well, that's clearly a nice to have, but I was talking about a way to
actually build the same bundle for the user, so a source distribution
which should work as you describe using the maven source plugin.
On Wed, Feb 23, 2011 at 14:01, Jean-Baptiste Onofré<[email protected]> wrote:
Just to be sure:
you're talking about the sources coming from the tiers dependency ?
In that case, you need to add it in the bundle-pom.
Regards
JB
On 02/23/2011 01:57 PM, Jean-Baptiste Onofré wrote:
+1
We do it in ACE simply using:
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-source-plugin</artifactId>
<executions>
<execution>
<id>attach-sources</id>
<phase>verify</phase>
<goals>
<goal>jar</goal>
</goals>
</execution>
</executions>
</plugin>
If all are OK, I will do the enhancement.
Regards
JB
On 02/23/2011 01:56 PM, Guillaume Nodet wrote:
We need to have a source distribution for bundles (i mean third party
libraries we turn into osgi bundles) we release, that's a clear ASF
policy and we don't really conform to it.
It should be quite easy to do in the parent bundle pom but we need to
do that before releasing anymore bundles.
