<div dir="ltr">3) You can put the zip file in an Addon on the classpath to accomplish that goal.</div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Jan 27, 2015 at 10:37 PM, Ondrej Zizka <span dir="ltr"><<a href="mailto:ozizka@redhat.com" target="_blank">ozizka@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000">
Reading this late; I already "externalized".<br>
<br>
There are 3 parts:<br>
1st is the actual code to read nexus index<br>
2nd executes it and creates a ZIP artifact<br>
3rd is the ruleset which needs it.<br>
<br>
And here comes my question: Can I make that ZIP (in step 2) a Forge
addon, and then put it as addon dep? Or is it somehow hardcoded to
just handle jars. (didn't try)<br>
<br>
Ondra<br>
<br>
<br>
<div>On 23.1.2015 19:25, Lincoln Baxter, III
wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">1) Eventually yes, but for now I think it's fine to
tie this information to our releases. Don't worry about this for
now. Businesses don't typically use the newest JARs in the
legacy apps they are trying to migrate ;) We'd probably even be
fine with data from 3 years ago.
<div><br>
<div>2) Just put it in our main windup/windup repo for now, in
the same module as the addon you're building.</div>
<div><br>
</div>
<div>3) Bundle it in the same addon that provides the
functionality for now, it will be easier to include in our
build. We can worry about externalizing it later. This will
also allow us to create a separate distribution just in case
people are worried about file size. (With Maven JAR
identification / Without Maven JAR identification)</div>
<div><br>
</div>
<div>4) Better to access on the classpath because you know its
location within the classloader. We can worry about
externalizing it later.</div>
</div>
<div><br>
</div>
<div>45 MB is not terrible. Nice job.</div>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Thu, Jan 22, 2015 at 5:00 AM, Ondrej
Zizka <span dir="ltr"><<a href="mailto:ozizka@redhat.com" target="_blank">ozizka@redhat.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000"> Hi,<br>
<br>
WRT <span title="WINDUP-459: Rules request: Identify
archives by their hash."> <a href="https://issues.jboss.org/browse/WINDUP-459" target="_blank">WINDUP-459</a> <span>Rules request:
Identify archives by their hash:<br>
<br>
I guess this need (for bulk data from an external
source) will appear in more rulesets.<br>
<br>
We agreed that the best way to build, store and
distribute the offline data will be best through
artifacts, resp. through a maven repo.<br>
<br>
1) Should it have independent release cycle? IMO it
should.<br>
2) If so - which git repo to put it to?<br>
3) Can Forge/Furnace work well with ZIP artifacts?
I.e, if there's a
<packaging>zip</packaging>, can that be an
addon?<br>
4) If something is an addon, is it better to access it
as a resource on classpath, or as a zip file, after
figuring out where it is on local FS?<br>
<br>
FYI, currently I just create a zip assembly </span></span><span title="WINDUP-459: Rules request: Identify archives by
their hash."><span><span title="WINDUP-459: Rules
request: Identify archives by their hash."><span>windup-nexusindexreader-mappings-<V>.jar</span></span>,
next to windup-nexusindexreader</span></span><span title="WINDUP-459: Rules request: Identify archives by
their hash."><span><span title="WINDUP-459: Rules
request: Identify archives by their hash."><span><span title="WINDUP-459: Rules request: Identify
archives by their hash."><span>-<V></span></span></span></span>.jar<br>
The artifact size is 45 MB.<br>
<br>
Regards,<br>
Ondra<br>
</span></span> </div>
<br>
_______________________________________________<br>
windup-dev mailing list<br>
<a href="mailto:windup-dev@lists.jboss.org" target="_blank">windup-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/windup-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/windup-dev</a><br>
</blockquote>
</div>
<br>
<br clear="all"><span class="HOEnZb"><font color="#888888">
<div><br>
</div>
-- <br>
<div>Lincoln Baxter, III<br>
<a href="http://ocpsoft.org" target="_blank">http://ocpsoft.org</a><br>
"Simpler is better."</div>
</font></span></div><span class="HOEnZb"><font color="#888888">
<br>
<fieldset></fieldset>
<br>
<pre>_______________________________________________
windup-dev mailing list
<a href="mailto:windup-dev@lists.jboss.org" target="_blank">windup-dev@lists.jboss.org</a>
<a href="https://lists.jboss.org/mailman/listinfo/windup-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/windup-dev</a></pre>
</font></span></blockquote>
<br>
</div>
<br>_______________________________________________<br>
windup-dev mailing list<br>
<a href="mailto:windup-dev@lists.jboss.org">windup-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/windup-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/windup-dev</a><br></blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature">Lincoln Baxter, III<br><a href="http://ocpsoft.org" target="_blank">http://ocpsoft.org</a><br>"Simpler is better."</div>
</div>