Hi Dale,
today I greatly updated the plugin to filter out unwanted artifacts.
Now the plugin has a configuration section:
<configuration>
<filterRules>
<!-- Filter out all test-jars -->
<filterRule>
<type>test-jar</type>
</filterRule>
<!-- Filter out the signatures of all test-jars -->
<filterRule>
<type>jar.asc</type>
<classifier>tests</classifier>
</filterRule>
<!-- Filter out any source release archives -->
<filterRule>
<classifier>source-release</classifier>
</filterRule>
</filterRules>
</configuration>
Here each "filter" rule is a different rule that would have an artifact
excluded. I added the "source-release" rule and it correctly filtered all
source-release related artifacts from deployment. Now if we find something else
to exclude, we wouldn't have to re-deploy the plugin and even re-release it.
Chris
Am 21.02.18, 20:19 schrieb "Christofer Dutz" <[email protected]>:
Hi Dale,
I'll look into this. But not today as I'm not feeling that well.
Chris
Am 21.02.18, 18:43 schrieb "Dale LaBossiere" <[email protected]>:
Thanks Chris.
I’ve rerun the process and all of the test files are now eliminated
from the staged repo. yay!
+1 on starting the vote to release the plugin.
Followup questions:
- are we in agreement that the edgent-parent source-release files in
the repo should NOT be present? (to clarify, those files are not the ones in
the official source release repo in dist.apache.org/repos/dist
<http://dist.apache.org/repos/dist>).
- if so, can the plugin, or some other tweak, eliminate them from the
repo?
Thanks,
— Dale
> On Feb 21, 2018, at 6:24 AM, Christofer Dutz
<[email protected]> wrote:
> ...
> so I updated the plugin to no longer deploy the test-jar asc files
and I re-deployed the plugin.
> So now all still existing problems should no longer be a problem.
>
> So if you've tested the plugin and now no problems remain, I thing we
could start a vote on releasing the plugin and hopefully never have to think
about it again ;-)
